Method, device, electronic device and storage medium for processing stimulus events

By receiving and encrypting unlock requests, generating authorization information, using key generation rules and key factors to encrypt unlock requests, isolating the encrypted/decrypting methods of different incentive events, solving the problem of illegal users skipping advertisements to obtain video permissions, and improving incentives The security of the carrier and the efficiency of server resource utilization.

CN115115384BActive Publication Date: 2024-11-12TENCENT TECHNOLOGY (SHENZHEN) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202110298266.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-03-19
Publication Date
2024-11-12
Estimated Expiration
2041-03-19

AI Technical Summary

Technical Problem

Illegal users obtain video playback permissions by skipping advertisements, destroying the security of video data and information dissemination effect, affecting the user experience of legitimate users.

Method used

By receiving the terminal's incentive task request and encryption unlock request, generating and sending authorization information, encrypting unlock requests using the key generation rules and key factors, isolating the encryption/decryption methods of different incentive events, and increasing the difficulty of cracking.

Benefits of technology

It improves the security of incentive carriers, filters out invalid requests from illegal users, saves server resources, and ensures the normal usage experience of legal users.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115115384B_ABST
    Figure CN115115384B_ABST
Patent Text Reader

Abstract

The present application provides a method, device, electronic device and computer-readable storage medium for processing an incentive event; the method includes: receiving an incentive task request corresponding to an incentive event sent by a terminal, and sending an incentive task to the terminal according to the incentive task request; receiving an encrypted unlock request corresponding to the incentive event sent by the terminal, wherein the encrypted unlock request is generated based on the incentive event after the terminal executes the incentive task; decrypting the encrypted unlock request based on the incentive event to obtain an unlock request, and performing an unlock operation on the unlock request to obtain authorization information; sending the authorization information to the terminal, wherein the authorization information is used for the terminal to execute the authorized incentive carrier fragment in the incentive carrier. Through the present application, the difficulty of cracking the incentive event can be increased, thereby improving the security of data related to the incentive event.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of Internet technology, and in particular to a method, device, electronic device and computer-readable storage medium for processing a stimulus event. Background Art

[0002] The Internet is an important channel for information dissemination. Applying incentive mechanisms on the Internet can enhance the effectiveness of information dissemination. Taking online videos as an example, when a user finishes watching an advertisement pushed to the user by the advertising system, he or she will be given the right to play a video clip as an incentive.

[0003] However, illegal users (such as hackers) can play any clip in the video by skipping the advertisement, which destroys the security of video data and the effect of information dissemination, and at the same time causes a large amount of invalid occupation of video server resources, seriously affecting the user experience of legitimate users. Summary of the invention

[0004] The embodiments of the present application provide a method, device, electronic device and computer-readable storage medium for processing a stimulus event, which can increase the difficulty of cracking the stimulus event, thereby improving the security of data related to the stimulus event.

[0005] The technical solution of the embodiment of the present application is implemented as follows:

[0006] The present application provides a method for processing an incentive event, including:

[0007] Receiving an incentive task request corresponding to an incentive event sent by a terminal, and sending an incentive task to the terminal according to the incentive task request;

[0008] Receiving an encrypted unlocking request corresponding to the incentive event and sent by the terminal, wherein the encrypted unlocking request is generated by the terminal based on the incentive event after executing the incentive task;

[0009] Decrypting the encrypted unlock request based on the stimulus event to obtain an unlock request, and performing an unlock operation on the unlock request to obtain authorization information;

[0010] The authorization information is sent to the terminal, wherein the authorization information is used for the terminal to execute the authorized incentive carrier segment in the incentive carrier.

[0011] In the above scheme, the generation of the key based on the key generation rule and the key factor includes: obtaining key information and signature information, wherein the key information includes at least one of the following: user account, device account; when the key generation rule is the first encryption rule, encrypting the key factor and the key information to generate the key; when the key generation rule is the second encryption rule, encrypting the key factor, the key information and the signature information to generate the key.

[0012] In the above scheme, obtaining the secret key factor based on the request identifier includes: querying a database based on the request identifier to obtain the secret key factor corresponding to the request identifier; wherein the database is used to store the correspondence between the secret key factor generated by the server according to different stimulus events and the request identifier.

[0013] In the above scheme, the method also includes: when the unlocking operation is successfully performed for the unlocking request, deleting the secret key factor corresponding to the incentive event; when the incentive task request sent by the terminal is received and the encrypted unlocking request sent by the terminal is not received, deleting the secret key factor corresponding to the incentive event after a preset time period.

[0014] The present application provides a device for processing a stimulus event, including:

[0015] A receiving module, used for receiving an incentive task request corresponding to an incentive event sent by a terminal;

[0016] A sending module, used for sending the incentive task to the terminal according to the incentive task request;

[0017] The receiving module is further configured to receive an encrypted unlocking request corresponding to the incentive event, wherein the encrypted unlocking request is generated by the terminal based on the incentive event after the terminal executes the incentive task;

[0018] A decryption module, configured to decrypt the encrypted unlocking request based on the stimulus event to obtain an unlocking request;

[0019] An unlocking module, used to perform an unlocking operation on the unlocking request and obtain authorization information;

[0020] The sending module is further used to send the authorization information to the terminal, wherein the authorization information is used for the terminal to execute the authorized incentive carrier segment in the incentive carrier.

[0021] In the above scheme, the device also includes an extraction module, which is used to extract the request identifier corresponding to the incentive event from the incentive task request, wherein the request identifiers corresponding to different incentive events are different; the sending module is also used to send the request identifier and the incentive task to the terminal, wherein the request identifier is used to characterize that the incentive task is used to respond to the incentive task request.

[0022] In the above scheme, the device also includes a generating module, which is used to generate a secret key factor corresponding to the stimulus event, wherein the secret key factor generated for different stimulus events is different; the sending module is also used to send the secret key factor to the terminal, wherein the secret key factor is used for the terminal to encrypt the request information required to perform the unlocking operation to obtain the encrypted unlocking request.

[0023] In the above scheme, the encrypted unlocking request includes an encrypted obfuscation request, a request identifier and encryption policy parameters; the decryption module is also used to search the encryption policy table based on the encryption policy parameters to obtain the encryption policy corresponding to the stimulus event, and the encryption policy includes a key generation rule and an obfuscation rule; based on the obfuscation rule, the encrypted obfuscation request is deobfuscated to obtain an encrypted unlocking request; the generation module is also used to obtain a key factor based on the request identifier, and generate a key based on the key generation rule and the key factor; the decryption module is also used to decrypt the encrypted unlocking request based on the key to obtain an unlocking request.

[0024] In the above scheme, the generation module is also used to obtain key information and signature information, wherein the key information includes at least one of the following: user account, device account; when the key generation rule is the first encryption rule, the key factor and the key information are encrypted to generate a key; when the key generation rule is the second encryption rule, the key factor, the key information and the signature information are encrypted to generate a key.

[0025] In the above scheme, the device also includes an update module, which is used to update the encryption policy when at least one of the following conditions is met: reaching the automatic update cycle; receiving an instruction to trigger the update of the encryption policy; the encryption policy is cracked.

[0026] In the above scheme, the decryption module is also used to query the database based on the request identifier to obtain the secret key factor corresponding to the request identifier; wherein the database is used to store the corresponding relationship between the secret key factor generated by the server according to different stimulus events and the request identifier.

[0027] In the above scheme, the unlocking module is also used to extract the request information carried in the unlocking request, wherein the request information includes the user account, the incentive carrier, and the identifier of the incentive carrier fragment to be authorized in the incentive carrier; based on the identifier, the incentive carrier fragment is determined from the incentive carrier; an unlocking operation is performed on the unlocking request of the user account for the incentive carrier fragment, and authorization information for executing the incentive carrier fragment as the user account is obtained.

[0028] In the above scheme, the device also includes a deletion module, which is used to delete the secret key factor corresponding to the incentive event when the unlocking operation is successfully performed for the unlocking request; when the incentive task request sent by the terminal is received and the encrypted unlocking request sent by the terminal is not received, the secret key factor corresponding to the incentive event is deleted after a preset time period.

[0029] The present application embodiment provides another method for processing a stimulus event, including:

[0030] Sending an incentive task request corresponding to an incentive event to a server, and receiving an incentive task sent by the server according to the incentive task request;

[0031] Execute the incentive task, and send an encrypted unlocking request generated based on the incentive event to the server;

[0032] receiving authorization information sent by the server according to the encrypted unlocking request;

[0033] The authorization information is generated by the server performing a decryption operation on the encrypted unlock request based on the incentive event to obtain an unlock request, and performing an unlock operation on the unlock request;

[0034] The authorized incentive carrier segment in the incentive carrier is executed according to the authorization information.

[0035] In the above scheme, the encryption policy parameters include: security algorithm parameters and encryption policy version parameters; the encryption policy includes: encryption algorithm type, key generation rules and obfuscation rules; the encryption policy table is searched based on the encryption policy parameters to obtain the encryption policy corresponding to the stimulus event, including: searching the encryption policy table according to the security algorithm parameters to obtain the corresponding encryption algorithm type; searching the encryption policy table based on the encryption policy version parameters to obtain the corresponding key generation rules and obfuscation rules.

[0036] In the above scheme, before sending the incentive task request to the server, the method further includes: generating a request identifier corresponding to the incentive event, wherein different incentive events correspond to different request identifiers; and generating the incentive task request carrying the request identifier.

[0037] The present application embodiment provides another device for processing a stimulus event, including:

[0038] A sending module, used for sending an incentive task request corresponding to an incentive event to a server;

[0039] A receiving module, used for receiving the incentive task sent by the server according to the incentive task request;

[0040] An execution module, used for executing the incentive task;

[0041] The sending module is further used to send an encrypted unlocking request generated based on the incentive event to the server;

[0042] The receiving module is further configured to receive authorization information sent by the server according to the encrypted unlocking request; wherein the authorization information is generated by the server performing a decryption operation on the encrypted unlocking request based on the incentive event to obtain an unlocking request, and performing an unlocking operation on the unlocking request;

[0043] The execution module is further used to execute the authorized incentive carrier segment in the incentive carrier according to the authorization information.

[0044] In the above scheme, the device also includes a generation module for generating request information required to perform the unlocking operation; the device also includes an encryption module for obtaining an encryption policy from the server, performing an encryption operation on the request information based on the encryption policy, and obtaining an encrypted unlocking request.

[0045] In the above scheme, the encryption module is also used to obtain encryption policy parameters corresponding to the incentive event from the server; search the encryption policy table based on the encryption policy parameters to obtain the encryption policy corresponding to the incentive event; wherein the encryption policy parameters corresponding to different incentive events are different; wherein the server updates the encryption policy in the following ways: periodic automatic update; manually triggered update; update when the encryption policy is cracked.

