Task processing method, equipment and computer program product

Abstract

The invention provides a task processing method and device and a computer program product, and belongs to the technical field of computers. Comprising the steps of determining task configuration information of a task system; calling a front-end SDK, wherein the front-end SDK packages a script generation interface; converting the task configuration information into script data based on a script generation interface; the script data and the identification information of the task system are stored in an associated mode, the script data and the identification information which are stored in the associated mode are used for obtaining the script data associated with the identification information on the basis of the identification information of the task system, and the service request is processed on the basis of the script data. In the embodiment of the invention, the script generation interface is packaged in the front-end SDK, and the script generation interface has the capability of generating script data; therefore, when the task system needs to be reconstructed, a user only needs to configure the task configuration information, and the script data is directly generated by the script generation interface packaged in the front-end SDK, so that the development cost of the task system is reduced.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a task processing method, device and computer program product. Background Art

[0002] At present, many applications have embedded task systems, which can effectively motivate users to take action and improve user participation and activity. Moreover, task systems are often combined with reward mechanisms, so that users can receive certain rewards after completing tasks, thereby generating a sense of satisfaction and achievement. At the same time, task systems can also guide users to gain a deeper understanding of the products or services in the application, stimulating their desire to purchase and thus increasing product conversion rates.

[0003] The task system has certain conditions for displaying to users; for example, the task system is only displayed to users whose application version number is greater than 5.0; or the task system is only displayed to users of Android phones, etc. When displaying conditions, developers are required to judge the code in the coding of the task system, which leads to high labor costs for R&D and testing. Summary of the invention

[0004] The embodiment of the present application provides a task processing method, device and computer program product, which reduces the development cost of the task system. The technical solution is as follows:

[0005] In one aspect, a task processing method is provided, the method comprising:

[0006] Determine the task configuration information of the task system;

[0007] Calling the front-end SDK, wherein the front-end SDK encapsulates the script generation interface;

[0008] Based on the script generation interface, converting the task configuration information into script data;

[0009] The script data and identification information of the task system are stored in association with each other. The script data and identification information stored in association are used to obtain the script data associated with the identification information based on the identification information of the task system, and process the business request based on the script data.

[0010] In another aspect, a task processing method is provided, the method comprising:

[0011] Receiving a service request from a terminal, the service request carrying identification information and request information of a task system;

[0012] Based on the identification information of the task system, obtaining script data associated with the identification information, wherein the script data is obtained by converting the task configuration information of the task system by the front-end SDK based on a script generation interface;

[0013] The service request is processed based on the request information and the script data.

[0014] In another aspect, a task processing device is provided, the device comprising:

[0015] A first determination module is used to determine task configuration information of the task system;

[0016] A calling module, used to call a front-end SDK, wherein the front-end SDK encapsulates a script generation interface;

[0017] A conversion module, used to convert the task configuration information into script data based on the script generation interface;

[0018] The first storage module is used to store the script data and the identification information of the task system in an associated manner, and the associated stored script data and identification information are used to obtain the script data associated with the identification information based on the identification information of the task system, and process the business request based on the script data.

[0019] In another aspect, a task processing device is provided, the device comprising:

[0020] A receiving module, used for receiving a service request from a terminal, wherein the service request carries identification information and request information of a task system;

[0021] A second acquisition module is used to acquire script data associated with the identification information based on the identification information of the task system, wherein the script data is obtained by converting the task configuration information of the task system by the front-end SDK based on the script generation interface;

[0022] A processing module is used to process the service request based on the request information and the script data.

[0023] On the other hand, a device is provided, comprising a processor and a memory, wherein the memory stores at least one program code, and the at least one program code is loaded and executed by the processor to implement the task processing method described above.

[0024] On the other hand, a computer-readable storage medium is provided, wherein at least one program code is stored in the storage medium, and the at least one program code is loaded and executed by a processor to implement the task processing method described above.

[0025] On the other hand, a computer program product is provided. The computer program product stores at least one program code. The at least one program code is used to be executed by a processor to implement the task processing method described above.

[0026] In an embodiment of the present application, the front-end SDK encapsulates a script generation interface, and the script generation interface has the ability to generate script data; therefore, when the task system needs to be reconstructed, the user only needs to configure the task configuration information, and the script data does not need to be written by the user, but is directly generated by the script generation interface encapsulated in the front-end SDK, thereby reducing the development cost of the task system. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 A schematic diagram showing multiple states of a task system shown in an exemplary embodiment of the present application is shown;

[0028] Figure 2 A schematic diagram showing an implementation environment of a task processing method shown in an exemplary embodiment of the present application;

[0029] Figure 3 An architectural diagram of a redesigned task system according to an exemplary embodiment of the present application is shown;

[0030] Figure 4 A flowchart of a task processing method shown in an exemplary embodiment of the present application is shown;

[0031] Figure 5 A flowchart of a task processing method shown in an exemplary embodiment of the present application is shown;

[0032] Figure 6 A flowchart of a task processing method shown in an exemplary embodiment of the present application is shown;

[0033] Figure 7 A flowchart of a task processing method shown in an exemplary embodiment of the present application is shown;

[0034] Figure 8 A flowchart of a task processing method shown in an exemplary embodiment of the present application is shown;

[0035] Fig. 9 A flowchart of a task processing method shown in an exemplary embodiment of the present application is shown;

[0036] Fig.10 A schematic diagram of an editing interface shown in an exemplary embodiment of the present application is shown;

[0037] Fig.11 A flowchart of a task processing method shown in an exemplary embodiment of the present application is shown;

[0038] Fig.12 An architectural diagram showing an exemplary embodiment of the present application is shown;

[0039] Fig.13 A sending flow chart of a first task event shown in an exemplary embodiment of the present application is shown;

[0040] Fig.14 A flowchart of a task processing method shown in an exemplary embodiment of the present application is shown;

[0041] Fig.15 A block diagram of a task processing device shown in an exemplary embodiment of the present application is shown;

[0042] Fig.16 A block diagram of a task processing device shown in an exemplary embodiment of the present application is shown;

[0043] Fig.17 A block diagram of a task management platform shown in an exemplary embodiment of the present application is shown;

[0044] Fig.18 A block diagram of a service server according to an exemplary embodiment of the present application is shown. DETAILED DESCRIPTION

[0045] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0046] The term "multiple" as used herein refers to two or more than two. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the related objects are in an "or" relationship.

