A data processing method and a data processing device

Abstract

The embodiments of the present application provide a data processing method and a data processing device, which relate to the field of data processing. The method can provide a rich judgment mechanism for reward information, so that the reward distribution process is more flexible, so as to adapt to the increasingly complex activity configurations. The method may include: obtaining first operation information. The first operation information includes: a first task code, a first user identifier. According to the first task code, the reward information configured in the first task instance is obtained, and the first task code is the task code of the first task instance. The first task instance is included in the at least one task instance. From all the reward information configured for the first task instance, the target reward information is determined. The target reward information is distributed to the first electronic device corresponding to the first user identifier.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of data processing, and in particular, to a data processing method and a data processing device. Background Art

[0002] Currently, a device server that is in communication with an electronic device used by a user may configure one or more task instances to provide a rich activity experience when the user uses related operations.

[0003] For example, the one or more task instances may include a task instance corresponding to a lottery event. The device server may determine the reward information allocated to the user according to the lottery instruction input by the user on the electronic device and the configured items of the task instance.

[0004] Most of the existing configuration items are relatively simple and can no longer adapt to the increasingly complex task configuration requirements. Summary of the invention

[0005] The present application provides a data processing method and a data processing device, which can provide a judgment mechanism for rich reward information, making the reward distribution process more flexible so as to adapt to the increasingly complex activity configurations.

[0006] In order to achieve the above technical objectives, this application adopts the following technical solutions:

[0007] In a first aspect, a data processing method is provided, the method being applied to a data processing device, the data processing device being configured with at least one task instance, any of the task instances being configured with at least one reward information. The method comprises: obtaining first operation information. The first operation information comprises: a first task code, a first user identifier. According to the first task code, the reward information configured in the first task instance is obtained, the first task code being the task code of the first task instance. The first task instance is included in the at least one task instance. From all the reward information configured in the first task instance, target reward information is determined. The target reward information is distributed to a first electronic device corresponding to the first user identifier. In some implementations, the data processing device may be configured in a device server.

[0008] Based on this solution, by reasonably configuring various task instances in the data processing device, the data processing device can determine the distribution of corresponding reward information according to the user's operation information. Therefore, when different reward information is configured in the task instance configuration, the data processing device can adaptively and accurately determine the reward information to be distributed through the above logic. This can better adapt to the increasingly complex activity configuration requirements.

[0009] Optionally, the first user identifier includes at least one of the following: an international mobile equipment identity code IMEI of the first electronic device, an international mobile subscriber identity number IMSI of the first electronic device, account information logged in to the first electronic device, and a user identity code user ID. This example provides a specific implementation of the first user identifier. It is understandable that the first user identifier can be used to uniquely identify the current user.

[0010] Optionally, obtaining the reward information configured in the first task instance includes: obtaining the reward content information and type identification corresponding to each reward information configured in the first task instance. The type identification of the reward information includes: a first identification, a second identification, and / or a third identification. Thus, by configuring any one or more types of reward information of three different types, the configuration of the reward information is enriched. Correspondingly, the data processing device implements a fast and accurate response to a variety of task configurations by executing corresponding judgment logic on each type of reward information.

[0011] Optionally, the first task instance is configured with second reward information, and the type identifier of the second reward information includes the second identifier. The second reward information is configured with a first number threshold. The target reward information is determined from all the reward information configured for the first task instance, including: when the number of operation requests including the first user identifier received reaches the first number threshold, the target reward information is determined according to the second reward information. Exemplarily, the second reward information can be must-win reward information. In this way, the data processing device can distribute reward information to users according to the number of operations input by the same user.

[0012] Optionally, when the second reward information is not configured with the third identifier, determining the target reward information based on the second reward information includes: determining the second reward information as the target reward information.

[0013] Optionally, the type identifier of the second reward information also includes the third identifier. The second reward information is configured with a first limit configuration, and the first limit configuration includes limit thresholds of at least two dimensions corresponding to the second reward, and the at least two dimensions include at least two of the following: a single user dimension, an all user dimension, a year dimension, a month dimension, a day dimension, an hour dimension, a minute dimension, and a second dimension. In this example, the same reward information can also be configured with multiple different types. For example, the second reward information can be both must-win reward information and limited reward information. Correspondingly, the data processing device can further determine whether the limit configuration is met when determining that the distribution of the must-win reward is met, thereby achieving reasonable distribution of reward information.

[0014] Optionally, before determining the target reward information according to the second reward information, the method further includes: determining that after distributing the second reward information, the number of times the second reward information is received in each of the at least two dimensions is less than or equal to the limit threshold of the corresponding dimension. Determining the target reward information according to the second reward information includes: determining the second reward information as the target reward information.

[0015] Optionally, the first limit configuration includes a first limit threshold of the first dimension. After the second reward information is determined to be distributed, the number of times the second reward information is received in each of the at least two dimensions is less than or equal to the limit threshold of the corresponding dimension, including: after the second reward information is determined to be distributed, the number of times the second reward information is received in the first dimension does not exceed the first limit threshold.

[0016] Optionally, the determination that after the second reward information is distributed, the number of times the second reward information is received in the first dimension does not exceed the first limit threshold includes: generating a first key value key according to the first request information. Determine whether the first key value exists in the first database of the data processing device. The first database is configured in the memory of the data processing device, and the first database is used to store the key values ​​of the reward information that has been received and the corresponding numerical values ​​value. In the case where the first key value exists in the first database, the first numerical value corresponding to the first key value is obtained from the first database. The first numerical value is added by 1 to obtain the second numerical value. In the case where the second numerical value is less than or equal to the first limit threshold, it is determined that after the second reward information is distributed, the number of times the second reward information is received in the first dimension does not exceed the first limit threshold. In this example, by setting the database in the memory, it is possible to quickly confirm whether the limit configuration of the reward information is met. In some implementations, a key and a value in the memory can form a simplified field.

[0017] Optionally, the first key value includes: corresponding characters of the first user identifier, corresponding characters of the reward information code, and corresponding characters of the first dimension.

[0018] Optionally, when the first key value does not exist in the first database, the method further includes: reading the number of times the second reward information is received in the first dimension from the second database, and generating the first key value and storing it in the first database. The second database is configured in the external memory of the data processing device, and the second database stores information on the number of times all reward information is received in all dimensions.

[0019] Optionally, before reading the number of times the second reward information is received in the first dimension from the second database, the method further includes: determining that the operation lock of the first key value is not held by other threads.

[0020] Optionally, when the operation lock of the first key value is held by other threads, before reading the number of times the second reward information is received in the first dimension from the second database, the method further includes: waiting for the operation lock of the first key value to be released.

[0021] Optionally, after the operation lock of the first key value is released and before the second reward information is read from the second database for the number of collections in the first dimension, the method further includes: determining that the first key value does not exist in the first database.

[0022] Therefore, in the multi-thread parallel processing process, the judgment accuracy of the first key value is improved by configuring the operation lock.

[0023] Optionally, the first task instance is configured with first reward information, and the type identifier of the first reward information is the first identifier. After the second reward information is distributed, if the number of times the second reward information is collected in at least one of the at least two dimensions is greater than the limit threshold of the corresponding dimension, the target reward information is determined according to the second reward information, including: determining the first reward information as the target reward information. In this way, when the distribution conditions for the must-win reward are not met, the first reward information can be distributed directly.

[0024] Optionally, the first task instance is configured with first reward information, and the type identifier of the first reward information is the first identifier. The data processing device is configured with an abnormal user list, and at least one user identifier is stored in the abnormal user list. The target reward information is determined from all the reward information configured for the first task instance, including: when the first user identifier is included in the abnormal user list, the first reward information is determined as the target reward information. In this way, in the case of an abnormal user, the first reward information can be directly distributed to him. Thereby avoiding the adverse effects of abnormal users on the execution process of the task instance.

[0025] Optionally, at least two third reward information are configured in the first task instance, and the type identifier of the third reward information is the third identifier. Each of the third reward information is configured with corresponding probability information. The at least two third reward information include: fourth reward information, and fifth reward information. According to the first task code, the reward information configured in the first task instance is obtained, including: obtaining the reward content information of the fourth reward information, the probability information of the fourth reward information, and the type identifier of the fourth reward information. Obtaining the reward content information of the fifth reward information, the probability information of the fifth reward information, and the type identifier of the fifth reward information. Determining the target reward information from all the reward information configured in the first task instance includes: generating a random positive integer. According to the random positive integer falling in the first interval, the target reward information is determined according to the fourth reward information. Or, according to the random positive integer falling in the second interval, the target reward information is determined according to the fifth reward information. Among them, the first interval is [0, a], the second interval is [a, a+b], the probability information of the fourth reward information is 0.01*a, the probability information of the fifth reward information is 0.01*b, and a+b is not greater than 1. Thus, a solution for determining the reward information to be distributed according to the configured probability information is provided.

[0026] Optionally, the fourth reward information is also configured with the second identifier. The fourth reward information is configured with a second limit configuration, and the second limit configuration includes limit thresholds of at least two dimensions corresponding to the fourth reward. The target reward information is determined based on the fourth reward information, including: determining that after the fourth reward information is distributed, the number of times the fourth reward information is collected in each of the at least two dimensions of the second limit configuration is less than or equal to the limit threshold of the corresponding dimension. The fourth reward information is determined as the target reward information. Alternatively, after the fourth reward information is distributed, the number of times the fourth reward information is collected in at least one of the at least two dimensions of the second limit configuration exceeds the limit threshold of the corresponding dimension. The reward information whose type identifier is the first type is determined as the target reward information.