[0046] In the above scheme, the encryption policy parameters include: security algorithm parameters and encryption policy version parameters; the encryption policy includes: encryption algorithm type, key generation rules and obfuscation rules; the encryption module is also used to search the encryption policy table according to the security algorithm parameters to obtain the corresponding encryption algorithm type; search the encryption policy table based on the encryption policy version parameters to obtain the corresponding key generation rules and obfuscation rules.

[0047] In the above scheme, the encryption strategy includes key generation rules and obfuscation rules; the encryption module is also used to generate a key based on the key generation rules and the key factor; the request information is encrypted based on the key to obtain encrypted request information; the encrypted request information is obfuscated based on the obfuscation rules to obtain obfuscated encrypted request information; a combined operation is performed based on the obfuscated encrypted request information, the request identifier and the encryption strategy to obtain an encrypted unlocking request.

[0048] In the above scheme, the receiving module is also used to receive the request identifier sent by the server according to the incentive task request, and the secret key factor corresponding to the incentive event; wherein the request identifier is extracted by the server from the incentive task request, and the secret key factor is generated by the server according to the incentive event, and the secret key factors corresponding to different incentive events are different.

[0049] In the above solution, the generating module is further used to generate a request identifier corresponding to the stimulus event, wherein different stimulus events correspond to different request identifiers; and generate a stimulus task request carrying the request identifier.

[0050] An embodiment of the present application provides an electronic device, including:

[0051] A memory for storing executable instructions;

[0052] The processor is used to implement the method for processing the stimulus event provided in the embodiment of the present application when executing the executable instructions stored in the memory.

[0053] The embodiment of the present application provides a computer-readable storage medium storing executable instructions for causing a processor to execute and implement the method for processing a stimulus event provided in the embodiment of the present application.

[0054] The embodiments of the present application have the following beneficial effects:

[0055] By matching the encryption and decryption methods of the unlock request with the incentive event, the encryption / decryption methods of different incentive events are isolated from each other, making it difficult for illegal users to obtain the authorization information of all incentive carrier fragments through a single crack, thereby giving up frequent requests for incentive carrier fragments. On the one hand, this ensures the security of the incentive carrier, and on the other hand, it saves the resources of the relevant servers by filtering out invalid requests from illegal users. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] Figure 1 It is a schematic diagram of the architecture of the system for processing incentive events provided in an embodiment of the present application;

[0057] Figure 2is a schematic diagram of the structure of the server 200 provided in an embodiment of the present application;

[0058] Figure 3 is a schematic diagram of the structure of the terminal 400 provided in an embodiment of the present application;

[0059] Figure 4 It is a flowchart of a method for processing an incentive event provided in an embodiment of the present application;

[0060] Figure 5 It is a flowchart of a method for processing an incentive event provided in an embodiment of the present application;

[0061] Figure 6 It is a flowchart of a method for processing an incentive event provided in an embodiment of the present application;

[0062] Figure 7 It is a flowchart of two stimulus event cross requests provided in an embodiment of the present application. DETAILED DESCRIPTION

[0063] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings. The described embodiments should not be regarded as limiting the present application. All other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of this application.

[0064] In the following description, reference is made to “some embodiments”, which describe a subset of all possible embodiments, but it can be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0065] In the following description, the terms "first\second" involved are merely used to distinguish similar objects and do not represent a specific ordering of the objects. It can be understood that "first\second" can be interchanged with a specific order or sequence where permitted, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein.

[0066] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0067] Before further describing the embodiments of the present application in detail, the nouns and terms involved in the embodiments of the present application are explained. The nouns and terms involved in the embodiments of the present application are subject to the following interpretations.

[0068] 1) Incentive Task: A task mode where users can receive corresponding rewards after completing specific tasks. For example, if the incentive task is an incentive advertisement, users need to watch the incentive advertisement before they can obtain the playback permission of the incentive video clip.

[0069] 2) Incentive carrier segment: a segment of the incentive carrier, each segment is used as a reward for completing an incentive task. For example: for incentive videos, video segments are the basic unit of user rewards; for incentive e-books, e-book chapters are the basic unit of user rewards; for incentive games, different maps and tasks of the game are the basic units of user rewards.

[0070] 3) Incentive event: the complete processing flow related to an incentive task, including sending an incentive task request, executing the incentive task, and obtaining authorization information. Taking the incentive carrier as an incentive video as an example, the complete process of the corresponding incentive event includes requesting ads, watching ads, and unlocking videos.

[0071] 4) Secret key factor: the variable used to generate the secret key.

[0072] 5) Supply Side Platform (SSP): an advertising platform that serves the media side.

[0073] In the application scenario of rewarded advertising, the prerequisite for successfully unlocking the rewarded video is that the user must finish watching the rewarded ad. That is, the user must first watch the rewarded ad before obtaining the playback permission of the rewarded video.

[0074] However, in the solution provided by the related technology, since the unlock request is not encrypted, illegal users (such as hackers) can easily simulate advertising requests and unlock requests during the incentive event, thereby obtaining authorization information for playing the incentive video without exposing the incentive advertisement, which affects the security of the data. At the same time, the requests of illegal users will also cause unnecessary occupation of the resources of the video server, affecting the normal usage experience of legitimate users.

[0075] In view of the above technical problems, the embodiments of the present application provide a method, device, electronic device and computer-readable storage medium for processing incentive events, which can increase the difficulty of cracking incentive events, thereby improving the security of data related to incentive events. The following describes an exemplary application of the electronic device provided by the embodiments of the present application. The electronic device provided by the embodiments of the present application can be implemented as a terminal, or as a server, or implemented by a terminal and a server in collaboration. Below, the method for processing incentive events provided by the embodiments of the present application in collaboration with a terminal and a server is used as an example for description.

[0076] See also Figure 1 , Figure 11 is a schematic diagram of the architecture of a system 100 for processing stimulus events provided in an embodiment of the present application. Figure 1 As shown, the stimulus event processing system 100 includes: a server 200, a network 300 and a terminal 400, which are described below respectively.

[0077] The server 200 is used to receive the incentive task request corresponding to the incentive event sent by the terminal 400, and send the corresponding incentive task to the terminal 400 according to the received incentive task request. The server 200 is also used to receive the encrypted unlocking request corresponding to the incentive event sent by the terminal 400, and decrypt the received encrypted unlocking request based on the incentive event to obtain the unlocking request, and perform the unlocking operation on the unlocking request to obtain the authorization information; then, the server 200 sends the obtained authorization information to the terminal 400 through the network 300.

[0078] The network 300 is used to connect the server 200 and the terminal 400, and may be a wide area network or a local area network, or a combination of the two.

[0079] A client 410 runs on the terminal 400. The client 410 can be various types of clients. For example, when the incentive carrier is a video, the client 410 can be a video client; when the incentive carrier is a game, the client 410 can be various types of game clients; when the incentive carrier is an e-book, the client 410 can be an e-book reading client; when the incentive carrier is news, the client 410 can be a news client.

[0080] The terminal 400 is used to send an incentive task request corresponding to an incentive event to the server 200, and receive an incentive task sent by the server 200 according to the incentive task request; then, the terminal 400 executes the incentive task, and after executing the incentive task, sends an encrypted unlocking request generated based on the incentive event to the server 200. The terminal 400 is also used to receive authorization information sent by the server 200 according to the encrypted unlocking request, and execute the authorized incentive carrier segment in the incentive carrier according to the authorization information.

[0081] For example, when the incentive carrier is a video, the incentive carrier fragment can be a segment of the video; when the incentive carrier is an e-book, the incentive carrier fragment can be a chapter of the e-book; when the incentive carrier is a game, the incentive carrier fragment can be a task or a level in the game.

[0082] In some embodiments, the server 200 may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The terminal 400 may be a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, a smart TV, etc., but is not limited thereto. The terminal 400 and the server 200 may be directly or indirectly connected via wired or wireless communication, which is not limited in the embodiments of the present application.

[0083] Below Figure 1 The structure of the server 200 shown in FIG. Figure 2 , Figure 2 is a schematic diagram of the structure of the server 200 provided in an embodiment of the present application, Figure 2 The server 200 shown includes: at least one processor 210, a memory 240, and at least one network interface 220. The various components in the server 200 are coupled together via a bus system 230. It is understood that the bus system 230 is used to achieve connection and communication between these components. In addition to the data bus, the bus system 230 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, the bus system 230 is not described in detail. Figure 2 Various buses are labeled as bus system 230 .

[0084] The processor 210 can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., where the general-purpose processor can be a microprocessor or any conventional processor, etc.

[0085] The memory 240 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state memory, hard disk drives, optical disk drives, etc. The memory 240 may optionally include one or more storage devices that are physically remote from the processor 210.

[0086] The memory 240 includes a volatile memory or a non-volatile memory, and may also include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), and the volatile memory may be a random access memory (RAM). The memory 240 described in the embodiments of the present application is intended to include any suitable type of memory.

[0087] In some embodiments, memory 240 can store data to support various operations, examples of which include programs, modules, and data structures, or a subset or superset thereof, as exemplarily described below.

[0088] Operating system 241, including system programs for processing various basic system services and performing hardware-related tasks, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and processing hardware-based tasks;

[0089] A network communication module 242, used to reach other computing devices via one or more (wired or wireless) network interfaces 220, exemplary network interfaces 220 include: Bluetooth, Wireless Compatibility Certification (WiFi), and Universal Serial Bus (USB);

[0090] In some embodiments, the stimulus event processing device provided in the embodiments of the present application may be implemented in software. Figure 2 The processing device 243 of the stimulus event stored in the memory 240 is shown, which can be software in the form of a program and a plug-in, etc., including the following software modules: a receiving module 2431, a sending module 2432, a decryption module 2433, an unlocking module 2434, an extraction module 2435, a generation module 2436, an update module 2437 and a deletion module 2438. These modules are logical, and therefore can be arbitrarily combined or further split according to the functions implemented. It should be pointed out that in Figure 2 For the sake of convenience, all the above modules are shown at once, but it should not be considered that the processing device 243 for the excitation event excludes the implementation that can only include the receiving module 2431, the sending module 2432, the decryption module 2433 and the unlocking module 2434. The functions of each module will be explained below.

[0091] In other embodiments, the processing device for the stimulus event provided in the embodiments of the present application can be implemented in hardware. As an example, the device provided in the embodiments of the present application can be a processor in the form of a hardware decoding processor, which is programmed to execute the processing method for the stimulus event provided in the embodiments of the present application. For example, the processor in the form of a hardware decoding processor can adopt one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field programmable gate arrays (FPGAs) or other electronic components.

