Data processing method and device

Abstract

The embodiment of the invention provides a data processing method and device, and relates to the field of data processing. According to the method, the convenience of different task configuration can be improved, and the corresponding reward information can be accurately and quickly determined according to the operation input by the user. The method is applied to a data processing device, the data processing device is configured with information of at least one task instance, and the information of each task instance comprises corresponding basic information, task conditions and reward information. The method comprises the following steps: acquiring first operation information, wherein the first operation information corresponds to an operation input into first electronic equipment by a user; basic information of at least one started task instance is obtained; and determining that the first basic information corresponds to the first operation information. Acquiring a first task condition of the first task instance; and determining to configure first reward information for the first electronic equipment according to the correspondence of the first operation information and the first task condition. The first reward information is reward information of the first task instance.

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 device. Background Art

[0002] After the user inputs an operation to the electronic device, the electronic device can get a corresponding response. For example, the user inputs a consumption (such as recharge) operation, and after the recharge is successful, the electronic device can provide the user with the corresponding function after the recharge. For another example, the user inputs a search operation, and the electronic device can provide the user with a display function of the search results.

[0003] In some cases, the electronic device can interact with the corresponding device server to provide a richer user experience. For example, the device server can push additional rewards to the user's electronic device based on the pre-configured task instance and the recharge operation input by the user. For another example, the device server can push preferential information corresponding to the searched product to the user's electronic device based on the pre-configured task instance and the search operation input by the user.

[0004] The more task instances are configured in the device server, the more types of reward information can be provided to users in more scenarios. However, the configuration of task instances of different types and scenarios varies greatly. Deploying and running a large number of task instances will cause excessive operating overhead of the device server, which is not conducive to implementation. Summary of the invention

[0005] The present application provides a data processing method and device, which can accurately and quickly determine corresponding reward information according to the operation input by the user. In some implementations, the solution provided by the embodiments of the present application can also improve the convenience of different task 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 information of at least one task instance, the information of each task instance including corresponding basic information, task conditions, and reward information. The method comprises: obtaining first operation information, the first operation information corresponding to an operation inputted by a user into a first electronic device. Obtaining basic information of at least one enabled task instance. Determining that the first basic information corresponds to the first operation information. The first basic information is basic information of a first task instance, the first task instance being included in the at least one enabled task instance. Obtaining a first task condition of the first task instance. Determining that first reward information is configured for the first electronic device based on the correspondence between the first operation information and the first task condition. The first reward information is reward information for the first task instance.

[0008] In this way, through the matching process of basic information and task conditions, the reward information corresponding to the current user operation can be accurately determined. It can be understood that different task instances can correspond to different scenarios. Then, through the screening and judgment mechanism of task instances in different scenarios, the judgment mechanism of different task instances in multiple scenarios can be conveniently implemented, and then the reward information in different scenarios can be determined.

[0009] Optionally, at least one operation message queue is configured in the data processing device, and different operation message queues are used to store different types of operation information. The obtaining of the first operation information includes: obtaining the first operation information in a first message queue, and the type of the first message queue is the same as the type of the first operation information. In this example, by configuring different message queues for different types of operation information, the operation information can be divided and stored according to type, which is convenient for subsequent processing.

[0010] Optionally, the type of the first operation information is a first type. The type of operation information includes at least one of the following: consumption, browsing, searching, booking, card binding, and logging in. The first type is included in the type of the operation information.

[0011] Optionally, the type of the first operation information is a consumption type, and the first operation information includes at least one of the following: a consumption amount, a currency identifier, and a device identifier of the first electronic device. Exemplarily, the device identifier of the first electronic device may be a user ID of the electronic device that generates the first operation information. The first electronic device may generate the first operation information after receiving the user's operation.

[0012] Optionally, each of the task instances is configured with a status identifier. The status identifier is configured as a first value or a second value. The task identifier is configured as the first value, indicating that the task instance is not enabled. The task identifier is configured as the second value, indicating that the task instance is enabled.

[0013] Optionally, obtaining basic information of at least one enabled task instance includes: obtaining basic information of a task instance whose status identifier is the second value among at least one configured task instance.

[0014] In this way, by configuring different status identifiers, the management of the working status of the task instance is realized. It is understandable that some task instances can be configured to take effect within a fixed time period. In this way, through the status identifier, the task instance can be controlled to work within the corresponding time period.

[0015] Optionally, the basic information of the task instance includes at least one of the following: task type, business field, task code, task name, country information, time zone information, and executable task time.

[0016] Optionally, determining that the first basic information corresponds to the first operation information includes: determining that each data included in the first operation information is the same as each data included in the first basic information. Exemplarily, the process of determining that the first basic information corresponds to the first operation information can be implemented by comparing each data item by item. Through this implementation, a preliminary screening of enabled task instances can be achieved. Thereby reducing the overhead of subsequent processing.

[0017] Optionally, obtaining the first task condition of the first task instance includes: obtaining the first task condition according to the task code of the first task instance.

[0018] Optionally, the first task condition includes first task setting information and first task achievement condition information. The first task setting information includes at least one of the following: country information, APP package name, currency information. The first task achievement condition information includes at least one of the following: cumulative or single calculation, consumption amount, number of consumptions, and search frequency.

[0019] Optionally, before determining to configure the first reward information for the first electronic device according to the correspondence between the first operation information and the first task condition, the method further includes: performing pre-configured data standardization processing on the first operation information to obtain first standard operation information. In this way, through standardization processing, the operation information in different scenarios can be unified to the same standard to facilitate subsequent accurate matching processing.

[0020] Optionally, determining that the first basic information corresponds to the first operation information includes: determining that various data included in the first standard operation information are the same as various data included in the first basic information.

[0021] Optionally, determining to configure the first reward information for the first electronic device based on the correspondence between the first operation information and the first task condition includes: determining whether various data included in the first standard operation information meet the conditions indicated by the first task setting information.

[0022] Optionally, the method further includes: determining whether various data included in the first standard operation information satisfies a condition indicated by the first task achievement condition information.

[0023] Optionally, the method further includes: obtaining the first reward information according to the encoding information of the first task instance.

[0024] Optionally, the first reward information includes at least one of the following: reward type, reward coding information, reward information issuance method, reward amount, and reward available time.

[0025] Optionally, the method also includes: sending the first reward information to the first electronic device.

[0026] According to a second aspect, a data processing device is provided, wherein the data processing device is used to execute the method provided by the first aspect and any possible design thereof.

[0027] According to a third aspect, a server is provided, which may be configured with the data processing device provided by the second aspect, so that the server executes the method provided by the first aspect and any possible design thereof when operating.

[0028] In a fourth aspect, a chip system is provided, which is applied to the aforementioned data processing device and / or server. 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 the memory 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 instruction, the technical solution provided in the above-mentioned first aspect and any possible implementation thereof is executed.

[0029] In a fifth aspect, the present application also provides a computer-readable storage medium, including computer instructions. When the computer instructions are executed on a relevant device, the relevant device executes the technical solution provided in the above-mentioned first aspect and any possible implementation thereof.

