WO2024001255A1 - 一种用户设备及奖励权益数据处理方法 - Google Patents

一种用户设备及奖励权益数据处理方法 Download PDF

Info

Publication number
WO2024001255A1
WO2024001255A1 PCT/CN2023/078601 CN2023078601W WO2024001255A1 WO 2024001255 A1 WO2024001255 A1 WO 2024001255A1 CN 2023078601 W CN2023078601 W CN 2023078601W WO 2024001255 A1 WO2024001255 A1 WO 2024001255A1
Authority
WO
WIPO (PCT)
Prior art keywords
rights
server
request
account
platform
Prior art date
Application number
PCT/CN2023/078601
Other languages
English (en)
French (fr)
Inventor
李铁柱
魏茂泉
薛健
张云龙
刘希伟
Original Assignee
聚好看科技股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN202210742122.2A external-priority patent/CN116823341A/zh
Priority claimed from CN202210804638.5A external-priority patent/CN116801055A/zh
Application filed by 聚好看科技股份有限公司 filed Critical 聚好看科技股份有限公司
Publication of WO2024001255A1 publication Critical patent/WO2024001255A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising

Definitions

  • the present disclosure relates to the field of data processing technology, and in particular, to a user equipment and a reward rights data processing method.
  • the reward rights are limited rights (for example, there are 100 discount coupons in total, that is, only 100 users can obtain the rights)
  • the reward rights when the user logs in to the online platform account, the reward rights have been distributed, resulting in the user not getting the rights.
  • Reward benefits Therefore, it affects the efficiency of users in obtaining reward rights and interests, that is, the efficiency of users in obtaining reward rights and interests is low and the real-time performance is poor.
  • Some embodiments of the present disclosure provide a user equipment, including:
  • a display configured to display reward entitlements
  • Controller configured as:
  • a first claim request is generated according to the device identification of the user device, and the first claim request is sent to the first server; wherein, the The first claim request includes the device identifier; the first claim request is used to instruct the first server to bind the device identifier and reward rights to each other; the first platform account is the account of a platform that provides reward rights ;
  • a transition request is sent to the first server; wherein the transition request includes the first platform account and the device identification; the transition request is used to indicate the first
  • the server binds the reward rights and interests bound to the device identification and the first platform account to each other; the first prompt information indicates that the reward rights and interests are received successfully.
  • Some embodiments of the present disclosure also provide a method for processing reward rights data of user equipment, the method includes:
  • a first claim request is generated according to the device identification of the user device, and the first claim request is sent to the server; wherein, the first claim request Including the device identification; the first claim request is used to instruct the server to bind the device identification and reward rights to each other. Determined; the platform account mentioned is the account of the platform that provides reward rights;
  • a transition request is sent to the server; wherein the transition request includes the platform account and the device identification; the transition request is used to instruct the server to bind the device identification to the platform account. Certain reward rights and the platform account are bound to each other; the first prompt message indicates that the reward rights are successfully collected.
  • Figure 1 is a usage scenario of user equipment in some embodiments of the present disclosure
  • Figure 2 is a schematic structural diagram of user equipment in some embodiments of the present disclosure.
  • Figure 3 is a schematic diagram of the software architecture of user equipment in some embodiments of the present disclosure.
  • Figure 4 is one of the schematic interface diagrams of user equipment in some embodiments of the present disclosure.
  • Figure 5 is a schematic diagram of a user device logging into a first platform account in some embodiments of the present disclosure
  • Figure 6 is a schematic diagram of a partial interaction process between devices in some embodiments of the present disclosure.
  • Figure 7 is a schematic diagram of a display screen of user equipment in some embodiments of the present disclosure.
  • Figure 8 is a schematic diagram of the recharge page of user equipment in some embodiments of the present disclosure.
  • Figure 9 is a second schematic diagram of part of the interaction process between devices in some embodiments of the present disclosure.
  • Figure 10 is a schematic diagram of the payment page of a user device in some embodiments of the present disclosure.
  • Figure 11 is a schematic diagram of an interface for inputting a payment password on a user device in some embodiments of the present disclosure
  • Figure 12 is a schematic diagram of a transaction order of a user device in some embodiments of the present disclosure.
  • Figure 13 is the second schematic diagram of the interface of user equipment in some embodiments of the present disclosure.
  • Figure 14 is a schematic diagram of the QR code control of user equipment in some embodiments of the present disclosure.
  • Figure 15 is a schematic diagram of the payment page of the terminal device in some embodiments of the present disclosure.
  • Figure 16 is a schematic diagram of a video playback screen of a user device in some embodiments of the present disclosure.
  • Figure 17 is one of the partial flow diagrams of a reward equity data processing method in some embodiments of the present disclosure.
  • Figure 18 is a partial flowchart 2 of a method for processing reward equity data in some embodiments of the present disclosure.
  • the first server provided by the embodiment of the present disclosure performs data communication with the user equipment. Receive the transaction configuration information sent by the user device, and after generating each transaction based on the transaction configuration information, the user device obtains the transaction.
  • the user equipment may have various implementation forms, for example, it may be a smart TV, a mobile terminal, a notebook computer, a tablet computer (such as an iPad), etc.
  • Figures 1 and 2 show a specific implementation of the first server of the present disclosure.
  • Figure 1 is a schematic diagram of an operation scenario between a user equipment and a first server according to an embodiment of the present disclosure.
  • the user can perform data communication with the first server 200 through the user device 100 (such as a mobile terminal, a tablet computer, a computer, a notebook computer, a smart TV, etc.).
  • the user can also perform data communication with the user equipment 100 and the first server 200 through another mobile terminal 300 .
  • Figure 2 shows a schematic structural diagram of user equipment 100.
  • the following uses the user equipment 100 as an example to describe the embodiment in detail. It should be understood that the user equipment 100 shown in Figure 2 is only an example, and the user equipment 100 may have more or fewer components than shown in Figure 2, may combine two or more components, or Can have different component configurations.
  • the various components shown in the figures may be implemented in hardware, software, or a combination of hardware and software including one or more signal processing and/or application specific integrated circuits.
  • FIG. 2 schematically illustrates a hardware configuration block diagram of the user equipment 100 according to an exemplary embodiment.
  • user equipment 100 includes: radio frequency (radio frequency, RF) circuit 110, memory 120, display unit 130, camera 140, sensor 150, audio circuit 160, wireless fidelity (Wireless Fidelity, Wi-Fi) module 170, processor 180, Bluetooth module 181, power supply 190 and other components.
  • the RF circuit 110 can be used to receive and send signals during sending and receiving information or during calls. It can receive downlink data from the base station and then hand it over to the processor 180 for processing; it can send uplink data to the base station.
  • RF circuits include, but are not limited to, antennas, at least one amplifier, transceivers, couplers, low noise amplifiers, duplexers and other components.
  • Memory 120 may be used to store software programs and data.
  • the processor 180 executes software programs or data stored in the memory 120 to perform various functions and data processing of the user device 100 .
  • Memory 120 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.
  • the memory 120 stores an operating system that enables the user device 100 to run. In the present disclosure, the memory 120 can store the operating system and various application programs, and can also store codes for executing the methods described in the embodiments of the present disclosure.
  • the display unit 130 may be configured to receive input numeric or character information and generate signal input related to user settings and function control of the user device 100.
  • the display unit 130 may include a touch screen disposed on the front of the user device 100. 131, which can collect the user's touch operations on or near it, such as clicking buttons, dragging scroll boxes, etc.
  • the display unit 130 may also be used to display information input by the user or information provided to the user and a graphical user interface (GUI) of various menus of the user device 100 .
  • GUI graphical user interface
  • the display unit 130 may include a display screen 132 disposed on the front of the user device 100.
  • the display screen 132 can be configured in the form of a liquid crystal display, a light-emitting diode, etc.
  • the display unit 130 may be used to display various graphical user interfaces described in this disclosure.
  • the touch screen 131 can cover the display screen 132, or the touch screen 131 and the display screen 132 can be integrated to realize the input and output functions of the communication terminal 100. After integration, it can be referred to as a touch display screen.
  • the display unit 130 can display application programs and corresponding operation steps.
  • Camera 140 may be used to capture still images or video.
  • the object passes through the lens to produce an optical image that is projected onto the photosensitive element.
  • the photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor.
  • CMOS complementary metal-oxide-semiconductor
  • the photosensitive element converts the optical signal into an electrical signal, and then passes the electrical signal to the processor 180 for conversion into a digital image signal.
  • the user equipment 100 may also include at least one sensor 150, such as an acceleration sensor 151, a distance sensor 152, a fingerprint sensor 153, and a temperature sensor 154.
  • the user equipment 100 may also be configured with other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, a light sensor, a motion sensor, and the like.
  • the audio circuit 160, the speaker 161, and the microphone 162 may provide an audio interface between the user and the user device 100.
  • the audio circuit 160 can transmit the electrical signal converted from the received audio data to the speaker 161, and the speaker 161 Convert to sound signal output.
  • the communication terminal 100 may also be configured with a volume button for adjusting the volume of the sound signal.
  • the microphone 162 converts the collected sound signal into an electrical signal, which is received by the audio circuit 160 and converted into audio data, and then outputs the audio data to the RF circuit 110 for sending to, for example, another terminal, or outputs the audio data to memory 120 for further processing.
  • Microphone 162 in this disclosure can capture the user's voice.
  • Wi-Fi is a short-distance wireless transmission technology.
  • the user equipment 100 can use the Wi-Fi module 170 to help users send and receive emails, browse web pages, trade configuration information, and access streaming media. It provides users with wireless broadband Internet access.
  • the processor 180 is the control center of the user equipment 100. It uses various interfaces and lines to connect various parts of the entire equipment, and executes the user equipment by running or executing software programs stored in the memory 120 and calling data stored in the memory 120. 100's of various functions and processing data.
  • the processor 180 may include one or more processing units; the processor 180 may also integrate an application processor and a baseband processor, where the application processor mainly processes the operating system, user interface, application programs, etc. , the baseband processor mainly handles wireless communications. It can be understood that the above-mentioned baseband processor may not be integrated into the processor 180 .
  • the processor 180 can run an operating system, application programs, user interface display and touch response, as well as the processing method described in the embodiments of the present disclosure.
  • the processor 180 is coupled with the input unit 130 and the display unit 140.
  • the Bluetooth module 181 is used to interact with other Bluetooth devices having Bluetooth modules through the Bluetooth protocol.
  • the user equipment 100 can establish a Bluetooth connection with a wearable electronic device (such as a smart watch) that also has a Bluetooth module through the Bluetooth module 181 to perform data exchange.
  • a wearable electronic device such as a smart watch
  • User equipment 100 also includes a power source 190 (such as a battery) that powers various components.
  • the power supply can be logically connected to the processor 180 through the power management system, so that functions such as charging, discharging, and power consumption can be managed through the power management system.
  • the user device 100 may also be configured with a power button for turning on and off the device, as well as locking the screen and other functions.
  • Figure 3 is a software structure block diagram of user equipment 100 according to an embodiment of the present invention.
  • the Android system is divided into four layers. From top to bottom, they are the application layer, the application framework layer, the system library of the Android runtime (Android runtime), and the kernel layer.
  • the application package can include camera, gallery, calendar, call, WeChat, Alipay, map, navigation, WLAN, Bluetooth, music, video, short message and other applications.
  • the application framework layer provides an application programming interface (API) and programming framework for applications in the application layer.
  • API application programming interface
  • the application framework layer includes some predefined functions.
  • the application framework layer can include window manager, content provider, view system, phone manager, resource manager, notification manager, etc.
  • a window manager is used to manage window programs.
  • the window manager can obtain the display size, determine whether there is a status bar, lock the screen, capture the screen, etc.
  • Content providers are used to store and retrieve data and make this data accessible to applications.
  • Said data can include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.
  • the view system includes visual controls, such as controls that display text, controls that display pictures, etc.
  • a view system can be used to build applications.
  • the display interface can be composed of one or more views.
  • a display interface including a text message notification icon may include a view for displaying text and a view for displaying pictures.
  • the phone manager is used to provide communication functions of user equipment 100. For example, call status management (including connected, hung up, etc.).
  • the resource manager provides various resources to applications, such as localized strings, icons, pictures, layout files, video files etc.
  • the notification manager allows applications to display notification information in the status bar, which can be used to convey notification-type messages and can automatically disappear after a short stay without user interaction.
  • the notification manager is used to notify download completion, message reminders, etc.
  • the notification manager can also be notifications that appear in the status bar at the top of the system in the form of charts or scroll bar text, such as notifications for applications running in the background, or notifications that appear on the screen in the form of conversation windows. For example, text information is prompted in the status bar, a prompt sound is emitted, the terminal device vibrates, and the indicator light flashes, etc.
  • the system libraries in Android runtime state include core libraries and virtual machines.
  • the Android runtime state system library is responsible for the scheduling and management of the Android system.
  • the core library contains two parts: one is the functional functions that need to be called by the Java language, and the other is the core library of Android.
  • the application layer and application framework layer run in virtual machines.
  • the virtual machine executes the java files of the application layer and application framework layer into binary files.
  • the virtual machine is used to perform object life cycle management, stack management, thread management, security and exception management, and garbage collection and other functions.
  • System libraries can include multiple functional modules. For example: surface manager (surface manager), media libraries (Media Libraries), 3D graphics processing libraries (for example: OpenGL ES), 2D graphics engines (for example: SGL), etc.
  • the surface manager is used to manage the display subsystem and provides the fusion of 2D and 3D layers for multiple applications.
  • the media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc.
  • the media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.
  • the 3D graphics processing library is used to implement 3D graphics drawing, image rendering, composition, and layer processing.
  • 2D Graphics Engine is a drawing engine for 2D drawing.
  • the kernel layer is the layer between hardware and software.
  • the kernel layer contains at least display driver, camera driver, audio driver, and sensor driver.
  • Figure 4 is a schematic diagram illustrating a user interface on a user device.
  • the user can open the corresponding application (such as shopping) by clicking (including touching a user device with a touch function and clicking on a connected peripheral input device) an application icon on the user interface. platform, video playback platform, etc.), or perform the corresponding operation by touching the operation icon on the user interface.
  • the user clicks the "Video” icon to open a video playback platform such as the Juhaokan platform
  • the user clicks the "Shopping" icon to open a shopping platform (such as a certain online mall).
  • users can conduct online transactions through the network platform corresponding to the application program in the user device 100; online transactions refer to transactions conducted on the virtual environment of the network, such as purchasing food and clothing on the network platform. Commodities, electronic equipment, activation of virtual rights (such as rights to watch paid videos provided by online video platforms), etc.
  • the following exemplifies the workflow of online transactions between the user device 100 and the first server 200 in conjunction with the online purchase of clothing products.
  • the user opens the shopping platform through the "shopping" icon in the user interface of the user device 100, and logs in to the user's first platform account on the shopping platform, then selects clothing products (such as clothes, pants, shoes, etc.) on the shopping platform, and finally The transaction amount is calculated, a payment request is initiated through the user device 100, and the payment request is sent to the first server 200.
  • “shopping" icon in the user interface of the user device 100
  • clothing products such as clothes, pants, shoes, etc.
  • the first server 200 feeds back the password input page according to the payment method selected by the user device 100, and generates a transaction order after determining that the user's password input is successful.
  • the transaction order includes transaction amount, transaction list and other information; for example, clothing Service manufacturer, consignee information, price (such as 200 yuan), quantity, and other information.
  • the transaction amount is obtained by calculating the difference between the total amount of purchased goods and the reward rights in the user account.
  • the purchased goods include a piece of clothing and a pair of pants; among them, the price of the clothing is 200 yuan and the price of the pants is 300 yuan, then the total amount of the purchased goods is 500 yuan.
  • the user account has a 50 yuan coupon (a type of reward benefit), so the transaction amount is calculated to be 450 yuan.
  • the user when a user obtains the reward rights issued by the shopping platform, the user needs to first log in to the first platform account on the shopping platform, and then request the reward rights in the first server 200 .
  • the first server 200 will bind the reward rights and the first platform account to each other, so that the user can use the reward rights when calculating the transaction amount.
  • a shopping platform issues a 10% off shopping coupon (a type of reward right); after the user logs in to the first platform account on the shopping platform, the user sends a request for a 10% off shopping coupon to the first server 200 .
  • the first server 200 determines that the first platform account is a first platform account that is allowed to receive reward rights and interests, it binds the first platform account and the reward rights and interests, generates a claim record, and stores the claim record.
  • the user device 100 accesses the stored claim record from the first server according to the first platform account, obtains the claim record corresponding to the first platform account, and then obtains the reward rights corresponding to the first platform account.
  • the reward rights issued by a platform that provides reward rights are limited; for example, the shopping platform issues 100 10% off coupons during a certain festival for different purposes. users to receive it. In other words, only 100 users can receive the “10% off coupon”.
  • the status on the user device 100 generally includes the following two situations: the user device 100 has logged in the user's first platform account, and the user device 100 has not logged in the user's first platform account. Platform account.
  • FIG. 5 is a schematic diagram of logging in to the first platform account in some embodiments of the present disclosure. As shown in Figure 5, when the user device is not logged in to the user's first platform account, it sends a login prompt and logs in. The prompt is used to indicate the need to log in to the first platform account; as shown in Figure 5, the user is required to enter a mobile phone number and mobile phone verification code.
  • Figure 6 illustrates an exemplary reward rights data processing method in some embodiments of the present disclosure. As shown in Figure 6, this method can Applied to the first server 200 capable of implementing the reward equity data processing method.
  • the specific contents are as follows:
  • the first server 200 receives the first collection request sent by the user equipment 100; wherein the first collection request includes the device identification of the user equipment 100.
  • the device identifier is a unique identifier; for example, the device identifier of the user equipment is an International Mobile Equipment Identity (IMEI), such as the IMEI is "8612***0344".
  • IMEI International Mobile Equipment Identity
  • the first collection request is generated based on the device identification when the user device 100 determines that it is not logged in to the first platform account. For example, when the user uses the user device 100 to obtain bonus rights, the user device 100 determines that the user is not logged in to the shopping platform.
  • the first platform account will generate the first claim request based on its own IMEI.
  • the first platform account is the account of the platform that provides reward rights; the first platform account is the user's identity document (ID).
  • ID the user's identity document
  • the first platform account is the user's mobile phone number, ID number, etc.
  • the first server 200 After obtaining the first claim request and before binding the device identification and the reward rights to each other, the first server 200 determines whether the device identification in the first claim request supports the claim of the reward rights, thereby ensuring the legitimacy of the issuance of the reward rights.
  • whether the device identification supports receiving reward rights is determined by determining whether the device identification is recorded in the blacklist.
  • the blacklist refers to the list of dishonest persons and is used to record information such as device identification and first platform account numbers that are prohibited from receiving reward rights.
  • the device identifier if it is determined that the device identifier is recorded in the blacklist, it is determined that the device identifier does not support receiving reward rights; if it is determined that the device identifier is not recorded in the blacklist, it is determined that the device identifier supports receiving reward rights. For example, if the blacklist record contains device identifiers a1 and a2, then device identifiers a1 and a2 are prohibited from receiving reward rights. That is, the user cannot receive the reward rights through the user device with the device identification a1 or a2; the user can receive the reward rights through the user device with the device identification a3 (other device identification than a1 and a2).
  • the device identification in order to prevent users from repeatedly claiming reward rights and interests through the user device 100, it is determined whether the device identification supports receiving reward rights and interests by determining whether the device identification has been bound to the reward rights and interests. For example, when it is determined that device identifier a3 is not recorded in the blacklist, if it is determined that device identifier a3 has been bound to the reward rights of "10% off coupon", it is determined that device identifier a3 does not support receiving reward rights; if it is determined that device identifier a3 is not If the reward rights and interests of "10% off coupon" are bound, it is determined that the device identification a3 supports receiving the reward rights and interests.
  • whether the device identification supports receiving reward rights is determined by determining whether the device identification has been bound to the same reward rights. For example, assuming that the reward rights include “20% off coupon” and "10% off coupon", device identification a3 is not recorded in the blacklist; if device identification a3 has been bound to the reward rights of "10% off coupon", it has not been bound to "10% off coupon”. If you want to receive the reward rights of "20% off coupon”, it is determined that the device identification a3 supports receiving the reward rights of "20% off coupon”, but does not support receiving the reward rights of "10% off coupon”.
  • whether the device identification supports receiving reward rights can also be determined based on the number of the same reward rights bound to the device identification. For example, assuming that the threshold for claiming reward rights is 3 and device identifier a3 is not recorded in the blacklist, that is, device identifier a3 can be bound to up to 3 reward rights; if device identifier a3 has been bound to 3 reward rights, it is determined that device identifier a3 is not Supports receiving reward rights.
  • judgment conditions for determining whether the device identification supports receiving reward rights is only an example and does not limit the judgment conditions.
  • the first server 200 After determining that the device identification supports receiving the reward rights and interests, the first server 200 binds the device identification and the reward rights and interests to each other, generates the device reward rights and interests, and stores the device reward rights and interests in the database and/or its own storage module.
  • the device identifier is "a4" and the reward benefit is "10% off coupon”. After binding "a4" with “10% off coupon”, the device reward benefit "a4-10% off coupon” is generated.
  • the reward rights and interests can be represented by rights identifiers.
  • the rights and interests identifier of "10% off coupon” is c9
  • the device reward rights and interests are "a4-c9”.
  • the device reward rights and interests may also include quantity information of the reward rights and interests, for example, the device reward rights and interests are "a4-c9(2)", and "(2)" means that the user equipment with the device identification of "a4" is claimed. There are two “10% off coupons”.
  • the first server 200 When the first server 200 generates device reward rights, it indicates that the user device 100 has received the reward rights. Then the first server 200 sends prompt information to the user device 100, and the prompt information is used to indicate success or failure in claiming the reward rights.
  • the first server 200 generates a device reward according to the device identification of the user device 100 After receiving the rights and interests, the first prompt information is sent to the user device 100; wherein the first prompt information is used to indicate that the reward rights and interests are successfully claimed; in some embodiments of the present disclosure, the first server 200 does not generate a device reward based on the device identification of the user device 100 After the reward rights are obtained, the second prompt information is sent to the user device 100; wherein the second prompt information is used to indicate failure to claim the reward rights.
  • the first server 200 determines whether the device identification in the first claim request supports receiving reward rights and interests (the relevant content of determining whether the device identification supports receiving reward rights and interests has been described above and will not be discussed here. (no more details).
  • the first server 200 determines that the device identification supports receiving reward rights and interests, it will generate the device reward rights and interests and send the first prompt message to the user device 100; if the first server 200 determines that the device identification does not support receiving the reward rights and interests, it will send the first prompt message to the user device 100. 2. Prompt information.
  • the second prompt information includes the reason for the failure, such as the device identification being added to the blacklist, the device identification having received reward rights, the number of reward rights being insufficient, etc.
  • the user equipment 100 After receiving the first prompt information, the user equipment 100 displays the first prompt information to let the user know that the reward rights have been successfully claimed.
  • the user uses or views the operation of reward rights and interests, he will log in to the first platform account on the platform on the user device 100; where the platform is a platform that provides reward rights and interests, and the first platform account is the account of the platform, which is used to indicate that the user is on the platform. The identity of the platform.
  • the first server 200 does not send prompt information to the user device 100, and the user device queries the first server 200 through the data access interface whether to generate device reward rights. For example, after sending the first claim request 1s to the first server 100, the user device 100 performs data communication with the first server 200 through the data access interface opened by the first server 200, thereby querying whether the first server 200 generates device reward rights. .
  • the user device 100 After determining that the first server 200 generates device reward rights and the user logs in to the first platform account, the user device 100 sends a transition request to the first server 200 to instruct the first server 200 to bind the reward rights and the first platform account to each other.
  • the transition request includes the first platform account and device identification.
  • the first server 200 determines whether the first platform account in the transition request supports receiving rewards before binding the reward rights bound to the device identification and the first platform account to each other. Rights and interests; if it is determined that the first platform account supports receiving reward rights and interests, the account reward rights and interests will be generated based on the device reward rights and interests.
  • whether the device identification supports receiving reward rights is determined by determining whether the first platform account is recorded in the blacklist. Based on the above description of determining whether the device identification supports receiving reward rights and interests, if it is judged that the first platform account is recorded in the blacklist, it is determined that the first platform account does not support receiving reward rights and interests; if it is judged that the first platform account is not recorded in the blacklist, then it is determined The first platform account supports receiving reward rights.
  • the first platform accounts b1 and b2 are recorded in the blacklist, it means that the first platform accounts b1 and b2 are prohibited from receiving reward rights. That is, the user cannot receive the reward rights and interests by using the user device logged in with the first platform account b1 or b2; the user can receive the reward rights and interests by using the user device logged in with the first platform account b3 (other first platform accounts other than b1 and b2).
  • the first platform account in order to prevent users from repeatedly receiving reward rights and interests through the user device 100, it is determined whether the first platform account supports receiving reward rights and interests by determining whether the first platform account has been bound to reward rights and interests. In other embodiments of the present disclosure, it is determined whether the first platform account supports receiving reward rights by determining whether the first platform account has been bound to the same reward rights. In some embodiments of the present disclosure, whether the first platform account supports receiving reward rights can also be determined based on the number of the same reward rights bound to the first platform account.
  • judgment conditions for judging whether the first platform account supports receiving reward rights can be the same as the judgment equipment.
  • the conditions for judging whether the logo supports receiving reward rights are the same conditions, and can be different conditions, which will not be described or limited here.
  • the first server 200 queries the database or storage module according to the device identification of the user device 100 whether the user device 100 has device reward rights and interests.
  • the first server 200 determines that the user device 100 has device reward rights, it unbinds the device identification and reward rights in the device reward rights. Then the first platform account and reward rights are bound to each other to generate account reward rights. Based on the above description, for example, the equipment reward rights are "a4-c9"; unbind the device identification "a4" in “a4-c9” from the reward rights "c9", and unbind the first platform account "b3" from the reward rights "c9" are bound to each other to generate account reward rights "b3-c9".
  • the first server can first realize the reward rights and interests based on the device identification, so as to avoid the situation of not receiving the reward rights and interests due to the inability to receive the reward rights and interests during the process of logging in to the account; Improvement This ensures the real-time and efficiency of receiving reward rights.
  • the reward rights and interests received by the device identification are transferred to the first platform account, which ensures that the reward rights and interests are used under the first platform account and ensures the legality and accuracy of the use of reward rights and interests.
  • the first server 200 after the first server 200 generates account reward rights based on the first platform account, it sends the first prompt information to the user device 100; in some embodiments, the first server 200 does not generate the account reward rights based on the first platform account. After the account is rewarded with benefits, the second prompt information is sent to the user device 100 .
  • the first server 200 determines whether the first platform account in the transition request supports receiving reward rights and interests (the content of determining whether the first platform account supports receiving reward rights and interests has been described above and will not be repeated here. ).
  • the first server 200 determines that the first platform account supports receiving reward rights, it will generate the account reward rights and send the first prompt message to the user device 100; if the first server 200 determines that the first platform account does not support receiving reward rights, it will send the user The device 100 sends the second prompt information.
  • the second prompt information includes the reason for the failure, such as the first platform account being added to the blacklist, the first platform account having received reward rights, the number of reward rights being insufficient, etc.
  • the first server 200 receives the second collection request sent by the user device 100; wherein the second collection request includes the user's first platform account.
  • the second collection request is generated based on the user's first platform account when the user device 100 determines that the first platform account has been logged in. For example, when the user uses the user device 100 to obtain bonus rights, the user device 100 determines that the shopping platform has logged into the user's first platform account, and then generates a second claim request based on the user's first platform account.
  • the first server 200 determines whether the first platform account supports receiving reward rights and interests (the content of determining whether the first platform account supports receiving reward rights and interests has been described above and will not be repeated here). When it is determined that the first platform account supports receiving reward rights and interests, the first platform account is bound to the reward rights and interests to generate account reward rights and interests. When it is determined that the first platform account does not support receiving reward rights, second prompt information is fed back to the user device 100 .
  • the network platform generally provides users with experience services before the electronic transaction.
  • the video playback platform is used to provide and play video data.
  • the video data includes free videos and paid videos.
  • free videos refer to videos that can be watched without paying
  • paid videos refer to videos that are only allowed to be viewed after paying for the playback rights of the video.
  • Paid videos provide free viewing segments; among them, the free viewing segments can be any of the paid videos part.
  • the duration of a paid video is 1 hour and 50 minutes
  • the free viewing segment is the first 6 minutes of the paid video (that is, the video segment from 0:00:00 to 0:06:00). So for users, when watching a paid video, they can first play the free viewing clip corresponding to the paid video to experience it, and then decide whether to purchase relevant playback rights for the paid video to watch the entire content after watching the free viewing clip.
  • the video playback platform generally has a membership mechanism.
  • Video members can play paid videos on the video playback platform and skip advertisements played before the video playback; non-video members cannot play paid videos on the video playback platform.
  • the platform account is a video member account of the video platform, when users use the platform account to watch videos, they can watch paid videos and skip the advertisements played before the video is played.
  • FIG. 7 is a schematic diagram of a display screen of a user device exemplarily shown in some disclosed embodiments; as shown in Figure 7, after the free viewing clip is played, the payment control jumps out to instruct the user to recharge the membership, and then obtain Playback rights enable the playback of paid videos.
  • FIG 8 is a schematic diagram of a recharge page exemplarily shown in some embodiments of the present disclosure.
  • the recharge details page includes multiple recharge options, such as 1 month, 2 months, 3 months, 6 months Monthly and other recharge options, after the user selects one of the recharge options, the user device 100 will jump to the payment screen.
  • the payment screen may be a QR code screen. After the user scans the QR code through the terminal device 300, the payment is made on the terminal device 300, and a payment order is generated based on the platform account number, video identification and other information. .
  • the terminal device 300 after the terminal device 300 generates the payment order, it sends the payment order to the server. Then the server generates and sends a playback rights activation request to the corresponding second platform account according to the payment order to activate the playback rights for the second platform account.
  • the second platform account mentioned above and below can be the first platform account mentioned above, that is, the first platform account/second platform account can be used to purchase physical items on the online platform. Commodities can also be used to purchase video playback rights on an online platform. Then the reward rights corresponding to the video playback rights can be issued through the content described above; the second platform account described above and below can also be A platform account that is different from the first platform account mentioned above; there are no too many limitations here.
  • the server asynchronously executes the following two processes: one is to return the payment result to the user device after determining that the payment order is successfully paid; the other is to activate the playback rights for the second platform account. After receiving the payment result, the user device 100 refreshes the second platform account and plays the paid video.
  • the platform account playback rights are not successfully activated, which results in the user device 100 still being unable to play the paid playback after refreshing the second platform account (that is, when using the playback rights).
  • Video that is, the activation of playback rights was not successful
  • the user device refreshes the platform account more than 100 times there is still a situation where paid videos cannot be played, resulting in a low accuracy in the use of playback rights and a waste of refreshing the second platform account
  • the user needs to jump to the display screen multiple times to purchase the playback rights. In other words, the steps for users to purchase broadcast rights are complicated, which affects the efficiency of activation of broadcast rights.
  • Figure 9 illustrates an exemplary method for solving the above problems in some embodiments of the present disclosure.
  • the first server used to provide reward rights issuance and the server corresponding to the video playback platform used to provide video playback rights can be the same server, or they can be different servers.
  • the following will mainly use The description is given as an example in which the server that provides bonus rights issuance and the server that provides video playback rights corresponding to the video playback platform are the same first server 200 .
  • the specific content is as follows:
  • the payment order includes the second platform account and the broadcast rights indicating the opening of the second platform account.
  • the graphic code is when the user equipment 100 sends a video data request instruction to the first server 200 after receiving the playback instruction triggered by the user, so as to receive the video data and rights configuration information fed back by the first server 200 based on the video data request instruction, so that the user can
  • the device 100 generates the rights configuration information when it determines that the second platform account does not have the rights to play.
  • the video data request instruction includes the second platform account logged in on the video playback platform.
  • the mobile terminal 300 requests the third platform based on its own terminal identification, the device identification of the user device 100, the second platform account number, the QR code identification, the order number of the payment order, and other information.
  • An interface corresponding to the server 200 obtains the payment page.
  • the mobile terminal 300 places an order in the first server 200 based on the information on the payment page, and the first server 200 returns the order number and payment address (such as WX Payment Application address, ZFB payment application address, bank card, etc.) and other information for users to make payments.
  • the mobile terminal 300 After the user successfully pays, the mobile terminal 300 generates a payment order and sends the payment order to the first server 200 .
  • the graphic code includes a first QR code control and a second QR code control;
  • the payment order includes a first order corresponding to the first QR code and a second order corresponding to the second QR code.
  • the first server 200 When receiving the first order and/or the second order, the first server 200 sends a activation request to the third-party server 400 based on the first order and/or the second order.
  • the activation request is used to instruct the third-party server 400 to activate playback rights for the third-party account corresponding to the second platform account.
  • the scheduled task is started at the same time.
  • the first server 200 sends an activation request to the third-party server 400
  • it sends a kafka message to the timing component; where the kafka message includes the order number of the payment order.
  • Timing components are used for timing.
  • the first server 200 after receiving the feedback message from the third-party server 400 based on the activation request, the first server 200 sends a task cancellation instruction to the timing component to cancel the timing task.
  • timing component receives the task cancellation instruction within the second time period, it means that the first server 200 receives the feedback message based on the activation request from the third-party server 400 within the preset second time period, and then cancels the timed task. And the first server 200 will send the second instruction to the user device 100.
  • the timing component If the timing component does not receive the task cancellation instruction within the second time period, it sends timeout information to the first server 200 . After receiving the timeout information, indicating that the first server 200 has not received a feedback message based on the activation request from the third-party server 400 within the preset second time period, the first server 200 sends a first instruction to the user equipment 100 .
  • the first instruction is used to instruct the user device 100 to suspend the refresh, and after a preset first period of time, re-log in to the second platform account of the video playback platform, and send a refresh request to the third-party server 400; wherein, re-log in The method of creating a second platform account will be described below.
  • the method can be applied to user equipment that can implement the reward equity data processing method.
  • the specific contents are as follows:
  • the rights claim instruction is triggered by the user on a platform that provides reward rights;
  • Figure 10 is a schematic diagram of a reward rights exemplarily shown in some embodiments of the present disclosure.
  • the reward rights are "10% off discount” Coupon" is displayed on the interface of the shopping platform.
  • the shopping platform is a platform that provides reward rights;
  • the rights collection instruction is "receive". In other words, when the user clicks on the "Receive” control, the rights claim instruction is triggered.
  • the user equipment 100 After receiving the rights claiming instruction, the user equipment 100 determines whether the shopping platform has logged in to the first platform account in response to the rights claiming instructions.
  • the user device 100 determines that the first platform account is not logged in, the user device 100 generates a first collection request according to the device identification of the terminal device, and sends the first collection request to the first server 200; wherein the first collection request is used to instruct the first server Bind the device identification with the reward rights and interests to generate the device reward rights and interests.
  • the user device 100 receives the rights claiming instruction of "10% off coupon" triggered by the user on the shopping platform, and then determines whether the user's first platform account is logged in to the shopping platform. If so, generates the first platform account according to its own device identification. Get the request, and send the first get request to the first server 200.
  • the user equipment 100 After the user equipment 100 sends the first collection request to the first server 200, it receives prompt information fed back by the first server 200 based on the first collection request; wherein the prompt information includes the first prompt information and the second prompt information; the first prompt information It indicates that the reward rights and interests have been collected successfully; the second prompt message indicates that the reward rights and interests have failed to be collected.
  • the prompt information received by the user equipment 100 is the first prompt information, it means that the user equipment 100 has received the reward rights and will be displayed to the user to make the user aware.
  • the user device 100 sends a login prompt to the user, as shown in Figure 5 above, to prompt the user to log in to the first platform account before allowing the user to use the reward rights.
  • Rights to operate (such as using or viewing reward rights, etc.).
  • the user device 100 After the user logs in to the first platform account, the user device 100 generates a transition request according to the first platform account and sends the transition request to the first server 200; where the transition request is used to instruct the first server 200 to modify the device reward rights. Bonus benefits for the account.
  • the user equipment 100 After sending the transition request to the first server 200, the user equipment 100 receives the prompt information fed back by the first server 200 based on the transition request, and displays the prompt information to the user, so that the user knows whether the reward rights have been successfully received.
  • the user device 100 when the user device 100 determines that the first platform account has been logged in, the user device 100 generates a second collection request based on the first platform account, and sends the second collection request to the first server 200; wherein, the second collection request The request is used to instruct the first server 200 to bind the first platform account with reward rights and generate account reward rights.
  • the user equipment 100 if the user equipment 100 receives the prompt information fed back by the first server 200 based on the first collection request as the second prompt information, then after determining to log in to the first platform account, the user device 100 sends the second prompt information to the first server 200. Pick up the request. This avoids failure to claim reward rights due to the fact that the device identification does not support receiving reward rights, but the first platform account supports receiving reward rights, and improves the flexibility and accuracy of receiving reward rights.
  • the user can trigger the usage instruction in the shopping platform interface on the user device 100 . For example, when a user submits a transaction request, the user uses the reward equity to calculate the transaction amount of the transaction request.
  • the user device 100 calculates the transaction amount of the transaction request, and initiates a payment password input interface for receiving the receiving password input by the user;
  • Figure 11 is exemplarily shown in some embodiments of the present disclosure.
  • FIG 12 is a schematic diagram of a transaction order exemplarily shown in some embodiments of the present disclosure.
  • the payment order includes order status (such as processing, that is, payment process; processing completed, that is, payment completed; processing Failure, that is, processing failure, etc.), order information (such as monthly purchase of movie and TV memberships, purchase of jackets of a certain brand, etc.)
  • order status such as processing, that is, payment process; processing completed, that is, payment completed; processing Failure, that is, processing failure, etc.
  • order information such as monthly purchase of movie and TV memberships, purchase of jackets of a certain brand, etc.
  • the user equipment 100 When the user device 100 is used by the user to play videos, after the user uses the terminal device 300 to generate a payment order and sends it to the server, but fails to successfully open a second platform account for playback rights, the user device 100 refreshes the platform account multiple times and still fails. There is a situation where paid videos cannot be played, resulting in a low accuracy in the use of playback rights, a waste of communication resources, computing resources, etc. required to refresh the second platform account, and affecting the user's video viewing experience. In this issue, In some disclosed embodiments, the user equipment 100 also includes the following content:
  • a video playback platform such as the Juhaokan platform
  • Multiple video resources are displayed on the video playback platform, such as movie A1, TV series A2, etc.
  • the playback instruction is triggered.
  • a video data request instruction is sent to the second server to receive video data and rights configuration information fed back by the second server based on the video data request instruction.
  • the video data request instruction includes the second platform account logged in on the video playback platform.
  • the second server is the third-party server 400 corresponding to the third-party video playback platform; that is, the playback data corresponding to the playback instructions is stored in the third-party server.
  • the configuration information is generated by the third-party server based on the correspondence between the second platform account and the third-party account of the third-party server and the equity information of the third-party account; that is, the third-party server 400
  • the corresponding relationship between the second platform account and the third-party account is recorded in it (for example, the second platform account a1 and the third-party account b1 are in a one-to-one correspondence, and the second platform account a2 and the third-party account b2 are in a one-to-one correspondence. relationship, etc.), generate equity configuration information based on the equity information of the third-party account and the corresponding relationship between the second platform account and the third-party account.
  • the equity configuration information is a1-b1-0; among them, "0" is the equity information of the third-party account "b1", which means that the third-party account "b1" does not have the rights to play.
  • the user equipment 100 determines that the rights configuration information represents whether the second platform account has broadcast rights. Because the equity configuration information records the corresponding relationship between the second platform account and the third-party account as well as the equity information of the third-party account, it is determined based on the equity information of the third-party account whether the second platform account corresponding to the third-party account has playback rights. .
  • the equity configuration information when the equity information of the third-party account does not have playback equity, based on the corresponding relationship between the second platform account and the third-party account, the second platform corresponding to the third-party account is represented.
  • Platform accounts do not have broadcast rights.
  • the equity configuration information is a1-b1-0; because the third-party account "b1" does not have the rights to play, it is determined that the second platform account "a1" corresponding to the third-party account "b1" does not have the rights to play.
  • the rights information of the third-party account When the rights information of the third-party account has the playback rights, based on the corresponding relationship between the second platform account and the third-party account, it indicates that the second platform account has the playback rights.
  • the equity allocation information is a2-b2-1; among them, "1"
  • the rights information of the third-party account "b2” which means that the third-party account "b2" has the rights to play. Because the third-party account "b2" has the right to play, it is determined that the second platform account "a2" corresponding to the third-party account "b2" has the right to play.
  • the user equipment 100 determines that the rights configuration information indicates that the second platform account does not have broadcast rights, it generates an image code.
  • graphics codes are generated according to the playback duration of the video data; if it is determined that the playback duration of the video data reaches the preset duration, the graphics code is generated; if it is determined that the playback duration of the video data does not reach the preset duration, then the graphics code is not generated. Generate graphics code.
  • the user device 100 will play the video data.
  • the user equipment 100 plays the video data in full screen.
  • the video data includes free viewing clips.
  • the free viewing clips can still be played.
  • the first 6 minutes of video data are free to watch clips. If it is determined that the playback time of the paid video reaches the preset time, the graphic code will be generated based on the second platform account, the logo of the paid video and the logo of the display device; if it is determined that the playback time of the paid video does not reach the preset time, no graphic code will be generated. .
  • the default duration is 3 minutes.
  • a graphic code is generated based on the second platform account, the logo of the paid video, and the logo of the user's device to prompt the user to purchase the playback rights.
  • the free viewing clip is played to the 2nd minute (that is, when it is not played to 3 minutes)
  • no graphic code is generated. This not only ensures that the user's viewing of the free viewing clips within the preset time period is not affected, but also ensures that the user is prompted to purchase playback rights before the free viewing clips end, preventing the real-time playback of the clips after the free viewing clips from being low.
  • the default duration is shorter than the duration of free viewing clips.
  • the free viewing clip is 6 minutes
  • the preset duration can be 3, 4 minutes, etc., or it can be a value preset based on experience, such as 1 minute, etc., which is not limited here.
  • the graphic code is generated based on a combination of one or more of the following information.
  • the information includes but is not limited to: the second platform account logged in on the video playback platform (the second platform account is the user’s identification number), the identification of the video data (such as the classification identification of the video data, the location of the video data in the video playback platform) area identification, etc.) and the device identification of the user equipment 100.
  • the graphic code includes a first QR code control and/or a second QR code control.
  • the first QR code control represents the QR code for activating the membership rights of the video playback platform;
  • the second QR code control represents the QR code for activating the rights for complete playback of video data.
  • Figure 14 is a schematic diagram of a QR code control exemplarily shown in some embodiments of the present disclosure.
  • a first QR code control and a second QR code control are displayed on the user device 100; wherein, The first QR code control is generated by the user device 100 based on the second platform account and device identification, and is used to represent the membership rights of the video playback platform; the second QR code control is generated by the user equipment 100 based on the identification of the paid video, the second Generated from the platform account and device identification, it is used to indicate the rights to activate the complete playback of the video data.
  • the user can use the terminal device 300 to scan the first QR code control, and after successful payment, purchase the membership rights of the video playback platform, so that the user device 100 can play all video data in the video playback platform.
  • the user can use the terminal device 300 to scan the second QR code control, and after the payment is successful, purchase the rights for the complete playback of the video data, so that the user device 100 can only play the video data and cannot play other video data. to play.
  • the graphic code may also include multiple QR code controls, such as a third QR code control, a fourth QR code control, etc., which are not limited here.
  • QR code controls can represent different payment contents.
  • the first QR code control represents purchase 1-month membership rights
  • the third QR code control indicates the purchase of 3-month membership rights, etc.
  • any QR code control also includes description information; the description information is used to describe the information of the QR code control.
  • the description information of the third QR code control is "3-month membership rights".
  • any QR code control also includes amount information to express the payment amount of the QR code. If the amount information in the third QR code control is "60 yuan", it means that the payment amount for 3-month membership rights is 60 yuan.
  • the user device 100 after generating the QR code control, sets the QR code control on the screen of the paid video and at a preset position. As shown in FIG. 14 above, the first QR code control and the second QR code control are displayed in the upper right layer of the playback window of the video data played in full screen.
  • the user equipment 100 uses the playback rights to completely play the video data.
  • the user equipment 100 does not generate an image code when determining that the rights configuration information indicates that the second platform account has broadcast rights. That is to say, after playing the video data, the user device 100 determines whether the second platform account logged in on the video playback platform has playback rights. If it is determined that the second platform account has playback rights, it means that the user device 100 can play the paid video. , there is no need to prompt the user to purchase playback rights (that is, no image code is generated), so as to avoid affecting the user's video viewing experience.
  • the rights content information can be generated based on the playback rights corresponding to the second platform account, and displayed on the display of the user device 100 .
  • the rights content information includes information such as the remaining time of the rights.
  • FIG. 15 is a schematic diagram of a payment page exemplarily shown in some embodiments of the present disclosure. As shown in Figure 15, the payment page displays information such as user name, second platform account number, membership rights time limit; where, the solid line Indicates the membership rights time limit corresponding to the scanned QR code, that is, the time limit to be purchased. The dotted line indicates the time limit of other membership rights, not the time limit of the current purchase.
  • the mobile terminal 300 displays the payment page, the user can click "Recharge Now" to complete the payment.
  • the mobile terminal 300 places an order in the first server 200 based on the information on the payment page.
  • the first server 200 will return the order number and payment address (such as WeChat, Alipay, bank card, etc.) for the user. Make payment.
  • the mobile terminal 300 After the user successfully pays, the mobile terminal 300 generates a payment order.
  • the mobile terminal 300 After the mobile terminal 300 generates the payment order, it sends the payment order to the first server 200 . So that the first server 200 generates an activation request according to the payment order, and goes to the third-party server 400 to activate the playback rights of the second platform account.
  • the third-party server 400 feeds back a message (such as an activation identifier) to the first server 200 to indicate whether the second platform account is successful in activating the playback rights.
  • a message such as an activation identifier
  • the first server 200 if the first server 200 does not receive the activation identification fed back by the third-party server 400 within the second period of time, the first server 200 sends the first instruction to the user equipment 100 .
  • the first instruction includes a first duration; the first duration and the second duration can be values preset based on experience, such as the first duration is 1s, 2s, etc., and the second duration is 3s, 4s, etc., which are not limited here. .
  • the user equipment 100 After receiving the first instruction, the user equipment 100 responds to the first instruction. Suspend the refresh of the second platform account, and after the first period of time, log in again to the second platform account of the video playback platform.
  • the first server 200 sends After the third-party server 400 sends the activation request, if it does not receive the first activation identification feedback from the third-party server 400 within 1s (the second time period), it means that the third-party server 400 has not completed the activation of the playback rights for the second platform account, and therefore needs to
  • the user equipment 100 sends the first instruction.
  • the user device 100 logs in to the second platform account of the video playback platform again (that is, refreshing the second platform account) after 3 seconds (the first duration).
  • the third-party server 400 is more likely to complete the activation of playback rights for the second platform account, that is, the success rate of successful activation of the second platform account's playback rights is increased, thus increasing the second platform's ability to re-login to the video playback platform.
  • the accuracy of using the playback rights reduces the number of times to refresh the second platform account, saving the consumption of communication resources and computing resources required when refreshing the second platform account.
  • the first server 200 if the first server 200 receives the activation identification fed back by the third-party server 400 within the second period of time, the first server 200 sends a second instruction to the user equipment 100 .
  • the first server 200 sends an activation request to the third-party server 400
  • it receives the first activation identifier fed back by the third-party server 400 within 1s (the second duration), which means that the third-party server 400 completes the processing of the second platform account.
  • the playback rights are activated, so the second instruction is sent to the user equipment 100.
  • the user device 100 After receiving the second instruction, the user device 100 directly logs in again to the second platform account of the video playback platform.
  • the software development kit (SDK) of the video playback platform in the user device 100 records the user's second platform account and other information, so the user device 100 calls the software development of the video playback platform.
  • the toolkit enables you to log in the second platform account to the video playback platform again without exiting the video playback platform.
  • the software development kit is a software development kit corresponding to the third-party server 400 .
  • the user equipment 100 determines whether the same instruction has been received based on the instruction identifier of the first instruction or the second instruction. Identified historical instructions.
  • the response command after receiving a response command, if it is determined that a historical response command with the same command identifier as the response command has been received, the response command will not be responded to; if it is determined that a historical response command with the same command identifier as the response command has not been received, If the same historical response command is received, the response command will be responded to.
  • the first instruction should be a delay instruction or the refresh instruction; if it is determined that a delay instruction or refresh instruction with the same order number has not been received, respond to the first instruction. This avoids duplicate messages appearing in network replay, improves the accuracy of response instructions, and thereby improves the accuracy of refreshing playback rights.
  • the user equipment 100 after responding to the response command, calls the software development tool kit of the video playback platform, logs in to the second platform account again, and sends a refresh request to the third-party server 400; to receive the third-party server 400 Feedback video data and second activation identification.
  • the third-party server 400 activates the playback rights for the third-party account and updates the rights configuration information.
  • the third-party server 400 queries the rights configuration information to see whether the third-party account corresponding to the second platform account has playback rights based on the second platform account in the refresh request, and then determines whether the second platform account has playback rights. , and then feeds back the activation identification to the user equipment 100.
  • the first activation logo indicates that the playback rights of the second platform account have been successfully activated.
  • the second activation identification indicates whether the playback rights of the second platform account have been successfully activated; if the second activation identification indicates that the playback rights of the second platform account have been successfully activated, it means that the user device 100 can completely play the video data, and therefore the video data is played. If the second activation identifier indicates that the second platform account fails to activate the playback rights, it means that the user device 100 cannot completely play the video data, and therefore cannot completely play the video data.
  • Figure 16 is a schematic diagram of a video playback screen exemplarily shown in some embodiments of the present disclosure.
  • the user device 100 After re-logging in to the second platform account of the video playback platform, the user device 100 displays that the rights and interests have been successfully activated (that is, the playback rights of the second platform account have been successfully opened), plays the paid video, and displays the information of the paid video (such as the video name, Number of episodes, etc.) and playback information (download speed, cache time, etc.).
  • the information of the paid video such as the video name, Number of episodes, etc.
  • playback information download speed, cache time, etc.
  • the rights of the platform account are opened in the first server 200.
  • each video icon in the video playback platform on the user device 100, and the video playback platform is logged in with a second platform account; the user clicks on any video icon to trigger the playback instruction of the video, where the video data of the video is stored in the first server 200 in.
  • the user equipment 100 After receiving the play instruction, the user equipment 100 sends a video request instruction to the first server 200 in response to the play instruction.
  • the first server 200 After receiving the video request instruction, the first server 200 feeds back the video data corresponding to the video and the rights identification of the second platform account.
  • the user device 100 determines that the rights identifier indicates that the second platform account does not have the rights to play, the user device 100 generates a graphic code.
  • a payment order is generated and sent to the first server 200 .
  • the first server 200 When the first server 200 receives the payment order and determines that the payment order is successful, it calls its own order management module to manage the payment order and generates an activation request.
  • the first server 200 calls its own rights activation module, responds to the activation request, and activates playback rights for the second platform account in the payment order. Among them, the rights activation module is periodically refreshed according to the first time interval. After the refresh, the activation identification of the second platform account is fed back.
  • the message module of the first server 200 waits for the activation identifier fed back by the rights activation module. If the message module does not receive the activation identifier fed back by the rights activation module within the second period of time, it sends a first instruction to the user equipment 100 to instruct the user equipment 100 to suspend the refresh, and after extending the first period of time, sends a first instruction to the first server 200 Send a refresh request.
  • the message module receives the activation identifier fed back by the rights activation module, it sends a second instruction to the user equipment 100 to instruct the user equipment 100 to directly send a refresh request to the first server 200 .
  • Figure 17 is a schematic flowchart of a reward equity data processing method exemplified in some embodiments of the present disclosure. As shown in Figure 17, the content is as follows:
  • Platforms that provide reward rights and interests can issue reward rights through QR codes, links, etc.
  • the rights and interests claim instruction is triggered (for example, the rights and interests claim instruction instructs to receive the reward rights and interests of "50 yuan coupon" ).
  • the user equipment 100 After receiving the rights claim instruction, the user equipment 100 responds to the rights claim instruction. Determine whether the user's first platform account is logged into the platform. When it is determined that the user has not logged into the user's first platform account, a first collection request is generated according to the own device identification, and the first collection request is sent to the first server 200 .
  • the first server 200 determines whether the device identification supports binding reward rights by querying the blacklist and whether the device identification has been bound to reward rights.
  • the first server 200 When determining that the device identification supports binding of reward rights and interests, the first server 200 binds the device identification with the reward rights and interests, and generates device reward rights and interests. For example, the device identifier is "a5" and the reward rights are “50 yuan coupons”. After binding "a5" with “50 yuan coupons", the device reward rights "a5-50 yuan coupons" are generated.
  • Step 1030 Record equipment reward rights.
  • the first server 200 After generating the device reward rights, the first server 200 stores the device reward rights into the database.
  • the device reward rights may also be stored in the storage module in the first server, which is not specifically limited here.
  • the first server 200 After storing the device reward rights, the first server 200 sends the first prompt information to the user device 100 to indicate that the user device 100 has successfully received the reward rights.
  • Step 1040 Send a transition request.
  • the user equipment 100 After receiving the first prompt information, the user equipment 100 displays the first prompt information to let the user know that the reward rights have been successfully claimed.
  • the first prompt message is "Received successfully, please log in to the first platform account to use”.
  • the user device 100 When users operate on the first platform account, they need to log in to the first platform account first. After recognizing that the user has logged in to the first platform account, the user device 100 generates a transition request according to the first platform account, and sends the transition request to the first server 200 .
  • Step 1050 Determine whether the first platform account is allowed to be collected.
  • the first server 200 determines whether the first platform account supports binding reward rights by querying the blacklist and whether the first platform account has been bound with reward rights.
  • the first server 200 determines that the first platform account supports binding reward rights and interests, it queries the corresponding device reward rights and interests according to the device identification, then unbinds the device identification and reward rights and interests in the device reward rights and interests, and then binds the first platform account Bound with reward rights and interests to generate account reward rights.
  • the equipment reward rights are "a5-50 yuan coupons”; unbind the equipment identification "a5" in “a5-50 yuan coupons” from the reward rights "50 yuan coupons", and combine the first The platform account "b5" and the reward rights "50 yuan coupon” are bound to each other to generate the account reward rights "b5-50 yuan coupon”.
  • Step 1060 Record the account reward rights.
  • Step 1070 Use the account to reward benefits.
  • the user device 100 sends a query request to the first server 200 to query the reward rights bound to the user's first platform account, so that the user can select the reward rights and use the reward rights.
  • the user device 100 After obtaining the usage instruction (instruction to use reward rights) input by the user, the user device 100 calculates the transaction amount of the transaction request; for example, if the usage instruction indicates the use of the reward rights of "50 yuan discount coupon", then the total transaction amount and " 50 yuan discount coupon” as the transaction amount.
  • the user device 100 After obtaining the payment password input by the user, the user device 100 sends the payment password to the first server 200 .
  • the first server 200 determines that the payment password is correct, it completes the transaction payment and generates a transaction order.
  • the user device 100 when the user is not logged in to the first platform account of a certain platform, in the process of receiving the platform's equity rewards through the user device 100, the user device 100 generates a first claim request based on its own device identification, and sends the first request The collection request is sent to the first server 200.
  • the first server 200 After receiving the first claim request and judging that the device identification in the first claim request supports the claim of reward rights and interests, the first server 200 binds the device identification with the reward rights and interests and generates the device reward rights and interests, thereby realizing the first request without logging in.
  • you create a platform account you can receive bonus rights. This avoids the situation of not receiving the reward rights due to the inability to claim the reward rights during the process of logging in to the account; it improves the real-time and efficiency of receiving the reward rights.
  • the user device 100 After the user logs in to the first platform account, the user device 100 sends a transition request to the first server 200 so that the first server 200 transitions the reward rights and interests received by the device identification to the first platform account, ensuring that the reward rights and interests are on the first platform. Use under the account to ensure the legality and accuracy of the use of reward rights.
  • the video data corresponding to the video icon is stored in the third-party server 400, and the user plays the video data corresponding to the video icon on the video playback platform corresponding to the first server 200. Therefore, the user equipment 100 sends a video data request instruction to the third-party server 400 .
  • the rights configuration information of the third-party server 400 records the corresponding relationship between the second platform account of the video playback platform and its own third-party account, as well as the rights information of the third-party account.
  • the third-party account does not have the right to play, it means that the second platform account does not have the right to play; when the third-party account does have the right to play, it means that the account on the second platform has the right to play.
  • the third-party server 400 can also feed back the rights identification according to the rights configuration information to indicate whether the second platform account has broadcast rights.
  • the video data is the video data corresponding to the playback instruction.
  • the user equipment 100 plays the video data in full screen. After receiving the rights configuration information, and determining that the rights configuration information indicates that the second platform account does not have the playback rights, it determines that the playback time of the video data reaches the preset time length. If so, a graphic code is generated.
  • the graphic code includes the first QR code control and/or the second QR code control; the first QR code control is used to activate the playback rights of the second platform account (that is, to open the rights to complete playback of each video data) ;
  • the second QR code control indicates the right to activate the complete playback of video data.
  • the user uses the mobile terminal 300 to scan the QR code control and place an order. Because the second platform account is the account of the video playback platform corresponding to the first server 200, payment interaction needs to be performed with the first server 200 to pay the payment order.
  • the mobile terminal 300 sends the purchase information (such as amount, time limit, equity type, user name, platform account, etc.) corresponding to the first QR code control to the first server 200, so that the first server 200 returns the corresponding callback address. (Such as payment address, etc.).
  • the purchase information such as amount, time limit, equity type, user name, platform account, etc.
  • the mobile terminal 300 calls the payer based on the callback address and returns the payer's payment page to the mobile terminal 300. After the user successfully pays on the mobile terminal 300, a payment order is generated.
  • the video data is the data of the third-party server 400, it is necessary to activate the playback rights of the third-party account, and then obtain the playback rights of the second platform account.
  • the first server 200 After receiving the payment order sent by the mobile terminal 300 and determining that the payment order was successfully paid, the first server 200 sends an activation request to the third-party server 400; where the activation request is used to instruct the third-party server 400 to correspond to the second platform account.
  • the third-party account activates playback rights.
  • the first server 200 When the first server 200 sends an activation request to the third-party server 400, it sends a kafka message to the timing component to start the timing task; where the kafka message includes the order number of the payment order.
  • the third-party server 400 After receiving the activation request, the third-party server 400 queries the payment success of the payment order based on the order number in the activation request; queries the third-party account corresponding to the second platform account based on the second platform account in the activation request, and checks the third-party account number. Activate playback rights and update rights configuration information.
  • a first activation identification is fed back to the first server 200; wherein, the first activation identification indicates that the second platform account is successfully activated for playback rights, that is, the second platform account has playback rights.
  • the first server 200 Before receiving the first activation identification fed back by the third-party server 400 based on the activation request, if the first server 200 receives the timeout information sent by the timing component, it generates the first instruction according to the preset first duration.
  • the first server 200 Before receiving the first activation identification based on the activation request feedback from the third-party server 400, if the first server 200 does not receive the timeout information sent by the timing component, it will generate a second instruction; and send a task cancellation instruction to the timing component to cancel the Scheduled tasks.
  • the first server sends the first instruction or the second instruction to the user device 100 .
  • the user equipment 100 After receiving the response instruction (the first instruction or the second instruction), the user equipment 100 determines whether it has received a historical response instruction with the same order identifier according to the instruction identifier of the response instruction; if so, it does not respond to the response instruction.
  • the third-party server 400 After receiving the refresh request, the third-party server 400 queries the rights information of the third-party account corresponding to the second platform account based on the second platform account in the refresh request (indicating whether the third-party account has playback rights). Then, a second activation identifier (indicating whether the platform account has the broadcasting rights) is generated based on the playback rights of the third-party account, and the video data and the second activation identifier are fed back to the user device 100 .
  • the user equipment 100 determines whether the platform account is successfully activated for playback rights (that is, determines whether the second platform account has playback rights); if so, the user equipment 100 plays the video data to complete the complete playback of the video data.
  • the QR code control is displayed on the user device 100, which does not require the user to jump to the screen for purchasing playback rights. This allows the user to directly activate the playback rights on the screen where the video data is played, reducing the need to activate playback rights. Steps for entitlements to improve users’ experience in activating playback entitlements.
  • the user equipment 100 Before responding to the response command, the user equipment 100 determines whether it has received a historical response command with the same order number. This avoids duplicate messages appearing in network replay, improves the accuracy of response instructions, and thereby improves the accuracy of refreshing playback rights.
  • the response command is the first command
  • the first server 200 has not received the feedback message from the third-party server 400, which means that the playback rights of the third-party account corresponding to the second platform account have not been successfully activated, and it also means that the playback rights of the third-party account corresponding to the second platform account have not been successfully activated.
  • the playback rights have not been successfully activated, so within the preset first period of time, the user device 100 does not refresh the second platform account, that is, it does not re-login to the second platform account, and does not send a refresh request, which reduces the need to refresh the second platform account. the number of times, This saves the consumption of communication resources and computing resources required when refreshing the second platform account.
  • the success rate of successfully activating the playback rights of the second platform account is increased. Therefore, the user device 100 refreshes the second platform account after the preset first period of time, and improves the success rate after re-logging in to the second platform account. , the second platform account has the accuracy of playback rights, which improves the user experience of watching paid videos.

