Marketing activity execution method and device, equipment and storage medium

Abstract

The invention discloses a marketing activity execution method and device, equipment and a storage medium, which are applied to the field of software development, and the method comprises the steps: constructing a multi-way tree comprising a root node layer, an event node layer and an event condition node layer; constructing a double linked list containing marketing event condition nodes based on the event condition logic relationship of the marketing activities; traversing in the multi-way tree based on the reported event, and matching from the event condition nodes to obtain a target event condition node; and determining the double linked list containing the target event condition node as a target double linked list, performing traversal trigger verification on a forward node and a backward node of the target event condition node in the target double linked list, and executing a marketing activity of the target double linked list based on a trigger verification result. According to the method and the system, the marketing activities are decoupled from each business platform, so that the unified configuration, management and maintenance of the marketing activities are realized, and the problems of high platform development cost, long period and difficulty in management and maintenance caused by tight coupling of the marketing activities and business systems are avoided.

Description

Technical Field

[0001] The present invention relates to the field of software development, and in particular to a marketing activity execution method, device, equipment and computer-readable storage medium. Background Art

[0002] With the rapid development of the consumer finance industry, the company's marketing activities have gradually become more diverse. Marketing activities are spread throughout various business process nodes. Marketing activities are often closely coupled with core business processes (credit, borrowing, repayment, increase in credit limit, etc.), which will have a certain impact on core business processes; and the formulation of marketing activities often has fine-grained trigger conditions, so the execution of marketing activities often involves a series of changes to the corresponding business systems, resulting in large R&D investment and long demand scheduling time; marketing activities require different business systems to undertake, and the dispersion of marketing activities will make it extremely difficult to maintain. Summary of the invention

[0003] The purpose of the present invention is to provide a marketing activity execution method, device, equipment and computer-readable storage medium, which are applied to the field of software development. The method decouples marketing activities from various business platforms to achieve unified configuration, management and maintenance of marketing activities, thereby avoiding the problems of high platform development costs, long cycles, and difficult management and maintenance caused by the close coupling of marketing activities with business systems.

[0004] In order to solve the above technical problems, the present invention provides a marketing activity execution method, comprising:

[0005] Based on business events and business event conditions, a multi-branch tree including a root node layer, an event node layer and an event condition node layer is constructed from top to bottom;

[0006] Selecting a marketing event condition node for configuring a marketing condition from the event condition nodes in the event condition node layer;

[0007] Constructing a bidirectional linked list including the marketing event condition nodes based on the event condition logical relationship of the marketing condition;

[0008] When receiving a reported event sent by the business system, traversing the multi-branch tree based on the reported event, and matching the target event condition node from the event condition nodes;

[0009] The bidirectional linked list including the target event condition node is determined as the target bidirectional linked list, a traversal trigger check is performed on the forward node and the backward node of the target event condition node in the target bidirectional linked list, and a marketing activity of the target bidirectional linked list is executed based on the trigger check result.

[0010] Optionally, the event condition logical relationship based on the marketing condition is used to construct a bidirectional linked list containing the marketing event condition nodes, including:

[0011] When the event condition logical relationship of the marketing condition is OR, each marketing event condition node is stored as an OR bidirectional linked list;

[0012] When the event condition logical relationship of the marketing condition is and, all the marketing event condition nodes are stored as an and bidirectional linked list, and adjacent bidirectional linked list nodes in the and bidirectional linked list are bidirectionally connected through a predecessor pointer and a successor pointer;

[0013] When the event condition logical relationship of the marketing condition is a sequence, all the marketing event condition nodes are stored in a sequence bidirectional linked list in sequence order, and adjacent bidirectional linked list nodes in the sequence bidirectional linked list are unidirectionally connected through the predecessor pointer.

[0014] Optionally, the traversing trigger verification of the forward node and the backward node of the target event condition node in the target bidirectional linked list, and executing the marketing activity of the target bidirectional linked list based on the trigger verification result, includes:

[0015] Constructing an event record table of each of the bidirectional linked lists, generating an event record of each of the target event condition nodes, and storing the event record in the event record table;

[0016] When the target doubly linked list is the or doubly linked list, executing the marketing activity of the or doubly linked list;

[0017] When the target doubly linked list is the and doubly linked list, traverse the forward nodes and backward nodes of the target event condition node in the and doubly linked list, and when the event records of all the forward nodes and the backward nodes exist in the event record table of the and doubly linked list, execute the marketing activity of the and doubly linked list;

[0018] When the target doubly linked list is the sequence doubly linked list, if the target event condition node is the tail node of the sequence doubly linked list, traverse the forward node of the target event condition node in the sequence doubly linked list, and when the event records of all the forward nodes exist in the event record table of the sequence doubly linked list, and the event records are stored in the sequence order, execute the marketing activity of the sequence doubly linked list.

