Management server and data display method

Abstract

The invention relates to a management server and a data display method. A processor in the management server is configured to: after receiving a right transaction request for a target application, query a dark account bound with a first bright account, and query historical receiving conditions of each specified application for mobile terminal rights based on the first bright account, according to the transaction source of the transaction, the historical receiving condition of each specified application and the application priority of each specified application, determining a display sequence between mobile terminal right and interest cards corresponding to different specified applications; and after the control application server superposes the right and interest data of the display end and the right and interest data under the corresponding dark account to obtain a right and interest transaction result of the display end, transaction result data including the right and interest transaction result, the display sequence and the card data of the mobile end right and interest card are sent to the display device. By adopting the method, the rationality of right and interest data display of the mobile terminal can be ensured, so that the maximization of right and interest use is ensured.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, in particular to a management server and a data display method. BACKGROUND

[0002] With the development of display devices and the diversified needs of users for information, more and more software development kits (SDKs) of third-party applications can be integrated into applications, such as system applications of smart televisions. When a user purchases a third-party application right on a device side, a designated application right on a mobile side is usually given as a gift. At this time, in order to prompt the user about the right gift, the taking of the mobile right is displayed on the device side.

[0003] However, in actual scenarios, when purchasing a right on a display device, multiple designated application rights on a mobile side are usually given as gifts. Since the display device lacks logic for simultaneously displaying the multiple mobile rights, this can result in unreasonable right display, thereby reducing the maximization of right use. SUMMARY

[0004] The present application provides a management server and a data display method, which can ensure the rationality of mobile right data display, thereby ensuring the maximization of right use.

[0005] In a first aspect, some embodiments provide a management server, comprising:

[0006] A communication device configured to be in communication connection with a display device and an application server corresponding to a target application;

[0007] and at least one processor connected with the communication device and configured to:

[0008] receive a right transaction request for the target application; the right transaction request carries right transaction information and a first open account number of a system application; the target application includes at least one third-party application, the target application and the system application are installed in the display device, and the system application is an application corresponding to the management server in the display device;

[0009] query a dark account number bound to the first open account number, and in a case where it is determined according to the right transaction information that this transaction is accompanied by mobile rights of at least two designated applications, query a historical taking situation of each designated application for the mobile right based on the first open account number; the dark account number is an account number used to authenticate access behaviors initiated by a software development kit (SDK) of a third-party application in the system application to the corresponding application server, the first open account number cannot be directly authenticated by the application server; different dark account numbers correspond to different third-party applications;

[0010] determine the display order between the mobile end benefit cards corresponding to different designated applications according to at least one of the transaction source of the current transaction, the historical taking conditions of the designated applications, and the application priorities of the designated applications;

[0011] superimpose the display end benefit data corresponding to the benefit transaction information and the benefit data under the corresponding dark account to obtain a display end benefit transaction result;

[0012] send transaction result data corresponding to the benefit transaction request to the display device; the transaction result data includes the display end benefit transaction result, the display order between the mobile end benefit cards corresponding to different designated applications, and card data of the mobile end benefit card corresponding to each designated application.

[0013] The above technical solution, in the case of determining that the current transaction is accompanied by mobile end benefits of at least two designated applications according to the benefit transaction information, on the one hand, determines the display order between the mobile end benefit cards corresponding to different designated applications according to at least one of the transaction source of the current transaction, the historical taking conditions of the designated applications, and the application priorities of the designated applications, which can ensure the rationality of the display of the mobile end benefits of the designated applications; on the other hand, after the control application server superimposes the display end benefit data corresponding to the benefit transaction information and the benefit data under the corresponding dark account to obtain a display end benefit transaction result, sends transaction result data containing the benefit transaction result, the display order between the mobile end benefit cards corresponding to different designated applications, and the card data of the mobile end benefit card corresponding to each designated application to the display device, so that the display device can intuitively display the mobile end benefits based on the display order between the mobile end benefit cards and the card data of the mobile end benefit cards, which can ensure that the user more reasonably obtains the mobile end benefit data, thereby ensuring the maximization of the use of benefits.

[0014] In some embodiments, when the processor determines the display order between the mobile end benefit cards corresponding to different designated applications according to at least one of the transaction source of the current transaction, the historical taking conditions of the designated applications, and the application priorities of the designated applications, it is configured to:

[0015] In the case that the historical taking conditions of the designated applications are all taken or not taken, the display order between the mobile end benefit cards corresponding to different designated applications is determined according to the transaction source of the current transaction and / or the application priorities of the designated applications;

[0016] In a case where the historical taking situation corresponding to each designated application includes a case where the first application is taken and a case where the second application is not taken, the mobile terminal benefit card corresponding to the second application is arranged in front of the mobile terminal benefit card corresponding to the first application, to obtain the display order between the mobile terminal benefit cards corresponding to different designated applications.

[0017] The technical solution can ensure flexibility and rationality of the display order determination by selecting and determining the display order between the mobile terminal benefit cards corresponding to different designated applications according to the benefit taking situation of each designated application as a whole.

[0018] In some embodiments, in a case where the target application includes at least two third-party applications and the designated application is a third-party application, when the processor determines the display order between the mobile terminal benefit cards corresponding to different designated applications according to the transaction source of the current transaction and / or the application priority of each designated application, the processor is configured to perform any one of the following:

[0019] In a case where the transaction source of the current transaction is the application detail page of any third-party application, the mobile terminal benefit cards corresponding to the remaining third-party applications are arranged after the mobile terminal benefit card corresponding to the third-party application, to obtain the display order; the remaining third-party applications are third-party applications other than the third-party application among the at least two third-party applications;

[0020] In a case where the transaction source of the current transaction is a non-target entry, the mobile terminal benefit card corresponding to the third-party application with a high application priority is arranged in front of the mobile terminal benefit card corresponding to the third-party application with a low application priority, to obtain the display order; the target entry is the application detail page of any third-party application among the at least two third-party applications.

[0021] The technical solution can ensure flexibility and rationality of the display order determination by judging whether the transaction source of the current transaction is the application detail page of any third-party application, to select and determine the display order between the mobile terminal benefit cards corresponding to different designated applications.

[0022] In some embodiments, when the processor arranges the mobile terminal benefit card corresponding to the second application in front of the mobile terminal benefit card corresponding to the first application to obtain the display order between the mobile terminal benefit cards corresponding to different designated applications, the processor is configured to:

[0023] determine a first order between the mobile terminal benefit cards corresponding to different first applications according to the transaction source of the current transaction and / or the application priority of different first applications;

[0024] determine a second order between the mobile terminal benefit cards corresponding to different second applications according to the transaction source of the current transaction and / or the application priority of different second applications;

[0025] The first sequence is spliced after the second sequence to obtain a display sequence between the mobile terminal benefit cards corresponding to different designated applications.

[0026] The above technical solution can ensure the rationality of the display sequence determination by first determining the first sequence between each first application and the second sequence between each second application, and then splicing the first sequence after the second sequence to obtain the display sequence.

[0027] In some embodiments, in the case that the target application includes at least two third-party applications and the designated application is a third-party application, when the processor performs control on the application server to superimpose the display terminal benefit data corresponding to the benefit transaction information and the benefit data under the corresponding dark account to obtain a display terminal benefit transaction result, it is configured to:

[0028] For each third-party application, in the case that the corresponding historical collection situation of the third-party application is that it has been collected, the second light account of the third-party application is read from the locally stored historical collection record;

[0029] A first transaction request is sent to the application server corresponding to the third-party application; the first transaction request is used to instruct the application server to superimpose the display terminal benefit data corresponding to the target transaction information and the benefit data under the dark account corresponding to the third-party application, and to superimpose the mobile terminal benefit data of the third-party application attached to this transaction and the benefit data under the second light account; the target transaction information is the benefit transaction information of the third-party application in the benefit transaction information;

[0030] The benefit transaction result sent by the application server is received; the benefit transaction result includes the display terminal benefit transaction result.

[0031] The above technical solution provides a way to obtain display terminal benefits and mobile terminal benefits at the same time, that is, by instructing the application server to superimpose the display terminal benefit data corresponding to the target transaction information and the benefit data under the dark account corresponding to the third-party application, and to superimpose the mobile terminal benefit data of the third-party application attached to this transaction and the benefit data under the second light account, which can ensure the reliability of the benefit superposition.

[0032] In some embodiments, the benefit transaction result further includes a mobile terminal benefit transaction result, and the processor is further configured to:

[0033] For each third-party application, in the case that the corresponding historical collection situation of the third-party application is that it has been collected, the card data of the mobile terminal benefit card corresponding to the third-party application is determined according to the mobile terminal benefit transaction result;

[0034] For each third-party application, if the corresponding historical taking condition of the third-party application is that no taking has been performed, the card data of the mobile terminal benefit card corresponding to the third-party application is determined according to the prompt taking information.

[0035] The technical solution described above can ensure the flexibility and reliability of the determination of the card data by selecting a corresponding card data determination manner according to the historical taking condition of the third-party application.

[0036] In some embodiments, if the benefit transaction request is sent by the mobile terminal, the first clear account is obtained by scanning a payment QR code presented in the system application by the mobile terminal.

[0037] If the benefit transaction request is sent by the display device, the first clear account is obtained by the display device according to a login operation on the system application.

[0038] The technical solution described above provides an optional way of scanning payment in the interaction scenario of the display device, the mobile terminal and the management server, and provides an optional way of logging in the first clear account on the display device in the interaction scenario of the display device and the management server. That is, different optional ways are provided in different scenarios, which not only expands the use scenarios of the solution, but also improves the user experience.

[0039] In a second aspect, some embodiments further provide a display device, comprising:

[0040] a display and a controller;

[0041] the controller is configured to:

[0042] receive transaction result data sent by the management server; the transaction result data comprises a display end benefit transaction result, a display order between mobile terminal benefit cards corresponding to different specified applications and card data of each mobile terminal benefit card corresponding to a specified application;

