Resource event processing method and apparatus

Abstract

The embodiment of the present specification provides a resource event processing method and device, wherein the resource event processing method comprises: performing resource parameter switching detection of a resource platform on each user according to a resource pre-configuration event; if the switching detection is passed, querying a user state based on a target scheduling instruction in a scheduling instruction sequence constructed to each user, and scheduling the target scheduling instruction to a resource processing system for resource configuration response processing based on the user state, so as to realize scheduling judgment of instruction scheduling of each user from multiple stages by combining resource parameter switching detection and user state.

Description

Technical Field

[0001] This document relates to the field of data processing technology, and in particular to a resource event processing method and apparatus. Background Technology

[0002] With the continuous development and promotion of Internet technology, the number of online service platforms provided by Internet technology is increasing, such as resource platforms. Resource platforms can provide users with resource-related services based on their needs and provide users with convenient means of service implementation. In this process, as the service scope of resource platforms continues to expand and users' demand for resource services from resource platforms becomes more diversified, the platform operators of resource platforms are also facing greater pressure and challenges. Summary of the Invention

[0003] This specification provides one or more embodiments of a resource event processing method applied to a scheduling system. The method includes: acquiring resource pre-configuration events for each user sent by a resource configuration system. The resource pre-configuration events are generated after pre-configuring resource parameters for each user on a resource platform. Using the user set identifier of the resource platform and the user identifiers of each user extracted from the resource pre-configuration events as system call inputs, the online database of the data system is invoked to perform user matching within the user set corresponding to the user set identifiers. Upon successful matching, a scheduling instruction corresponding to the resource pre-configuration event is constructed based on the event type of the resource pre-configuration event, obtaining a scheduling instruction sequence for each user. The user status is queried based on the target scheduling instruction in the scheduling instruction sequence, and the target scheduling instruction is scheduled to the resource processing system for resource configuration response processing based on the user status.

[0004] This specification provides one or more embodiments of a resource event processing apparatus, operating within a scheduling system. The apparatus includes: an event acquisition module configured to acquire resource pre-configuration events for each user sent by a resource configuration system. The resource pre-configuration events are generated after pre-configuring resource parameters for each user on a resource platform. A switch detection module configured to use a user set identifier from the resource platform and user identifiers extracted from the resource pre-configuration events as system call inputs to call the online database of a data system to perform user matching within the user set corresponding to the user set identifiers. An instruction construction module configured, upon successful matching, to construct scheduling instructions corresponding to the resource pre-configuration events based on the event type of the resource pre-configuration events, obtaining a sequence of scheduling instructions for each user. An instruction scheduling module configured to query user status based on target scheduling instructions in the sequence of scheduling instructions, and schedule the target scheduling instructions to the resource processing system for resource configuration response processing based on the user status.

[0005] This specification provides one or more embodiments of a resource event processing device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: acquire resource pre-configuration events for each user sent by a resource configuration system. The resource pre-configuration events are generated after pre-configuring resource parameters for each user on a resource platform. Using the user set identifier of the resource platform and the user identifiers of each user extracted from the resource pre-configuration events as system call inputs, the system calls an online database to perform user matching within the user set corresponding to the user set identifier. Upon successful matching, a scheduling instruction corresponding to the resource pre-configuration event is constructed based on the event type of the resource pre-configuration event, obtaining a sequence of scheduling instructions for each user. The user status is queried based on the target scheduling instruction in the sequence of scheduling instructions, and the target scheduling instruction is scheduled to the resource processing system for resource configuration response processing based on the user status.

[0006] This specification provides one or more embodiments of a computer-readable storage medium for storing computer-executable instructions, which, when executed, perform the following steps: Obtaining resource pre-configuration events for each user sent by a resource configuration system. The resource pre-configuration events are generated after pre-configuring resource parameters for each user on a resource platform. Using the user set identifier of the resource platform and the user identifiers of each user extracted from the resource pre-configuration events as system call inputs, the online database of the data system is invoked to perform user matching within the user set corresponding to the user set identifier. Upon successful matching, a scheduling instruction corresponding to the resource pre-configuration event is constructed based on the event type of the resource pre-configuration event, obtaining a sequence of scheduling instructions for each user. The user status is queried based on the target scheduling instruction in the sequence of scheduling instructions, and the target scheduling instruction is scheduled to the resource processing system for resource configuration response processing based on the user status. Attached Figure Description

[0007] To more clearly illustrate the technical solutions in one or more embodiments of this specification or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0008] Figure 1 A schematic diagram illustrating the implementation environment of a resource event handling method provided in one or more embodiments of this specification;

[0009] Figure 2A flowchart illustrating a resource event handling method provided in one or more embodiments of this specification;

[0010] Figure 3 A flowchart illustrating a resource event handling method for a quota increase scenario, provided for one or more embodiments of this specification;

[0011] Figure 4 A flowchart illustrating a resource event handling method applied to a pricing reduction scenario, provided for one or more embodiments of this specification;

[0012] Figure 5 A schematic diagram of an embodiment of a resource event processing apparatus provided for one or more embodiments of this specification;

[0013] Figure 6 This is a schematic diagram of the structure of a resource event processing device provided for one or more embodiments of this specification. Detailed Implementation

[0014] To enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of this document.

[0015] The resource event handling method provided in one or more embodiments of this specification is applicable to the instruction scheduling implementation environment. (Refer to...) Figure 1 The implementation environment includes at least:

[0016] The system includes a scheduling system 101, a resource allocation system 102, and a resource processing system 103; in addition, the implementation environment may also include a data system 104 and a resource platform 105.

[0017] The scheduling system 101 is used to perform resource parameter switching detection on each user's resource platform based on the resource pre-configuration events sent by the resource configuration system. If the switching detection is successful, the system queries the user status based on the target scheduling instruction in the user's scheduling instruction sequence and schedules the target scheduling instruction to the resource processing system for resource configuration response processing based on the user status.

[0018] Resource configuration system 102 is used to send resource pre-configuration events of each user to the scheduling system; resource processing system 103 is used to perform resource configuration response processing according to the target scheduling instructions of the scheduling system; data system 104 can be used for user matching; resource platform 105 can be used to send user behavior tags to the data system.

[0019] The scheduling system 101, resource allocation system 102, and resource processing system 103 can be deployed on the same server or on different servers; the server on which the scheduling system 101, resource allocation system 102, and resource processing system 103 are deployed can be one or more servers, a server cluster composed of several servers, or a cloud server of a cloud computing platform.

[0020] In this implementation environment, the scheduling system 101 obtains the resource pre-configuration events of each user sent by the resource configuration system 102, performs resource parameter switching detection on each user based on the resource pre-configuration events, and if the switching detection passes, queries the user status based on the target scheduling instruction in the scheduling instruction sequence constructed for each user, and schedules the target scheduling instruction to the resource processing system 103 for resource configuration response processing based on the user status. In this way, by combining resource parameter switching detection and user status, the scheduling judgment of each user's instruction scheduling is realized from multiple stages.

[0021] One or more embodiments of a resource event handling method provided in this specification are as follows:

[0022] Reference Figure 2 The resource event handling method provided in this embodiment can be applied to a scheduling system, specifically including steps S202 to S208.