[0019] Optionally, the method further includes:

[0020] Setting a status flag of the event record in the event record table; the status flag includes an available status and an invalid status;

[0021] When the event record is stored in the event record table, setting the status flag of the event record to an available state;

[0022] When the event record is used to trigger the marketing activity, setting the status flag of the event record to an invalid state;

[0023] The event record with the status flag as the invalid state is cleared from the event record table.

[0024] Optionally, when the target doubly linked list is the or doubly linked list, executing the marketing activity of the or doubly linked list includes:

[0025] When the target doubly linked list is the or doubly linked list, determining the target marketing condition to which the or doubly linked list belongs;

[0026] If the marketing activity of the target marketing condition is not executed, then executing the marketing activity of the or bidirectional linked list;

[0027] If the marketing activity of the target marketing condition has been executed, the marketing activity of the or bidirectional linked list is intercepted.

[0028] Optionally, the constructing of a multi-branch tree including a root node layer, an event node layer and an event condition node layer from top to bottom based on the business event and the business event condition includes:

[0029] Constructing the business event condition of each business event based on the attributes of the business event;

[0030] Constructing the multi-branch tree including the root node layer, the event node layer and the event condition node layer from top to bottom, storing the business events in the event nodes in the event node layer, and storing the business event conditions in the event condition nodes in the event condition node layer;

[0031] A regular expression of each of the event nodes and the event condition nodes is constructed based on the business event and the business event condition.

[0032] Accordingly, when a reported event sent by the business system is received, the multitree is traversed based on the reported event, and a target event condition node is matched from the event condition nodes, including:

[0033] When receiving the reported event sent by the business system, determining a target event node matching the reported event based on the rule expression of the event node;

[0034] A target event condition node matching the reported event is determined based on a regular expression of the event condition node under the target event node.

[0035] Optionally, the business events include: registration, login, card binding, real-name authentication, credit granting, borrowing, repayment and credit limit increase.

[0036] In order to solve the above technical problems, the present invention provides a marketing activity execution device, comprising:

[0037] The first module is used to construct a multi-branch tree including a root node layer, an event node layer and an event condition node layer from top to bottom based on business events and business event conditions;

[0038] A second module is used to select a marketing event condition node for configuring a marketing condition from the event condition nodes in the event condition node layer;

[0039] The third module is used to construct a bidirectional linked list containing the marketing event condition nodes based on the event condition logical relationship of the marketing condition;

[0040] A fourth module is used for, when receiving a reporting event sent by a business system, traversing the multi-branch tree based on the reporting event, and matching a target event condition node from the event condition nodes;

[0041] The fifth module is used to determine the bidirectional linked list containing the target event condition node as the target bidirectional linked list, perform traversal trigger verification on the forward node and the backward node of the target event condition node in the target bidirectional linked list, and execute the marketing activities of the target bidirectional linked list based on the trigger verification result.

[0042] In order to solve the above technical problems, the present invention provides a marketing activity execution device, comprising:

[0043] Memory, for storing computer programs;

[0044] A processor is used to implement the above-mentioned marketing activity execution method when executing the computer program.

[0045] In order to solve the above technical problems, the present invention provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, the above-mentioned marketing activity execution method is implemented.

[0046] It can be seen that the method of the present invention constructs a multi-branch tree including a root node layer, an event node layer and an event condition node layer from top to bottom based on business events and business event conditions; selects a marketing event condition node for configuring marketing conditions from the event condition nodes in the event condition node layer; constructs a bidirectional linked list including marketing event condition nodes based on the event condition logical relationship of the marketing conditions; when receiving a reported event sent by the business system, traverses the multi-branch tree based on the reported event, and matches the target event condition node from the event condition node; determines the bidirectional linked list including the target event condition node as the target bidirectional linked list, performs traversal trigger verification on the forward node and the backward node of the target event condition node in the target bidirectional linked list, and executes the marketing activities of the target bidirectional linked list based on the trigger verification result. By decoupling the marketing conditions from each business platform, the unified configuration, management and maintenance of the marketing conditions are realized, avoiding the problems of high platform development cost, long cycle, and difficult management and maintenance caused by the tight coupling of marketing conditions with the business system. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0048] Figure 1 A flowchart of a marketing activity execution method provided by an embodiment of the present invention;

[0049] Figure 2 An example diagram of a multi-branch tree provided by an embodiment of the present invention;

[0050] Figure 3 An example of a bidirectional link table provided by an embodiment of the present invention;

[0051] Figure 4 This is a structural block diagram of a marketing activity execution device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0052] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0053] With the rapid development of the consumer finance industry, the company's marketing activities have gradually become richer. Marketing activities are spread throughout various business process nodes, such as credit granting, borrowing, card binding, repayment, real-name authentication, credit limit increase, registration, login, etc.; in the existing marketing campaign formulation, users often trigger certain behavior nodes, which will trigger a series of marketing actions, such as sending interest-free coupons for successful registration, issuing interest-free coupons for successful credit limit increase, and sending SMS loan reminders after real-name authentication, etc.