[0027] Optionally, when the fifth reward information is only configured with the third identifier, determining the target reward information based on the fifth reward information includes: determining the fifth reward information as the target reward information.

[0028] In this example, after determining the reward information to be distributed according to the probability information, if the reward information is configured with a limited quantity, a determination of the limited quantity configuration can also be made. Correspondingly, if the reward information is not configured with a limited quantity configuration, the reward information is directly distributed.

[0029] In a second aspect, a data processing device is provided, which is used to execute the method provided in the first aspect and any possible method thereof.

[0030] In a third aspect, a server is provided, wherein the server is configured with the data processing device provided in the second aspect. The server is used to execute the method provided in the first aspect and any possible method thereof during operation.

[0031] In a fourth aspect, a data processing system is provided. The data processing system includes a data processing device as provided in the second aspect, or a server as provided in the third aspect. The data processing system also includes a first electronic device. The first electronic device is communicatively connected to the data processing device or the server. The first electronic device is used to receive a user's operation and generate first operation information. The first electronic device is also used to send the first operation information to the data processing device or the server, so that the data processing device or the server executes the method provided in the first aspect and any possible one thereof.

[0032] In a fifth aspect, the present application also provides a chip system, which is applied to a data processing device as provided in the second aspect, or a server as provided in the third aspect; the chip system may include one or more interface circuits and one or more processors. The interface circuit and the processor are interconnected by a line, and the interface circuit is used to receive a signal from a memory of an electronic device and send the signal to the processor, where the signal includes a computer instruction stored in the memory. When the processor executes the above-mentioned computer instructions, the data processing device as provided in the second aspect, or the server as provided in the third aspect executes the technical solution provided in the above-mentioned first aspect and any possible implementation thereof.

[0033] In a sixth aspect, the present application also provides a computer-readable storage medium, comprising computer instructions. When the computer instructions are executed on an electronic device, the data processing device as provided in the second aspect, or the server as provided in the third aspect, executes the technical solution provided in the above-mentioned first aspect and any possible implementation thereof.

[0034] In a seventh aspect, the present application also provides a computer program product, which, when executed on a computer, enables the computer to execute the technical solution provided in the above-mentioned first aspect and any possible implementation thereof.

[0035] It can be understood that the solutions provided in the second aspect to the seventh aspect of the present application can respectively correspond to the first aspect and any possible design thereof, so the beneficial effects that can be achieved are similar and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 A schematic diagram of an interaction scenario;

[0037] Figure 2 A schematic diagram of an interface interaction;

[0038] Figure 3 A schematic diagram of the composition of a device server provided in an embodiment of the present application;

[0039] Figure 4 A schematic diagram of the composition of reward information provided in an embodiment of the present application;

[0040] Figure 5 A logic diagram of randomly determining reward information provided in an embodiment of the present application;

[0041] Figure 6 A flowchart of a data processing method provided in an embodiment of the present application;

[0042] Figure 7 A schematic diagram of the storage medium composition of a device server provided in an embodiment of the present application;

[0043] Figure 8 A flowchart of a data processing method provided in an embodiment of the present application;

[0044] Fig. 9 A flowchart of a data processing method provided in an embodiment of the present application;

[0045] Fig.10 A schematic diagram of the composition of a data processing device provided in an embodiment of the present application;

[0046] Fig.11 A schematic diagram of the composition of a chip system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0047] Currently, electronic devices can provide different functions to users by installing and running one or more application programs.

[0048] Exemplary, reference Figure 1 , mall applications, community applications, etc. can be installed in electronic devices.

[0049] It should be noted that, in the present application, the application programs installed in the electronic device may include system applications and third-party applications.

[0050] Among them, system applications may include Figure 1 The mall applications, community applications, etc. shown.

[0051] Third-party applications can be applications developed by third-party developers to adapt to the operating system running on the electronic device. According to different types, the third-party applications can include game applications, shopping applications, search applications, etc.

[0052] In the following examples, a system application installed in an electronic device is taken as an example.

[0053] When the electronic device runs a system application (such as a shopping mall application), it can provide users with functions related to product selection in the shopping mall application. In addition, the shopping mall application can also provide users with a lottery function to improve user stickiness and optimize the user shopping experience. Generally, the lottery function can be implemented by the application program in the electronic device and the corresponding server in cooperation with each other.

[0054] For example, continue to refer to Figure 1 Take the server corresponding to the mall application as an example, which is the device server corresponding to the mall application.

[0055] The device server may be configured with lottery-related logic, for example, in a lottery module.

[0056] In some implementations, the lottery module may be configured with one or more task instances corresponding to the lottery activities. Figure 1 In the example, the one or more task instances may include task instance 1, task instance 2, etc.

[0057] For one of the task instances (such as task instance 1 or task instance 2), the corresponding lottery algorithm logic and the corresponding prize pool information may be configured.

[0058] For example, task instance 1 may include lottery algorithm logic 1 and prize pool information 1.

[0059] The prize pool information may include two or more different reward information, so as to configure a variety of reward information for the user according to the lottery algorithm logic.

[0060] As an example, refer to Figure 2 , is a schematic diagram of the interaction between the electronic device and the device server. Figure 2 By implementing the solution shown, you can realize the logic of a lottery process.

[0061] like Figure 2 As shown, the electronic device may receive a user's operation 201.

[0062] As mentioned above Figure 1 The example of 201 shows that the electronic device can display icons of various application programs on the interface. For example, icons of mall applications, icons of community applications, etc. In this example, the operation 201 can include an operation of a user clicking on the icon of a mall application.

[0063] Correspondingly, the electronic device can send operation information 1 to the device server.

[0064] For example, the operation information 1 may be generated by the electronic device according to the operation 201 input by the user. The operation information 1 may be used to request the interface information of the mall application. For example, the interface information may include: Figure 2 Interface information of interface 202 is shown.

[0065] like Figure 2 As shown, the device server can determine to display the lottery interface in the mall application according to the operation information 1 and the current configuration. Then, the device server can send the lottery interface information to the electronic device.

[0066] The electronic device may display interface 202 according to the received lottery interface information.

[0067] Take the example where the device server determines that the user participates in a lottery activity corresponding to task instance 1 based on operation information 1.

[0068] In this example, the interface 202 may include various rewards in the reward pool information 1 configured in the task instance 1. For example, the reward pool information 1 may include reward information 1, reward information 2, reward information 3, and reward information 4. Correspondingly, the electronic device may display the logos of reward 1, reward 2, reward 3, and reward 4 on the interface 202, respectively.

[0069] The interface 202 may further include a button 203. The button 203 may be used to receive a lottery instruction from a user.

[0070] Take the case where the user inputs a click operation 205 on the button 203 as an example. Correspondingly, the electronic device can generate operation information 2.

[0071] The operation information 2 may indicate that the user has input a lottery operation for the task instance 1 .

[0072] In some embodiments, the operation information 2 may include a task code of the task instance 1. The task code uniquely corresponds to the lucky draw activity that the user indicates to participate in.

[0073] In some embodiments, the operation information 2 may include a user identifier. The user identifier may be used to uniquely correspond to the current user.

[0074] For example, in some implementations, the user identification may include information of the electronic device, such as International Mobile Equipment Identity (IMEI), etc. In other implementations, the user identification may include at least one of the following: International Mobile Subscriber Identification Number (IMSI), account information of the user currently logged into the mall application, user ID, and other user information.

[0075] The electronic device can send the operation information 2 to the device server.

[0076] In the present application, the process of the electronic device generating the operation information 2 and sending the operation information 2 including the user identification to the device server may be performed after the user authorizes.

[0077] Correspondingly, the device server can trigger the judgment of the lottery logic in the execution task instance 1 according to the operation information 2.

[0078] For example, the device server can determine the task instance of the lottery activity that the user wants to participate in according to the task code. The device server can also determine the reward information configured for the user according to the lottery algorithm logic of the task instance.

[0079] For example, the device server may send the reward information 1 to the electronic device, and the electronic device may display the interface 204 corresponding to "reward 1 obtained" on the interface.

[0080] In this way, the device interaction logic for users participating in the lottery can be implemented.

[0081] In the current device server configuration, after receiving the operation information 2, the logic configuration for determining the reward information is mostly relatively simple. For example, after receiving the operation information 2, the reward information is configured for the user according to the random extraction logic. This can only achieve a relatively simple lottery activity configuration. This may cause problems such as a large number of configurations of one or several types of reward information leading to distribution failures. The current logic implementation is also unable to support more complex reward configuration methods.

[0082] Based on this, the embodiment of the present application provides a data processing method, which realizes the configuration support of multi-dimensional lottery activities by configuring the judgment logic of multi-dimensional reward information in the device server. Thereby meeting the requirements of the increasingly complex reward extraction scenarios. In some embodiments, the solution provided by the present application can also support the judgment logic of limited configuration to facilitate the reasonable distribution of different reward information.

[0083] The solution provided in the embodiments of the present application is described in detail below with reference to the accompanying drawings.

[0084] The solution provided in the embodiment of the present application can be applied to a device server.

[0085] refer to Figure 1 According to the description, the device server may be a server connected to the user's electronic device. In the process of using the electronic device, the user may authorize the device server to obtain the relevant information sent by the electronic device through authorization operations on the electronic device. For example, the relevant information may include the user's operation information, etc.