[0023] Step S202: Obtain the resource pre-configuration events for each user sent by the resource configuration system.

[0024] The resource pre-configuration event mentioned in this embodiment refers to the event generated by pre-configuring the resource parameters of each user on the resource platform; optionally, the resource pre-configuration event is generated after pre-configuring the resource parameters of each user on the resource platform; the resource platform may be a credit granting platform used to grant credit to users.

[0025] In practical applications, users can submit resource requests, and the resource platform can create credit resource projects for users based on the submitted resource requests. Since users' credit risk is constantly changing, in order to improve users' resource usage experience on the resource platform and to improve the operational effectiveness of the resource platform, the resource parameters of users on the resource platform can be adjusted, thereby achieving flexible configuration of users' resource parameters.

[0026] In practice, the system acquires resource pre-configuration events for each user sent by the resource configuration system. These pre-configuration events are generated after pre-configuring the resource parameters for each user on the resource platform. Specifically, configuration personnel on the resource platform or the resource configuration system can submit parameter pre-configuration instructions for each user. The resource configuration system can pre-configure the resource parameters for each user on the resource platform based on the pre-configuration parameter values ​​carried in the pre-configuration instructions, and generate resource pre-configuration events for each user based on the resource parameter type, user identifier, pre-configuration parameter value, and / or the effective duration of the pre-configuration parameter value.

[0027] Among them, the pre-configured parameter value refers to the specific parameter value of the resource parameter; the configuration personnel can submit parameter pre-configuration instructions for each user based on the pre-configured parameter values ​​of the resource parameters sent by the resource platform; the resource configuration system can be a configuration system that performs parameter pre-configuration for each user.

[0028] Optionally, the resource parameters include the credit limit of the credit resource project created by the resource platform for each user for trading under a specific transaction category; based on this, in the first optional implementation of this embodiment, during the process of pre-configuring the resource parameters of each user on the resource platform, the following operation is performed: the credit limit of each user's credit resource project on the resource platform is marked as increased.

[0029] The specific transaction category here can be an education transaction category, a medical transaction category, a home renovation transaction category, a tourism transaction category, and / or an e-commerce transaction category. In addition, the specific transaction category can also be other types of transaction categories; the credit resource project can be a project that provides credit resources, such as a resource credit project, a credit project, or a resource borrowing project; the credit limit can be a credit line.

[0030] Specifically, in the process of marking an increase in the credit limit of each user in the credit resource project on the resource platform, the credit limit of each user in the credit resource project on the resource platform can be marked for an increase based on the credit limit value and / or credit limit type of each user carried by the parameter pre-configuration instruction submitted by the configuration personnel; where the credit limit value can be a specific credit limit value, and the credit limit type can be a type of credit limit, such as temporary credit limit and / or general credit limit.

[0031] In addition, optionally, the resource parameters include the credit resource pricing of the credit resource projects created by the resource platform for each user for targeted payments; based on this, in the second optional implementation provided in this embodiment, during the process of pre-configuring the resource parameters of each user on the resource platform, the following operation is performed: the credit resource pricing of each user's credit resource projects on the resource platform is marked as reduced.

[0032] Among them, targeted payment can be targeted payment for car purchase, targeted payment for home renovation, targeted payment for medical care, targeted payment for education, and / or targeted payment for daily necessities. In addition, targeted payment can also be other types of targeted payment; credit resource pricing can be fee information for charging users for credit resources, such as credit resource pricing being the interest rate of credit resources.

[0033] Specifically, in the process of marking a price reduction for each user's credit resource project on the resource platform, the price reduction can be marked based on the credit resource pricing type and / or credit resource pricing value carried by the parameter pre-configuration instruction submitted by the configuration personnel. Here, the credit resource pricing value can be the specific pricing value of the credit resource, and the credit resource pricing type can be the type of credit resource pricing, such as temporary resource pricing and / or general resource pricing.

[0034] It should be noted that, in the process of pre-configuring the resource parameters of each user on the resource platform, the first optional implementation method and the second optional implementation method provided above can also be used for parameter pre-configuration.

[0035] During the process of pre-configuring resource parameters for each user on the resource platform, the resource parameters for each user on the resource platform can also be pre-configured based on the user whitelist synchronized by the resource platform. Specifically, the resource parameters for each user on the resource platform in the user whitelist synchronized by the resource platform can be pre-configured according to the pre-generated resource parameter values. The user whitelist can be obtained in the following way: users are filtered by the data system based on user behavior tags sent by the resource platform, and the filtered users are written into the offline data table of the resource platform in the data system. The data system reads the user set from the offline data table and constructs the user whitelist and sends it to the resource platform.

[0036] User behavior tags may include tags that characterize the degree of risk of a user’s behavior, tags that characterize the user’s operation behavior in the resource service on the resource platform, user attribute tags, and / or tags that characterize the user’s registration lifecycle on the resource platform; resource parameter values ​​may be the same as or different from pre-configured parameter values.

[0037] Step S204: Using the user set identifier of the resource platform and the user identifiers of each user extracted from the resource pre-configuration event as system call inputs, the online database of the data system is invoked to perform user matching in the user set corresponding to the user set identifier.

[0038] Here, the user set identifier of the resource platform and the user identifier of each user extracted from the resource pre-configuration event are used as the system call input. The operation of calling the online database of the data system to perform user matching in the user set corresponding to the user set identifier can be replaced by performing resource parameter switching detection of the resource platform on each user according to the resource pre-configuration event.

[0039] The resource pre-configuration events sent by the resource configuration system for each user are generated after pre-configuring the resource parameters for each user. Therefore, the pre-configured resource parameter values ​​may not yet be effective, and the users may not be aware of or using them. In order to improve the accuracy of subsequent resource configuration responses, avoid providing resource configuration responses to users who do not need them, and reduce resource loss on the resource platform, this step performs resource parameter switching detection on each user based on the resource pre-configuration events. This resource parameter switching detection improves the accuracy of subsequent scheduling instructions for each user.

[0040] In practical applications, since the scheduling system performs resource parameter switching detection for batches of users and subsequent resource configuration response processing, the number of processing operations that the scheduling system needs to perform may be large. To improve the efficiency of resource parameter switching detection, the data system is combined with the scheduling system to perform resource parameter switching detection in addition to the processing performed by the scheduling system, thereby improving the detection efficiency. In one optional implementation of this embodiment, during the process of resource parameter switching detection for each user based on the resource pre-configuration event, the user set identifier of the resource platform and the user identifiers of each user extracted from the resource pre-configuration event are used as system call inputs. The online database of the data system is called to perform user matching in the user set corresponding to the user set identifier, and the resource parameter switching detection is determined to be passed after a successful match. Specifically, the resource parameter switching detection can be performed in the following way:

[0041] Extract the user identifier for each user from the resource pre-configuration event;

[0042] The system calls input the user identifier and the user set identifier of the resource platform. The system calls the online database of the data system to perform user matching in the user set corresponding to the user set identifier. After a successful match, the system confirms that the resource parameter switching test has passed.