[0030] In a sixth 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.

[0031] It can be understood that the solutions provided in the second aspect to the sixth 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

[0032] Figure 1 A schematic diagram of a multi-device scenario provided in an embodiment of the present application;

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

[0034] Figure 3 A schematic diagram of the composition of task configuration information provided in an embodiment of the present application;

[0035] Figure 4 A schematic diagram of the composition of an operation message queue provided in an embodiment of the present application;

[0036] Figure 5 A schematic diagram of data standard processing provided in an embodiment of the present application;

[0037] Figure 6 A schematic diagram of the interaction between different modules in a device server provided in an embodiment of the present application;

[0038] Figure 7 A schematic diagram of an interaction process between different devices provided in an embodiment of the present application;

[0039] Figure 8 A logic diagram of cumulative judgment provided in an embodiment of the present application;

[0040] Fig. 9 A schematic diagram of the device composition of a device server configuration task instance provided in an embodiment of the present application;

[0041] Fig.10 A schematic diagram of a configuration interface for basic task information provided in an embodiment of the present application;

[0042] Fig.11 A schematic diagram of a configuration interface for task planning settings provided in an embodiment of the present application;

[0043] Fig.12 A schematic diagram of a configuration interface for a task achievement condition provided in an embodiment of the present application;

[0044] Fig.13 A schematic diagram of a configuration interface for task reward settings provided in an embodiment of the present application;

[0045] Fig.14 A schematic diagram of a configuration interface for a search-type task instance provided in an embodiment of the present application;

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

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

[0048] In the following, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this embodiment, unless otherwise specified, "plurality" means two or more.

[0049] Currently, electronic devices can respond accordingly according to operations input by users, so as to provide users with different functional experiences.

[0050] Exemplarily, the operation input by the user may include a search operation, a consumption operation, and the like.

[0051] For example, when a user inputs a search operation, the electronic device can perform a related search based on the input field according to the operation input by the user. For another example, when a user inputs a consumption operation for a certain function, the electronic device can perform consumption processing (such as recharging) of the corresponding function according to the operation input by the user, and then provide the user with a unique function after consumption.

[0052] In some cases, the above-mentioned user input operation may be performed on an application program running in the electronic device. Accordingly, the electronic device may provide the user with corresponding functions through the corresponding application program.

[0053] For example, when a user inputs a search operation to a search application, the search application can instruct the electronic device to interact with a server corresponding to the search application (such as a search server). The electronic device can send the keyword information (such as a certain product A) input by the user to the search server. The electronic device can also receive search results from the search server and display them to the user (such as the search results corresponding to product A). This implements the search function provided to the user.

[0054] For another example, when a user inputs a consumption operation to a game application, the game application can instruct the electronic device to interact with the server corresponding to the game application (such as a game server). The electronic device can send consumption information corresponding to the consumption operation input by the user to the game server. After the game server determines that the user's consumption is successful, the electronic device can provide the user with the corresponding unique functions after consumption based on the information sent by the game server when running the game application in the future. For example, the electronic device can, under the operation of the user, exchange specific items or features in the game based on the above-mentioned successful consumption operation.

[0055] In some cases, the electronic device may also correspond to a device server. The device server may provide additional information related to the user input operation based on the user's operation through interaction with the electronic device. For example, the information related to the user input operation may include reward information such as coupons and activity rewards, thereby improving user stickiness.

[0056] For example, take a user inputting a search operation corresponding to a product A as an example. The device server can provide the user with additional rewards such as purchase coupons corresponding to product A. Thus, when the user wants to purchase product A, he or she can use the purchase coupons to obtain a better purchase experience.

[0057] For another example, taking the case where a user inputs a consumption operation in a game application, the device server can provide the user with an additional consumption reward, thereby enabling the user to obtain more and richer consumption results after performing a consumption operation using the current electronic device.

[0058] It is understandable that the above-mentioned device server provides additional coupons, consumption rewards and other information, which can all correspond to the electronic device used by the user. That is, the device server can send the reward information corresponding to the user's input operation to the electronic device used by the user, thereby realizing the distribution of reward information to the user. In turn, the user can obtain more information than conventional operations when using the electronic device, thereby improving the user experience.

[0059] In some implementations, the device server may configure one or more task instances so that the device server can determine to issue reward information to a user device (ie, an electronic device used by a user) based on an operation input by a user.

[0060] For example, the device server may configure task instance A, and when the user inputs a search operation that meets the corresponding requirements, the reward information corresponding to the search operation is sent to the user device. For another example, the device server may configure task instance B, and when the user inputs a consumption operation that meets the corresponding requirements, the reward information corresponding to the consumption operation is sent to the user device.

[0061] In this way, the more task instances are configured in the device server, the more types of reward information in more scenarios can be provided to users. However, the configuration of task instances of different types and scenarios is quite different. Deploying and running a large number of task instances will cause excessive operating overhead of the device server, which is not conducive to implementation.

[0062] Based on this, the technical solution provided by the embodiment of the present application enables the device server to realize the configuration of multiple different types of tasks. Different types of tasks correspond to different types of operations. This improves the convenience of configuring different tasks. In addition, the device server can also accurately and quickly determine the corresponding reward information based on the operation input by the user. Based on the convenient configuration of different task instances, and / or the realization of quickly and accurately determining the reward information, the operating overhead of the device server can be effectively controlled.

[0063] The solution provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0064] As an example, Figure 1 An example of a system composition provided in an embodiment of the present application is provided. The solutions provided in the embodiments of the present application can be applied to the system. Figure 1 in the system shown.

[0065] like Figure 1 As shown, the system may include electronic equipment, a device server, a business server, and an application server, which are described below.

[0066] The electronic device may be an electronic device used by a user. In different implementations, the electronic device may include 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 at least one of a smart city device. The embodiment of the present application does not impose any special restrictions on the specific type of the electronic device.

[0067] In the present application, the electronic device may run one or more applications. For example, the one or more applications may include system applications, such as application market applications, shopping mall applications, search applications, etc. that come with the electronic device. For another example, the one or more applications may include third-party applications, such as game applications, shopping applications, search applications, etc. developed by third-party developers.

[0068] The electronic device can receive user input operations through running third-party applications or system applications.

[0069] In the present application, the operations input by the user may include different types.

[0070] For example, the type of user operation may include at least one of the following: consumption, browsing, searching, booking, card binding, logging in, etc.

[0071] In response to the user's operation, corresponding operation information (or operation event) may be generated in the electronic device.

[0072] In the present application, the operation information may also include different types corresponding to the type of user operation.

[0073] For example, the type of operation information may also include at least one of the following: consumption, browsing, searching, booking, card binding, logging in, etc.

[0074] For any type of operation information, it may include at least one of the following: country information, operation time information, device identification of the receiving operation, command code, type identification, operation content, package name of the app receiving the operation, etc.

[0075] For different types of operation information, the operation contents may be different. For example, the operation contents of consumption operation information may include consumption amount, currency identifier, device identifier, etc. The operation contents of search operation information may include keyword information of search operation, etc.