[0086] Correspondingly, the device server can provide reward drawing services to the electronic device and the user who uses the electronic device based on the relevant information from the electronic device.

[0087] In some implementations, one or more functional modules may be configured in the device server so that the one or more functional modules cooperate with each other to realize the logic implementation of the above-mentioned reward extraction service.

[0088] As an example, refer to Figure 3 , is a schematic diagram of the composition of a device server provided in an embodiment of the present application.

[0089] It should be noted that if Figure 3 The example is only an implementation and does not constitute any limitation on the device server involved in the embodiments of the present application.

[0090] like Figure 3 As shown, one or more task instances may be configured in the device server. The device server may also be configured with a probability judgment module, a limit judgment module, and a reward configuration module.

[0091] The following explains them respectively.

[0092] Each task instance may correspond to a reward drawing service. In other words, a task instance may correspond to a lottery activity. For example, the one or more task instances may include task instances 1 to n. n is an integer greater than or equal to 1. When n is 1, a task instance may be configured in the device server.

[0093] For each task instance, one or more corresponding reward information can be configured. In this way, in the corresponding scenario of the task instance, diversified reward information can be configured for different users / different operations of the same user according to the logic in the subsequent description.

[0094] Take the n task instances including task instance A as an example.

[0095] like Figure 3 As shown, task instance A may be configured with reward information 1, reward information 2, reward information 3, and reward information 4.

[0096] As an example, refer to Figure 4 Each reward information may include corresponding reward content information, type identification, etc. In some implementations, the reward information may also include probability information for configuring the reward information.

[0097] Among them, the reward content information may include at least one of the following: reward information serial number, reward information code, reward information name, reward information type, reward information picture, serial number of the prize corresponding to the reward information, name of the prize corresponding to the reward information, value information of the prize corresponding to the reward information, quantity of the prize corresponding to the reward information, and code of the prize corresponding to the reward information.

[0098] As an example, the following Table 1 provides a configuration diagram of reward content information, wherein the prize is the prize corresponding to the reward information.

[0099] Table 1

[0100]