[0092] Next, continue Figure 1 The structure of the terminal 400 in FIG. Figure 3 , Figure 3 4 is a schematic diagram of the structure of the terminal 400 provided in the embodiment of the present application. Figure 3 As shown, the structure of the terminal 400 includes: a memory 450 for storing executable instructions; a processor 410 for executing the executable instructions stored in the memory 450 to implement the method for processing the stimulus event provided in the embodiment of the present application. In addition, the stimulus event processing device 455 stored in the memory 450 includes the following software modules: a sending module 4551, a receiving module 4552, an execution module 4553, a generation module 4554 and an encryption module 4555. The functions of each module will be described below. In addition, as Figure 3 As shown, the structure of the terminal 400 also includes a network interface 420, a user interface 430 (the user interface 430 includes one or more output devices 431 that enable the presentation of media content, including one or more speakers and / or one or more visual display screens. The user interface 430 also includes one or more input devices 432, including user interface components that facilitate user input, such as a keyboard, a mouse, a microphone, a touch screen display, a camera, other input buttons and controls) and a bus system 440. In addition, the memory 450 also stores an operating system 451, a network communication module 452, a presentation module 453 (for enabling the presentation of information via one or more output devices 431 associated with the user interface 430) and an input processing module 454 (for detecting one or more user inputs or interactions from one of the one or more input devices 432 and translating the detected inputs or interactions). The functions of the above components are similar to those of the present invention. Figure 2 The corresponding components in the function are similar, please refer to Figure 2The description of the embodiments of the present application will not be repeated here.

[0093] The following is an explanation of the processing method of the incentive event provided by the embodiment of the present application from the perspective of the interaction between the terminal and the server. It should be noted that for the steps on the terminal side, the terminal can be implemented by running a computer program, wherein the computer program can be a native program or software module in the operating system; it can be a local (Native) application (APP, APPlication), that is, a program that needs to be installed in the operating system to run, such as a video client, etc.; it can also be a browser that displays video pages or game pages in the form of a web page; it can also be a video applet or a game applet that can be embedded in any APP. In short, the above-mentioned computer program can be an application, module or plug-in in any form.

[0094] See also Figure 4 , Figure 4 is a flowchart of a method for processing an incentive event provided in an embodiment of the present application, which will be combined with Figure 4 The steps shown are explained.

[0095] In step S101, the terminal sends an incentive task request corresponding to an incentive event to the server.

[0096] In some embodiments, when the terminal receives a trigger operation (such as a click operation or a long press operation, etc.) from a user for a stimulus event displayed in the human-computer interaction interface, a stimulus task request corresponding to the stimulus event is sent to the server.

[0097] For example, taking the incentive task as an incentive advertisement, an incentive event is displayed in the human-computer interaction interface of the terminal (for example, an incentive event of obtaining the right to watch the incentive video by watching the incentive advertisement). When the terminal receives a trigger operation from the user for the incentive event (for example, receiving a click operation from the user on the "Watch Ad to Unlock Video" button displayed in the human-computer interaction interface), an incentive advertisement request corresponding to the incentive event is sent to the server to request the server to return the incentive advertisement to the terminal.

[0098] For example, taking the incentive task as a sharing task, a button for sharing the game is displayed in the interface for starting the game. When the user clicks on the sharing button, the terminal sends a sharing task request to the server. That is to say, the user first needs to share the game with other users (for example, recommend it to friends, or post and comment on it in the circle of friends, etc.) before starting the game or continuing to the next round in the game.

[0099] In other embodiments, see Figure 5 , the terminal is executing Figure 4Before step S101 shown in the figure, you can also perform Figure 5 Steps S107 and S108 shown in FIG. Figure 5 Step S107 and step S108 are shown for explanation.

[0100] In step S107, the terminal generates a request identifier corresponding to the stimulus event.

[0101] In some embodiments, for different stimulus events, the terminal may generate a unique corresponding request identifier, that is, different stimulus events correspond to different request identifiers.

[0102] For example, the terminal can use a universally unique identifier (UUID) as the request identifier corresponding to the incentive event. For example, for each incentive event, the terminal can perform a hash calculation on the sending time of the incentive task request in the incentive event to obtain the corresponding time-based UUID, and use the obtained time-based UUID as the request identifier corresponding to the incentive event. Since the UUID is randomly generated based on time, its uniqueness can be guaranteed. In this way, by using the UUID as the request identifier corresponding to the incentive event, different incentive events can be distinguished to avoid mutual interference between different incentive events.

[0103] In step S108, the terminal generates an incentive task request carrying a request identifier.

[0104] In some embodiments, after generating a unique request identifier corresponding to the stimulus event, the terminal sends a stimulus task request carrying the request identifier to the server.

[0105] For example, taking the incentive event A as an example, before the terminal sends the incentive task request corresponding to the incentive event A to the server, it generates a unique request identifier B corresponding to the incentive event A (for example, the UUID corresponding to the incentive event A). Then, when the terminal receives the user's trigger operation for the incentive event displayed in the human-computer interaction interface, it generates an incentive task request carrying the request identifier B and sends the incentive task request carrying the request identifier B to the server.

[0106] It should be noted that, in actual applications, the request identifier can be sent to the server at the same time as the incentive task request, or it can be sent successively with the incentive task request, for example, the incentive task request is sent first, and then the request identifier is sent; or, the request identifier is sent first, and then the incentive task request is sent. This application does not make specific limitations on this.

[0107] Next, continue to combine Figure 4 To explain, in step S102, the server sends an incentive task to the terminal.

[0108] In some embodiments, the server may send the incentive task to the terminal in the following manner: extracting a request identifier corresponding to the incentive event from the incentive task request; and sending the request identifier and the incentive task to the terminal.

[0109] For example, taking the incentive task as an incentive advertisement, when the server receives an incentive advertisement request for incentive event A sent by the terminal, it first extracts the request identifier (such as request identifier B) corresponding to incentive event A from the incentive advertisement request; then, the server requests the incentive advertisement from the advertising server, and after receiving the incentive advertisement returned by the advertising server, it sends the incentive advertisement and request identifier B to the terminal. In this way, by carrying request identifier A in the incentive advertisement request, request identifier A can be used to indicate that the incentive advertisement is used to respond to the incentive advertisement request in incentive event B, rather than to respond to other incentive events, thereby avoiding cross-interference between different incentive events.

[0110] In other embodiments, when the server sends an incentive task to the terminal according to the incentive task request, it can also perform the following operations: generate a secret key factor corresponding to the incentive event, wherein the secret key factor is used for the terminal to encrypt the request information required to perform the unlocking operation to obtain an encrypted unlocking request.

[0111] For example, still taking the incentive task as an incentive advertisement, when the server receives an incentive advertisement request sent by the terminal corresponding to the incentive event, the server sends an advertisement request to the advertisement server to obtain the incentive advertisement requested by the terminal from the advertisement server; the server can also generate a secret key factor corresponding to the incentive event, for example, the server can use a random string generator and use the generated random string as the secret key factor corresponding to the incentive event; or, the server can also use the UUID obtained by hashing the name of the incentive event as the secret key factor corresponding to the incentive event, wherein the secret key factor generated by the server can be used for the terminal to encrypt the request information required to perform an unlocking operation (for example, an unlocking operation for an incentive video clip) to obtain an encrypted unlocking request.

[0112] It should be noted that the key factors corresponding to different incentive events may be the same or different. For example, the server may generate a unique key factor for each incentive event, or may generate the same key factor for each incentive event (when the key factors of each incentive event are the same, different encryption strategies may be used for subsequent encryption, so that the keys finally generated are also different), or may generate the same key factor for some incentive events, for example, the key factors corresponding to incentive event A and incentive event B are the same, but different from the key factor of incentive event C. This embodiment of the present application does not limit this.

[0113] In some embodiments, when the server sends an incentive task to the terminal, it may also send a request identifier and a key factor corresponding to the incentive event to the terminal; wherein the request identifier is extracted from the incentive task request, the key factor is generated by the server according to the incentive event, and different incentive events correspond to different key factors.

[0114] For example, taking the incentive task as an incentive advertisement, when the server receives the incentive advertisement request corresponding to the incentive event sent by the terminal, it first extracts the request identifier (such as request identifier A) carried in the incentive advertisement request, then generates a unique secret key factor B corresponding to the incentive event, and then obtains the incentive advertisement corresponding to the incentive advertisement request, and finally sends the request identifier A, secret key factor B and the obtained incentive advertisement to the terminal. In other words, since the secret key factor corresponds to the incentive event one by one, that is, a secret key factor is only valid within a corresponding incentive event, even if a secret key factor is leaked, it will not affect the security of the relevant data of other incentive events.

[0115] In step S103, the terminal sends an encrypted unlocking request corresponding to the stimulus event to the server.

[0116] In some embodiments, when the terminal completes the incentive task, it generates request information required to perform the unlocking operation; then, it obtains the encryption strategy from the server, encrypts the request information based on the encryption strategy, and obtains an encrypted unlocking request. Subsequently, the terminal sends the obtained encrypted unlocking request to the server.

[0117] For example, taking the incentive event of unlocking an incentive video by watching an incentive ad as an example, after the terminal finishes playing the incentive ad, it obtains the request information required to perform the incentive video unlocking operation (such as the user account, the incentive video, and the identifier of the video clip to be authorized in the incentive video, etc.); then, the terminal obtains the encryption policy from the server, and encrypts the request information based on the encryption policy to obtain an encrypted unlocking request for the incentive video. Subsequently, the terminal sends the encrypted unlocking request to the server. In this way, by encrypting the unlocking request, the cost of illegal users bypassing the exposure of the incentive ad and directly obtaining the viewing rights of the incentive video is increased, thereby ensuring the security of the incentive video.

[0118] It should be noted that in actual applications, the terminal can generate request information required for performing the unlocking operation during the execution of the incentive task, and obtain the encryption strategy from the server, encrypt the request information based on the encryption strategy, and obtain an encrypted unlocking request, so as to send the encrypted unlocking request generated based on the incentive event to the server after completing the incentive task; of course, the terminal can also generate the request information required for performing the unlocking operation after completing the incentive task, and obtain the encryption strategy from the server, encrypt the request information based on the encryption strategy, and obtain an encrypted unlocking request, and then send the obtained encrypted unlocking request to the server. The embodiments of the present application do not make specific limitations on this.

[0119] In some embodiments, following the above example, the terminal can obtain the encryption policy from the server in the following ways: obtain the encryption policy parameters corresponding to the incentive event from the server; search the encryption policy table based on the encryption policy parameters to obtain the encryption policy corresponding to the incentive event; wherein different incentive events correspond to different encryption policy parameters; wherein the server updates the encryption policy in the following ways: periodic automatic update; manually triggered update; update when the encryption policy is cracked.