[0047] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.) and signals involved in this application are all authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions. For example, the task configuration information and request information involved in this application are all obtained with full authorization.

[0048] Many applications have task systems embedded in them. Task systems can effectively motivate users to take action and increase user participation and activity. Moreover, task systems are often combined with reward mechanisms. Users will receive certain rewards after completing tasks, which will generate a sense of satisfaction and achievement. At the same time, task systems can also guide users to gain a deeper understanding of the products or services in the application, stimulate users' desire to buy, and thus increase product conversion rates. Please refer to Figure 1 The task system includes multiple states, namely, unstarted, unfinished, pending, received, and ended; the task system can set task display conditions. When the first terminal meets the task display conditions, the task system is displayed on the first terminal, that is, the task system is transferred from the unstarted state to the unfinished state; when the user completes the task set by the task system, that is, when the first terminal meets the task completion conditions, the task system is transferred from the unfinished state to the pending state; after the user receives the reward or the system issues the reward, the task system is transferred from the pending state to the received state; when the task system automatically ends the expired task, the task system is transferred from the received state to the ended state. When the task of the task system is reset or the task can be completed repeatedly, the task system is transferred from the received state to the unfinished state.

[0049] In the related technologies, when adding or modifying task display conditions, or adding or modifying task completion conditions, the developers and testers of the task system need to invest a long time (for example, one week), resulting in a high cost for the reconstruction of the task system. In addition, the related technologies will lead to poor reusability and scalability of the task system, obvious duplication of development work, and difficulty in meeting operational plans. In addition, if a new task system is to be connected to an application, the business party of the application needs a long time (for example, one week) to customize the development code of the application, and it is highly invasive to the business process of the application; for example, when a user completes a task set by the task system, the business process of the application needs to send a message to the task system to inform the task system.

[0050] In the embodiment of the present application, by introducing a decision engine and a marketing bus, the decision engine is used to generate scripts for the task system, thereby reducing the reconstruction cost of the task system, improving the reusability and scalability of the task system, and reducing the duplication of development work to meet the operation plan. The marketing bus is connected to the message queue of the application, the messages in the message queue are cleaned and understood, and then the cleaned messages are sent to the task system to avoid excessive intrusion into the business system of the application.

[0051] Please refer to Figure 2 , which shows a schematic diagram of an implementation environment of a task processing method shown in an exemplary embodiment of the present application. Figure 2The implementation environment includes: a task management platform, a business server and a first terminal; the task management platform is used to access the decision engine, generate script data of the task system through a decision request, and associate the script data with identification information of the task system and store them in a database; the business server is used to receive a business request from the first terminal, obtain script data associated with the identification information based on the identification information of the task system, and process the business request of the first terminal based on the script data.

[0052] In some embodiments, the task configuration information includes at least one of a task display condition and a task completion condition; when the task configuration information includes a task completion condition, the operator of the task system configures the task completion condition on the task management platform; when the task configuration information includes a task display condition, the implementation environment also includes a metadata management platform, the developer of the task system configures the task display condition in the metadata management platform, and then the task management platform obtains the configured task display condition from the metadata management platform. In other embodiments, the business server is connected to a marketing bus, and the marketing bus is connected to the message queue of the application program, and the messages in the message queue are cleaned and understood, and then the cleaned messages are sent to the task system to avoid excessive intrusion into the business system of the application program.

[0053] The task management platform and the business server can be independent physical servers, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms, but are not limited to this. In some embodiments, the task management platform and the business server are two different servers. In other embodiments, the task management platform and the business server can be integrated in the same server, that is, the task management platform and the business server can be two modules in the same server; or the task management platform can be integrated in the business server, that is, the business server has the function of the task management platform.

[0054] Please refer to Figure 3 , which shows an architecture diagram of a redesigned task system according to an exemplary embodiment of the present application. Figure 3, the architecture diagram includes: business layer, task capability system, public service layer and middleware layer. The business layer includes front-end data display module, background management configuration module and task data output module. Among them, the front-end data display module is used to display the interface-related data of the task system, such as task data, task style and task title. The background management configuration module is used to configure the relevant tasks of the task system. The task data output module is used to output the task data of the task. The task capability system includes business data encapsulation output module, user task life cycle management module, task compliance status policy rule verification module, task gameplay management module, other trigger capability management module and task configuration data cache module. The business data encapsulation output module is used to encapsulate the task data into an interface and output it to the front-end data display module. The user task life cycle management module is used to manage the life cycle of the task, that is, to manage multiple states of the task. The task compliance status policy rule verification module is used to verify whether the task message meets the task completion conditions. The task gameplay management module is used to manage tasks. For example, a task can be completed 5 times a day, and the task gameplay management module is the manager of 5 tasks. Other trigger capability management modules are used to notify the task system after the task is completed, and the task system notifies the user. The task configuration data cache module is used to cache task-related data to improve the response speed of the interface.

[0055] The public service layer includes the marketing bus, decision engine (or marketing decision engine), marketing user basic data module and public tracking module. The marketing bus is used to monitor, filter, convert and send between the task management platform and the task system. The decision engine is used to generate script data. The marketing user basic data module is used to manage the user's basic data. The public tracking module is used to track browsing tasks. The middleware layer includes RocketMQ, MySQL, Redis and ElasticSearch.

[0056] Please refer to Figure 4 , which shows a flowchart of a task processing method shown in an exemplary embodiment of the present application. Figure 4 , the method comprising:

[0057] Step 401: Determine the task configuration information of the task system.

[0058] The task configuration information includes at least one of a task display condition and a task completion condition. The task display condition refers to a condition that the application of the first terminal needs to meet in order to display the task system. In some embodiments, the task display condition may be that the user attribute of the application logged into the first terminal satisfies the condition; for example, the user's age is greater than a preset age. In other embodiments, the task display condition may be a behavioral condition of the user who logs into the application of the first terminal; for example, the number of times the user logs into the application is greater than a preset number. In other embodiments, the task display condition may also be that the version identifier of the application satisfies the condition; for example, the task display condition may be that the version number of the application of the first terminal is greater than a preset version number. In other embodiments, the task display condition may also be that the operating system of the first terminal satisfies the condition; for example, the task display condition may be that the operating system of the first terminal is an Android operating system, etc.