[0043] Specifically, in the process of matching users in the user set corresponding to the user set identifier, user matching can be performed based on the user identifier in the user set corresponding to the user set identifier; the user set can be stored in the online database of the data system.

[0044] Based on this, in order to improve the comprehensiveness and accuracy of the user set stored in the online database of the data system, the user set can be obtained from the offline data table according to the data loading node, and the obtained user set can be loaded into the online database of the data system; in an optional implementation method provided in this embodiment, the user set is obtained in the following way:

[0045] The data system filters users based on user behavior tags sent by the resource platform, and writes the filtered users into the offline data table of the resource platform in the data system.

[0046] The data system retrieves the user set from the offline data table according to the data loading node, and then loads the retrieved user set into the online database.

[0047] The user behavior tags can include tags representing the degree of risk of a user's behavior, tags representing the user's operational behavior in resource services on the resource platform, user attribute tags, and / or tags representing the user's registration lifecycle on the resource platform. The data loading node can be a data loading time point, or a data loading time point and a bound offline user identifier block. By using the user behavior tags sent by the data system in the offline environment based on the resource platform to screen users, the stability and compliance of user screening can be improved. At the same time, by loading the user set from the offline data table to the online database according to the data loading node in the online environment, the efficiency of subsequent resource parameter switching detection can be improved.

[0048] Furthermore, optionally, the data system generates a user set identifier for the user set of the resource platform in the online database based on the acquired user set. The data loading node obtains the identifier based on the table capacity of the offline data table, the data loading frequency of the data system, and the data write volume of the online database through node parsing. Here, the table capacity of the offline data table can be the storage capacity of the offline data table, the data loading frequency of the data system can be the loading frequency of the data system, the data write volume of the online database can be the write volume of the online database per unit time, such as the data write throughput, and the data loading frequency of the data system can be replaced with the data write frequency of the online database.

[0049] To improve the timeliness of loading user sets from offline data tables to the online database, ensuring timely updates of user sets in the online database and preventing detection errors caused by outdated user sets during resource parameter switching detection in the scheduling system, thus guaranteeing the accuracy of resource parameter switching detection and avoiding interference with other operations of the data system, node parsing can be performed based on the table size of the offline data table, the data loading frequency of the data system, and / or the data write volume of the online database to obtain data loading nodes. User sets are then loaded using these real-time determined data loading nodes. This ensures timely loading of user sets from the offline data table to the online database while minimizing interference with other thread pools in the data system. In one optional implementation of this embodiment, during the node parsing process based on the table size of the offline data table, the data loading frequency of the data system, and the data write volume of the online database, the following operations are performed:

[0050] Data loading verification is performed based on the table capacity and the data write threshold of the online database.

[0051] After the load verification passes, the data loading time is calculated based on the table capacity and the amount of data written, and the data loading node is determined based on the data loading time and the data loading frequency.

[0052] Among them, the data writing threshold of the online database can be the remaining data storage capacity of the online database; the data loading time can be the loading time spent loading the user set in the offline data table into the online database.

[0053] Specifically, during the data loading verification process based on table capacity and online database data write threshold, the current data write threshold can be calculated based on the data write threshold and the reserved write coefficient. If the table capacity is less than or equal to the current data write threshold, the loading verification is considered successful; if the table capacity is greater than the current data write threshold, the loading verification is considered unsuccessful. Furthermore, during the calculation of the current data write threshold based on the data write threshold and the reserved write coefficient, the product of the data write threshold and the reserved write coefficient can be used as the current data write threshold.

[0054] Among them, the reserved write coefficient can be a pre-reserved write coefficient, specifically a security coefficient.

[0055] Based on this, to further improve the accuracy and effectiveness of determining data loading nodes, in the first optional implementation of this embodiment, during the process of determining data loading nodes based on data loading duration and data loading frequency, if the data loading duration is less than or equal to the data loading interval duration corresponding to the data loading frequency of the data system, the data loading nodes are obtained by splitting the loading nodes according to the data loading frequency and the preset loading time point. If the data loading duration is greater than the data loading interval duration corresponding to the data loading frequency of the data system, the data loading time point is determined based on the data loading frequency. The offline data table is then divided to obtain multiple offline user identifier blocks. The data loading nodes are determined based on the data loading time point and the corresponding offline user identifier blocks among the multiple offline user identifier blocks. Specifically, the following method can be used to determine data loading nodes based on data loading duration and data loading frequency:

[0056] Determine whether the data loading time is less than or equal to the data loading interval time corresponding to the data loading frequency of the data system;

[0057] If so, the data loading nodes are obtained by splitting the loading nodes according to the data loading frequency and the preset loading time point.

[0058] Specifically, if the data loading time is less than or equal to the data loading interval, the data loading nodes can be obtained by splitting the loading nodes according to the data loading frequency and the preset loading time point; the data loading interval can be determined based on the data loading frequency; in the process of splitting the loading nodes according to the data loading frequency and the preset loading time point to obtain the data loading nodes, at least one data loading time point after the preset loading time point can be determined according to the data loading frequency, and the preset loading time point and at least one data loading time point can be used as the data loading nodes.

[0059] Furthermore, in an optional implementation of this embodiment, if the result of determining whether the data loading time is less than or equal to the data loading interval time corresponding to the data loading frequency of the data system is negative, the following operation is performed:

[0060] The data loading time point is determined based on the data loading frequency, and the offline data table is segmented to obtain multiple offline user identifier blocks;

[0061] The data loading time point is bound to the corresponding offline user identifier block among multiple offline user identifier blocks, and the data loading time point and the bound offline user identifier block are used as data loading nodes.

[0062] Among them, multiple offline user identifier blocks can be obtained by dividing the user set in the offline data table into multiple offline user identifier blocks. The division can be an average division or a division in descending order of proportion. Each data loading time point can correspond to one or more offline user identifier blocks.

[0063] Specifically, in the process of determining the data loading time point based on the data loading frequency, the data loading nodes can be obtained by splitting the loading nodes according to the data loading frequency and the preset loading time point.

[0064] In the process of detecting resource parameter switching for each user based on the resource pre-configuration event, the status of each user's fund account on the resource platform can be queried based on the user identifier contained in the resource pre-configuration event. If the fund account status is an available account status, the resource parameter switching detection is considered to have passed. All the resource parameter switching detection implementation methods provided above can be executed in combination or independently.

[0065] Step S206: After a successful match, construct the scheduling instruction corresponding to the resource pre-configuration event based on the event type of the resource pre-configuration event to obtain the scheduling instruction sequence for each user.

[0066] Here, after a successful match, the operation of constructing the scheduling instruction corresponding to the resource pre-configuration event based on the event type of the resource pre-configuration event to obtain the scheduling instruction sequence of each user can be replaced by: if the handover detection passes, constructing the scheduling instruction corresponding to the resource pre-configuration event based on the event type of the resource pre-configuration event to obtain the scheduling instruction sequence of each user.

[0067] The above-mentioned resource parameter switching detection for each user based on the resource pre-configuration event is performed. In this step, if the switching detection fails, no action is taken. If the switching detection passes, the scheduling instruction corresponding to the resource pre-configuration event is constructed based on the event type of the resource pre-configuration event, and the scheduling instruction sequence for each user is obtained. In this way, when the resource parameter switching detection passes, scheduling instructions are constructed for each user, improving the effectiveness of scheduling instruction construction. Through the scheduling instructions, resource configuration responses for each user are subsequently implemented, realizing resource marketing for each user.