[0054] Marketing activities are often closely coupled with core business processes (credit granting, borrowing, repayment, credit limit increase, etc.). For example, coupons are sent when credit is successfully granted, and text message reminders are sent when credit limit is successfully increased. The increasing number of marketing activities will have a certain impact on core business processes. The formulation of marketing activities often has fine-grained trigger conditions. For example, borrowing more than 10,000 triggers the issuance of interest-free coupons, borrowing 50,000 triggers the issuance of interest-free coupons, increasing credit limit to 100,000 triggers outbound call reminders, and increasing credit limit to 20,000 triggers text message reminders. Therefore, the execution of marketing activities often involves a series of changes to the corresponding business systems, resulting in large R&D investment and long demand scheduling time. Marketing activities require different business systems to undertake, and the dispersion of marketing activities will make it extremely difficult to maintain.

[0055] The present invention aims to get rid of the influence of various business systems on marketing activities and reduce the development cycle of marketing activities. Through configuration, the release and execution of marketing activities can be realized, which is decoupled from various business systems and executed as a side link to avoid the influence on core business processes and uniformly manage and maintain all marketing activities.

[0056] The following combination Figure 1 , Figure 1 A flowchart of a marketing activity execution method provided by an embodiment of the present invention, the method may include:

[0057] S101: constructing a multi-branch tree including a root node layer, an event node layer and an event condition node layer from top to bottom based on business events and business event conditions.

[0058] This embodiment does not limit the execution subject of the marketing activity execution method, which can be specifically set based on actual applications and can generally be a server.

[0059] Marketing activities are spread throughout various business process nodes, and the execution of marketing activities depends on the node data of various systems of the company, such as the login, registration, real-name authentication, and card binding process node data of the middle office system, the credit approval, increase, and adjustment process node data of the risk control system, and the borrowing and repayment process node data of the accounting system. This embodiment can abstract the process node data of all business systems into a series of business events.

[0060] This embodiment can construct a multi-branch tree including a root node layer, an event node layer and an event condition node layer from top to bottom based on business events and business event conditions. This embodiment does not limit the specific type of business events, and can generally be business events related to financial events, such as registration, login, card binding, real-name authentication, credit, borrowing, repayment and increase in credit limit, etc.

[0061] The business event condition in this embodiment may be a limiting condition of a business event. The business event condition generally includes four elements: an event, an attribute, an attribute value, and an operator.

[0062] This embodiment does not limit the specific method of setting the business event conditions. Generally, the business event conditions of each business event can be constructed based on the attributes of the business event. For example, when the business event is a repayment event, the repayment event conditions of the repayment event can be set based on the repayment attributes such as time and amount. The specific repayment event conditions also need to include specific attribute values, such as timestamp and amount value. That is, the repayment event conditions can be set to "repayment amount is greater than 10,000" and "repayment time is less than xx / xx / xx".

[0063] The same attribute can be used to set multiple business event conditions. For example, the repayment event condition can also be set to "repayment amount is greater than 20,000" and "repayment amount is greater than 30,000". The attributes of each business event can be shown in Table 1:

[0064] Table 1: Business event attribute table

[0065]

[0066] This embodiment can construct a multi-branch tree including a root node layer, an event node layer and an event condition node layer from top to bottom, store business events in event nodes in the event node layer, and store business event conditions in event condition nodes in the event condition node layer.

[0067] Furthermore, this embodiment can construct regular expressions for each event node and event condition node based on business events and business event conditions, that is, convert the data stored in the multi-branch tree nodes into the form of regular expressions, that is, encode business events and business event conditions according to preset rules.

[0068] This embodiment does not limit the specific method of generating the regular expression. Generally, the regular expression, that is, the MVEL expression, can be generated by performing data conversion through the MVEL syntax. MVEL is an expression language based on the Java programming language.

[0069] In this embodiment, for the convenience of representation, the nodes in the multi-branch tree can be numbered. Specifically, the root node in the root node layer can be represented by ER; the event nodes in the event node layer can be represented by EN, such as registration (EN1), login (EN2), card binding (EN3), real-name authentication (EN4), credit (EN5), loan (EN6), repayment (EN7) and increase (EN8); the event nodes in the event node layer can be represented by CN. This embodiment does not limit the number of event condition nodes connected to each event node, which can be configured based on actual applications.

[0070] In this embodiment, the rule expression of the business event can be preset and generated, and the specific format can be eventCode (event code) = `event name`, such as the rule expression of the loan event can be eventCode = `loanSubmit`.