[0076] In different implementations, the operation information may be generated by an operating system of the electronic device, or the operation information may be generated by an application.

[0077] In some embodiments, taking the user inputting an operation to a third-party application as an example, the third-party application can generate corresponding operation information according to the operation input by the user. The electronic device can send the operation information to the application server of the application program that receives the user operation in order to obtain a corresponding response.

[0078] In other embodiments, the operating information may be generated by an operating system of the electronic device.

[0079] Exemplarily, the electronic device may be configured with a unit module for monitoring the user's input operations in various applications. In this way, after the user inputs the operation, the electronic device may generate corresponding operation information according to the user's input operation. In some cases, the process of the electronic device generating operation information according to the user's input operation may be performed with the user's authorization.

[0080] In this example, the electronic device can generate corresponding operation information according to the preconfigured operation type.

[0081] The preconfigured operation type may be the same as the operation type corresponding to the task instance in the device server. The electronic device may obtain the preconfigured operation type through synchronization with the device server. Correspondingly, the unit module for monitoring the user input operation in the electronic device may also be set corresponding to the preconfigured operation type.

[0082] The electronic device may send the generated operation information to a correspondingly configured service server, or to a device server, so that other devices can perform corresponding processing. In some cases, the electronic device may send the operation information to other devices under the authorization of the user.

[0083] In the following examples, an application in an electronic device generates operation information according to an operation input by a user.

[0084] The application server may correspond to an application installed and running in the electronic device. When multiple applications are installed in the electronic device, there may be multiple application servers. Each application corresponds to an application server, or multiple applications may correspond to the same application server, or one application may correspond to multiple application servers.

[0085] For example, multiple system applications installed in an electronic device may correspond to the same server. For another example, third-party applications from different manufacturers installed in an electronic device may correspond to different application servers.

[0086] It is understandable that after the user inputs an operation to application A in the electronic device, application A can exchange data with the corresponding application server (such as application server A) through the electronic device.

[0087] For example, taking the operation input by the user as a consumption operation, application A can send the consumption operation information input by the user to the corresponding application server A through the electronic device, so that application server A can configure the corresponding function to the user's consumption account according to the consumption information.

[0088] For another example, taking the operation input by the user as a search operation, application A can send the search operation information input by the user to the corresponding application server A through the electronic device, so that application server A can feed back the search results to the electronic device for display to the user according to the search operation information.

[0089] The system composition provided in this example may also include a business server.

[0090] In some embodiments, the service server can be used to obtain various operation information input by the user through the electronic device. For example, the service server can obtain the operation information from the application server. For another example, the service server can directly obtain the operation information from the electronic device.

[0091] In other embodiments, the service server may also be used to transmit the operation information to other devices for subsequent processing.

[0092] For example, the business server may transmit the operation information to the device server so that the device server can determine whether to configure corresponding reward information for the current user account based on the operation information.

[0093] As a possible implementation, the business server may obtain each piece of operation information and transmit and store the information to a message queue corresponding to the type configured in the device server, thereby realizing information transmission to the device server.

[0094] Optionally, the business server is the same as or related to the manufacturer of the electronic device used by the user. In this way, when the user uses the electronic device, the electronic device can authorize the information transmission between the electronic device and the business server to obtain a richer and more user-friendly experience.

[0095] The system composition provided in this example may also include a device server.

[0096] In some embodiments, the device server may also be referred to as a marketing server.

[0097] In this application, the device server can implement functions such as acquisition, matching, standardization, and reward information confirmation for different types of operation information. In some embodiments, the device server can also provide a task configuration function. Based on the task configuration function, the device server can obtain task configuration information under the control of developers (such as operators) and generate new task instances accordingly. Based on the operation of different task instances, response processing to different operation information can be achieved.

[0098] Taking the example of the device server obtaining the user's operation information, in some implementations, the device server can obtain the operation information through the business server. In other embodiments, the device server can also obtain the operation information directly from the electronic device under the user's authorization. It can be understood that in the case where the device server directly obtains the operation information from the electronic device, Figure 1 The device units included in the system shown can also be streamlined accordingly, for example, the service server, application server, etc. are streamlined. In the following example, the device server obtains the operation information through the service server as an example.

[0099] Similar to the above description of the service server, in some implementations, the device server involved in the embodiments of the present application is the same as or related to the manufacturer of the electronic device and / or service server used by the user. In this way, when the user uses the electronic device, the electronic device can authorize the information transmission between the electronic device, the service server, and the device server through the electronic device, thereby obtaining a richer and more user-friendly experience.

[0100] In the embodiment of the present application, one or more functional modules may be configured in the device server to implement corresponding functions.

[0101] Exemplary, reference Figure 2 , which is a schematic diagram of the composition of a device server provided in an embodiment of the present application.

[0102] like Figure 2As shown, the device server may include a task configuration module, a data matching module, a data standardization module, a task engine module, and a storage module. The storage module may be configured with a task storage unit and an operation message queue.

[0103] It should be noted that if Figure 2 The components of the device server shown are only examples and do not constitute a limitation on the device server. In other embodiments of the present application, the device server may also have more or fewer components.

[0104] Based on Figure 2 The task configuration module can be used to implement the task configuration function. In some embodiments, the task configuration module can provide a visual interface (such as an Http interface) to developers (such as operators) so that developers can access task configuration related information through the visual interface.

[0105] As a possible implementation, the visual interface can be implemented based on an application (such as a task configuration application) deployed in the task configuration module. In this way, after the developer inputs the task configuration information through the task configuration application, the task configuration module can receive the task configuration information through the interface corresponding to the task configuration application on the device server. Then, the task configuration module can realize the generation and operation of the corresponding task instance according to the task configuration information.

[0106] like Figure 3 As shown, in the present application, in the task configuration function provided by the task configuration module, the task configuration information that can be configured may include: basic information, task conditions, and reward information, etc.

[0107] The basic information may include at least one of the following: task type, business field, task code, task name, country information, time zone information, executable task time, etc. In some implementations, the task code may be used to identify the task instance corresponding to the basic task information. The task code may be manually configured by the developer or automatically generated by the task configuration module. Generally, different task instances correspond to different task codes. In some implementations, the basic information may also be referred to as task basic information.

[0108] The task type in the basic information may correspond to the type of operation information in the above description. For example, the task type in the basic information may include: consumption, browsing, searching, booking, card binding, logging in, etc.

[0109] It is understandable that task configuration information can correspond to a task instance. Then, task configuration information corresponding to different task types can also correspond to different types of task instances, thereby achieving multi-type and multi-scenario support from task instance configuration.

[0110] The task condition can be used to determine whether the current operation information corresponds to the configured reward information.

[0111] In some implementations, the task condition may include: task setting information and task achievement condition information. The task setting information may also be referred to as task rule information or task rule setting.

[0112] The task setting information may include at least one of the following: country information, APP package name, currency information, etc. The APP package name may be the package name of the APP involved in the current task instance.