[0068] The event types of the resource pre-configuration events described in this embodiment may include a credit limit increase event, which increases the credit limit of each user's credit resource project on the resource platform, and / or a pricing decrease event, which decreases the pricing of each user's credit resource project on the resource platform; the scheduling instruction sequence may be a sequence of one or more scheduling instructions.

[0069] In practice, the scheduling instructions for resource configuration responses can be constructed according to the instruction construction strategy corresponding to the event type of the resource pre-configuration event, thus obtaining the scheduling instruction sequence for each user. The scheduling instruction sequence here can correspond to the resource pre-configuration event. The instruction construction strategy can be a construction strategy or construction rule for constructing scheduling instructions. For example, the scheduling instruction sequence for each user generated according to the instruction construction strategy corresponding to the credit limit increase event consists of scheduling instruction 1, scheduling instruction 2, and scheduling instruction 3. Scheduling instruction 1 is the scheduling instruction to issue credit limit benefits on the xx1st day after the effective date of the credit limit increase, scheduling instruction 2 is the scheduling instruction to remind users of the credit limit benefit cancellation on the xx2nd day, and scheduling instruction 3 is the scheduling instruction to remind users of the credit limit benefit expiration on the xx3rd day.

[0070] Optionally, the scheduling instructions in the scheduling instruction sequence include at least one of the following: a scheduling instruction for issuing credit line rights, a scheduling instruction for issuing a credit line rights write-off reminder, a scheduling instruction for issuing a credit line rights expiration reminder, a scheduling instruction for issuing a credit resource pricing reduction reminder, and a scheduling instruction for issuing a credit resource pricing reduction expiration reminder; wherein, the credit line rights may be credit line vouchers.

[0071] In practical applications, the data volume of scheduling instruction sequences for a batch of users can be quite large, falling under the category of big data processing. The scheduling system handles a significant amount of data. To address this, and to improve the scheduling efficiency of the scheduling system in task scheduling, as well as the processing speed of the computer system storing the scheduling instruction sequences, this embodiment provides an optional implementation. After constructing scheduling instructions for resource configuration responses based on the event type of resource pre-configuration events and obtaining the execution of each user's scheduling instruction sequence, the user's scheduling instruction sequence is written to an instruction database on the hard disk. Based on the execution time of each scheduling instruction in the sequence, each scheduling instruction is transferred to a scheduling database in memory. Specifically, after obtaining the scheduling instruction sequence for each user, the following operations can also be performed:

[0072] Write the sequence of scheduling instructions for each user into the instruction database on the hard disk;

[0073] The time difference is calculated based on the execution time of each scheduling instruction in the scheduling instruction sequence and the current time. If the time difference meets the instruction transfer condition, each scheduling instruction is transferred to the scheduling database in memory, and the following step S208 is executed: query the user status based on the target scheduling instruction in the scheduling instruction sequence, and schedule the target scheduling instruction to the resource processing system for resource configuration response processing based on the user status.

[0074] Among them, the time difference can satisfy the instruction transfer condition if the time difference is less than the difference threshold.

[0075] The above-mentioned method writes the scheduling instruction sequence of each user into the instruction database on the hard disk. Then, when the time difference meets the instruction transfer condition, the scheduling instructions are transferred to the scheduling database in memory. Since the data storage cost of the instruction database on the hard disk is low, the scheduling instruction sequence obtained by constructing the scheduling instructions is stored in the instruction database on the hard disk. Since the processing speed of the scheduling database in memory is fast, when the time difference meets the instruction transfer condition, the scheduling instructions are transferred from the instruction database on the hard disk to the scheduling database in memory. This improves the scheduling efficiency of subsequent instruction scheduling, thereby ensuring low data storage cost while improving the scheduling efficiency of instruction scheduling.

[0076] Step S208: Query the user status based on the target scheduling instruction in the scheduling instruction sequence, and schedule the target scheduling instruction to the resource processing system for resource configuration response processing based on the user status.

[0077] The user status described in this embodiment may include each user's resource contract status, credit limit usage status, and / or resource account status. In addition, the user status may also include other types of user status.

[0078] In practice, after the execution time of the target scheduling instruction in the scheduling instruction sequence expires, the corresponding user status can be queried based on the target scheduling instruction. If the user status meets the scheduling conditions, the target scheduling instruction can be scheduled to the resource processing system for resource configuration response processing, so that each user can conduct credit transactions or return credit resources based on the resource parameters after the resource configuration response.

[0079] In the specific execution process, in order to improve the scheduling effectiveness of subsequent instruction scheduling and avoid scheduling instructions that do not need to be scheduled to the resource processing system, a user status verification process is added on the basis of constructing the scheduling instruction sequence for each user only after the above-mentioned resource parameter switching detection has passed. This combines resource parameter switching detection and user status to gradually determine whether to perform instruction scheduling, thereby improving the accuracy of instruction scheduling. In an optional implementation of this embodiment, during the process of querying user status based on the target scheduling instruction in the scheduling instruction sequence, if the target scheduling instruction in the scheduling instruction sequence meets the resource confirmation conditions, the user status category is determined based on the instruction parameters of the target scheduling instruction and / or the event type of the resource pre-configuration event to which it belongs, and the user status of each user is queried according to the user status category. Specifically, the following operations can be performed:

[0080] Check whether the target scheduling instruction in the scheduling instruction sequence meets the resource confirmation conditions;

[0081] If so, determine the user status category based on the instruction parameters of the target scheduling instruction and the event type of the resource pre-configuration event to which it belongs, and query the user status of each user according to the user status category.

[0082] The resource confirmation conditions may include the expiration of the execution time of the target scheduling instruction; the instruction parameters may include the execution stage of the target scheduling instruction, that is, the execution stage of the target scheduling instruction in the scheduling instruction sequence; the user status category may include the user subscription status category and / or the quota usage status category.

[0083] Based on this, in an optional implementation of this embodiment, during the process of querying the user status of each user according to the user status category, the following operation is performed: query the resource platform's contract system according to the user contract status category to query the resource contract status of each user; optionally, the resource contract status includes valid contract status and / or invalid contract status.

[0084] Furthermore, in the first optional implementation provided in this embodiment, during the process of scheduling the target scheduling instruction to the resource processing system for resource configuration response processing based on the user status, if the resource subscription status is a valid subscription status, the target scheduling instruction is scheduled to the first resource processing system. The first resource processing system reads the credit limit benefit obtained from the credit limit increase flag from the target scheduling instruction and distributes it to each user. Specifically, the following operations can be performed:

[0085] If the resource contract status is valid, the target scheduling instruction will be scheduled to the first resource processing system;

[0086] The first resource processing system reads the credit limit benefits obtained from the quota increase flag in the target scheduling instruction and distributes the credit limit benefits to the resource programs of each user.

[0087] Among them, the resource contract status can be the contract status between each user and the resource platform; the credit limit benefits can be the benefits that represent the credit limit value, specifically credit limit coupons.