[0043] control the display to display the display end benefit transaction result, and control the display to display each mobile terminal benefit card according to the display order and the card data of each mobile terminal benefit card corresponding to a specified application;

[0044] the display order is determined by the management server according to at least one of a transaction source of the current transaction, a historical taking condition of each specified application for the mobile terminal benefit and an application priority of each specified application;

[0045] The historical acquisition of the mobile terminal benefit of each designated application is obtained by the management server based on the first open account of the system application obtained by querying the dark account bound to the first open account in the case that the management server determines that the transaction is accompanied by the mobile terminal benefits of at least two designated applications according to the benefit transaction information carried by the received benefit transaction request for the target application.

[0046] The display terminal benefit transaction result is obtained by the management server by controlling the application server corresponding to the target application to superimpose the display terminal benefit data corresponding to the benefit transaction information on the benefit data under the corresponding dark account.

[0047] The target application includes at least one third-party application, and the target application and the system application are installed in the display device, and the system application is an application corresponding to the management server in the display device.

[0048] The dark account is an account used to authenticate the access behavior initiated by the third-party application SDK in the system application by the corresponding application server, and the first open account cannot be directly authenticated by the application server. Different dark accounts correspond to different third-party applications.

[0049] The above technical solution can ensure the rationality of the display of the mobile terminal benefit information by controlling the display to display the display terminal benefit transaction result in the transaction result data after receiving the transaction result data sent by the management server, and controlling the display to display each mobile terminal benefit card according to the display order and the card data of the mobile terminal benefit card corresponding to each designated application, so that the user can clearly understand the mobile terminal benefit data he owns, thereby maximizing the use of the benefit data.

[0050] In a third aspect, some embodiments further provide a data display method applied to a management server, comprising:

[0051] Receiving a benefit transaction request for a target application; the benefit transaction request carries benefit transaction information and a first open account of a system application; the target application includes at least one third-party application, and the target application and the system application are installed in a display device, and the system application is an application corresponding to the management server in the display device;

[0052] Querying a dark account bound to the first open account, and in the case that the management server determines that the transaction is accompanied by the mobile terminal benefits of at least two designated applications according to the benefit transaction information, querying the historical acquisition of the mobile terminal benefit of each designated application based on the first open account; 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 corresponding application server, and the first open account cannot be directly authenticated by the application server; different dark accounts correspond to different third-party applications.

[0053] Determine a display order between the mobile end benefit cards corresponding to different designated applications according to at least one of a transaction source of the current transaction, historical taking conditions of the designated applications, and application priorities of the designated applications; and

[0054] Control the application server to superimpose the display end benefit data corresponding to the benefit transaction information and the benefit data under the corresponding dark account to obtain a display end benefit transaction result;

[0055] Send transaction result data corresponding to the benefit transaction request to the display device; the transaction result data includes the display end benefit transaction result, the display order between the mobile end benefit cards corresponding to different designated applications, and card data of the mobile end benefit card corresponding to each designated application.

[0056] In a fourth aspect, some embodiments further provide a data display method applied to a display device, comprising:

[0057] Receive the transaction result data sent by the management server; the transaction result data includes the display end benefit transaction result, the display order between the mobile end benefit cards corresponding to different designated applications, and the card data of the mobile end benefit card corresponding to each designated application;

[0058] Control the display to display the display end benefit transaction result, and control the display to display each mobile end benefit card according to the display order and the card data of the mobile end benefit card corresponding to each designated application;

[0059] The display order is determined by the management server according to at least one of a transaction source of the current transaction, historical taking conditions of the designated applications for mobile end benefits, and application priorities of the designated applications;

[0060] The historical taking conditions of the designated applications for mobile end benefits are obtained by the management server based on a first light account of a system application carried by the received benefit transaction information carried by the benefit transaction request, in a case where the current transaction is accompanied by mobile end benefits of at least two designated applications;

[0061] The display end benefit transaction result is obtained by the management server by controlling the application server corresponding to the target application to superimpose the display end benefit data corresponding to the benefit transaction information and the benefit data under the corresponding dark account;

[0062] The target application includes at least one third-party application, and the target application and the system application are installed in the display device; the system application is an application corresponding to the management server in the display device;

[0063] The dark account is an account used for authenticating access behaviors initiated by a third-party application SDK in a system application by a corresponding application server, and the first clear account cannot be directly authenticated by the application server; different dark accounts correspond to different third-party applications.

[0064] In a fifth aspect, some embodiments further provide a data display device configured in a management server, comprising:

[0065] The request receiving module is configured to receive a benefit transaction request for a target application; the benefit transaction request carries benefit transaction information and a first clear account of a system application; the target application includes at least one third-party application, and the target application and the system application are installed in a display device, and the system application is an application corresponding to the management server in the display device;

[0066] The information querying module is configured to query a dark account bound to the first clear account, and in a case where it is determined according to the benefit transaction information that the current transaction is accompanied by mobile terminal benefits of at least two specified applications, query a historical receiving situation of each specified application for the mobile terminal benefits based on the first clear account; the dark account is an account used for authenticating access behaviors initiated by a third-party application software development kit (SDK) in a system application by a corresponding application server, and the first clear account cannot be directly authenticated by the application server; different dark accounts correspond to different third-party applications;

[0067] The sequence determining module is configured to determine a display sequence between mobile terminal benefit cards corresponding to different specified applications according to at least one of a transaction source of the current transaction, the historical receiving situation of each specified application, and an application priority of each specified application; and

[0068] The result determining module is configured to control the application server to superimpose display terminal benefit data corresponding to the benefit transaction information and benefit data under the corresponding dark account to obtain a display terminal benefit transaction result.

[0069] The data generating module is configured to send transaction result data for the benefit transaction request to the display device; the transaction result data includes the display terminal benefit transaction result, the display sequence between the mobile terminal benefit cards corresponding to different specified applications, and card data of the mobile terminal benefit card corresponding to each specified application.

[0070] In a sixth aspect, some embodiments further provide a data display device configured in a display device, comprising:

[0071] The data receiving module is configured to receive transaction result data sent by the management server; the transaction result data includes a display terminal benefit transaction result, a display sequence between mobile terminal benefit cards corresponding to different specified applications, and card data of a mobile terminal benefit card corresponding to each specified application.

[0072] The display module is configured to control the display to display the mobile terminal benefit card according to the display order and the card data of the mobile terminal benefit card corresponding to each specified application.

[0073] The display order is determined by the management server according to at least one of a transaction source of the current transaction, a historical taking situation of the mobile terminal benefit by each specified application, and an application priority of each specified application. The historical taking situation of the mobile terminal benefit by each specified application is obtained by the management server based on a first open account of a system application carried in the benefit transaction information carried in the received benefit transaction request of the target application, in a case that the current transaction is accompanied by mobile terminal benefits of at least two specified applications. The display terminal benefit transaction result is obtained by the management server by controlling the application server corresponding to the target application to superimpose the display terminal benefit data corresponding to the benefit transaction information and the benefit data under the corresponding dark account. The target application includes at least one third-party application, and the target application and the system application are installed in the display device. The system application is an application corresponding to the management server in the display device. The dark account is an account used to authenticate the access behavior initiated by the third-party application SDK in the system application by the corresponding application server. The first open account cannot be directly authenticated by the application server. Different dark accounts correspond to different third-party applications.

[0074] In a seventh aspect, a computer-readable storage medium is provided, and the computer-readable storage medium stores a computer program. When the computer program is run by a data display device, the data display device executes any one of the data display methods in the first aspect or the second aspect.

[0075] In an eighth aspect, a computer program product is provided, and the computer program product includes a computer program. When the computer program is run by a data display device, the data display device executes any one of the data display methods in the first aspect or the second aspect. BRIEF DESCRIPTION OF DRAWINGS

[0076] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related art, the drawings needed to be used in the description of the embodiments of the present application or the related art will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other related drawings can also be obtained without creative labor on the basis of these drawings.

[0077] Figure 1 The schematic diagram of the operation scenario between the display device and the control device provided by some embodiments of the present application;

[0078] Figure 2A hardware configuration schematic diagram of a display device provided for some embodiments of the present application;

[0079] Figure 3 A hardware configuration schematic diagram of a control device provided for some embodiments of the present application;

[0080] Figure 4 A software configuration schematic diagram of a display device provided for some embodiments of the present application;

[0081] Figure 5 A flowchart of a data display method provided for some embodiments of the present application;

[0082] Figure 6 A mobile terminal benefit card display schematic diagram provided for some embodiments of the present application;

[0083] Figure 7 A mobile terminal benefit card display schematic diagram provided for some embodiments of the present application;

[0084] Figure 8 A flowchart of a display order determination provided for some embodiments of the present application;

[0085] Figure 9 A mobile terminal benefit card display schematic diagram provided for some embodiments of the present application;

[0086] Figure 10 A benefit superposition flowchart provided for some embodiments of the present application;

[0087] Figure 11 A flowchart of a data display method provided for some embodiments of the present application;

[0088] Figure 12 A benefit display page schematic diagram provided for some embodiments of the present application;

[0089] Figure 13 A benefit display page schematic diagram provided for some embodiments of the present application;

[0090] Figure 14 A data display schematic diagram between devices in a data display process provided for some embodiments of the present application;

[0091] Figure 15 A structural block diagram of a data display device in some embodiments;

[0092] Figure 16 A structural block diagram of a data display device in some embodiments. DETAILED DESCRIPTION

[0093] The embodiments will be described in detail below with reference to examples thereof as illustrated in the accompanying drawings. In the following description, like reference characters designate like or similar elements in different views. The embodiments described in the following examples do not represent all of the implementations consistent with the present application. Rather, they are merely examples consistent with some aspects of the present application as detailed in the appended claims.

[0094] It should be noted that the brief description of terms in the present application is only for the convenience of understanding the following description of the embodiments, and is not intended to limit the embodiments of the present application. Unless otherwise specified, these terms should be understood according to their ordinary and customary meanings.

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

[0096] The terms "include" and "have" and any variations thereof are intended to cover but not exclusive of inclusion, for example, a product or device including a series of components does not necessarily limit to all components clearly listed, but can include other components not clearly listed or inherent to such products or devices.