[0059] The task completion condition refers to the condition that the first terminal needs to meet to complete the task set by the task system; for example, if the application is a shopping application, the task completion condition may be that the user purchases the goods in the shopping application; for another example, if the application is a shopping application, the task completion condition may be that the user purchases the goods in the shopping application and the total amount of the goods is greater than the preset amount; for another example, if the application is a shopping application, the task completion condition may be that the user purchases the goods in the shopping application and the total amount of the goods is greater than the preset amount, etc. For another example, if the application is a loan application, the task completion condition may be that the amount of the user's loan is greater than the preset amount, etc.

[0060] Step 402: calling the front-end SDK of the decision engine, which encapsulates the script generation interface.

[0061] The front-end SDK of the decision engine can be stored in the metadata management platform; the task management platform calls the front-end SDK of the decision engine from the metadata management platform. The decision engine can also be called a rule engine, and the decision engine is developed from the reasoning engine. It is a component embedded in the application, which realizes the separation of the business decisions of the application from the application code and writes business decisions using predefined semantic modules; and the decision engine is used to receive data input, parse business rules, and make business decisions on the input data according to the business rules. The front-end SDK refers to a set of tools and libraries for developing front-end applications, aiming to simplify the development process and improve development efficiency. These tools and libraries provide the implementation of common functions; for example, the front-end SDK of the decision engine encapsulates the script generation script. The script generation interface is used to generate corresponding script data based on the task configuration information.

[0062] Step 403: Based on the script generation interface, the task configuration information is converted into script data of the task system.

[0063] The script generation interface has the ability to generate script data; therefore, in this step, the front-end SDK of the decision engine automatically calls the script generation interface and completes the generation of script data based on the script generation interface. The script data can be Java script data.

[0064] Step 404: The script data and the identification information of the task system are associated and stored in a database. The script data and identification information associated and stored in the database are used by the business server to obtain the script data associated with the identification information based on the identification information of the task system, and process the business request of the first terminal based on the script data.

[0065] The task representation of the task system can be the unique identifier (Identity Document, ID) of the task system. In the embodiment of the present application, the front-end SDK of the decision engine encapsulates the script generation interface, and the script generation interface has the ability to generate script data; therefore, when the task system needs to be reconstructed, the user only needs to configure the task configuration information, and the script data does not need to be written by the user, but is directly generated by the script generation interface encapsulated in the front-end SDK of the decision engine, thereby reducing the development cost of the task system.

[0066] In related technologies, when a task system is connected to new task display conditions or task completion conditions, one week of development and testing manpower is required. However, after the task system is reconstructed, the above manpower is no longer required. When the original task system is connected to new business events, the intrusion of business-side code is great, and it also relies on business development to invest one week of connection. After the task system is reconstructed, there is no need to invest business manpower to connect to new business events.

[0067] Please refer to Figure 5 , which shows a flowchart of a task processing method shown in an exemplary embodiment of the present application. Figure 5 , the method comprising:

[0068] Step 501: receiving a service request from a first terminal, where the service request carries identification information and request information of a task system.

[0069] The identification information of the task system may be the ID of the task system; the request information includes condition verification information or task verification information. The condition verification information is used to verify whether the first terminal meets the task display condition of the task system, thereby determining whether the first terminal can display the task system. The task verification information is used to verify whether the first terminal meets the task completion condition of the task system, thereby determining whether the first terminal can obtain the reward information of the task system.

[0070] Step 502: Based on the identification information of the task system, the script data associated with the identification information is obtained from the database. The script data is obtained by converting the task configuration information of the task system based on the script generation interface by the front-end SDK in the decision engine.

[0071] The task configuration information includes at least one of a task display condition and a task completion condition. In some embodiments, the business server sends a query request to the database, and the query request carries the identification information of the task system; the database receives the query request, obtains the script data associated with the identification information based on the identification information of the task system, and sends the script data to the business server. For example, based on the ID of the task system, the java script data to be executed is queried from the database, and the database returns the java script data to the business server.

[0072] Step 503: Process the service request based on the request information and script data.

[0073] The request information is passed in the script data, and the script data of the passed request information is executed by the decision engine to realize the processing of the business request. In the embodiment of the present application, the front-end SDK of the decision engine encapsulates the script generation interface, and the script generation interface has the ability to generate script data; therefore, when the task system needs to be reconstructed, the user only needs to configure the task configuration information, and the script data does not need to be written by the user, but is directly generated by the script generation interface encapsulated in the front-end SDK of the decision engine, and the generated script data is stored in the database, which is convenient for subsequent direct acquisition of script data from the database for business processing, thereby reducing the development cost of the task system and further reducing the cost of business processing.

[0074] Please refer to Figure 6 , which shows a flowchart of a task processing method shown in an exemplary embodiment of the present application. In the embodiment of the present application, the task configuration information includes the task display condition as an example for explanation. Figure 6 , the method comprising:

[0075] Step 601: The task management platform displays a second task editing interface through the metadata management platform.

[0076] The second task editing interface is an editing interface for configuring task display conditions, and the second task editing interface includes an input box corresponding to the first option corresponding to the task display condition and an input box corresponding to the condition, the input box corresponding to the first option is used to input or select the condition option, and the input box corresponding to the condition is used to input or select the condition that the selected condition option needs to meet; for example, the first user selects user attributes in the input box corresponding to the first option, and the first user enters the conditions that the user attributes need to meet in the input box corresponding to the condition; for another example, the first user selects user behavior in the input box corresponding to the first option, and the first user enters the conditions that the user behavior needs to meet in the input box corresponding to the condition. The task display condition can be configured by the developer of the task system; accordingly, the user in this step can refer to the developer.

[0077] In some embodiments, the metadata management platform is used to configure and manage task display conditions; and the metadata management platform may be a module in the task management platform; or the metadata management platform is independent of the task management platform. In the case where the metadata management platform is independent of the task management platform, this step may be: the metadata management platform sends the interface data of the second task editing interface to the second terminal, the second terminal receives the interface data sent by the metadata management platform, and renders the interface data to obtain the second task editing interface. The second terminal may be a terminal used by a developer.

[0078] Step 602: The task management platform obtains the task display conditions configured based on the second task editing interface, and stores the task display conditions in the metadata management platform.