[0088] After issuing credit limit rights to each user's resource program, at least one scheduling instruction following the target scheduling instruction can be scheduled to the first resource processing system to remind each user of credit limit rights cancellation and / or credit limit rights expiration.

[0089] Based on the above-mentioned pricing reduction marking for credit resource projects of each user on the resource platform, in the first optional implementation of this embodiment, the following operation is performed during the process of querying user status based on target scheduling instructions in the scheduling instruction sequence:

[0090] After the execution time of the target scheduling instruction expires, the credit limit disbursement system of the resource platform is invoked to query the credit limit disbursement status of each user; optionally, the credit limit disbursement status includes the status of unused credit limit and / or the status of used credit limit.

[0091] Furthermore, in the second optional implementation provided in this embodiment, during the process of scheduling the target scheduling instruction to the resource processing system for resource configuration response processing based on the user status, the following operations are performed:

[0092] If the credit limit usage status is "unused", the target scheduling instruction will be scheduled to the second resource processing system.

[0093] The pricing reduction message is extracted from the target scheduling instruction by the second resource processing system, and a pricing reduction reminder is sent to each user based on the pricing reduction message.

[0094] Specifically, pricing reduction notifications can be sent to users via SMS; the SMS channel can be a text message.

[0095] Among them, the credit limit usage status can be the status of each user's credit limit usage.

[0096] After notifying each user of the price reduction based on the price reduction message, at least one scheduling instruction following the target scheduling instruction can be scheduled to the second resource processing system to provide a price reduction failure notification for each user regarding credit resource pricing.

[0097] Based on the above-mentioned transfer of each scheduling instruction to the scheduling database in memory, in the second optional implementation provided in this embodiment, the following operation is performed during the process of querying the user status based on the target scheduling instruction in the scheduling instruction sequence: after the execution time of each scheduling instruction expires, each scheduling instruction is taken as the target scheduling instruction, and the corresponding user status is queried based on the instruction stage to which the target scheduling instruction belongs.

[0098] The instruction phase can be either the position of the target scheduling instruction in the sequence of scheduling instructions, or the resource configuration response phase corresponding to the target scheduling instruction. For example, if the target scheduling instruction is a scheduling instruction for issuing credit line benefits, then the instruction phase is the phase for issuing credit line benefits.

[0099] It should be noted that the user data obtained in this manual, such as user status and user behavior tags, has been authorized by the user and does not involve user privacy.

[0100] It should be added that each optional implementation method and each feasible execution method in steps S202 to S208 provided in this embodiment can be executed independently as needed, or they can be combined and referenced with each other. At the same time, each specific execution step in each optional implementation method or each feasible execution method can also be executed independently or combined as needed. The execution conditions of "if" or "under what circumstances" involved in each step or operation can be directly deleted, and subsequent operations can be executed. This embodiment does not make specific limitations on this.

[0101] It should also be added that, depending on the actual application scenario, step S202 and any of the subsequent steps S204 to S208 can be deleted, or any feature in any step can be deleted. For example, "sent by the resource configuration system" in step S202 can be deleted. The execution order of steps S202 to S208 can also be arbitrary.

[0102] In summary, the one or more resource event processing methods provided in this embodiment can be applied to a scheduling system. First, the resource pre-configuration events of each user sent by the resource configuration system are obtained. The user identifier of each user is extracted from the resource pre-configuration events. The user identifier and the user set identifier of the resource platform are used as input for system calls. The online database of the data system is called to perform user matching in the user set corresponding to the user set identifier. If the matching is successful, the resource parameter switching detection is determined to be passed. In this way, the resource parameter switching detection is realized through the cooperation of the scheduling system and the data system, thereby improving the detection efficiency of resource parameter switching detection. On this basis, if the switching detection is passed, the scheduling instructions corresponding to the resource pre-configuration events are constructed based on the event type of the resource pre-configuration events to obtain the scheduling instruction sequence of each user.

[0103] After the execution time of the target scheduling instruction in the scheduling instruction sequence expires, the resource platform's contract signing system is invoked to query the resource contract status of each user. If the resource contract status is valid, the target scheduling instruction is scheduled to the first resource processing system. The first resource processing system reads the credit limit benefits obtained from the credit limit increase flag in the target scheduling instruction and distributes the credit limit benefits to each user's resource program. Alternatively, after the execution time of the target scheduling instruction in the scheduling instruction sequence expires, the resource platform's credit limit disbursement system is invoked to query the credit limit disbursement status of each user. If the credit limit disbursement status is undisbursed, the target scheduling instruction is scheduled to the second resource processing system. The second resource processing system extracts the pricing reduction message of credit resource pricing from the target scheduling instruction and sends a pricing reduction reminder to each user based on the pricing reduction message. In this way, the scheduling instruction sequence is asynchronously scheduled for each user to complete the distribution of credit limit benefits or pricing reduction reminders for each user. The asynchronous distribution of benefits or pricing reduction reminders is achieved in an automated manner, improving the efficiency of benefit distribution or pricing reduction reminders and meeting the diverse resource needs of each user.

[0104] The following description uses the application of a resource event handling method provided in this embodiment in a scenario of quota increase as an example to further illustrate the resource event handling method provided in this embodiment. See [link to relevant documentation]. Figure 3 The resource event handling method applied to the scenario of quota increase includes the following steps.

[0105] Step S302: Obtain the credit limit pre-increase event sent by the resource configuration system to increase the credit limit of each user.

[0106] Optionally, the pre-adjustment event is generated after marking the credit limit of each user in the credit resource project on the resource platform as increased.

[0107] Step S304: Extract the user identifier of each user from the pre-increase event of the credit limit.

[0108] Step S306: Using the user identifier and the user set identifier of the resource platform as inputs for the system call, the online database of the data system is called to perform user matching in the user set corresponding to the user set identifier, and the quota switching detection is confirmed to be passed after the matching is successful.

[0109] Step S308: Based on the quota pre-increase event, generate a sequence of scheduling instructions for each user to respond to the quota pre-increase.

[0110] The response to a pre-adjustment of the credit limit can be either user confirmation of the pre-adjustment or the adjustment taking effect.

[0111] Step S310: Detect whether the target scheduling instruction in the scheduling instruction sequence meets the resource confirmation conditions;

[0112] If not, no action needs to be taken.

[0113] If so, proceed with steps S312 to S316 below.

[0114] Step S312: Query the resource contract status of each user by calling the contract system of the resource platform according to the user contract status category.

[0115] Step S314: If the resource contract status is a valid contract status, the target scheduling instruction is scheduled to the first resource processing system, and the credit limit benefits obtained by the limit increase flag are read from the target scheduling instruction through the first resource processing system.

[0116] Step S316: Distribute credit limit benefits to each user's resource program.

[0117] It should be noted that any one or more of steps S302 to S316 can be replaced by the corresponding technical means provided in steps S202 to S208 as needed for implementation and deployment. Any one or more of steps S302 to S316 can also be combined into a new implementation method as needed for implementation and deployment. Furthermore, any one or more of steps S302 to S316 can also be combined with one or more of the steps provided in steps S202 to S208 to form a new implementation method, or combined with one or more of the optional implementation methods provided in steps S202 to S208 to form a new implementation method, as needed for actual deployment. These will not be elaborated on here.