[0120] For example, taking the incentive event A as an example, the terminal obtains the unique encryption policy parameter B corresponding to the incentive event A from the server (for example, it can be the same server as the one that receives the incentive task request, or a configuration center server specifically used to generate encryption policies), and then searches the encryption policy table based on the obtained encryption policy parameter B to obtain the encryption policy corresponding to the incentive event A. Since the encryption policies corresponding to different incentive events are different, the secret keys generated in the end are also different, that is, a secret key is only valid within a corresponding incentive event, so even if a secret key is leaked, since the secret keys used by other incentive events are different from the leaked secret keys, it will not affect the security of the relevant data of other incentive events.

[0121] It should be noted that in order to further ensure the security of incentive events, for incentive event A, the server can randomly generate a unique secret key factor corresponding to incentive event A, and the server will also periodically update the encryption policy, for example, once every day, or when receiving an update instruction triggered by the administrator, the server updates the encryption policy, or when it detects that the encryption policy has been cracked, the server updates the encryption policy. In this way, by randomly generating secret key factors and updating the encryption policy in real time, the difficulty of cracking the incentive event is further increased, thereby further improving the security of data related to the incentive event.

[0122] In other embodiments, when the encryption policy parameters include security algorithm parameters and encryption policy version parameters, and the encryption policy includes encryption algorithm type, key generation rules and obfuscation rules, the terminal implements the above-mentioned search for the encryption policy table based on the encryption policy parameters in the following manner to obtain the encryption policy corresponding to the stimulus event: search the encryption policy table according to the security algorithm parameters to obtain the corresponding encryption algorithm type; search the encryption policy table based on the encryption policy version parameters to obtain the corresponding key generation rules and obfuscation rules.

[0123] For example, taking the incentive event A as an example, after the terminal obtains the encryption policy parameters corresponding to the incentive event A from the configuration center server, the terminal searches the encryption policy table (for example, the encryption policy table stored in the configuration center server) based on the security algorithm parameters included in the encryption policy parameters to obtain the corresponding encryption algorithm type. For example, when the security algorithm parameter is 2, the corresponding encryption algorithm type is symmetric encryption, such as the Advanced Encryption Standard (AES) algorithm; when the security algorithm parameter is 3, the corresponding encryption algorithm type is asymmetric encryption, such as the RSA algorithm, the backpack algorithm, etc.; then, based on the encryption policy version parameter included in the encryption policy parameter, the encryption policy table is searched to obtain the corresponding key generation rule and obfuscation rule. For example, when the encryption policy version is 1.1, the corresponding key generation rule is to encrypt the key factor and the device ID (for example, using the message digest algorithm 5 (MD5, Message-Digest Algorithm 5) Encrypt the key factor and device ID) to generate a key; the obfuscation rule is to perform a circular left shift of N bits on the string obtained after encryption (i.e., the key), where N is a positive integer greater than or equal to 1; when the encryption policy version is 1.2, the corresponding key generation rule is to perform encryption based on the key factor, device ID, and signature information to generate a key; the obfuscation rule is to perform a circular right shift of M bits on the string obtained after encryption or to insert irrelevant characters at predetermined positions (for example, for the string obtained after encryption, insert irrelevant new characters every 5 characters), where M is a positive integer greater than or equal to 1.

[0124] It should be noted that when the security algorithm parameter is the default value (for example, when the security algorithm parameter is 1), the corresponding encryption algorithm type can be empty, which means no encryption; when the encryption policy version parameter is the default value (for example, when the encryption policy version is 1.0), the corresponding encryption rule type can be empty, which means that the encryption rule is not adopted and the key factor is directly used as the key.

[0125] In other embodiments, when the encryption policy includes key generation rules and obfuscation rules, the terminal implements the above-mentioned encryption operation on the request information based on the encryption policy to obtain an encrypted unlocking request in the following manner: generate a key based on the key generation rule and the key factor; perform an encryption operation on the request information based on the key to obtain encrypted request information; perform an obfuscation operation on the encrypted request information based on the obfuscation rule to obtain obfuscated encrypted request information; perform a combined operation based on the obfuscated encrypted request information, the request identifier and the encryption policy to obtain an encrypted unlocking request.

[0126] For example, when the encryption policy obtained by the terminal from the server includes a key generation rule and an obfuscation rule, the terminal first generates a key based on the key generation rule and the key factor. For example, when the key generation rule is the first encryption rule, the terminal uses the MD5 algorithm to encrypt the key factor obtained from the server and the terminal's own device ID to generate a key; when the key generation rule is the second encryption rule, the terminal uses the MD5 algorithm to encrypt the key factor obtained from the server, the terminal's own device ID, and the signature information obtained from the configuration center server to generate a key; then, the terminal performs an encryption operation on the request information based on the key to obtain encrypted request information; then, the terminal performs an obfuscation operation on the encrypted request information based on the obfuscation rule to obtain obfuscated encrypted request information; for example, when the obfuscation rule is the first obfuscation rule, the terminal cyclically shifts the string obtained after the encryption operation (i.e., the encrypted request information) to the left by 5 bits; when the obfuscation rule is the second obfuscation rule, the terminal cyclically shifts the string obtained after the encryption operation to the right by 5 bits; finally, the terminal performs a combined operation based on the obfuscated encrypted request information, the request identifier, and the encryption policy to obtain an encrypted unlocking request. In this way, the unlocking request is encrypted through multiple factors (such as secret key factors, device ID and signature information, etc.), which increases the uncertainty in the encryption process and further increases the difficulty of cracking, thereby improving the security of data related to the incentive event.

[0127] In step S104, the server decrypts the encrypted unlock request based on the stimulus event to obtain an unlock request, and performs an unlock operation on the unlock request to obtain authorization information.

[0128] In some embodiments, the encrypted unlocking request may include an encrypted obfuscation request, a request identifier, and an encryption policy parameter. The server may implement the above-mentioned decryption operation on the encrypted unlocking request based on the incentive event in the following manner: search the encryption policy table based on the encryption policy parameters to obtain the encryption policy corresponding to the incentive event, wherein the encryption policy includes a key generation rule and an obfuscation rule; perform a deobfuscation operation on the encrypted obfuscation request based on the obfuscation rule to obtain an encrypted unlocking request; obtain a key factor based on the request identifier, and generate a key based on the key generation rule and the key factor; perform a decryption operation on the encrypted unlocking request based on the key to obtain an unlocking request.

[0129] For example, taking the incentive event A as an example, after receiving the encrypted unlocking request sent by the terminal, the server searches the encryption policy table (for example, the encryption policy table stored in the configuration center server) based on the encryption policy parameters carried in the encrypted unlocking request to obtain the encryption policy corresponding to the incentive event A; wherein the encryption policy may include a key generation rule and an obfuscation rule; then, the server performs a deobfuscation operation on the encrypted obfuscation request included in the encrypted unlocking request based on the obfuscation rule to obtain the encrypted unlocking request. For example, when the obfuscation rule is to cyclically shift the string obtained after encryption processing to the left by 5 bits, the server cyclically shifts the encrypted obfuscation request to the right by 5 bits to obtain the encrypted unlocking request; then, the server obtains the key factor corresponding to the request identifier from the database based on the request identifier carried in the encrypted unlocking request, and generates a key based on the key generation rule and the obtained key factor; finally, the server performs a deobfuscation operation on the encrypted unlocking request obtained after the deobfuscation operation based on the generated key to obtain an unlocking request.

[0130] In other embodiments, following the above examples, the server can implement the above-mentioned key generation based on key generation rules and key factors in the following manner: obtain key information and signature information from the configuration center server; wherein the key information includes at least one of the following: user account, device account; when the key generation rule is the first encryption rule, encrypt the key factor and the key information to generate the key; when the key generation rule is the second encryption rule, encrypt the key factor, the key information and the signature information to generate the key.

[0131] For example, after receiving the encryption unlocking request sent by the terminal, the server extracts the encryption policy parameters from the encryption unlocking request, and searches for the corresponding encryption policy from the encryption policy table stored in the configuration center server based on the extracted encryption policy parameters, wherein the encryption policy includes a key generation rule. Then, the server obtains relevant information from the configuration center server based on the key generation rule. For example, when the key generation rule is the first encryption rule, the server obtains key information (such as user account, device account, etc.) from the configuration center server, and encrypts the key factor and key information to generate a key; when the key generation rule is the second encryption rule, the server obtains key information and signature information from the configuration center server, and encrypts the key factor, key information and signature information to generate a key.

[0132] In some embodiments, the server can obtain the secret key factor in the following manner: query the database based on the request identifier to obtain the secret key factor corresponding to the request identifier; wherein the database is used to store the correspondence between the secret key factor and the request identifier generated by the server according to different stimulus events. It should be noted that the correspondence between the secret key factor and the request identifier stored in the database specifically includes the correspondence between the secret key factor and the request identifier, and the correspondence between the secret key factor and the request identifier. For example, taking the correspondence between the request identifier A and the secret key factor B stored in the database as an example, in actual applications, it can be stored in the form of a key-value pair consisting of the request identifier A and the secret key factor B, in which the request identifier A points to the secret key factor B.

[0133] For example, for each stimulus event, the server can generate a unique corresponding secret key factor, and establish a correspondence between the secret key factor generated by the stimulus event and the request identifier. For example, taking stimulus event A as an example, the server can use the request identifier corresponding to stimulus event A as the key (Key) and the secret key factor (Value) generated for stimulus event A as the value, and use a key-value pair to store the correspondence between the secret key factor generated by stimulus event A and the request identifier. In this way, the correspondence between the secret key factors generated by different stimulus events and the request identifier is stored in the form of key-value pairs, and the server can subsequently quickly find the secret key factor corresponding to the request identifier based on the request identifier.

[0134] In other embodiments, the server may update the encryption policy when at least one of the following conditions is met: reaching an automatic update cycle; receiving an instruction to trigger updating the encryption policy; and the encryption policy is cracked.

[0135] For example, in order to further increase the difficulty of cracking the incentive event and to improve the security of the data related to the incentive event, the server may also update the encryption policy. For example, the server may update the encryption policy every certain period (for example, 1 day); or, when the server receives an update instruction sent by the administrator, the server updates the encryption policy; or, when it detects that the encryption policy has been illegally cracked, the server updates the encryption policy.

[0136] In some embodiments, the server may perform an unlocking operation on the unlocking request and obtain authorization information in the following manner: extract the request information carried in the unlocking request, wherein the request information includes the user account, the incentive carrier, and the identifier of the incentive carrier fragment to be authorized in the incentive carrier; based on the identifier, determine the incentive carrier fragment from the incentive carrier; perform an unlocking operation on the unlocking request of the user account for the incentive carrier fragment, and obtain authorization information for executing the incentive carrier fragment as the user account.