[0101] Thus, in determining the distribution of a reward (such as Figure 3 After receiving the reward information 1, reward information 2, reward information 3, etc. shown in the figure, the device server can send the reward content information to the corresponding electronic device (or the user account corresponding to the electronic device).

[0102] In this example, the type identifier of the reward information can be used to indicate the type of the corresponding reward information. One reward information can be configured with one type identifier. Alternatively, one reward information can also be configured with two or more type identifiers at the same time.

[0103] In the present application, the types of reward information may include: a first type, a second type, and a third type. In some other implementations, the first type may also be referred to as a bottom-line type. The second type may also be referred to as a must-win type. The third type may also be referred to as a limited-quantity type. Accordingly, the first type of reward information is also a bottom-line reward, the second type of reward information is also a must-win reward, and the third type of reward information is also a limited-quantity reward.

[0104] Corresponding to the implementation of the type identifier, the type identifier corresponding to the first type may be a first identifier, the type identifier corresponding to the second type may be a second identifier, and the type identifier corresponding to the third type may be a third identifier.

[0105] Exemplarily, the first type of reward information may be the reward information with the highest configuration probability. In other implementations, the first type of reward information may also be used to configure rewards for abnormal users. In other implementations, the first type of reward information may also be used to distribute to users when the distribution conditions of the second type of reward information or the third type of reward information are not met.

[0106] The second type of reward information may be configured with a number threshold. The number threshold may be a threshold of the number of operations input by the same user ID. For example, the number threshold of the first type of reward information is m. The device server may distribute the corresponding second type of reward information to the user when the number of operations received from the same user ID reaches m.

[0107] The third type of reward information may correspond to the configuration of limited information. In the embodiment of the present application, the limited information may also be referred to as limited configuration. In some embodiments of the present application, the limited information may be a multi-dimensional configuration threshold, such as at least one of the following dimensions: single user dimension, multi-user (such as total user) dimension, year dimension, month dimension, day dimension, hour dimension, minute dimension, second dimension, etc. The limited information can be used to control the configuration quantity of the corresponding reward information in each dimension, so that in each dimension, the configuration quantity of the corresponding reward information can be maintained in a relatively balanced state.

[0108] As an example, the following Table 2 provides an example of multi-dimensional limited information configuration of a third type of reward information.

[0109] Table 2

[0110] total each year per month daily Every hour Per minute per second Single User 0 0 0 1 0 0 0 Total users 45 0 0 3 0 0 0 Issued 20 0 0 0 0 0 0

[0111] In the example of Table 2, the third type of reward information may be configured with limited information of a single user dimension, a total user dimension, and a daily dimension. Among them, an item configured as "0" corresponds to being unconfigured and having no corresponding restrictions.

[0112] Based on the configuration in Table 2, the third type of reward information can be configured once per user at most per day; the maximum number of configurations for all users per day is 3 times; and the number of configurations for all users during the complete cycle of the current task instance does not exceed 45 times.

[0113] It is understandable that Table 2 is only an example. In other implementations, each third type of reward information can also be configured with more or fewer dimensions of limited information based on the configuration example shown in Table 2.

[0114] In some embodiments, each third type of reward information may carry corresponding address information. The address information may include an address storing the limited information corresponding to the reward information. When the device server wants to configure the third type of reward information for the user, it can obtain the corresponding configured limited information through the corresponding address. Then, it is determined whether the configuration is within the limited range of the limited information, and the configuration of the reward information to the user is realized.

[0115] It should be noted that, in the example of Table 2, the issued record of the reward information may also be stored together with the limited quantity information. The issued record may also correspond to the dimension of the configured limited quantity information.

[0116] For example, as shown in Table 2, the issued record of the reward information may indicate that the current reward information has been issued 20 times. However, the current user has not configured the reward information. Thus, based on the information shown in Table 2, when the device server wants to configure the corresponding reward information for the current user, it can determine that the configuration behavior will not exceed the limited information of each dimension, and accordingly execute the issuance of the reward information for the user.

[0117] In some other embodiments of the present application, the issued records may also be stored in other locations of the device server, separated from the information related to the limited information as shown in Table 2.

[0118] It is understandable that after the task instance configuration is created, the limit information can be a configured fixed value. Therefore, the limit information can be stored together with other configured fixed values ​​of the task instance (such as reward content information, etc.).

[0119] Correspondingly, the issued record may be dynamic information related to the user operation, and the issued record may be maintained and updated by the device server according to the received operation information.

[0120] In some embodiments of the present application, a corresponding table of issued records may be configured in the device server to store the corresponding relationship between each user identifier (such as user ID), task instance, and configured information.

[0121] As an example, the following Table 3 provides an example of a corresponding table of issued records.

[0122] Table 3

[0123]

[0124] As shown in Table 3, the task codes of the enabled task instances are task code 1, task code 2, and so on.

[0125] The device server can store the task instances that each user has participated in and the configured information in each task instance according to different user IDs in the corresponding table of issued records. Among them, the configured information may include the reward code, the number of issued times (or the number of received times) and the like of the reward information that has been distributed to the current user in the corresponding task instance. It should be pointed out that when the reward information is configured with a limited configuration of multiple dimensions, the number of issued times in the configured information may include the number of received times under each dimension.

[0126] For example, in the example of Table 3, when a user whose user ID is ID 1 participates in a task instance of task code 1, the device server has issued the reward information corresponding to the configured information 1-1 to the user. Similarly, when a user whose user ID is ID 1 participates in a task instance of task code 2, the device server has issued the reward information corresponding to the configured information 1-2 to the user.

[0127] In addition, Table 3 may also include task instances in which other users (such as a user whose user ID is ID 2) participate, and corresponding relationships of configured information.

[0128] The device server may update the issued record correspondence table each time after configuring reward information for the user, so as to accurately determine the configuration of the next reward information according to the issued record correspondence table.

[0129] As another implementation of the issued record correspondence table shown in Table 3, the issued record correspondence table may also record in sequence according to the logical order of task code-user ID-configured information.

[0130] Exemplary, reference Figure 4 , which is a schematic diagram of another issued record correspondence table provided in an embodiment of the present application.

[0131] Table 4

[0132]

[0133] Based on the implementation of Table 4, after determining the task code according to the operation information, the device server can obtain the configured information of each user (such as different user IDs) corresponding to the task code.

[0134] For example, when the device server determines that the current operation corresponds to a task instance of task code 1, it can determine, based on Table 4, that the configuration of each reward information corresponding to the user with user ID ID 1 is configured information 1-1. For another example, the device server can also determine that the configuration of each reward information corresponding to the user with user ID ID 1 is configured information 2-1. Others are similar.

[0135] This application does not limit the specific implementation form of the issued record correspondence table.

[0136] In the examples of Table 3 or Table 4, the device server can centrally manage and maintain the configured information of multiple users, multiple task instances, and corresponding reward information. In this way, whenever an operation information is received, the device server can call the corresponding table of issued records to accurately determine the reward information corresponding to the operation information.

[0137] In other embodiments, the device server may also establish a corresponding table of issued records for each user or each task instance, thereby realizing the separation of configuration of reward information of different users or different task instances. This can avoid the problem that the corresponding table of issued records maintained centrally appears abnormal, resulting in the inability to query the reward configuration of all users or task instances.

[0138] In the specific implementation process, any one of the implementations provided in the above embodiments may be adopted to perform storage and maintenance of the configured information.

[0139] In other embodiments of the present application, part or all of the reward information in one or more reward information in the task instance may also include corresponding configured probability information. In other words, there may be reward information that is not configured with probability information. Then the reward information can be distributed according to the corresponding issuance conditions.

[0140] The probability information may be used to indicate the probability of extracting the corresponding reward information. In the present application, for reward information configured with probability information, the sum of all probability information configured may not exceed 1.

[0141] As an example, take task instance A as an example. Table 5 below provides the type identification of each reward information in task instance A, and the configuration diagram of probability information.

[0142] Table 5

[0143] First logo Second mark The third mark Probability Information Reward Information 1 1 0 0 0.7 Reward Information 2 0 1 0 NA Reward Information 3 0 0 1 0.2 Reward Information 4 0 0 1 0.1

[0144] In the example shown in Table 5, each reward information may be configured with a first identifier, a second identifier, and / or a third identifier. When the reward information is of a type corresponding to the corresponding identifier, the corresponding identifier is configured as 1. Correspondingly, when the reward information does not correspond to the corresponding identifier, the corresponding identifier is configured as 0.

[0145] In the example shown in Table 5, it is taken as an example that any reward information is configured with a type identifier, that is, any reward information can be the first type of reward information, or the second type of reward information, or the third type of reward information.

[0146] Take the configuration shown in Table 5 as an example. Reward information 1 can be the first type of reward information (such as a guaranteed reward). Reward information 2 can be the second type of reward information (such as a guaranteed reward). Reward information 3 and reward information 4 can be the third type of reward information (such as a limited reward).

[0147] It should be noted that in other embodiments of the present application, the same reward information may have two or more types of features.

[0148] For example, the same reward information may be configured with the first identifier and the third identifier at the same time. In this way, the reward information may correspond to the first type of reward information, and also be configured with the limited configuration corresponding to the third type.

[0149] For another example, the same reward information may be configured with the second identifier and the third identifier at the same time. In this way, the reward information may correspond to the second type of reward information, and may also be configured with the limited configuration corresponding to the third type.

[0150] Exemplarily, refer to Table 6, which is a schematic diagram of the type identification of each reward information of task instance A and the configuration of probability information in another implementation.

[0151] Table 6

[0152] First logo Second mark The third mark Probability Information Reward Information 1 1 0 0 0.7 Reward Information 2 0 1 1 NA Reward Information 3 0 0 1 0.2 Reward Information 4 0 0 1 0.1

[0153] In the example of Table 6, the reward information 2 may be configured with a second identifier, and the reward information 2 may also be configured with a third identifier. Therefore, the type of the reward information 2 may be the second type and the third type.

[0154] In this way, the device server determines that the distribution condition corresponding to the second type is satisfied when the number of operations performed by the same user (such as the same user ID) on the same task instance reaches m according to the second type judgment mechanism.

[0155] In addition, since the reward information 2 is also configured with a third identifier, the device server needs to confirm that the distributed information of the reward information 2 meets the limited quantity information before distributing the reward information 2, that is, to determine whether the distribution conditions corresponding to the third type are met.

[0156] For example, when the distributed information of the reward information 2 meets the conditions of the corresponding limited information, it is determined that the reward information 2 meets the distribution conditions corresponding to the third type.

[0157] Thus, the device server can configure the reward information 2 for the user corresponding to the current user identification when the reward information 2 satisfies both the second type of distribution conditions and the third type of distribution conditions.

[0158] It should be noted that in the embodiment of the present application, there is no fixed binding relationship between the configuration of probability information and the type identification. The configuration of probability information can be flexibly configured in different specific task instances.

[0159] In combination with the above description, in the examples of Table 5 or Table 6, reward information 1, reward information 3, and reward information 4 may also be configured with probability information. For example, the probability information of reward information 1 is 0.7; the probability information of reward information 3 is 0.2; and the probability information of reward information 4 is 0.1.

[0160] It can be seen that the sum of the probability information of all reward information can be 1. The probability information of each reward information can be used for subsequent determination of configuring one of the reward information for the current user.

[0161] In addition, in this example, the probability information may not be configured for the reward information 2. In this way, the device server may configure the reward information 2 to the user according to the type identifier of the reward information 2 as the second identifier based on the configured logic, when determining that a must-win reward needs to be configured for the user. The logic example of this specific configuration will be described in detail later.

[0162] As shown in the example of Table 5, the probability information is configured in reward information 1 (such as a guaranteed reward). In other embodiments, the probability information may not be configured in reward information 1. Correspondingly, the limited reward may be configured with probability information.

[0163] For example, as shown in Table 7.

[0164] Table 7

[0165] First logo Second mark The third mark Probability Information Reward Information 1 1 0 0 NA Reward Information 2 0 1 0 NA Reward Information 3 0 0 1 0.7 Reward Information 4 0 0 1 0.3

[0166] In the example of Table 7, reward information 1 (such as a guaranteed reward) and reward information 2 (such as a guaranteed reward) may not be configured with probability information. Reward information 3 and reward information 4 (such as a limited reward) may be configured with probability information. For example, the probability information of reward information 3 is configured as 0.7, and the probability information of reward information 4 is configured as 0.3.

[0167] In this way, the device server can configure the reward information 1 to the user according to the configuration logic, based on the type identifier of the reward information 1 as the first identifier, if it is determined that a guaranteed reward needs to be configured for the user. The device server can configure the reward information 2 to the user according to the configuration logic, based on the type identifier of the reward information 2 as the second identifier, if it is determined that a guaranteed reward needs to be configured for the user.

[0168] The above describes in detail the task instance in the device server.

[0169] like Figure 3As shown, a probability judgment module, a limit judgment module, and a reward configuration module may also be configured in the device server.

[0170] In some embodiments of the present application, the probability judgment module and the limit judgment module can be used to execute the data processing method provided in the embodiments of the present application according to the logic preconfigured in the device server, and preliminarily judge the reward information configured for the current user based on the probability information of each reward information configuration.

[0171] As an example, refer to Figure 5 The probability judgment module can be Figure 5 The logic implementation shown determines the reward information that needs to be distributed based on the probability information of each reward information.

[0172] In this example, the currently running task instance is task instance A, and task instance A is configured with rewards A, B, and C. The probability information of reward A is configured to 10%, the probability information of reward B is configured to 20%, and the probability information of reward C is configured to 70%.

[0173] Since the sum of the probabilities of all rewards is 1, in this example, the probability judgment module can generate a line segment with a length of 100. The line segment can configure the corresponding length interval as each reward information according to the probability information of each reward information.

[0174] For example, Figure 5 As shown, the probability of reward A is 10%, so the probability judgment module can configure the partial line segment of length 10 in the line segment of length 100 with a length interval of [1,10) as reward A. Similarly, the partial line segment of length 20 in the length interval of [10,30) is configured as reward B, and the partial line segment of length 70 in the length interval of [30,100) is configured as reward C.

[0175] Next, the probability judgment module can generate a random number and determine the reward information distribution result based on the probability judgment according to the length interval of the random number.

[0176] For example, take the random number 66 as an example. The random number falls within the length interval [30,100). Correspondingly, the probability judgment module can determine the reward C to be distributed this time.

[0177] In other embodiments of the present application, when the information to be configured is configured with a third identifier, that is, the determined information to be configured is configured with a limited quantity, the limited quantity judgment module can determine whether the information to be configured can be distributed according to the corresponding limited quantity configuration.

[0178] Thus, the device server can comprehensively determine the reward information configured for the current user based on the information to be configured and the judgment result of the limit judgment module, that is, determine the lottery result of the current user.

[0179] The device server may also include a reward configuration module. The reward configuration module may be used to distribute the reward information to the user identifier carried in the operation request after determining the reward information to be distributed, for example, to send the reward content information in the reward information to the electronic device corresponding to the user identifier.

[0180] In some embodiments of the present application, the Figure 3 The device server shown can be used for Figure 1 That is, the device server can be connected to the user's electronic device in communication so that upon receiving the user's input operation (such as Figure 2 After the operation of button 203 is performed, the reward information configured for the user is determined through the logic implementation of the above modules. Further, the device server can send the reward information for the user to the user's electronic device through the reward configuration module to realize the distribution of the prize information.

[0181] It should be noted that, in a specific implementation, the electronic device involved in the embodiments of the present application may have a variety of different implementations.

[0182] Exemplarily, the electronic device in the embodiments of the present application may include at least one of a mobile phone, a foldable electronic device, a tablet computer, a desktop computer, a laptop computer, a handheld computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a personal digital assistant (PDA), an augmented reality (AR) device, a virtual reality (VR) device, an artificial intelligence (AI) device, a wearable device, a vehicle-mounted device, a smart home device, or a smart city device.

[0183] The data processing method provided in the embodiments of the present application is described in detail below.

[0184] As a possible implementation, refer to Figure 6 , is a flow chart of a method for determining reward information provided in an embodiment of the present application. The method can be applied to a device server. The device server can have the aforementioned Figure 3 The composition of Figure 6 As shown, the program may include:

[0185] S601: Obtain first operation information.

[0186] Exemplarily, the first operation information may be generated and sent to the device server after the electronic device receives a first operation input by a user indicating to conduct a lottery.

[0187] Combination Figure 2 As a possible implementation, the first operation may include operation 205. Correspondingly, the first operation information may correspond to the following: Figure 2 Operation information in 2.

[0188] For example, in this example, the first operation information may include information such as a task code and a user identifier.

[0189] The task code may be the code of the task instance corresponding to the lottery interface indicated by the user for lottery drawing. The electronic device may determine the task code according to the interface information displayed when receiving the user operation 205.

[0190] The user identification may include at least one of the following: IMEI, IMSI, user ID, currently logged-in account information, etc.

[0191] S602. Obtain reward information for the first task instance according to the first operation information.

[0192] The first task instance may be a task instance indicated by a task code included in the first operation information.

[0193] The device server may obtain the first task instance from one or more configured task instances according to the task code carried in the received first operation information, and read the reward information of the first task instance. In some embodiments, this step may be performed by a probability judgment module in the device server.

[0194] Combined with the above Figure 4 , the step of obtaining the reward information of the first task instance may specifically include: obtaining the reward content information and type identification of each reward information of the first task instance. When the reward information is configured with probability information, the step of obtaining the reward information of the first task instance may also include obtaining the probability information of each configured reward information.

[0195] As an example, take the first task instance as task instance A, and correspondingly configure reward information 1, reward information 2, reward information 3 and reward information 4 as an example.

[0196] Take the configuration of the type identification and probability information of each reward information as shown in Table 6 as an example. Then the reward information 1 can be the first type of reward information, that is, the bottom-line reward. The reward information 2 can be the second type and the third type of reward information, that is, the must-win reward and the limited reward. The reward information 3 and the reward information 4 can be the third type of reward information, that is, the limited reward.

[0197] Thus, in S602, the device server may obtain the reward content information 1 corresponding to the reward information 1, the first identifier indicating that the reward information 1 is of the first type, and the probability information of the reward information 1, which is 0.7.

[0198] The device server can obtain the reward content information 2 corresponding to the reward information 2, indicating that the reward information 2 is a second identifier of the second type and the reward information 2 is also a third identifier of the third type.

[0199] The device server can obtain the reward content information 3 corresponding to the reward information 3, indicating that the reward information 3 is a third identifier of the third type, and the probability information of the reward information 3 is 0.2.

[0200] The device server may obtain reward content information 4 corresponding to reward information 4 , indicating that reward information 4 is a third identifier of the third type, and probability information 0.1 of reward information 4 .

[0201] It should be noted that, in some embodiments of the present application, the device server may also obtain issued information corresponding to each reward information.

[0202] For example, the device server may obtain the issued record correspondence table shown in Table 3 or Table 4.

[0203] S603: Determine whether the current user is a first type of user.

[0204] Exemplarily, the first type of user corresponds to an abnormal user. For example, if a user enters a lottery operation multiple times in a short period of time, the user can be configured as an abnormal user. The short period of time can be defined by a preconfigured duration. For example, the preconfigured duration is duration T1, and within duration T1, when the number of times operation information with the same user identifier is received reaches the corresponding maximum threshold, the user is an abnormal user.

[0205] Correspondingly, the device server may store the user identification of the abnormal user. For example, the device server may store an abnormal user list, and the abnormal user list may be used to store the user identification of the abnormal user (such as user ID and other information).

[0206] In the present application, the device server may determine whether the current user is an abnormal user before determining the distribution of reward information according to the probability configuration and the limited configuration.

[0207] For example, the device server may determine, based on the user ID carried in the first operation information acquired in S601, whether the user ID is included in the abnormal user list.

[0208] When the user ID carried in the first operation information is included in the abnormal user list, the user is a first-category user, and the device server executes S604 accordingly.

[0209] If the user ID carried in the first operation information is not included in the abnormal user list, the user is not a first-category user, that is, the user is a normal user. The device server executes S605 accordingly.

[0210] S604: Determine and configure the first reward information.

[0211] Exemplarily, the first reward information may be the first type of reward information, that is, a guaranteed reward, such as reward information 1.

[0212] In some embodiments, the device server may directly distribute a guaranteed reward to the user if it is determined that the user is an abnormal user.

[0213] It is understandable that in other embodiments, the judgment logic of S603 in the device server may also be omitted. For example, the device server may directly jump to execute S605 after executing S602. In this way, in a safe environment (such as when there are no abnormal users), judgment execution steps are saved and processing efficiency is improved.

[0214] S605: Determine whether to configure the second type of reward information.

[0215] Exemplarily, the second type of reward information may be reward information of a guaranteed reward. For example, the second type of reward information may be reward information 2 in the above example.

[0216] In the present application, the device server may record the number of operation information corresponding to the same user ID that has been received after the first task instance is run, and then determine whether to configure the second type of reward information for the corresponding first user when the first operation information is currently received.

[0217] For example, before receiving the first operation information, the number of first operation information received recorded by the device server is a; and the number threshold of the second type of reward information is configured as m.

[0218] In S601, after receiving the first operation information, the device server may update a to a+1. In S605, the device server may determine to configure the second type of reward information 2 for the first user identification when it is determined that a+1 reaches m. The process jumps to S606.

[0219] On the contrary, when it is determined that a+1 does not reach m, the device server may determine to configure the second type of reward information 2 for the first user identification. Jump to S608.

[0220] In some embodiments of the present application, when it is determined to configure the second type of reward information, after jumping to S606, the device server may set the number of times the first operation information has been received to 0, thereby avoiding the second type of reward information being distributed to the first user identifier.

[0221] S606: Determine whether the limited configuration is in compliance.

[0222] It should be noted that, in this example, the types of reward information 2 include the second type and the third type. Then, when it is determined in S605 that reward information 2 meets the distribution conditions corresponding to the number threshold of the second type, the device server may also execute S606 to determine whether reward information 2 meets the distribution conditions corresponding to the limited configuration of the third type.

[0223] Correspondingly, if the reward information type is only the second type, S606 can be skipped and S607 can be executed.

[0224] In this example, the device server can determine whether the reward information 2 meets the third type of distribution conditions for each third type of reward information (such as reward information 2) based on the configured information of the reward information recorded in the corresponding table of issued records and the limited configuration corresponding to the reward information (such as the limited configuration shown in Table 2).

[0225] The configured information may include the number of rewards distributed in each dimension. In combination with the above description, each dimension may include at least one of the following: a single user dimension, an all user dimension, a year dimension, a month dimension, a day dimension, an hour dimension, a minute dimension, a second dimension, etc.

[0226] In this example, the device server can confirm dimension by dimension according to the configured information, so that after the reward information 2 is distributed again, it will not exceed the limited configuration. In this way, the reward information 2 meets the limited configuration. Therefore, it can jump to S607. On the contrary, if the distribution of reward information 2 again will cause at least one dimension to exceed the limited configuration, the reward information 2 will not be distributed. For example, jump to S604.

[0227] S607: Determine and configure the second reward information.

[0228] Exemplarily, the second reward information may be reward information of the second type, that is, a guaranteed reward, such as reward information 2.

[0229] In this way, through the above S606-S607, the situation of determining that the configuration must receive the reward is explained in detail.

[0230] Correspondingly, in S605, when the device server determines that no guaranteed reward is configured, the reward information configured for the first user identifier can be determined from one or more reward information configured with probability information in the first task instance.

[0231] Exemplarily, the process may include:

[0232] S608. Determine to configure third reward information according to the probability information of the configured reward information.

[0233] For example, the device server may Figure 5 The illustrated solution enables the determination of third reward information among all reward information that has been configured with probability information.

[0234] For example, continue with the example in Table 6. In the current task instance, the reward information configured with probability information may include reward information 1, reward information 3, and reward information 4.

[0235] In this way, the device server can Figure 5 The scheme shown implements selecting the third reward information from reward information 1, reward information 3 and reward information 4.

[0236] In the following description, the third reward information is taken as reward information 3 as an example.

[0237] S609: Determine whether the limited configuration is in compliance.

[0238] Similar to the description of S606 above, in this example, the limited amount configuration of the third reward information is taken as an example.

[0239] In this way, the device server can determine whether the configuration of the reward information 3 complies with the limited configuration according to the configured information of the reward information 3. The specific execution can refer to S606, which will not be repeated here.

[0240] In this application, if the configuration of the third reward information (such as reward information 3) meets the limited configuration, S610 is executed. On the contrary, if the configuration of the third reward information does not meet the limited configuration, the third reward information is not configured for the first user identifier this time. For example, jump to execute S604. Configuring the first reward information for the first user identifier, that is, configuring the bottom-line reward.

[0241] S610: Determine and configure the third reward information.

[0242] Thus, through the above solution, the device server can determine the reward information configured for the current first user identification after receiving the first operation information, such as the first reward information in S604, the second reward information in S607, or the third reward information in S610.

[0243] It should be noted that each of the above steps can be accomplished by Figure 3 The probability judgment module and / or the limit judgment module in the device server shown are implemented.

[0244] Exemplarily, S606 and S609 may be implemented by a limit determination module. Figure 6 The other logical steps in can be executed by the probability judgment module.

[0245] In the present application, after determining the reward information configured for the current first user identifier, the device server can distribute the reward information to the electronic device through the reward configuration module.

[0246] For example, taking the device server determining to configure the first reward information (such as reward information 1) as an example, the reward configuration module can send information such as reward content information 1 included in the reward information 1 to the electronic device corresponding to the first user identifier.

[0247] Similarly, taking the device server determining to configure the second reward information (such as reward information 2) as an example, the reward configuration module can send information such as reward content information 2 included in the reward information 2 to the electronic device corresponding to the first user identifier.

[0248] Taking the device server determining to configure the third reward information (such as reward information 3) as an example, the reward configuration module can send information such as reward content information 3 included in the reward information 3 to the electronic device corresponding to the first user identifier.

[0249] The above Figure 6 In the example of , a solution for determining a limited configuration is provided. In some implementations of the present application, the device server can combine the storage space size and data reading rate of different storage media to achieve fast determination of limited configuration.

[0250] In an embodiment of the present application, a first storage medium and a second storage medium may be configured in the device server. The first storage medium may have a large storage space, and the corresponding data read rate is low. In contrast, the second storage medium has a high data read rate, but the storage space is limited. As a possible implementation, the first storage medium may be an external memory or a hard disk configured in the device server. The second storage medium may be a memory configured in the device server.

[0251] As a possible implementation, the data in the first storage medium may be stored in a corresponding database, such as a MySQL database. Correspondingly, the data in the second storage medium may also be stored in a corresponding database for maintenance, such as a Redis database.

[0252] In this application, since each task instance is configured with limited configurations in multiple dimensions, the amount of stored data of the issued configuration (that is, the above-mentioned issued record correspondence table) as shown in Table 2 is very large and cannot be stored in the memory. When the issued record correspondence table is stored in the external memory, during the limited configuration judgment process, the processor of the device server needs to frequently read data from the external memory to obtain the configured information of each dimension. This will generate a large amount of data reading and writing overhead, which is not conducive to the rapid confirmation and distribution of reward information.

[0253] In some embodiments of the present application, the complete configured information can be stored in the external memory. In addition, simplified fields of each configured information can also be configured in the internal memory. In this way, only a small amount of data needs to be stored in the internal memory, so that when making a limited configuration judgment, there is no need to frequently read a large amount of data from the external memory. This achieves the purpose of improving the efficiency of limited configuration and reducing the overhead of the process. The following is a specific description.

[0254] For ease of explanation, Figure 3 Take task instance A in as an example to illustrate.

[0255] In the following example, the task instance A can be configured with limited configurations in four dimensions, such as dimension 1, dimension 2, dimension 3, and dimension 4. Thus, the configured information corresponding to the reward information 1 involved in the above example may specifically include:

[0256] User ID: 1001; #User ID is 1001;

[0257] Reward information code: pack01; #The code of the reward information corresponding to the current record is pack01, corresponding to reward information 1;

[0258] Dimension 1 = a11 times; #The number of times the current user has received reward information 1 in dimension 1 is a11 times;

[0259] Dimension 2 = a12 times; #The number of times the current user has received reward information 1 in dimension 2 is a12 times;

[0260] Dimension 3 = a13 times; #The number of times the current user has received reward information 1 in dimension 3 is a13 times;

[0261] Dimension 4 = a14 times; #The number of times the current user has received reward information 1 in dimension 4 is a14 times.

[0262] The above 6 data segments can be stored in external memory respectively.

[0263] In addition, the external memory may also store the current user ID and configured information for receiving other reward information.

[0264] For example, reward information 2 corresponds to:

[0265] User ID: 1001, reward information code: pack02, dimension 1 = a21 times, dimension 2 = a22 times, dimension 3 = a23 times, dimension 4 = a24 times.

[0266] Reward information 3 corresponds to:

[0267] User ID: 1001, reward information code: pack03, dimension 1 = a31 times, dimension 2 = a32 times, dimension 3 = a33 times, dimension 4 = a34 times.

[0268] Reward information 4 corresponds to:

[0269] User ID: 1001, reward information code: pack04, dimension 1 = a41 times, dimension 2 = a42 times, dimension 3 = a43 times, dimension 4 = a44 times.

[0270] Therefore, at least 24 data segments are required in the external memory to store the reward acquisition status of the user with user ID 1001 in the task instance A.

[0271] In this application, simplified fields corresponding to the reward information that has been obtained can be configured in the memory.

[0272] Exemplarily, a simplified field in memory may consist of two parts: a key part and a value part.

[0273] In some embodiments, the key part is used to identify the User ID, the reward information code, and the dimension identifier. The value part is used to identify the number of acquisitions corresponding to the key. In other embodiments, the key part may include a single user or total user flag, a reward information code, a dimension identifier (year, month, etc.), a current dimension start timestamp, etc.

[0274] For example, take user ID 1001, reward information 1, and dimension 1 as an example.

[0275] The corresponding simplified fields in the memory may include a field of "key1=1001:pack01:1,value=a11". Correspondingly, take the example that user ID 1001 has received reward information 1 in all dimensions. The following four fields can be stored in the memory: "key1=1001:pack01:1,value=a11", "key1=1001:pack01:2,value=a12", "key1=1001:pack01:3,value=a13", "key1=1001:pack01:4,value=a14".

[0276] This enables the recording of the configured information of the reward information 1 in the memory.

[0277] In this application, the device server can generate and store corresponding simplified fields in the memory for each reward information that has been received. Figure 7 As shown, the simplified fields are configured in the memory of the device server, and the complete configuration information is stored in the external memory. Figure 6 S606 or S609 shown is to quickly obtain the configured information and make a judgment on the limited configuration.

[0278] As an implementation, Figure 8 A schematic diagram of the limit determination process is provided. This scheme can be applied to Figure 3 In the limit determination module shown in FIG. Figure 8 The solution implementation shown can be used to implement the judgment logic of whether the distribution of reward information will cause the limited configuration of each dimension to be inconsistent with multiple different dimensions of reward information.

[0279] like Figure 8 As shown, the process may include:

[0280] S801: Generate a first key value according to first operation information and reward information, wherein the first key value corresponds to a first dimension.

[0281] Exemplarily, the quantity limit determination module may execute S801 when the quantity limit determination is triggered. For example, the quantity limit determination module may execute S606 or S609 when the quantity limit determination is triggered.

[0282] In this application, the first operation information is the first operation information generated by the first electronic device after the first user inputs the first operation through the first electronic device, and the user identifier of the first user (and the first electronic device) is the first user identifier. The generation and acquisition process of the first operation information can refer to Figure 6 The instructions in are not repeated here.

[0283] As an implementation, the limit determination module may obtain the reward information corresponding to the configuration of the first task instance according to the task code of the first task instance carried in the first operation information.

[0284] The limit determination module may generate a first key value of the first dimension accordingly.

[0285] For example, in combination with the above description, take the example that the first reward information includes reward information 1, and the corresponding limited configuration includes dimension 1, dimension 2, dimension 3 and dimension 4.

[0286] In this example, the limited determination module can generate key1 of dimension 1 corresponding to reward information 1 after the first operation information arrives.

[0287] For example, key1=1001:pack01:1.

[0288] S802: Determine whether the first key value exists in the memory.

[0289] Exemplarily, the limit determination module may search in the memory according to the generated key1 to determine whether key1 and the corresponding value are stored in the memory.

[0290] Combination Figure 7 As described in, in this application, when key1 corresponds to user ID, reward information, and dimension 1 has been claimed, the simplified fields corresponding to the configured information can be stored in the memory. Correspondingly, when there are multiple rewards that have been claimed, multiple simplified fields under different dimensions corresponding to multiple reward information can be stored in the memory.

[0291] In this way, when the first key value (such as key1) exists, the value corresponding to key1 in the memory can be the number of times the userID is 1001, the reward information is 1, and the dimension 1 corresponds to the number of times the reward has been received.

[0292] In this example, if the first key value exists in the memory, S804 is executed. Correspondingly, if the first key value does not exist in the memory, S803 is executed.

[0293] S803. Increase the value of the first key by 1.

[0294] Take the first key value (such as key1) in the memory as an example.

[0295] The limit determination module can determine whether the first operation information satisfies the limit configuration of the first dimension according to the data (value) corresponding to key1 stored in the memory.

[0296] Exemplarily, the limit determination module may first perform a process of adding 1 to the value of key1 stored in the memory. In this way, the value of key1 in the memory after processing is: if the first user identifier corresponding to the current first operation information is configured with reward information 1, the number of times the rewards have been received under the current dimension (i.e., user ID is 1001, reward information 1, dimension 1).

[0297] Further, the limit determination module can determine whether the configuration of the first user identifier exceeds the limit configuration of the first dimension according to the value after the processing. For example, the process jumps to S805.

[0298] S804: Get data from the external memory, generate a first key value and a corresponding value in the memory, and increase the value by 1.

[0299] In this example, it is assumed that key1 is not in the memory. Correspondingly, the user ID is 1001, and reward information 1 has not been claimed under containment 1, or the corresponding configured information is lost due to memory abnormality.

[0300] Therefore, the limited quantity determination module can read the number of times received corresponding to "user ID is 1001, reward information 1, dimension 1" from the external memory according to task code 1, user ID is 1001, and the reward information code of reward information 1 and the identifier of dimension 1. Correspondingly, the limited quantity determination module can generate simplified fields of key1 and corresponding value in the memory according to the read information.

[0301] Similar to the processing in S803, the limit determination module can determine the value that identifies the number of times the reward has been received under the current dimension for key1 generated in the memory and corresponding to the first key value generated in S801. The limit determination module can add 1 to the value to obtain the number of times the reward has been received after the reward information 1 is reconfigured. Then execute S805.

[0302] S805: Determine whether it is greater than the corresponding limit configuration.

[0303] Exemplarily, the limit determination module may compare the value obtained after processing in S803 or S804 with the limit configuration of the corresponding dimension to determine whether the current dimension is greater than the corresponding limit configuration.

[0304] For example, the limit determination module can obtain the limit value in the limit configuration according to the code corresponding to "user ID is 1001, reward information 1, dimension 1". As a strength, the limit determination module can obtain the limit value corresponding to "user ID is 1001, reward information 1, dimension 1" from the multi-dimensional limit information configuration shown in Table 2.

[0305] Correspondingly, when it is determined that it is greater than the corresponding limit configuration, it indicates that if the reward information 1 is configured again, the limit configuration under dimension 1 will not be met. In other words, the reward information 1 cannot be configured for user ID 1001.

[0306] On the contrary, if the value after adding 1 is not greater than the corresponding limit configuration, it means that if the reward information 1 is configured again, the limit configuration under dimension 1 is still met. In other words, the reward information 1 can be configured for user ID 1001.

[0307] In some embodiments, if the current reward information 1 is configured with only one dimension (such as dimension 1), the limited configuration is judged to pass, and the reward information 1 is configured as follows: Figure 6 The logic shown is executed backwards.

[0308] In this embodiment, the current reward information 1 is configured with multiple dimensions as an example. In some implementations, the processing of S801-S805 can also be called first dimension limit determination.

[0309] Thus, through the processing of S801-S805, if the judgment result of S805 is "No", it indicates that the first dimension (ie, dimension 1) has passed the limit judgment. Correspondingly, the limit judgment module can perform limit judgments of other dimensions according to the similar logic of S801-S805.

[0310] S806. The first key value is added to the preset list.

[0311] In the present application, the limit determination module can configure a corresponding preset list (list) for the first reward information. In this way, when it is determined that the limit determination of the first dimension is passed, the limit determination module can add the key value corresponding to the first dimension (such as key1) to the preset list. Each key in the preset list corresponds to the dimension that the limit determination is passed.

[0312] It should be noted that if Figure 8 As shown, when the limit judgment of any dimension fails, the limit judgment module can perform a process of subtracting 1 from the corresponding values ​​of all key values ​​in the preset list.

[0313] Combined with the description of S803 and S804, before the key is put into the preset list, when judging whether it meets the limited configuration of the corresponding dimension, the value of the key will be increased by 1. Then, the value of all keys in the preset list will be increased by 1, corresponding to the number of times the first reward information has been received after this configuration.

[0314] In this way, if it is determined that the limit judgment fails, the limit judgment module performs a subtraction process on the value of all keys in the preset list, so that the value of each key can accurately reflect the number of times the current dimension has been collected.

[0315] Next, the limit determination module can execute the following S807: second dimension limit determination, and if the second dimension limit configuration is met, execute S808: add the second key value to the preset list. Thus, the second dimension limit determination logic is completed. The processing logic of S807 to S808 can refer to the specific description of the first dimension limit determination in S801-S806 above, and the specific implementation process can refer to each other.

[0316] After that, similarly, the limit judgment logic of other dimensions is carried out.

[0317] For example, the limit judgment logic for the third dimension may include: S809: third dimension limit judgment, and if the limit configuration of the third dimension is met, execute S810: add the third key value to the preset list.

[0318] For another example, the limit judgment logic for the fourth dimension may include: S811: fourth dimension limit judgment, and if the limit configuration of the fourth dimension is met, execute S812: add the fourth key value to the preset list.

[0319] It should be noted that, in this example, the first reward information is configured with four-dimensional limited configuration as an example. In other embodiments, when the limited configuration dimensions of the specific first reward information are different, the device server can also perform corresponding limited judgments for each dimension respectively.

[0320] By analogy, take the case where all dimension limit judgments are passed as an example. In this way, after completing the limit judgments of all dimensions, the limit judgment module can execute S813: determine that the key values ​​of all dimensions are added to the preset list. This indicates that the limit judgments of all dimensions are successfully passed. In this way, the limit judgment module can determine that the limit judgment of the first reward information is passed, and can configure the first reward information for the first user identifier. For subsequent specific processing, please refer to Figure 6 The relevant instructions in are not repeated here.

[0321] In this way, combined Figures 6 to 8With the instructions, the device server can efficiently and accurately realize multi-dimensional reward information confirmation.

[0322] In other embodiments of the present application, the device server may also provide multi-threaded concurrent capabilities. Thus, when two or more operation information corresponding to the same user ID or different user IDs are received in a short period of time, the device server may perform parallel processing respectively. For example, the device server may be based on the following example: Figure 6 or Figure 8 The solution shown implements parallel processing of the received operation information, thereby providing a reward information extraction service to multiple electronic devices simultaneously through one device server.

[0323] As an example, refer to Fig. 9 , taking the example of a device server receiving the first operation information and the second operation information in a short period of time, wherein the time when the device server receives the first operation information is earlier than the time when the device server receives the second operation information.

[0324] In addition, the first operation information and the second operation information may correspond to different user identifiers. For example, the first operation information may include a user ID of 1001, and the second operation information may include a user ID of 1002.

[0325] In this way, the device server can run the first thread to respond to the first operation information and determine that the user with the userID 1001 configures the corresponding reward information.

[0326] like Fig. 9 As shown, the first thread can implement the limited configuration judgment of the first dimension by executing S801 to S805. For specific steps, please refer to Figure 8 Instructions in .

[0327] Similarly, the device server may run a second thread to determine, in response to the second operation information, that the user whose user ID is 1002 has configured corresponding reward information.

[0328] like Fig. 9 As shown, the second thread can implement the limited configuration judgment of the first dimension by executing S901 to S905. For specific steps, please refer to Figure 8 Instructions in .

[0329] For example, in Fig. 9 In the example of , the limited configuration of the first dimension that the device server can perform through the second thread may include:

[0330] S901. Generate a fifth key value of the first dimension according to the second operation information and the reward information. The fifth key value may correspond to the simplified field in the memory under the first dimension corresponding to when the user ID of the second operation information receives the reward information 1. For example, the fifth key value may include "key5=1002:pack01:1".

[0331] S902: Determine whether the fifth key value exists in the memory.

[0332] S903: Determine again whether the fifth key value exists in the memory.

[0333] In some embodiments, the execution of S903 can make the limit determination process of the second operation information more accurate. In other embodiments, S903 can also be an optional step, that is, after executing S902, the process directly jumps to execute S904. The specific situation will be described in detail later.

[0334] S904: Get data from the external memory, generate a fifth key value and a corresponding value in the memory, and increase the value by 1.

[0335] S905: Determine whether it is greater than the corresponding limit configuration.

[0336] This can realize multi-threaded concurrent processing based on different threads and parallel judgment of different operation information.

[0337] It should be noted that, in some cases, the first operation information and the second operation information are respectively for different task instances, or for different reward information. Figures 6 to 8 The solution implementation shown independently determines the corresponding reward information configured for the user with user ID 1001, and determines the corresponding reward information configured for the user with user ID 1002.

[0338] Thus, the above Fig. 9 S903 shown can be omitted. Therefore, the limit determination logic of the second operation information can include S901-S902-S904-S905.

[0339] In other cases, the user IDs of the first operation information and the second operation information are different, but the judgment can be performed on the same reward information (such as the first reward information) in the same task instance.

[0340] In this way, the device server can avoid problems in judging the two operation information by configuring the locking logic of the memory information.

[0341] As an implementation, Fig. 9As shown, after the first thread executes S802, if it is determined that there is no first key value corresponding to the first operation information in the memory, the first thread executes S803. During the execution of S803, the device server can assign the operation lock corresponding to the first reward information to the first thread, that is, the first thread holds the lock. In this way, during this process, if other threads need to read or modify the content corresponding to the first reward information in the memory, they can wait for the first thread to end the lock, that is, the first thread unlocks. In this way, it is ensured that when the first thread modifies the simplified field of the first reward information in the memory, other threads wait for the unlocking before operating the simplified field.

[0342] For example, after the second thread executes S902, if it is determined that the fifth key value is not included in the memory, before executing S903, it can be determined that the operation lock corresponding to the first reward information is being locked by other threads (such as being locked by the first thread). In this way, the second thread can wait for the operation lock corresponding to the first reward information to be released before executing S903.

[0343] It is understandable that, before the second thread reads the relevant data of the first reward information from the external memory, the first thread can read the configured information of the first reward information from the external memory through S803 and generate the corresponding simplified field in the memory. Therefore, after the first thread releases the operation lock corresponding to the first reward information, the simplified field corresponding to the fifth key value may already exist in the memory. In this way, before the second thread reads the configured information of the first reward information from the external memory (i.e., executes S904), it can execute S903 again to determine whether the fifth key value exists in the memory, so as to achieve the effect of accurately matching the simplified field in the memory.

[0344] Correspondingly, in other scenarios, after the second thread executes S903, if the fifth key value exists in the memory, the operation lock of the corresponding first reward information is being held by other threads. Then, the second thread can also wait for other threads to release the operation lock of the first reward implementation, and then execute subsequent operations such as adding 1 to the value of the fifth key value and limiting judgment. In this way, after the first thread updates the configured information of the first reward information, the second thread can make a limiting judgment based on the latest configured information. This improves the data accuracy in the multi-threaded concurrent processing mechanism.

[0345] It is understandable that the electronic device provided in the embodiment of the present application includes a hardware structure and / or software module corresponding to each function in order to realize the above functions. Those skilled in the art should easily realize that, in conjunction with the units and algorithm steps of each example described in the embodiment disclosed herein, the embodiment of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but this implementation should not be considered to exceed the scope of the embodiment of the present application.

[0346] The embodiment of the present application can divide the functional modules of the above-mentioned electronic device according to the above-mentioned method example. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0347] For example, Fig.10 A schematic diagram of the composition of a data processing apparatus 1000 is shown. In some implementations, the data processing apparatus 1000 may be configured in a device server.

[0348] like Fig.10 As shown, the data processing device 1000 may include: a processor 1001 and a memory 1002. The memory 1002 is used to store computer-executable instructions. Exemplarily, in some embodiments, when the processor 1001 executes the instructions stored in the memory 1002, the data processing device 1000 may execute any of the methods shown in the above embodiments.

[0349] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0350] Fig.11 FIG. 1 is a schematic diagram showing the composition of a chip system 1100. In some implementations, the chip system 1100 may be configured as follows: Fig.10 In the data processing device 1000 shown, or, the chip system 1100 can be configured in the device server involved in the above embodiments.