[0071] The rule expression of business events can be generated by operators through the configuration page. Operators can select business events in the configuration interface, select the attributes corresponding to the business events, and further select operators supported by the current attributes. For example, when the attribute is numeric, the operators may include greater than, less than, greater than or equal to, less than or equal to, and equal to, etc. When the attribute is string type, the operators may include equal to, not equal to, contain, not contain, has value, and has no value, etc.

[0072] The specific format of the rule expression of a business event can be eventCode=`event name` && (attribute name) (operator) (attribute value), where && is a logical AND.

[0073] Taking the loan event as an example, the loan event condition "the loan amount is greater than 10,000" is used as an example. The rule expression of the event condition can be eventCode=`loanSubmit` && amt >10000.

[0074] For example of the rule expression of specific business event conditions, see Table 2. The number of multi-branch trees constructed based on Table 2 can be as follows: Figure 2 shown.

[0075] Table 2: Regular expression examples

[0076]

[0077] S102: Selecting a marketing event condition node for configuring a marketing condition from the event condition nodes in the event condition node layer.

[0078] S103: Construct a bidirectional linked list containing marketing event condition nodes based on the event condition logical relationship of the marketing conditions.

[0079] This embodiment can select a marketing event condition node for configuring a marketing condition from the event condition nodes in the event condition node layer, and construct a bidirectional linked list including the marketing event condition nodes based on the event condition logical relationship of the marketing condition.

[0080] The marketing conditions in this embodiment can be configured by operation and maintenance personnel on the configuration platform. Marketing personnel can select configured business event conditions to construct marketing conditions. This embodiment does not limit the number of marketing conditions that can be constructed, nor does it limit the number of business event conditions contained in each marketing condition.

[0081] In this embodiment, the event condition logical relationship of the marketing conditions can generally include OR logic, AND logic and sequence logic. Each marketing condition can be bound to a corresponding marketing activity. When the event condition logical relationship of the marketing conditions is OR logic, only one or more marketing event conditions in the marketing conditions need to be triggered before the corresponding marketing activity can be executed; when the event condition logical relationship of the marketing conditions is AND logic, all marketing event conditions in the marketing conditions need to be triggered before the corresponding marketing activity can be executed; when the event condition logical relationship of the marketing conditions is sequence logic, the marketing event conditions in the marketing conditions need to be triggered in sequence order before the corresponding marketing activity can be executed.

[0082] A doubly linked list is a linked data structure in which each node contains three parts: a data field, a pointer to the previous node, and a pointer to the next node. This structure allows the entire linked list to be traversed forward or backward starting from any node.

[0083] This embodiment can construct a bidirectional linked list containing marketing event condition nodes based on the event condition logical relationship of the marketing conditions. Each linked list node includes a forward node, a backward node, an event condition node, and a head and tail identifier. The predecessor pointer points to the forward node, and the successor pointer points to the backward node.

[0084] Specifically, in this embodiment, when the event condition logical relationship of the marketing condition is or, each marketing event condition node can be stored as an or bidirectional linked list, that is, the marketing condition can construct multiple independent bidirectional linked lists, and each node of the bidirectional linked list stores a marketing event condition node, and there are no forward nodes and backward nodes.

[0085] When the event condition logic relationship of the marketing condition is and, all the marketing event condition nodes are stored as an and bidirectional linked list, and the adjacent bidirectional linked list nodes in the bidirectional linked list are bidirectionally connected through the predecessor pointer and the successor pointer. Since the event condition logic relationship of the marketing condition is and, all the marketing event conditions in the marketing condition are triggered, the corresponding marketing activities can be executed without considering the triggering order of the marketing event conditions, so the marketing event condition nodes can be stored as a bidirectional linked list in any order.

[0086] When the event condition logic relationship of the marketing condition is a sequence, all the marketing event condition nodes are stored in a sequence bidirectional linked list in sequence order, and the adjacent bidirectional linked list nodes in the sequence bidirectional linked list are unidirectionally connected through the predecessor pointer. Since when the event condition logic relationship of the marketing condition is a sequence logic, the marketing event conditions in the marketing condition need to be triggered in sequence order so that the corresponding marketing activities can be executed, so the marketing event condition nodes need to be stored in a bidirectional linked list in sequence order. Specifically, the starting node in the sequence can be stored in the first node of the bidirectional linked list, and the ending node can be stored in the tail node of the bidirectional linked list. The adjacent bidirectional linked list nodes are unidirectionally connected through the predecessor pointer.

