Management server, mobile terminal and account processing method

Abstract

The invention relates to a management server, a mobile terminal and an account processing method. A processor in the management server is configured to receive an initial right and interest transaction request which is sent by a terminal, aims at a third-party application and carries right and interest transaction information and a first bright account number and current version information of a system application; under the condition that a dark account bound with the first bright account is queried, the request is used for requesting the application server to superpose right and interest data corresponding to the right and interest transaction information and right and interest data under the dark account; and under the condition that the dark account bound with the first bright account is not queried, if the current version information represents that the system application is an application after version degradation, requesting the application server to superpose right and interest data corresponding to the right and interest transaction information and right and interest data under the second bright account. By adopting the method, the maximization of rights and interests can be ensured.

Description

Technical Field

[0001] This application relates to the field of computer technologies, and particularly to an administrative server, a mobile terminal, and an account processing method. Background Art

[0002] With the development of devices (such as smart TVs) and users' diverse demands for information, software development kits (SDKs) of more and more third-party applications can be integrated into applications, such as system applications of smart TVs. Further, users can access corresponding third-party applications by invoking the third-party application SDKs in the system applications.

[0003] Before a user accesses a third-party application based on a third-party application SDK, in addition to logging in to the account corresponding to the system application, the user also needs to log in with the plain account of the pre-registered third-party application, and the process is rather cumbersome. For this reason, in order to improve the convenience of users' access to third-party applications, in related technologies, after the user logs in to the account corresponding to the system application, a corresponding third-party hidden account can be directly created for the user, and the rights and interests data purchased by the user can be directly bound to the user's hidden account.

[0004] However, in actual scenarios, the system application version is lowered due to factors such as the device restoring to factory settings, so that the third-party application cannot be accessed using the hidden account anymore, and thus the rights and interests data in the hidden account cannot be used continuously, making the users' rights and interests data not fully utilized. Summary of the Invention

[0005] This application provides an administrative server, a mobile terminal, and an account processing method, which can ensure the full utilization of users' rights and interests data.

[0006] In a first aspect, some embodiments provide an administrative server, including:

[0007] A communication device configured to communicate with a terminal and an application server corresponding to a third-party application;

[0008] And at least one processor connected to the communication device and configured to:

[0009] Receive an initial rights and interests transaction request for a third-party application sent by the terminal; the initial rights and interests transaction request carries rights and interests transaction information, as well as a first plain account of the system application and current version information; the system application is an application corresponding to the administrative server in the device side;

[0010] In the case of querying a hidden account bound to the first plain account, send a first rights and interests transaction request to the application server; the first rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the hidden account;

[0011] In the case where the dark account bound to the first plain account is not queried, if the current version information indicates that the system application is an application after version downgrade, obtain the second plain account of the third-party application bound to the first plain account, and send a second rights trading request to the application server; the second rights trading request is used to request the application server to superimpose the rights data corresponding to the rights trading information on the rights data under the second plain account.

[0012] Among them, the binding relationships between the dark account, the first plain account, and the second plain account are constructed before the system application undergoes version downgrade; the dark account is an account used to authenticate the access behavior initiated by the third-party application software development kit (SDK) in the system application by the application server, and the first plain account cannot be directly authenticated by the application server.

[0013] In the above technical solution, on the one hand, by binding the first plain account, the dark account, and the second plain account to each other, in the subsequent process of using rights, whether the user logs in with the dark account or the second plain account, they can continue to use the superimposed rights data under the dark account and the second plain account based on the account binding relationship, thus enabling the full utilization of the user's rights data, that is, ensuring the maximization of the use of rights data; on the other hand, when the user purchases new rights data, giving priority to superimposing the rights data under the dark account can avoid the chaos of rights data superimposition. In addition, in the scenario where the first plain account is not bound to the dark account, by adopting a fallback strategy, that is, opening the rights data to the second plain account, the smooth progress of the user's rights trading is ensured.

[0014] In some embodiments, when the terminal is a mobile terminal and the device end is a display device, the first plain account and the current version information are obtained by the mobile terminal scanning the payment QR code presented in the system application; or,

[0015] When the terminal and the device end are the same display device, the first plain account is obtained by the display device according to the login operation of the system application.

[0016] In the above technical solution, in the interaction scenario among the display device, the mobile terminal, and the management server, an optional method of scan code payment is provided, and in the interaction scenario between the display device and the management server, an optional method of logging in the first plain account at the display device end is provided. That is, different optional methods are provided in different scenarios, which not only broadens the usage scenarios of the solution but also improves the user experience.

[0017] In some embodiments, after the processor executes sending the first rights trading request to the application server or sending the second rights trading request to the application server, it is further configured to:

[0018] Receive new entitlement data; wherein, the new entitlement data is the entitlement data obtained by superimposing the entitlement data corresponding to the entitlement transaction information and the entitlement data under the dark account, or the new entitlement data is the entitlement data obtained by superimposing the entitlement data corresponding to the entitlement transaction information and the entitlement data under the second clear account;

[0019] Use the new entitlement data to update the entitlement data associated with the first clear account.

[0020] In the above technical solution, by associating the first clear account with the entitlement data locally on the management server and dynamically updating based on the new entitlement data sent by the application server, on the one hand, by dynamically updating the entitlement data, the accuracy of the entitlement data stored locally on the management server can be ensured; on the other hand, in the case where it is necessary to display the entitlement data to the user or the user has a need to obtain the entitlement data, compared with obtaining the entitlement data from the application server in real time, obtaining the entitlement data from the management server locally has a faster response rate.

[0021] In some embodiments, the processor is further configured to:

[0022] In response to an entitlement query request carrying the first clear account sent by the device side, based on the first clear account, obtain the entitlement data associated with the first clear account from the entitlement data stored locally;

[0023] Feed back the obtained entitlement data to the device side.

[0024] In the above technical solution, on the one hand, by associating and storing the first clear account with the entitlement data locally on the management server, compared with accessing the application server to obtain the entitlement data, directly obtaining the entitlement from the management server has a faster response rate; on the other hand, by interacting with the device side to feed back the entitlement data to the device side, so that the device side can display the entitlement data in real time, thereby enabling the user to intuitively understand the entitlement situation under the third-party application.

[0025] In some embodiments, before the processor executes the initial entitlement transaction request for the third-party application sent by the receiving terminal, the processor is further configured to:

[0026] Receive the binding indication information sent by the receiving terminal; wherein, the binding indication information carries the first clear account and the second clear account;

[0027] Obtain the dark account bound to the first clear account, and send a light-dark binding request to the application server; wherein, the light-dark binding request is used to request the application server to perform light-dark binding on the second clear account and the dark account;

[0028] After receiving the successful binding message fed back by the application server, send a first rights transfer message to the application server; wherein, the first rights transfer message is used to instruct the application server to stack the rights data under the second explicit account with the rights data under the hidden account.

[0029] In the above technical solution, by performing explicit and hidden binding between the second explicit account and the hidden account bound to the first explicit account, and after the explicit and hidden binding is successful, stacking the rights data under the second explicit account with the rights data under the hidden account, it can ensure that the rights data of the same user under different accounts is no longer scattered, thereby ensuring the maximization of the use of user rights. Further, since the second explicit account and the hidden account are bound, the rights data under the second explicit account and the rights data under the hidden account are the same, that is, the rights data when the user accesses the third-party application based on the second explicit account or the hidden account subsequently are all consistent, realizing the sharing of the rights data of the user under the second explicit account and the hidden account.

[0030] In some embodiments, when the processor executes to obtain the hidden account bound to the first explicit account, it is configured to:

[0031] In the case where the corresponding hidden binding relationship cannot be queried based on the first explicit account, send a hidden account generation request to the application server; wherein, the hidden account generation request carries the first explicit account and the device identifier of the device side;

[0032] Obtain the hidden account fed back by the application server; wherein, the hidden account is generated by the application server according to the first explicit account and the device identifier;

[0033] Bind the first explicit account with the hidden account to generate the hidden binding relationship corresponding to the first explicit account;

[0034] Based on the first explicit account and the hidden binding relationship, query the hidden account bound to the first explicit account.

[0035] In the above technical solution, on the one hand, by instructing the application server to generate a hidden account, it provides conditions for the subsequent smooth progress of account binding; on the other hand, instructing the application server to generate a hidden account based on the system explicit account and the device identifier can ensure the uniqueness of the generated hidden account, thereby ensuring the accuracy of the rights data such as opening and querying from the application server based on the hidden account.

[0036] In some embodiments, after the processor executes to send a first rights transaction request to the application server or send a second rights transaction request to the application server, it is further configured to:

[0037] Receive the binding request sent by the terminal; wherein, the binding request carries the first explicit account and the third explicit account of the third-party application;

[0038] In response to a binding request, in the case where the first explicit account has been bound to the second explicit account, the third explicit account is used to replace the second explicit account in the explicit binding relationship between the first explicit account and the second explicit account; and,

[0039] Send a request for explicit and implicit binding change to the application server; wherein, the request for explicit and implicit binding change is used to instruct the application server to unbind the second explicit account from the implicit account and bind the third explicit account to the implicit account;

[0040] After receiving the successful binding change message fed back by the application server, send a second rights and interests transfer message to the application server; wherein, the second rights and interests transfer message is used to instruct the application server to stack the rights and interests data under the third explicit account with the rights and interests data of the implicit account.

[0041] In the above technical solution, compared with the related art where the rights and interests data of a third-party application purchased within the system application can only be bound to a single device or a single account, by using the above method, by binding the rights and interests data to the implicit account and binding the implicit account to different explicit accounts respectively, and then stacking the rights and interests data under the implicit account with the rights and interests data in different accounts respectively, the rights and interests data under the implicit account is no longer only able to be bound to a certain account singly, thus ensuring the full use of the rights and interests data.

[0042] In a second aspect, some embodiments further provide a mobile terminal, including:

[0043] A display and a controller;

[0044] The controller is configured to:

[0045] Scan the payment QR code for a third-party application presented by the system application in the display device to obtain the first explicit account and the current version information of the system application, the address information of the management server, and output a payment page; the system application is the application corresponding to the management server in the device terminal;

[0046] In response to a payment operation on the payment page, obtain rights and interests transaction information;

[0047] Based on the address information, send an initial rights and interests transaction request to the management server;

[0048] The initial rights and interests transaction request carries the rights and interests transaction information, the first explicit account and the current version information;

[0049] The initial rights and interests transaction request is used to request the management server to send a first rights and interests transaction request to the application server of a third-party application when an anonymous account bound to the first explicit account is queried; when the anonymous account is not queried, if the current version information indicates that the system application is an application after version downgrade, obtain the second explicit account of the third-party application bound to the first explicit account, and send a second rights and interests transaction request to the application server.

[0050] The first rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the anonymous account; the second rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the second explicit account.

[0051] The binding relationships among the anonymous account, the first explicit account, and the second explicit account are established before the system application undergoes version downgrade; the anonymous account is used to authenticate the access behavior initiated by the software development kit (SDK) of the third-party application in the system application, and the first explicit account cannot be directly authenticated by the application server.