[0097] The term "module" refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and / or software code capable of performing a function associated with that element.

[0098] In some embodiments, the management server can be a server 400 with account management capabilities. It can be a standalone server or a server cluster. The display device 200 refers to a device with picture 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.

[0099] Figure 1 The schematic diagram of the operation scenario between the display device and the control device is provided for some embodiments of the present application. As shown in Figure 1 The user can operate the display device 200 through touch operation, mobile terminal 300 and control device 100. For example, the control device 100 can be a remote controller, a stylus, a handle, etc.

[0100] The mobile terminal 300 can serve as a control device for performing human-computer interaction between a user and the display device 200. The mobile terminal 300 can also serve as a communication device for establishing a communication connection with the display device 200 and performing data interaction. In some embodiments, the mobile terminal 300 can install a software application with the display device 200, implement connection communication through a network communication protocol, and achieve the purpose of one-to-one control operation and data communication. The mobile terminal 300 can also display audio and video content on the display device 200 to achieve a synchronous display function.

[0101] As shown in Figure 1 It is also shown in the

[0102] The display device 200 can provide a broadcast receiving television function, and can additionally provide an intelligent network television function with computer support, including but not limited to, a network television, a smart television, an Internet Protocol Television (IPTV), and the like.

[0103] Figure 2 The display device 200 provided in some embodiments of the present application Figure 1 A hardware configuration block diagram of the display device 200 is shown in

[0104] In some embodiments, the display device 200 can include at least one of a tuning 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.

[0105] In some embodiments, the detector 230 is used to collect signals of an external environment or interaction with the outside. For example, the detector 230 includes a light receiver for collecting ambient light intensity, or an image collector such as a camera for collecting an external environment scene, user attributes, or user interaction gestures, or a sound collector such as a microphone for receiving external sound.

[0106] In some embodiments, the display 260 includes a display functional component for presenting a picture, and a driving component for driving image display. The display 260 is used to receive an image signal output from the controller 250 for display. For example, the display 260 can be used to display video content, image content, and components of a menu control interface, as well as a user control UI interface, and the like.

[0107] In some embodiments, the communication device 220 is a component for communicating with the external device or the server 400 according to various communication protocol types. The display device 200 can be provided with multiple communication devices 220 according to different supported communication manners. For example, when the display device 200 supports wireless network communication, the display device 200 can be provided with a communication device 220 containing a Wireless Fidelity (WiFi) function. When the display device 200 supports Bluetooth connection communication, the display device 200 needs to be provided with a communication device 220 containing a Bluetooth function.

[0108] The communication device 220 can make the display device 200 communicate with the external device or the server 400 through wireless or wired connection. The wired connection can connect the display device 200 with the external device through a data line, an interface, etc. The wireless connection can connect the display device 200 with the external device through a wireless signal or a wireless network. The display device 200 can directly establish a connection relationship with the external device, or indirectly establish a connection relationship through a gateway, a router, a connection device, etc.

[0109] In some embodiments, the controller 250 can include at least one of a central processor, a video processor, an audio processor, a graphics processor, a power supply processor, a first interface to an n-th interface for input / output, and control the operation of the display device and respond to the user's operation through various software control programs stored on the memory. The controller 250 controls the overall operation of the display device 200.

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

[0111] In some embodiments, the user can input a user command in a Graphical User Interface (GUI) displayed on the display 260, and the user input interface receives the user input command through the Graphical User Interface (GUI).

[0112] In some embodiments, the audio output device 270 can be a native loudspeaker of the display device 200, or an audio output device connected to the display device 200. For the audio output device connected to the display device 200, the display device 200 can also be provided with an external audio output terminal, and the audio output device can be connected to the display device 200 through the external audio output terminal to output the sound of the display device 200.

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

[0114] Figure 3 A hardware configuration block diagram of a control device is provided in some embodiments of the present application. Figure 1 As shown in the figure, the control device 100 can include a controller 110, a communication interface 130, a user input / output interface, a memory, a power supply. Figure 3

[0115] The control device 100 is configured to control the display device 200, and can receive user input operation instructions, and convert the operation instructions into instructions that the display device 200 can recognize and respond to, acting as an intermediary between the user and the display device 200.

[0116] In some embodiments, the control device 100 can be a smart device. For example, the control device 100 can install various applications for controlling the display device 200 according to user needs.

[0117] In some embodiments, as shown in the figure, the mobile terminal 300 or other smart electronic devices can perform similar functions to the control device 100 after installing applications for controlling the display device 200. Figure 1

[0118] The controller 110 includes a processor 112 and a RAM 113 and 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 the internal components and the external and internal data processing functions.

[0119] The communication interface 130, under the control of the controller 110, realizes the communication of control signals and data signals between the display device 200. The communication interface 130 can include at least one of a WiFi chip 131, a Bluetooth module 132, an N FC module 133, and other near field communication modules.

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

[0121] In some embodiments, the control device 100 includes at least one of the communication interface 130 and the input / output interface 140. The control device 100 is configured with a communication interface 130, such as a WiFi, Bluetooth, N FC, etc. module, which can encode user input instructions through WiFi protocol, or Bluetooth protocol, or N FC protocol and send them to the display device 200.

[0122] ​​A memory 190 is configured to store various operation 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.

[0123] A power supply 180 is configured to provide operation power support for the elements of the control device 100 under the control of the controller.

[0124] To perform user interaction, in some embodiments, the display device 200 can run an operating system. The operating system is a computer program for managing and controlling hardware resources and software resources in the display device 200. The operating system can provide a user interface to allow the user to interact with the display device 200 and support running various application programs.

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

[0126] The operating system can be divided into different modules or levels according to the functions implemented, for example, as shown in FIG. 2, in some embodiments, the system is divided into four layers, from top to bottom, the Applications layer (referred to as the "application layer"), the Application Framework layer (referred to as the "framework layer"), the system library layer and the kernel layer. Figure 4

[0127] In some embodiments, the application layer is configured to provide services and interfaces for application programs, so that the display device 200 can run application programs and interact with the user based on the application programs. At least one application program can be run in the application layer, which can be a window (Window) program, a system setting program or a clock program provided by the operating system, or an application program developed by a third-party developer. In specific implementation, the application programs in the application layer are not limited to the above examples.

[0128] The framework layer provides application programming interfaces (APIs) and programming frameworks for application programs. The application framework layer includes some pre-defined functions. The application framework layer is equivalent to a processing center that decides which application program in the application layer to act. The application program can access the resources in the system and obtain the services of the system through the API interface in the execution.

[0129] As shown in FIG. 2, in some embodiments, the framework layer includes a Java® virtual machine (JVM) and a Dalvik virtual machine (Dalvik VM). The JVM is a virtual machine for running Java® programs, and the Dalvik VM is a virtual machine for running Android® programs. Figure 4 ​As shown, in the embodiment of the present application, the application framework layer includes a view system, managers, content providers, etc., wherein the view system can design and implement the interface and interaction of the application, and the view system includes lists, grids, text boxes, buttons, etc. The manager includes at least one of the following modules: an activity manager for interacting with all activities running in the system; a location manager for providing system services or applications with access to the system location service; a package manager for retrieving various information related to the application packages currently installed on the device; a notification manager for controlling the display and clearing of notification messages; and a window manager for managing icons, windows, toolbars, wallpapers, and desktop widgets on the user interface.

[0130] In some embodiments, the activity manager is used to manage the lifecycle of each application and common navigation back functions, such as controlling application exit, opening, and back. The window manager is used to manage all window programs, such as obtaining the display screen size, determining whether there is a status bar, locking the screen, taking screenshots, and controlling changes in display windows, such as shrinking, shaking, or distorting the display window.

[0131] In some embodiments, the system runtime layer can provide support for the framework layer. When the framework layer is used, the operating system will run the instruction library contained in the system runtime layer, such as the C / C++ instruction library, to implement the functions to be implemented by the framework layer.

[0132] In some embodiments, the kernel layer is a functional layer between the hardware and software of the display device 200. The kernel layer can implement functions such as hardware abstraction, multitasking, and memory management. Figure 4 As shown, the kernel layer can be configured with hardware drivers, 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 driver (such as fingerprint sensor, temperature sensor, pressure sensor, etc.), and power driver, etc.

[0133] It should be noted that the above examples are only a simple division of the operating system function, and do not constitute a limitation on the specific operating system form of the display device 200 in the embodiments of the present application. According to the function of the display device, the type of the operating system, and other factors, the number and specific level types of the levels contained in the operating system can be in other forms.

[0134] With the development of display devices, and the diversified needs of users for information, more and more third-party application SDKs can be integrated into applications, such as system applications of smart televisions. For example, a smart television can integrate system applications and third-party application SDKs. The system application is a host application deployed in the terminal, that is, a third-party application can be accessed by calling the third-party application SDK.

[0135] Further, in order to ensure the convenience of user operation, after the user has logged in to the system application with the first clear account, the dark account of the third-party application can be automatically generated for the user, and the dark account is used for login. After that, the rights and interests data purchased by the user on the display device will be directly bound to the dark account of the user. It should be noted that the dark accounts used by each third-party application are different.

[0136] In actual scenarios, when purchasing rights and interests on display devices, a variety of specified applications on mobile terminals are usually gifted with rights and interests, but due to the lack of logic for simultaneously displaying multiple mobile terminal rights and interests on display devices, this can lead to unreasonable rights and interests display, thereby reducing the maximization of rights and interests use.

[0137] Based on this, in some embodiments, a data display method is provided. The data display method can be implemented by a management server and a display device. In an optional implementation, the data display method is applied to a processor in the management server, wherein the management server includes a communication device and at least one processor; the communication device is in communication connection with a display device and an application server corresponding to a target application, which can be wired communication connection or wireless communication connection, and the processor is connected with the communication device.

[0138] As shown in Figure 5 , specifically comprising the following steps:

[0139] S510, receiving a rights and interests transaction request for a target application.