[0137] For example, taking the incentive event of unlocking an incentive video by watching an incentive advertisement as an example, after receiving the encrypted unlock request sent by the terminal, the server first decrypts the encrypted unlock request to obtain an unlock request, and then the server extracts the request information carried in the unlock request, wherein the request information may include the user account (for example, user account A), the incentive video, and the identifier of the incentive video segment to be authorized in the incentive video (for example, identifier B); then, the server determines the incentive video segment from the incentive video based on identifier B, and finally, performs an unlock operation on the unlock request of user account A for the incentive video segment, and obtains authorization information for executing the incentive video segment as user account A, that is, after the unlock operation, user account A has the authority to watch the incentive video segment corresponding to identifier B.

[0138] In some embodiments, in order to prevent the key factor from being reused, after the unlocking operation is successfully performed for the unlocking request, the server may delete the key factor corresponding to the stimulus event.

[0139] For example, taking the stimulus event as stimulus event A, after the unlocking operation is successfully executed for the unlocking request corresponding to stimulus event A, the server can delete the secret key factor corresponding to stimulus event A, thereby avoiding the secret key factor from being reused.

[0140] In other embodiments, in order to avoid the repeated use of the secret key factor, when the server receives an incentive task request sent by the terminal and does not receive an encrypted unlocking request sent by the terminal, the server may also delete the secret key factor corresponding to the incentive event after a preset period of time.

[0141] For example, still taking incentive event A as an example, when the server receives an incentive task request corresponding to incentive event A sent by the terminal, and has not received an encrypted unlocking request corresponding to incentive event A sent by the terminal after a predetermined period of time (for example, 1 hour), the server can delete the secret key factor corresponding to incentive event A.

[0142] In step S105, the server sends authorization information to the terminal.

[0143] In some embodiments, after the server performs an unlocking operation on the unlocking request and obtains corresponding authorization information, the server may return the authorization information to the terminal.

[0144] For example, taking the incentive carrier as an e-book, after the server performs an unlocking operation on the unlocking request of the user account (for example, user account A) for chapter B of the e-book, it obtains the authorization information for executing chapter B in the e-book as user account A, and then the server sends the authorization information to the terminal.

[0145] For example, taking the incentive carrier as a game, after the server performs an unlocking operation on the unlocking request of the user account (for example, user account A) for level B in the game, it obtains the authorization information for executing level B in the game as user account A, and then the server sends the authorization information to the terminal.

[0146] In step S106, the terminal executes the authorized incentive bearer segment in the incentive bearer.

[0147] In some embodiments, after receiving the authorization information sent by the server, the terminal may execute the authorized incentive carrier segment in the incentive carrier based on the authorization information.

[0148] For example, taking the incentive carrier as a game, when the terminal receives the authorization information sent by the server (for example, the authorization information for executing level B in the game as user account A), the screen of level B can be loaded. At this time, user A can initiate a challenge for level B.

[0149] For example, taking the incentive carrier as video, when the terminal receives the authorization information sent by the server (for example, the authorization information for executing the incentive video segment B in the incentive video as user account A), the incentive video segment B in the incentive video is played. At this time, user A can watch the incentive video segment B.

[0150] In other embodiments, the method for processing incentive events provided in the embodiments of the present application can also be implemented in combination with blockchain technology.

[0151] Blockchain is a new application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, encryption algorithm, etc. Blockchain is essentially a decentralized database, a string of data blocks generated by cryptographic methods. Each data block contains a batch of network transaction information, which is used to verify the validity of its information (anti-counterfeiting) and generate the next block. Blockchain can include the underlying blockchain platform, platform product service layer, and application service layer.

[0152] The underlying blockchain platform can include processing modules such as user management, basic services, smart contracts, and operation monitoring. Among them, the user management module is responsible for the identity information management of all blockchain participants, including maintaining public and private key generation (account management), key management, and the maintenance of the correspondence between the user's real identity and the blockchain address (authority management), etc., and, under authorization, supervises and audits the transactions of certain real identities and provides risk control rule configuration (risk control audit); the basic service module is deployed on all blockchain node devices to verify the validity of business requests, and records valid requests to storage after consensus is reached. For a new business request, the basic service first adapts the interface for parsing and authentication (interface adaptation), and then encrypts the business information through the consensus algorithm (consensus management). The smart contract module is responsible for the registration and issuance of contracts, as well as contract triggering and contract execution. Developers can define the contract logic in a programming language and publish it to the blockchain (contract registration). According to the logic of the contract terms, the key or other events are called to trigger the execution and complete the contract logic. It also provides the function of contract upgrade and cancellation. The operation monitoring module is mainly responsible for the deployment, configuration modification, contract setting, cloud adaptation and real-time status visualization output of the product during the product release process, such as alarm, network monitoring, node equipment health monitoring, etc.

[0153] The following takes the example of a server uploading a request identifier and a secret key factor corresponding to an incentive event to a blockchain network for storage to illustrate an exemplary application of a blockchain network.

[0154] First, when the server receives the incentive task request corresponding to the incentive event sent by the terminal, it extracts the request identifier from the incentive task request and generates a secret key factor corresponding to the incentive event; then, the server sends the request identifier and the secret key factor to the blockchain network and generates a corresponding transaction, which includes: the request identifier and the secret key factor for chaining, the sending timestamp of the request identifier and the secret key factor, the smart contract that needs to be called to create the correspondence between the request identifier and the secret key factor, and the parameters passed to the smart contract; the transaction can also include the server's digital certificate, the signed digital signature, and broadcast the transaction to the consensus node in the blockchain network.