[0079] The first user (developer) of the task system can select or input the condition option corresponding to the first option and the condition that the condition option needs to meet in the second task editing interface. The task management platform obtains the condition option configured in the second task editing interface and the condition that the condition option needs to meet, and forms the task display condition with the condition option and the condition that the condition option needs to meet, and stores the task display condition in the metadata management platform. For example, if the condition option selected by the user is user attribute, and the condition that the user attribute needs to meet is that the age is greater than the preset age, then the task display condition is that the user's age is greater than the preset age. For another example, if the condition option selected by the user is user behavior (login behavior), and the condition that the user behavior needs to meet is that the number of logins is greater than the preset number, then the task display condition is that the number of times the user logs into the application is greater than the preset number.

[0080] In some embodiments, the metadata management platform is independent of the task management platform; in this step, the metadata management platform obtains the task display conditions and stores the task display conditions. Accordingly, this step can be replaced by: the metadata management platform obtains the task display conditions configured based on the second task editing interface and stores the task management conditions.

[0081] Step 603: The task management platform calls the front-end SDK of the decision engine, and the front-end SDK of the decision engine encapsulates the script generation interface and the metadata interface.

[0082] The script generation interface is used to generate corresponding script data based on task configuration information. The metadata interface is used to obtain task display conditions from the metadata management platform.

[0083] Step 604: The task management platform obtains the task display conditions from the metadata management platform based on the metadata interface.

[0084] When reconstructing the task system, the task management platform obtains the task display conditions from the metadata management platform based on the metadata interface.

[0085] Step 605: The task management platform converts the task display conditions into script data of the task system based on the script generation interface.

[0086] The script generation interface has the ability to generate script data; therefore, in this step, the front-end SDK of the decision engine automatically calls the script generation interface and completes the generation of script data corresponding to the task display condition based on the script generation interface. The script data can be Java script data.

[0087] Step 606: The task management platform associates the script data with the identification information of the task system and stores it in a database. The script data and identification information associated with each other and stored in the database are used by the business server to obtain the script data associated with the identification information based on the identification information of the task system, and process the business request of the first terminal based on the script data.

[0088] In an embodiment of the present application, the front-end SDK of the decision engine encapsulates a script generation interface, and the script generation interface has the ability to generate script data; therefore, when the task system needs to be reconstructed, especially when reconstructing the task display conditions of the task system, the user only needs to configure the task display conditions, and the script data does not need to be written by the user, but is directly generated by the script generation interface encapsulated in the front-end SDK of the decision engine, thereby reducing the development cost of the task system. In addition, the embodiment of the present application combines the decision engine, the task management platform and the metadata management platform to create a simplified version of the low-code platform, with zero development to connect new task display conditions and task completion conditions; the task management background is connected through the front-end SDK of the decision engine to complete the rule configuration of the background task display conditions and task completion conditions. In addition, the subsequent business server can complete the rule judgment locally through the front-end SDK of the decision engine, without the need for network calls, thereby improving the performance of the business server in processing requests.

[0089] Please refer to Figure 7 , which shows a flowchart of a task processing method shown in an exemplary embodiment of the present application. In the embodiment of the present application, the task configuration information includes the task completion condition as an example for explanation. Figure 7 , the method comprising:

[0090] Step 701: The task management platform displays a first task editing interface.

[0091] The first task editing interface is an editing interface for configuring the task completion conditions, and the first task editing interface includes an input box corresponding to the second option corresponding to the task completion condition and an input box corresponding to the condition, the input box corresponding to the second option is used to enter or select the condition option, and the input box corresponding to the condition is used to enter or select the conditions that need to be met for the selected condition option; for example, the second user selects the second user behavior in the input box corresponding to the second option, and the second user enters the behavior condition in the input box corresponding to the condition.

[0092] The task display conditions can be configured by the operator of the task system; therefore, the user in this step may refer to the operator, and the operator configures the task completion conditions through the third terminal; accordingly, this step may be: the task management platform sends the interface data of the first task editing interface to the third terminal, the third terminal receives the interface data of the first task editing interface, and renders the interface data to obtain the first task editing interface.

[0093] Step 702: The task management platform obtains the task completion condition configured based on the first task editing interface.

[0094] The second user (operator) of the task system can select or input the condition option corresponding to the second option and the condition that the condition option needs to meet in the first task editing interface. The task management platform obtains the condition option configured in the first task editing interface and the condition that the condition option needs to meet, and combines the condition option and the condition that the condition option needs to meet into the task completion condition. For example, the condition option selected by the user is that the user behavior is a browsing time task, the behavior condition that the user behavior needs to meet is that the traffic duration is greater than 10 seconds, and the task ID is the task ID of the current task.

[0095] Step 703: The task management platform calls the front-end SDK of the decision engine, and the front-end SDK of the decision engine encapsulates the script generation interface.

[0096] In some embodiments, this step is the same as step 402 and will not be repeated here.

[0097] Step 704: The task management platform converts the task completion conditions into script data of the task system based on the script generation interface.

[0098] The script generation interface has the ability to generate script data; therefore, in this step, the front-end SDK of the decision engine automatically calls the script generation interface and completes the generation of script data corresponding to the task completion condition based on the script generation interface. The script data can be java script data.

[0099] Step 705: The task management platform associates the script data with the identification information of the task system and stores it in a database. The script data and identification information associated with each other and stored in the database are used by the business server to obtain the script data associated with the identification information based on the identification information of the task system, and process the business request of the first terminal based on the script data.

[0100] In an embodiment of the present application, the front-end SDK of the decision engine encapsulates a script generation interface, and the script generation interface has the ability to generate script data; therefore, when the task system needs to be reconstructed, especially when reconstructing the task completion conditions of the task system, the user only needs to configure the task display conditions, and the script data does not need to be written by the user, but is directly generated by the script generation interface encapsulated in the front-end SDK of the decision engine, thereby reducing the development cost of the task system.

[0101] Please refer to Figure 8 , which shows a flowchart of a task processing method shown in an exemplary embodiment of the present application. In the embodiment of the present application, the task configuration information includes a task display condition and a task completion condition. Figure 8 , the method comprising:

[0102] Step 801: The task management platform displays a second task editing interface through the metadata management platform.

[0103] In some embodiments, this step is the same as step 601 and will not be repeated here.

[0104] Step 802: The task management platform obtains the task display conditions configured based on the second task editing interface, and stores the task display conditions in the metadata management platform.

[0105] In some embodiments, this step is the same as step 602 and will not be described in detail here. The task display condition may be referred to as metadata; Fig. 9 , the developer configures the task display conditions such as user attributes / behavior conditions in the metadata management platform, and the configuration of the task display conditions is completed.