[0351] like Fig.11As shown, the chip system 1100 may include: a processor 1101 and a communication interface 1102, which are used to support related devices to implement the functions involved in the above embodiments. In one possible design, the chip system also includes a memory for storing program instructions and data necessary for electronic devices. The chip system may be composed of chips, or may include chips and other discrete devices. It should be noted that in some implementations of the present application, the communication interface 1102 may also be referred to as an interface circuit.

[0352] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0353] The functions or actions or operations or steps in the above embodiments can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using a software program, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or may include one or more servers, data centers and other data storage devices that can be integrated with the medium. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0354] Although the present application has been described in conjunction with specific features and embodiments thereof, it is obvious that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Accordingly, this specification and the drawings are merely exemplary illustrations of the present application as defined by the appended claims, and are deemed to have covered any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A data processing method, characterized in that: The method is applied to a data processing device, wherein the data processing device is configured with at least one task instance, and any of the task instances is configured with at least one reward information; The method comprises: Acquire first operation information; the first operation information includes: a first task code and a first user identifier; According to the first task code, obtaining reward information configured in the first task instance, wherein the first task code is the task code of the first task instance; the first task instance is included in the at least one task instance; Wherein, the first task instance is configured with second reward information; the obtaining of the reward information configured in the first task instance includes: obtaining reward content information and type identification corresponding to the second reward information; the type identification of the second reward information includes a second identification and a third identification; The second identifier is used to indicate that the second reward information is distributed when the operation request reaches the first number threshold, and the third identifier is used to indicate that the second reward information is distributed in limited quantity; The second reward information is configured with a first limit configuration, the first limit configuration includes limit thresholds of at least two dimensions corresponding to the second reward, the at least two dimensions including at least two of the following: a single user dimension, an all user dimension, a year dimension, a month dimension, a day dimension, an hour dimension, a minute dimension, and a second dimension; the first limit configuration is used to limit the quantity of the limited distribution; Determine target reward information from all reward information configured for the first task instance; The target reward information is distributed to a first electronic device corresponding to the first user identifier.