[0113] The task achievement condition information may include at least one of the following: cumulative or single calculation, consumption amount, number of consumptions, search frequency, etc.

[0114] It is understandable that, during the configuration process of a task instance, the corresponding task conditions may be different depending on the basic information.

[0115] The reward information may include at least one of the following: reward type, reward coding information, reward information issuance method, reward amount, reward available time, etc. In some embodiments, the reward information may also be referred to as task reward settings. In some implementations, the device server may generate a corresponding reward picture according to the configuration of the reward.

[0116] Therefore, based on Figure 3 The multi-dimensional task configuration mechanism shown enables the device server to provide task configuration capabilities to developers (such as operators) and realize flexible task instance configuration in multiple scenarios.

[0117] In the present application, information of a configured task instance (ie, task configuration information) may be stored in a task storage unit.

[0118] In some embodiments, the task storage unit may include one or more storage areas. Each storage area may include multiple forms. Different storage areas may be used to store the contents of different task configuration information. Different forms in the same storage area are used to store different configuration contents of a task configuration information.

[0119] For example, the task storage unit may include a storage area A1. The storage area A1 may store basic information, task conditions, and reward information of the task configuration information 1 corresponding to the task instance 1.

[0120] Storage area A1 may be configured with form A11, form A12, form A13, etc. Form A11 in storage area A1 may store basic information of task instance 1, form A12 may store task conditions of task instance 1, and form A13 may store reward information of task instance 1.

[0121] After the task configuration information is stored in the corresponding storage area, the task storage unit may provide the device server with a storage address corresponding to the storage area. For example, the task storage unit may provide the device server with a corresponding relationship between the task code and the storage area address. The task code and the storage area may correspond to the same task instance (or task configuration information).

[0122] For example, after completing the configuration of task instance 1, the device server can store the task configuration information of task instance 1 in storage area A1. Correspondingly, the device server can store the corresponding relationship between task code 1 and the address of storage area A1. Among them, task code 1 can be the task code of task instance 1. As a result, when it is necessary to obtain the task configuration information of task instance 1 (such as basic information, task conditions and reward information), the storage address of the task configuration of task instance 1 can be obtained according to task code 1.

[0123] like Figure 2 As shown, an operation message queue may also be configured in the storage module of the device server.

[0124] In combination with the above description, the device server can obtain the user's operation information from the service server. In this application, the user's operation information can be stored in the operation message queue.

[0125] As an example, refer to Figure 4 In some embodiments, the operation message queue may include multiple message queues of different types. Different message queues store different types of user operations. For example, the operation message queue may include message queues corresponding to consumption, browsing, searching, booking, card binding, login, etc.

[0126] For example, the operation message queue includes a consumption queue, a search queue, etc. Correspondingly, after obtaining the user's consumption operation information, the business server transmits and stores it in the consumption queue of the device server. After obtaining the user's search operation information, the business server transmits and stores it in the search queue of the device server.

[0127] The data matching module configured in the device server may have a monitoring function for operation information.

[0128] Exemplarily, the data matching module may determine, based on the monitoring function, that new operation information has entered the operation message queue.

[0129] In this example, the data matching module may also have a matching function, such as field matching, keyword matching, etc.

[0130] Exemplarily, after new operation information enters the operation message queue, the data matching module may trigger the following judgment logic: the data matching module reads basic information of all enabled task instances from the task storage unit.

[0131] The data matching module can match the operation information with the read multiple basic information. In the case where the basic information and the operation information are completely matched, the task instance corresponding to the matched basic information is the target task instance.

[0132] It is understandable that in some cases, all basic information fails to match, and the target task instance may be 0. In other cases, there is a task instance whose basic information matches successfully, and the target task instance may be 1. In other cases, there are multiple task instances whose basic information matches successfully, and the target task instance may be multiple.

[0133] Taking the case where the data matching module determines that there is a target task instance as an example, the data matching module can provide the user's operation information to the data standardization module for subsequent processing when confirming that there is a target task instance.

[0134] For example, the data standardization module can be used to standardize the operation information so as to convert the operation information in different formats into a unified format, thereby improving the success rate of judging whether the subsequent task instance indicates that the condition has been met.

[0135] It is understandable that the data formats of the operation information from different devices and different applications are different. Therefore, through the processing of the data standardization module, the device server can process the operation information more efficiently.

[0136] For example, Figure 5 A processing schematic diagram of a data standardization module is shown. Through the processing of the data standardization module, the conversion of key values ​​and the formatting of values ​​can be achieved.

[0137] In such Figure 5In the example, the operation information can specifically be consumption operation information. The consumption operation information can include country (nation) information as "CN", consumption time as "2023-07-22 08:52:32", device identification (user ID) as "616xxxxxx", command code (orderNO) as "dea3fxxxxxx", type (type) as 2, and consumption amount (payMoney) as 13. Among them, the data format of country information, consumption time, device identification, and command code can all correspond to a string (string). Identified by double quotes "". The data format of information such as type and consumption amount can be an integer (int).

[0138] Correspondingly, after the standardization processing of the data standardization module, the content of the output operation standard operation information can correspond to the operation information, and the data format thereof is different. Figure 5 In the example, standard operation information may include: country (nation) information as string data: "CN", consumption time as converted integer (int) data: 1689987152000, device identification (user ID) as integer (int) data: 616xxxxxx, command code (orderNO) as string data: "dea3fxxxxxx", type (type) name converted to "cancelFlag", its value is integer (int) data: 1, consumption amount (payMoney) as string data: "13".

[0139] In this way, the consumption operation information from different electronic devices and different applications can be processed by the data standardization module to obtain Figure 5 The data format of the standard operating information is shown.

[0140] Similarly, when the operation information is of other types, the data standardization module can also perform corresponding standardization processing to obtain corresponding standard operation data.

[0141] In this example, the task engine module can be used to determine whether the current operation needs to be configured with reward information, as well as the specific content of the reward information, based on the target task instance determined by the data matching module and the standard operation data obtained after processing by the data standard module.

[0142] Exemplarily, the task engine module can be used to judge the standard operation data according to the task conditions in the target task instance, and then determine whether to configure reward information for the corresponding account after the user inputs the current operation information. Among them, the account can be identified by the device identifier (user ID).

[0143] In some implementations, the task engine module can perform the judgment process of the current operation information in a certain order. For example, the task engine module can compare and judge the country information, APP package name, currency information in the standard operation information with the task setting information of the target task instance. When the country information, APP package name, and currency information are consistent, the task engine module can compare and judge the task achievement condition information of the target task instance based on the consumption amount, search frequency, and other information in the standard operation information. When all judgments and comparisons are passed, the corresponding reward information is determined.

[0144] It is understandable that for some task instances, the judgment result may include a fixed reward information, or no reward information. In this way, the task engine module can determine that the user's current operation can be configured with the fixed reward information when the standard operation information is consistent with the task setting information and task achievement condition information of the target task instance. Otherwise, it is determined that the user's current operation does not need to be configured with reward information.