[0140] The so-called target application is an application corresponding to the user's rights and interests purchase demand, further, the target application includes at least one third-party application, and the target application and the system application are installed in the display device, and the system application is an application corresponding to the management server in the display device. The rights and interests can be a VIP member rights and interests of the user in the third-party application, such as a music application VIP. The third-party application can be integrated in the mobile terminal.

[0141] The equity transaction request carries equity transaction information and a first clear account number of the system application. The equity transaction information is transaction information generated when the equity transaction is performed on the target application, and can include equity transaction time, equity transaction details (such as equity purchase quantity, payment information), and further can include the mobile terminal equity gift condition when the transaction is performed. It is worth noting that the mobile terminal equity gift condition can or can not correspond to the display terminal equity purchase. For example, when purchasing a display terminal music application VIP, a corresponding mobile terminal music application VIP can be gifted, or a mobile terminal video application VIP can be gifted.

[0142] Optionally, after the user logs in to the system application using the first clear account number, the device detects that the user has an operation of performing equity data purchase on the target application, and initiates an equity transaction request for the target application according to the equity transaction information of the transaction. The user's operation of performing equity data purchase on the target application can be triggering the equity purchase control of the target application in the display device. For example, triggering the equity purchase identifier in the target application page displayed by the display device.

[0143] In an optional implementation, when the equity transaction request is sent by the mobile terminal, the first clear account number is obtained by the mobile terminal by scanning a payment two-dimensional code presented in the system application.

[0144] Specifically, when the display device detects that the user has an operation of performing equity data purchase on the target application, the system application can display a payment two-dimensional code for purchasing the display terminal equity of the target application to the user based on the equity transaction information (i.e., the display terminal equity details to be purchased in the transaction, and the mobile terminal equity details attached in the transaction) displayed in the equity purchase interface of the target application. The payment two-dimensional code can include the first clear account number of the system application, the address information of the management server, and the equity transaction information of the transaction. The user can first scan the payment two-dimensional code using the payment application integrated in the mobile terminal. At this time, the mobile terminal can obtain the first clear account number, the address information of the management server, and the equity transaction information of the transaction, and generate a payment interface based on the resource information required for purchasing the display terminal equity in the equity transaction information. Further, after detecting that the user clicks the payment control in the payment interface, the mobile terminal can send an equity transaction request carrying the equity transaction information and the first clear account number to the management server according to the address information of the management server. At this time, the management server can obtain the equity transaction request initiated by the mobile terminal.

[0145] In another optional implementation, the first open account is obtained by the display device according to a login operation applied to the system application in a case where the equity transaction request is sent by the display device.

[0146] Specifically, the user stores the first open account locally when logging in to the system application by using the first open account. Then, the display device can show the user an equity purchase interface of a target application in a case where the user has a demand for equity purchase. Further, the display device can obtain the first open account of the system application from the local storage and send an equity transaction request carrying the equity transaction information and the first open account of the system application to the management server after the user inputs the equity transaction information to be purchased in the equity purchase interface and triggers a purchase control in the equity purchase interface.

[0147] S520, query the dark account bound to the first open account, and in a case where it is determined according to the equity transaction information that the transaction is accompanied by mobile end equity of at least two specified applications, query the history of receiving the mobile end equity of each specified application based on the first open account.

[0148] The dark account is an account used to enable the corresponding application server to authenticate an access behavior initiated by a third-party application SDK in the system application, and the first open account cannot be directly authenticated by the application server. Different dark accounts correspond to different third-party applications.

[0149] It is worth noting that the specified application can be any third-party application that deploys a corresponding SDK in the system application, or can be another application that is not deployed on the display device but only on the mobile end, and can or can not contain the target application. In this embodiment, no limitation is made to this.

[0150] In an optional implementation, after receiving the equity transaction request, the dark account of the target application bound to the first open account in the equity transaction request can be queried in the binding relationship between the first open account and the dark account stored in the management server according to the first open account and the application identifier of the target application, and an equity purchase request can be sent to the application server corresponding to the target application based on the dark account and the equity transaction information. At the same time, in order to determine the mobile end equity gifted by the transaction, the equity gift situation of the mobile end can also be obtained from the equity transaction information.

[0151] It is worth noting that in order to improve the convenience of mobile terminal benefit collection, if the user is given the mobile terminal benefit again after collecting any mobile terminal benefit, the user can directly collect the mobile terminal benefit based on the historical benefit collection path. Based on this, in the case where the mobile terminal benefit of at least two specified applications is determined to be accompanied by the current transaction based on the benefit giving condition, the historical collection condition of each specified application for the mobile terminal benefit can be queried in the historical benefit collection data stored in the management server based on the first clear account and the application identifier of each specified application.

[0152] For example, after the user logs in to the system application by using the first clear account, the video application VIP of the display terminal can be purchased through the dark account corresponding to the video application, at this time, the mobile terminal video application VIP and the music application VIP are given; thereafter, the historical collection condition of the user collecting the mobile terminal video application VIP can be queried according to the first clear account and the identifier information of the video application, and the historical collection condition of the user collecting the mobile terminal music application VIP can be queried according to the first clear account and the identifier information of the music application.

[0153] S530, according to at least one of the transaction source of the current transaction, the historical collection condition of each specified application and the application priority of each specified application, determine the display order between the mobile terminal benefit cards corresponding to different specified applications.

[0154] The so-called transaction source is the transaction location that initiates the current transaction, for example, if the current transaction is initiated based on the benefit purchase link in the music application, the transaction source is the benefit purchase page corresponding to the music application. Further, the way to determine the transaction source can be to determine the transaction source according to the corresponding web address when initiating the transaction.

[0155] The so-called application priority is used to represent the importance of each application, for example, which can be determined based on the number of users, influence intensity and application attributes of each application; the so-called mobile terminal benefit card is a card form to show the mobile terminal benefit to the user.

[0156] It is worth noting that when displaying the mobile terminal benefit cards corresponding to different specified applications, the user will pay attention to the mobile terminal benefit card sorted in the front, therefore, in order to improve the sufficiency of resource use, the display order between each mobile terminal benefit card can be determined based on at least one of the transaction source of the current transaction, the historical collection condition of each specified application and the application priority of each specified application.

[0157] In an optional embodiment, the display order between the mobile end benefit cards corresponding to different designated applications can be determined according to the transaction source of the current transaction only. For example, the display order between the mobile end benefit cards corresponding to different designated applications can be determined according to the relevance between the designated applications and the transaction source in descending order. For example, when the transaction source is the benefit purchase page corresponding to the video application, the display order between the mobile end benefit card of the video application and the mobile end benefit card of the music application is that the mobile end benefit card of the video application is displayed first, and then the mobile end benefit card of the music application is displayed.

[0158] In another optional embodiment, the display order between the mobile end benefit cards corresponding to different designated applications can be determined according to the historical taking situation of the designated applications only. For example, the mobile end benefit card corresponding to a designated application that has been taken can be directly arranged at the back. For example, when the mobile end benefit of the video application has been taken, and the mobile end benefit of the music application has not been taken, the display order of the mobile end benefit cards is that the mobile end benefit card of the music application is displayed first, and then the mobile end benefit card of the video application is displayed.

[0159] In yet another optional embodiment, the display order between the mobile end benefit cards corresponding to different designated applications can be determined according to the application priority of the designated applications only. For example, the display order between the mobile end benefit cards corresponding to different designated applications can be determined according to the priority of the designated applications in descending order.

[0160] In still another optional embodiment, the transaction source of the current transaction, the historical taking situation of the designated applications, and the application priority of the designated applications can be directly input into a trained order determination model, and the order determination model can output the display order between the mobile end benefit cards according to the transaction source, the historical taking situation, and the application priority.

[0161] S540, the control application server superimposes the display end benefit data corresponding to the benefit transaction information and the benefit data under the corresponding dark account to obtain a display end benefit transaction result.

[0162] The display end benefit transaction result can represent the result of the display end benefit superposition, and can include specific information of success or failure of the benefit superposition, and benefit information under the dark account when the benefit superposition is successful.

[0163] In an optional implementation, the application server corresponding to the target application can be sent a benefit purchase request according to the dark account and the benefit transaction information. Correspondingly, the application server corresponding to the target application can obtain the display-end benefit data to be purchased by the user from the benefit transaction information in the benefit purchase request in the case of successful benefit purchase, and superimpose the display-end benefit data and the display-end benefit data under the dark account in the benefit purchase request to obtain superimposed display-end benefit data. Further, the display-end benefit transaction result can be generated according to the superimposed display-end benefit data, and the display-end benefit transaction result can be fed back to the management server.

[0164] S550, sending the transaction result data for the benefit transaction request to the display device.

[0165] The so-called transaction result data includes the display-end benefit transaction result, the display order between the mobile-end benefit cards corresponding to different specified applications, and the card data of the mobile-end benefit card corresponding to each specified application. Optionally, for each specified application, the card data of the mobile-end benefit card corresponding to the specified application can be determined according to the historical collection situation of the specified application. Further, the card data can include but is not limited to the collection situation of the mobile-end benefit, the benefit details of the mobile-end benefit, etc.

[0166] In an optional implementation, the transaction result data can be generated according to the display-end benefit data under the dark account in the display-end benefit transaction result, the display order between the mobile-end benefit cards corresponding to different specified applications, and the card data of the mobile-end benefit card corresponding to each specified application, and the transaction result data can be sent to the display device.

[0167] For example, in the case of a display-end benefit transaction result of transaction failure, the display device is directly fed back transaction failure information; in the case of a display-end benefit transaction result of transaction success, the transaction result data can be generated according to the display order between the mobile-end benefit cards corresponding to different specified applications and the card data of the mobile-end benefit card corresponding to each specified application, and the transaction result data can be sent to the display device.

[0168] It is worth noting that in the case of determining that the current transaction is only accompanied by a mobile-end benefit of a specified application according to the benefit giving situation, the transaction result data can be generated only according to the display-end benefit transaction result and the card data of the mobile-end benefit card corresponding to the specified application, and the transaction result data can be sent to the display device.