2. The method according to claim 1, characterized in that The first user identifier includes at least one of the following: The international mobile equipment identity code IMEI of the first electronic device, the international mobile subscriber identity number IMSI of the first electronic device, the account information logged in to the first electronic device, and the user identity code userID.

3. The method according to claim 1 or 2, characterized in that: The obtaining of reward information configured in the first task instance includes: Obtain reward content information and type identifier corresponding to each reward information configured in the first task instance; The type identifier of the reward information includes: a first identifier, a second identifier, and / or a third identifier.

4. The method according to claim 3, characterized in that The second reward information is configured with a first number threshold; The step of determining target reward information from all reward information configured for the first task instance includes: When the number of times the operation request including the first user identifier is received reaches the first number threshold, the target reward information is determined according to the second reward information.

5. The method according to claim 4, characterized in that In a case where the second reward information is not configured with the third identifier, determining the target reward information according to the second reward information includes: The second reward information is determined as the target reward information.

6. The method according to claim 4, characterized in that Before determining the target reward information according to the second reward information, the method further includes: After determining to distribute the second reward information, the number of times the second reward information is received in each of the at least two dimensions is less than or equal to the limit threshold of the corresponding dimension; The determining the target reward information according to the second reward information includes: The second reward information is determined as the target reward information.

7. The method according to claim 6, characterized in that The first limit configuration includes a first limit threshold of a first dimension; After the determination to distribute the second reward information, the number of times the second reward information is received in each dimension of the at least two dimensions is less than or equal to the limit threshold of the corresponding dimension, including: After determining to distribute the second reward information, the number of times the second reward information is collected in the first dimension does not exceed the first limit threshold.