[0155] Then, when the consensus node in the blockchain network receives the transaction, it verifies the digital certificate and digital signature carried in the transaction. After successful verification, it confirms whether the server has transaction authority based on the identity of the server carried in the transaction. Any verification error in the digital signature and authority verification will cause the transaction to fail. After successful verification, the consensus node signs its own digital signature (for example, using the node's private key to encrypt the summary of the transaction) and continues to broadcast it in the blockchain network.

[0156] Finally, after receiving the successfully verified transaction, the consensus node in the blockchain network fills the transaction into a new block and broadcasts it. When a consensus node in a blockchain network broadcasts a new block, it verifies the new block, for example, verifies whether the digital signature of the transaction in the new block is valid. If the verification is successful, the new block is appended to the end of the blockchain stored by itself, and the state database is updated according to the transaction results, and the transaction in the new block is executed. For example, for the transaction submitted for the storage request identifier and secret key factor, the consensus node adds a key-value pair with the request identifier as the key and the secret key factor as the value in the state database.

[0157] Taking the example of a server sending a secret key factor query request to a blockchain network, the exemplary application of the blockchain network is further explained.

[0158] In some embodiments, after receiving the encrypted unlocking request corresponding to the incentive event sent by the terminal, the server extracts the request identifier from the encrypted unlocking request, and sends the extracted request identifier to the blockchain network, generating a transaction for querying the secret key factor, so that the consensus node in the blockchain network can execute the transaction to query the secret key factor corresponding to the request identifier from the state database, and return the queried secret key factor to the server. In this way, by storing the request identifier and the secret key factor in the blockchain network, based on the decentralized, distributed storage and tamper-proof characteristics of the blockchain network, the traceability of the corresponding relationship between the request identifier and the secret key factor is ensured, and cross-interference between different incentive events is avoided, further improving the security of the incentive event.

[0159] The method for processing incentive events provided in the embodiment of the present application achieves isolation of the encryption / decryption methods of different incentive events by matching the encryption and decryption methods of the unlock request with the incentive event, making it difficult for illegal users to obtain the authorization information of all incentive carrier fragments through a single cracking, thereby giving up frequent requests for incentive carrier fragments. On the one hand, the security of the incentive carrier is guaranteed, and on the other hand, the resources of the relevant servers are saved by filtering out invalid requests from illegal users.

[0160] Below, taking the incentive carrier as an incentive video as an example, an exemplary application of an embodiment of the present application in an actual application scenario is explained.

[0161] In the application scenario of incentive advertising (i.e., you need to watch the incentive advertising first before you can unlock the viewing rights of the incentive video), the solution provided by the relevant technology does not encrypt the unlocking request. Therefore, illegal users (such as hackers) can easily simulate the advertising requests and unlocking requests during the incentive event, resulting in the viewing rights of the incentive video being obtained without the exposure of the incentive advertising.

[0162] In response to the above technical problems, an embodiment of the present application provides a method for processing incentive events, and the entities involved include: a terminal, an SSP, an advertising service (i.e., an advertising server), a storage service (i.e., a storage server, where the form of data storage may include a database and a file system, etc.) and a configuration center (i.e., a configuration center server).

[0163] Among them, when the SSP receives the incentive advertisement request sent by the terminal, it generates the corresponding secret key factor (for example, the SSP can generate a random string through a random string generator, and use the generated random string as the secret key factor corresponding to the incentive event), and returns the generated secret key factor together with the pulled incentive advertisement to the terminal, so that the terminal uses the secret key factor to encrypt the unlocking request of the incentive video, and sends the encrypted unlocking request to the SSP. The SSP uses the previously generated secret key factor to decrypt the encrypted unlocking request and completes the subsequent unlocking operation. In this way, by generating the secret key factor when pulling the incentive advertisement, the terminal adds an encryption strategy when reporting the unlocking request (that is, the unlocking request is encrypted by the secret key factor generated by the SSP), thereby increasing the difficulty for illegal users to bypass the exposure of the incentive advertisement and directly obtain the viewing permission of the incentive video, effectively improving the security of the incentive video.

[0164] In the method for processing incentive events provided by the embodiment of the present application, the SSP can dynamically and randomly generate secret key factors, and the life cycle of the secret key generated based on the secret key factor is only one complete incentive event (that is, when the incentive event ends, the corresponding secret key will also become invalid); at the same time, an efficient and flexible generation strategy is adopted for the secret key and the encryption result, so that the cost of decryption is higher, and the security of the data can be further guaranteed; in addition, the incentive advertisement pull involved in the same incentive event and the reporting of the unlocking request for the incentive video correspond one to one, and are connected in series through the request identifier (request_id), thereby ensuring that different incentive events do not interfere with each other. In other words, the prerequisite for the successful unlocking of the incentive video is that the incentive task must be completed (for example, the incentive advertisement is watched), otherwise the encryption operation in the unlocking request cannot be completed, and the SSP cannot perform the decryption operation, thus effectively preventing illegal unlocking.

[0165] It should be noted that the method for processing incentive events provided in the embodiment of the present application, in addition to being applicable to incentive advertising scenarios, is applicable to the method for processing incentive events provided in the embodiment of the present application as long as the success of the second request strictly depends on the result of the previous request. This avoids the situation where an illegal user skips the first request (such as an incentive task request) and directly initiates a second request (such as an unlock request for an incentive game) to obtain the corresponding benefits.

[0166] The method for processing incentive events provided in the embodiments of the present application is transparent and imperceptible to legitimate users, and legitimate users do not need to worry about it; however, for illegal users, it is costly to crack the encryption strategy in order to obtain the corresponding plaintext (such as an unlocking request for an incentive video) and then perform an unlocking operation on the plaintext.

[0167] The following is a detailed description of the method for processing the stimulus event provided in the embodiment of the present application.

[0168] For example, see Figure 6 , Figure 6 is a flowchart of a method for processing an incentive event provided in an embodiment of the present application, which will be combined with Figure 6 The steps shown are explained.

[0169] In step S601, the terminal sends an encryption policy pull request to the configuration center.

[0170] In some embodiments, the terminal may send an encryption policy acquisition request to the configuration center to obtain the encryption policy from the configuration center, where the encryption policy may include the encryption algorithm type, key generation rules, and obfuscation rules, etc.

[0171] In step S602, the configuration center returns the encryption policy to the terminal.

[0172] In step S603, the terminal sends an advertisement pull request to the SSP.

[0173] In some embodiments, before sending an advertisement pull request to the SSP, the terminal may first generate a corresponding request identifier. For example, when the terminal receives a click operation from a user on a "Watch Ad Unlock Video" button displayed in the human-computer interaction interface, the terminal generates a request identifier and initiates an advertisement pull request carrying the request identifier to the SSP.

[0174] For example, a field named request identifier (request_id) can be used, which is generated by the terminal and is unique. After generating the request identifier, the terminal will send the request identifier to the SSP in an incentive advertisement request for an incentive event. When the SSP returns the corresponding advertising order information to the terminal, it will also return the request identifier to the terminal. When the user completes the incentive task, such as watching the incentive advertisement, the terminal will initiate an unlock request for the incentive video, and in this request, the request identifier will be returned to the SSP again.

[0175] That is to say, in the same incentive event, the same request identifier is used in multiple interactions between the terminal and the SSP, and different incentive events correspond to different request identifiers. In other words, a request identifier can identify an incentive event, and can also associate the incentive ad request and unlock request in an incentive event.

[0176] In step S604, the SSP requests advertisements from the advertising service.

[0177] For example, after receiving the advertisement pull request sent by the terminal, the SSP requests the corresponding advertisement from the advertisement service.

[0178] In step S605, the advertising service returns the advertising order to the SSP.

[0179] In step S606, the SSP generates and stores a key factor.

[0180] In some embodiments, after generating the key factor, the SSP may store the request identifier and the key factor in a database in the form of a key-value pair.

[0181] In step S607, the SSP returns the key factor to the terminal.

[0182] For example, after receiving the advertising pull request sent by the terminal, in addition to processing the advertising pull logic, the SSP will also generate a secret key factor, and then store the request identifier and the secret key factor in the database in the form of a key-value pair (with the request identifier as the key and the secret key factor as the value). At the same time, the advertising order information, request identifier and secret key factor are returned to the terminal.

[0183] For example, after the terminal sends the request identifier to the SSP, the SSP can use the request identifier generated by the terminal to perform the following operations: use the request identifier as the primary key and the secret key factor generated by the SSP as the value, and the two form a key-value pair, and store the request identifier and the secret key factor in the database; when the SSP receives the encrypted unlocking request in the incentive event sent by the terminal, it can obtain the secret key factor corresponding to the request identifier according to the request identifier carried in the request, and generate a secret key based on the secret key factor to perform a decryption operation.

[0184] In addition, SSP can also use the request identifier to associate the incentive ad request and the unlock request in an incentive event, thereby effectively avoiding pulling an incentive ad once or even directly initiating an unlock request for the incentive video to obtain viewing rights for the incentive video without pulling the incentive ad.

[0185] In step S608, the terminal reports the encryption unlocking request and encryption policy parameters to the SSP.

[0186] For example, after the user has watched the incentive advertisement, the terminal constructs the request information (req) required to unlock the incentive video, such as the user ID, the incentive video, and the identifier of the incentive video segment to be unlocked in the incentive video. Then, the terminal uses the key factor carried in the advertisement reply packet and the encryption policy (including encryption algorithm type, key generation rules, and obfuscation rules, etc.) obtained from the configuration center. For example, the encryption algorithm type and key generation rules in the encryption policy are used to encrypt the key factor and other factors (such as the device ID or the signature information issued by the configuration center), generate a key, and use the generated key to encrypt the request information; then, the obfuscation policy in the encryption policy is used to confuse the encrypted request information. Finally, the terminal reports an encrypted unlocking request to the SSP, which carries the encrypted and obfuscated request information, request identifier, and encryption policy parameters, wherein the encryption policy parameters include security algorithm parameters (alg) and version parameters (version).

[0187] In other embodiments, the terminal encrypts the unlock request based on the generated key, for example, the unlock request is encrypted using the AES algorithm, and after obtaining the binary ciphertext, the base64 algorithm may be used to encrypt it again. Subsequently, the terminal may also perform obfuscation processing on the ciphertext obtained after the re-encryption according to the obfuscation rules in the encryption policy issued by the configuration center, such as salting. The salting processing may be a cyclic shift of the encrypted string or adding irrelevant characters at regular intervals. In this way, the string after the cyclic shift cannot be decrypted into the ciphertext encrypted for the first time (i.e., the encrypted unlock request) with a certain probability, thereby further increasing the complexity of cracking the request plaintext.

[0188] In addition, it should be noted that the secret key involved in the embodiment of the present application is obtained by encrypting the secret key factor (secret_factor) generated by the SSP, the key information issued by the configuration center, such as the user ID, device ID, etc., and the signature information issued by the configuration center, wherein the secret key factor is dynamically and randomly generated by the SSP, thereby ensuring that the subsequently generated secret key is random and cannot be simulated or tried out; at the same time, for different incentive events, when pulling incentive advertisements, the SSP will generate a new and different secret key factor, which also ensures the dynamic update of the secret key.

[0189] In addition, since the key and sign in the factors of generating the secret key are issued by the configuration center, they can be adjusted and take effect in minutes. In other words, even if an illegal user cracks the secret key once, it can only complete one incentive event, or when an illegal user cracks the encryption policy (such as the secret key generation rule), the secret key generation rule can also be changed by the configuration center, making the cracked encryption policy invalid in minutes.

[0190] In step S609, the SSP obtains the corresponding encryption policy from the configuration center according to the encryption policy parameters carried in the encryption unlocking request sent by the terminal.

[0191] In step S6010, the SSP obtains the key factors from the database to construct the key and decrypts it.

[0192] For example, after receiving the encrypted unlocking request sent by the terminal, the SSP queries the secret key factor corresponding to the request identifier from the database through the request identifier carried in the request. Then, based on the encryption policy parameters carried in the request, namely the two parameters alg and version, the SSP obtains the encryption policy corresponding to the incentive event from the configuration center. The encryption policy includes the encryption algorithm type and encryption rules (rule), wherein the encryption rules may also include secret key generation rules (corresponding to the key field) and obfuscation rules (corresponding to the index field). Subsequently, the SSP performs deobfuscation processing on the obfuscated encrypted unlocking request sent by the terminal according to the index field in the encryption rule to obtain the encrypted unlocking request, and generates a secret key according to the key field and the secret key factor in the encryption rule, and uses the generated secret key to decrypt the encrypted unlocking request to obtain the unlocking request in plain text.

[0193] For example, see Table 1, which is an encryption policy table provided in an embodiment of the present application. As shown in Table 1, for different security algorithms and encryption policy versions, the corresponding encryption rules are different. For example, when the security algorithm is 1 and the encryption policy version is 1.01, encryption is not performed by default, and the secret key factor generated by the SSP can be directly used as the secret key; when the security algorithm is 2 and the encryption policy version is 1.1, the corresponding encryption rule is to use the MD5 algorithm to encrypt the secret key factor generated by the SSP and the device ID obtained from the configuration center, and the obfuscation rule (index: 5) is to perform a circular right shift of 5 bits for the string obtained after encryption; when the security algorithm is 2 and the encryption policy version is 1.2, the corresponding encryption rule is to use the MD5 algorithm to encrypt the secret key factor generated by the SSP, and the device ID and signature information obtained from the configuration center, and the obfuscation rule (index: -5) is to perform a circular left shift of 5 bits for the string obtained after encryption.

[0194] Table 1 Encryption strategy table

[0195]

[0196] In step S6011, the SSP returns the point information to the terminal.

[0197] For example, after the SSP decrypts the encrypted unlocking request and obtains the unlocking request, it performs the unlocking operation on the unlocking request and obtains the unlocking point information. For example, the SSP unlocks the viewing permission of user account A for the incentive video segment B. Subsequently, the SSP returns the unlocked point information to the terminal. At this time, user A obtains the playback permission of the incentive video segment B and can continue to watch the incentive video segment B in the incentive video.

[0198] The following is an explanation of the process of cross-requests for different stimulus events.

[0199] For example, see Figure 7 , Figure 7 is a flow chart of two stimulus event cross requests provided in the embodiment of the present application, which will be combined with Figure 7 The steps shown are explained.

[0200] In step S701, the terminal sends an advertisement pull request 1 (eg, update 1) corresponding to stimulus event 1 and carrying a request identifier 1 (eg, request_id=aaa) to the SSP.

[0201] In step S702, the SSP sends the generated random string 1 to the storage service. For example, the SSP generates a random string 1 (for example, str1) for the advertisement pull request 1 sent by the terminal as a secret key factor corresponding to the stimulus event 1, and sends the generated random string 1 to the storage service so that the storage service stores the correspondence between the random string 1 and the request identifier 1. For example, the storage service can use a key-value pair (for example, "request_id=aaa" as the key and "str1" as the value) for storage.

[0202] In step S703, the SSP returns the generated random character string 1 (ie, the secret key factor corresponding to stimulus event 1) and request identifier 1 (ie, request_id=aaa) to the terminal.

[0203] In step S704, the terminal sends an advertisement pull request 2 (eg, update2) corresponding to stimulus event 2 and carrying a request identifier 2 (eg, request_id=bbb) to the SSP.

[0204] In step S705, the SSP sends the generated random string 2 to the storage service. For example, the SSP generates a random string 2 (for example, str2) for the advertisement pull request 2 sent by the terminal as a secret key factor corresponding to the stimulus event 2, and sends the generated random string 2 to the storage service so that the storage service stores the correspondence between the random string 2 and the request identifier 2.

[0205] In step S706, the SSP returns the generated random string 2 (ie, the secret key factor corresponding to the stimulus event 2) and the request identifier 2 (ie, request_id=bbb) to the terminal.

[0206] In step S707, the terminal sends an encrypted unlocking request 1 (eg, play1) corresponding to stimulus event 1 and carrying a request identifier 1 (ie, request_id=aaa) and encryption policy parameters 1 (eg, alg1 and version1) to the SSP.

[0207] In step S708, the SSP sends the extracted request identifier 1 to the storage service. For example, the SSP extracts the request identifier 1 (ie, request_id=aaa) from the encrypted unlocking request 1 sent by the terminal, and sends the extracted request identifier 1 to the storage service so that the storage service performs a query.

[0208] In step S709, the storage service returns the random string 1 corresponding to the request identifier 1 (ie, the key factor corresponding to the stimulus event 1) to the SSP.

[0209] In step S7010, the SSP sends the extracted encryption policy parameter 1 to the configuration center. For example, the SSP extracts encryption policy parameter 1 (ie, alg1 and version1) from the encryption unlocking request 1 sent by the terminal, and sends the extracted encryption policy parameter 1 to the configuration center for query.

[0210] In step S7011, the configuration center returns encryption policy 1 (eg, encryption rule 1) corresponding to encryption policy parameter 1 to the SSP.

[0211] In step S7012, the SSP decrypts the encrypted unlock request 1 (ie, play1) reported by the terminal according to the encryption policy 1 (eg, encryption rule 1) returned by the configuration center, obtains the unlock request 1, and performs an unlock operation on the unlock request 1.

[0212] In step S7013, the SSP returns point information 1 corresponding to the encrypted unlocking request 1 to the terminal.

[0213] In step S7014, the terminal sends an encrypted unlocking request 2 (eg, play2) corresponding to stimulus event 2 and carrying a request identifier 2 (ie, request_id=bbb) and encryption policy parameters 2 (eg, alg2 and version2) to the SSP.

[0214] In step S7015, the SSP sends the extracted request identifier 2 to the storage service. For example, the SSP extracts the request identifier 2 (ie, request_id=bbb) from the encrypted unlocking request 2 sent by the terminal, and sends the extracted request identifier 2 to the storage service so that the storage service performs a query.

[0215] In step S7016, the storage service returns the random string 2 corresponding to the request identifier 2 (ie, the key factor corresponding to the stimulus event 2) to the SSP.

[0216] In step S7017, the SSP sends the extracted encryption policy parameter 2 to the configuration center. For example, the SSP extracts encryption policy parameter 2 (ie, alg2 and version2) from the encryption unlocking request 2 sent by the terminal, and sends the extracted encryption policy parameter 2 to the configuration center for query.

[0217] In step S7018, the configuration center returns encryption policy 2 (eg, encryption rule rule 2) corresponding to encryption policy parameter 2 to the SSP.

[0218] In step S7019, the SSP decrypts the encrypted unlock request 2 (ie, play2) reported by the terminal according to the encryption policy 2 (eg, encryption rule 2) returned by the configuration center, obtains the unlock request 2, and performs an unlock operation on the unlock request 2.

[0219] In step S7020, the SSP returns point information 2 corresponding to the encrypted unlocking request 2 to the terminal.

[0220] It can be seen that if the terminal does not send an advertisement pull request to the SSP, the correct secret key factor will not be obtained. Therefore, the unlock request cannot be correctly encrypted when the unlock request is subsequently reported. At the same time, the SSP cannot decrypt it correctly, resulting in the failure of the unlock request reported by the terminal.

[0221] In addition, it should be noted that the encryption strategy used by the terminal each time it performs an encryption operation may also be different, that is, random. For example, the specific encryption strategy can be associated by the terminal, SSP through the two parameters alg and version and the configuration center. In this way, it can increase the difficulty for illegal users to crack the encryption strategy.

[0222] Furthermore, for each incentive event, the incentive event processing method provided in the embodiment of the present application can associate the two requests within the incentive event (for example, an advertisement pull request and an encryption unlock request) through a request identifier (request_id), thereby ensuring that there is no crossover or reuse of keys between different incentive events, that is, for different incentive events, the corresponding encryption strategies, key factors, etc. can be different, that is, a key is only valid in one incentive event. In this way, even if a key is leaked, since the keys corresponding to different incentive events are different, it will not affect the security of other incentive events.

[0223] In other embodiments, in order to prevent the key factor from being reused, the SSP may actively delete the key factor corresponding to the incentive event after each successful unlocking. For example, when the SSP successfully unlocks the unlock request corresponding to incentive event A, the SSP deletes the key factor corresponding to incentive event A. At the same time, if the user only pulls the advertisement in an incentive event but does not completely complete the unlock request, the SSP may also delete the corresponding key factor after a certain period of time.

[0224] The method for processing incentive events provided in the embodiment of the present application encrypts the unlocking request in the incentive event process based on the secret key factor randomly generated by SSP, and obfuscates the encrypted character string, thereby increasing the uncertainty in the encryption process, thereby increasing the difficulty of cracking the incentive event, and further improving the security of data related to the incentive video.

[0225] The following is an exemplary structure of the stimulus event processing device 243 provided in the embodiment of the present application being implemented as a software module. In some embodiments, for example Figure 2 As shown, the software modules stored in the stimulus event processing device 243 of the memory 240 may include: a receiving module 2431 , a sending module 2432 , a decryption module 2433 , and an unlocking module 2434 .

[0226] The receiving module 2431 is used to receive an incentive task request corresponding to an incentive event sent by a terminal; the sending module 2432 is used to send an incentive task to the terminal according to the incentive task request; the receiving module 2431 is also used to receive an encrypted unlocking request corresponding to an incentive event sent by the terminal, wherein the encrypted unlocking request is generated based on the incentive event after the terminal executes the incentive task; the decryption module 2433 is used to decrypt the encrypted unlocking request based on the incentive event to obtain an unlocking request; the unlocking module 2434 is used to perform an unlocking operation on the unlocking request to obtain authorization information; the sending module 2432 is also used to send authorization information to the terminal, wherein the authorization information is used for the terminal to execute the authorized incentive carrier fragment in the incentive carrier.

[0227] In some embodiments, the stimulus event processing device 243 also includes an extraction module 2435, which is used to extract a request identifier corresponding to the stimulus event from the stimulus task request, wherein different stimulus events correspond to different request identifiers; a sending module 2432 is also used to send a request identifier and a stimulus task to the terminal, wherein the request identifier is used to characterize that the stimulus task is used to respond to the stimulus task request.

[0228] In some embodiments, the processing device 243 for the stimulus event also includes a generating module 2436, which is used to generate a secret key factor corresponding to the stimulus event, wherein the secret key factors generated for different stimulus events are different; the sending module is also used to send the secret key factor to the terminal, wherein the secret key factor is used for the terminal to encrypt the request information required to perform the unlocking operation, and obtain an encrypted unlocking request.

[0229] In some embodiments, the encrypted unlocking request includes an encrypted obfuscation request, a request identifier, and encryption policy parameters; the decryption module 2433 is also used to search the encryption policy table based on the encryption policy parameters to obtain the encryption policy corresponding to the stimulus event, the encryption policy including a key generation rule and an obfuscation rule; based on the obfuscation rule, a deobfuscation operation is performed on the encrypted obfuscation request to obtain an encrypted unlocking request; the generation module 2436 is also used to obtain a key factor based on the request identifier, and generate a key based on the key generation rule and the key factor; the decryption module 2433 is also used to decrypt the encrypted unlocking request based on the key to obtain an unlocking request.

[0230] In some embodiments, the generation module 2436 is also used to obtain key information and signature information, wherein the key information includes at least one of the following: user account, device account; when the key generation rule is the first encryption rule, the key factor and the key information are encrypted to generate a key; when the key generation rule is the second encryption rule, the key factor, the key information and the signature information are encrypted to generate a key.

[0231] In some embodiments, the stimulus event processing device 243 also includes an update module 2437 for updating the encryption policy when at least one of the following conditions is met: reaching an automatic update cycle; receiving an instruction to trigger the update of the encryption policy; the encryption policy is cracked.

[0232] In some embodiments, the decryption module 2433 is also used to query the database based on the request identifier to obtain the secret key factor corresponding to the request identifier; wherein the database is used to store the corresponding relationship between the secret key factor generated by the server according to different stimulus events and the request identifier.

[0233] In some embodiments, the unlocking module 2434 is further used to extract request information carried in the unlocking request, wherein the request information includes a user account, an incentive carrier, and an identifier of an incentive carrier fragment to be authorized in the incentive carrier; based on the identifier, determining the incentive carrier fragment from the incentive carrier; performing an unlocking operation on the unlocking request of the user account for the incentive carrier fragment, and obtaining authorization information for executing the incentive carrier fragment as the user account.

[0234] In some embodiments, the processing device 243 for the incentive event also includes a deletion module 2438, which is used to delete the secret key factor corresponding to the incentive event when the unlocking operation is successfully performed for the unlocking request; when the incentive task request sent by the terminal is received and the encrypted unlocking request sent by the terminal is not received, the secret key factor corresponding to the incentive event is deleted after a preset time period.

[0235] The following is a description of an exemplary structure of the stimulus event processing device 455 provided in the embodiment of the present application implemented as a software module. In some embodiments, for example, Figure 3 As shown, the software modules stored in the stimulus event processing device 455 of the memory 450 may include: a sending module 4551 , a receiving module 4552 , and an execution module 4553 .

[0236] The sending module 4551 is used to send an incentive task request corresponding to the incentive event to the server; the receiving module 4552 is used to receive the incentive task sent by the server according to the incentive task request; the executing module 4553 is used to execute the incentive task; the sending module 4551 is also used to send an encrypted unlocking request generated based on the incentive event to the server; the receiving module 4552 is also used to receive the authorization information sent by the server according to the encrypted unlocking request; wherein the authorization information is generated by the server performing a decryption operation on the encrypted unlocking request based on the incentive event and performing an unlocking operation on the unlocking request; the executing module 4553 is also used to execute the authorized incentive carrier fragment in the incentive carrier according to the authorization information.

[0237] In some embodiments, the processing device 455 for the stimulus event also includes a generation module 4554 for generating request information required to perform an unlocking operation; the processing device 455 for the stimulus event also includes an encryption module 4555 for obtaining an encryption strategy from the server, performing encryption operations on the request information based on the encryption strategy, and obtaining an encrypted unlocking request.

[0238] In some embodiments, the encryption module 4555 is also used to obtain encryption policy parameters corresponding to the incentive event from the server; search the encryption policy table based on the encryption policy parameters to obtain the encryption policy corresponding to the incentive event; wherein different incentive events correspond to different encryption policy parameters; wherein the server updates the encryption policy in the following ways: periodic automatic update; manually triggered update; update when the encryption policy is cracked.

[0239] In some embodiments, the encryption policy parameters include: security algorithm parameters and encryption policy version parameters; the encryption policy includes: encryption algorithm type, key generation rules and obfuscation rules; the encryption module 4555 is also used to search the encryption policy table according to the security algorithm parameters to obtain the corresponding encryption algorithm type; search the encryption policy table based on the encryption policy version parameters to obtain the corresponding key generation rules and obfuscation rules.

[0240] In some embodiments, the encryption strategy includes key generation rules and obfuscation rules; the encryption module 4555 is also used to generate a key based on the key generation rules and the key factor; the request information is encrypted based on the key to obtain encrypted request information; the encrypted request information is obfuscated based on the obfuscation rules to obtain obfuscated encrypted request information; a combined operation is performed based on the obfuscated encrypted request information, the request identifier and the encryption strategy to obtain an encrypted unlocking request.

[0241] In some embodiments, the receiving module 4552 is also used to receive a request identifier sent by the server according to the incentive task request, and a secret key factor corresponding to the incentive event; wherein the request identifier is extracted by the server from the incentive task request, and the secret key factor is generated by the server according to the incentive event, and different incentive events correspond to different secret key factors.

[0242] In some embodiments, the generating module 4554 is further used to generate a request identifier corresponding to the stimulus event, wherein different stimulus events correspond to different request identifiers; and to generate a stimulus task request carrying the request identifier.

[0243] It should be noted that the description of the device in the embodiment of the present application is similar to the description of the method embodiment above, and has similar beneficial effects as the method embodiment, so it will not be repeated. Figure 4-6 The present invention should be understood by referring to the description of any one of the accompanying drawings.

[0244] The embodiment of the present application provides a computer program product or a computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of an electronic device (such as a computer device) reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the electronic device executes the above-mentioned method for processing the stimulus event in the embodiment of the present application.

[0245] The present application embodiment provides a computer-readable storage medium storing executable instructions, wherein the executable instructions are stored. When the executable instructions are executed by a processor, the processor will be caused to execute the method provided by the present application embodiment, for example, Figure 4-6 A method for processing a stimulus event as shown in any of the accompanying drawings.

[0246] In some embodiments, the computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface storage, optical disk, or CD-ROM; or it may be various devices including one or any combination of the above memories.

[0247] In some embodiments, executable instructions may be in the form of a program, software, software module, script or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as a stand-alone program or as a module, component, subroutine or other unit suitable for use in a computing environment.

[0248] As an example, executable instructions may, but need not, correspond to a file in a file system, may be stored as part of a file that stores other programs or data, such as in one or more scripts in a HyperText Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files storing one or more modules, subroutines, or code portions).