[0169] In the above data display method, in the case that it is determined according to the equity transaction information that the current transaction is accompanied by mobile end equity of at least two specified applications, on the one hand, the display order between the mobile end equity cards corresponding to different specified applications is determined according to at least one of the transaction source of the current transaction, the historical taking situation of each specified application and the application priority of each specified application, so as to ensure the rationality of the display of the mobile end equity of each specified application; on the other hand, after the control application server superimposes the display end equity data corresponding to the equity transaction information and the equity data under the corresponding dark account to obtain the display end equity transaction result, the transaction result data containing the equity transaction result, the display order between the mobile end equity cards corresponding to different specified applications and the card data of the mobile end equity card corresponding to each specified application is sent to the display device, so that the display device can intuitively display each mobile end equity based on the display order between each mobile end equity card and the card data of each mobile end equity card, so as to ensure that the user can more reasonably obtain each mobile end equity data, thereby ensuring the maximization of the use of equity.

[0170] On the basis of the above embodiment, in the embodiment of the application, step S530 is further refined, specifically, in the case that the historical taking situation of each specified application is taking or not taking, the display order between the mobile end equity cards corresponding to different specified applications is determined according to the transaction source of the current transaction and / or the application priority of each specified application; in the case that the historical taking situation of each specified application includes taking of the first application and not taking of the second application, the mobile end equity card corresponding to the second application is arranged before the mobile end equity card corresponding to the first application to obtain the display order between the mobile end equity cards corresponding to different specified applications.

[0171] Among them, the so-called first application is a specified application that has taken mobile end equity; the so-called second application is a specified application that has not taken mobile end equity.

[0172] It is worth noting that in the case that the historical taking situation of any specified application corresponding to the first clear account is taking, the mobile end equity data corresponding to the specified application will be automatically taken according to the historical taking mode, therefore, in the case that the current transaction is accompanied by mobile end equity of at least two specified applications, there may be a case that part of the mobile end equity is automatically taken and part of the mobile end equity needs to be manually taken by the user, at this time, in order to prompt the user to manually take the mobile end equity data, the mobile end equity that has not been taken needs to be displayed in front.

[0173] Based on this, in an optional implementation, in a case where the historical taking conditions of the specified applications corresponding to the first clear account are all taken or not taken, it is proved that there is no priority difference between the specified applications in the benefit taking dimension, and therefore, the display order between the mobile end benefit cards corresponding to different specified applications can be determined only according to the transaction source of the current transaction and / or the application priority of the specified applications.

[0174] For example, the display order between the mobile end benefit cards corresponding to different specified applications can be determined only according to the transaction source of the current transaction. Alternatively, the display order between the mobile end benefit cards corresponding to different specified applications can be determined only according to the application priority of the specified applications. Alternatively, the display order between the mobile end benefit cards corresponding to different specified applications can be determined according to both the transaction source of the current transaction and the application priority of the specified applications.

[0175] In another optional implementation, in a case where the historical taking conditions of the specified applications corresponding to the first clear account include a case where the first application has been taken and the second application has not been taken, it is proved that the priority of the second application is higher than the priority of the first application in the benefit taking dimension, and therefore, the mobile end benefit card corresponding to the second application can be directly arranged in front of the mobile end benefit card corresponding to the first application to obtain the display order between the mobile end benefit cards corresponding to different specified applications.

[0176] For example, referring to the mobile end benefit card display schematic diagram shown in Figure 6 , when the user has taken the mobile end benefit of the video application and has not taken the mobile end benefit of the music application, the card data of the mobile end benefit card 1 of the music application can include the application name A of the music application, the text information “not taken”, and the benefit details “one-month music VIP”, and the card data of the mobile end benefit card 2 of the video application can include the application name B of the video application, the text information “has been taken”, and the benefit superposition result “benefit valid period to x year x month x day”. Then, the mobile end benefit card 1 of the music application is arranged in front of the mobile end benefit card 2 of the video application.

[0177] The above technical solution can ensure the flexibility and rationality of the determination of the display order between the mobile end benefit cards corresponding to different specified applications by selecting the display order between the mobile end benefit cards corresponding to different specified applications according to the overall benefit taking conditions of the specified applications.

[0178] On the basis of the above embodiments, in the embodiments of the present application, in the case that the target application includes at least two third-party applications and the specified application is a third-party application, that is, the specified application corresponds to the target application. For example, in the case that the target application is a music application and a video application, the specified application is also a music application and a video application. Further refinement of step S530 is as follows. In the case that the transaction source of the current transaction is the application detail page of any third-party application, the mobile terminal benefit card corresponding to the remaining third-party applications is arranged after the mobile terminal benefit card corresponding to the third-party application, and the display order is obtained; in the case that the transaction source of the current transaction is a non-target portal, the mobile terminal benefit card corresponding to the third-party application with high application priority is arranged before the mobile terminal benefit card corresponding to the third-party application with low application priority, and the display order is obtained.

[0179] In the above embodiments, in the case that the target application includes at least two third-party applications and the specified application is a third-party application, that is, the specified application corresponds to the target application. For example, in the case that the target application is a music application and a video application, the specified application is also a music application and a video application. Further refinement of step S530 is as follows. In the case that the transaction source of the current transaction is the application detail page of any third-party application, the mobile terminal benefit card corresponding to the remaining third-party applications is arranged after the mobile terminal benefit card corresponding to the third-party application, and the display order is obtained; in the case that the transaction source of the current transaction is a non-target portal, the mobile terminal benefit card corresponding to the third-party application with high application priority is arranged before the mobile terminal benefit card corresponding to the third-party application with low application priority, and the display order is obtained.

[0180] In an optional embodiment, in the case that the transaction source of the current transaction is the application detail page of any third-party application, it is proved that the user prefers to use the third-party application among multiple third-party applications. At this time, the mobile terminal benefit card corresponding to the remaining third-party applications can be arranged after the mobile terminal benefit card corresponding to the third-party application, so as to obtain the display order.

[0181] For example, in the case that the user purchases the display terminal music VIP and the display terminal video VIP through the application detail page of the music application, the mobile terminal benefit card corresponding to the music application can be displayed before the mobile terminal benefit card corresponding to the video application; in the case that the user purchases the display terminal video VIP and the display terminal music VIP through the application detail page of the video application, the mobile terminal benefit card corresponding to the video application can be displayed before the mobile terminal benefit card corresponding to the music application.

[0182] For example, in the case that the history of the music application and the video application corresponding to the application detail page is both taken, if the user purchases the display terminal music VIP and the display terminal video VIP through the application detail page of the music application, the mobile terminal benefit card display schematic diagram shown in Figure 7 The mobile terminal benefit card 3 containing the application name C of the music application, the text information "has been taken", and the benefit superposition result "the benefit validity period is x years x months x day" is arranged before the mobile terminal benefit card 4 containing the application name D of the video application, the text information "has been taken", and the benefit superposition result "the benefit validity period is x years x months x day".

[0183] In another optional embodiment, in the case that the transaction source of the current transaction is not the target portal, it is proved that the user does not prefer to use any third-party application in multiple third-party applications, at this time, the mobile end benefit card corresponding to the third-party application with high application priority can be arranged in front of the mobile end benefit card corresponding to the third-party application with low application priority based on the application priority of each third-party application, to obtain the display order.

[0184] For example, when the user directly purchases the display end music VIP and the display end video VIP through the benefit purchase page, since the priority of the video application is higher than that of the music application, the mobile end benefit card corresponding to the video application can be displayed in front of the mobile end benefit card corresponding to the music application.

[0185] In another optional embodiment, in the case that the transaction source of the current transaction is not the target portal, for each third-party application, the association degree between the third-party application and the transaction source and the priority of the third-party application can be weighted to obtain the comprehensive importance degree of the third-party application. Then, the display order can be determined according to the comprehensive importance degree of each third-party application.

[0186] The above technical solution can ensure the flexibility and rationality of the determination of the display order by judging whether the transaction source of the current transaction is the application detail page of any third-party application to select the way of determining the display order between the mobile end benefit cards corresponding to the specified applications.

[0187] On the basis of the above embodiments, in the embodiments of the present application, before arranging the mobile end benefit card corresponding to the second application in front of the mobile end benefit card corresponding to the first application, step S530 is further refined, as shown in the following table: Figure 8 The specific steps include the following steps:

[0188] S810, determining a first order between the mobile end benefit cards corresponding to different first applications according to the transaction source of the current transaction and / or the application priorities of different first applications.

[0189] The first order is the display order of the mobile end benefit cards between the first applications.

[0190] It can be understood that in the case that multiple first applications have already obtained the mobile end benefit, in order to ensure the rationality of the display between the first applications, the first order between the mobile end benefit cards corresponding to different first applications can be determined according to the transaction source of the current transaction and / or the application priorities of different first applications, by referring to the above steps.

[0191] Exemplarily, the first order between the mobile end benefit cards corresponding to the first applications can be determined only according to the association degrees between the first applications and the transaction source of the current transaction. Alternatively, the first order between the mobile end benefit cards corresponding to the first applications can be determined according to the application priorities of the first applications in descending order of the priorities. Alternatively, for each first application, the association degree between the first application and the transaction source and the priority of the first application can be weighted to obtain a comprehensive importance degree of the first application; and then the first order can be determined according to the comprehensive importance degrees of the first applications.

[0192] S820, determining a second order between the mobile end benefit cards corresponding to the different second applications according to the transaction source of the current transaction and / or the application priorities of the different second applications.

[0193] The second order is the display order of the mobile end benefit cards between the second applications.

[0194] It can be understood that in the case that multiple second applications without mobile end benefits are present at the same time, in order to ensure the rationality of the display between the second applications, the second order between the mobile end benefit cards corresponding to the different second applications can be determined according to the transaction source of the current transaction and / or the application priorities of the different second applications, by referring to the above steps.