8. The method according to claim 7, characterized in that After the determination to distribute the second reward information, the number of times the second reward information is received in the first dimension does not exceed the first limit threshold, including: Generate a first key value key according to the first request information; Determine whether the first key value exists in the first database of the data processing device; the first database is configured in the memory of the data processing device, and the first database is used to store the key value of the reward information that has been received and the corresponding value; If the first key value exists in the first database, obtaining a first numerical value corresponding to the first key value from the first database; Add 1 to the first value to obtain a second value; When the second value is less than or equal to the first limit threshold, after the second reward information is determined to be distributed, the number of times the second reward information is collected in the first dimension does not exceed the first limit threshold.

9. The method according to claim 8, characterized in that The first key value includes: corresponding characters of the first user identifier, corresponding characters of the reward information code, and corresponding characters of the first dimension.

10. The method according to claim 8 or 9, characterized in that: In a case where the first key value does not exist in the first database, the method further includes: The number of times the second reward information is received in the first dimension is read from the second database, and a first key value is generated and stored in the first database; wherein the second database is configured in the external memory of the data processing device, and the second database stores information on the number of times all reward information is received in all dimensions.

11. The method according to claim 10, characterized in that Before reading the number of times the second reward information is received in the first dimension from the second database, the method further includes: Determine that the operation lock of the first key value is not held by other threads.