[0087] In a specific example, Figure 3 As shown, the marketing conditions may include CN1, CN2 and CN3. If the logical relationship of the event conditions of the marketing conditions is an OR logic, CN1, CN2 and CN3 are stored as three different OR bidirectional linked lists respectively, and each OR bidirectional linked list contains only one bidirectional linked list node for storing CN1, CN2 or CN3; if the logical relationship of the event conditions of the marketing conditions is an AND logic, CN1, CN2 and CN3 are stored as an AND bidirectional linked list, and the bidirectional linked list contains three bidirectional linked list nodes. CN1, CN2 and CN3 can be stored in the three bidirectional linked list nodes in any order, and the bidirectional linked list nodes are bidirectionally connected through the predecessor pointer (pre) and the successor pointer (next); if the logical relationship of the event conditions of the marketing conditions is an AND logic, and the sequence order is CN1→CN2→CN3, then CN1, CN2 and CN3 are stored as a sequence bidirectional linked list in the sequence order, CN1 is the head node (head) of the sequence bidirectional linked list, CN3 is the tail node (tail) of the sequence bidirectional linked list, CN2 is the middle node of the sequence bidirectional linked list, and adjacent nodes of the sequence bidirectional linked list are connected through the predecessor pointer.

[0088] This embodiment can construct and set multiple marketing conditions, and construct a bidirectional linked list corresponding to each marketing condition. The marketing strategy of each bidirectional linked list is the marketing strategy bound to its marketing condition.

[0089] S104: When a reporting event sent by the business system is received, a multi-branch tree is traversed based on the reporting event, and a target event condition node is obtained from the event condition nodes by matching.

[0090] In this embodiment, when a reported event is received from a business system, a multi-branch tree is traversed based on the reported event, and a target event condition node is matched from the event condition node. This embodiment does not limit the specific type of business system, and generally can include user systems, risk control systems, middle office systems, accounting systems, financial systems, and accounting systems.

[0091] This embodiment decouples marketing activities from various business systems, and sets up an event reporting interface in each business system. Events are reported through the event reporting interface. Generally, the input parameters of the event reporting interface may include: reporting time, reporting user, event number (EN), event name, attribute object list, etc., where the attribute objects mainly include attribute number (CN), attribute name, attribute type, attribute value, etc.

[0092] This embodiment does not limit the specific method of matching the target event condition node. Generally, when a reported event sent by a business system is received, the target event node that matches the reported event is determined based on the rule expression of the event node; the target event condition node that matches the reported event is determined based on the rule expression of the event condition node under the target event node. This embodiment does not limit the specific matching method. The specific matching method can be matched by comparing the parameters of the reported event with the parameters in the rule expression, such as determining the target event node by comparing the event name, and further determining the target event condition node by comparing the attribute name and attribute value in the event condition node of the target event node.

[0093] Since each event node in the event node layer corresponds to a business event, and each event node is mutually exclusive, it can match only one event node. Since each event condition node does not have mutually exclusive rows, there is a situation where a reported event is matched to multiple event condition nodes at the same time.

[0094] In a specific example, when the reported event is a repayment event, and the reported event is represented as "the repayment amount is 10,000", the repayment event node can be matched as the target event node. If the repayment event node contains two event condition nodes represented as "the repayment amount is greater than 5,000" and "the repayment amount is greater than 6,000" respectively, then after matching the rule expression, the above two event condition nodes can both be used as the target event condition nodes of the reported event.

[0095] S105: Determine the doubly linked list containing the target event condition node as the target doubly linked list, perform traversal trigger verification on the forward nodes and backward nodes of the target event condition node in the target doubly linked list, and execute the marketing activities of the target doubly linked list based on the trigger verification result.

[0096] This embodiment can determine the doubly linked list containing the target event condition node as the target doubly linked list, perform traversal trigger verification on the forward nodes and backward nodes of the target event condition node in the target doubly linked list, and execute the marketing activities of the target doubly linked list based on the trigger verification results.

[0097] Since each reported event can match multiple target event condition nodes, this embodiment can sequentially execute the steps of determining the bidirectional linked list containing the target event condition nodes as the target bidirectional linked list for each target event condition node, traversing and triggering the forward nodes and backward nodes of the target event condition nodes in the target bidirectional linked list, and executing the marketing activities of the target bidirectional linked list based on the trigger verification results.

[0098] This embodiment does not limit the specific method of executing the marketing strategy of the target bidirectional linked list. Generally, an event record table for each bidirectional linked list can be constructed to generate event records for each target event condition node, and the event records can be stored in the event record table. In this embodiment, the event record may include the event trigger time and the event trigger user, which can specifically come from the reporting time and reporting user in the reported event.

[0099] In this embodiment, when the target bidirectional linked list is or bidirectional linked list, since there is no forward node and backward node in the target event condition node in the or bidirectional linked list, the marketing activity of the or bidirectional linked list can be directly executed at this time; further, since the same marketing condition can contain multiple or bidirectional linked lists, the marketing activity corresponding to the marketing condition can be executed when the target event condition in any or bidirectional linked list is triggered. Therefore, in order to avoid repeated execution of marketing activities, when the target bidirectional linked list is or bidirectional linked list, the target marketing condition to which the or bidirectional linked list belongs is determined; if the marketing activity of the target marketing condition has not been executed, the marketing activity of the or bidirectional linked list is executed; if the marketing activity of the target marketing condition has been executed, the marketing activity of the or bidirectional linked list is intercepted.