[0195] Exemplarily, the second order between the mobile end benefit cards corresponding to the second applications can be determined only according to the association degrees between the second applications and the transaction source of the current transaction. Alternatively, the second order between the mobile end benefit cards corresponding to the second applications can be determined according to the application priorities of the second applications in descending order of the priorities. Alternatively, for each second application, the association degree between the second application and the transaction source and the priority of the second application can be weighted to obtain a comprehensive importance degree of the second application; and then the second order can be determined according to the comprehensive importance degrees of the second applications.

[0196] S830, splicing the first order after the second order to obtain the display order between the mobile end benefit cards corresponding to the different specified applications.

[0197] Optionally, after the first order and the second order are determined, since the priority of the second order is higher than that of the first order as a whole, the first order can be directly spliced after the second order to obtain the display order between the mobile end benefit cards corresponding to the different specified applications.

[0198] For example, for the first applications E and F, in the case that the application priority of application E is higher than that of application F, the first order is determined to be to first display the mobile terminal benefit card 5 corresponding to application E (containing the application name E, the text information "has been taken", and the benefit superposition result "the benefit validity period is until x year x month x day"), and then to display the mobile terminal benefit card 6 corresponding to application F (containing the application name F, the text information "has been taken", and the benefit superposition result "the benefit validity period is until x year x month x day"). Then, for the second applications G and H, in the case that the application priority of application G is higher than that of application H, the second order is determined to be to first display the mobile terminal benefit card 7 corresponding to application G (containing the application name G, the text information "has not been taken", and the benefit details "one month VIP"), and then to display the mobile terminal benefit card 8 corresponding to application H (containing the application name H, the text information "has not been taken", and the benefit details "one month VIP"). Finally, by referring to the mobile terminal benefit card display schematic diagram shown in FIG. 8, the display order between the mobile terminal benefit cards corresponding to the applications E, F, G and H can be obtained. Figure 9

[0199] The above technical solution can ensure the rationality of the display order determination by first determining the first order between each first application and the second order between each second application, and then splicing the first order after the second order to obtain the display order.

[0200] On the basis of the above embodiment, in the embodiment of the present application, in the case that the target application includes at least two third-party applications, and the specified application is a third-party application, step S540 is refined, as shown in FIG. 10, and specifically includes the following steps. Figure 10

[0201] S1010, for each third-party application, in the case that the historical taking situation corresponding to the third-party application is that the third-party application has been taken, reading the second open account number of the third-party application from the locally stored historical taking record.

[0202] The so-called second open account number is the open account number of the third-party application registered by the user.

[0203] It is worth noting that since the mobile terminal benefit can only be superimposed on the second open account number of the user in the third-party application, in order to facilitate the taking of the mobile terminal benefit, the second open account number used by the user when taking the mobile terminal benefit can be locally stored when the user takes the mobile terminal benefit for the first time.

[0204] Optionally, for each third-party application, in the case that the historical taking situation corresponding to the third-party application is that the third-party application has been taken, the second open account number corresponding to the third-party application can be read from the locally stored historical taking record based on the application identifier of the third-party application. ​​

[0205] S1020, sending the first transaction request to the application server corresponding to the third-party application.

[0206] The first transaction request is used to instruct the application server to superimpose the display end benefit data corresponding to the target transaction information on the benefit data under the dark account corresponding to the third-party application, and superimpose the mobile end benefit data of the third-party application attached in this transaction on the benefit data under the second light account. The target transaction information is the benefit transaction information of the third-party application.

[0207] Optionally, the first transaction request can be generated according to the dark account, the second light account, and the target transaction information corresponding to the third-party application, and the first transaction request is sent to the application server corresponding to the third-party application. Correspondingly, the application server corresponding to the third-party application can directly superimpose the display end benefit data purchased in the target transaction information on the dark account to obtain the superimposed display end benefit data, and superimpose the mobile end benefit data attached in this transaction on the second light account to obtain the superimposed mobile end benefit data after receiving the first transaction request.

[0208] Further, the application server can determine the display end benefit transaction result according to the superimposed display end benefit data, and determine the mobile end benefit transaction result according to the superimposed mobile end benefit data. Then, the benefit transaction result is generated according to the display end benefit transaction result and the mobile end benefit transaction result, and the benefit transaction result is sent to the management server. The mobile end benefit transaction result can represent the result of the mobile end benefit superposition, which can include specific information of the success or failure of the benefit superposition, and the benefit information under the second light account when the benefit superposition is successful.

[0209] S1030, receiving the benefit transaction result sent by the application server.

[0210] The benefit transaction result includes the display end benefit transaction result.

[0211] Optionally, the benefit transaction result sent by the application server can be received, and the superimposed display end benefit data and the superimposed mobile end benefit data in the benefit transaction result can be used to determine the transaction result data in the subsequent processing.

[0212] The above technical solution provides a way to obtain display end benefit and mobile end benefit at the same time, that is, by instructing the application server to superimpose the display end benefit data corresponding to the target transaction information on the benefit data under the dark account corresponding to the third-party application, and superimposing the mobile end benefit data of the third-party application attached in this transaction on the benefit data under the second light account, the reliability of the benefit superposition can be ensured.

[0213] On the basis of the above-mentioned embodiments, in the embodiments of the present application, the equity transaction result further includes a mobile terminal equity transaction result, and further, an optional mode of determining card data is provided, specifically, for each third-party application, in a case where the historical taking condition corresponding to the third-party application is that the third-party application has been taken, the card data of the mobile terminal equity card corresponding to the third-party application is determined according to the mobile terminal equity transaction result; for each third-party application, in a case where the historical taking condition corresponding to the third-party application is that the third-party application has not been taken, the card data of the mobile terminal equity card corresponding to the third-party application is determined according to prompt taking information.

[0214] The so-called prompt taking information is information for prompting a user to take a mobile terminal equity, for example, a text information "not taken" and the like.

[0215] Optionally, for each third-party application in a case where the historical taking condition corresponding to the third-party application is that the third-party application has been taken, a mobile terminal equity detail (for example, an equity expiration date) after equity stacking can be extracted from the mobile terminal equity transaction result; then, the equity expiration date, the taking condition and the application identifier of the third-party application are input into a first card data template to obtain the card data of the mobile terminal equity card corresponding to the third-party application. The first card data template is a card data template applicable to a case of automatically taking a mobile terminal equity.

[0216] Further, for each third-party application in a case where the historical taking condition corresponding to the third-party application is that the third-party application has not been taken, preset prompt taking information, equity details of a mobile terminal equity to be taken and an application identifier of the third-party application can be input into a second card data template to obtain the card data of the mobile terminal equity card corresponding to the third-party application. The second card data template is a card data template applicable to a case of manually taking a mobile terminal equity.

[0217] The above technical solution can ensure the flexibility and reliability of the determination of card data by selecting a corresponding card data determination mode according to the historical taking condition corresponding to the third-party application.

[0218] In an optional implementation, another data display method is provided. Taking a controller in a data display method applied to a display device as an example, the display device includes a display and the controller. As shown in Figure 11 the specific steps include the following steps:

[0219] S1110, receiving transaction result data sent by a management server.

[0220] The transaction result data includes a display terminal equity transaction result, a display order between mobile terminal equity cards corresponding to different specified applications and card data of a mobile terminal equity card corresponding to each specified application.

[0221] Optionally, after the management server sends the transaction result data to the display device, the display device can accept the transaction result data and obtain the display end benefit transaction result, the display order between the mobile end benefit cards corresponding to each specified application, and the card data of each mobile end benefit card from the transaction result data.

[0222] The display order is determined by the management server according to at least one of the transaction source of the current transaction, the historical collection of the mobile end benefit by each specified application, and the application priority of each specified application. The historical collection of the mobile end benefit by each specified application is obtained by the management server based on the first clear account of the system application obtained from the benefit transaction information carried by the received benefit transaction request, in the case that the current transaction is accompanied by the mobile end benefits of at least two specified applications. The display end benefit transaction result is obtained by the management server by controlling the application server corresponding to the target application to superimpose the display end benefit data corresponding to the benefit transaction information and the benefit data under the corresponding dark account.

[0223] The target application includes at least one third-party application, and the target application and the system application are installed in the display device. The system application is an application corresponding to the management server in the display device. The dark account is an account used to authenticate the access behavior initiated by the third-party application SDK in the system application by the corresponding application server. The first clear account cannot be directly authenticated by the application server. Different dark accounts correspond to different third-party applications.

[0224] S1120, controlling the display to display the display end benefit transaction result, and controlling the display to display each mobile end benefit card according to the display order and the card data of the mobile end benefit card corresponding to each specified application.

[0225] Optionally, the display end benefit transaction result can be displayed at a preset position in the benefit display page, and the display end benefit card corresponding to each specified application can be displayed according to the display order and the card data of the mobile end benefit card corresponding to each specified application.

[0226] For example, in the case of purchasing a display end video application VIP, it is determined that the expiration time of the purchased display end video application VIP is December 25, 2025, at the same time, the expiration time of the mobile end video application VIP is November 25, 2025, and the mobile end music application VIP is not collected for one month. The display mode of the above transaction result data can refer to the benefit display page shown in Figure 12 .

[0227] It is worth noting that in the case that the information represented by any mobile terminal benefit card is not collected, the user can trigger the mobile terminal benefit card through the remote control device, at this time, the benefit display page will automatically jump to the application login interface corresponding to the mobile terminal benefit card, and the user can send the second clear account under the application corresponding to the mobile terminal benefit card to the management server through the scanning login two-dimensional code / entering account password, so that the management server superimposes the mobile terminal benefit corresponding to the mobile terminal benefit card to the obtained second clear account, thereby completing the collection of the mobile terminal benefit.

[0228] The above technical solution can ensure the rationality of the display of mobile terminal benefit information, make the user clear about the mobile terminal benefit data he / she owns, and thereby maximize the use of benefit data, by controlling the display to display the display terminal benefit transaction result contained in the transaction result data after receiving the transaction result data sent by the management server, and controlling the display to display each mobile terminal benefit card according to the display order and the card data of the mobile terminal benefit card corresponding to each specified application.