[0249] As an example, executable instructions may be deployed to be executed on one electronic device (eg, a computer device), or on multiple electronic devices located at one site, or on multiple electronic devices distributed at multiple sites and interconnected by a communication network.

[0250] To summarize, the embodiments of the present application achieve isolation of the encryption / decryption methods of different incentive events by matching the encryption and decryption methods of the unlock request with the incentive event, making it difficult for illegal users to obtain the authorization information of all incentive carrier fragments through a single cracking, thereby giving up frequent requests for incentive carrier fragments. On the one hand, this ensures the security of the incentive carrier, and on the other hand, it saves the resources of the relevant servers by filtering out invalid requests from illegal users.

[0251] The above is only an embodiment of the present application and is not intended to limit the protection scope of the present application. Any modifications, equivalent substitutions and improvements made within the spirit and scope of the present application are included in the protection scope of the present application.

Claims

1. A method for processing an incentive event, characterized in that: The method comprises: Receiving an incentive task request corresponding to an incentive event sent by a terminal, and sending an incentive task to the terminal according to the incentive task request; Receiving an encrypted unlocking request corresponding to the incentive event and sent by the terminal, wherein the encrypted unlocking request is generated by the terminal based on the incentive event after executing the incentive task; Decrypting the encrypted unlock request based on the stimulus event to obtain an unlock request, and performing an unlock operation on the unlock request to obtain authorization information; The authorization information is sent to the terminal, wherein the authorization information is used for the terminal to execute the authorized incentive carrier segment in the incentive carrier.