[0100] In this embodiment, when the target doubly linked list is a and doubly linked list, the forward nodes and backward nodes of the target event condition node in the and doubly linked list are traversed, and when the event record table of the and doubly linked list contains event records of all forward nodes and backward nodes, the marketing activities of the and doubly linked list are executed. When the event record table of the and doubly linked list contains event records of all forward nodes and backward nodes, it can be determined that all marketing event condition nodes of the and doubly linked list are triggered, and the marketing activities of the and doubly linked list can be executed.

[0101] Since the target event condition may be at the head node or tail node of the bidirectional linked list, when traversing the forward and backward nodes of the target event condition node in the bidirectional linked list, there are situations where there are only forward nodes or only backward nodes. At this time, when there are event records of all forward nodes or all backward nodes in the event record table of the bidirectional linked list, the marketing activities of the bidirectional linked list can be executed.

[0102] In this embodiment, when the target doubly linked list is a sequence doubly linked list, if the target event condition node is the tail node of the sequence doubly linked list, the forward node of the target event condition node in the sequence doubly linked list is traversed. When the event record table of the sequence doubly linked list contains event records of all forward nodes and the event records are stored in sequence order, the marketing activities of the sequence doubly linked list can be executed.

[0103] Since the event condition logic relationship corresponding to the sequence bidirectional linked list is sequence logic, the execution order of the marketing event condition nodes in the sequence bidirectional linked list needs to be triggered in sequence order. Therefore, only when the target event condition node is at the tail node and the triggering order of its forward node is sequence order, that is, the event records of all forward nodes are stored in sequence order, the marketing activities of the sequence bidirectional linked list can be executed.

[0104] Furthermore, in order to avoid repeated use of event records, the present embodiment may mark the event records. Specifically, a status flag of the event record may be set in the event record table; the status flag includes an available state and an invalid state; when the event record is stored in the event record table, the status flag of the event record is set to an available state; when the event record is used to trigger a marketing strategy, the status flag of the event record is set to an invalid state; and event records with a status flag of an invalid state are cleared from the event record table.

[0105] That is, when an event condition record participates in triggering a marketing activity, its status flag is set to an invalid state, and event records with a status flag of an invalid state are cleared from the event record table in real time.

[0106] To further expand, in this embodiment, the marketing event condition nodes in the marketing conditions can also be configured by a combination of multiple event condition logical relationships. The specific trigger verification method of the marketing event condition nodes in the bidirectional linked list can be set based on actual applications, and this embodiment does not limit it.

[0107] Based on the above embodiments, the method of the present invention achieves unified configuration, management and maintenance of marketing activities by decoupling marketing activities from various business platforms, thereby avoiding the problems of high platform development costs, long cycles, and difficult management and maintenance caused by the close coupling of marketing activities with business systems.

[0108] The following combination Figure 4 , Figure 4 This is a structural block diagram of a marketing activity execution device provided by an embodiment of the present invention, and the device may include:

[0109] The first module 100 is used to construct a multi-branch tree including a root node layer, an event node layer and an event condition node layer from top to bottom based on business events and business event conditions;

[0110] The second module 200 is used to select a marketing event condition node for configuring a marketing condition from the event condition nodes in the event condition node layer;

[0111] The third module 300 is used to construct a bidirectional linked list containing the marketing event condition nodes based on the event condition logical relationship of the marketing condition;

[0112] The fourth module 400 is used for, when receiving a report event sent by the business system, traversing the multi-branch tree based on the report event, and matching a target event condition node from the event condition nodes;

[0113] The fifth module 500 is used to determine the bidirectional linked list containing the target event condition node as the target bidirectional linked list, perform traversal trigger verification on the forward node and the backward node of the target event condition node in the target bidirectional linked list, and execute the marketing activities of the target bidirectional linked list based on the trigger verification result.

[0114] Based on the above embodiments, the method of the present invention achieves unified configuration, management and maintenance of marketing conditions by decoupling marketing conditions from various business platforms, thereby avoiding the problems of high platform development costs, long cycles, and difficult management and maintenance caused by the close coupling of marketing conditions with business systems.

[0115] Based on the above embodiment, the first module 100 may include:

[0116] The first unit is used for storing each marketing event condition node as an OR bidirectional linked list when the event condition logical relationship of the marketing condition is OR;