[0052] In the above technical solution, the mobile terminal scans the payment QR code for the third-party application presented by the system application in the display device to obtain the first explicit account and the current version information of the system application, the address information of the management server, and outputs the payment page. Then, in response to the payment operation on the payment page, the rights and interests transaction information is obtained, and based on the address information, an initial rights and interests transaction request is sent to the management server. When the user purchases new rights and interests data, the account to which the purchased rights and interests data is to be superimposed can be selected based on the binding relationships among the first explicit account, the anonymous account, and the second explicit account, which can avoid the chaos of rights and interests data superimposition. Further, by binding the first explicit account, the anonymous account, and the second explicit account to each other, in the subsequent process of using rights and interests, whether the user logs in with the anonymous account or the second explicit account, the superimposed rights and interests data under the anonymous account and the second explicit account can continue to be used based on the account binding relationship, thus ensuring the maximization of the use of rights and interests data. In addition, in the scenario where the first explicit account is not bound to the anonymous account, by adopting a fallback strategy, that is, opening the rights and interests data to the second explicit account, the smooth progress of the user's rights and interests transaction is ensured.

[0053] Thirdly, some embodiments also provide an account processing method, which is applied to the management server and includes:

[0054] Receiving an initial rights and interests transaction request for a third-party application sent by the terminal; the initial rights and interests transaction request carries the rights and interests transaction information, as well as the first explicit account and the current version information of the system application; the system application is the application corresponding to the management server in the device terminal.

[0055] When the dark account bound to the first explicit account is queried, send a first rights and interests transaction request to the application server corresponding to the third-party application; the first rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the dark account.

[0056] When the dark account bound to the first explicit account is not queried, if the current version information indicates that the system application is an application after version downgrade, obtain the second explicit account of the third-party application bound to the first explicit account, and send a second rights and interests transaction request to the application server; the second rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the second explicit account.

[0057] Among them, the binding relationships between the dark account, the first explicit account, and the second explicit account are constructed before the system application undergoes version downgrade; the dark account is an account used to authenticate the access behavior initiated by the third-party application software development kit (SDK) in the system application, and the first explicit account cannot be directly authenticated by the application server.

[0058] In the above technical solution, by receiving the initial rights and interests transaction request sent by the terminal for the third-party application, which carries the rights and interests transaction information, the first explicit account of the system application, and the current version information, query the dark account bound to the first explicit account, and when the dark account bound to the first explicit account is queried, send a first rights and interests transaction request to the application server to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the dark account, and when the dark account bound to the first explicit account is not queried, if the current version information indicates that the system application is an application after version downgrade, obtain the second explicit account of the third-party application bound to the first explicit account, and send a second rights and interests transaction request to the application server to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the second explicit account. By adopting the above method, on the one hand, by binding the first explicit account, the dark account, and the second explicit account to each other, in the subsequent process of using rights and interests, whether the user logs in with the dark account or the second explicit account, they can continue to use the superimposed rights and interests data under the dark account and the second explicit account based on the account binding relationship, thus ensuring the maximization of the use of rights and interests data; on the other hand, when the user purchases new rights and interests data, the rights and interests data is preferentially superimposed under the dark account, which can avoid the confusion of rights and interests data superposition. In addition, in the scenario where the first explicit account is not bound to the dark account, by adopting a fallback strategy, that is, opening the rights and interests data to the second explicit account, the smooth progress of the user's rights and interests transaction is ensured.

[0059] Fourthly, some embodiments further provide an account processing method, which is applied to a mobile terminal and includes:

[0060] Scan the payment QR code for a third-party application presented by the system application in the display device to obtain the first plain account and the current version information of the system application, the address information of the management server, and output the payment page; the system application is the application corresponding to the management server in the device terminal;

[0061] In response to a payment operation on the payment page, obtain the rights and interests transaction information;

[0062] Based on the address information, send an initial rights and interests transaction request to the management server;

[0063] The initial rights and interests transaction request carries the rights and interests transaction information, the first plain account, and the current version information;

[0064] The initial rights and interests transaction request is used to request the management server to send a first rights and interests transaction request to the application server of the third-party application when an encrypted account bound to the first plain account is queried; when the encrypted account is not queried, if the current version information indicates that the system application is an application after version downgrade, obtain the second plain account of the third-party application bound to the first plain account, and send a second rights and interests transaction request to the application server;

[0065] The first rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the encrypted account; the second rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the second plain account;

[0066] The binding relationships among the encrypted account, the first plain account, and the second plain account are established before the system application undergoes version downgrade; the encrypted account is an account used to authenticate the access behavior initiated by the third-party application software development kit (SDK) in the system application by the application server, and the first plain account cannot be directly authenticated by the application server.

[0067] In the above technical solution, the mobile terminal scans the payment QR code for a third-party application presented by the system application in the display device to obtain the first clear account and the current version information of the system application, the address information of the management server, and outputs a payment page. Then, in response to a payment operation on the payment page, the mobile terminal obtains rights and interests transaction information and sends an initial rights and interests transaction request to the management server based on the address information. When the user purchases new rights and interests data, the account to which the purchased rights and interests data is to be superimposed can be selected based on the binding relationship among the first clear account, the dark account, and the second clear account, which can avoid the confusion of rights and interests data superposition. Further, by binding the first clear account, the dark account, and the second clear account to each other, in the subsequent process of using rights and interests, whether the user logs in with the dark account or the second clear account, the superimposed rights and interests data under the dark account and the second clear account can continue to be used based on the account binding relationship, thus ensuring the maximization of the use of rights and interests data. In addition, in the scenario where the first clear account is not bound to the dark account, by adopting a fallback strategy, that is, opening the rights and interests data to the second clear account, the smooth progress of the user's rights and interests transaction is ensured.

[0068] In a fifth aspect, some embodiments further provide an account processing device configured in the management server, including:

[0069] A request receiving module, configured to receive an initial rights and interests transaction request for a third-party application sent by the terminal; the initial rights and interests transaction request carries rights and interests transaction information, and the first clear account and the current version information of the system application; the system application is an application corresponding to the management server in the device end;

[0070] A first request sending module, configured to send a first rights and interests transaction request to the application server when a dark account bound to the first clear account is queried; the first rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the dark account;

[0071] A second request sending module, configured to, when a dark account bound to the first clear account is not queried, if the current version information indicates that the system application is an application after version downgrade, obtain the second clear account of the third-party application bound to the first clear account, and send a second rights and interests transaction request to the application server; the second rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the second clear account;

[0072] Wherein, the binding relationship among the dark account, the first clear account, and the second clear account is established before the system application undergoes version downgrade; the dark account is an account used to authenticate the access behavior initiated by the third-party application software development kit (SDK) in the system application by the application server, and the first clear account cannot be directly authenticated by the application server.

[0073] In a sixth aspect, some embodiments further provide an account processing device configured in a mobile terminal, including:

[0074] A scanning module, configured to scan a payment QR code for a third-party application presented by a system application in a display device, to obtain a first plain account number of the system application, current version information, address information of a management server, and output a payment page; the system application is an application corresponding to the management server in the device terminal;

[0075] An information acquisition module, configured to acquire rights and interests transaction information in response to a payment operation on the payment page;

[0076] A third request sending module, configured to send an initial rights and interests transaction request to the management server based on the address information;

[0077] The initial rights and interests transaction request carries the rights and interests transaction information, the first plain account number, and the current version information;

[0078] The initial rights and interests transaction request is used to request the management server to send a first rights and interests transaction request to the application server of the third-party application when a dark account bound to the first plain account number is queried; when the dark account is not queried, if the current version information indicates that the system application is an application after version downgrade, obtain a second plain account number of the third-party application bound to the first plain account number, and send a second rights and interests transaction request to the application server;

[0079] The first rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the dark account; the second rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the second plain account number;

[0080] The binding relationships among the dark account, the first plain account number, and the second plain account number are established before the system application undergoes version downgrade; the dark account is an account used to authenticate access behaviors initiated by a third-party application software development kit (SDK) in the system application by the application server, and the first plain account number cannot be directly authenticated by the application server.

[0081] In a seventh aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program, which, when run by the account processing device, causes the account processing device to execute any one of the account processing methods in the first aspect or the second aspect.

[0082] In an eighth aspect, there is provided a computer program product, which includes a computer program that, when run on an account processing device, causes the account processing device to execute any one of the account processing methods in the first aspect or the second aspect. Description of the Drawings

[0083] To more clearly illustrate the technical solutions in the embodiments of the present application or the related art, the following will briefly introduce the drawings required for the description of the embodiments of the present application or the related art. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other related drawings can be obtained based on these drawings without creative efforts.

[0084] Figure 1 Schematic diagram of an operation scenario between a display device and a control device provided in some embodiments of the present application;

[0085] Figure 2 Schematic diagram of the hardware configuration of a display device provided in some embodiments of the present application;

[0086] Figure 3 Schematic diagram of the hardware configuration of a control device provided in some embodiments of the present application;

[0087] Figure 4 Schematic diagram of the software configuration of a display device provided in some embodiments of the present application;

[0088] Figure 5 Schematic diagram of the process of an account processing method provided in some embodiments of the present application;

[0089] Figure 6 Schematic diagram of the process of updating entitlement data provided in some embodiments of the present application;

[0090] Figure 7 Schematic diagram of the process of obtaining entitlement data provided in some embodiments of the present application;

[0091] Figure 8 Schematic diagram of the process of an account binding process provided in some embodiments of the present application;

[0092] Figure 9 Schematic diagram of the process of obtaining a hidden account provided in some embodiments of the present application;

[0093] Figure 10 Schematic diagram of the process of changing the bound account provided in some embodiments of the present application;

[0094] Figure 11 Schematic diagram of the process of an account processing method provided in some other embodiments of the present application;

[0095] Figure 12 A schematic diagram of account processing among devices in the account processing process provided by other embodiments of the present application;

[0096] Figure 13 A schematic diagram of account processing among devices in the account processing process provided by other embodiments of the present application;

[0097] Figure 14 A structural block diagram of an account processing device in some embodiments;

[0098] Figure 15 A structural block diagram of an account processing device in other embodiments;

[0099] Figure 16 An internal structure diagram of a computer device in one embodiment. Detailed implementation manners

[0100] The embodiments will be described in detail below, and the examples are shown in the accompanying drawings. When the following description refers to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementation manners described in the following embodiments do not represent all implementation manners consistent with the present application. They are merely examples of systems and methods consistent with some aspects of the present application detailed in the claims.

[0101] It should be noted that the brief description of the terms in the present application is only for facilitating the understanding of the following described implementation manners, rather than intending to limit the implementation manners of the present application. Unless otherwise specified, these terms should be understood in their ordinary and common meanings.

[0102] The terms "first", "second", "third", etc. in the specification, claims and the above-mentioned drawings of the present application are used to distinguish similar or like objects or entities, and do not necessarily mean to limit a specific order or sequence, unless otherwise noted. It should be understood that such terms can be interchanged under appropriate circumstances.