Landscapes

  • Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Development Economics (AREA)
  • Finance (AREA)
  • Economics (AREA)
  • Game Theory and Decision Science (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Marketing (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Telephonic Communication Services (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本公开一些实施例中提供一种用户设备及奖励权益数据处理方法，所述方法包括：获取用户输入的权益领取指令；响应于所述权益领取指令，在判断未登录平台账号时，根据所述用户设备的设备标识生成第一领取请求，并将所述第一领取请求发送至服务器；其中，所述第一领取请求包括所述设备标识；所述第一领取请求用于指示所述服务器将所述设备标识与奖励权益相互绑定；所述平台账号为提供奖励权益的平台的账号；在登录所述平台账号之后，向所述服务器发送过渡请求；其中，所述过渡请求包括所述平台账号和所述设备标识；所述过渡请求用于指示所述服务器将与所述设备标识绑定的奖励权益和所述平台账号相互绑定；所述第一提示信息表示奖励权益领取成功。

Description

一种用户设备及奖励权益数据处理方法
相关申请的交叉引用
本公开要求在2022年06月27日提交中国专利局、申请号为202210742122.2，以及要求在2022年07月08日提交中国专利局、申请号为202210804638.5的中国专利申请的优先权，其全部内容通过引用结合在本公开中。
技术领域
本公开涉及数据处理技术领域，尤其涉及一种用户设备及奖励权益数据处理方法。
背景技术
随着终端设备以及网络的广泛应用，在网络购物等场景中，网络平台或商家为了提高用户交易率、交易金额等，会向用户发放奖励权益(如折扣券、满减券等)。
目前，用户在获取奖励权益时，通常被要求先登录对应网络平台的平台账号。因为平台账号用于标识用户身份，绑定用户数据，因此需要先登录对应网络平台的平台账号，进而获得网络平台或该平台中商家发放的奖励权益。
但是，在一些奖励权益为限量权益的场景中(如折扣券共有100张，即只能有100个用户获得权益)，用户在登录网络平台账号时，奖励权益已经发放完，导致用户未获取到奖励权益。因此影响了用户获取奖励权益的效率，即用户获取奖励权益的效率低、实时性差。
发明内容
本公开一些实施例中提供了一种用户设备，包括：
显示器，被配置为显示奖励权益；
控制器，被配置为：
获取用户输入的权益领取指令；
响应于所述权益领取指令，在判断未登录第一平台账号时，根据所述用户设备的设备标识生成第一领取请求，并将所述第一领取请求发送至第一服务器；其中，所述第一领取请求包括所述设备标识；所述第一领取请求用于指示所述第一服务器将所述设备标识与奖励权益相互绑定；所述第一平台账号为提供奖励权益的平台的账号；
在登录所述第一平台账号之后，向所述第一服务器发送过渡请求；其中，所述过渡请求包括所述第一平台账号和所述设备标识；所述过渡请求用于指示所述第一服务器将与所述设备标识绑定的奖励权益和所述第一平台账号相互绑定；所述第一提示信息表示奖励权益领取成功。
本公开的一些实施例中还提供了一种用户设备的奖励权益数据处理方法，所述方法包括：
获取用户输入的权益领取指令；
响应于所述权益领取指令，在判断未登录平台账号时，根据所述用户设备的设备标识生成第一领取请求，并将所述第一领取请求发送至服务器；其中，所述第一领取请求包括所述设备标识；所述第一领取请求用于指示所述服务器将所述设备标识与奖励权益相互绑 定；所述平台账号为提供奖励权益的平台的账号；
在登录所述平台账号之后，向所述服务器发送过渡请求；其中，所述过渡请求包括所述平台账号和所述设备标识；所述过渡请求用于指示所述服务器将与所述设备标识绑定的奖励权益和所述平台账号相互绑定；所述第一提示信息表示奖励权益领取成功。
附图说明
图1为本公开一些实施例中用户设备的使用场景；
图2为本公开一些实施例中用户设备的结构示意图；
图3为本公开一些实施例中用户设备的软件架构示意图；
图4为本公开一些实施例中用户设备的界面示意图之一；
图5为本公开一些实施例中用户设备的登录第一平台账号的示意图；
图6为本公开一些实施例中设备间的部分交互过程的示意图之一；
图7为本公开一些实施例中用户设备的显示画面示意图；
图8为本公开一些实施例中用户设备的充值页面示意图；
图9为本公开一些实施例中设备间的部分交互过程的示意图之二；
图10为本公开一些实施例中用户设备的支付页面示意图；
图11为本公开一些实施例中用户设备的输入支付密码界面的示意图；
图12为本公开一些实施例中用户设备的交易订单的示意图；
图13为本公开一些实施例中用户设备的界面示意图之二；
图14为本公开一些实施例中用户设备的二维码控件示意图；
图15为本公开一些实施例中终端设备的支付页面示意图；
图16为本公开一些实施例中用户设备的视频播放画面的示意图；
图17为本公开一些实施例中一种奖励权益数据处理方法的部分流程示意图之一；
图18为本公开一些实施例中一种奖励权益数据处理方法的部分流程示意图之二。
具体实施方式
为使本公开的目的和实施方式更加清楚，下面将结合本公开示例性实施例中的附图，对本公开示例性实施方式进行清楚、完整地描述，显然，描述的示例性实施例仅是本公开一部分实施例，而不是全部的实施例。
需要说明的是，本公开中对于术语的简要说明，仅是为了方便理解接下来描述的实施方式，而不是意图限定本公开的实施方式。除非另有说明，这些术语应当按照其普通和通常的含义理解。
本公开实施方式提供的第一服务器与用户设备进行数据通信。接收用户设备发送的交易配置信息，并在根据交易配置信息生成各交易之后，由用户设备获取交易。
用户设备可以具有多种实施形式，例如，可以是智能电视、移动终端、笔记本电脑、平板电脑(例如ipad)等。图1和图2为本公开的第一服务器的一种具体实施方式。
图1为根据本公开实施例中用户设备与第一服务器之间操作场景的示意图。如图1所示，用户可通过用户设备100(如移动终端、平板电脑、计算机、笔记本电脑、智能电视等)与第一服务器200进行数据通信。用户还可以通过另一个移动终端300与所述用户设备100、所述第一服务器200进行数据通信。
图2示出了用户设备100的结构示意图。
下面以用户设备100为例对实施例进行具体说明。应该理解的是，图2所示用户设备100仅是一个范例，并且用户设备100可以具有比图2中所示的更多的或者更少的部件，可以组合两个或多个的部件，或者可以具有不同的部件配置。图中所示出的各种部件可以在包括一个或多个信号处理和/或专用集成电路在内的硬件、软件、或硬件和软件的组合中实现。
图2中示例性示出了根据示例性实施例中用户设备100的硬件配置框图。如图2所示，用户设备100包括：射频(radio frequency，RF)电路110、存储器120、显示单元130、摄像头140、传感器150、音频电路160、无线保真(Wireless Fidelity，Wi-Fi)模块170、处理器180、蓝牙模块181、以及电源190等部件。
RF电路110可用于在收发信息或通话过程中信号的接收和发送，可以接收基站的下行数据后交给处理器180处理；可以将上行数据发送给基站。通常，RF电路包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等器件。
存储器120可用于存储软件程序及数据。处理器180通过运行存储在存储器120的软件程序或数据，从而执行用户设备100的各种功能以及数据处理。存储器120可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。存储器120存储有使得用户设备100能运行的操作系统。本公开中存储器120可以存储操作系统及各种应用程序，还可以存储执行本公开实施例所述方法的代码。
显示单元130可用于接收输入的数字或字符信息，产生与用户设备100的用户设置以及功能控制有关的信号输入，在本公开一些实施例中，显示单元130可以包括设置在用户设备100正面的触摸屏131，可收集用户在其上或附近的触摸操作，例如点击按钮，拖动滚动框等。
显示单元130还可用于显示由用户输入的信息或提供给用户的信息以及用户设备100的各种菜单的图形用户界面(graphical user interface，GUI)。在本公开一些实施例中，显示单元130可以包括设置在用户设备100正面的显示屏132。其中，显示屏132可以采用液晶显示器、发光二极管等形式来配置。显示单元130可以用于显示本公开中所述的各种图形用户界面。
其中，触摸屏131可以覆盖在显示屏132之上，也可以将触摸屏131与显示屏132集成而实现通信终端100的输入和输出功能，集成后可以简称触摸显示屏。本公开中显示单元130可以显示应用程序以及对应的操作步骤。
摄像头140可用于捕获静态图像或视频。物体通过镜头生成光学图像投射到感光元件。感光元件可以是电荷耦合器件(charge coupled device，CCD)或互补金属氧化物半导体(complementary metal-oxide-semiconductor，CMOS)光电晶体管。感光元件把光信号转换成电信号，之后将电信号传递给处理器180转换成数字图像信号。
用户设备100还可以包括至少一种传感器150，比如加速度传感器151、距离传感器152、指纹传感器153、温度传感器154。用户设备100还可配置有陀螺仪、气压计、湿度计、温度计、红外线传感器、光传感器、运动传感器等其他传感器。
音频电路160、扬声器161、麦克风162可提供用户与用户设备100之间的音频接口。音频电路160可将接收到的音频数据转换后的电信号，传输到扬声器161，由扬声器161 转换为声音信号输出。通信终端100还可配置音量按钮，用于调节声音信号的音量。另一方面，麦克风162将收集的声音信号转换为电信号，由音频电路160接收后转换为音频数据，再将音频数据输出至RF电路110以发送给比如另一终端，或者将音频数据输出至存储器120以便进一步处理。本公开中麦克风162可以获取用户的语音。
Wi-Fi属于短距离无线传输技术，用户设备100可以通过Wi-Fi模块170帮助用户收发电子邮件、浏览网页、交易配置信息和访问流媒体等，它为用户提供了无线的宽带互联网访问。
处理器180是用户设备100的控制中心，利用各种接口和线路连接整个设备的各个部分，通过运行或执行存储在存储器120内的软件程序，以及调用存储在存储器120内的数据，执行用户设备100的各种功能和处理数据。在一些本公开实施例中，处理器180可包括一个或多个处理单元；处理器180还可以集成应用处理器和基带处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序等，基带处理器主要处理无线通信。可以理解的是，上述基带处理器也可以不集成到处理器180中。本公开中处理器180可以运行操作系统、应用程序、用户界面显示及触控响应，以及本公开实施例所述的处理方法。另外，处理器180与输入单元130和显示单元140耦接。
蓝牙模块181，用于通过蓝牙协议来与其他具有蓝牙模块的蓝牙设备进行信息交互。例如，用户设备100可以通过蓝牙模块181与同样具备蓝牙模块的可穿戴电子设备(例如智能手表)建立蓝牙连接，从而进行数据交互。
用户设备100还包括给各个部件供电的电源190(比如电池)。电源可以通过电源管理系统与处理器180逻辑相连，从而通过电源管理系统实现管理充电、放电以及功耗等功能。用户设备100还可配置有电源按钮，用于设备的开机和关机，以及锁屏等功能。
图3是本发明实施例用户设备100的软件结构框图。
在本公开一些实施例中，将Android系统分为四层，从上至下分别为应用程序层，应用程序框架层，安卓运行时(Android runtime)的系统库，以及内核层。
如图3所示，应用程序包可以包括相机，图库，日历，通话，微信，支付宝，地图，导航，WLAN，蓝牙，音乐，视频，短信息等应用程序。
应用程序框架层为应用程序层的应用程序提供应用编程接口(application programming interface，API)和编程框架。应用程序框架层包括一些预先定义的函数。
如图3所示，应用程序框架层可以包括窗口管理器，内容提供器，视图系统，电话管理器，资源管理器，通知管理器等。
窗口管理器用于管理窗口程序。窗口管理器可以获取显示屏大小，判断是否有状态栏，锁定屏幕，截取屏幕等。
内容提供器用来存放和获取数据，并使这些数据可以被应用程序访问。所述数据可以包括视频，图像，音频，拨打和接听的电话，浏览历史和书签，电话簿等。
视图系统包括可视控件，例如显示文字的控件，显示图片的控件等。视图系统可用于构建应用程序。显示界面可以由一个或多个视图组成的。例如，包括短信通知图标的显示界面，可以包括显示文字的视图以及显示图片的视图。
电话管理器用于提供用户设备100的通信功能。例如通话状态的管理(包括接通，挂断等)。
资源管理器为应用程序提供各种资源，比如本地化字符串，图标，图片，布局文件， 视频文件等等。
通知管理器使应用程序可以在状态栏中显示通知信息，可以用于传达告知类型的消息，可以短暂停留后自动消失，无需用户交互。比如通知管理器被用于告知下载完成，消息提醒等。通知管理器还可以是以图表或者滚动条文本形式出现在系统顶部状态栏的通知，例如后台运行的应用程序的通知，还可以是以对话窗口形式出现在屏幕上的通知。例如在状态栏提示文本信息，发出提示音，终端设备振动，指示灯闪烁等。
Android runtime状态的系统库包括核心库和虚拟机。Android runtime状态的系统库负责安卓系统的调度和管理。
核心库包含两部分：一部分是java语言需要调用的功能函数，另一部分是安卓的核心库。
应用程序层和应用程序框架层运行在虚拟机中。虚拟机将应用程序层和应用程序框架层的java文件执行为二进制文件。虚拟机用于执行对象生命周期的管理，堆栈管理，线程管理，安全和异常的管理，以及垃圾回收等功能。
系统库可以包括多个功能模块。例如：表面管理器(surface manager)，媒体库(Media Libraries)，三维图形处理库(例如：OpenGL ES)，2D图形引擎(例如：SGL)等。
表面管理器用于对显示子系统进行管理，并且为多个应用程序提供了2D和3D图层的融合。
媒体库支持多种常用的音频，视频格式回放和录制，以及静态图像文件等。媒体库可以支持多种音视频编码格式，例如：MPEG4，H.264，MP3，AAC，AMR，JPG，PNG等。
三维图形处理库用于实现三维图形绘图，图像渲染，合成，和图层处理等。
2D图形引擎是2D绘图的绘图引擎。
内核层是硬件和软件之间的层。内核层至少包含显示驱动，摄像头驱动，音频驱动，传感器驱动。
图4是用于示出用户设备上的用户界面的示意图。在本公开一些实施例中，用户通过点击(包括对具有触控功能的用户设备的触摸，以及通过对连接的外设输入设备点击)用户界面上的应用图标可以打开相应的应用程序(如购物平台、视频播放平台等程序)，或者通过触摸用户界面上的操作图标执行对应的操作。例如，如图4所示，用户点击“视频”图标，打开视频播放平台(如聚好看平台)；用户点击“购物”图标，打开购物平台(如某某网上商城)。
在本公开一些实施例中，用户可通过用户设备100中的应用程序对应的网络平台进行网上交易；网上交易指的是在网络的虚拟环境上进行的交易，如在网络平台上购买食品、服装商品、电子设备、开通虚拟权益(例如对网络视频平台的提供的付费视频的观看权益)等。
下面结合网上购买服装商品，示例性说明用户设备100与第一服务器200之间进行网上交易的工作流程。
用户通过用户设备100的用户界面中“购物”图标，打开购物平台，并在购物平台上登录该用户的第一平台账号，然后购物平台上挑选服装商品(如衣服、裤子、鞋子等)，最后计算交易金额，通过用户设备100发起支付请求，并将支付请求发送中第一服务器200。
第一服务器200根据用户设备100选择的支付方式反馈输入密码页面，在确定用户密码输入成功之后，生成交易订单。交易订单中包括交易金额、交易清单等信息；例如，衣 服的厂家、收货人信息、价格(如200元)、数量、等信息。
在本公开一些实施例中，用户设备100计算交易金额时，通过计算购买商品的总金额与用户账号中的奖励权益的差值，得到交易金额。
例如，购买商品包括一件衣服、一条裤子；其中，衣服的价格为200元，裤子的价格为300元，则购买商品的总金额为500元。用户账号中具有50元优惠券(奖励权益的一种)，因此计算出交易金额为450元。
在本公开一些实施例中，用户在获取购物平台发放的奖励权益时，用户需要先在购物平台登录第一平台账号，然后在第一服务器200中请求奖励权益。第一服务器200会将奖励权益与第一平台账号相互绑定，因此实现用户在计算交易金额时，使用该奖励权益。
例如，购物平台发放有9折购物券(奖励权益的一种)；用户在购物平台上登录第一平台账号之后，向第一服务器200发送针对9折购物券的领取请求。第一服务器200在确定该第一平台账号为允许领取奖励权益的第一平台账号时，则将第一平台账号与奖励权益进行绑定，生成领取记录，并将领取记录进行存储。
用户在用户设备100上使用奖励权益时，用户设备100根据第一平台账号向第一服务器访问存储的领取记录，得到第一平台账号对应的领取记录，进而得到第一平台账号对应的奖励权益。
在本公开一些实施例中，提供奖励权益的平台(如上述购物平台)所发放的奖励权益是限量的；例如，购物平台在某一节日中，发放100张9折优惠券，用于供不同的用户进行领取。也就是说，只有100个用户可以领取到“9折优惠券”。
用户在使用用户设备100领取“9折优惠券”时，在用户设备100上的状态一般包括以下两种情况：用户设备100已登录用户的第一平台账号和用户设备100未登录用户的第一平台账号。
针对已登录第一平台账号的用户设备100，可以直接领取“9折优惠券”；针对未登录第一平台账号的用户设备100，需要用户先登录第一平台账号，再领取“9折优惠券”；图5为本公开一些实施例中示例性示出的一种登录第一平台账号的示意图，如图5所示，用户设备在未登录用户的第一平台账号时，发出登录提示，登录提示用于表示需要登录第一平台账号；如图5所示需要用户输入手机号和手机验证码。
基于上述描述可知，导致在登录第一平台账号时，限量的“9折优惠券”已被其他用户领取，进而使未登录第一平台账号的用户在使用用户设备100领取“9折优惠券”时，领取失败。也就是说，未登录第一平台账号的用户使用用户设备100没有及时的领取到“9折优惠券”。影响了用户获取奖励权益的效率和实时性。
综上，为了提高用户获取奖励权益的效率和实时性，图6为本公开在本公开一些实施例中示例性的示出了一种奖励权益数据处理方法，如图6所示，该方法可应用于能够实施奖励权益数据处理方法的第一服务器200。具体内容如下：
第一服务器200接收用户设备100发送的第一领取请求；其中，第一领取请求包括用户设备100的设备标识。在本公开一些实施例中，设备标识为唯一标识；例如，用户设备的设备标识为国际移动设备识别码(International Mobile Equipment Identity，IMEI)，如IMEI为“8612***0344”。
第一领取请求是用户设备100在确定未登录第一平台账号时，根据设备标识生成的。例如，用户在使用用户设备100获取奖励权益时，用户设备100确定购物平台未登录用户 的第一平台账号，则根据自身的IMEI生成第一领取请求。
第一平台账号为提供奖励权益的平台的账号；第一平台账号为用户的身份标识号(Identity document，ID)。例如，第一平台账号为用户的手机号码、身份证号码等。
第一服务器200在得到第一领取请求之后，将设备标识与奖励权益相互绑定之前，判断第一领取请求中的设备标识是否支持领取奖励权益，以此保证奖励权益发放的合法性。
在本公开一些实施例中，通过判断设备标识是否记录在黑名单中，来确定设备标识是否支持领取奖励权益。黑名单指的是记录失信人员的名单，用于记录禁止领取奖励权益的设备标识、第一平台账号等信息。
在本公开一些实施例中，若判断设备标识记录在黑名单，则确定设备标识不支持领取奖励权益；若判断设备标识未记录在黑名单，则确定设备标识支持领取奖励权益。例如，黑名单记录有设备标识a1和a2，则设备标识a1和a2被禁止领取奖励权益。即用户通过设备标识为a1或a2的用户设备无法领取奖励权益；用户通过设备标识为a3(非a1和a2的其他设备标识)的用户设备可以领取奖励权益。
在本公开一些实施例中，为了防止用户通过用户设备100重复领取奖励权益，通过判断设备标识是否已绑定奖励权益，来确定设备标识是否支持领取奖励权益。例如，在确定设备标识a3未记录在黑名单时，若判断设备标识a3已经绑定有“9折优惠券”的奖励权益，则确定设备标识a3不支持领取奖励权益；若判断设备标识a3未绑定有“9折优惠券”的奖励权益，则确定设备标识a3支持领取奖励权益。
在本公开一些实施例中，通过判断设备标识是否已绑定相同奖励权益，来确定设备标识是否支持领取奖励权益。例如，假设奖励权益包括“8折优惠券”和“9折优惠券”，设备标识a3未记录在黑名单；若设备标识a3已经绑定“9折优惠券”的奖励权益，未绑定“8折优惠券”的奖励权益，则确定设备标识a3支持领取“8折优惠券”的奖励权益，不支持领取“9折优惠券”的奖励权益。
在本公开一些实施例中，还可以通过设备标识已绑定相同奖励权益的数量来确定设备标识是否支持领取奖励权益。例如，假设奖励权益的领取阈值为3且设备标识a3未记录在黑名单，即设备标识a3最多绑定3个奖励权益；若设备标识a3已经绑定3个奖励权益，则确定设备标识a3不支持领取奖励权益。
需要说明的是，上述确定设备标识是否支持领取奖励权益的判断条件仅作为一种实施例，并不对判断条件进行限定。
第一服务器200在确定设备标识支持领取奖励权益之后，将设备标识与奖励权益相互绑定，生成设备奖励权益；并将设备奖励权益存储至数据库和/或自身的存储模块中。
例如，设备标识为“a4”，奖励权益为“9折优惠券”，将“a4”与“9折优惠券”绑定后，生成设备奖励权益“a4-9折优惠券”。在本公开一些实施例中，奖励权益可以由权益标识来表示，如“9折优惠券”的权益标识为c9，则设备奖励权益为“a4-c9”。在本公开一些实施例中，设备奖励权益还可以包括奖励权益的数量信息，如设备奖励权益为“a4-c9(2)”，“(2)”表示设备标识为“a4”的用户设备领取有两张“9折优惠券”。
第一服务器200在生成设备奖励权益时，表示用户设备100已经领取到了奖励权益。然后第一服务器200向用户设备100发送提示信息，提示信息用于表示奖励权益领取成功或失败。
在本公开一些实施例中，第一服务器200根据用户设备100的设备标识生成设备奖励 权益之后，向用户设备100发送第一提示信息；其中，第一提示信息用于表示奖励权益领取成功；在本公开一些实施例中，第一服务器200根据用户设备100的设备标识未生成设备奖励权益之后，向用户设备100发送第二提示信息；其中，第二提示信息用于表示奖励权益领取失败。
例如，第一服务器200在接收第一领取请求之后，判断第一领取请求中的设备标识是否支持领取奖励权益(判断设备标识是否支持领取奖励权益的相关内容已在上述进行描述，在此不做赘述)。
第一服务器200若判断设备标识支持领取奖励权益，则生成设备奖励权益，向用户设备100发送第一提示信息；第一服务器200若判断设备标识不支持领取奖励权益，则向用户设备100发送第二提示信息。
在本公开一些实施例中，第二提示信息包括失败原因，如设备标识被加入黑名单、设备标识已领取奖励权益、奖励权益数量不足等。
用户设备100在接收到第一提示信息后，显示第一提示信息，以使用户知悉奖励权益领取成功。用户在使用或查看奖励权益的操作时，会在用户设备100上的平台登录第一平台账号；其中，平台为提供奖励权益的平台，第一平台账号为该平台的账号，用于表示用户在该平台的身份标识。
在本公开一些实施例中，第一服务器200不向用户设备100发送提示信息，由用户设备通过数据访问接口查询第一服务器200是否生成设备奖励权益。例如，用户设备100向第一服务器100发送第一领取请求1s之后，通过第一服务器200开放的数据访问接口与第一服务器200进行数据通信，以此查询出第一服务器200是否生成设备奖励权益。
用户设备100在确定第一服务器200生成设备奖励权益，且用户登录第一平台账号之后，向第一服务器200发送过渡请求，以指示第一服务器200将奖励权益与第一平台账号相互绑定。其中，过渡请求包括第一平台账号和设备标识。
在本公开一些实施例中，第一服务器200接收到过渡请求之后，将与设备标识绑定的奖励权益和第一平台账号相互绑定之前，判断过渡请求中的第一平台账号是否支持领取奖励权益；若判断第一平台账号支持领取奖励权益，则根据设备奖励权益生成账号奖励权益。
在本公开一些实施例中，通过判断第一平台账号是否记录在黑名单中，来确定设备标识是否支持领取奖励权益。基于上述判断设备标识是否支持领取奖励权益的描述，若判断第一平台账号记录在黑名单，则确定第一平台账号不支持领取奖励权益；若判断第一平台账号未记录在黑名单，则确定第一平台账号支持领取奖励权益。
例如，黑名单记录有第一平台账号b1和b2，则表示第一平台账号b1和b2被禁止领取奖励权益。即用户使用登录有第一平台账号b1或b2的用户设备无法领取奖励权益；用户使用登录有第一平台账号b3(非b1和b2的其他第一平台账号)的用户设备可以领取奖励权益。
在本公开一些实施例中，为了防止用户通过用户设备100重复领取奖励权益，通过判断第一平台账号是否已绑定奖励权益，来确定第一平台账号是否支持领取奖励权益。在本公开另一些实施例中，通过判断第一平台账号是否已绑定相同奖励权益，来确定第一平台账号是否支持领取奖励权益。在又本公开一些实施例中，还可以通过第一平台账号已绑定相同奖励权益的数量来确定第一平台账号是否支持领取奖励权益。
需要说明的是，判断第一平台账号是否支持领取奖励权益的判断条件可以与判断设备 标识是否支持领取奖励权益的判断条件是相同的条件，可以为不同的条件，在此不做赘述与限定。
在本公开一些实施例中，第一服务器200在确定第一平台账号支持领取奖励权益之后，则根据用户设备100的设备标识在数据库或存储模块中查询用户设备100是否具有设备奖励权益。
若第一服务器200确定用户设备100具有设备奖励权益，则将设备奖励权益中的设备标识和奖励权益解除绑定。然后将第一平台账号与奖励权益相互绑定，生成账号奖励权益。基于上述描述进行举例，设备奖励权益为“a4-c9”；将“a4-c9”中的设备标识“a4”与奖励权益“c9”解除绑定，将第一平台账号“b3”与奖励权益“c9”相互绑定，生成账号奖励权益“b3-c9”。
基于以上内容可知，用户在未登录第一平台账号时，第一服务器可以先根据设备标识实现领取奖励权益，避免因登录账号的过程中，无法领取奖励权益导致未领取到奖励权益的情况；提升了领取奖励权益的实时性和效率。
用户在登录第一平台账号之后，将设备标识领取的奖励权益过渡到第一平台账号，保证了奖励权益是在第一平台账号下进行使用，保证了奖励权益使用的合法性和准确性。
在本公开一些实施例中，第一服务器200根据第一平台账号生成账号奖励权益之后，向用户设备100发送第一提示信息；在一些实施例中，第一服务器200根据第一平台账号未生成账号奖励权益之后，向用户设备100发送第二提示信息。
例如，第一服务器200在接收过渡请求之后，判断过渡请求中的第一平台账号是否支持领取奖励权益(判断第一平台账号是否支持领取奖励权益的内容已在上述进行描述，在此不做赘述)。
第一服务器200若判断第一平台账号支持领取奖励权益，则生成账号奖励权益，向用户设备100发送第一提示信息；第一服务器200若判断第一平台账号不支持领取奖励权益，则向用户设备100发送第二提示信息。
在本公开一些实施例中，第二提示信息包括失败原因，如第一平台账号被加入黑名单、第一平台账号已领取奖励权益、奖励权益数量不足等。
在本公开一些实施例中，第一服务器200接收用户设备100发送的第二领取请求；其中，第二领取请求包括用户的第一平台账号。第二领取请求是用户设备100在确定已登录第一平台账号时，根据用户的第一平台账号生成的。例如，用户在使用用户设备100获取奖励权益时，用户设备100确定购物平台已登录用户的第一平台账号，则根据用户的第一平台账号生成第二领取请求。
第一服务器200在接收第二领取请求之后，断过第一平台账号是否支持领取奖励权益(判断第一平台账号是否支持领取奖励权益的内容已在上述进行描述，在此不做赘述)。在判断第一平台账号支持领取奖励权益时，将第一平台账号与奖励权益绑定，生成账号奖励权益。在判断第一平台账号不支持领取奖励权益时，向用户设备100反馈第二提示信息。
针对于虚拟电子权益的电子交易过程，与在网络平台进行实物商品的电子交易过程相比，网络平台一般会在电子交易之前为用户提供体验服务。例如，视频播放平台用于提供视频数据并进行播放，视频数据包括免费视频和付费视频。其中，免费视频表示不需要付费就可以观看的视频；付费视频表示在针对该视频进行付费购买播放权益之后，才允许观看的视频。付费视频提供有免费观看片段；其中，免费观看片段可以为付费视频中任一片 段。例如，付费视频的时长为1小时50分钟，免费观看片段为付费视频的前6分钟的视频片段(即0：00：00至0：06：00的视频片段)。那么对于用户而言，在观看付费视频时，可以首先播放所述付费视频对应的免费观看片段进行体验，在观看完免费观看片段之后再决定是否对付费视频购买相关播放权益以观看全部内容。
在本公开一些实施例中，视频播放平台一般是具有会员机制的，视频会员在视频播放平台上可以播放付费视频，且跳过视频播放之前播放的广告；而非视频会员在视频播放平台上无法播放付费视频，也无法跳过视频播放之前播放的广告。例如，针对某一视频平台，若平台账号为该视频平台的视频会员账号，则用户在使用该平台账号观看视频时，可以观看付费视频，且跳过视频播放之前播放的广告。
在本公开一些实施例中，用户设备100在播放完免费观看片段之后，向不具有播放权益的用户提示购买该付费视频的播放权益。图7为公开一些实施例中示例性示出的一种用户设备的显示画面示意图；如图7所示，免费观看片段播放完之后，跳转出支付控件，用于指示用户充值会员，进而获取播放权益，实现对付费视频的播放。
基于图7进行举例，用户在点击“前往充值”的控件之后，用户设备100将显示画面跳转至充值详情页面。图8为本公开一些实施例中示例性示出的一种充值页面的示意图，如图8所示，充值详情页面包括多个充值选项，如1个月、2个月、3个月、6个月等充值选项，用户在选择其中一个充值选项之后，用户设备100将显示画面跳转至支付画面。
在一些本公开实施例中，支付画面可以为二维码画面，由用户通过终端设备300扫面二维码之后，在终端设备300上进行支付，并根据平台账号、视频标识等信息生成支付订单。
在本公开一些实施例中，终端设备300生成支付订单之后，将支付订单发送至服务器。然后服务器根据支付订单向对应的第二平台账号生成并发送播放权益开通请求，以对第二平台账号开通播放权益。
需要说明的是，上文以及下文所述的第二平台账号可以为上文所述的第一平台账号，即所述第一平台账号/第二平台账号既可以用于在网络平台上购买实物商品，也可以用于在网络平台上购买视频的播放权益，那么视频的播放权益所对应的奖励权益可以通过上文所述内容进行发放；上文以及下文所述的第二平台账号也可以为与上文所述的第一平台账号不同的平台账号；在此不做过多限定。
在本公开一些实施例中，服务器异步执行以下两个处理过程：一个是在确定支付订单支付成功之后，将支付结果返回直至用户设备；另一个是对第二平台账号开通播放权益。用户设备100接收支付结果后，刷新第二平台账号，对付费视频进行播放。
但是在本公开一些实施例中，用户设备100接收支付结果时，平台账号播放权益并未开通成功，进而导致用户设备100刷新第二平台账号(也就是使用播放权益时)之后，仍然无法播放付费视频(即播放权益开通未成功)，也就是说，即使用户设备100多次刷新平台账号，仍然存在无法播放付费视频的情况，导致播放权益的使用准确率较低，浪费了刷新第二平台账号时所需要的通信资源、计算资源等消耗，且影响了用户观看视频的体验。且根据上述描述，用户需要多次跳转显示画面实现对播放权益的购买。也就是说，用户购买播放权益的步骤繁杂，影响了播放权益开通的效率。
综上，为了提高用户观看视频的体验，避免通信资源、计算资源的浪费，提升用户购买播放权益的效率，图9为本公开在一些实施例中示例性的示出了一种针对于上述问题解 决方法的示意图，其中，用于提供奖励权益发放的第一服务器与视频播放平台对应的用于提供视频的播放权益的服务器可以为相同的服务器，也可以为不同的服务器，下文将主要以用于提供奖励权益发放的服务器与视频播放平台对应的用于提供视频的播放权益的服务器为相同的第一服务器200为例进行说明。如图9所示，对于第一服务器200而言，具体内容如下：
接收移动终端300基于图形码生成的支付订单。其中，支付订单中包括第二平台账号以及表示开通第二平台账号的播放权益。
其中，图形码是用户设备100在接收用户触发的播放指令之后，向第一服务器200发送视频数据请求指令，以接收第一服务器200基于视频数据请求指令反馈的视频数据和权益配置信息，使用户设备100在确定权益配置信息表征第二平台账号不具备播放权益时生成的。其中，视频数据请求指令中包括登录在视频播放平台上的第二平台账号。这部分具体内容将在下文详细说明，此处暂且不表。
例如，用户使用移动终端300扫描二维码控件之后，移动终端300根据自身的终端标识、用户设备100的设备标识、第二平台账号、二维码标识、支付订单的订单号等信息，请求第一服务器200对应的接口(二维码标识对应的接口)获取支付页面。如上述图9所示的支付页面，用户点击“立即充值”之后，移动终端300基于支付页面的信息在第一服务器200中下单，第一服务器200会返回订单号、支付地址(如WX支付应用地址、ZFB支付应用地址、银行卡等)等信息，以供用户进行付费。用户在成功付费之后，移动终端300生成支付订单，并将支付订单发送至第一服务器200。
在本公开一些实施例中，图形码包括第一二维码控件和第二二维码控件；支付订单包括第一二维码对应的第一订单和第二二维码对应的第二订单。
基于上述描述进行举例，用户使用移动终端300扫描第一二维码时，会生成开通视频播放平台会员权益的第一订单；用户使用移动终端300扫描第二二维码时，会生成开通针对视频数据完整播放权益的第二订单。
第一服务器200在接收第一订单和/或第二订单时，基于第一订单和/或第二订单向第三方服务器400发送开通请求。其中，开通请求用于指示第三方服务器400对第二平台账号对应的第三方账号开通播放权益。
在本公开一些实施例中，第一服务器200向第三方服务器400发送开通请求时，同时开启定时任务。例如，第一服务器200向第三方服务器400发送开通请求时，向定时组件发送kafka消息；其中，kafka消息包括支付订单的订单号。定时组件用于计时。
在本公开一些实施例中，第一服务器200在接收到第三方服务器400基于开通请求反馈的消息之后，向定时组件发送任务取消指令，以取消定时任务。
定时组件若在第二时长内接收到任务取消指令，则表示第一服务器200在预设的第二时长内接收到第三方服务器400基于开通请求反馈的消息，进而取消定时任务。且第一服务器200会向用户设备100发送第二指令。
定时组件若在第二时长内未接收到任务取消指令，则向第一服务器200发送超时信息。第一服务器200在接收到超时信息之后，表示第一服务器200在预设的第二时长内未接收到第三方服务器400基于开通请求反馈的消息，则向用户设备100发送第一指令。
其中，第一指令用于指示用户设备100暂缓刷新，在经过预设的第一时长后，重新登录视频播放平台的第二平台账号，并向第三方服务器400发送刷新请求；其中，重新登录 第二平台账号的方法将在下文进行展开描述。
为了更好的阐述上述内容，基于图6所示的奖励权益数据处理方法，所述方法可应用于能够实施奖励权益数据处理方法的用户设备。具体内容如下：
获取用户输入的权益领取指令。其中，权益领取指令是用户在提供奖励权益的平台上触发的；图10为本公开一些实施例中示例性示出的一种奖励权益示意图，如图10所示，奖励权益为“9折优惠券”，在购物平台的界面上进行显示。其中，购物平台为提供奖励权益的平台；权益领取指令为“领取”。也就是说，用户在点击“领取”控件时，触发权益领取指令。
用户设备100在接收权益领取指令之后，响应于权益领取指令，判断购物平台是否已登录第一平台账号。
用户设备100在判断未登录第一平台账号时，根据终端设备的设备标识生成第一领取请求，并将第一领取请求发送至第一服务器200；其中，第一领取请求用于指示第一服务器将设备标识与奖励权益绑定，生成设备奖励权益。
例如，用户设备100接收用户在购物平台上触发的领取“9折优惠券”的权益领取指令，然后判断购物平台是否登录有用户的第一平台账号，若是，则根据自身的设备标识生成第一领取请求，并将第一领取请求发送至第一服务器200。
用户设备100将第一领取请求发送至第一服务器200之后，接收第一服务器200基于第一领取请求反馈的提示信息；其中，提示信息包括第一提示信息和第二提示信息；第一提示信息表示奖励权益领取成功；第二提示信息表示奖励权益领取失败。
用户设备100若接收的提示信息为第一提示信息，则表示用户设备100领取到了奖励权益，并展示给用户，以使用户知悉。用户在知悉用户设备100领取到奖励权益，并使用或查看奖励权益时，用户设备100向用户发出登录提示，如上述图5所示，用于提示用户登录第一平台账号后，才允许对奖励权益进行操作(如使用或查看奖励权益等)。
因此，用户在登录第一平台账号之后，用户设备100根据第一平台账号生成过渡请求，并将过渡请求发送至第一服务器200；其中，过渡请求用于指示第一服务器200将设备奖励权益修改为账号奖励权益。
用户设备100在将过渡请求发送至第一服务器200之后，接收第一服务器200基于过渡请求反馈的提示信息，并将提示信息展示给用户，以使用户知悉是否成功领取到奖励权益。
在本公开一些实施例中，用户设备100在判断已登录第一平台账号时，根据第一平台账号生成第二领取请求，并将第二领取请求发送至第一服务器200；其中，第二领取请求用于指示第一服务器200将第一平台账号与奖励权益绑定，生成账号奖励权益。
在本公开一些实施例中，若用户设备100接收第一服务器200基于第一领取请求反馈的提示信息为第二提示信息，则在确定登录第一平台账号之后，向第一服务器200发送第二领取请求。以此避免因设备标识不支持领取奖励权益，而第一平台账号支持领取奖励权益导致的领取奖励权益失败，提升了领取奖励权益的灵活性和准确性。
用户在知悉领取奖励权益成功之后，可以在用户设备100上的购物平台界面中，触发使用指令。例如，用户在进行交易请求提交时，使用奖励权益，计算交易请求的交易金额。
用户设备100在获取用户输入的使用指令之后，计算交易请求的交易金额，并发起输入支付密码界面，用于接收用户输入的接收密码；图11本公开一些实施例中示例性示出的 一种输入支付密码界面的示意图，如图11所示，假设奖励权益为“50元抵扣券”，交易总金额为50.01元，则经过计算，需要用户支付的交易金额为0.01元，在用户输入支付密码后，将用户输入的支付密码发送至第一服务器200。
第一服务器200在接收支付密码后，确认支付密码是否正确时，若是，则完成交易支付，生成交易订单。图12本公开一些实施例中示例性示出的一种交易订单的示意图，如图12所示，支付订单中包括订单状态(如处理中，即支付过程中；处理完成，即支付完成；处理失败，即处理失败等)、订单信息(如包月购买影视会员，购买某品牌的外套等。用户在支付完成之后，可以点击“已完成支付”退出支付订单页面；或在支付失败时，点击“重新支付”，返回如图8所示的输入支付密码界面。
而对于用户设备100在被用户用于播放视频时，用户使用终端设备300生成支付订单并发送至服务器之后，没有成功开通播放权益第二平台账号时，用户设备100在多次刷新平台账号，仍然存在无法播放付费视频的情况，导致播放权益的使用准确率较低，浪费了刷新第二平台账号时所需要的通信资源、计算资源等消耗，且影响了用户观看视频的体验的问题，在本公开一些实施例中，对于用户设备100还包括如下内容：
接收用户触发的播放指令。
基于图13举例来说，用户点击用户设备100上的“视频”图标，打开视频播放平台(如聚好看平台)，视频播放平台上显示有多个视频资源，如电影A1、电视剧A2等。用户在点击“电影A1”的显示画面时，触发播放指令。
响应于播放指令，向第二服务器发送视频数据请求指令，以接收第二服务器基于视频数据请求指令反馈的视频数据和权益配置信息。其中，视频数据请求指令中包括登录在视频播放平台上的第二平台账号。
在本公开一些实施例中，第二服务器为第三方视频播放平台对应的第三方服务器400；也就是说，播放指令对应的播放数据存储第三方服务器中。
在本公开一些实施例中，配置信息是第三方服务器根据第二平台账号与第三方服务器的第三方账号之间的对应关系以及第三方账号的权益信息生成的；也就是说，第三方服务器400中记录有第二平台账号于第三方账号之间的对应关系(如第二平台账号a1与第三方账号b1为一一对应的关系，第二平台账号a2与第三方账号b2为一一对应的关系等)，根据第三方账号的权益信息以及第二平台账号与第三方账号之间的对应关系生成权益配置信息。例如，权益配置信息为a1-b1-0；其中，“0”为第三方账号“b1”的权益信息，表示第三方账号“b1”不具备播放权益。
用户设备100在获取权益配置信息之后，确定权益配置信息表征第二平台账号是否具备播放权益。因为权益配置信息中记录有第二平台账号与第三方账号之间的对应关系以及第三方账号的权益信息，因此根据第三方账号的权益信息确定第三方账号对应的第二平台账号是否具备播放权益。
在本公开一些实施例中，在权益配置信息中，第三方账号的权益信息不具备播放权益时，基于第二平台账号与第三方账号之间的对应关系，表征该第三方账号对应的第二平台账号不具备播放权益。例如，权益配置信息为a1-b1-0；因为第三方账号“b1”不具备播放权益，因此确定第三方账号“b1”对应的第二平台账号“a1”不具备播放权益。
在第三方账号的权益信息具备播放权益时，基于第二平台账号与第三方账号之间的对应关系，表征第二平台账号具备所述播放权益。例如，权益配置信息为a2-b2-1；其中，“1” 为第三方账号“b2”的权益信息，表示第三方账号“b2”具备播放权益。因为第三方账号“b2”具备播放权益，因此确定第三方账号“b2”对应的第二平台账号“a2”具备播放权益。
用户设备100在确定权益配置信息表征第二平台账号不具备播放权益时，生成图像码。
在本公开一些实施例中，根据视频数据的播放时长生成图形码；若判断视频数据的播放时长达到预设时长，则生成图形码；若判断视频数据的播放时长未达到预设时长，则不生成图形码。
也就是说，在生成图形码之前，用户设备100会对视频数据进行播放。在本公开一些实施例中，用户设备100对视频数据进行全屏播放。
在本公开一些实施例中，视频数据中包括免费观看片段，第二平台账号不具备播放权益时，仍然可以对免费观看片段进行播放。视频数据的前6分钟的视频为免费观看片段。若判断付费视频的播放时长达到预设时长，则根据第二平台账号、付费视频的标识和显示设备的标识生成图形码；若判断付费视频的播放时长未达到预设时长，则不生成图形码。
举例来说，预设时长为3分钟，当免费观看片段播放至第3分钟时，根据第二平台账号、付费视频的标识和用户设备的标识生成图形码，以提示用户购买播放权益。当免费观看片段播放至第2分钟时(即未播放至3分钟时)，则不生成图形码。既保证了不影响用户对预设时长内免费观看片段的观看，又保证了在免费观看片段播放结束之前提示用户购买播放权益，防止免费观看片段之后的片段播放实时性低。
其中，预设时长小于免费观看片段的时长。例如，免费观看片段为6分钟，预设时长可以为3、4分钟等，或者可以为根据经验预设的值，如1分钟等，在此不做限定。
在本公开一些实施例中，图形码是根据下述一种或多种信息组合生成的。信息包括但不限于：登录在视频播放平台上的第二平台账号(第二平台账号为用户的身份标识号)，视频数据的标识(如视频数据的分类标识，视频数据在视频播放平台中的专区标识等)和用户设备100的设备标识。
在本公开一些实施例中，图形码包括第一二维码控件和\或第二二维码控件。其中，第一二维码控件表示开通视频播放平台会员权益的二维码；第二二维码控件表示开通针对视频数据完整播放的权益。
图14为本公开一些实施例中示例性示出的一种二维码控件示意图，如图14所示，用户设备100上显示有第一二维码控件和第二二维码控件；其中，第一二维码控件是用户设备100根据第二平台账号和设备标识生成的，用于表示开通视频播放平台的会员权益；第二二维码控件是用户设备100根据付费视频的标识、第二平台账号和设备标识生成的，用于表示开通针对该视频数据完整播放的权益。
也就是说，用户可以使用终端设备300扫描第一二维码控件，在支付成功之后，购买视频播放平台的会员权益，进而使用户设备100可以对视频播放平台中所有视频数据进行播放。或者，用户可以使用终端设备300扫描第二二维码控件，在支付成功之后，购买针对该视频数据完整播放的权益，进而使用户设备100仅可以对该视频数据进行播放，无法对其他视频数据进行播放。
在本公开一些实施例中，图形码还可以包括多个二维码控件，如第三二维码控件、第四二维码控件等，在此不做限定。
其中，不同的二维码控件可以表示不同的支付内容。例如，第一二维码控件表示购买 1个月的会员权益，第三二维码控件表示购买3个月的会员权益等。
在本公开一些实施例中，任一二维码控件上还包括描述信息；描述信息用于描述该二维码控件的信息。如第三二维码控件的描述信息为“3个月的会员权益”。
在本公开一些实施例中，任一二维码控件上还包括金额信息，用于表述该二维码的付款金额。如第三二维码控件的金额信息为“60元”，则表示3个月会员权益的付款金额为60元。
在本公开一些实施例中，用户设备100在生成二维码控件之后，将二维码控件设置于付费视频的画面上以及预设位置。如上述图14所示，将第一二维码控件和第二二维码控件显示在全屏播放的视频数据的播放窗口的右上方图层中。
由以上内容可知，若确定第二平台账号不具有播放权益，则表示用户设备100无法对视频数据进行完整播放，需要提示用户购买播放权益(即生成二维码控件)，以此在用户购买播放权益之后，用户设备100使用播放权益，对视频数据进行完整播放。
在本公开一些实施例中，用户设备100在确定权益配置信息表征第二平台账号具备播放权益时，不生成图像码。也就是说，用户设备100在播放视频数据之后，判断视频播放平台上登录的第二平台账号是否具有播放权益，若确定第二平台账号具有播放权益，则表示用户设备100可以对付费视频进行播放，无需再提示用户购买播放权益(即不生成图像码)，避免影响用户观看视频的体验。
在本公开一些实施例中，用户设备100若确定第二平台账号具有播放权益，可以根据该第二平台账号对应的播放权益生成权益内容信息，并通过用户设备100的显示器进行显示。例如，权益内容信息包括权益所剩时长等信息。
用户设备100生成图形码之后，由用户使用移动终端300扫描图形码。扫描图形码之后，根据自身的终端标识、用户设备100的设备标识、第二平台账号、二维码标识等信息，请求第一服务器200对应的接口(二维码标识对应的接口)获取支付页面。图15为本公开一些实施例中示例性示出的一种支付页面示意图，如图15所示，支付页面中显示有用户名，第二平台账号，会员权益的时限等信息；其中，实线表示所扫描的二维码对应的会员权益时限，即所要购买的时限。虚线表示其他会员权益时限，不是当前所要购买的时限。
基于上述图15举例来说，移动终端300显示支付页面之后，用户可以点击“立即充值”实现付费。用户点击“立即充值”之后，移动终端300基于支付页面的信息在第一服务器200中下单，第一服务器200会返回订单号、支付地址(如微信、支付宝、银行卡等)，以供用户进行付费。用户在成功付费之后，移动终端300生成支付订单。
移动终端300生成支付订单之后，将支付订单发送至第一服务器200。以使第一服务器200根据支付订单生成开通请求，去第三方服务器400中开通第二平台账号的播放权益。
第三方服务器400在对第二平台账号开通播放权益之后，向第一服务器200反馈消息(如开通标识)，以指示第二平台账号开通播放权益是否成功。
在本公开一些实施例中，第一服务器200若在第二时长内未接收到第三方服务器400反馈的开通标识，则向用户设备100发送第一指令。其中，第一指令包括第一时长；第一时长和第二时长可以为根据经验预设的值，如第一时长为1s、2s等，第二时长为3s、4s等，在此不做限定。
用户设备100在接收到第一指令之后，响应于第一指令。暂缓对第二平台账号的刷新，经过第一时长之后，重新登录视频播放平台的第二平台账号。例如，第一服务器200在向 第三方服务器400发送开通请求之后，在1s(第二时长)内未接收到第三方服务器400反馈的第一开通标识，则表示第三方服务器400未完成对第二平台账号开通播放权益，因此向用户设备100发送第一指令。用户设备100在接收到第一指令之后，经过3s(第一时长)后，再重新登录视频播放平台的第二平台账号(即刷新第二平台账号)。
因为3s后，第三方服务器400完成对第二平台账号开通播放权益的可能性较大，即第二平台账号的播放权益开通成功的成功率提升，因此提升了重新登录视频播放平台的第二平台账号后，使用播放权益的准确性，减少了刷新第二平台账号的次数，节省了刷新第二平台账号时所需要的通信资源、计算资源消耗。
在本公开一些实施例中，第一服务器200若在第二时长内接收到第三方服务器400反馈的开通标识，则向用户设备100发送第二指令。例如，第一服务器200在向第三方服务器400发送开通请求之后，在1s(第二时长)内接收到第三方服务器400反馈的第一开通标识，则表示第三方服务器400完成对第二平台账号开通播放权益，因此向用户设备100发送第二指令。用户设备100在接收到第二指令之后，直接重新登录视频播放平台的第二平台账号。
在本公开一些实施例中，用户设备100中视频播放平台的软件开发工具包(Software Development Kit，SDK)中记录有用户的第二平台账号等信息，因此用户设备100调用视频播放平台的软件开发工具包，不需要退出视频播放平台，实现将第二平台账号重新登录在视频播放平台上。其中，软件开发工具包为第三方服务器400对应的软件开发工具包。
在本公开一些实施例中，用户设备100在接收到第一指令或第二指令之后，响应于第一指令或第二指令之前，根据第一指令或第二指令的指令标识判断是否接收过相同标识的历史指令。
在本公开一些实施例中，接收到应答指令之后，若判断接收过与该应答指令的指令标识相同的历史应答指令，则不响应该应答指令；若判断未接收过与该应答指令的指令标识相同的历史应答指令，则响应该应答指令。
例如，第一指令应该延迟指令或该刷新指令；若判断未接收过与订单号相同的延迟指令或刷新指令，则响应该第一指令。以此避免网络重放出现的重复消息，提升响应指令的准确性，进而提升刷新播放权益的准确性。
在本公开一些实施例中，用户设备100相应于应答指令之后，调用视频播放平台的软件开发工具包，重新登录第二平台账号，并向第三方服务器400发送刷新请求；以接收第三方服务器400反馈的视频数据和第二开通标识。
基于上述内容可知，第三方服务器400在接收开通请求之后，对第三方账号开通播放权益，并更新权益配置信息。第三方服务器400接收到刷新请求之后，基于刷新请求中的第二平台账号，在权益配置信息中查询第二平台账号对应第三方账号是否具有播放权益，进而确定该第二平台账号是否具备播放权益，然后向用户设备100反馈开通标识。如第一开通标识表示第二平台账号的播放权益开通成功。
因此，第二开通标识表示第二平台账号的播放权益是否开通成功；若第二开通标识表示第二平台账号开通播放权益成功时，表示用户设备100可以完整播放视频数据，因此播放视频数据。若第二开通标识表示第二平台账号开通播放权益失败时，则表示用户设备100无法完整播放视频数据，因此无法完整播放视频数据。
图16为本公开一些实施例中示例性示出的一种视频播放画面的示意图，如图16所示， 用户设备100在重新登录视频播放平台的第二平台账号之后，显示权益开通成功(即表示第二平台账号的播放权益开通成功)，对付费视频进行播放，显示付费视频的信息(如视频名称、集数等)以及播放信息(下载速度、缓存时间等)。
在本公开一些实施例中，用户使用移动终端300提交支付订单之后，在第一服务器200中开通平台账号的权益。
例如，用户设备100上视频播放平台中各视频图标，且视频播放平台登录有第二平台账号；用户点击任一视频图标，触发该视频的播放指令，其中该视频的视频数据存储在第一服务器200中。用户设备100接收播放指令之后，响应于播放指令，向第一服务器200发送视频请求指令。
第一服务器200接收视频请求指令之后，反馈该视频对应的视频数据和第二平台账号的权益标识。用户设备100在确定权益标识表示第二平台账号不具备播放权益时，生成图形码。
用户使用移动终端300扫描图形码之后，生成支付订单，并将支付订单发送至第一服务器200。
第一服务器200在接收支付订单，且确定支付订单为支付成功时，调用自身的订单管理模块对支付订单进行管理，并生成开通请求。
第一服务器200调用自身的权益开通模块，响应于开通请求，对支付订单中第二平台账号开通播放权益。其中，权益开通模块是按照第一时间间隔，周期性刷新的，在刷新之后，反馈第二平台账号的开通标识。
第一服务器200的消息模块在生成开通请求之后，等待权益开通模块反馈的开通标识。消息模块在第二时长内，若未接收到权益开通模块反馈的开通标识，则向用户设备100发送第一指令，以指示用户设备100暂缓刷新，在延长第一时长后，向第一服务器200发送刷新请求。
消息模块在第二时长内，若接收到权益开通模块反馈的开通标识，则向用户设备100发送第二指令，以指示用户设备100直接向第一服务器200发送刷新请求。
为了更好的阐述上述内容，图17为本公开一些实施例中示例性示出的一种奖励权益数据处理方法的流程示意图，如图17所示，内容如下：
S1010、发送第一领取请求。
提供奖励权益的平台可以通过二维码、链接等方式发放奖励权益。用户使用用户设备100上的平台领取奖励权益时(如用户通过使用用户设备100扫描二维码领取奖励权益)，触发权益领取指令(如权益领取指令指示领取“50元抵用券”的奖励权益)。
用户设备100在接收权益领取指令之后，响应于权益领取指令。判断平台是否登录有用户的第一平台账号。在判断用户未登录有用户的第一平台账号时，根据自身的设备标识生成第一领取请求，并将第一领取请求发送至第一服务器200。
S1020、判断设备标识是否允许领取。
第一服务器200在获取第一领取请求之后，通过查询黑名单、设备标识是否已绑定奖励权益等方式，确定设备标识是否支持绑定奖励权益。
第一服务器200在确定设备标识支持绑定奖励权益时，将设备标识与奖励权益绑定，生成设备奖励权益。例如，设备标识为“a5”，奖励权益为“50元抵用券”，将“a5”与“50元抵用券”绑定后，生成设备奖励权益“a5-50元抵用券”。
步骤1030、记录设备奖励权益。
第一服务器200在生成设备奖励权益之后，将设备奖励权益存储至数据库。在本公开一些实施例中，也可以将设备奖励权益存储至第一服务器中的存储模块，在此不做具体限定。
第一服务器200在存储设备奖励权益之后，向用户设备100发送第一提示信息，以指示用户设备100领取奖励权益成功。
步骤1040、发送过渡请求。
用户设备100在接收到第一提示信息后，显示第一提示信息，以使用户知悉奖励权益领取成功。例如，第一提示信息为“领取成功，请登录第一平台账号使用”。
用户在对第一平台账号进行操作时，需要先登录第一平台账号。用户设备100在识别出用户登录第一平台账号之后，根据第一平台账号生成过渡请求，并将过渡请求发送至第一服务器200。
步骤1050、判断第一平台账号是否允许领取。
第一服务器200在获取过渡请求之后，通过查询黑名单、第一平台账号是否已绑定奖励权益等方式，确定第一平台账号是否支持绑定奖励权益。
第一服务器200在确定第一平台账号支持绑定奖励权益时，根据设备标识查询出对应的设备奖励权益，然后将设备奖励权益中的设备标识和奖励权益解除绑定，再将第一平台账号与奖励权益相互绑定，生成账号奖励权益。例如，设备奖励权益为“a5-50元抵用券”；将“a5-50元抵用券”中的设备标识“a5”与奖励权益“50元抵用券”解除绑定，将第一平台账号“b5”与奖励权益“50元抵用券”相互绑定，生成账号奖励权益“b5-50元抵用券”。
步骤1060、记录账号奖励权益。
步骤1070、使用账号奖励权益。
用户在使用奖励权益时，用户设备100向第一服务器200发送查询请求，查询出用户的第一平台账号所绑定的奖励权益，以供用户选择奖励权益，并使用该奖励权益。
用户设备100在获取用户输入的使用指令(使用奖励权益的指令)之后，计算交易请求的交易金额；例如，使用指令指示使用“50元抵扣券”的奖励权益，则将交易总金额与“50元抵扣券”的差值作为交易金额。
用户设备100在获取用户输入的支付密码之后，将支付密码发送至第一服务器200。第一服务器200在确定支付密码正确时，完成交易支付，生成交易订单。
由以上内容可知，用户在未登录某平台的第一平台账号时，通过用户设备100领取该平台的权益奖励的过程中，用户设备100根据自身的设备标识生成第一领取请求，并将第一领取请求发送至第一服务器200。第一服务器200在接收第一领取请求之后，并判断第一领取请求中的设备标识支持领取奖励权益时，将设备标识与奖励权益绑定，生成设备奖励权益，以此实现在未登录第一平台账号时，领取奖励权益。以此避免了因登录账号的过程中，无法领取奖励权益导致未领取到奖励权益的情况；提升了领取奖励权益的实时性和效率。
用户在登录第一平台账号之后，用户设备100向第一服务器200发送过渡请求，以使第一服务器200将设备标识领取的奖励权益过渡到第一平台账号，保证了奖励权益是在第一平台账号下进行使用，保证了奖励权益使用的合法性和准确性。
在本公开一些实施例中，如图18所示，还包括如下内容：
S1101、响应播放指令。
用户在用户设备100的视频播放平台中点击视频图标，触发该视频图标对应的播放指令。
S1102、发送视频数据请求指令。
在本公开一些实施例中，该视频图标对应的视频数据存储在第三方服务器400，而用户在第一服务器200对应的视屏播放平台上播放该视频图标对应的视频数据。因此用户设备100向第三方服务器400发送视频数据请求指令。
S1103、反馈视频数据和权益配置信息。
第三方服务器400的权益配置信息中记录有视频播放平台的第二平台账号与自身的第三方账号的对应关系，以及第三方账号的权益信息。在第三方账号不具备播放权益时，表示第二平台账号不具备播放权益；在第三方账号具备播放权益时，表示第二平台账号具备播放权益。
在本公开一些实施例中，第三方服务器400也可以根据权益配置信息反馈权益标识，以指示第二平台账号是否具备播放权益。
视频数据为播放指令对应的视频数据。
S1104、生成图形码。
用户设备100全屏播放视频数据，在接收权益配置信息之后，在确定权益配置信息表征第二平台账号不具备播放权益时，判断视频数据的播放时长达到预设时长，若是，则生成图形码。
其中，图形码包括第一二维码控件和\或第二二维码控件；第一二维码控件用于开通第二平台账号的播放权益(即开通对各视频数据进行完整播放的权益)；第二二维码控件表示开通针对视频数据完整播放的权益。
S1105、扫描二维码控件。
用户使用移动终端300扫描二维码控件，进行下单。因为第二平台账号为第一服务器200对应的视频播放平台的账号，因此需要与第一服务器200进行支付交互，对支付订单进行付款。
例如，移动终端300将第一二维码控件对应的购买信息(如金额、时限、权益类型、用户名、平台账号等)发送到第一服务器200，以使第一服务器200返回对应的回调地址(如支付地址等)。
用户在移动终端300上进行支付时，移动终端300根据回调地址调用支付方，并将支付方的支付页面返回移动终端300。用户在移动终端300上支付成功之后，生成支付订单。
S1106、发送支付订单。
将支付订单发送至第一服务器200。
S1107、发送开通请求。
因为视频数据为第三方服务器400的数据，因此需要开通第三方账号的播放权益，进而得到第二平台账号的播放权益。
第一服务器200在接收到移动终端300发送的支付订单，并在确定支付订单支付成功之后，向第三方服务器400发送开通请求；其中，开通请求用于指示第三方服务器400对第二平台账号对应的第三方账号开通播放权益。
S1108、开启定时任务。
第一服务器200向第三方服务器400发送开通请求时，向定时组件发送kafka消息，开启定时任务；其中，kafka消息包括支付订单的订单号。
S1109、反馈开通标识。
第三方服务器400接收开通请求之后，根据开通请求中的订单号，查询支付订单支付成功；根据开通请求中的第二平台账号查询出该第二平台账号对应的第三方账号，并对第三方账号开通播放权益，更新权益配置信息。
在对第三方账号开通播放权益成功之后，向第一服务器200反馈第一开通标识；其中，第一开通标识表示第二平台账号开通播放权益成功，即第二平台账号具备播放权益。
S1110、生成应答指令，并发送至用户设备100。
第一服务器200在接收到第三方服务器400基于开通请求反馈的第一开通标识之前，若接收到定时组件发送的超时信息，则根据预设的第一时长生成第一指令。
第一服务器200在接收到第三方服务器400基于开通请求反馈的第一开通标识之前，若未接收到定时组件发送的超时信息，则长生成第二指令；并向定时组件发送任务取消指令，取消定时任务。
第一服务器将第一指令或第二指令发送至用户设备100。
S1111、响应于应答指令，发送刷新请求。
用户设备100在接收到应答指令(第一指令或第二指令)之后，根据应答指令的指令标识判断是否接收过与订单标识相同的历史应答指令；若是，则不响应应答指令。
若否，则在确定应答指令为第一指令时，经过第一指令中的第一时长后，重新登录视频播放平台的第二平台账号，向第三方服务器400发送刷新请求。在确定应答指令为第二指令，则直接重新登录视频播放平台的第二平台账号，向第三方服务器400发送刷新请求。
S1112、反馈第二开通标识和视频数据。
第三方服务器400在接收刷新请求之后，基于刷新请求中的第二平台账号，查询第二平台账号对应的第三方账号的权益信息(表示第三方账号是否具备播放权益)。然后基于第三方账号的播放权益生成第二开通标识(表示平台账号是否具备播放权益)，并将视频数据和第二开通标识反馈至用户设备100。
S1113、播放视频数据。
用户设备100基于第二开通标识，确定平台账号开通播放权益是否成功(即确定第二平台账号是否具备播放权益)；若是，则播放视频数据，完成对视频数据的完整播放。
由以上内容可知，用户设备100上显示有二维码控件，不需要用户在跳转至购买播放权益的画面中进行购买，实现用户在播放视频数据的画面上，直接开通播放权益，减少开通播放权益的步骤，提升用户开通播放权益的体验。
用户设备100在响应应答指令之前，判是否断接收过与订单号相同的历史应答指令。以此避免网络重放出现的重复消息，提升响应指令的准确性，进而提升刷新播放权益的准确性。
应答指令为第一指令时，表示第一服务器200未收到第三方服务器400反馈的消息，即表示第二平台账号对应的第三方账号的播放权益并未开通成功，也表示第二平台账号的播放权益并未开通成功，因此在预设的第一时长内，用户设备100不对第二平台账号进行刷新，即不重新登录第二平台账号，也不发送刷新请求，减少了刷新第二平台账号的次数， 节省了刷新第二平台账号时所需要的通信资源、计算资源消耗。
在预设的第一时长内，第二平台账号的播放权益开通成功的成功率提升，因此用户设备100在预设的第一时长后刷新第二平台账号，提升了重新登录第二平台账号之后，第二平台账号具有播放权益的准确率，提升了用户观看付费视频的体验。

Claims (18)

  1. 一种用户设备，包括：
    显示器，被配置为显示奖励权益；
    控制器，被配置为：
    获取用户输入的权益领取指令；
    响应于所述权益领取指令，在判断未登录第一平台账号时，根据所述用户设备的设备标识生成第一领取请求，并将所述第一领取请求发送至第一服务器；其中，所述第一领取请求包括所述设备标识；所述第一领取请求用于指示所述第一服务器将所述设备标识与奖励权益相互绑定；所述第一平台账号为提供奖励权益的平台的账号；
    在登录所述第一平台账号之后，向所述第一服务器发送过渡请求；其中，所述过渡请求包括所述第一平台账号和所述设备标识；所述过渡请求用于指示所述第一服务器将与所述设备标识绑定的奖励权益和所述第一平台账号相互绑定；所述第一提示信息表示奖励权益领取成功。
  2. 根据权利要求1所述的用户设备，所述控制器还被配置为：
    响应于所述权益领取指令，在判断已登录所述第一平台账号时，根据所述第一平台账号生成第二领取请求，并将所述第二领取请求发送至所述第一服务器；其中，所述第二领取请求包括第一平台账号；所述第二领取请求用于指示所述第一服务器将所述第一平台账号与奖励权益相互绑定。
  3. 根据权利要求1所述的用户设备，所述控制器将所述第一领取请求发送至第一服务器之后，还被配置为：
    接收所述第一服务器基于所述第一领取请求反馈的提示信息；
    若所述提示信息为第一提示信息，则在登录所述第一平台账号之后，向所述第一服务器发送过渡请求；
    若所述提示信息为第二提示信息，则在登录所述第一平台账号之后，向所述第一服务器发送第二领取请求；其中，所述第二提示信息表示所述奖励权益领取失败。
  4. 根据权利要求1所述的用户设备，所述显示器，还被配置为全屏显示视频播放平台的视频数据；所述视频播放平台登录有第二平台账号；
    所述控制器，还被配置为：
    接收播放指令；
    响应于所述播放指令，向第二服务器发送视频数据请求指令，以接收所述第二服务器基于所述视频数据请求指令反馈的视频数据和权益配置信息；
    确定所述权益配置信息表征所述第二平台账号不具备播放权益时，则生成图形码；所述图形码用于使移动终端扫码后生成开通所述第二平台账号的播放权益的支付订单；
    接收所述第一服务器反馈的应答指令；其中，所述应答指令是所述第一服务器生成开通请求，并将所述开通请求发送至所述第二服务器后发送的；所述开通请求是所述第一服务器在确定所述支付订单支付成功后生成的；
    在确定所述应答指令为第一指令时，暂缓刷新，在延长第一时长后，向所述第二服务器发送刷新请求；其中，所述第一指令是所述第一服务器在发送开通请求后的第二时长内未接收到所述第二服务器反馈的第一开通标识后发送的；所述第一开通标识表示所述第二 平台账号开通所述播放权益成功；所述刷新请求用于指示所述第二服务器反馈视频数据和第二开通标识；
    在所述第二开通标识表示所述第二平台账号开通所述播放权益成功时，播放所述视频数据。
  5. 根据权利要求4所述的用户设备，所述控制器还被配置为：
    在确定所述应答指令为第二指令时，向所述第二服务器发送刷新请求；其中，所述第二指令是所述第一服务器在发送开通请求后的第二时长内接收到所述第二服务器反馈的第一开通标识后发送的。
  6. 根据权利要求4所述的用户设备，所述第二服务器为第三方视频播放平台对应的第三方服务器，所述第一服务器为所述视频播放平台对应的服务器；
    所述权益配置信息是所述第三方服务器根据所述视频数据请求指令中的第二平台账号与所述第三方服务器的第三方账号之间的对应关系以及所述第三方账号的权益信息生成的；在所述权益配置信息中第三方账号不具备所述播放权益时，表征所述第二平台账号不具备所述播放权益；在所述第三方账号的权益信息具备所述播放权益时，表征所述第二平台账号具备所述播放权益；
    所述开通请求用于指示所述第三方服务器对所述第二平台账号对应的第三方账号开通播放权益；所述第一开通标识是所述第三方服务器在接收开通请求后，对所述第三方账号开通播放权益成功后发送的。
  7. 根据权利要求6所述的用户设备，所述控制器生成图形码，具体被配置为：
    全屏播放所述视频数据；
    若判断所述视频数据的播放时长达到预设时长，则生成图形码；
    若判断所述视频数据的播放时长未达到预设时长，则不生成图形码。
  8. 根据权利要求7所述的用户设备，所述图形码包括第一二维码控件和\或第二二维码控件；其中，所述第一二维码控件用于开通所述第二平台账号的播放权益；所述第二二维码控件表示开通针对所述视频数据完整播放的权益。
  9. 根据权利要求4所述的用户设备，所述应答指令包括指令标识；
    所述控制器在接收应答指令之后，发送刷新请求之前，还被配置为：
    若判断接收过与所述指令标识相同的历史应答指令，则不响应所述应答指令；
    若判断未接收过与所述指令标识相同的历史应答指令，则响应所述应答指令。
  10. 一种用户设备的奖励权益数据处理方法，所述方法包括：
    获取用户输入的权益领取指令；
    响应于所述权益领取指令，在判断未登录平台账号时，根据所述用户设备的设备标识生成第一领取请求，并将所述第一领取请求发送至服务器；其中，所述第一领取请求包括所述设备标识；所述第一领取请求用于指示所述服务器将所述设备标识与奖励权益相互绑定；所述平台账号为提供奖励权益的平台的账号；
    在登录所述平台账号之后，向所述服务器发送过渡请求；其中，所述过渡请求包括所述平台账号和所述设备标识；所述过渡请求用于指示所述服务器将与所述设备标识绑定的奖励权益和所述平台账号相互绑定；所述第一提示信息表示奖励权益领取成功。
  11. 根据权利要求10所述的方法，所述方法还包括：
    响应于所述权益领取指令，在判断已登录所述第一平台账号时，根据所述第一平台账 号生成第二领取请求，并将所述第二领取请求发送至所述第一服务器；其中，所述第二领取请求包括第一平台账号；所述第二领取请求用于指示所述第一服务器将所述第一平台账号与奖励权益相互绑定。
  12. 根据权利要求10所述的方法，所述将所述第一领取请求发送至第一服务器之后，所述方法还包括：
    接收所述第一服务器基于所述第一领取请求反馈的提示信息；
    若所述提示信息为第一提示信息，则在登录所述第一平台账号之后，向所述第一服务器发送过渡请求；
    若所述提示信息为第二提示信息，则在登录所述第一平台账号之后，向所述第一服务器发送第二领取请求；其中，所述第二提示信息表示所述奖励权益领取失败。
  13. 根据权利要求10所述的方法，所述方法还包括：
    接收播放指令；
    响应于所述播放指令，向第二服务器发送视频数据请求指令，以接收所述第二服务器基于所述视频数据请求指令反馈的视频数据和权益配置信息；
    确定所述权益配置信息表征所述第二平台账号不具备播放权益时，则生成图形码；所述图形码用于使移动终端扫码后生成开通所述第二平台账号的播放权益的支付订单；
    接收所述第一服务器反馈的应答指令；其中，所述应答指令是所述第一服务器生成开通请求，并将所述开通请求发送至所述第二服务器后发送的；所述开通请求是所述第一服务器在确定所述支付订单支付成功后生成的；
    在确定所述应答指令为第一指令时，暂缓刷新，在延长第一时长后，向所述第二服务器发送刷新请求；其中，所述第一指令是所述第一服务器在发送开通请求后的第二时长内未接收到所述第二服务器反馈的第一开通标识后发送的；所述第一开通标识表示所述第二平台账号开通所述播放权益成功；所述刷新请求用于指示所述第二服务器反馈视频数据和第二开通标识；
    在所述第二开通标识表示所述第二平台账号开通所述播放权益成功时，播放所述视频数据。
  14. 根据权利要求13所述的方法，所述方法还包括：
    在确定所述应答指令为第二指令时，向所述第二服务器发送刷新请求；其中，所述第二指令是所述第一服务器在发送开通请求后的第二时长内接收到所述第二服务器反馈的第一开通标识后发送的。
  15. 根据权利要求13所述的方法，所述第二服务器为第三方视频播放平台对应的第三方服务器，所述第一服务器为所述视频播放平台对应的服务器；
    所述权益配置信息是所述第三方服务器根据所述视频数据请求指令中的第二平台账号与所述第三方服务器的第三方账号之间的对应关系以及所述第三方账号的权益信息生成的；在所述权益配置信息中第三方账号不具备所述播放权益时，表征所述第二平台账号不具备所述播放权益；在所述第三方账号的权益信息具备所述播放权益时，表征所述第二平台账号具备所述播放权益；
    所述开通请求用于指示所述第三方服务器对所述第二平台账号对应的第三方账号开通播放权益；所述第一开通标识是所述第三方服务器在接收开通请求后，对所述第三方账号开通播放权益成功后发送的。
  16. 根据权利要求15所述的方法，所述生成图形码，具体包括：
    全屏播放所述视频数据；
    若判断所述视频数据的播放时长达到预设时长，则生成图形码；
    若判断所述视频数据的播放时长未达到预设时长，则不生成图形码。
  17. 根据权利要求16所述的方法，所述图形码包括第一二维码控件和\或第二二维码控件；其中，所述第一二维码控件用于开通所述第二平台账号的播放权益；所述第二二维码控件表示开通针对所述视频数据完整播放的权益。
  18. 根据权利要求13所述的方法，所述应答指令包括指令标识；
    所述在接收应答指令之后，且在发送刷新请求之前，还包括：
    若判断接收过与所述指令标识相同的历史应答指令，则不响应所述应答指令；
    若判断未接收过与所述指令标识相同的历史应答指令，则响应所述应答指令。
PCT/CN2023/078601 2022-06-27 2023-02-28 一种用户设备及奖励权益数据处理方法 WO2024001255A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202210742122.2A CN116823341A (zh) 2022-06-27 2022-06-27 一种服务器、终端设备及奖励权益发放方法
CN202210742122.2 2022-06-27
CN202210804638.5A CN116801055A (zh) 2022-07-08 2022-07-08 一种显示设备、服务器及权益开通方法
CN202210804638.5 2022-07-08

Publications (1)

Publication Number Publication Date
WO2024001255A1 true WO2024001255A1 (zh) 2024-01-04

Family

ID=89382569

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/078601 WO2024001255A1 (zh) 2022-06-27 2023-02-28 一种用户设备及奖励权益数据处理方法

Country Status (1)

Country Link
WO (1) WO2024001255A1 (zh)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2014071536A (ja) * 2012-09-27 2014-04-21 Gourmet Navigator Inc クーポン管理システム
CN108197976A (zh) * 2017-12-18 2018-06-22 广东欧珀移动通信有限公司 奖励发放方法、装置以及服务器
CN111355731A (zh) * 2020-02-28 2020-06-30 北京奇艺世纪科技有限公司 资源访问的方法、装置、资源访问系统、设备及存储介质
CN111506834A (zh) * 2020-03-27 2020-08-07 拉扎斯网络科技（上海）有限公司 权益资源信息的推送方法及装置、存储介质、终端
CN111756796A (zh) * 2020-05-11 2020-10-09 拉扎斯网络科技（上海）有限公司 权益资源信息的推送方法及装置、存储介质、终端
US20210304159A1 (en) * 2020-03-26 2021-09-30 Toyota Jidosha Kabushiki Kaisha Server, computer-readable recording medium and system
CN114401121A (zh) * 2021-12-27 2022-04-26 北京百度网讯科技有限公司 应用程序登录方法、装置、电子设备及可读存储介质

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2014071536A (ja) * 2012-09-27 2014-04-21 Gourmet Navigator Inc クーポン管理システム
CN108197976A (zh) * 2017-12-18 2018-06-22 广东欧珀移动通信有限公司 奖励发放方法、装置以及服务器
CN111355731A (zh) * 2020-02-28 2020-06-30 北京奇艺世纪科技有限公司 资源访问的方法、装置、资源访问系统、设备及存储介质
US20210304159A1 (en) * 2020-03-26 2021-09-30 Toyota Jidosha Kabushiki Kaisha Server, computer-readable recording medium and system
CN111506834A (zh) * 2020-03-27 2020-08-07 拉扎斯网络科技（上海）有限公司 权益资源信息的推送方法及装置、存储介质、终端
CN111756796A (zh) * 2020-05-11 2020-10-09 拉扎斯网络科技（上海）有限公司 权益资源信息的推送方法及装置、存储介质、终端
CN114401121A (zh) * 2021-12-27 2022-04-26 北京百度网讯科技有限公司 应用程序登录方法、装置、电子设备及可读存储介质

Similar Documents

Publication Publication Date Title
US10761680B2 (en) Display method of scenario emoticon using instant message service and user device therefor
US8521857B2 (en) Systems and methods for widget rendering and sharing on a personal electronic device
EP3726376B1 (en) Program orchestration method and electronic device
JP7065102B2 (ja) 情報プッシング方法及び装置
US20120196626A1 (en) Mobile valet
CN105787776A (zh) 信息处理方法及装置
US20110238498A1 (en) Service stage for subscription management
US20150100463A1 (en) Collaborative home retailing system
EP1768346A1 (en) Provision of game applications across a network according to the display characteristics of a user terminal
US9258691B2 (en) Merchant server programmed for user acquisition within a repeat payment computer system
US11435876B1 (en) Techniques for sharing item information from a user interface
WO2021008295A1 (zh) 小程序的制作方法、装置、终端及存储介质
CN109118189A (zh) 一种使用智能设备进行支付的方法和装置
US20220377157A1 (en) Method for displaying data, and computer device
TW202147146A (zh) 頁面展示方法、裝置及電子設備
KR20200058511A (ko) 아이콘 디스플레이 방법, 디바이스, 및 시스템
CN112616091A (zh) 虚拟物品的发送方法、装置、计算机设备及存储介质
CN111667328A (zh) 页面内容展示方法、装置及电子设备
CN112533015A (zh) 直播互动方法、装置、设备及存储介质
US20220383394A1 (en) Live shopping broadcast
KR20100092687A (ko) 컨텐츠 재생방법
CN110012150A (zh) 一种消息显示方法及终端设备
US20110138307A1 (en) Publishing client device usage data
WO2024001255A1 (zh) 一种用户设备及奖励权益数据处理方法
CN109889906B (zh) 一种购物方法及相关设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23829447

Country of ref document: EP

Kind code of ref document: A1