[0145] For some other task instances, their task configuration information may include multiple reward information. Different reward information may correspond to different judgment results. In the task configuration information corresponding to this example, multiple conditional branches may be included. Each conditional branch may correspond to different reward information. Thus, when the task engine module can determine that the user's current operation can configure the reward information corresponding to the conditional branch when the standard operation information is consistent with the task setting information and task achievement condition information of a conditional branch of the target task instance. Otherwise, it is determined that the user's current operation does not need to configure reward information.

[0146] The solutions provided in the embodiments of this application can be applied to Figures 1 to 5 For example, the solution provided in the embodiment of the present application can be configured in Figure 2 The device server shown is used to implement various technical implementations.

[0147] The following combination Figure 2 The composition of the device server shown is used to illustrate the technical solution provided in the embodiment of the present application.

[0148] Exemplary, reference Figure 6 , is a schematic diagram of an interaction between modules provided in an embodiment of the present application. Figure 6 The solution implementation shown can be applied in a device server.

[0149] like Figure 6 As shown, the task configuration module can cooperate with the task storage unit to implement the configuration of the task instance.

[0150] Exemplarily, the task configuration module may receive task configuration information 1. Correspondingly, the task configuration module may store the task configuration information 1 in the task storage unit of the storage module. The task configuration information 1 may include basic information 1, task conditions 1, and reward information 1.

[0151] Similarly, the task configuration module can also receive task configuration information 2. Correspondingly, the task configuration module can store the task configuration information 2 in the task storage unit of the storage module. The task configuration information 2 can include basic information 2, task conditions 2, and reward information 2.

[0152] In some embodiments of the present application, the device server may be connected to a configuration device. For example, the configuration device may be a personal computer (PC).

[0153] Under the operation of the operator, the PC can input the task configuration information 1 and the task configuration information 2. Correspondingly, the PC can send the task configuration information 1 and the task configuration information 2 to the task configuration module respectively.

[0154] In some embodiments, the task configuration module may set a corresponding status flag for each configuration information in the task storage unit. The status flag may be used to indicate whether the corresponding task instance is in use.

[0155] For example, after receiving the task configuration information 1, the task configuration module may store the task configuration information 1 in the storage area A1 of the task storage unit. In this way, the task configuration information 1 also corresponds to the task instance 1.

[0156] When the task configuration information 1 is stored in the storage area A1, the corresponding state flag 1 may be configured as a first value, correspondingly indicating that the task instance 1 is not enabled.

[0157] When the device server determines to enable task instance 1, the state identifier 1 may be configured as a second value, corresponding to indicating that task instance 1 is being enabled.

[0158] In some implementations, the device server may determine to enable task instance 1 according to a preset time policy. In other implementations, the device server may configure state identifier 1 to the second value under the control of a developer (eg, a marketing person).

[0159] Thus, the task storage unit can store the task configuration information of the configured task instance and the corresponding state identifier.

[0160] In combination with the above description, the operation message queue in the storage module can be configured with message queues corresponding to different operation types. The message queue is used to store operation information of corresponding types.

[0161] For example, the device server may store the operation information 1 from the service server in the corresponding message queue.

[0162] In this example, the data matching module of the device server can monitor the message queue for new operation information (such as operation information 1), thereby triggering the execution of subsequent steps.

[0163] Exemplarily, the data matching module may obtain the operation information 1 from the operation message queue 1 after the operation information 1 enters the operation message queue.

[0164] The data matching module may also obtain basic information corresponding to all currently stored enabled task instances from the task storage unit after the operation information 1 enters the operation message queue.

[0165] Take the example where the status identifiers of task instance 1 and task instance 2 are both the second value.

[0166] The data matching module can obtain basic information 1 of task instance 1 from the task storage unit after confirming that the status identifier of task instance 1 is the second value. Similarly, the data matching module can obtain basic information 2 of task instance 2 from the task storage unit after confirming that the status identifier of task instance 2 is the second value.

[0167] In the present application, the data matching module can perform matching processing with each acquired basic information based on the current operation information, so as to confirm whether the currently enabled task instance includes the task instance corresponding to the current operation.

[0168] If the operation information and the basic information are completely identical, the matching process is successful. Correspondingly, the task instance to which the basic information belongs is also the task instance corresponding to the operation information.

[0169] Exemplarily, the data matching module can perform matching processing with basic information 1 and basic information 2 respectively according to operation information 1. For example, operation information 1 includes operation type, country information, and time zone information.

[0170] Thus, when the operation type, country information, and time zone information of basic information 1 are the same as those of operation information 1, basic information 1 successfully matches operation information 1. Then, correspondingly, task instance 1 corresponding to basic information 1 is also the task instance corresponding to operation information 1.

[0171] Similarly, the data matching module can perform matching processing based on the operation information 1 and the basic information 2, thereby confirming whether the task instance 2 is the task instance corresponding to the operation information 1.

[0172] It can be understood that in different implementations, the number of task instances matching one piece of operation information 1 may be one or more.

[0173] In this example, the task instance matching the operation information 1 is taken as task instance 1.

[0174] The data matching module can perform subsequent operations when confirming that there is a task instance that matches the current operation.

[0175] For example, the data matching module can send the operation information 1 to the data standardization module for standardization processing. Figure 5 Correspondingly, the method performs standardization processing on the operation information 1, thereby obtaining the corresponding standard operation information 1.

[0176] Next, the data standardization module may send the acquired standard operation information (such as standard operation information 1) to the task engine module.

[0177] like Figure 6 As shown, the data matching module may also send the task code of the task instance matching the current operation to the task engine module.

[0178] For example, the data matching module may also send the task code 1 corresponding to the task instance 1 to the task engine module.

[0179] In this way, the task engine module can obtain the task code of the task instance matching the current operation and the operation information of the current operation after standardized processing.

[0180] Next, the task engine module may obtain the task condition 1 and reward information 1 corresponding to the task instance 1 from the task storage unit according to the task code 1 .

[0181] The task engine module can use the standard operation information 1 to perform judgment processing according to each judgment item in the task condition 1, and then confirm whether to configure the reward information 1 for the electronic device currently used by the user.

[0182] In the above example, one target task instance is used as an example. In other embodiments, when there are multiple target task instances, the task engine module can respectively implement the above scheme for each target task instance to determine whether the current operation meets the task condition of the corresponding target task instance, thereby determining whether to configure the reward information corresponding to the current target task instance for the electronic device receiving the operation.

[0183] Thus, by Figure 6 The scheme shown in the figure can accurately determine the corresponding reward information according to the operation input by the user. Figure 6 The description of the scheme shown in the figure shows that, since the task configuration module in the device server has the task configuration function, comprehensive configuration of multi-task scenarios can be achieved. Based on the cooperation of the data matching module, the data standardization module, and the task engine module, different types of user operations can be judged. In this way, the reward information in multiple scenarios and complex user operations can be quickly and accurately confirmed.

[0184] In order to more clearly illustrate the solution provided by the embodiment of the present application, refer to Figure 7 , which is a flow chart of the interaction between modules provided in an embodiment of the present application.