[0103] The terms "comprising" and "having" and any variations thereof are intended to cover but not be exclusive of inclusion. For example, a product or device comprising a series of components does not necessarily have to be limited to all the components clearly listed, but may include other components not clearly listed or inherent to these products or devices.

[0104] The term "module" refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic or a combination of hardware or / and software code that can perform functions related to the element.

[0105] In some embodiments, the management server may be a server 400 with account management capabilities. It can be an independent server or a server cluster. The display device 200 generally refers to a device with screen display and data processing capabilities. For example, the display device 200 includes, but is not limited to, smart TVs, mobile terminals, computers, monitors, advertising screens, wearable devices, virtual reality devices, augmented reality devices, etc.

[0106] Figure 1 Schematic diagram of the operation scenario between the display device and the control device provided by some embodiments of the present application. As Figure 1 shown, the user can operate the display device 200 through touch operations, the mobile terminal 300, and the control device 100. For example, the control device 100 can be a remote control, a stylus, a gamepad, etc.

[0107] The mobile terminal 300 can be used as a control device to perform human-computer interaction between the user and the display device 200. The mobile terminal 300 can also be used as a communication device to establish a communication connection with the display device 200 for data interaction. In some embodiments, software applications can be installed on the mobile terminal 300 and the display device 200, and connection communication can be achieved through network communication protocols to achieve the purpose of one-to-one control operations and data communication. It is also possible to transmit the audio and video content displayed on the mobile terminal 300 to the display device 200 to achieve the synchronous display function.

[0108] As Figure 1 also shown, the display device 200 also communicates with the server 400 through various communication methods. The display device 200 is allowed to communicate and connect through a local area network (LAN), a wireless local area network (WLAN), and other networks.

[0109] The display device 200 can provide a broadcast reception television function, and can also additionally provide an intelligent network television function with computer support functions, including but not limited to, network television, smart television, Internet Protocol Television (IPTV), etc.

[0110] Figure 2 Provided by some embodiments of the present application Figure 1 Hardware configuration block diagram of the display device 200 in

[0111] In some embodiments, the display device 200 may include at least one of a tuner demodulator 210, a communication device 220, a detector 230, a device interface 240, a controller 250, a display 260, an audio output device 270, a memory, a power supply, and a user input interface.

[0112] In some embodiments, the detector 230 is used to collect signals of the external environment or for external interactions. For example, the detector 230 includes a light receiver, a sensor for collecting the intensity of ambient light; or, the detector 230 includes an image collector, such as a camera, which can be used to collect external environmental scenes, user attributes, or user interaction gestures. Or, the detector 230 includes a sound collector, such as a microphone, etc., for receiving external sounds.

[0113] In some embodiments, the display 260 includes a display function component for presenting a picture and a driving component for driving image display. The display 260 is used to receive the image signal output from the controller 250 for display. For example, the display 260 can be used to display video content, image content, components of a menu manipulation interface, and a user manipulation UI interface, etc.

[0114] In some embodiments, the communication device 220 is a component for communicating with external devices or the server 400 according to various communication protocol types. The display device 200 can be provided with a plurality of communication devices 220 according to different supported communication methods. For example, when the display device 200 supports wireless network communication, the display device 200 can be provided with a communication device 220 including the function of the international wireless local area network standard (Wireless Fidelity, WiFi). When the display device 200 supports Bluetooth connection communication, the display device 200 needs to be provided with a communication device 220 including Bluetooth function.

[0115] The communication device 220 can enable the display device 200 to communicate with external devices or the server 400 in a wireless or wired connection manner. Among them, the wired connection can connect the display device 200 with an external device through components such as a data cable and an interface. The wireless connection can connect the display device 200 with an external device through a wireless signal or a wireless network. The display device 200 can directly establish a connection relationship with an external device, or can indirectly establish a connection relationship through a gateway, a router, a connection device, etc.

[0116] In some embodiments, the controller 250 can include at least one of a central processing unit, a video processor, an audio processor, a graphics processor, and a power processor, and first interfaces to n interfaces for input / output. The controller 250 controls the operation of the display device and responds to user operations through various software control programs stored in the memory. The controller 250 controls the overall operation of the display device 200.

[0117] In some embodiments, the controller 250 and the tuner-demodulator 210 may be located in different split devices, that is, the tuner-demodulator 210 may also be in an external device of the main device where the controller 250 is located, such as an external set-top box, etc.

[0118] In some embodiments, the user may input a user command through the graphical user interface (GUI) displayed on the display 260, and then the user input interface receives the user input command through the graphical user interface (GUI).

[0119] In some embodiments, the audio output device 270 may be the built-in speaker of the display device 200, or may be an external audio output device connected to the display device 200. Among them, for the external audio output device connected to the display device 200, the display device 200 may also be provided with an external audio output terminal, and the audio output device may be connected to the display device 200 through the external audio output terminal to output the sound of the display device 200.

[0120] In some embodiments, the user input interface 280 can be used to receive instructions from the user input.

[0121] Figure 3 The hardware configuration block diagram of the control device provided in some embodiments of the present application. As Figure 1 shown, the control device 100 may include: a controller 110, a communication interface 130, a user input / output interface, a memory, and a power supply. Figure 3 The control device 100 is configured to control the display device 200, and can receive the input operation instructions of the user, and convert the operation instructions into instructions recognizable and responsive by the display device 200, playing the role of an interaction intermediary between the user and the display device 200.

[0122] In some embodiments, the control device 100 may be an intelligent device. For example: the control device 100 can install various applications for controlling the display device 200 according to user needs.

[0123] In some embodiments, as

[0124] shown, after installing the application for controlling the display device 200, the mobile terminal 300 or other intelligent electronic devices can play a similar function to the control device 100. Figure 1 The controller 110 includes a processor 112, a RAM 113, a ROM 114, a communication interface 130, and a communication bus. The controller 110 is used to control the operation and operation of the control device 100, as well as the communication and cooperation between internal components and the data processing functions inside and outside.

[0125] ​

[0126] Under the control of the controller 110, the communication interface 130 enables the communication of control signals and data signals with the display device 200. The communication interface 130 may include at least one of other near-field communication modules such as a WiFi chip 131, a Bluetooth module 132, an NFC module 133, etc.

[0127] The user input / output interface 140, where the input interface includes at least one of a microphone 141, a touchpad 142, a sensor 143, a button 144, and other input interfaces.

[0128] In some embodiments, the control device 100 includes at least one of the communication interface 130 and the input / output interface 140. The communication interface 130 configured in the control device 100, such as modules like Wi-Fi, Bluetooth, NFC, etc., can encode user input instructions through the Wi-Fi protocol, or the Bluetooth protocol, or the NFC protocol and send them to the display device 200.

[0129] The memory 190 is used to store various operating programs, data, and applications for driving and controlling the control device 100 under the control of the controller. The memory 190 can store various control signal instructions input by the user.

[0130] The power supply 180 is used to provide operating power support for each component of the control device 100 under the control of the controller.

[0131] In order to perform user interaction, in some embodiments, the display device 200 may run an operating system. The operating system is a computer program for managing and controlling the hardware resources and software resources in the display device 200. The operating system can (control the display device) provide a user interface, allow users to interact with the display device 200, and support the running of various application programs.

[0132] It should be noted that the operating system can be a native operating system based on a specific operating platform, or a third-party operating system deeply customized based on a specific operating platform, or an independent operating system specially developed for the display device.

[0133] The operating system can be divided into different modules or layers according to the functions implemented. For example, as Figure 4 shown, in some embodiments, the system is divided into four layers, from top to bottom, namely the application layer (abbreviated as the "application layer"), the application framework layer (abbreviated as the "framework layer"), the system library layer, and the kernel layer.

[0134] In some embodiments, the application layer is used to provide services and interfaces for applications so that the display device 200 can run the applications and interact with users based on the applications. At least one application can run in the application layer. These applications can be window programs, system setting programs, or clock programs, etc. that come with the operating system; they can also be applications developed by third-party developers. In specific implementations, the application packages in the application layer are not limited to the above examples.

[0135] The framework layer provides application programming interfaces (APIs) and programming frameworks for applications. The application framework layer includes some predefined functions. The application framework layer is equivalent to a processing center that decides what actions the applications in the application layer should take. Through the API interfaces, applications can access the resources in the system and obtain the services of the system during execution.

[0136] As Figure 4 shown, in the embodiment of the present application, the application framework layer includes a view system, managers, content providers, etc. Among them, the view system can design and implement the interfaces and interactions of applications. The view system includes lists, grids, text boxes, buttons, etc. The managers include at least one of the following modules: The activity manager is used to interact with all the activities running in the system; the location manager is used to provide access to the system location service for system services or applications; the package manager is used to retrieve various information related to the application packages currently installed on the device; the notification manager is used to control the display and clearing of notification messages; the window manager is used to manage the icons, windows, toolbars, wallpapers, and desktop widgets on the user interface.

[0137] In some embodiments, the activity manager is used to manage the life cycles of various applications and the general navigation back function, such as controlling the exit, opening, and backward movement of applications. The window manager is used to manage all window programs, such as obtaining the size of the display screen, determining whether there is a status bar, locking the screen, taking screenshots, and controlling the changes of the display window. For example, shrinking the display window, jittering the display, or distorting the display.

[0138] In some embodiments, the system runtime library layer can provide support for the framework layer. When the framework layer is used, the operating system will run the instruction libraries included in the system runtime library layer, such as C / C++ instruction libraries, to implement the functions that the framework layer is intended to achieve.

[0139] In some embodiments, the kernel layer is a functional level between the hardware and software of the display device 200. The kernel layer can implement functions such as hardware abstraction, multitasking, and memory management. For example, as Figure 4 shown, hardware drivers can be configured in the kernel layer, and the drivers included in the kernel layer can be at least one of the following drivers: audio driver, display driver, Bluetooth driver, camera driver, WIFI driver, USB driver, HDMI driver, sensor drivers (such as fingerprint sensors, temperature sensors, pressure sensors, etc.), and power drivers, etc.

[0140] It should be noted that the above examples are only a simple division of the functions of the operating system, and do not limit the specific form of the operating system of the display device 200 in the embodiments of the present application. Depending on factors such as the functions of the display device and the type of operating system, the number of levels and the specific level types included in the operating system can be in other forms.

[0141] With the development of devices and the diverse needs of users for information, more and more third-party application SDKs can be integrated into applications, such as in the system applications of smart TVs. Exemplarily, a smart TV can integrate system applications and third-party application SDKs. The system application is a host application deployed on the terminal, that is, it can access third-party applications by calling third-party application SDKs.

[0142] Furthermore, to ensure the convenience of user operations, after the user has logged in to the system application with a first explicit account, in the case where the system application is a high-version application, a dark account can be generated for the user without the user's awareness and used for logging in. After that, the entitlement data purchased by the user will be directly bound to the user's dark account. Among them, when the user calls a third-party application SDK to access a third-party application, the dark account needs to be carried so that the application server corresponding to the third-party application can authenticate the access behavior of the third-party application SDK accessing the third-party application based on the dark account.