[0106] Step 803: The task management platform displays the first task editing interface; and obtains the task completion condition configured based on the first task editing interface.

[0107] In some embodiments, this step is the same as steps 701 and 702 and will not be repeated here.

[0108] Step 804: the task management platform calls the front-end SDK of the decision engine, and the front-end SDK of the decision engine encapsulates the script generation interface and the metadata interface.

[0109] In some embodiments, this step is the same as step 603 and will not be repeated here.

[0110] Step 805: The task management platform obtains the task display conditions of the task system from the metadata management platform based on the metadata interface.

[0111] In some embodiments, this step is the same as step 604 and will not be repeated here. In other embodiments, the task management platform may first display the task display conditions in the background, and then configure the task completion conditions; accordingly, steps 803-805 may be replaced by: the task management platform displays the first task editing interface, based on the script generation interface, converts the task display conditions and the task completion conditions into script data of the task system, displays the task display conditions in the background, and obtains the task completion conditions configured based on the first task editing interface. For example, please continue to refer to Fig. 9 , the operator of the task system issues tasks / configures tasks; at this time, the task management platform requests to obtain the task display conditions from the metadata management platform, and the metadata management platform returns the task display conditions to the task management platform, displays the task display conditions in the background, and then the operator configures the task completion conditions according to the actual situation.

[0112] Step 806: The task management platform converts the task display conditions and task completion conditions into script data of the task system based on the script generation interface.

[0113] The script generation interface has a splicing function, and the script generation interface at this time can also be called a script splicing interface; accordingly, this step can be: the task management platform splices the task display condition and the task completion condition through the script generation interface, and converts the spliced ​​conditions into script data based on the script generation interface. The script data can be Java script data.

[0114] In some embodiments, the task management platform performs reverse display processing on the task configuration information to obtain a reverse display file; the reverse display file is associated with the script data and stored in a database; the reverse display file is used to display the task editing interface corresponding to the task configuration information; the reverse display file can be a json file; and the task editing interface can be at least one of a first task editing interface and a second task editing interface. Among them, the process of the task management platform reverse displaying the task editing interface based on the reverse display file can be: the task management platform reads the reverse display file from the database, inputs the reverse display file into the front-end SDK of the decision engine, and the front-end SDK displays the task editing interface according to the reverse display file.

[0115] For example, the task configuration information includes the task completion condition, and the task management platform displays the task completion condition to the first task editing interface. Fig.10 As shown, the subtitle of the task completion condition is to get a red envelope by browsing for 10 seconds; the task description is 100% to get a red envelope; the task completion condition includes the user behavior of browsing time task, the behavior condition is browsing time equal to 10 seconds and the task ID is equal to the task ID of the current task. For example, please continue to refer to Fig. 9 The task management platform calls the script generation interface encapsulated in the front-end SDK of the decision engine from the metadata management platform, generates a java script based on the script generation interface, and the metadata management platform returns the java script to the task management platform and the reverse display json; the task management platform stores the java script and the reverse display json in the database.

[0116] Step 807: The task management platform associates the script data with the identification information of the task system and stores it in a database. The script data and identification information associated with each other and stored in the database are used by the business server to obtain the script data associated with the identification information based on the identification information of the task system, and process the business request of the first terminal based on the script data.

[0117] In an embodiment of the present application, the front-end SDK of the decision engine encapsulates a script generation interface, and the script generation interface has the ability to generate script data; therefore, when it is necessary to reconstruct the task system, especially when reconstructing the task display conditions and task completion conditions of the task system, the user only needs to configure the task display conditions, and the script data does not need to be written by the user, but is directly generated by the script generation interface encapsulated in the front-end SDK of the decision engine, thereby reducing the development cost of the task system.

[0118] Please refer to Fig.11 , which shows a flowchart of a task processing method shown in an exemplary embodiment of the present application. In the embodiment of the present application, the task configuration information includes task display conditions, and the request information includes condition verification information.

[0119] refer to Fig.11 , the method comprising:

[0120] Step 1101: The service server receives a service request from a first terminal, where the service request carries identification information and condition verification information of a task system.

[0121] The condition verification information is used to verify whether the first terminal meets the task display condition of the task system, and further determine whether the first terminal can display the task system.

[0122] Step 1102: Based on the identification information of the task system, the business server obtains script data associated with the identification information from the database. The script data is obtained by converting the task configuration information of the task system based on the script generation interface by the front-end SDK in the decision engine.

[0123] The business server sends a query request to the database, and the query request carries the identification information of the task system; the database receives the query request, obtains the script data associated with the identification information based on the identification information of the task system, and sends the script data to the business server. For example, please continue to refer to Fig. 9 , the business server queries the java script data to be executed from the database based on the ID of the task system, and the database returns the java script data to the business server.

[0124] Step 1103: The business server runs the script data to determine whether the condition verification information satisfies the task display condition.

[0125] The business server passes the conditional verification information into the script data, and runs the script data to obtain a verification result, which is either satisfied or not satisfied. A satisfied verification result means that the conditional verification information satisfies the task display condition, that is, the first terminal allows the task system to be displayed; a not satisfied verification result means that the conditional verification information does not meet the task display condition, that is, the first terminal does not allow the task system to be displayed. In the case where the conditional verification information meets the task display condition, a first task event is sent to the task system through the following steps 1104-1105, and the first task event is used to notify the task system to display in the first terminal. In the case where the conditional verification information does not meet the task display condition, the task system is terminated or a third task event is sent to the task system to notify the task system not to display in the first terminal.

[0126] Step 1104: When the condition verification information satisfies the task display condition, the business server sends a first task event to the marketing bus, and the first task event is used to notify the first terminal to display the task system.

[0127] The marketing bus is a high-concurrency, low-latency message platform that integrates monitoring, filtering, conversion, and sending. In this embodiment of the application, the marketing bus is connected between the business server and the task system, and the first task event is monitored, filtered, converted, and sent through the marketing bus. For example, please refer to Fig.12 , which shows an architecture diagram of an exemplary embodiment of the present application; refer to Fig.12 , the architecture diagram includes a first terminal, a business server, a marketing bus and a task system; the business server may include at least one business server and at least one epoch tracking service; the business server is used to receive and process the business request of the first terminal. The marketing bus includes multiple message queues, an event source module, an event routing module, an event management module and an event target module. Multiple message queues are used to receive and store task events; for example, multiple message queues include a first RocketMQ, a first Kafka, a second RocketMQ and a second Kafka; the first RocketMQ or the first Kafka is used to receive and store the first task event sent by the business server. The second RocketMQ or the second Kafka is used to receive and store the first task event transmitted from the marketing bus to the task system.