[0117] The second unit is used for storing all the marketing event condition nodes as an AND bidirectional linked list when the event condition logical relationship of the marketing condition is AND, and the adjacent bidirectional linked list nodes in the AND bidirectional linked list are bidirectionally connected through a predecessor pointer and a successor pointer;

[0118] The third unit is used for storing all the marketing event condition nodes as a sequence bidirectional linked list in sequence order when the event condition logical relationship of the marketing condition is a sequence, and the adjacent bidirectional linked list nodes in the sequence bidirectional linked list are unidirectionally connected through the predecessor pointer.

[0119] Based on the above embodiments, the fifth module 500 may include:

[0120] The fourth unit is used to construct an event record table of each of the bidirectional linked lists, generate an event record of each of the target event condition nodes, and store the event record in the event record table;

[0121] A fifth unit, configured to execute the marketing activity of the or bidirectional linked list when the target bidirectional linked list is the or bidirectional linked list;

[0122] The sixth unit is used for, when the target doubly linked list is the and doubly linked list, traversing the forward nodes and backward nodes of the target event condition node in the and doubly linked list, and when the event records of all the forward nodes and the backward nodes exist in the event record table of the and doubly linked list, executing the marketing activity of the and doubly linked list;

[0123] The seventh unit is used for traversing the forward node of the target event condition node in the sequence bidirectional linked list when the target bidirectional linked list is the sequence bidirectional linked list and the target event condition node is the tail node of the sequence bidirectional linked list, and executing the marketing activity of the sequence bidirectional linked list when the event records of all the forward nodes exist in the event record table of the sequence bidirectional linked list and the event records are recorded in the sequence order.

[0124] Based on the above embodiments, the device may further include:

[0125] The sixth module is used to set the status flag of the event record in the event record table; the status flag includes an available state and an invalid state;

[0126] A seventh module, configured to set the status flag of the event record to an available state when the event record is stored in the event record table;

[0127] An eighth module, configured to set the status flag of the event record to an invalid state when the event record is used to trigger the marketing activity;

[0128] The ninth module is used to clear the event record whose status is marked as invalid from the event record table.

[0129] Based on the above embodiments, the fifth unit may include:

[0130] A first subunit is used for determining a target marketing condition to which the or bidirectional linked list belongs when the target bidirectional linked list is the or bidirectional linked list;

[0131] A second subunit is used for executing the marketing activity of the or bidirectional linked list if the marketing activity of the target marketing condition is not executed;

[0132] The third subunit is used to intercept the marketing activity in the or bidirectional linked list if the marketing activity of the target marketing condition has been executed.

[0133] Based on the above embodiments, the first module 100 may include:

[0134] An eighth unit, configured to construct the business event condition of each business event based on the attributes of the business event;

[0135] A ninth unit is used to construct a multi-branch tree including the root node layer, the event node layer and the event condition node layer from top to bottom, store the business event in the event node in the event node layer, and store the business event condition in the event condition node in the event condition node layer;

[0136] The tenth unit is used to construct a regular expression of each of the event nodes and the event condition nodes based on the business event and the business event condition.

[0137] Accordingly, the fourth module 400 may include:

[0138] An eleventh unit is configured to determine a target event node matching the reported event based on a regular expression of the event node when receiving the reported event sent by the business system;

[0139] The twelfth unit is used to determine a target event condition node matching the reported event based on a regular expression of the event condition node under the target event node.

[0140] Based on the above embodiments, the business events include: registration, login, card binding, real-name authentication, credit granting, borrowing, repayment and credit limit increase.

[0141] Based on the above embodiments, the present invention further provides a marketing activity execution device, which may include a memory and a processor, wherein a computer program is stored in the memory, and when the processor calls the computer program in the memory, the steps provided in the above embodiments may be implemented. Of course, the device may also include various necessary network interfaces, power supplies, and other components.

[0142] The present invention also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by an execution terminal or a processor, the method provided in the embodiment of the present invention can be implemented; the storage medium may include: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and other media that can store program codes.

[0143] In this article, relational terms such as first and second, etc. are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

Claims

1. A method for executing a marketing activity, characterized in that: include: Based on business events and business event conditions, a multi-branch tree including a root node layer, an event node layer and an event condition node layer is constructed from top to bottom; Selecting a marketing event condition node for configuring a marketing condition from the event condition nodes in the event condition node layer; Constructing a bidirectional linked list including the marketing event condition nodes based on the event condition logical relationship of the marketing condition; When receiving a reported event sent by the business system, traversing the multi-branch tree based on the reported event, and matching the target event condition node from the event condition nodes; The bidirectional linked list including the target event condition node is determined as the target bidirectional linked list, a traversal trigger check is performed on the forward node and the backward node of the target event condition node in the target bidirectional linked list, and a marketing activity of the target bidirectional linked list is executed based on the trigger check result.