[0143] However, after the system application is downgraded, it is no longer possible to access third-party applications using the dark account, which will cause the entitlement data in the dark account to be unusable, making the user entitlement data not fully utilized.

[0144] Based on this, in some embodiments, an account processing method is provided. Among them, the account processing method can be implemented in cooperation with a management server, a mobile terminal, a display device, etc.

[0145] In an alternative embodiment, taking the account processing method applied to a processor in a management server as an example, the management server includes a communication device and at least one processor; the communication device is communicatively connected to a terminal and an application server corresponding to a third-party application, which can be a wired communication connection or a wireless communication connection, and the processor is connected to the communication device.

[0146] As Figure 5 shown, it specifically includes the following steps:

[0147] S510, receiving an initial rights and interests transaction request for a third-party application sent by a terminal.

[0148] Among them, the initial rights and interests transaction request carries rights and interests transaction information, as well as a first clear account number and current version information of the system application, which are used to instruct the management server to conduct rights and interests transaction matters for the user for the third-party application. The so-called rights and interests transaction information is the information of the rights and interests transaction for the third-party application, which can include the rights and interests transaction time, rights and interests transaction details (such as the quantity of rights and interests purchased, payment information), etc. The current version information is the version information of the system application at the current moment, which can be represented by a version identifier. The first clear account number is the account number registered by the user to log in to the system application. Among them, the rights and interests can be the VIP membership rights and interests of the user in the third-party application; the rights and interests data can include the usage period of the VIP membership rights and interests, such as the expiration date, etc.

[0149] The system application is the application corresponding to the device side in the management server. Optionally, the device side can be a device integrated with the system application, such as a display device, such as a smart TV; further, the third-party application can be integrated in the terminal, and the terminal can be the same as or different from the device side.

[0150] Optionally, after the user logs in to the system application with the first clear account number, in the case where the device side detects that the user has an operation of purchasing rights and interests data for the third-party application, an initial rights and interests transaction request for the third-party application can be initiated directly or indirectly. Among them, the operation of the user purchasing rights and interests data for the third-party application can be to trigger the rights and interests purchase control of the third-party application in the device side. For example, trigger the rights and interests purchase identifier in the page of the third-party application displayed by the display device 200.

[0151] In practical applications, the terminal and the device side can be different devices. For example, the terminal is a mobile terminal 300 and the device side is a display device 200. Or, the terminal and the device side can also be the same device. For example, the terminal and the device side are the same display device 200. It should be noted that under different device combinations, the method of initiating the initial rights and interests transaction request is different, and thus the method for the management server to obtain the initial rights and interests transaction request is also different.

[0152] In an alternative embodiment, when the terminal is a mobile terminal and the device side is a display device, the first plain account number and the current version information are obtained by the mobile terminal scanning the payment QR code presented in the system application.

[0153] In some embodiments, when the terminal is a mobile terminal 300 and the device side is a display device 200, in order to obtain an initial rights and interests transaction request, the display device 200 will display a payment QR code for a third-party application to the user. Among them, the payment QR code may include the first plain account number and the current version information of the system application. The user can first use the payment application integrated in the mobile terminal 300 to scan the payment QR code. At this time, the mobile terminal 300 can obtain the first plain account number and the current version information of the system application, and generate a payment interface based on the rights and interests purchase situation.

[0154] Further, after detecting that the user clicks the payment control in the payment interface, the mobile terminal 300 can send an initial rights and interests transaction request carrying the rights and interests transaction information, as well as the first plain account number and the current version information of the system application, to the management server. Then, the management server can obtain the initial rights and interests transaction request initiated by the mobile terminal 300.

[0155] In another alternative embodiment, when the terminal and the device side are the same display device, the first plain account number is obtained by the display device according to the login operation of the system application.

[0156] In some embodiments, after the display device 200 directly displays a login input interface for the system application to the user, the management server can obtain the first plain account number by obtaining the login information input by the user in the login input interface, and store the first plain account number locally.

[0157] Further, when the user has a need to purchase rights and interests, the display device 200 can display a rights and interests purchase interface for a third-party application to the user. The user can input the rights and interests information to be purchased in the rights and interests purchase interface and trigger the purchase control in the rights and interests purchase interface. At this time, the display device 200 can obtain the first plain account number and the current version information of the system application from the local storage, and send an initial rights and interests transaction request carrying the rights and interests transaction information, as well as the first plain account number and the current version information of the system application, to the management server. Then, the management server can obtain the initial rights and interests transaction request initiated by the mobile terminal 300.

[0158] Optionally, after the management server obtains the initial rights and interests transaction request sent by the terminal, it can extract the first plain account number from the initial rights and interests transaction request, and query locally whether there is a dark binding relationship, that is, the binding relationship between the first plain account number and the dark account plain account number. If it exists, execute S520; if it does not exist, execute S530.

[0159] S520, in the case of querying the dark account bound to the first plain account number, send a first rights and interests transaction request to the application server.

[0160] Among them, the first rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information with the rights and interests data under the dark account. The binding relationships between the dark account, the first plain account number, and the second plain account number are constructed before the version downgrade of the system application. The binding relationships between the dark account, the first plain account number, and the second plain account number may include the plain binding relationship between the first plain account number and the second plain account number, the dark binding relationship between the first plain account number and the dark account, and the plain and dark binding relationship between the dark account and the second plain account number.

[0161] The dark account is an account used to authenticate the access behavior initiated by the third-party application software development kit (SDK) in the system application by the application server, and the first plain account number cannot be directly authenticated by the application server. The second plain account number is the account registered by the user to log in to the third-party application.

[0162] In some embodiments, since the management server is the server corresponding to the system application, the historical behavior data of the user will be managed with the first plain account number. In the system service, in addition to the functions corresponding to the third-party SDK, there are many other functions, such as the video service function and the fitness service function different from the third-party application in the system application. Therefore, a lot of historical behavior data of the user will be generated. However, considering that the authentication of the content of the third-party SDK must be carried out through the third-party server, the management server sets the logic of the dark account for rights and interests authentication on the third-party server in order to isolate the user's historical behavior and user rights and interests. That is, the user can view the historical behavior data and rights and interests data of the user on the management server through the first plain account number. However, when performing rights and interests authentication, it is necessary to request authentication from the third-party server through the dark account.

[0163] In some embodiments, the management server is the server corresponding to the system application. The first plain account can be modified and configured by the user, but the authentication of the third-party SDK content must be performed through the third-party server. To reduce the frequent changes between the management server and the application server, the logic for authenticating rights and interests through the dark account on the third-party server is set. That is, the user can modify the first plain account of the system application, and the management server updates the binding relationship between the first plain account and the dark account. When performing rights and interests authentication, it is necessary to request authentication from the third-party server through the dark account.

[0164] In practical applications, to ensure the maximum utilization of rights and interests, after logging in to the third-party application with the dark account, the user can also bind the second plain account to the dark account to superimpose the rights and interests data under the dark account and the rights and interests data under the second plain account. At this time, the rights and interests data in the dark account and the second plain account are the same.

[0165] Optionally, if the dark account bound to the first plain account is queried based on the first plain account, it proves that the corresponding dark account has been configured for the first plain account. In this case, the rights and interests data to be purchased can be directly superimposed under the dark account. Therefore, a first rights and interests transaction request carrying the rights and interests transaction information and the dark account can be sent to the application server, and the application server superimposes the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the dark account.

[0166] It should be noted that in the case where the system application is an application after version downgrade, if the dark account bound to the first plain account can be queried, it proves that the current scenario is that the user has a dark account, but due to version downgrade, the dark account cannot be used to access the third-party application, and the user can only log in with the second plain account. Among them, the management server stores the binding relationships between the dark account, the first plain account, and the second plain account, and the rights and interests data under the second plain account have been superimposed on the rights and interests data under the dark account.

[0167] Furthermore, to avoid confusion in rights and interests superimposition, the purchased rights and interests can be uniformly superimposed under the dark account, that is, still send a first rights and interests transaction request carrying the rights and interests transaction information and the dark account to the application server, and the application server superimposes the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the dark account. At this time, when logging in with the second plain account, the user can still use the rights and interests data under the dark account based on the account binding relationship.

[0168] S530, in the case where the dark account bound to the first plain account is not queried, if the current version information indicates that the system application is an application after version downgrade, obtain the second plain account of the third-party application bound to the first plain account, and send a second rights and interests transaction request to the application server.

[0169] Among them, the second rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the second explicit account. Version downgrade means that the version of the system application is lowered from a higher version to a lower version. In practical applications, operations such as the device restoring to factory settings will cause the version of the system application to be downgraded.

[0170] Optionally, in the case where the hidden account bound to the first explicit account is not queried, it can be determined whether the system application has the function of actively creating a hidden account for the user based on the current version information. If the current version information indicates that the system application is a high-version application, that is, the system application has the function of actively creating a hidden account for the user, a hidden account generation request carrying the first explicit account and the device identifier can be sent to the application management server of the third-party application to generate a hidden account. After the management server obtains the hidden account, a first rights and interests transaction request carrying the rights and interests transaction information and the hidden account can be sent to the application server, and the application server superimposes the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the hidden account.

[0171] If the current version information indicates that the system application is an application after version downgrade, the second explicit account of the third-party application bound to the first explicit account can be obtained based on the explicit binding relationship associated with the first explicit account, and a second rights and interests transaction request carrying the rights and interests transaction information and the second explicit account can be sent to the application server, and the application server superimposes the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the second explicit account.

[0172] In some embodiments, the management server can determine whether the system application is a high-version application by identifying whether the version identifier corresponding to the current version information is a high-version identifier. For example, if it is identified that the version identifier is a high-version identifier, it is determined that the system application is a high-version application; if it is identified that the version identifier is a low-version identifier, it is determined that the system application is a low-version application. Optionally, the management server can locally record the application situations of different version identifiers of the system application, that is, whether the system application corresponding to different version identifiers is a high-version application or a low-version application.

[0173] In the above technical solution, by receiving an initial rights and interests transaction request sent by a receiving terminal for a third-party application, which carries rights and interests transaction information, as well as the first clear account number and the current version information of the system application, querying the hidden account bound to the first clear account number, and in the case where the hidden account bound to the first clear account number is queried, sending a first rights and interests transaction request to the application server to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the hidden account, and in the case where the hidden account bound to the first clear account number is not queried, if the current version information indicates that the system application is an application after version downgrade, obtaining the second clear account number of the third-party application bound to the first clear account number, and sending a second rights and interests transaction request to the application server to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the second clear account number. By adopting the above method, on the one hand, by binding the first clear account number, the hidden account number and the second clear account number to each other, in the subsequent process of using rights and interests, whether the user logs in with the hidden account number or the second clear account number, the user can continue to use the superimposed rights and interests data under the hidden account number and the second clear account number based on the account binding relationship, so that the user's rights and interests data is fully utilized, that is, the maximization of the use of rights and interests data is ensured; on the other hand, when the user purchases new rights and interests data, preferentially superimposing the rights and interests data under the hidden account number can avoid the chaos of superimposing rights and interests data. In addition, in the scenario where the first clear account number is not bound to the hidden account number, by adopting a fallback strategy, that is, opening the rights and interests data to the second clear account number, the smooth progress of the user's rights and interests transaction is ensured.