[0118] The following description uses the application of a resource event handling method provided in this embodiment in a pricing reduction scenario as an example to further illustrate the resource event handling method provided in this embodiment. (See also...) Figure 4 The resource event handling method applied to pricing reduction scenarios includes the following steps.

[0119] Step S402: Obtain the pricing pre-reduction event sent by the resource allocation system to reduce the credit resource pricing for each user.

[0120] Optionally, the pricing pre-reduction event is generated after the pricing of each user's credit resource project on the resource platform is marked as reduced.

[0121] Step S404: Extract the user identifier of each user from the pricing pre-reduction event.

[0122] Step S406: Using the user identifier and the user set identifier of the resource platform as inputs for the system call, the online database of the data system is called to perform user matching in the user set corresponding to the user set identifier, and the resource pricing switching test is confirmed to be passed after the matching is successful.

[0123] Step S408: Based on the pricing pre-reduction event, generate a sequence of scheduling instructions for each user to respond to the pricing pre-reduction.

[0124] The response to a pre-price reduction can be either user confirmation of the pre-price reduction or the price reduction taking effect.

[0125] Step S410: After the execution time of the target scheduling instruction in the scheduling instruction sequence expires, call the credit limit disbursement system of the resource platform to query the credit limit disbursement status of each user.

[0126] Step S412: If the credit limit usage status is "unused", the target scheduling instruction is scheduled to the second resource processing system.

[0127] Step S414: Extract the pricing reduction message from the target scheduling instruction through the second resource processing system, and send a pricing reduction reminder to each user through the SMS channel based on the pricing reduction message.

[0128] It should be noted that any one or more of steps S402 to S414 can be replaced by the corresponding technical means provided in steps S202 to S208 as needed for implementation and deployment. Any one or more of steps S402 to S414 can also be combined into a new implementation method as needed for implementation and deployment. Furthermore, any one or more of steps S402 to S414 can also be combined with one or more of the steps provided in steps S202 to S208 to form a new implementation method, or combined with one or more optional implementation methods provided in steps S202 to S208 to form a new implementation method, as needed for actual deployment. These will not be elaborated on here.

[0129] This specification provides an embodiment of a resource event handling device as follows:

[0130] In the above embodiments, a resource event processing method is provided, and correspondingly, a resource event processing apparatus is also provided, which will be described below with reference to the accompanying drawings.

[0131] Reference Figure 5 This illustration shows a schematic diagram of an embodiment of a resource event processing device provided in this embodiment.

[0132] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0133] This embodiment provides a resource event processing device that runs in a scheduling system. The device includes:

[0134] The event acquisition module 502 is configured to acquire resource pre-configuration events sent by the resource configuration system for each user; the resource pre-configuration events are generated after the resource parameters of each user on the resource platform are pre-configured.

[0135] The switching detection module 504 is configured to use the user set identifier of the resource platform and the user identifier of each user extracted from the resource pre-configuration event as system call inputs to call the online database of the data system to perform user matching in the user set corresponding to the user set identifier;

[0136] The instruction construction module 506 is configured to, after a successful match, construct the scheduling instruction corresponding to the resource pre-configuration event based on the event type of the resource pre-configuration event, and obtain the scheduling instruction sequence for each user;

[0137] The instruction scheduling module 508 is configured to query the user status based on the target scheduling instruction in the scheduling instruction sequence, and schedule the target scheduling instruction to the resource processing system for resource configuration response processing based on the user status.

[0138] For ease of description, the above devices are described by dividing them into various modules or units based on their functions. Of course, when implementing one or more of these specifications, the functions of each module or unit can be implemented in the same or different software and / or hardware, or a module that performs the same function can be implemented by a combination of multiple sub-modules or sub-units, etc. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0139] The following is an embodiment of a resource event handling device provided in this specification:

[0140] Corresponding to the resource event handling method described above, based on the same technical concept, one or more embodiments of this specification also provide a resource event handling device for executing the resource event handling method provided above. Figure 6 This is a schematic diagram of the structure of a resource event processing device provided for one or more embodiments of this specification.

[0141] This embodiment provides a resource event processing device, including:

[0142] like Figure 6 As shown, device 600 mainly consists of a communication interface 602, a user interface 604, a processor 606, and a data storage 608. These components are interconnected and communicate with each other via a system bus, network, or other connection mechanism 610. The communication interface 602 enables device 600 to communicate with other devices, access networks, and transmission networks via analog or digital modulation. For example, the communication interface 602 may include a chipset and antenna for wireless communication with a radio access network or access point. Furthermore, the communication interface 602 can be a wired interface such as Ethernet, Token Ring, or a USB port, or a wireless interface such as Wi-Fi, Bluetooth, Global Positioning System (GPS), or a wide-area wireless interface (e.g., WiMAX or LTE). Of course, the communication interface 602 can also support other forms of physical layer interfaces and standard or proprietary communication protocols. The communication interface 602 may also include multiple physical communication interfaces, such as Wi-Fi, Bluetooth, and wide-area wireless interfaces. The user interface 604 includes receiving user input and providing output to the user. Therefore, user interface 604 may include input components such as a keypad, keyboard, touch-sensitive or presence-sensitive panel, computer mouse, trackball, joystick, microphone, still camera, and video camera, and output components such as a display screen (which may be combined with a touch-sensitive panel), CRT, LCD, LED, display using DLP technology, printer, and other similar devices known or developed in the future. User interface 604 may also generate auditory output via speakers, speaker jacks, audio output ports, audio output devices, headphones, and other similar devices known or developed in the future. In some embodiments, user interface 604 may include software, circuitry, or other forms of logic capable of transmitting and receiving data from external user input / output devices. Additionally or alternatively, device 600 may support remote access from other devices via communication interface 602 or another physical interface (not shown). User interface 604 may be configured to receive user input, the position and movement of which may be indicated by indicators or cursors described herein. User interface 604 may also be configured as a display device for rendering or displaying text fragments.

[0143] Processor 606 may include one or more general-purpose processors and / or special-purpose processors. Data storage 608 may include one or more volatile and / or non-volatile storage components and may be integrated wholly or partially with processor 606. Data storage 608 may include removable and non-removable components.

[0144] Processor 606 is capable of executing program instructions 618 (e.g., compiled or uncompiled program logic and / or machine code) stored in data storage 608 to perform the various functions described herein. Data storage 608 may comprise a non-transitory computer-readable medium on which program instructions are stored, which, when executed by device 600, enable device 600 to perform any methods, processes, or functions disclosed in this specification and / or the accompanying drawings. Execution of program instructions 618 by processor 606 may result in processor 606 using data 612. For example, program instructions 618 may include an operating system 622 (e.g., an operating system kernel, device drivers, and / or other modules) installed on device 600 and one or more application programs 620 (e.g., a browser, social application, or game application). Similarly, data 612 may include operating system data 616 and application data 614. Operating system data 616 is primarily accessible to operating system 622, while application data 614 is primarily accessible to one or more application programs 620. Application data 614 may reside in a file system visible or hidden from the user of device 600. Application 620 can communicate with operating system 622 through one or more application programming interfaces (APIs). These APIs facilitate application 620 in reading and / or writing application data 614, transmitting or receiving information via communication interface 602, and receiving or displaying information on user interface 604. In some terms, application 620 may be simply referred to as "app". Furthermore, application 620 can be downloaded to device 600 through one or more online app stores or app markets. However, applications can also be installed on device 600 in other ways, such as through a web browser or a physical interface on device 600 (e.g., a USB port).