[0185] In this Figure 7 In the implementation of the scheme shown, Figure 6 Based on the interaction between the various modules of the device server shown in Figure 1 The interaction between the various devices in the system is shown.

[0186] like Figure 7 As shown, the program may include:

[0187] S701. An electronic device receives a consumption operation from a user.

[0188] In this example, the operation input by the user is a consumption operation. For example, the consumption operation may be a recharge operation input to application A.

[0189] Correspondingly, application A (or electronic device) can generate corresponding consumption operation information according to the consumption operation input by the user.

[0190] As an example, the consumption operation information may include: consumption type identification, device identification of the electronic device (such as user ID), aap package name of application A, consumption time, country information, currency information, consumption amount, etc. Optionally, the consumption operation information may also include command codes. The command codes of different consumption operation information are different.

[0191] S702: The electronic device sends consumption operation information to the application server.

[0192] Exemplarily, application A may send consumption operation information to application server A corresponding to application A through an electronic device.

[0193] S703: The business server obtains consumption operation information from the application server.

[0194] The application server can send a corresponding response to the electronic device based on the consumption operation information.

[0195] In this example, the business server can obtain the operation information input by the user in application A from application server A.

[0196] For example, the business server may obtain consumption operation information from application server A.

[0197] S704: The device server obtains consumption operation information from the service server.

[0198] S705. The consumption operation information is stored in the consumption queue of the device server.

[0199] In some embodiments, after the business server actively obtains the operation information, it can store the operation information in a corresponding message queue in the device server according to different types.

[0200] For example, the service server may store the consumption operation information in a consumption queue of the service server.

[0201] In other embodiments, the device server may also send a request message to the service server so that the service server sends the consumption operation information to the device server according to the request message. Correspondingly, the device server may store the received operation information in the consumption queue according to the received operation information including the consumption type identifier.

[0202] It should be noted that, in some embodiments, the device server may implement queue monitoring of operation information in the message queue by configuring a monitor.

[0203] As an example, the monitor may be configured with the address information of each message queue. Optionally, the monitor may also be configured with the topic information corresponding to the address information. In this way, the monitor can determine that a new type of operation information has been queued by monitoring the above-mentioned address information. Furthermore, the monitor can determine the type of the newly arrived operation information based on the topic information corresponding to the address where the operation information enters.

[0204] In some embodiments, the monitor in the device server can be dynamically configured. In this way, when a message queue or topic information is newly configured in the device server, the device server can update the monitoring of subsequent operation information by dynamically configuring a new monitor.

[0205] S706: The device server obtains basic information of all enabled task instances.

[0206] In this example, the device server may trigger the execution of S706 according to the entry of a new operation type.

[0207] Exemplarily, the device server may store basic information corresponding to all enabled task instances from the task storage unit.

[0208] Combination Figure 6 As described in, in some embodiments, the status identifier of an enabled task instance is configured as a second value as an example.

[0209] The device server can read the basic information of all task instances whose status identifiers are configured as the second value in the task storage unit. In some embodiments, the basic information of each task instance is stored in the first form in the corresponding storage area as an example. In this way, the device server can read the information in the first form of each task instance whose status identifier is the second value, thereby obtaining the basic information of each enabled task instance.

[0210] S707: The device server determines a target task instance corresponding to the consumption operation information.

[0211] Exemplarily, the device server may obtain the newly queued operation information from the operation message queue. The device server may also perform matching processing on the operation information with the basic information of all enabled task instances obtained in S706.

[0212] For example, the device server may compare the operation information with each of the basic information of all enabled task instances one by one. For example, the device server may compare the country information, time information, APP package name, and other information one by one in the order of priority.

[0213] If every data item is the same, the match is successful. If at least one data item is different, the match fails.

[0214] In this example, the task instance corresponding to the successfully matched basic information may be referred to as a target task instance.

[0215] In some embodiments, the device server may store the task code of the target task instance in a preset location, thereby implementing the identification call related to the target task instance in subsequent steps.

[0216] S708. The device server performs standardization processing on the consumption operation information to obtain standard consumption operation information.

[0217] In some embodiments of the present application, the device server may trigger the execution of S708 when executing S707 and determining that the newly queued operation information has a corresponding target task instance.

[0218] In some other embodiments, S708 may be executed before S707 or synchronously with S707.

[0219] In this way, the device server can implement standardized processing of the operation information and obtain the corresponding standard operation information.

[0220] For example, the device server performs standardized processing on the consumption operation information newly entering the consumption queue and obtains the corresponding standard consumption operation information. For specific implementation, please refer to Figure 5 The description is not repeated here.

[0221] S709: The device server obtains the task conditions and reward information of the target task instance.

[0222] Exemplarily, the device server may determine the storage location of the target task instance according to the task code of the target task instance determined in S707.

[0223] Correspondingly, the device server can obtain the task conditions of the target task instance from the preconfigured table item location (such as the second table item) in the storage location of the target task instance. For example, the device server can obtain the task setting information and the task achievement conditions from the storage location of the target task instance. The device server can also obtain the reward information of the target task instance from the preconfigured table item location (such as the third table item) in the storage location of the target task instance.

[0224] It should be noted that, in some embodiments, the device server may only read the task conditions of the target task instance in S709. The reward information may be obtained in subsequent operations when it is determined that the task conditions are met.

[0225] S710. The device server determines reward information corresponding to the consumption operation information.

[0226] For example, the device server can compare the data in the operation information with the task setting information and the task achievement conditions in sequence. If the task setting information and the task achievement conditions are met, it means that the conditions of the current target task instance are met, and the corresponding reward information can be configured according to the newly entered operation information.

[0227] As an example, it is taken that the newly entered operation information includes consumption operation information.

[0228] The device server may first determine that the type in the consumption operation information is the same as the task type in the task setting information.

[0229] For example, the task setting information includes the country information "China" and the APP package name "Application A". The relationship between the two is "and".

[0230] In this way, the device server can determine that the country information of the consumption operation information is "China". The device server can also determine that the APP package name of the application that received the consumption operation information is "Application A". The device server can thus determine that the consumption operation information meets the conditions indicated by the task setting information.

[0231] For example, the task setting information includes the currency "CNY" and the APP package name "com.xxx.theme". The relationship between the two is "and".

[0232] In this way, the device server can determine that the currency of the consumption operation information is "CNY". The device server can also determine the APP package name "com.xxx.theme" of the application that received the consumption operation information. The device server can thus determine that the consumption operation information meets the conditions indicated by the task setting information.

[0233] In the above example, the multiple conditions in the task setting information are in an "and" relationship. In this way, the device server can determine that when each condition is satisfied, the corresponding consumption operation information satisfies the condition indicated by the task setting information.

[0234] In other embodiments, multiple conditions in the task setting information may also be configured as an "or" relationship. In this way, when the device server determines that any one of the conditions is satisfied, the corresponding consumption operation information satisfies the condition indicated in the task setting information.