[0174] Based on the above embodiments, after sending the first rights and interests transaction request to the application server or sending the second rights and interests transaction request to the application server, in some embodiments, an optional method for updating rights and interests data is provided, such as Figure 6 shown, which specifically includes the following steps:

[0175] S610, receive new rights and interests data.

[0176] Among them, after sending the first rights and interests transaction request to the application server, the new rights and interests data is the rights and interests data obtained by superimposing the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the hidden account; after sending the second rights and interests transaction request to the application server, the new rights and interests data is the rights and interests data obtained by superimposing the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the second clear account number.

[0177] Optionally, after the application server superimposes the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the hidden account / second clear account number, the new rights and interests data can be obtained. At this time, the application server can feedback the new rights and interests data, as well as the hidden account / second clear account number, to the management server.

[0178] S620 updates the entitlement data associated with the first explicit account using the new entitlement data.

[0179] Optionally, the management server may first locate the first explicit account associated with the dark account / second explicit account based on the dark account / second explicit account; then update the entitlement data associated with the located first explicit account based on the new entitlement data.

[0180] It should be noted that, in order to prevent a user from invoking the third-party application SDK to use the entitlement functions in the third-party application when the entitlement data is insufficient, an entitlement display page may be presented on the display of the device terminal. Among them, the entitlement display page may include the entitlement data associated with the first explicit account.

[0181] Furthermore, after the management server updates the entitlement data associated with the first explicit account based on the new entitlement data, in order to ensure that the device terminal dynamically updates the entitlement data, an entitlement update prompt may be sent to the device terminal to instruct the device terminal to send an entitlement query request carrying the first explicit account to the management server. At this time, the management server may use the first explicit account as index information to query in the locally stored entitlement data, so as to obtain the new entitlement data associated with the first explicit account, and feedback the obtained new entitlement data to the device terminal. Thus, the new entitlement data can be presented in the device terminal.

[0182] In the above technical solution, by associating the first explicit account with the entitlement data locally in the management server and dynamically updating based on the new entitlement data sent by the application server, on the one hand, by dynamically updating the entitlement data, the accuracy of the entitlement data stored locally in the management server can be ensured; on the other hand, in the case where it is necessary to display the entitlement data to the user or the user has a need to obtain the entitlement data, compared with obtaining the entitlement data from the application server in real time, the response rate is faster by obtaining the entitlement data from the local of the management server.

[0183] To improve the response rate of obtaining entitlement data, the entitlement data can be stored locally. In some embodiments, an optional way to obtain entitlement data is provided, as Figure 7 shown, including the following steps:

[0184] S710, in response to an entitlement query request carrying the first explicit account sent by the device terminal, based on the first explicit account, obtain the entitlement data associated with the first explicit account from the locally stored entitlement data.

[0185] Among them, the entitlement query request is used to query the overall entitlement data of the user under the third-party application.

[0186] Optionally, the management server may send a rights query request to the application server in advance to obtain the rights data associated with the dark account / second clear account, and store the obtained rights data in association with the first clear account.

[0187] In an alternative embodiment, when it is detected that the user has a rights data query event for a third-party application, a rights query request carrying the first clear account may be sent to the management server through the device side. After receiving the rights query request, the management server may use the first clear account as index information to query among the candidate first clear accounts stored in the management server and the corresponding rights data, so as to obtain the rights data associated with the first clear account.

[0188] Exemplarily, the rights data query event may be that the user triggers a rights function displayed in the third-party application SDK on the device side, where the rights function can be used only when the user account contains rights data. For example, the user triggers the function of playing member music in the music application SDK. At this time, it is required that the expiration time of the music VIP rights under the user account is greater than the current date. Or, the rights data query event may also be that the user triggers a rights data query control corresponding to the third-party application on the device side. For example, the user clicks the query control corresponding to the expiration time of the music VIP rights of the music application in the system application, etc.

[0189] In another alternative embodiment, the device side may also actively update the rights data to be displayed. Exemplarily, the device side may send a rights query request carrying the first clear account to the management server based on a preset polling interval to obtain the rights data associated with the first clear account. For example, when the rights data is the expiration time of the music VIP rights, the polling interval may be 24 hours, that is, the device side will send a rights query request to the management server every 24 hours to obtain the expiration time of the music VIP rights associated with the first clear account.

[0190] S720, feedback the obtained rights data to the device side.

[0191] Optionally, after obtaining the rights data associated with the first clear account, the obtained rights data may be fed back to the device side. After the device side receives the rights data, it can be displayed in the associated display page.

[0192] In the above technical solution, on the one hand, by associating and storing the first clear account with the rights and interests data locally on the management server, compared with accessing the application server to obtain the rights and interests data, obtaining the rights and interests directly from the management server has a faster response rate; on the other hand, by interacting with the device side to feedback the rights and interests data to the device side, so that the device side can display the rights and interests data in real time, enabling the user to intuitively understand the rights and interests situation under the third-party application.

[0193] Based on the above embodiments, in some embodiments, the binding process of the second clear account and the dark account is refined, such as Figure 8 shown, and specifically includes the following steps:

[0194] S810, receive the binding indication information sent by the terminal.

[0195] Among them, the binding indication information carries the first clear account and the second clear account. Further, there may be a record of logging in to the third-party application using the second clear account in the device side.

[0196] Optionally, after the user logs in to the system application using the first clear account, when the device side detects that the user has an access action of calling the third-party application SDK to access the third-party application, it will send a binding query request containing the first clear account to the management server. In some embodiments, the device side can detect whether the user has an access action based on the distance between the focus position on the display page and the icon corresponding to the third-party application SDK. For example, when the focus position on the display page is located on the icon corresponding to the third-party application SDK, it is determined that the user has an access action. It should be noted that in order to save the loading time of the SDK, when the distance between the focus position on the display page and the icon corresponding to the third-party application SDK is less than the distance threshold, the third-party application SDK can be pre-loaded for the user to call.

[0197] Further, if there is no light-dark binding relationship between the second clear account and the dark account in the management server, an operation of binding the second clear account and the dark account associated with the first clear account needs to be performed. Before performing the binding operation of the second clear account and the dark account, it is necessary to ensure that the management server stores the light binding relationship between the first clear account and the second clear account, and the dark binding relationship between the first clear account and the dark account. If the management server does not store the second clear account bound to the first clear account, the second clear account of the user needs to be obtained.

[0198] In practical applications, the terminal and the device end can be different devices. For example, the terminal is a mobile terminal 300 and the device end is a display device 200. Alternatively, the terminal and the device end can also be the same device. For example, the terminal and the device end are the same display device 200. It should be noted that under different device combinations, the method for obtaining the second clear account is also different.

[0199] In an alternative implementation, when the terminal is a mobile terminal 300 and the device end is a display device 200, in order to obtain the second clear account of the user in a third-party application, the display device 200 will display a login QR code for the third-party application to the user. Among them, the login QR code can include the user's first clear account information and the address information of the management server. The user can first log in to the third-party application integrated in the mobile terminal 300 using the second clear account, and then use the scanning device in the third-party application in the mobile terminal 300 to scan the login QR code. At this time, a login interface will be generated in the third-party application in the mobile terminal 300 based on the second clear account. After the user clicks the login control in the login interface, the binding indication information carrying the first clear account and the second clear account can be sent to the management server.

[0200] In another alternative implementation, when the terminal and the device end are the same display device, after the display device 200 displays a login input interface for a third-party application to the user, the user can enter the second clear account and the account password corresponding to the second clear account in the login input interface, and trigger the login control in the login input interface to send the obtained second clear account and the account password corresponding to the second clear account to the application server for login verification. After the application server verifies the login operation of the second clear account and passes, it can feedback a verification passed message to the display device 200. At this time, the display device 200 can obtain the second clear account; then the display device 200 can send the binding indication information carrying the first clear account and the second clear account to the management server.

[0201] Optionally, the binding indication information is used to instruct the management server to perform account binding processing. After the management server obtains the binding indication information sent by the terminal, it can extract the first clear account and the second clear account from the binding indication information, and query whether there is a clear binding relationship locally based on the first clear account, that is, the binding relationship between the first clear account and the second clear account. If not, the first clear account and the second clear account can be bound first; if it exists, the subsequent binding logic between the second clear account and the dark account can be directly executed, that is, continue to execute S820 and S830.

[0202] S820, obtain the dark account bound to the first clear account, and send a light-dark binding request to the application server.

[0203] Among them, the light-dark binding request is used to request the application server to perform light-dark binding on the second light account and the dark account.

[0204] Optionally, the first light account can be obtained from the binding indication information, and the first light account can be used as index information to query in the binding relationships between each candidate first light account and each candidate dark account stored in the management server. If the query result shows that there is a dark account bound to the first light account, the dark account is obtained, and a light-dark binding request is generated based on the dark account and the second light account, and the light-dark binding request is sent to the application server corresponding to the third-party application.

[0205] If the query result shows that there is no dark account bound to the first light account, a dark account generation request needs to be sent to the application server corresponding to the third-party application first, and the application server generates a dark account and feeds it back; after the management server obtains the dark account, the first light account and the dark account can be bound first, and the dark account is obtained from the binding relationship, and then a light-dark binding request is generated based on the dark account and the second light account, and the light-dark binding request is sent to the application server corresponding to the third-party application.

[0206] S830, after receiving the binding success message fed back by the application server, send a first rights transfer message to the application server.

[0207] Among them, the binding success message is the message fed back by the application server to the management server when the dark account and the second light account are successfully bound; the first rights transfer message is used to instruct the application server to superimpose the rights data under the second light account and the rights data under the dark account, and store the rights superposition record.

[0208] Optionally, after receiving the binding success message fed back by the application server, a rights transfer message including the dark account and the second light account can be sent to the application server. The application server uses the dark account and the second light account in the rights transfer message as index information respectively to query in the stored rights data, so as to obtain the rights data under the dark account and the rights data under the second light account; then, the rights data under the second light account and the rights data under the dark account are superimposed, and a rights superposition record is generated based on the superposition process and stored. Thus, the rights data under the second light account and the rights data under the dark account of the user are consistent.

[0209] It should be noted that the binding between the above-mentioned dark account and the second explicit account does not mean merging the dark account with the second explicit account. That is, the dark account and the second explicit account remain independent accounts, but only the entitlement data between the dark account and the second explicit account can be superimposed. Therefore, the second explicit account after the light-dark binding can still be used to log in to third-party applications. Correspondingly, the superimposition between the entitlement data under the second explicit account and the entitlement data under the dark account is reversible, that is, the above-mentioned superimposition process can be revoked based on user needs subsequently.