[0145] In one specific embodiment, the resource event processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the resource event processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0146] The system acquires resource pre-configuration events for each user sent by the resource configuration system; these resource pre-configuration events are generated after the resource parameters for each user on the resource platform are pre-configured.

[0147] Using the user set identifier of the resource platform and the user identifier of each user extracted from the resource pre-configuration event as the system call input, the online database of the data system is invoked to perform user matching in the user set corresponding to the user set identifier;

[0148] After a successful match, the scheduling instructions corresponding to the resource pre-configuration event are constructed based on the event type of the resource pre-configuration event to obtain the scheduling instruction sequence for each user;

[0149] Based on the target scheduling instruction in the scheduling instruction sequence, query the user status, and based on the user status, schedule the target scheduling instruction to the resource processing system for resource configuration response processing.

[0150] This specification provides an embodiment of a computer-readable storage medium as follows:

[0151] Corresponding to the resource event handling method described above, and based on the same technical concept, one or more embodiments of this specification also provide a computer-readable storage medium.

[0152] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, perform the following steps:

[0153] The system acquires resource pre-configuration events for each user sent by the resource configuration system; these resource pre-configuration events are generated after the resource parameters for each user on the resource platform are pre-configured.

[0154] Using the user set identifier of the resource platform and the user identifier of each user extracted from the resource pre-configuration event as the system call input, the online database of the data system is invoked to perform user matching in the user set corresponding to the user set identifier;

[0155] After a successful match, the scheduling instructions corresponding to the resource pre-configuration event are constructed based on the event type of the resource pre-configuration event to obtain the scheduling instruction sequence for each user;

[0156] Based on the target scheduling instruction in the scheduling instruction sequence, query the user status, and based on the user status, schedule the target scheduling instruction to the resource processing system for resource configuration response processing.

[0157] It should be noted that the embodiments of a computer-readable storage medium described in this specification and the embodiments of a resource event handling method described in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0158] This specification provides an example of a computer program product as follows:

[0159] Corresponding to the resource event handling method described above, based on the same technical concept, one or more embodiments of this specification also provide a computer program product.

[0160] A computer program product includes a computer program / instructions that, when executed by a processor, perform the following steps:

[0161] The system acquires resource pre-configuration events for each user sent by the resource configuration system; these resource pre-configuration events are generated after the resource parameters for each user on the resource platform are pre-configured.

[0162] Using the user set identifier of the resource platform and the user identifier of each user extracted from the resource pre-configuration event as the system call input, the online database of the data system is invoked to perform user matching in the user set corresponding to the user set identifier;

[0163] After a successful match, the scheduling instructions corresponding to the resource pre-configuration event are constructed based on the event type of the resource pre-configuration event to obtain the scheduling instruction sequence for each user;

[0164] Based on the target scheduling instruction in the scheduling instruction sequence, query the user status, and based on the user status, schedule the target scheduling instruction to the resource processing system for resource configuration response processing.

[0165] It should be noted that the embodiments of a computer program product described in this specification and the embodiments of a resource event handling method described in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0166] The various embodiments in this specification are described in a progressive manner. The same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on describing the differences from other embodiments. For example, the device embodiment, equipment embodiment and computer-readable storage medium embodiment are all similar to the method embodiment, so the description is relatively simple. When reading the relevant content of the device embodiment, equipment embodiment and computer-readable storage medium embodiment, please refer to the description of the method embodiment.

[0167] Although one or more embodiments of this specification provide method steps as described in the embodiments or flowcharts, it is understood that the order of steps listed in the embodiments or flowcharts is only one of many possible execution orders and does not represent the only execution order. Therefore, when the claims involve method steps, any changes or adjustments to the order of such steps, or the parallelism between steps, are also within the scope of protection of the claims.

[0168] This specification uses specific terms to describe embodiments thereof. Terms such as "an embodiment," "one embodiment," and / or "some embodiments" refer to a particular feature, structure, or characteristic associated with at least one embodiment of this specification. Therefore, it should be emphasized and noted that references to "an embodiment," "one embodiment," or "an alternative embodiment" in different locations throughout this specification do not necessarily refer to the same embodiment. Furthermore, those skilled in the art can combine and integrate the different embodiments or examples described herein, as well as the features of those different embodiments or examples, without contradiction.

[0169] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0170] In the 1930s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many improvements to the methodology today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that an improvement to the methodology cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program and "integrate" a digital system onto a PLD themselves, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must also be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0171] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0172] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0173] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.

[0174] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0175] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable test processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable test processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0176] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable test processing equipment to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0177] These computer program instructions can also be loaded onto a computer or other programmable test processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0178] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0179] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0180] Computer-readable media include both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0181] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of features includes not only those features but also other features not expressly listed, or features inherent to such process, method, article, or apparatus. Without further limitations, a feature defined by the phrase "comprising one..." does not exclude the presence of other identical features in the process, method, article, or apparatus that includes said feature.

[0182] One or more embodiments of this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. One or more embodiments of this specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0183] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0184] The above description is merely an embodiment of this document and is not intended to limit the scope of this document. Various modifications and variations can be made to this document by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this document should be included within the scope of the claims of this document.

Claims

1. A resource event handling method, characterized in that, Applied to a scheduling system, the method includes: The system acquires resource pre-configuration events for each user sent by the resource configuration system; these resource pre-configuration events are generated after pre-configuring the credit resource parameters of each user's credit resource project on the credit granting platform. Using the user set identifier of the credit granting platform and the user identifiers of each user extracted from the resource pre-configuration event as system call inputs, the online database of the data system is invoked to perform user matching in the user set corresponding to the user set identifier; the user set is filtered by the data system in an offline environment based on the user behavior tags sent by the credit granting platform, and the filtered users are written into the offline data table of the credit granting platform in the data system; in an online environment, the data system retrieves the data from the offline data table according to the data loading node and loads it into the online database; After a successful match, the scheduling instructions corresponding to the resource pre-configuration event are constructed based on the event type of the resource pre-configuration event to obtain the scheduling instruction sequence for each user; Based on the target scheduling instruction in the scheduling instruction sequence, the user status is queried, and based on the user status, the target scheduling instruction is scheduled to the resource processing system for resource configuration response processing, so that each user can conduct credit transactions based on the credit resource parameters after the resource configuration response.

2. The resource event handling method according to claim 1, characterized in that, The data system generates a user set identifier for the user set of the credit granting platform in the online database based on the user set. The data loading node is obtained by parsing the table size of the offline data table, the data loading frequency of the data system, and the data writing volume of the online database.