[0229] Further, in some optional embodiments, the target application includes at least two third-party applications, and the specified application is a third-party application. That is, the user purchases multiple display terminal application VIPs, and the mobile terminal application VIPs corresponding to the transaction are also third-party applications deployed in the system application. For example, in the case of purchasing a display terminal video application VIP and a display terminal music application VIP through the music details page, it is determined that the display terminal video application VIP expires on December 25, 2025, and the display terminal music application VIP expires on December 27, 2025, while the mobile terminal video application VIP expires on November 25, 2025, and the mobile terminal music application VIP expires on November 27, 2025. The display method of the above transaction result data can refer to the benefit display page shown in Figure 13 .

[0230] On the basis of the technical solutions of the above embodiments, an optional embodiment is provided. In the embodiments of the present application, the target application is two third-party applications, and the specified application is the corresponding two third-party applications. Referring to the data display process of the management server, the application servers (application server 1 and application server 2 correspond to two third-party applications), the display device and the mobile terminal between the data display schematic diagram shown in Figure 14 .

[0231] S1401, under the premise of logging in the system application by using the first open account, the display device outputs a payment QR code based on the first open account of the system application, the address information of the management server and the benefit transaction information, in the case that the display device detects that the user has a demand for purchasing benefits for two third-party applications.

[0232] S1402, the mobile terminal scans the payment QR code in the display device to obtain the first open account of the system application and the address information of the management server, and outputs a payment page according to the benefit transaction information.

[0233] S1403, the mobile terminal sends a benefit transaction request carrying the first open account and the benefit transaction information to the management server based on the address information in response to a payment operation on the payment page.

[0234] S1404, the management server queries the dark account bound to the first open account based on the first open account, and queries the historical collection of the mobile terminal benefit of each third-party application based on the first open account in the case that it is determined according to the benefit transaction information that the transaction is accompanied by the mobile terminal benefits of the two third-party applications.

[0235] S1405, the management server determines the display order between the mobile terminal benefit cards corresponding to different third-party applications according to at least one of the transaction source of the transaction, the historical collection corresponding to each third-party application and the application priority of each third-party application.

[0236] S1406, the management server sends a benefit transaction request carrying the dark account and the benefit transaction information to the application server corresponding to each third-party application.

[0237] S1407, each application server superimposes the benefit data corresponding to the benefit transaction information of the third-party application corresponding to the application server in the benefit transaction information and the benefit data under the dark account to obtain the display terminal benefit transaction result, and feeds back the display terminal benefit transaction result to the management server.

[0238] S1408, the management server determines the card data of the mobile terminal benefit card corresponding to each third-party application according to the mobile terminal benefit transaction result corresponding to the third-party application that has collected and / or the prompt collection information corresponding to the third-party application that has not collected according to the historical collection.

[0239] S1409, the management server sends the display terminal benefit transaction result, the display order and the card data of each mobile terminal benefit card to the display device.

[0240] S1410, the display device controls the display to display the display terminal benefit transaction result, and controls the display to display each mobile terminal benefit card according to the display order and the card data of the mobile terminal benefit card corresponding to each third-party application.

[0241] The specific process of S1401-S1410 can refer to the description of the method embodiments, and the implementation principle and technical effects are similar, which will not be repeated here.

[0242] It should be understood that, although each step in the flowchart involved in each embodiment as described above is displayed in sequence according to the arrow, these steps are not necessarily executed in the order indicated by the arrow. Unless otherwise stated herein, the execution of these steps has no strict order limitation, and these steps can be executed in other orders. Moreover, at least part of the steps in the flowchart involved in each embodiment as described above can include multiple steps or stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily sequential, but can be alternately executed with other steps or steps or stages in other steps.

[0243] Based on the same inventive concept, the embodiments of the present application also provide a data display device for implementing the above-mentioned data display method. The implementation scheme of the problem solving provided by the device is similar to the implementation scheme described in the above method, so the specific limitations in one or more data display device embodiments provided below can refer to the limitations of the data display method described above, and will not be repeated here.

[0244] In one exemplary embodiment, as shown in Figure 15 A data display device 1 is provided, configured in a management server, comprising: a request receiving module 10, an information querying module 20, a sequence determining module 30, a result determining module 40 and a data generating module 50, wherein:

[0245] The request receiving module 10 is used to receive a benefit transaction request for a target application; the benefit transaction request carries benefit transaction information and a first clear account number of a system application; the target application includes at least one third-party application, the target application and the system application are installed in a display device, and the system application is an application corresponding to the management server in the display device;

[0246] The information query module 20 is configured to query the dark account bound to the first open account, and in the case that it is determined according to the benefit transaction information that the current transaction is accompanied by mobile terminal benefits of at least two specified applications, query the historical taking situation of each specified application for the mobile terminal benefits based on the first open account; the dark account is an account used for authenticating the access behavior initiated by the third-party application software development kit (SDK) in the system application to the corresponding application server, and the first open account cannot be directly authenticated by the application server; different dark accounts correspond to different third-party applications;

[0247] The sequence determination module 30 is configured to determine the display order between the mobile terminal benefit cards corresponding to different specified applications according to at least one of the transaction source of the current transaction, the historical taking situation of each specified application, and the application priority of each specified application; and

[0248] The result determination module 40 is configured to control the application server to superimpose the display terminal benefit data corresponding to the benefit transaction information and the benefit data under the corresponding dark account to obtain a display terminal benefit transaction result.

[0249] The data generation module 50 is configured to send transaction result data for the benefit transaction request to the display device; the transaction result data includes the display terminal benefit transaction result, the display order between the mobile terminal benefit cards corresponding to different specified applications, and the card data of the mobile terminal benefit card corresponding to each specified application.

[0250] In some embodiments, the sequence determination module 30 includes:

[0251] The first determination unit is configured to, in the case that the historical taking situation of each specified application is taking or not taking, determine the display order between the mobile terminal benefit cards corresponding to different specified applications according to the transaction source of the current transaction and / or the application priority of each specified application.

[0252] The second determination unit is configured to, in the case that the historical taking situation of each specified application includes taking of the first application and not taking of the second application, arrange the mobile terminal benefit card corresponding to the second application before the mobile terminal benefit card corresponding to the first application to obtain the display order between the mobile terminal benefit cards corresponding to different specified applications.

[0253] In some embodiments, the first determining unit is specifically configured to: in a case where the transaction source of the current transaction is an application detail page of any third-party application, arrange the mobile terminal benefit card corresponding to the remaining third-party applications after the mobile terminal benefit card corresponding to the third-party application to obtain the display order; the remaining third-party applications are third-party applications other than the third-party application among the at least two third-party applications; in a case where the transaction source of the current transaction is a non-target portal, arrange the mobile terminal benefit card corresponding to the third-party application with a high application priority before the mobile terminal benefit card corresponding to the third-party application with a low application priority to obtain the display order; and the target portal is the application detail page of any third-party application among the at least two third-party applications.

[0254] In some embodiments, the first determining unit is further configured to: determine a first order between the mobile terminal benefit cards corresponding to different first applications according to the transaction source of the current transaction and / or the application priorities of the different first applications; determine a second order between the mobile terminal benefit cards corresponding to different second applications according to the transaction source of the current transaction and / or the application priorities of the different second applications; and splice the first order after the second order to obtain the display order between the mobile terminal benefit cards corresponding to different specified applications.

[0255] In some embodiments, the result determining module 40 is specifically configured to: for each third-party application, in a case where the historical taking situation corresponding to the third-party application is that the third-party application has been taken, read the second clear account number of the third-party application from the locally stored historical taking record; send a first transaction request to the application server corresponding to the third-party application; the first transaction request is used to instruct the application server to superimpose the display terminal benefit data corresponding to the target transaction information on the benefit data under the dark account number corresponding to the third-party application, and superimpose the mobile terminal benefit data of the third-party application attached to the current transaction on the benefit data under the second clear account number; the target transaction information is the benefit transaction information of the third-party application; receive the benefit transaction result sent by the application server; and the benefit transaction result includes the display terminal benefit transaction result.

[0256] In some embodiments, the data display device 1 further includes a card data determining module, wherein the card data determining module is specifically configured to: for each third-party application, in a case where the historical taking situation corresponding to the third-party application is that the third-party application has been taken, determine the card data of the mobile terminal benefit card corresponding to the third-party application according to the mobile terminal benefit transaction result; and for each third-party application, in a case where the historical taking situation corresponding to the third-party application is that the third-party application has not been taken, determine the card data of the mobile terminal benefit card corresponding to the third-party application according to the prompt taking information.

[0257] In some embodiments, the data display device 1 further comprises an account obtaining module, wherein the account obtaining module is specifically configured to: in the case that the benefit transaction request is sent by the display device, the first open account is obtained by the display device according to a login operation on the system application.

[0258] In an exemplary embodiment, as shown in Figure 16 Fig. 2, a data display device 2 is provided, configured in a display device, comprising a data receiving module 60 and a display module 70, wherein:

[0259] The data receiving module 60 is configured to receive transaction result data sent by the management server; the transaction result data comprises display end benefit transaction result, display order between mobile end benefit cards corresponding to different specified applications, and card data of each mobile end benefit card corresponding to a specified application.

[0260] The display module 70 is configured to control the display to display the display end benefit transaction result, and control the display to display each mobile end benefit card according to the display order and the card data of each mobile end benefit card corresponding to a specified application.

[0261] The display order is determined by the management server according to at least one of the transaction source of the current transaction, the historical taking situation of each specified application for the mobile end benefit, and the application priority of each specified application; the historical taking situation of each specified application for the mobile end benefit is obtained by the management server based on the first open account of the system application carried by the received benefit transaction information for the target application, in the case that the current transaction is accompanied by mobile end benefits of at least two specified applications; the display end benefit transaction result is obtained by the management server by controlling the application server corresponding to the target application to superimpose the display end benefit data corresponding to the benefit transaction information and the benefit data under the corresponding dark account; the target application comprises at least one third-party application, the target application and the system application are installed in the display device, and the system application is an application corresponding to the management server in the display device; the dark account is an account used to authenticate the access behavior initiated by the third-party application SDK in the system application by the corresponding application server, and the first open account cannot be directly authenticated by the application server; different dark accounts correspond to different third-party applications.