[0210] In the above technical solution, by performing light-dark binding on the dark account bound to the second explicit account and the first explicit account, and after the light-dark binding is successful, superimposing the entitlement data under the second explicit account and the entitlement data under the dark account, it can ensure that the entitlement data of the same user under different accounts is no longer scattered, thereby maximizing the use of user entitlements. Further, since the second explicit account and the dark account are bound, the entitlement data under the second explicit account and the entitlement data under the dark account are the same, that is, the entitlement data is the same whether the user accesses the third-party application based on the second explicit account or the dark account subsequently, realizing the sharing of entitlement data of the user under the second explicit account and the dark account.

[0211] Based on the above embodiments, in some embodiments, the process of obtaining the dark account is further refined, such as Figure 9 shown, and specifically includes the following steps:

[0212] S910, in the case where no corresponding dark binding relationship is found based on the first explicit account, send a dark account generation request to the application server.

[0213] Among them, the dark account generation request carries the first explicit account and the device identifier of the device end, and is used to instruct the application server to generate a dark account. The device identifier is used to represent the basic attribute information of the device end, and may include, but is not limited to, information such as the model, specification, and batch of the device end.

[0214] Optionally, in the case where the initialization of the third-party application SDK is detected, it is necessary to register a dark account for the user for the third-party application SDK. At this time, the device identifier of the device end can be obtained, and a dark account generation request carrying the first explicit account and the device identifier of the device end is sent to the application server.

[0215] It should be noted that in the related art, when accessing a third-party application by invoking the third-party application SDK within the system application without prior account login, the access is always in the unlogged state, which may cause some rights and interests functions within the third-party application to be unavailable. At this time, the system application will actively present the login and binding page of the third-party application and jump to the rights and interests purchase interface after successful binding. However, in the above method, the process of scanning the code and binding is relatively cumbersome, which may cause some users to be lost, thereby reducing the conversion rate of rights and interests purchase. The method of the management server actively registering a hidden account with the application server can omit the step of scanning the code and binding, thereby increasing the conversion rate of rights and interests purchase.

[0216] S920, obtain the hidden account fed back by the application server.

[0217] Among them, the hidden account is generated by the application server based on the first plain account and the device identifier.

[0218] Optionally, after receiving the hidden account generation request carrying the first plain account and the device identifier of the device end, the application server can generate a hidden account based on the pre-set hidden account generation logic using the first plain account and the device identifier of the device end, and feed back the hidden account to the management server.

[0219] Exemplarily, the application server can input the first plain account and the device identifier of the device end into the trained account generation model at the same time, and the account generation model outputs the hidden account according to the first plain account, the device identifier and the model parameters. Or, the first plain account and the device identifier of the device end can be combined to obtain the hidden account. For example, directly perform a splicing process on the first plain account and the device identifier of the device end. Or, relevant algorithms can be used to use the first plain account and the device identifier as parameters in the algorithm to generate the hidden account.

[0220] S930, bind the first plain account with the hidden account to generate the hidden binding relationship corresponding to the first plain account.

[0221] Among them, the hidden binding relationship corresponding to the first plain account is the binding relationship between the first plain account and the hidden account.

[0222] It should be noted that since the management server provides the hidden account query service and the service of obtaining the hidden account of the third-party application SDK for multiple device ends at the same time, in order to avoid the chaos of hidden account feedback, for each first plain account, after obtaining the hidden account of the first plain account, it is necessary to perform a binding process on the first plain account and the hidden account.

[0223] S940, query the hidden account bound to the first plain account based on the first plain account and the hidden binding relationship.

[0224] Optionally, after binding the first explicit account to the implicit account, based on the first explicit account, a re-query can be performed among various implicit binding relationships to obtain the implicit account bound to the first explicit account.

[0225] In the above technical solution, on the one hand, by instructing the application server to generate an implicit account, conditions are provided for the subsequent smooth progress of account binding; on the other hand, instructing the application server to generate an implicit account based on the system explicit account and the device identifier can ensure the uniqueness of the generated implicit account, and further ensure the accuracy of rights and interests data such as opening and querying from the application server based on the implicit account.

[0226] Based on the above embodiments, after sending a first rights and interests transaction request to the application server or sending a second rights and interests transaction request to the application server, in some embodiments, an optional method for account re-binding is provided, such as Figure 10 shown, and specifically includes the following steps:

[0227] S1010, receive a binding request sent by the terminal.

[0228] Among them, the binding request carries the first explicit account and the third explicit account of the third-party application, and is used to request the management server to bind the first explicit account and the third explicit account. The third explicit account is the account of the third-party application registered by the user.

[0229] In some embodiments, if the user wants to log in to other explicit accounts on the device side and continue to use the rights and interests data included in the implicit account itself, the second explicit account bound to the implicit account can be unbound and re-bound to the third explicit account.

[0230] In an optional implementation manner, when the terminal is the mobile terminal 300 and the device side is the display device 200, a login QR code for the third-party application can be displayed to the user through the display device 200. Among them, the login QR code can be generated based on the first explicit account. The user can first log in to the third-party application integrated in the mobile terminal 300 using the third explicit account, and then use the scanning device in the third-party application in the mobile terminal 300 to scan the login QR code. At this time, a login interface will be generated in the third-party application in the mobile terminal 300 based on the third explicit account, and the first explicit account will be obtained at the backend. After the user clicks the login control in the login interface, a binding request carrying the third explicit account and the first explicit account can be sent to the management server.

[0231] In another alternative embodiment, when the terminal and the device side are the same display device, after the display device 200 shows a login input interface of a third-party application to the user, the management server can obtain the third-party account by obtaining the login information entered by the user in the login input interface. After the user triggers the login control in the login input interface, a binding request carrying the third-party account and the first-party account can be sent to the management server.

[0232] S1020, in response to the binding request, when the first-party account has been bound to the second-party account, use the third-party account to replace the second-party account in the explicit binding relationship between the first-party account and the second-party account.

[0233] Optionally, after receiving the binding request sent by the terminal, the first-party account in the binding request can be used as index information to query among the candidate explicit binding relationships stored in the management server. After it is found that the first-party account has been bound to the second-party account of the third-party application, the second-party account in the original explicit binding relationship can be replaced with the third-party account, that is, the first-party account and the second-party account in the original explicit binding relationship can be unbound first, and the first-party account and the third-party account can be rebound to complete the rebinding in the explicit binding relationship.

[0234] S1030, send an explicit and implicit rebinding request to the application server.

[0235] Among them, the explicit and implicit rebinding request is used to instruct the application server to unbind the second-party account from the implicit account and bind the third-party account to the implicit account.

[0236] Optionally, after replacing the second-party account in the explicit binding relationship, the first-party account can be used as index information to query among the candidate explicit and implicit binding relationships to obtain the implicit account bound to the first-party account. Then, an explicit and implicit rebinding request carrying the implicit account and the third-party account can be sent to the application server.

[0237] After receiving the explicit and implicit rebinding request, the application server can query among the candidate explicit and implicit binding relationships based on the implicit account to obtain the second-party account bound to the implicit account. Then, the second-party account is unbound from the implicit account, and after the unbinding, the third-party account is bound to the implicit account.

[0238] Furthermore, after the application server successfully completes the rebinding, it can feedback a successful rebinding message to the management server.

[0239] It can be understood that when unbinding the second explicit account from the hidden account, in some alternative embodiments, the remaining entitlement data of the second explicit account and the remaining entitlement data of the hidden account can be split from the current entitlement data under the secret signal according to the entitlement stacking record from the second explicit account to the hidden account. Among them, the current entitlement data under the hidden account is the overall remaining entitlement data of the entitlement data under the second explicit account and the entitlement data under the hidden account at the current moment. The remaining entitlement data is the entitlement data under the second explicit account / hidden account included in the current entitlement data when performing the rebinding process.

[0240] In some other alternative embodiments, the remaining entitlement data of the second explicit account can be continued to be retained in the hidden account.

[0241] S1040, after receiving the successful rebinding message feedback from the application server, send a second entitlement transfer message to the application server.

[0242] Among them, the second entitlement transfer message is used to instruct the application server to stack the entitlement data under the third explicit account and the entitlement data of the hidden account.

[0243] Optionally, after receiving the successful rebinding message feedback from the application server, a second entitlement transfer message carrying the third explicit account and the hidden account can be sent to the application server. The application server uses the third explicit account and the hidden account in the second entitlement transfer message as index information respectively to query in the stored entitlement data, so as to obtain the entitlement data under the hidden account and the entitlement data under the third explicit account; then, the entitlement data under the third explicit account and the entitlement data under the hidden account are stacked. Thus, the entitlement data under the third explicit account and the entitlement data under the hidden account of the user are consistent.

[0244] Compared with the related art, in the above technical solution, the entitlement data of the third-party application purchased within the system application can only be bound to a single device or a single account. By adopting the above method, the entitlement data is bound under the hidden account, and the hidden account is respectively bound to different explicit accounts, and then the entitlement data under the hidden account is respectively stacked with the entitlement data in different accounts, so that the entitlement data under the hidden account can no longer be only bound to a single account, thus ensuring the full use of the entitlement data.

[0245] In an alternative embodiment, another account processing method is provided. Taking the account processing method applied to the controller in the mobile terminal as an example, where the mobile terminal includes a display and a controller. As Figure 11 shown, it specifically includes the following steps:

[0246] S1110. Scan the payment QR code for a third-party application presented by the system application in the display device to obtain the first clear account number and the current version information of the system application, the address information of the management server, and output a payment page.

[0247] Among them, the system application is the application corresponding to the management server in the device terminal.

[0248] Optionally, the display device 200 can generate a payment QR code for a third-party application based on the first clear account number and the current version information of the system application, as well as the address information of the management server, and display it on the display 260 in the display device 200. At this time, the user can use the mobile terminal 300 to scan the payment QR code, so that the mobile terminal 300 can obtain the first clear account number and the current version information of the system application, as well as the address information of the management server, and output a payment page for a third-party application through the display in the mobile terminal 300.

[0249] S1120. Respond to the payment operation on the payment page and obtain the rights and interests transaction information.

[0250] Optionally, the user can enter the rights and interests information to be purchased in the payment interface and click the purchase control. At this time, the mobile terminal can obtain the rights and interests transaction information based on the rights and interests information to be purchased.

[0251] S1130. Based on the address information, send an initial rights and interests transaction request to the management server.

[0252] Among them, the initial rights and interests transaction request carries the rights and interests transaction information, the first clear account number and the current version information; the initial rights and interests transaction request is used to request the management server to send a first rights and interests transaction request to the application server of the third-party application when the dark account bound to the first clear account number is queried; in the case where the dark account is not queried, if the current version information indicates that the system application is an application after version downgrade, obtain the second clear account number of the third-party application bound to the first clear account number, and send a second rights and interests transaction request to the application server.

[0253] The first rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the dark account; the second rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the second clear account number; the binding relationship between the dark account, the first clear account number and the second clear account number is established before the system application undergoes version downgrade; the dark account is an account used to authenticate the access behavior initiated by the third-party application software development kit (SDK) in the system application by the application server, and the first clear account number cannot be directly authenticated by the application server.