[0235] In this example, after the device server determines that the consumption operation information satisfies the condition indicated by the character setting information, it determines whether the consumption operation information satisfies the indication of the task achievement condition.

[0236] Exemplarily, the task achievement condition is indicated by the calculation form of "single time", and when the "consumption amount" is greater than or equal to 100, the condition of the task achievement condition is met.

[0237] In this way, the device server can compare the consumption amount carried in the consumption operation information with 100. Correspondingly, when the consumption amount carried in the consumption operation information is greater than or equal to 100, it means that the consumption operation information meets the condition indicated by the task achievement condition.

[0238] In other embodiments, the calculation form of the task achievement condition indication may also be "accumulation".

[0239] In this case, if Figure 8 As shown, the device server may update the task status when it is determined that the consumption operation information satisfies the condition indicated by the task setting information.

[0240] Exemplarily, updating the task status may include: reading the consumed amount corresponding to the current device identification (such as user ID) from a preset location, and accumulating the consumed amount and the consumed amount carried in the currently received consumption operation information to obtain an updated consumption amount.

[0241] Thus, the device server can determine whether the task achievement condition is met based on the updated consumption amount.

[0242] In this example, it is taken that the device server determines that the currently received consumption operation information satisfies the task setting information and the task achievement condition in the target task instance.

[0243] In this way, the device server can configure the reward information corresponding to the target task instance to the electronic device that obtains the consumption operation information through subsequent steps.

[0244] S711. The device server sends the device identification and reward information to the business server.

[0245] S712: The business server configures reward information to the electronic device.

[0246] In this example, it is taken that the device server configures reward information to the electronic device through the business server.

[0247] Exemplarily, the device server can send the user ID of the electronic device that receives the consumption operation information and the reward information corresponding to the target instance to the business information. In some implementations, the reward information may include: reward amount, picture information corresponding to the reward, redemption time, etc. Correspondingly, the business server can send the reward information to the device corresponding to the user ID. This realizes the configuration of reward information to the user.

[0248] It is understandable that through the above Figure 7 The implementation of the solution shown in the figure can enable the device server to compare the started task instances according to the newly received user operations, and then determine whether to configure reward information for the user. The above example uses consumption operation information as an example. In other embodiments, the operation information may also include other types, such as search operation information. The specific implementation can refer to Figure 7 . I will not repeat them here.

[0249] In combination with the above description, the device server can also provide a configuration function of the task instance through the task configuration module configuration.

[0250] The following is an example of how to implement the task configuration function.

[0251] refer to Fig. 9In some embodiments, the device server may be coupled to the configuration device. The coupling connection may include a wired connection and / or a wireless connection. The configuration device may be a PC, a display screen, or other devices with display functions and operation receiving functions.

[0252] As a possible implementation, the device server may control the configuration device to display configuration options according to a preset logic, so that developers (such as operators) can configure new task instances based on the configuration options.

[0253] refer to Fig.10 , which is an example of a configuration interface for a device server to control the configuration of basic task information (ie, basic information) provided by the device.

[0254] like Fig.10 As shown, in the task basic information configuration interface, the business field configuration item 1001, the task code configuration item 1002, the task name configuration item 1003, the participating country restriction configuration item 1004, the task time zone configuration item 1005, and the executable task time configuration item 1006 can be included. Fig.10 The interface configuration mechanism shown can realize the configuration of basic information of the newly added task instance.

[0255] In completing Fig.10 After configuring the basic information of the task shown in the figure, you can click Fig.10 The button 1007 shown enters the next configuration item.

[0256] refer to Fig.11 , shows an example of a configuration interface for task rule settings. Fig.11 The corresponding interfaces of 1110 and / or 1120 shown may be as follows Fig.10 The interface shown is displayed after configuration is completed.

[0257] like Fig.11 As shown in 1110, the task rule setting in this example may include a task type configuration item 1111, and a conditional relationship configuration item 1112, etc. In this example, the task type can be configured as a consumption type. The conditional relationship can be configured as condition 1 is "country" = "China", and "APP package name" = "Application A". In some embodiments, the interface as shown in 1110 may also include a button 1113. The button 1113 may correspond to adding a judgment formula. The button 1113 may provide an entry for adding an additional judgment mechanism.

[0258] exist Fig.11An example of a task rule setting interface corresponding to 1120 is also provided. The interface 1120 provides another configuration example of a conditional relationship configuration item 1112. In the example 1120, the conditional relationship can be configured as condition 1 is "currency" = "CNY", and "APP package name" = "com.xxx.theme".

[0259] It is understandable that in other embodiments, such as Fig.11 In the task rule setting configuration interface shown, other conditional relationships and / or task types may also be configured to implement configuration of different task instances.

[0260] refer to Fig.12 , provides an example of the configuration interface for task achievement conditions.

[0261] In the example of interface 1210, the task achievement condition can be configured as "accumulated" "consumption amount" "greater than or equal to" "100" to complete the task. That is, through the cumulative calculation form, when the accumulated consumption amount is greater than or equal to 100, it indicates that the task achievement condition is met.

[0262] In other embodiments, the task achievement conditions can also be selected by other configurations. For example, as shown in interface 1220, the task achievement conditions can also be configured with a ladder type configuration of "cumulative ladder". Based on this configuration, the task achievement conditions can be configured with branches corresponding to multiple ladders. The ranges of each ladder do not overlap. If the conditions of any ladder are met, the reward information corresponding to the ladder can be configured accordingly.

[0263] For example, in Fig.12 In the example, take the number of steps as 2. Among them, step 1 can be configured as: when the cumulative consumption amount is greater than or equal to 8 and less than 20, the corresponding reward information (such as reward information 1) can be configured. In addition, step 2 can be configured as: when the cumulative consumption amount is greater than or equal to 20 and less than 50, the corresponding reward information (such as reward information 2) can be configured. Generally, reward information 2 is different from reward information 1. As a result, when the user enters consumption information of different amounts, different reward information configurations are provided by running a task instance.

[0264] After completing the configuration of the aforementioned configuration information, the device server can also provide task rewards by configuring the device.

[0265] For example, Fig.13 The figure shows a schematic diagram of an interface for setting task rewards.

[0266] In this example, the task reward setting may include the distribution form, such as automatic distribution of rewards, automatic distribution of push notifications, automatic distribution of rewards and push, and doing nothing. Among them, the distribution of rewards is to directly configure the reward information. Push notification corresponds to the push of notification messages to the electronic devices used by the user.

[0267] like Fig.13 As shown, the task reward setting may also include the configuration of the gift package single code, the configuration of the gift package group code, and the configuration of the gift package code, etc. Thus, a multi-level reward information configuration is achieved.

[0268] Above Figure 10 to Figure 13 The following takes the task instance of configuring consumption type as an example. Fig.14 , and also provides a configuration implementation for a search type task instance.

[0269] like Fig.14 As shown in 1410 , the task type configuration item 1411 may be configured as “search”.

[0270] In combination with the above examples, the device server can provide the configuration capability of task instances of various types in various scenarios.