3. The resource event handling method according to claim 1, characterized in that, The credit resource parameters of the credit resource project include the credit limit of the credit resource project created by the credit granting platform for each user for transactions under a specific transaction category; The step of pre-configuring the credit resource parameters of each user's credit resource project on the credit granting platform includes: marking an increase in the credit limit of each user's credit resource project on the credit granting platform.

4. The resource event handling method according to claim 3, characterized in that, The step of querying the user status based on the target scheduling instruction in the scheduling instruction sequence includes: Detect whether the target scheduling instruction in the scheduling instruction sequence meets the resource confirmation conditions; If so, the user status category is determined based on the instruction parameters of the target scheduling instruction and the event type of the resource pre-configuration event to which it belongs, and the user status of each user is queried according to the user status category.

5. The resource event handling method according to claim 4, characterized in that, The step of querying the user status of each user according to the user status category includes: The system of the credit granting platform is invoked to query the resource contract status of each user according to the user's contract status category; The step of scheduling the target scheduling instruction to the resource processing system for resource configuration response processing based on the user status includes: If the resource contract status is a valid contract status, the target scheduling instruction will be scheduled to the first resource processing system; The first resource processing system reads the credit limit benefit obtained by the limit increase flag from the target scheduling instruction and distributes the credit limit benefit to the resource program of each user.

6. The resource event handling method according to claim 1, characterized in that, The credit resource parameters of the credit resource project include the credit resource pricing of the credit resource project created by the credit granting platform for each user for targeted payment; The step of pre-configuring the credit resource parameters of each user's credit resource project on the credit granting platform includes: marking a price reduction for the credit resource pricing of each user's credit resource project on the credit granting platform.

7. The resource event handling method according to claim 6, characterized in that, The step of querying the user status based on the target scheduling instruction in the scheduling instruction sequence includes: After the execution time of the target scheduling instruction expires, the credit limit disbursement system of the credit granting platform is invoked to query the credit limit disbursement status of each user. The step of scheduling the target scheduling instruction to the resource processing system for resource configuration response processing based on the user status includes: If the credit limit usage status is unused, the target scheduling instruction will be scheduled to the second resource processing system. The second resource processing system extracts the pricing reduction message from the target scheduling instruction and sends a pricing reduction reminder to each user based on the pricing reduction message.

8. The resource event handling method according to claim 1, characterized in that, The scheduling instructions in the scheduling instruction sequence include at least one of the following: Dispatch instructions for issuing credit line rights, dispatch instructions for reminding credit line rights to be revoked, dispatch instructions for reminding credit line rights to expire, dispatch instructions for reminding credit resource pricing to be adjusted downwards, and dispatch instructions for reminding credit resource pricing to expire downwards.

9. The resource event handling method according to claim 2, characterized in that, The node parsing based on the table size of the offline data table, the data loading frequency of the data system, and the data write volume of the online database includes: Data loading verification is performed based on the table capacity and the data write threshold of the online database; After the loading verification is passed, the data loading time is calculated based on the table capacity and the amount of data written, and the data loading node is determined based on the data loading time and the data loading frequency.

10. The resource event handling method according to claim 9, characterized in that, Determining the data loading node based on the data loading duration and the data loading frequency includes: Determine whether the data loading time is less than or equal to the data loading interval time corresponding to the data loading frequency of the data system; If so, the data loading nodes are split according to the data loading frequency and the preset loading time point to obtain the data loading nodes.

11. The resource event handling method according to claim 10, characterized in that, If the result of the operation to determine whether the data loading time is less than or equal to the data loading interval time corresponding to the data loading frequency of the data system is negative, the following operation is performed: The data loading time point is determined based on the data loading frequency, and the offline data table is segmented to obtain multiple offline user identifier blocks; The data loading time point is bound to the corresponding offline user identifier block among the plurality of offline user identifier blocks, and the data loading time point and the bound offline user identifier block are used as the data loading node.

12. The resource event handling method according to claim 1, characterized in that, After constructing the scheduling instruction corresponding to the resource pre-configuration event based on the event type of the resource pre-configuration event, and executing the scheduling instruction sequence operation for each user, and before executing the operation to query the user status based on the target scheduling instruction in the scheduling instruction sequence, the method further includes: Write the scheduling instruction sequence of each user into the instruction database on the hard disk; The time difference is calculated based on the execution time of each scheduling instruction in the scheduling instruction sequence and the current time. If the time difference meets the instruction transfer condition, each scheduling instruction is transferred to the scheduling database in memory, and the user status query operation based on the target scheduling instruction in the scheduling instruction sequence is executed.

13. The resource event handling method according to claim 12, characterized in that, The step of querying the user status based on the target scheduling instruction in the scheduling instruction sequence includes: After the execution time of each scheduling instruction expires, each scheduling instruction is taken as the target scheduling instruction, and the corresponding user status is queried based on the instruction stage to which the target scheduling instruction belongs.

14. A resource event processing device, characterized in that, Operating in a scheduling system, the device includes: The event acquisition module is configured to acquire resource pre-configuration events for each user sent by the resource configuration system; the resource pre-configuration events are generated after the credit resource parameters of each user's credit resource project on the credit granting platform are pre-configured. The switching detection module is configured to use the user set identifier of the credit granting platform and the user identifiers of each user extracted from the resource pre-configuration event as system call inputs to call the online database of the data system to perform user matching in the user set corresponding to the user set identifier; the user set is filtered by the data system in an offline environment based on user behavior tags sent by the credit granting platform, and the filtered users are written into the offline data table of the credit granting platform in the data system; in an online environment, the data system retrieves the data from the offline data table according to the data loading node and loads it into the online database; The instruction construction module is configured to, after a successful match, construct the scheduling instruction corresponding to the resource pre-configuration event based on the event type of the resource pre-configuration event, and obtain the scheduling instruction sequence for each user; The instruction scheduling module is configured to query the user status based on the target scheduling instruction in the scheduling instruction sequence, and schedule the target scheduling instruction to the resource processing system for resource configuration response processing based on the user status, so that each user can conduct credit transactions based on the credit resource parameters after the resource configuration response.

15. A resource event processing device, characterized in that, The device includes: A processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: The system acquires resource pre-configuration events for each user sent by the resource configuration system; these resource pre-configuration events are generated after pre-configuring the credit resource parameters of each user's credit resource project on the credit granting platform. Using the user set identifier of the credit granting platform and the user identifiers of each user extracted from the resource pre-configuration event as system call inputs, the online database of the data system is invoked to perform user matching in the user set corresponding to the user set identifier; the user set is filtered by the data system in an offline environment based on the user behavior tags sent by the credit granting platform, and the filtered users are written into the offline data table of the credit granting platform in the data system; in an online environment, the data system retrieves the data from the offline data table according to the data loading node and loads it into the online database; After a successful match, the scheduling instructions corresponding to the resource pre-configuration event are constructed based on the event type of the resource pre-configuration event to obtain the scheduling instruction sequence for each user; Based on the target scheduling instruction in the scheduling instruction sequence, the user status is queried, and based on the user status, the target scheduling instruction is scheduled to the resource processing system for resource configuration response processing, so that each user can conduct credit transactions based on the credit resource parameters after the resource configuration response.

16. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store computer-executable instructions that, when executed, implement the steps of the method of claim 1.

Images