2. The marketing activity execution method according to claim 1, characterized in that: The event condition logical relationship based on the marketing condition is used to construct a bidirectional linked list containing the marketing event condition nodes, including: When the event condition logical relationship of the marketing condition is OR, each marketing event condition node is stored as an OR bidirectional linked list; When the event condition logical relationship of the marketing condition is and, all the marketing event condition nodes are stored as an and bidirectional linked list, and adjacent bidirectional linked list nodes in the and bidirectional linked list are bidirectionally connected through a predecessor pointer and a successor pointer; When the event condition logical relationship of the marketing condition is a sequence, all the marketing event condition nodes are stored in a sequence bidirectional linked list in sequence order, and adjacent bidirectional linked list nodes in the sequence bidirectional linked list are unidirectionally connected through the predecessor pointer.

3. The marketing activity execution method according to claim 2, characterized in that: The traversing trigger verification of the forward node and the backward node of the target event condition node in the target bidirectional linked list, and executing the marketing activity of the target bidirectional linked list based on the trigger verification result, includes: Constructing an event record table of each of the bidirectional linked lists, generating an event record of each of the target event condition nodes, and storing the event record in the event record table; When the target doubly linked list is the or doubly linked list, executing the marketing activity of the or doubly linked list; When the target doubly linked list is the and doubly linked list, traverse the forward nodes and backward nodes of the target event condition node in the and doubly linked list, and when the event records of all the forward nodes and the backward nodes exist in the event record table of the and doubly linked list, execute the marketing activity of the and doubly linked list; When the target doubly linked list is the sequence doubly linked list, if the target event condition node is the tail node of the sequence doubly linked list, traverse the forward node of the target event condition node in the sequence doubly linked list, and when the event records of all the forward nodes exist in the event record table of the sequence doubly linked list, and the event records are stored in the sequence order, execute the marketing activity of the sequence doubly linked list.

4. The marketing activity execution method according to claim 3, characterized in that: Also includes: Setting a status flag of the event record in the event record table; the status flag includes an available status and an invalid status; When the event record is stored in the event record table, setting the status flag of the event record to an available state; When the event record is used to trigger the marketing activity, setting the status flag of the event record to an invalid state; The event record with the status flag as the invalid state is cleared from the event record table.

5. The marketing activity execution method according to claim 3, characterized in that: When the target doubly linked list is the or doubly linked list, executing the marketing activity of the or doubly linked list comprises: When the target doubly linked list is the or doubly linked list, determining the target marketing condition to which the or doubly linked list belongs; If the marketing activity of the target marketing condition is not executed, then executing the marketing activity of the or bidirectional linked list; If the marketing activity of the target marketing condition has been executed, the marketing activity of the or bidirectional linked list is intercepted.

6. The marketing activity execution method according to claim 1, characterized in that: The multi-branch tree including a root node layer, an event node layer and an event condition node layer from top to bottom is constructed based on the business events and business event conditions, including: Constructing the business event condition of each business event based on the attributes of the business event; Constructing the multi-branch tree including the root node layer, the event node layer and the event condition node layer from top to bottom, storing the business events in the event nodes in the event node layer, and storing the business event conditions in the event condition nodes in the event condition node layer; Constructing regular expressions of each of the event nodes and the event condition nodes based on the business event and the business event condition; Accordingly, when a reported event sent by the business system is received, the multitree is traversed based on the reported event, and a target event condition node is matched from the event condition nodes, including: When receiving the reported event sent by the business system, determining a target event node matching the reported event based on the rule expression of the event node; A target event condition node matching the reported event is determined based on a regular expression of the event condition node under the target event node.

7. The marketing activity execution method according to claim 1, characterized in that: The business events include: registration, login, card binding, real-name authentication, credit granting, borrowing, repayment and credit limit increase.

8. A marketing activity execution device, characterized in that: include: The first module is used to construct a multi-branch tree including a root node layer, an event node layer and an event condition node layer from top to bottom based on business events and business event conditions; A second module is used to select a marketing event condition node for configuring a marketing condition from the event condition nodes in the event condition node layer; The third module is used to construct a bidirectional linked list containing the marketing event condition nodes based on the event condition logical relationship of the marketing condition; A fourth module is used for, when receiving a reporting event sent by a business system, traversing the multi-branch tree based on the reporting event, and matching a target event condition node from the event condition nodes; The fifth module is used to determine the bidirectional linked list containing the target event condition node as the target bidirectional linked list, perform traversal trigger verification on the forward node and the backward node of the target event condition node in the target bidirectional linked list, and execute the marketing activities of the target bidirectional linked list based on the trigger verification result.

9. A marketing activity execution device, characterized in that: include: Memory, for storing computer programs; A processor, configured to implement the marketing activity execution method as claimed in any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, the marketing activity execution method according to any one of claims 1 to 7 is implemented.

Images