[0128] The event source module is used when the business server corresponding to the application is started. The application will load the configured event routing information and the message source of the task event and initialize the corresponding event handler. If the same message source appears in the event routing information of different events, you only need to configure one corresponding event handler. If the message source of the task event is an MQ source, you need to set an adapted MQ message listener; for task events in RPC or HTTP mode, there is no need to dynamically load the event handler, you only need to implement the corresponding interface in the code; for example, the event source module includes an event consumption unit and an event conversion unit; the event consumption unit is used to consume the first task event stored in the first RocketMQ or the first Kafka; the event conversion unit is used to convert the format of the first task event.

[0129] The event routing module includes a routing rule unit and a conversion rule unit; the routing rule unit loads the event routing information of the event into the memory and refreshes it regularly; when storing the event routing information, the routing rule unit uses the event identifier as the key and the event routing information as the value to associate and store the event identifier and the event routing information, so as to facilitate the rapid location of the matching event routing information when the event is received. The event management module includes a metadata management unit, an event persistence unit and a filtering unit; the metadata management unit is used to read the metadata in the metadata management platform. The event persistence unit is used to save the first task event into the persistent storage after the first task event is set to be persisted; the filtering unit is used to filter the first task events that meet the conditions.

[0130] The event target module is used to automatically load the first task event of RocketMQ or Kafka type when the application starts, initialize the corresponding producer bean (business server), and put the ID of the first task event as the key into a map to facilitate the event delivery station to find the corresponding producer bean for operation. For example, the event target module includes an event sending unit and a target metadata management unit. The event sending unit is used to send the first task event to the task system, and the target metadata management unit is used to read the metadata in the metadata management platform.

[0131] Step 1105: The business server forwards the first task event to the task system via the marketing bus.

[0132] In some embodiments, the marketing bus forwards the first task event based on event routing information; correspondingly, this step may be: the business server determines the event routing information of the first task event based on the event identifier of the first task event through the marketing bus, and the event routing information is used to represent the route between the marketing bus and the task system; and forwards the first task event to the task system based on the event routing information through the marketing bus.

[0133] Prior to this step, the marketing bus loads the event routing information of the event into the memory and refreshes it periodically; when storing the event routing information, the marketing bus uses the event identifier as the key and the event routing information as the value, and associates and stores the event identifier and the event routing information, so as to facilitate rapid location of the matching event routing information when the event is received; accordingly, the step in which the marketing bus determines the event routing information of the task event based on the event identifier of the first task event may be: the marketing bus obtains the event routing information of the first task event from the correspondence between the event identifier and the event routing information based on the event identifier of the first task event.

[0134] In other embodiments, the marketing bus can directly forward the first task event; or the marketing bus converts the format of the first task event and then forwards the first task event after the format conversion; and the marketing bus predefines the task event in a standard format; for task events in non-standard formats, the task events in non-standard formats are converted into task events in standard formats through conversion rules; for example, the format of the first task event is a standard format (such as json), and the marketing bus can configure variables and templates to achieve format conversion with the help of the default standard event converter; if the standard event converter cannot meet the requirements, or the format of the first task event is not a standard format (non-json), the user can customize the format converter to complete the required format conversion. Accordingly, this step can be implemented by the following steps (1) to (2), including:

[0135] (1) When the format of the first task event is not a standard format, the business server converts the first task event into a first task event of a standard format through the marketing bus.

[0136] (2) The business server forwards the first task event in a standard format to the task system through the marketing bus.

[0137] The business server parses the first task event through the marketing bus to obtain the message content; when the format of the message content is the target format, the first task event is converted into a first task event in a standard format through the standard event converter in the marketing bus, and the standard event converter is used to convert between the target format and the standard format; when the format of the message content is not the target format, the first task event is converted into a first task event in a standard format through the custom event converter in the marketing bus, and the custom event converter is used to convert between other formats and the standard format.

[0138] The format of the message content is not the target format, which means that the format of the message content is kafka, RocketMQ or RabbitMQ, etc. The business server in the embodiment of the present application connects the task event through the marketing bus, has no intrusion into the business system of the application, and supports converting the task event in non-standard format into the task event in standard format through the configuration of the business system, and then pushes it to the task system.

[0139] In other embodiments, the first task event is filtered by the marketing bus; accordingly, this step may be: filtering and judging the first task event based on the filtering information through the marketing bus; when the first task event meets the filtering condition corresponding to the filtering information, forwarding the first task event to the task system through the marketing bus. When the first task event meets the filtering condition corresponding to the filtering information, the first task event is filtered out, that is, the first task event is not forwarded to the task system. The marketing bus may filter and judge the first task event through an event filter, and the event filter may be a jsonpath open source filtering architecture, so as to filter out task events that meet the conditions. For example, the filtering information may be a non-empty event; when the first task event is a non-empty event, it is determined that the first task event meets the filtering condition; when the first task event is not a non-empty event, it is determined that the first task event does not meet the filtering condition.

[0140] Please refer to Fig.13 , which shows the sending process of the first task event shown in an exemplary embodiment of the present application. Fig.13 The sending process includes parsing the message content based on the event message details of the first task event, converting the first task event into a standard event based on the message content, filtering the converted first task event, and then determining the event routing information, and sending the first task event to the task system based on the event routing information. In some embodiments, after filtering the first task event, it can also be determined whether the first task event needs to be persisted, and if it is determined that the first task event needs to be persisted, the first task event is asynchronously stored in the database.

[0141] In an embodiment of the present application, a marketing bus is connected to the business server, and the message queue of the application is connected through the marketing bus to clean and understand the messages in the message queue, and then the cleaned messages are sent to the task system to avoid excessive intrusion into the business system of the application.

[0142] Please refer to Fig.14 , which shows a flowchart of a task processing method shown in an exemplary embodiment of the present application. In the embodiment of the present application, the task configuration information includes the task completion condition, and the request information includes the task verification information.

[0143] refer to Fig.14, the method comprising:

[0144] Step 1401: The service server receives a service request from a first terminal, where the service request carries identification information of the task system and task verification information.

[0145] The task verification information is used to verify whether the first terminal meets the task completion conditions of the task system, and further determine whether the first terminal can obtain the reward information of the task system.

[0146] Step 1402: Based on the identification information of the task system, the business server obtains script data associated with the identification information from the database. The script data is obtained by converting the task configuration information of the task system based on the script generation interface by the front-end SDK in the decision engine.

[0147] In some embodiments, this step is the same as step 1102 and will not be repeated here.

[0148] Step 1403: The business server runs the script data to determine whether the task verification information meets the task completion conditions.

[0149] The business server passes the task verification information into the script data, and runs the script data to obtain the verification result, which is satisfied or not satisfied. If the verification result is satisfied, it means that the task verification information satisfies the task completion condition, that is, the first terminal allows the issuance of reward information; if the verification result is not satisfied, it means that the task verification information does not satisfy the task completion condition, that is, the first terminal does not allow the issuance of reward information. When the task verification information satisfies the task completion condition, the second task event is sent to the task system through the following steps 1404-1405, and the second task event is used to notify the task system to issue reward information to the first terminal. When the task verification information does not meet the task completion condition, the task ends or sends a fourth task event to the task system, and the fourth task event is used to notify the task system not to issue reward information to the first terminal.

[0150] Step 1404: When the task verification information meets the task completion condition, the business server sends a second task event to the marketing bus, and the second task event is used to notify the task system to issue reward information to the first terminal.

[0151] In some embodiments, this step is the same as step 1104 and will not be repeated here.

[0152] Step 1405: The business server forwards the second task event to the task system via the marketing bus.

[0153] In some embodiments, this step is similar to step 1105 and will not be repeated here.

[0154] In the embodiment of the present application, the business server is connected to the marketing bus, and the message queue of the application is connected through the marketing bus to clean and understand the messages in the message queue, and then the cleaned messages are sent to the task system to avoid excessive intrusion of the business system of the application. In addition, since the embodiment of the present application can decouple the business code of the application and the rule code of the task system, when adding or modifying the task display conditions or task completion conditions of the task system, the business code does not need to be changed, which greatly improves the maintainability of the business system.

[0155] Please refer to Fig.15 , which shows a task processing device shown in an exemplary embodiment of the present application, the device includes:

[0156] The first determination module 1501 is used to determine the task configuration information of the task system; the calling module 1502 is used to call the front-end SDK, which encapsulates the script generation interface; the conversion module 1503 is used to convert the task configuration information into script data based on the script generation interface; the first storage module 1504 is used to associate and store the script data and the identification information of the task system, and the associated stored script data and identification information are used to obtain the script data associated with the identification information based on the identification information of the task system, and process the business request based on the script data.

[0157] In some embodiments, the task configuration information includes task display conditions, and the front-end SDK also encapsulates a metadata interface; the first determination module 1501 is used to obtain the task display conditions based on the metadata interface, and the task display conditions are configurable. In some embodiments, the task configuration information includes task completion conditions; the first determination module 1501 is used to display the first task editing interface; obtain the task completion conditions configured based on the first task editing interface. In some embodiments, the task configuration information includes task display conditions and task completion conditions, and the front-end SDK also encapsulates a metadata interface; the first determination module 1501 is used to obtain the task display conditions based on the metadata interface, and the task display conditions are configurable; display the first task editing interface; obtain the task completion conditions configured based on the first task editing interface.

[0158] In some embodiments, the device further comprises: a display module for displaying the second task editing interface; a first acquisition module for acquiring and storing the task display conditions configured based on the second task editing interface. In some embodiments, the device further comprises: a reverse display module for performing reverse display processing on the task configuration information to obtain a reverse display file; a second storage module for associating and storing the reverse display file with the script data, and the reverse display file is used to display the task editing interface corresponding to the task configuration information.

[0159] In the embodiment of the present application, the front-end SDK encapsulates the script generation interface, and the script generation interface has the ability to generate script data; therefore, when the task system needs to be reconstructed, the user only needs to configure the task configuration information, and the script data does not need to be written by the user, but is directly generated by the script generation interface encapsulated in the front-end SDK, thereby reducing the development cost of the task system. It should be noted that when the task processing device provided in the above embodiment performs task processing, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned function allocation can be completed by different functional modules as needed, that is, the internal structure of the device (task management platform) is divided into different functional modules to complete all or part of the functions described above. In addition, the task processing device provided in the above embodiment belongs to the same concept as the task processing method embodiment. The specific implementation process is detailed in the method embodiment, which will not be repeated here.

[0160] Please refer to Fig.16 , which shows a task processing device shown in an exemplary embodiment of the present application, the device includes:

[0161] The receiving module 1601 is used to receive the business request of the terminal, and the business request carries the identification information and request information of the task system; the second acquisition module 1602 is used to obtain the script data associated with the identification information based on the identification information of the task system, and the script data is obtained by converting the task configuration information of the task system based on the script generation interface of the front-end SDK; the processing module 1603 is used to process the business request based on the request information and the script data.

[0162] In some embodiments, the task configuration information includes task display conditions, and the request information includes condition verification information; the processing module 1603 is used to run the script data to determine whether the condition verification information meets the task display conditions; when the condition verification information meets the task display conditions, a first task event is sent to the task system, and the first task event is used to notify the task system to display in the first terminal.

[0163] In some embodiments, the task configuration information includes task completion conditions, and the request information includes task verification information; the processing module 1603 is used to run the script data to determine whether the task verification information meets the task completion conditions; when the task verification information meets the task completion conditions, a second task event is sent to the task system, and the second task event is used to notify the task system to issue reward information to the first terminal.

[0164] In some embodiments, the task event is a first task event or a second task event, and the processing module 1603 is used to send the task event to the marketing bus; and forward the task event to the task system through the marketing bus. In some embodiments, the processing module 1603 is used to determine the event routing information of the task event based on the event identifier of the task event through the marketing bus, and the event routing information is used to indicate the route between the marketing bus and the task system; and forward the task event to the task system through the marketing bus based on the event routing information. In some embodiments, the processing module 1603 is used to convert the task event into a task event in a standard format through the marketing bus when the format of the task event is not in a standard format; and forward the task event in the standard format to the task system through the marketing bus.