12. The method according to claim 11, characterized in that In the case where the operation lock of the first key value is held by other threads, before reading the number of times the second reward information is received in the first dimension from the second database, the method further includes: waiting for the operation lock of the first key value to be released.

13. The method according to claim 12, characterized in that After the operation lock of the first key value is released, and before the number of times the second reward information is received in the first dimension is read from the second database, the method further includes: It is determined that the first key value does not exist in the first database.

14. The method according to claim 6, characterized in that The first task instance is configured with first reward information, and the type identifier of the first reward information is the first identifier; After the second reward information is distributed, if the number of times the second reward information is received in at least one of the at least two dimensions is greater than the limit threshold of the corresponding dimension, determining the target reward information according to the second reward information includes: The first reward information is determined as the target reward information.

15. The method according to any one of claims 4 to 9 or any one of claims 11 to 14, characterized in that: The first task instance is configured with first reward information, and the type identifier of the first reward information is the first identifier; The data processing device is provided with an abnormal user list, wherein the abnormal user list stores at least one user identification; The step of determining target reward information from all reward information configured for the first task instance includes: In a case where the first user identifier is included in the abnormal user list, the first reward information is determined as the target reward information.

16. The method according to any one of claims 4 to 9 or any one of claims 11 to 14, characterized in that: At least two third reward information are configured in the first task instance, and the type identifier of the third reward information is the third identifier; each of the third reward information is configured with corresponding probability information; The at least two third reward information include: fourth reward information, and fifth reward information; The obtaining, according to the first task code, reward information configured in the first task instance includes: Acquire reward content information of the fourth reward information, probability information of the fourth reward information, and a type identifier of the fourth reward information; Acquire reward content information of the fifth reward information, probability information of the fifth reward information, and type identifier of the fifth reward information; The step of determining target reward information from all reward information configured for the first task instance includes: Generate a random positive integer; According to the random positive integer falling within the first interval, the target reward information is determined according to the fourth reward information; or, According to the random positive integer falling within the second interval, the target reward information is determined according to the fifth reward information; Among them, the first interval is [0, a], the second interval is [a, a+b], the probability information of the fourth reward information is 0.01*a, the probability information of the fifth reward information is 0.01*b, and a+b is not greater than 1.

17. The method according to claim 16, characterized in that The fourth reward information is further configured with the second identifier; the fourth reward information is configured with a second limit configuration, the second limit configuration including limit thresholds of at least two dimensions corresponding to the fourth reward; The step of determining the target reward information according to the fourth reward information includes: After determining to distribute the fourth reward information, the number of times the fourth reward information is claimed in each of at least two dimensions of the second limit configuration is less than or equal to the limit threshold of the corresponding dimension; determining the fourth reward information as the target reward information; or, After determining to distribute the fourth reward information, the number of times the fourth reward information is received in at least one of the at least two dimensions of the second limit configuration exceeds the limit threshold of the corresponding dimension; The reward information whose type identifier is the first identifier is determined as the target reward information.

18. The method according to claim 16, characterized in that When the fifth reward information is only configured with the third identifier, determining the target reward information according to the fifth reward information includes: The fifth reward information is determined as the target reward information.

19. A data processing device, characterized in that: The device is used to perform the method according to any one of claims 1 to 18.

Images