[0271] In this Fig.14 In the provided implementation, the task rule settings may include conditional relationship configuration items corresponding to the "search" type.

[0272] As shown in the configuration example of 1412 in 1410, the conditional relationship may include condition 1: "Keyword list" includes "product 1, product 2, product 3". Thus, through this task instance, reward information is determined and issued when the user searches for product 1, product 2 or product 3.

[0273] like Fig.14 As shown in 1420, in the search scenario, the task completion condition may include the configuration item corresponding to 1413: the related configuration of the task completion number type.

[0274] Based on the configuration of the task completion times type, the task instance can be configured as repeated or single. Based on the configuration of the task completion times type, the maximum number of triggers of the task instance within a certain period of time can also be configured, thereby avoiding configuring the same reward for the same user device multiple times.

[0275] Exemplarily, as shown in 1413, in this example, the task completion times type can be configured as: repeated completion, which can be completed once a day at most within the task cycle, and a maximum of 10 times within the task cycle.

[0276] also, Fig.14Also provided is a task reward setting configuration as shown in 1430. Similar to Fig.13 In the distance of the "consumption" type task instance shown in the figure, in the "search" type task instance, the gift package code can be configured as 50Fxxxxxx.

[0277] Thus, through Figure 10 to Figure 13 ,as well as Fig.14 The configuration implementations corresponding to different types of task instances are provided respectively. It is understandable that the device server can also provide corresponding task rule setting configuration items, task achievement condition configuration items, and / or task reward settings in other scenarios. The details will not be repeated here.

[0278] Therefore, through the above Figure 10 to Figure 14 The provided example enables the device server to configure the new task instance by configuring the device. This process can be applied to the new configuration of task instances corresponding to different types of scenarios, thereby simplifying the process of adding task instances and improving efficiency.

[0279] 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 such implementation should not be considered to exceed the scope of the embodiment of the present application.

[0280] 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.

[0281] For example, Fig.15 FIG. 1 is a schematic diagram showing the composition of a data processing device 1500. In some embodiments, the data processing device may correspond to the device server involved in the above embodiments.

[0282] like Fig.15As shown, the data processing device 1500 may include: a processor 1501 and a memory 1502. The memory 1502 is used to store computer-executable instructions. Exemplarily, in some embodiments, when the processor 1501 executes the instructions stored in the memory 1502, the data processing device 1500 may execute any of the methods shown in the above embodiments executed by the device server.

[0283] 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.

[0284] Fig.16 A schematic diagram of the composition of a chip system 1600 is shown. The chip system 1600 may include: a processor 1601 and a communication interface 1602, which are used to support related devices (such as device servers) 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 the device server. 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 1602 may also be referred to as an interface circuit.

[0285] 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.

[0286] 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)).

[0287] 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, the data processing device is configured with information of at least one task instance, the information of each task instance includes corresponding basic information, task conditions, and reward information; the method comprises: Acquire first operation information, where the first operation information corresponds to an operation input into the first electronic device by a user; Get the basic information of at least one enabled task instance; Determining that first basic information corresponds to the first operation information; the first basic information is basic information of a first task instance, and the first task instance is included in the at least one enabled task instance; Obtaining a first task condition of the first task instance; According to the correspondence between the first operation information and the first task condition, it is determined to configure first reward information for the first electronic device; the first reward information is reward information of the first task instance.

2. The method according to claim 1, characterized in that At least one operation message queue is configured in the data processing device, and different operation message queues are used to store different types of operation information; The obtaining of the first operation information includes: The first operation information is obtained in a first message queue, where the type of the first message queue is the same as the type of the first operation information.

3. The method according to claim 2, characterized in that The type of the first operation information is a first type; Among them, the type of operation information includes at least one of the following: consumption, browsing, searching, booking, card binding, and logging in; the first type is included in the type of operation information.

4. The method according to claim 3, characterized in that The type of the first operation information is a consumption type, and the first operation information includes at least one of the following: a consumption amount, a currency identifier, and a device identifier of the first electronic device.

5. The method according to any one of claims 1 to 4, characterized in that Each of the task examples is configured with a state identifier; the state identifier is configured as a first value or a second value; The task identifier is configured as a first value indicating that the task instance is not enabled; The task identifier being configured as the second value indicates that the task instance is enabled.

6. The method according to claim 5, characterized in that The obtaining basic information of at least one enabled task instance includes: Obtain basic information of a task instance whose status identifier is the second value in at least one configured task instance.

7. The method according to any one of claims 1 to 6, characterized in that The basic information of a task instance includes at least one of the following: task type, business field, task code, task name, country information, time zone information, and executable task time.

8. The method according to any one of claims 1 to 7, characterized in that The determining that the first basic information corresponds to the first operation information includes: It is determined that each item of data included in the first operation information is the same as each item of data included in the first basic information.

9. The method according to any one of claims 1 to 8, characterized in that The obtaining of the first task condition of the first task instance includes: According to the task code of the first task instance, the first task condition is obtained.

10. The method according to claim 9, characterized in that The first task condition includes first task setting information and first task achievement condition information; Wherein, the first task setting information includes at least one of the following: country information, APP package name, currency information; The first task achievement condition information includes at least one of the following: cumulative or single calculation, consumption amount, number of consumptions, and search frequency.

11. The method according to claim 9 or 10, characterized in that: Before determining to configure the first reward information for the first electronic device according to the correspondence between the first operation information and the first task condition, the method further includes: The first operation information is subjected to preconfigured data standardization processing to obtain first standard operation information.

12. The method according to claim 11, characterized in that The determining that the first basic information corresponds to the first operation information includes: It is determined that each item of data included in the first standard operation information is the same as each item of data included in the first basic information.

13. The method according to claim 11 or 12, characterized in that: The step of determining to configure first reward information for the first electronic device according to the correspondence between the first operation information and the first task condition includes: It is determined that various data included in the first standard operation information meet the conditions indicated by the first task setting information.

14. The method according to claim 13, characterized in that The method further comprises: Determine whether various data included in the first standard operation information meet the conditions indicated by the first task achievement condition information.

15. The method according to any one of claims 1 to 14, characterized in that The method further comprises: The first reward information is obtained according to the encoding information of the first task instance.

16. The method according to any one of claims 1 to 15, characterized in that The first reward information includes at least one of the following: reward type, reward coding information, reward information issuance method, reward amount, and reward available time.

17. The method according to any one of claims 1 to 16, characterized in that The method further comprises: The first reward information is sent to the first electronic device.

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

19. A server, characterized in that: The server is configured with a data processing device as described in claim 18. When the server is running, the reward information corresponding to the user input operation is determined according to the method described in any one of claims 1-17.

20. A chip system, characterized in that: The chip system is applied to the data processing device as described in claim 18, or the server as described in claim 19; the chip system includes one or more interface circuits and one or more processors; the interface circuit and the processor are interconnected through lines; the interface circuit is used to receive a signal from a memory and send the signal to the processor, the signal including a computer instruction stored in the memory; when the processor executes the computer instruction, it executes the method described in any one of claims 1-17.

Images