[0165] In some embodiments, processing module 1603 is used to parse the task event through the marketing bus to obtain the message content; when the format of the message content is the target format, the task event is converted into a task event in the standard format through the standard event converter in the marketing bus, and the standard event converter is used to convert between the target format and the standard format; when the format of the message content is not the target format, the task event is converted into a task event in the standard format through the custom event converter in the marketing bus, and the custom event converter is used to convert between other formats and the standard format.

[0166] In some embodiments, the processing module 1603 is used to filter and judge the task event based on the filtering information through the marketing bus; when the task event meets the filtering condition corresponding to the filtering information, the task event is forwarded to the task system through the marketing bus.

[0167] In an embodiment of the present application, the front-end SDK encapsulates a script generation interface, and the script generation interface has the ability to generate script data; therefore, when the task system needs to be reconstructed, the user only needs to configure the task configuration information, and the script data does not need to be written by the user. It is directly generated by the script generation interface encapsulated in the front-end SDK, and the generated script data is stored in the database, which is convenient for subsequent direct acquisition of script data from the database for business processing, thereby reducing the development cost of the task system and further reducing the cost of business processing.

[0168] It should be noted that the task processing device provided in the above embodiment only uses the division of the above functional modules as an example when performing task processing. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device (business server) is divided into different functional modules to complete all or part of the functions described above. In addition, the task processing device provided in the above embodiment and the task processing method embodiment belong to the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0169] The structure diagram of the task management platform can be found in Fig.17 The task management platform 1700 may have relatively large differences due to different configurations or performances, and may include a processor (Central Processing Units, CPU) 1701 and a memory 1702, wherein the memory 1702 stores at least one program code, which is loaded and executed by the processor 1701 to implement the operations performed by the server in the above-mentioned vehicle display method. Of course, the server 1700 may also have components such as a wired or wireless network interface, a keyboard, and an input and output interface for input and output, and the server 1700 may also include other components for implementing device functions, which will not be described in detail here.

[0170] The structural diagram of the business server can be found in Fig.18 The business server 1800 may have relatively large differences due to different configurations or performances, and may include a processor (Central Processing Units, CPU) 1801 and a memory 1802, wherein the memory 1802 stores at least one program code, which is loaded and executed by the processor 1801 to implement the operations performed by the server in the above-mentioned vehicle display method. Of course, the server 1800 may also have components such as a wired or wireless network interface, a keyboard, and an input and output interface for input and output. The server 1800 may also include other components for implementing device functions, which will not be described in detail here.

[0171] The embodiment of the present application also provides a computer-readable medium, which stores at least one program code, which is loaded and executed by a processor to implement the task processing method shown in the above embodiments. The embodiment of the present application also provides a computer program product, which stores at least one program code, which is loaded and executed by a processor to implement the task processing method shown in the above embodiments.

[0172] In some embodiments, the computer program product involved in the embodiments of the present application may be deployed and executed on a task management platform, or on multiple task management platforms located at one location, or on multiple task management platforms distributed at multiple locations and interconnected by a communication network. Multiple task management platforms distributed at multiple locations and interconnected by a communication network may constitute a blockchain system.

[0173] In some embodiments, the computer program product involved in the embodiments of the present application may be deployed and executed on a business server, or on multiple business servers located at one location, or on multiple business servers distributed at multiple locations and interconnected by a communication network. Multiple business servers distributed at multiple locations and interconnected by a communication network can constitute a blockchain system.

[0174] Those skilled in the art should be aware that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented with hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein the communication media include any media that facilitates the transmission of a computer program from one place to another. The storage medium can be any available medium that a general or special-purpose computer can access.

[0175] The above description is only an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. A task processing method, characterized in that: The method comprises: Determine the task configuration information of the task system; Calling the front-end SDK, wherein the front-end SDK encapsulates the script generation interface; Based on the script generation interface, converting the task configuration information into script data; The script data and identification information of the task system are stored in association with each other. The script data and identification information stored in association are used to obtain the script data associated with the identification information based on the identification information of the task system, and process the business request based on the script data.

2. The method according to claim 1, characterized in that The task configuration information includes task display conditions, and the front-end SDK also encapsulates a metadata interface; The step of determining the task configuration information of the task system includes: The task display condition is acquired based on the metadata interface, and the task display condition is configurable.

3. The method according to claim 1, characterized in that The task configuration information includes task completion conditions; The step of determining the task configuration information of the task system includes: Display the first task editing interface; Acquire the task completion condition configured based on the first task editing interface.

4. The method according to claim 1, characterized in that: The task configuration information includes task display conditions and task completion conditions, and the front-end SDK also encapsulates a metadata interface; The step of determining the task configuration information of the task system includes: Acquiring the task display condition based on the metadata interface, where the task display condition is configurable; Displaying a first task editing interface; and obtaining the task completion condition configured based on the first task editing interface.

5. The method according to claim 2 or 4, characterized in that: The method further comprises: Display the second task editing interface; Acquire and store the task display condition configured based on the second task editing interface.

6. A task processing method, characterized in that: The method comprises: Receiving a service request from a terminal, the service request carrying identification information and request information of a task system; Based on the identification information of the task system, obtaining script data associated with the identification information, wherein the script data is obtained by converting the task configuration information of the task system by the front-end SDK based on a script generation interface; The service request is processed based on the request information and the script data.

7. The method according to claim 6, characterized in that The task configuration information includes task display conditions, and the request information includes condition verification information; The processing of the service request based on the request information and the script data includes: Run the script data to determine whether the condition verification information satisfies the task display condition; When the condition verification information satisfies the task display condition, a first task event is sent to the task system, where the first task event is used to notify the task system to display in the first terminal.

8. The method according to claim 6, characterized in that The task configuration information includes task completion conditions, and the request information includes task verification information; The processing of the service request based on the request information and the script data includes: Run the script data to determine whether the task verification information meets the task completion condition; When the task verification information satisfies the task completion condition, a second task event is sent to the task system, where the second task event is used to notify the task system to issue reward information to the first terminal.

9. A device, characterized in that: The device includes a processor and a memory, wherein at least one program code is stored in the memory, and the at least one program code is loaded and executed by the processor to implement the task processing method according to any one of claims 1 to 8.

10. A computer program product, characterized in that The computer program product stores at least one program code, and the at least one program code is used to be executed by a processor to implement the task processing method according to any one of claims 1 to 8.

Images