[0262] In an exemplary embodiment, the target application comprises at least two third-party applications, and the specified application is a third-party application.

[0263] Each module in the data display device described above can be implemented wholly or partially by software, hardware, and combinations thereof. Each module described above can be embedded in a processor in hardware form or independent of the processor in the computer device, or stored in a memory in the computer device in software form, so as to be called and executed by the processor to perform the operations corresponding to each module.

[0264] In an embodiment, a computer-readable storage medium is provided, and the computer-readable storage medium stores a computer program. The computer program is executed by a processor to implement the steps in each method embodiment described above.

[0265] In an embodiment, a computer program product is provided, and the computer program product includes a computer program. The computer program is executed by a processor to implement the steps in each method embodiment described above.

[0266] It should be noted that the user information (including but not limited to user account information, etc.) and data (including but not limited to benefit 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 related data need to comply with relevant regulations.

[0267] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer readable storage medium, and when executed, can include the processes of the above-mentioned embodiment methods. Any reference to memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. The non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical storage, 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. The volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration but not limitation, the RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The database involved in the embodiments provided in the present application can include at least one of a relational database and a non-relational database. The non-relational database can include a distributed database based on a block chain, etc., without being limited thereto. The processor involved in the embodiments provided in the present application can be a general-purpose processor, a central processing unit, a graphics processing unit, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., without being limited thereto.

[0268] The technical features of the above embodiments can be combined in any manner. To make the description concise, not all possible combinations of the technical features in the above embodiments are described, but as long as the combinations of the technical features do not exist contradictions, they should be considered as the scope of the present application.

[0269] The above-described embodiments are merely illustrative of several embodiments of the present application, and the description is relatively specific and detailed, but should not be understood as a limitation on the scope of the patent. It should be noted that for those skilled in the art, without departing from the concept of the present application, a number of modifications and improvements can be made, which are all within the scope of the present application. Therefore, the scope of protection of the present application should be subject to the appended claims.

Claims

1. A management server, characterized in that: include: a communication device configured to be communicatively connected to the display device and an application server corresponding to the target application; and at least one processor, connected to the communication device and configured to: receiving an equity transaction request for the target application; the equity transaction request carries equity transaction information and a first explicit account number of the system application; the target application includes at least one third-party application, the target application and the system application are both installed in a display device, and the system application is an application in the display device corresponding to the management server; Querying the dark account bound to the first visible account, and, if it is determined based on the rights transaction information that the current transaction involves mobile rights for at least two designated applications, querying the historical receipt of mobile rights for each designated application based on the first visible account; the dark account is used by the corresponding application server to authenticate access initiated by a third-party application software development kit (SDK) in the system application, and the first visible account cannot be directly authenticated by the application server; Different dark accounts correspond to different third-party applications; Determine the display order of mobile terminal benefit cards corresponding to different designated applications based on at least one of the transaction source, the historical claims corresponding to each designated application, and the application priority of each designated application; Controlling the application server to superimpose the display-end equity data corresponding to the equity transaction information with the equity data under the corresponding dark account to obtain the display-end equity transaction result; Sending transaction result data for the rights transaction request to the display device; the transaction result data includes the display-end rights transaction result, the display order between the mobile-end rights cards corresponding to different designated applications, and the card data of the mobile-end rights card corresponding to each designated application.

2. The management server according to claim 1, wherein: When the processor determines the display order of mobile terminal benefit cards corresponding to different designated applications based on at least one of the transaction source of the current transaction, the historical claim status corresponding to each designated application, and the application priority of each designated application, the processor is configured to: If the historical claims corresponding to each designated app are all claimed or unclaimed, the display order of the mobile rights cards corresponding to different designated apps will be determined based on the transaction source and / or the application priority of each designated app; When the historical receipt status corresponding to each designated application includes receipt corresponding to the first application and non-receipt corresponding to the second application, the mobile terminal rights and interests card corresponding to the second application is arranged before the mobile terminal rights and interests card corresponding to the first application, so as to obtain the display order between the mobile terminal rights and interests cards corresponding to different designated applications.

3. The management server according to claim 2, wherein: When the target applications include at least two third-party applications and the designated application is a third-party application, the processor is configured to perform any of the following when determining the display order of mobile terminal benefit cards corresponding to different designated applications based on the transaction source of the transaction and / or the application priority of each designated application: If the transaction source of this transaction is the application details page of any third-party application, the mobile terminal rights and interests cards corresponding to the remaining third-party applications are arranged after the mobile terminal rights and interests card corresponding to the third-party application to obtain the display order; the remaining third-party applications are third-party applications other than the third-party application among the at least two third-party applications; When the transaction source of this transaction is a non-target entry, the mobile terminal rights and interests card corresponding to the third-party application with a higher application priority is arranged before the mobile terminal rights and interests card corresponding to the third-party application with a lower application priority, so as to obtain the display order; The target entry is the application details page of any third-party application among at least two third-party applications.

4. The management server according to claim 2, wherein: When the control processor arranges the mobile terminal benefit card corresponding to the second application before the mobile terminal benefit card corresponding to the first application to obtain a display order between the mobile terminal benefit cards corresponding to different designated applications, the control processor is configured to: Determine the first order among the mobile terminal benefit cards corresponding to different first applications based on the transaction source of the current transaction and / or the application priorities of different first applications; Determine a second order among mobile terminal benefit cards corresponding to different second applications based on the transaction source of the current transaction and / or the application priorities of different second applications; The first order is spliced ​​after the second order to obtain the display order between mobile terminal rights cards corresponding to different designated applications.

5. The management server according to claim 1, wherein: When the target application includes at least two third-party applications and the designated application is a third-party application, the processor is configured to: For each third-party application, if the historical claim status corresponding to the third-party application is that the application has been claimed, read the second account number of the third-party application from the locally stored historical claim records; Sending a first transaction request to an application server corresponding to the third-party application; The first transaction request is used to instruct the application server to superimpose the display-end equity data corresponding to the target transaction information with the equity data under the dark account corresponding to the third-party application, and to superimpose the mobile-end equity data of the third-party application accompanying this transaction with the equity data under the second bright account; The target transaction information is the equity transaction information of the third-party application in the equity transaction information; Receive the equity transaction result sent by the application server; the equity transaction result includes the display end equity transaction result.

6. The management server according to claim 5, characterized in that The equity transaction result also includes a mobile terminal equity transaction result, and the processor is further configured to: For each third-party application, if the historical claim status corresponding to the third-party application is that the application has been claimed, determine the card data of the mobile terminal benefit card corresponding to the third-party application based on the mobile terminal benefit transaction result; For each third-party application, if the historical claim status corresponding to the third-party application is that the application has not been claimed, the card data of the mobile terminal rights card corresponding to the third-party application is determined according to the prompt claim information.

7. The management server according to any one of claims 1 to 6, characterized in that: When the equity transaction request is sent by a mobile terminal, the first clear account number is obtained by scanning the payment QR code presented in the system application by the mobile terminal; In the case where the equity transaction request is sent by a display device, the first account number is obtained by the display device according to a login operation on the system application.

8. A display device, characterized in that: include: Display and controller; The controller is configured to: Receive transaction result data sent by the management server; the transaction result data includes the display terminal rights transaction result, the display order between the mobile terminal rights cards corresponding to different designated applications, and the card data of the mobile terminal rights cards corresponding to each designated application; controlling the display to display the display-end benefit transaction result, and controlling the display to display each mobile-end benefit card according to the display order and the card data of the mobile-end benefit card corresponding to each designated application; the display order is determined by the management server based on at least one of the transaction source of the current transaction, the historical receipt of mobile-end benefits by each designated application, and the application priority of each designated application; The historical claim status of mobile terminal benefits for each designated application is obtained by querying the first account number of the system application carried in the benefit transaction request, when the management server determines, based on the benefit transaction information carried in the received benefit transaction request for the target application, that the current transaction involves mobile terminal benefits for at least two designated applications; The display terminal equity transaction result is obtained by the management server controlling the application server corresponding to the target application to superimpose the display terminal equity data corresponding to the equity transaction information with the equity data under the corresponding dark account; The target application includes at least one third-party application, the target application and the system application are both installed in the display device, and the system application is an application in the display device corresponding to the management server; The hidden account is an account used to enable the corresponding application server to authenticate access actions initiated by the third-party application SDK in the system application. The first visible account cannot be directly authenticated by the application server; Different dark accounts correspond to different third-party applications.

9. The display device according to claim 8, wherein The target applications include at least two third-party applications, and the designated application is a third-party application.

10. A data display method, characterized in that: Used for management servers, including: receiving an equity transaction request for a target application; the equity transaction request carries equity transaction information and a first explicit account number of a system application; the target application includes at least one third-party application, the target application and the system application are both installed in a display device, and the system application is an application in the display device corresponding to the management server; Querying the dark account bound to the first visible account, and, if it is determined based on the rights transaction information that the current transaction involves mobile rights for at least two designated applications, querying the historical receipt of mobile rights for each designated application based on the first visible account; the dark account is used by the corresponding application server to authenticate access initiated by the third-party application software development kit (SDK) in the system application, and the first visible account cannot be directly authenticated by the application server; different dark accounts correspond to different third-party applications; Determine the display order of mobile terminal benefit cards corresponding to different designated applications based on at least one of the transaction source of the current transaction, the historical claims corresponding to each designated application, and the application priority of each designated application; and Controlling the application server to superimpose the display-end equity data corresponding to the equity transaction information with the equity data under the corresponding dark account to obtain the display-end equity transaction result; Sending transaction result data for the rights transaction request to the display device; the transaction result data includes the display-end rights transaction result, the display order between the mobile-end rights cards corresponding to different designated applications, and the card data of the mobile-end rights card corresponding to each designated application.

Images