2. The method according to claim 1, characterized in that The sending the incentive task to the terminal according to the incentive task request includes: Extracting a request identifier corresponding to the incentive event from the incentive task request, wherein the request identifiers corresponding to different incentive events are different; The request identifier and the incentive task are sent to the terminal, wherein the request identifier is used to indicate that the incentive task is used to respond to the incentive task request.

3. The method according to claim 1, characterized in that The method further comprises: generating a secret key factor corresponding to the stimulus event, wherein the secret key factor generated for different stimulus events is different; The secret key factor is sent to the terminal, wherein the secret key factor is used by the terminal to encrypt request information required to perform the unlocking operation to obtain the encrypted unlocking request.

4. The method according to claim 1, characterized in that: The encrypted unlocking request includes an encrypted obfuscation request, a request identifier, and an encryption strategy parameter, wherein the request identifier is the same as the request identifier carried in the incentive task request; The decrypting operation on the encrypted unlocking request based on the incentive event to obtain the unlocking request includes: Searching an encryption strategy table based on the encryption strategy parameters to obtain an encryption strategy corresponding to the stimulus event, wherein the encryption strategy includes a key generation rule and an obfuscation rule; Performing a deobfuscation operation on the encrypted obfuscation request based on the obfuscation rule to obtain an encrypted unlocking request; Acquire a key factor based on the request identifier, and generate a key based on the key generation rule and the key factor; The encrypted unlocking request is decrypted based on the secret key to obtain an unlocking request.

5. The method according to claim 4, characterized in that The method further comprises: When at least one of the following conditions is met, the encryption policy is updated: An automatic update cycle is reached; an instruction to trigger updating of the encryption policy is received; and the encryption policy is cracked.

6. The method according to claim 1, characterized in that The performing an unlock operation on the unlock request to obtain authorization information includes: Extracting request information carried in the unlock request, wherein the request information includes a user account, an incentive carrier, and an identifier of an incentive carrier segment to be authorized in the incentive carrier; determining the incentive carrier segment from the incentive carrier based on the identifier; An unlock operation is performed on the unlock request of the user account for the incentive carrier fragment, and authorization information for executing the incentive carrier fragment as the user account is obtained.

7. A method for processing an incentive event, characterized in that: The method comprises: Sending an incentive task request corresponding to an incentive event to a server, and receiving an incentive task sent by the server according to the incentive task request; Execute the incentive task, and send an encrypted unlocking request generated based on the incentive event to the server; receiving authorization information sent by the server according to the encrypted unlocking request; The authorization information is generated by the server performing a decryption operation on the encrypted unlock request based on the incentive event to obtain an unlock request, and performing an unlock operation on the unlock request; The authorized incentive carrier segment in the incentive carrier is executed according to the authorization information.

8. The method according to claim 7, characterized in that The method further comprises: Generate request information required to perform the unlocking operation; Acquire an encryption policy from the server, and perform an encryption operation on the request information based on the encryption policy to obtain an encrypted unlocking request; The sending to the server an encrypted unlocking request generated based on the incentive event comprises: When the incentive task is completed, an encrypted unlocking request generated based on the incentive event is sent to the server.

9. The method according to claim 8, characterized in that The obtaining the encryption policy from the server includes: Acquire encryption policy parameters corresponding to the stimulus event from the server; Searching an encryption strategy table based on the encryption strategy parameters to obtain an encryption strategy corresponding to the stimulus event; Wherein, different incentive events correspond to different encryption strategy parameters; The server updates the encryption policy in the following ways: periodic automatic update; manually triggered update; update when the encryption policy is cracked.

10. The method according to claim 8, characterized in that The encryption strategy includes key generation rules and obfuscation rules; The step of performing an encryption operation on the request information based on the encryption policy to obtain an encrypted unlocking request includes: Generate a secret key based on the secret key generation rule and the secret key factor; Performing an encryption operation on the request information based on the secret key to obtain encrypted request information; Performing an obfuscation operation on the encrypted request information based on the obfuscation rule to obtain obfuscated encrypted request information; A combined operation is performed based on the obfuscated encryption request information, the request identifier and the encryption strategy to obtain an encrypted unlocking request.

11. The method according to claim 10, characterized in that The method further comprises: Receiving the request identifier sent by the server according to the incentive task request and the secret key factor corresponding to the incentive event; The request identifier is extracted by the server from the incentive task request, the secret key factor is generated by the server according to the incentive event, and different incentive events correspond to different secret key factors.

12. A device for processing a stimulus event, characterized in that: The device comprises: A receiving module, used for receiving an incentive task request corresponding to an incentive event sent by a terminal; A sending module, used for sending the incentive task to the terminal according to the incentive task request; The receiving module is further configured to receive an encrypted unlocking request corresponding to the incentive event and sent by the terminal, wherein the encrypted unlocking request is generated by the terminal based on the incentive event after the terminal executes the incentive task; A decryption module, configured to decrypt the encrypted unlocking request based on the stimulus event to obtain an unlocking request; An unlocking module, used to perform an unlocking operation on the unlocking request and obtain authorization information; The sending module is further used to send the authorization information to the terminal, wherein the authorization information is used for the terminal to execute the authorized incentive carrier segment in the incentive carrier.

13. A device for processing a stimulus event, characterized in that: The device comprises: A sending module, used for sending an incentive task request corresponding to an incentive event to a server; A receiving module, used for receiving the incentive task sent by the server according to the incentive task request; An execution module, used for executing the incentive task; The sending module is further used to send an encrypted unlocking request generated based on the incentive event to the server; The receiving module is further configured to receive authorization information sent by the server according to the encrypted unlocking request; wherein the authorization information is generated by the server performing a decryption operation on the encrypted unlocking request based on the incentive event to obtain an unlocking request, and performing an unlocking operation on the unlocking request; The execution module is further used to execute the authorized incentive carrier segment in the incentive carrier according to the authorization information.

14. An electronic device, characterized in that: include: A memory for storing executable instructions; The processor is used to implement the method for processing the stimulus event described in any one of claims 1 to 6 or any one of claims 7 to 11 when executing the executable instructions stored in the memory.

15. A computer-readable storage medium, characterized in that: Executable instructions are stored, and when the executable instructions are executed, they are used to implement the method for processing the stimulus event described in any one of claims 1 to 6 or any one of claims 7 to 11.