[0254] Optionally, the mobile terminal 300 may send an initial rights trading request carrying rights trading information, the first plain account number, and the current version information to the management server at the corresponding location based on the address information.

[0255] When the management server queries the dark account bound to the first plain account number, it sends a first rights trading request to the application server of the third-party application, and the application server superimposes the rights data corresponding to the rights trading information on the rights data under the dark account.

[0256] When the management server fails to query the dark account bound to the first plain account number, if the current version information indicates that the system application is an application after version downgrade, it may obtain the second plain account number of the third-party application bound to the first plain account number based on the plain binding relationship associated with the first plain account number, and send a second rights trading request carrying rights trading information and the second plain account number to the application server, and the application server superimposes the rights data corresponding to the rights trading information on the rights data under the second plain account number.

[0257] In the above technical solution, the mobile terminal scans the payment QR code for the third-party application presented by the system application in the display device to obtain the first plain account number and the current version information of the system application, the address information of the management server, and outputs the payment page. Then, in response to the payment operation on the payment page, it obtains the rights trading information, and based on the address information, sends an initial rights trading request to the management server. When the user purchases new rights data, it can select the account to which the purchased rights data is to be superimposed based on the binding relationship between the first plain account number, the dark account number, and the second plain account number, which can avoid the chaos of rights data superposition. Further, by binding the first plain account number, the dark account number, and the second plain account number, in the subsequent process of using rights, whether the user logs in with the dark account number or the second plain account number, they can continue to use the superimposed rights data under the dark account number and the second plain account number based on the account binding relationship, thus ensuring the maximization of the use of rights data.

[0258] Based on the technical solutions of the above embodiments, in the case where the terminal is a mobile terminal and the device end is a display device, an optional embodiment is provided. Refer to Figure 12 The schematic diagram of the account processing among devices in the account processing process shown below, including:

[0259] S1201, on the premise of logging in to the system application with the first plain account number, when the display device detects that the user has a rights purchase requirement, it outputs a payment QR code based on the first plain account number and the current version information of the system application, and the address information of the management server.

[0260] S1202, the mobile terminal scans the payment QR code in the display device to obtain the first clear account number and the current version information of the system application, the address information of the management server, and outputs the payment page.

[0261] S1203, in response to a payment operation on the payment page, the mobile terminal obtains the first clear account number and the current version information of the system application, the address information of the management server, and based on the address information, sends an initial rights and interests transaction request carrying the first clear account number, the current version information, and the rights and interests transaction information to the management server.

[0262] S1204, the management server queries the dark account bound to the first clear account number. If a dark account bound to the first clear account number is found, S1205 is executed; if no dark account bound to the first clear account number is found, S1207 is executed.

[0263] S1205, the management server sends a first rights and interests transaction request carrying the dark account number and the rights and interests transaction information to the application server.

[0264] S1206, the application server superimposes the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the dark account number to obtain new rights and interests data.

[0265] S1207, the management server sends a second rights and interests transaction request carrying the second clear account number and the rights and interests transaction information to the application server.

[0266] S1208, the application server superimposes the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the second clear account number to obtain new rights and interests data.

[0267] S1209, the application server feeds back the new rights and interests data to the management server.

[0268] S1210, the management server uses the new rights and interests data to update the rights and interests data associated with the first clear account number.

[0269] For the specific processes of the above S1201 - S1210, reference can be made to the descriptions of the above method embodiments. Their implementation principles and technical effects are similar and will not be elaborated here.

[0270] Based on the technical solutions of the above embodiments, the management server can be refined. Among them, the management server can include an account management system associated with the system application and an e-commerce management system. The account management system is used to manage the binding relationship between the clear and dark accounts under the system clear account number, and the e-commerce management system is used to manage the rights and interests under the dark account number associated with the system clear account number.

[0271] Based on this, the present application refines the rights and interests transaction process for the management server. SeeFigure 13 Schematic diagram of account processing among devices under the account processing process shown, including:

[0272] S1301, when the device detects a purchase of rights and interests for a third-party application, it sends an initial rights and interests transaction request carrying rights and interests transaction information, the first clear account of the system application, and the current version information to the e-commerce management system.

[0273] S1302, the e-commerce management system sends a dark account query request carrying the first clear account to the account management system.

[0274] S1303, the account management system queries the dark account bound to the first clear account based on the first clear account, and when the dark account bound to the first clear account is found, it executes S1304; when the dark account bound to the first clear account is not found, it executes 1307.

[0275] S1304, the account management system feeds back the dark account to the e-commerce management system.

[0276] S1305, the e-commerce management system sends a first rights and interests transaction request carrying the dark account and rights and interests transaction information to the application server.

[0277] S1306, the application server superimposes the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the dark account to obtain new rights and interests data.

[0278] S1307, the account management system feeds back the second clear account bound to the first clear account to the e-commerce management system.

[0279] S1308, the e-commerce management system sends a second rights and interests transaction request carrying the second clear account and rights and interests transaction information to the application server.

[0280] S1309, the application server superimposes the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the second clear account to obtain new rights and interests data.

[0281] S1310, the application server feeds back the new rights and interests data to the e-commerce management system.

[0282] S1311, the e-commerce management system uses the new rights and interests data to update the rights and interests data associated with the first clear account.

[0283] S1312, the device sends a rights and interests query request carrying the first clear account to the e-commerce management first.

[0284] S1313, the e-commerce management first obtains the rights and interests data associated with the first clear account based on the first clear account and feeds back the obtained rights and interests data to the device.

[0285] For the specific processes of S1301 - S1313 above, reference can be made to the descriptions in the above - mentioned method embodiments. Their implementation principles and technical effects are similar, and thus will not be elaborated here.

[0286] It should be understood that although each step in the flowcharts involved in the above - described embodiments is shown in sequence according to the indication of the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless clearly stated in this article, there is no strict order limit for the execution of these steps, and these steps can be executed in other orders. Moreover, at least some of the steps in the flowcharts involved in the above - described embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily executed at the same moment, but can be executed at different moments, and the execution order of these steps or stages is not necessarily sequential, but can be executed alternately or in turn with at least a part of other steps or steps or stages in other steps.

[0287] Based on the same inventive concept, an embodiment of the present application further provides an account processing device for implementing the above - mentioned account processing method. The solution provided by this device to solve the problem is similar to the solution described in the above - mentioned method. Therefore, the specific limitations in one or more embodiments of the account processing device provided below can refer to the limitations on the account processing method in the above text, and will not be elaborated here.

[0288] In an exemplary embodiment, as Figure 14 shown, an account processing device 1 is provided, configured in a management server, including: a request receiving module 10, a first request sending module 20, and a second request sending module 30, where:

[0289] The request receiving module 10 is used to receive an initial rights and interests transaction request sent by a terminal for a third - party application; the initial rights and interests transaction request carries rights and interests transaction information, as well as a first clear account number and current version information of a system application; the system application is the application corresponding to the management server in the device end;

[0290] The first request sending module 20 is used to send a first rights and interests transaction request to an application server when an encrypted account number bound to the first clear account number is queried; the first rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the encrypted account number;

[0291] The second request sending module 30 is configured to, when the dark account bound to the first plain account is not queried, if the current version information indicates that the system application is the application after version downgrade, obtain the second plain account of the third-party application bound to the first plain account, and send a second rights and interests transaction request to the application server; the second rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the second plain account; wherein, the binding relationships among the dark account, the first plain account, and the second plain account are established before the system application undergoes version downgrade; the dark account is an account used to authenticate the access behavior initiated by the third-party application software development kit (SDK) in the system application by the application server, and the first plain account cannot be directly authenticated by the application server.

[0292] In some embodiments, when the terminal is a mobile terminal and the device end is a display device, the first plain account and the current version information are obtained by the mobile terminal scanning the payment QR code presented in the system application; or, when the terminal and the device end are the same display device, the first plain account is obtained by the display device based on the login operation of the system application.

[0293] In some embodiments, after sending the first rights and interests transaction request or the second rights and interests transaction request to the application server, the account processing device 1 further includes a rights and interests update module. The rights and interests update module is configured to receive new rights and interests data; the new rights and interests data is the rights and interests data obtained by superimposing the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the dark account, or the new rights and interests data is the rights and interests data obtained by superimposing the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the second plain account; the rights and interests data associated with the first plain account is updated using the new rights and interests data.

[0294] In some embodiments, the account processing device 1 further includes a rights and interests query module. The rights and interests query module is configured to, in response to a rights and interests query request carrying the first plain account sent by the device end, obtain the rights and interests data associated with the first plain account from the rights and interests data stored locally based on the first plain account; and feedback the obtained rights and interests data to the device end.

[0295] In some embodiments, before receiving an initial rights and interests transaction request for a third-party application sent by a receiving terminal, the account processing device 1 further includes an account binding module. The account binding module is configured to receive binding indication information sent by the receiving terminal. The binding indication information carries a first plain account number and a second plain account number. Obtain the hidden account bound to the first plain account number, and send a plain-hidden binding request to the application server. The plain-hidden binding request is used to request the application server to perform plain-hidden binding on the second plain account number and the hidden account number. After receiving the binding success message feedback from the application server, send a first rights and interests transfer message to the application server. The first rights and interests transfer message is used to instruct the application server to superimpose the rights and interests data under the second plain account number and the rights and interests data under the hidden account number.

[0296] In some embodiments, the account processing device 1 further includes a hidden account acquisition module. The hidden account acquisition module is configured to, when no corresponding plain-hidden binding relationship is queried based on the first plain account number, send a hidden account generation request to the application server. The hidden account generation request carries the first plain account number and the device identifier of the device terminal. Obtain the hidden account number feedback by the application server. The hidden account number is generated by the application server according to the first plain account number and the device identifier. Bind the first plain account number and the hidden account number to generate a plain-hidden binding relationship corresponding to the first plain account number. Query the hidden account number bound to the first plain account number based on the first plain account number and the plain-hidden binding relationship.

[0297] In some embodiments, after sending a first rights and interests transaction request to the application server or sending a second rights and interests transaction request to the application server, the account processing device 1 further includes an account re-binding module. The account re-binding module is configured to receive a binding request sent by the receiving terminal. The binding request carries the first plain account number and the third plain account number of the third-party application. In response to the binding request, when the first plain account number is already bound to the second plain account number, use the third plain account number to replace the second plain account number in the plain binding relationship between the first plain account number and the second plain account number. And send a plain-hidden re-binding request to the application server. The plain-hidden re-binding request is used to instruct the application server to unbind the second plain account number from the hidden account number and bind the third plain account number to the hidden account number. After receiving the re-binding success message feedback from the application server, send a second rights and interests transfer message to the application server. The second rights and interests transfer message is used to instruct the application server to superimpose the rights and interests data under the third plain account number and the rights and interests data under the hidden account number.

[0298] In an exemplary embodiment, as Figure 15 shown, there is provided an account processing device 2 configured in a mobile terminal, including: a scanning module 40, an information acquisition module 50, and a third request sending module 60, where:

[0299] A scanning module 40 is configured to scan a payment QR code for a third-party application presented by a system application in a display device, obtain a first plain account number and current version information of the system application, address information of a management server, and output a payment page; the system application is an application corresponding to the management server in the device terminal;

[0300] An information acquisition module 50 is configured to acquire rights and interests transaction information in response to a payment operation performed on the payment page;

[0301] A third request sending module 60 is configured to send an initial rights and interests transaction request to the management server based on the address information; the initial rights and interests transaction request carries the rights and interests transaction information, the first plain account number, and the current version information; the initial rights and interests transaction request is used to request the management server to send a first rights and interests transaction request to the application server of the third-party application when a hidden account bound to the first plain account number is queried; in the case where no hidden account is queried, if the current version information indicates that the system application is an application after version downgrade, obtain a second plain account number of the third-party application bound to the first plain account number, and send a second rights and interests transaction request to the application server; the first rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the hidden account; the second rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the second plain account number; the binding relationships among the hidden account, the first plain account number, and the second plain account number are established before the system application undergoes version downgrade; the hidden account is an account used to authenticate access behaviors initiated by a third-party application software development kit (SDK) in the system application by the application server, and the first plain account number cannot be directly authenticated by the application server.

[0302] Each module in the above account processing device can be implemented in whole or in part by software, hardware, and their combination. The above modules can be embedded in the processor in the computer device in hardware form or be independent of it, or be stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to the above respective modules.

[0303] In an exemplary embodiment, a computer device is provided. The computer device can be a server, and its internal structural diagram can be as shown in Figure 16As shown in the figure. The computer device includes a processor, a memory, an input / output interface (Input / Output, abbreviated as I / O), and a communication interface. Among them, the processor, the memory, and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store account-related data. The input / output interface of the computer device is used to exchange information between the processor and external devices. The communication interface of the computer device is used to communicate with external terminals through a network connection. The computer program, when executed by the processor, implements an account processing method.

[0304] Those skilled in the art can understand that Figure 16 the structure shown in the figure is only a block diagram of some structures related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine some components, or have different component arrangements.

[0305] In an alternative embodiment, Figure 16 the computer device shown in the figure may be the aforementioned management server.

[0306] In an embodiment, a computer device is further provided, including a memory and a processor. A computer program is stored in the memory, and when the processor executes the computer program, the steps in the above method embodiments are implemented.

[0307] In an embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by the processor, the steps in the above method embodiments are implemented.

[0308] In an embodiment, a computer program product is provided, including a computer program. When the computer program is executed by the processor, the steps in the above method embodiments are implemented.

[0309] It should be noted that the user information (including but not limited to user account information, etc.) and data (including but not limited to rights and interests data, etc.) involved in the present application are all information and data authorized by the user or fully authorized by all parties, and the collection, use, and processing of relevant data need to comply with relevant regulations.

[0310] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, database, or other medium used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The databases involved in the embodiments provided in this application can include at least one of relational databases and non-relational databases. Non-relational databases can include distributed databases based on blockchain, etc., without limitation. The processors involved in the embodiments provided in this application can be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, data processing logics based on quantum computing, artificial intelligence (AI) processors, etc., without limitation.

[0311] The technical features of the above embodiments can be combined arbitrarily. For the sake of concise description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered to be within the scope recorded in this application.

[0312] The above-described embodiments merely represent several implementation manners of the present application. The description thereof is relatively specific and detailed, but it should not be construed as a limitation on the patent scope of the present application. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can still be made, and these all fall within the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the appended claims.

Claims

1. A management server, characterized in that, Including: A communication device configured to communicate and connect with a terminal and an application server corresponding to a third-party application; And at least one processor, connected to the communication device and configured to: Receive an initial rights and interests transaction request for the third-party application sent by the terminal; the initial rights and interests transaction request carries rights and interests transaction information, as well as a first plain account number and current version information of the system application; the system application is an application in the device side corresponding to the management server; In the case of querying a hidden account bound to the first plain account number, send a first rights and interests transaction request to the application server; The first rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the hidden account; In the case of not querying a hidden account bound to the first plain account number, if the current version information indicates that the system application is an application after version downgrade, obtain a second plain account number of the third-party application bound to the first plain account number, and send a second rights and interests transaction request to the application server; the second rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the second plain account number; Wherein, the binding relationships among the hidden account, the first plain account number and the second plain account number are established before the system application undergoes version downgrade; the hidden account is an account used to authenticate the access behavior initiated by the third-party application software development kit (SDK) in the system application by the application server, and the first plain account number cannot be directly authenticated by the application server.

2. The management server according to claim 1, characterized in that, When the terminal is a mobile terminal and the device side is a display device, the first plain account number and the current version information are obtained by the mobile terminal scanning a payment QR code presented in the system application; or, When the terminal and the device side are the same display device, the first plain account number is obtained by the display device according to a login operation of the system application.

3. The management server according to claim 1 or 2, characterized in that, After the processor executes sending the first rights and interests transaction request to the application server or sending the second rights and interests transaction request to the application server, it is further configured to: Receive new rights and interests data; wherein, the new rights and interests data is the rights and interests data after superimposing the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the hidden account, or the new rights and interests data is the rights and interests data after superimposing the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the second plain account number; Use the new rights and interests data to update the rights and interests data associated with the first plain account number.

4. The management server according to any one of claims 1-3, characterized in that, The processor is further configured to: In response to a rights and interests query request carried by the device side and carrying the first plain account number, based on the first plain account number, obtain the rights and interests data associated with the first plain account number from the rights and interests data stored locally; Feedback the obtained rights and interests data to the device side.

5. The management server according to any one of claims 1-3, characterized in that Before the processor executes receiving the initial rights and interests transaction request for the third-party application sent by the terminal, it is further configured to: Receive the binding indication information sent by the terminal; wherein, the binding indication information carries the first plain account number and the second plain account number; Obtain the dark account bound to the first plain account number, and send a plain-dark binding request to the application server; wherein, the plain-dark binding request is used to request the application server to perform plain-dark binding on the second plain account number and the dark account number; After receiving the binding success message feedback from the application server, send a first rights transfer message to the application server; wherein, the first rights transfer message is used to instruct the application server to superimpose the rights data under the second plain account number and the rights data under the dark account number.

6. The management server according to claim 5, wherein When the processor executes to obtain the dark account bound to the first plain account number, it is configured as: In the case that no corresponding dark binding relationship is queried based on the first plain account number, send a dark account generation request to the application server; wherein, the dark account generation request carries the first plain account number and the device identifier of the device side; Obtain the dark account number feedback by the application server; wherein, the dark account number is generated by the application server according to the first plain account number and the device identifier; Bind the first plain account number and the dark account number to generate the dark binding relationship corresponding to the first plain account number; Based on the first plain account number and the dark binding relationship, query the dark account number bound to the first plain account number.

7. The account management server according to any one of claims 1-3, characterized in that, After the processor executes to send a first rights transaction request to the application server or send a second rights transaction request to the application server, it is further configured as: Receive the binding request sent by the terminal; wherein, the binding request carries the first plain account number and the third plain account number of the third-party application; In response to the binding request, in the case that the first plain account number has been bound to the second plain account number, use the third plain account number to replace the second plain account number in the plain binding relationship between the first plain account number and the second plain account number; and Send a plain-dark rebinding request to the application server; wherein, the plain-dark rebinding request is used to instruct the application server to unbind the second plain account number from the dark account number and bind the third plain account number to the dark account number; After receiving the rebinding success message feedback from the application server, send a second rights transfer message to the application server; wherein, the second rights transfer message is used to instruct the application server to superimpose the rights data under the third plain account number and the rights data of the dark account number.

8. A mobile terminal, characterized in that, Includes: A display and a controller; The controller is configured as: Scan the payment QR code for the third-party application presented by the system application in the display device to obtain the first plain account number and the current version information of the system application, the address information of the management server, and output a payment page; the system application is the application corresponding to the management server in the device side; In response to a payment operation on the payment page, obtain rights transaction information; Based on the address information, send an initial rights transaction request to the management server; The initial rights and interests transaction request carries the rights and interests transaction information, a first explicit account number, and current version information; The initial rights and interests transaction request is used to request the management server to send a first rights and interests transaction request to the application server of the third-party application when an implicit account bound to the first explicit account is queried; In the case where the implicit account is not queried, if the current version information indicates that the system application is an application after version downgrade, obtain a second explicit account of the third-party application bound to the first explicit account, and send a second rights and interests transaction request to the application server; The first rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the implicit account; the second rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the second explicit account; The binding relationships among the implicit account, the first explicit account, and the second explicit account are established before the system application undergoes version downgrade; the implicit account is an account used to authenticate access behaviors initiated by the software development kit (SDK) of the third-party application in the system application, and the first explicit account cannot be directly authenticated by the application server.

9. An account processing method, characterized in that, Applied to a management server, the method includes: Receiving an initial rights and interests transaction request for a third-party application sent by a terminal; the initial rights and interests transaction request carries rights and interests transaction information, a first explicit account number of the system application, and current version information; the system application is an application corresponding to the management server in the device terminal; In the case where an implicit account bound to the first explicit account is queried, sending a first rights and interests transaction request to the application server corresponding to the third-party application; the first rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the implicit account; In the case where an implicit account bound to the first explicit account is not queried, if the current version information indicates that the system application is an application after version downgrade, obtain a second explicit account of the third-party application bound to the first explicit account, and send a second rights and interests transaction request to the application server; the second rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the second explicit account; Wherein, the binding relationships among the implicit account, the first explicit account, and the second explicit account are established before the system application undergoes version downgrade; the implicit account is an account used to authenticate access behaviors initiated by the software development kit (SDK) of the third-party application in the system application, and the first explicit account cannot be directly authenticated by the application server.

10. An account processing method, characterized in that, Applied to a mobile terminal, the method includes: Scan the payment QR code for a third-party application presented by the system application in the display device to obtain the first clear account number and the current version information of the system application, the address information of the management server, and output a payment page; the system application is the application corresponding to the management server in the device terminal; In response to a payment operation on the payment page, obtain rights and interests transaction information; Based on the address information, send an initial rights and interests transaction request to the management server; The initial rights and interests transaction request carries the rights and interests transaction information, the first clear account number and the current version information; The initial rights and interests transaction request is used to request the management server to send a first rights and interests transaction request to the application server of the third-party application when an encrypted account number bound to the first clear account number is found; when the encrypted account number is not found, if the current version information indicates that the system application is an application after version downgrade, obtain the second clear account number of the third-party application bound to the first clear account number, and send a second rights and interests transaction request to the application server; The first rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the encrypted account number; the second rights and interests transaction request is used to request the application server to superimpose the rights and interests data corresponding to the rights and interests transaction information on the rights and interests data under the second clear account number; The binding relationships among the encrypted account number, the first clear account number and the second clear account number are established before the system application undergoes version downgrade; the encrypted account number is used to authenticate the access behavior initiated by the third-party application software development kit (SDK) in the system application by the application server, and the first clear account number cannot be directly authenticated by the application server.

Images