Processing method, orchestration method, and computing device

Abstract

Embodiments of the present application provide a processing method, an arrangement method and a computing device. The method comprises: obtaining rule arrangement information sent by a client; the rule arrangement information comprises a plurality of target nodes configured for a target population, a connection relationship between the plurality of target nodes, and attribute data corresponding to the plurality of target nodes; establishing a corresponding relationship between the rule arrangement information and a target user conforming to the target population; and performing an execution operation corresponding to each of the plurality of target nodes according to the attribute data and the connection relationship in the rule arrangement information, to implement a target processing operation on the target user. The technical solution provided by the embodiments of the present application reduces development cost and improves processing effect.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a processing method, an arrangement method, and a computing device. Background Technology

[0002] With the development of network and electronic technologies, there is an increasing number of online systems that allow users to perform various transactions, such as e-commerce systems and logistics service systems. These online systems typically involve user-facing operations, such as sending notifications, recommending products or activities offered by the system, and thus reaching users with information.

[0003] In current technology, to implement specific user actions, operations personnel typically set corresponding rule requirements for a specific group of users, which are then handed over to developers to write scripts to generate the corresponding rules. The execution system then performs the corresponding actions according to the rules for users within that specific group. However, this method of implementing actions is costly to develop and has poor processing results. Summary of the Invention

[0004] This application provides a processing method, an arrangement method, and a computing device to solve the technical problems of high development costs and poor processing effects in the prior art.

[0005] Firstly, this application provides a processing method, including:

[0006] Obtain rule orchestration information sent by the client; the rule orchestration information includes multiple target nodes configured for the target audience, the connection relationships between the multiple target nodes, and the attribute data corresponding to the multiple target nodes;

[0007] Establish the correspondence between the rule arrangement information and the target users who conform to the target group;

[0008] According to the attribute data in the rule-arranged information and the connection relationship, the execution operations corresponding to the multiple target nodes are executed respectively to realize the target processing operation for the target user.

[0009] Optionally, the method further includes:

[0010] A rule orchestration interface is provided to the client; the rule orchestration interface provides multiple node controls; the multiple target nodes are determined based on the selection operations of the target personnel on the multiple node controls; the connection relationships are determined based on the connection operations of the target personnel on the multiple target nodes; the attribute data is determined based on the configuration operations of the target personnel.

[0011] Optionally, the attribute data includes node attributes and connection attributes corresponding to the plurality of target nodes respectively;

[0012] The step of executing the execution operations corresponding to the multiple target nodes according to the attribute data and the connection relationship, so as to realize the target processing operation for the target user, includes:

[0013] For any target node to be executed, perform the corresponding execution operation according to the node attributes to obtain the execution result;

[0014] Based on the execution results and the matching results of different connection attributes, the next target node to be executed is determined.

[0015] Optionally, the step of performing the corresponding execution operation according to the node attributes to obtain the execution result for any target node to be executed includes:

[0016] For any target node to be executed, if the target node is the starting node, the processing flow corresponding to the rule orchestration information is initiated.

[0017] If the target node is an end node, the processing flow corresponding to the rule arrangement information is terminated.

[0018] If the target node is a traffic splitting node, the status data corresponding to the target user is detected according to the traffic splitting conditions configured in the node attributes, and the status data is matched with the traffic splitting conditions to obtain the execution result;

[0019] If the target node is a processing node, the corresponding processing operation is performed according to the processing method configured in the node attributes.

[0020] Optionally, the processing node includes an access node, a delay node, a filter node, a tag node, or an experiment node;

[0021] When the target node is a processing node, the corresponding processing operation is performed according to the processing method configured in the node attributes, including:

[0022] When the target node is a reach node, according to the reach timing configured in the node attributes, the reach method corresponding to the target node is used to send the reach text configured in the node attributes for the target object to the target user, so as to recommend the target object to the target user;

[0023] If the target node is a delayed node, a timing operation is performed according to the delay time configured in the node attributes;

[0024] If the target node is a filter node, the target user is matched with the filter conditions configured in the node attributes.

[0025] If the target node is an experimental node, the experimental group to which the target user belongs is determined according to the experimental attributes configured in the node attributes;

[0026] If the target node is a tag node, the tag attribute is set for the target user according to the tag information configured in the node attribute.

[0027] Optionally, the traffic splitting conditions include any of the following implementation methods:

[0028] Meets the predetermined user level; executes the predetermined user behavior; a predetermined event occurs; the user's rights usage status is in the predetermined state; the target behavior is executed a predetermined number of times.

[0029] Optionally, the attribute data includes programming attributes; the programming attributes include the target audience, programming cycle, and predetermined time range;

[0030] The step of performing corresponding execution operations according to the node attributes to obtain execution results for any target node to be executed includes:

[0031] According to the aforementioned arrangement cycle, the rule arrangement information is periodically executed within the predetermined time range;

[0032] For any target node to be executed, perform the corresponding execution operation according to the node attributes to obtain the execution result.

[0033] Optionally, the step of executing the execution operations corresponding to the multiple target nodes according to the attribute data in the information arranged according to the rules and the connection relationship, so as to realize the target processing operation for the target user, includes:

[0034] Based on the multiple groups to which the target user belongs, determine at least one rule arrangement information that the target user matches;

[0035] For any rule arrangement information, according to the attribute data and connection relationship in the rule arrangement information, the execution operations corresponding to the multiple target nodes are executed respectively to realize the target processing operation for the target user.

[0036] Optionally, establishing the correspondence between the rule arrangement information and target users that fit the target population includes:

[0037] Based on the attribute data of multiple target nodes in the rule arrangement information and the connection relationships between the multiple target nodes, a directed acyclic graph is generated;

[0038] Establish the correspondence between the directed acyclic graph and the target users that match the target population.

[0039] Optionally, determining the next target node to be executed based on the matching results of the execution result and different connection attributes includes:

[0040] Identify at least one target node that has a connection relationship with the currently executing target node;

[0041] The target node corresponding to the connection relationship whose connection attribute matches the execution result is taken as the next target node to be executed.

[0042] Optionally, the connection attribute includes a matching mode and a matching line value. The matching mode includes a conditional matching mode with a corresponding matching line value of yes or no. The matching mode includes a value matching mode with a corresponding matching line value of a specified value. The matching mode includes a normal mode with a corresponding matching line value of empty.

[0043] Optionally, the step of performing the corresponding execution operation according to the node attributes to obtain the execution result for any target node to be executed includes:

[0044] For any target node to be executed, if the execution conditions configured in the node attributes are met, the corresponding execution operation is executed to obtain the execution result.

[0045] Optionally, the method further includes:

[0046] According to the attribute data and connection relationships in the rule-arranged information, for the test user, the execution operations corresponding to the multiple target nodes are executed respectively to obtain test results;

[0047] If the test results meet the test requirements, establish the correspondence between the rule arrangement information and the target users who fit the target group.

[0048] Optionally, sending the plurality of target nodes, the connection relationships between the plurality of target nodes, and the attribute data as rule orchestration information to the server includes:

[0049] In response to the save operation performed on the rule orchestration interface, the multiple target nodes, the connection relationships between the multiple target nodes, and the attribute data are sent to the server as rule orchestration information.

[0050] Optionally, determining the connection relationship between the plurality of target nodes in response to the connection operation for the plurality of target nodes includes:

[0051] In response to a connection operation from the first target node to the second target node for any two of the plurality of target nodes, a directed connection line is established between the two target nodes if a preset rule is satisfied.

[0052] Secondly, embodiments of this application provide an arrangement method, including:

[0053] In response to the arrangement operation of the target personnel, the system determines the configured multiple target nodes, the connection relationships between the multiple target nodes, and the attribute data of the multiple target nodes; the attribute data includes the target population targeted by the multiple target nodes.

[0054] The multiple target nodes, the connection relationships between the multiple target nodes, and the attribute data are sent to the server as rule orchestration information. The rule orchestration information is used to establish the correspondence between the rule orchestration information and the target users that conform to the target group, and to trigger the execution of the execution operations corresponding to the multiple target nodes according to the attribute data and the connection relationships in the rule orchestration information, so as to realize the target processing operation for the target users.

[0055] Optionally, the step of determining the configured multiple target nodes, the connection relationships between the multiple target nodes, and the attribute data of the multiple target nodes in response to the arrangement operation of the target personnel includes:

[0056] Displays the rule arrangement interface;

[0057] The rule arrangement result provides multiple node controls;

[0058] In response to a selection operation on the plurality of node controls, a plurality of target nodes are displayed on the rule orchestration interface;

[0059] In response to connection operations targeting the plurality of target nodes, the connection relationships between the plurality of target nodes are determined;

[0060] In response to configuration operations for the plurality of target nodes, attribute data is determined.

[0061] Optionally, the rule arrangement interface includes a selection area, an editing area, and a configuration area;

[0062] The provision of multiple node controls in the rule arrangement result includes: providing multiple node controls in the selection area;

[0063] The step of displaying multiple target nodes in the rule arrangement interface in response to a selection operation of the multiple node controls includes: displaying the dragged multiple target nodes in the editing area in response to a drag operation of the multiple node controls from the selection area to the editing area;

[0064] Determining the connection relationship between the plurality of target nodes in response to a connection operation for the plurality of target nodes includes: determining the connection relationship between the plurality of target nodes in response to a connection operation for the plurality of target nodes in the editing area;

[0065] The determination of attribute data in response to the configuration operation for the plurality of target nodes includes:

[0066] In response to a first configuration operation in the configuration area, orchestration attributes are determined;

[0067] In response to a touch operation on any target node, a node configuration prompt message for the target node is displayed in the configuration area;

[0068] Based on the second configuration operation triggered in response to the configuration prompt information, the node attributes corresponding to the target node are determined;

[0069] In response to a touch operation for any connection relationship, a connection attribute configuration prompt message for the connection relationship is displayed in the configuration area;

[0070] Based on the third configuration operation triggered by the configuration prompt information for the connection attribute, the node attribute corresponding to the connection relationship is determined.

[0071] Thirdly, embodiments of this application provide a computing device, including a processing component and a storage component; the storage component stores one or more computer instructions; the one or more computer instructions are to be invoked and executed by the processing component to implement the processing method as described in the first aspect above or the orchestration method as described in the second aspect above.

[0072] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program, which, when executed by a computer, implements the processing method described in the first aspect above or the arrangement method described in the second aspect above.

[0073] In this embodiment, the target personnel can perform orchestration operations on the client side for the target group, based on the processing flow for that group. This results in rule orchestration information composed of multiple target nodes. The server can maintain this rule orchestration information for the target users within the target personnel and execute the corresponding execution operations for the target nodes according to the attribute data and connection relationships of the rule orchestration information. This achieves the target processing operation for the target user. This embodiment does not require writing script code; the rule orchestration information can be achieved by the target personnel on the client side through orchestration operations for the target nodes. Based on this, the processing operation for the target user can be implemented. The target personnel can design the rule orchestration information according to actual needs to ensure processing effectiveness. The operation is simple and the development cost is low.

[0074] These or other aspects of this application will become more apparent in the following description of the embodiments. Attached Figure Description

[0075] To more clearly illustrate the technical solutions in the embodiments of this application 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 some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0076] Figure 1 This application provides a schematic diagram illustrating the structure of an embodiment of an execution system.

[0077] Figure 2 A flowchart of one embodiment of a processing method provided in this application is shown;

[0078] Figure 3 A flowchart of one embodiment of the arrangement method provided in this application is shown;

[0079] Figure 4a This illustration shows a schematic diagram of a rule arrangement interface in a practical application according to an embodiment of this application;

[0080] Figure 4b This illustration shows yet another display diagram of a rule arrangement interface in a practical application according to an embodiment of this application;

[0081] Figure 5 This illustration shows a scenario interaction diagram of an embodiment of this application in a practical application;

[0082] Figure 6 This illustration shows a schematic diagram of rule arrangement information in a practical application according to an embodiment of this application;

[0083] Figure 7This invention provides a schematic diagram of the structure of one embodiment of a processing apparatus.

[0084] Figure 8 This invention provides a schematic diagram of the structure of one embodiment of a scheduling apparatus.

[0085] Figure 9 A schematic diagram of one embodiment of a computing device provided in this application is shown. Detailed Implementation

[0086] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.

[0087] In some of the processes described in the specification, claims, and accompanying drawings of this application, multiple operations appearing in a specific order are included. However, it should be clearly understood that these operations may not be executed in the order they appear herein, or may be executed in parallel. The operation numbers, such as 101, 102, etc., are merely used to distinguish different operations and do not themselves represent any execution order. Furthermore, these processes may include more or fewer operations, and these operations may be executed sequentially or in parallel. It should be noted that the descriptions such as "first," "second," etc., in this document are used to distinguish different messages, devices, modules, etc., and do not represent a chronological order, nor do they limit "first" and "second" to different types.

[0088] The technical solutions of this application can be applied to application scenarios where specific processing operations are performed on users in online systems. The technical solutions of this application can be implemented by an execution system.

[0089] Taking recommending target users in an e-commerce system as an example, the traditional approach—where operations staff submit recommendation requests, developers create scripts to generate outreach rules, and the execution system follows these rules—typically suffers from one or more of the following drawbacks: 1) It requires the involvement of both operations and development staff, resulting in high development costs; 2) It cannot achieve personalized processing. To achieve this, operations staff need to segment the user group as much as possible and edit various rule contents, which is complex and further increases development costs; 3) When there are multiple processing requests, multiple rules need to be set. In the traditional approach, these rules are not interconnected, leading to duplicate processing of the same user and the possibility that users may receive multiple processing operations simultaneously, resulting in a poor user experience and affecting processing effectiveness. Implementing logically complex rules requires operations staff to accurately provide requirements, and developers to rewrite the scripts, which places higher demands on personnel and undoubtedly increases development costs.

[0090] To reduce development costs and improve processing effectiveness, the inventors, after a series of studies, proposed the technical solution of this application embodiment. In this application embodiment, target users can combine the processing flow for the target group and perform orchestration operations on the client side for the target group, realizing rule orchestration information composed of multiple target nodes. The server can maintain the rule orchestration information for each user among the target users and, according to the attribute data and connection relationships of the rule orchestration information, execute the execution operation corresponding to the target node for the target user, thus realizing the target processing operation for the target user. This application embodiment does not require writing code to implement rule configuration; the rule orchestration information can be realized by the target users through orchestration operations on the target nodes on the client side. Target users can design rule orchestration information according to actual needs to ensure processing effectiveness. The operation is simple, the development cost is low, and the learning cost is low, thus improving development efficiency.

[0091] The target users can design and arrange rules according to their actual needs without the need for developers. For example, multiple rules can be linked together through the arrangement of rules, and different processing operations can be performed on users in different states through user traffic distribution nodes and configured execution conditions. This achieves personalized processing without the need for manually segmenting the user groups, which can improve processing efficiency and reduce development costs.

[0092] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0093] Figure 1 The diagram illustrates an architecture of an execution system that can be applied to one of the technical solutions of this application. The system architecture may include a client 101 and a server 102.

[0094] In this setup, client 101 and server 102 establish a connection via a network. The network provides a communication link between client 101 and server 102. The network can include various connection types, such as wired or wireless communication links or fiber optic cables. Client 101 can interact with server 102 via the network to receive or send messages, etc.

[0095] The client 101 can be a browser, an app (application), a web application such as an H5 (HyperText Markup Language 5) application, a lightweight application (also known as a mini-program), or a cloud application, etc. The user client 101 can be deployed on electronic devices, requiring the device to run or certain apps on the device to function. Electronic devices can have displays and support information browsing, such as personal mobile terminals like mobile phones, tablets, personal computers, desktop computers, smart speakers, smartwatches, etc. For ease of understanding, Figure 1 The client is primarily represented by the image of a device. Various other types of applications can also be configured in electronic devices, such as human-computer interaction applications, model training applications, text processing applications, web browser applications, shopping applications, search applications, instant messaging tools, email clients, and social media platform software. Electronic devices can refer to devices used by users that have the computing, internet access, and communication functions required by the user, such as mobile phones, tablets, personal computers, and wearable devices. Electronic devices typically include at least one processing component and at least one storage component. Electronic devices may also include basic configurations such as network interface cards (NICs), I / O (input / output) buses, and audio / video components; this application does not limit this. Optionally, depending on the implementation of the electronic device, it may also include some peripheral devices, such as keyboards, mice, input pens, and printers; this application does not limit this.

[0096] Server 102 may include servers that provide various services, such as servers that process interactive information sent by clients.

[0097] It should be noted that server 102 can be implemented as a distributed server cluster consisting of multiple servers, or as a single server. The server can also be a server in a distributed system, or a server integrated with blockchain. The server can also be a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms, or an intelligent cloud computing server or intelligent cloud host with artificial intelligence technology.

[0098] It should be noted that the processing methods provided in the embodiments of this application are generally executed by the server 102, and the corresponding processing devices are generally located in the server 102. Similarly, the orchestration methods provided in the embodiments of this application are generally executed by the client 101, and the corresponding orchestration devices are generally located in the client 101. However, in other embodiments of this application, the client 101 and the server 102 may have similar functions to execute the processing methods or orchestration methods provided in the embodiments of this application. In other embodiments, the processing methods or orchestration methods provided in the embodiments of this application may also be jointly executed by the client 101 and the server 102.

[0099] It should be understood that Figure 1 The number of clients and servers shown is merely illustrative. Depending on implementation needs, there can be any number of clients and servers.

[0100] It should be noted that the technical solutions of this application embodiment are applicable to a virtual network environment. The described user generally refers to a "virtual user." Real users can register user accounts through registration to obtain a user identity in the network environment. For example, in this application embodiment, a user can refer to a virtual user obtained by registering a user account on an online system. Virtual users can have various types of accounts to achieve interoperability on the network. For example, users registered on an online system can also correspond to communication accounts, such as email accounts, instant messaging accounts, etc.

[0101] It should be noted that the embodiments of this application may involve the use of user data. In practical applications, user-specific personal data may be used in the scheme described herein within the scope permitted by applicable laws and regulations, provided that it complies with the applicable laws and regulations of the country (e.g., with the user's explicit consent, with the user being properly notified, etc.).

[0102] The implementation details of the technical solutions in the embodiments of this application are described in detail below.

[0103] Figure 2 A flowchart illustrating a processing method provided in this application is provided. The technical solution of this embodiment can be executed by a server, and the method may include the following steps:

[0104] 201: Retrieve rule orchestration information sent by the client.

[0105] The rule orchestration information includes multiple target nodes configured for the target audience, the connection relationships between these target nodes, and the attribute data of these target nodes. This rule orchestration information can be generated based on the orchestration operations performed by the target audience.

[0106] Among them, multiple target nodes can have connection directions, and the connection relationship can be determined based on the connection established in the connection direction.

[0107] Each target node has a corresponding execution operation, and the scripts for executing the operation can be generated in advance.

[0108] In this embodiment of the application, the rule arrangement information may include at least one rule, which can be arranged by the target personnel in combination with actual needs, such as target processing operations for the target group, through node settings.

[0109] Rule arrangement information can indicate the execution operations corresponding to multiple target nodes and the execution order of different execution operations, thereby forming a processing flow for the target processing operations implemented for the target user.

[0110] In this context, a target node can connect to at least one other target node.

[0111] These multiple target nodes can correspond to various node types, such as start nodes, end nodes, diversion nodes, and processing nodes. Start and end nodes indicate the initiation and termination of the processing flow; diversion nodes are used for conditional judgments to achieve user diversion; and processing nodes are used to execute processing operations targeting the processing flow or users. Depending on actual needs, processing nodes can be further categorized as, for example, delay nodes, experimental nodes, marker nodes, or reach nodes. In scenarios involving triggering information for users, such as sending notifications or recommending target objects, reach nodes can be included. Reach nodes can be used to send corresponding reach messages to users according to the reach method.

[0112] To ensure normal processing requirements, the rule arrangement information may include at least a start node, an end node, and a processing node. These node types will be further described in the corresponding embodiments below.

[0113] The client can respond to the orchestration operations of the target personnel and determine the multiple target nodes configured by the target personnel for the target group, the connection relationships between the multiple target nodes, and the attribute data of the multiple target nodes.

[0114] To facilitate orchestration operations by target users, the server can optionally provide a rule orchestration interface to the client. The client displays this interface. The interface can provide multiple node controls; multiple target nodes can be determined based on the target user's selections of these controls; the connection relationships between different target nodes can be determined based on the target user's connection operations to multiple target nodes; and attribute data can be determined based on the target user's configuration operations.

[0115] The target audience can refer to a set of users with the same characteristics. Users in an online system can be classified into one or more groups based on their user characteristics. Since user characteristics in an online system may change as users behave in the online system, the group to which each user belongs can be dynamically divided and changed.

[0116] The target audience can be broadly defined without being overly granular, to facilitate operation by the target users. In one implementation, the target audience could refer to all registered users. Then, through orchestration operations, traffic splitting or filtering nodes can be set in the rule orchestration information to implement user traffic splitting, filtering, or selection, ensuring granular operation.

[0117] 202: Establish the correspondence between rule arrangement information and target users that match the target audience.

[0118] The target user can refer to any user who fits the target group, that is, any user who has the characteristics corresponding to the target personnel.

[0119] In this embodiment, by establishing a correspondence between rule arrangement information and target users, the rule arrangement information can be maintained for each user who meets the target criteria.

[0120] The multiple target nodes and their connections arranged by the target personnel in the client form a graph. The connections are directional. To facilitate the storage and use of rule arrangement information, the establishment of the correspondence between rule arrangement information and target users that match the target group may include: generating a directed acyclic graph (DAG) based on the attribute data of multiple target nodes in the rule arrangement information and the connection relationships between multiple target nodes; and establishing the correspondence between the directed acyclic graph and target users that match the target group.

[0121] Of course, the directed acyclic graph can also be generated by the client, and the rule arrangement information can be used to generate the directed acyclic graph. This application does not impose any restrictions on this.

[0122] In addition, other data structures can be used to store the rule arrangement information, and this application does not impose any restrictions on this.

[0123] 203: According to the rules, arrange the attribute data and connection relationships in the information, and execute the corresponding execution operations of multiple target nodes to achieve the target processing operation for the target user.

[0124] After maintaining the corresponding rule orchestration information for the target user, the execution operations corresponding to multiple target nodes can be executed according to the rule orchestration information, thereby realizing the target processing operation for the target user.

[0125] In this embodiment, the target personnel can perform orchestration operations through the client based on their actual processing needs for the target population. This generates rule orchestration information consisting of multiple target nodes, the connection relationships between these nodes, and the attribute data of the target nodes. The server can establish a correspondence between the rule orchestration information and target users that match the target population. Therefore, according to the attribute data and connection relationships in the rule orchestration information, the execution operations corresponding to each target node can be executed to achieve the target processing operation for the target user. In this embodiment, the target personnel can generate rule orchestration information by performing orchestration operations on the target nodes on the client based on actual needs, thus ensuring processing effectiveness. Furthermore, no coding is required, making the operation simple and the development cost low.

[0126] In some embodiments, the target personnel can configure attributes for each target node and each connection relationship. Therefore, the attribute data configured for multiple target nodes may include the node attributes and connection attributes corresponding to each target node. Each target node may have a connection relationship with at least one target node, and the connection attributes corresponding to each target node may include the connection attributes of at least one connection relationship corresponding to the at least one target node.

[0127] Node attributes can include basic attributes such as node name, as well as execution attributes related to the operation being performed.

[0128] The above-mentioned execution of multiple target nodes according to attribute data and connection relationships, to achieve the target processing operation for the target user, may include:

[0129] For any target node to be executed, perform the corresponding execution operation according to the node attributes to obtain the execution result; determine the next target node to be executed based on the execution result and the matching results of different connection attributes.

[0130] As described above, multiple target nodes can correspond to various types. In some embodiments, for any target node to be executed, performing the corresponding execution operation according to the node attributes to obtain the execution result may include:

[0131] For any target node to be executed, if the target node is the starting node, the processing flow corresponding to the rule orchestration information is initiated.

[0132] When the target node is the end node, the processing flow corresponding to the end rule orchestration information is as follows:

[0133] When the target node is a traffic splitting node, the status data corresponding to the target user is detected according to the traffic splitting conditions configured in the node attributes, and the status data is matched with the traffic splitting conditions to obtain the execution result;

[0134] If the target node is a processing node, perform the corresponding processing operation according to the processing method configured in the node attributes.

[0135] Among multiple target nodes, the first target node to be executed can be the starting node, and the execution operation corresponding to the starting node can be the processing flow corresponding to the startup rule orchestration information, etc.

[0136] If the target node to be executed is an edge node, the processing flow corresponding to the rule orchestration information can be terminated, and the next target node to be executed will be empty. An edge node can be an end node or a processing node, etc.

[0137] As described above, multiple target nodes have connection directions, and the connection relationship can be determined based on the connections established along these directions. In some embodiments, determining the next target node to be executed based on the matching results of the execution result and different connection attributes may include:

[0138] Identify at least one target node that has a connection relationship with the currently executing target node; select the target node whose connection attribute matches the execution result as the next target node to be executed.

[0139] The connection attribute can include a matching mode and a matching line value. In one possible case, the matching mode can include a conditional matching mode, and the corresponding matching line value can be true (yes) or false (no). In another possible case, the matching mode can include a value matching mode, and the corresponding matching line value can be a specified value. In yet another possible case, the matching mode can include a regular mode, and the corresponding matching line value can be empty.

[0140] For the starting node, if the connection attribute of its corresponding connection relationship can be in normal mode, then the execution result of the starting node will match the connection attribute of any connection relationship, and all target nodes connected to the starting node will be the next target nodes to be executed.

[0141] For a branch node, the connection attribute of its corresponding connection relationship can be a conditional matching mode, etc. If the execution result is negative, the next target node to be executed is the target node corresponding to the connection relationship with the connection attribute "negative", such as the end node; if the execution result is positive, the next target node to be executed is the target node corresponding to the connection relationship with the connection attribute "positive", such as the processing node.

[0142] For processing nodes, the connection attributes of their corresponding connection relationships can be conditional matching mode, value matching mode, or normal mode, etc.

[0143] In some embodiments, for a traffic splitting node, the node attributes may include traffic splitting conditions, which indicate the required data type and judgment requirements, thereby enabling the detection of the status data corresponding to the target user. Matching the status data with the judgment requirements may involve determining whether the status data meets the traffic splitting conditions.

[0144] Status data may include, for example, user behavior data and user characteristic data.

[0145] As an optional approach, the routing conditions for a routing node can include meeting a predetermined user level. In this case, the status data can refer to the user level, and the corresponding operation can be determining whether the target user's user level is a predetermined user level. The predetermined user level includes one or more levels, etc.

[0146] As an alternative approach, the traffic splitting condition may include executing a predetermined user behavior. In this case, the status data may refer to the user behavior, and the corresponding execution operation may be to determine whether the target user's user behavior data is a predetermined user behavior.

[0147] User behavior can refer to actions performed in an online system, such as browsing, clicking, and saving.

[0148] As another optional approach, the routing conditions for the routing node can include the occurrence of a predetermined event. The status data can refer to events related to the target user, and the corresponding operation can be determining whether the event related to the target user is a predetermined event. Events can include, for example, client installation events, client startup events, account binding events, etc. Predetermined events can be, for example, the installation of a client on a new device, or the binding of a user account to a specified third-party account.

[0149] As another optional approach, the routing conditions for the routing node can include the user's benefit usage status being in a predetermined state. The status data is the user's benefit usage status, and the corresponding operation can be to determine whether the user's benefit usage status is in a predetermined state. User benefits may include, for example, electronic coupons or electronic red envelopes allocated to the user, and the user benefit usage status may include, for example, pending redemption, pending use, or already redeemed.

[0150] As another option, the routing conditions for the routing node can include executing a target behavior a predetermined number of times; then the status data can refer to the number of times the target behavior has been executed, and the corresponding execution operation can be determining whether the number of times the target user's target behavior has been executed is greater than or equal to the predetermined number. This target behavior could be, for example, a check-in action.

[0151] As described above, depending on the actual application, the processing node may include the reach node, delay node, filter node, mark node, or experiment node.

[0152] If the target node is a processing node, then according to the processing method configured in the node attributes, the corresponding processing operations can include:

[0153] 1) When the target node is a reach node, according to the reach timing configured in the node attributes, the reach method corresponding to the target node is used to send the reach text configured in the node attributes for the target object to the target user, so as to recommend the target object to the target user.

[0154] In practical applications, the technical solutions of this application embodiment can be applied to object recommendation scenarios. Therefore, the processing node can include at least a touchpoint node. The node attributes can be configured with touchpoint timing and touchpoint text, etc. The touchpoint text is used to recommend target objects, etc. The touchpoint timing can include time type, time information, etc. The time type can be, for example, localized time, personalized time, fixed time, or immediate sending, etc. The time information can refer to a specific moment, such as the specific moment corresponding to a fixed time, etc.

[0155] The "reach method" can indicate the recommended way to reach the message, such as email, instant messaging, reservation location on the reservation page, or pop-up window.

[0156] These nodes can be categorized into various reach nodes based on different reach methods. Furthermore, node attributes can also include the reach method, which can be configured by the target personnel.

[0157] The execution operation corresponding to the reaching node is to send the reaching message according to the reaching time and the reaching method. The execution result can be sending successfully or failing to send.

[0158] The connection attributes corresponding to the reached node can be condition matching mode, value matching mode, or normal mode, etc.

[0159] The target can refer to promotional activities, products, live streaming rooms, short videos, content, positions, industries, etc., and this application does not make specific limitations in this regard.

[0160] 2) If the target node is a delayed node, perform the timing operation according to the delay time configured in the node properties.

[0161] To meet practical needs, target nodes can also include delay nodes, with corresponding execution operations performed according to the delay time. The execution result is the timeout period. The corresponding connection attribute can be in value matching mode or normal mode. In value matching mode, the matching line value of a connection attribute is assumed to be the delay time. Therefore, if the timeout period satisfies the connection attribute, the corresponding target node becomes the next target node to be executed. Alternatively, normal mode can be used, where after the delay time has elapsed, the target node connected to the delay node becomes the next target node to be executed.

[0162] 3) When the target node is a filter node, match the target user with the filter conditions configured in the node attributes.

[0163] The connection attributes corresponding to the filter node can be conditions matching patterns, etc.

[0164] As an optional approach, the filtering conditions can include belonging to a predetermined group; then the status data can refer to the target user's group attributes, and the corresponding operation can be to determine whether the target user's group includes the predetermined group, etc.

[0165] As an alternative, filtering criteria can include user fatigue levels exceeding a predetermined value.

[0166] User fatigue can be determined based on the conversion rate of the target user's historical outreach copy; the higher the conversion rate, the lower the user fatigue. Target users can take further actions in response to outreach copy, such as clicking on the outreach copy or searching for the target audience recommended by the outreach copy. The conversion rate can be determined by calculating the ratio of the number of outreach copy instances where the target user takes further action to the total number of outreach copy instances obtained historically.

[0167] 4) If the target node is an experimental node, determine the experimental group to which the target user belongs according to the experimental attributes configured in the node attributes.

[0168] Among them, experimental attributes may include user attributes corresponding to different experimental groups, so that the execution point corresponding to the experimental node can determine the experimental group to which the target user belongs based on the user attributes. Of course, experimental attributes can also be randomly assigned, so the execution operation corresponding to the experimental node can be a random assignment of the user's experimental group.

[0169] The connection attribute corresponding to the experimental node can be a value matching mode. The matching line value can be a group identifier, so the target node corresponding to the connection attribute of the experimental group to which the target user belongs can be used as the next target node to be executed.

[0170] 5) If the target node is a tag node, set the tag attributes for the target user according to the tag information configured in the node attributes.

[0171] The connection attributes corresponding to the marker node can be in regular mode or value matching mode, etc.

[0172] Another possible way to filter the above conditions is to have a target tag attribute. In this case, the status data can refer to the tag information of the target user, and the corresponding operation can be to determine whether the target user has set a target tag attribute, etc.

[0173] In addition, as another optional implementation, multiple target nodes may also include all-class nodes, and the corresponding execution operation may be to indicate that at least one target node with which it has a connection relationship is to be executed.

[0174] In addition, it may include a call node, whose corresponding execution operation could be an instruction to call a third-party service to perform a target operation. The call node can provide a standard interface, facilitating expansion to integrate more third-party services to perform corresponding operations.

[0175] It should be noted that the target node can be set according to actual needs. The above is only an example to illustrate possible implementations, and this application is not limited to this.

[0176] The attribute data may also include orchestration attributes, which are global attributes for rule orchestration information. Orchestration attributes may include, for example, one or more of the following: target audience, orchestration cycle, and predetermined time range.

[0177] Therefore, the information can be arranged according to the arrangement cycle; or, the information can be arranged according to the rules within a predetermined time range; or, the information can be arranged according to the arrangement cycle within a predetermined time range.

[0178] In some embodiments, the above-mentioned execution of the corresponding execution operation according to the node attributes to obtain the execution result for any target node to be executed may include:

[0179] According to the arrangement cycle, information is arranged periodically within a predetermined time range according to the rules;

[0180] For any target node to be executed, perform the corresponding execution operation according to the node attributes to obtain the execution result.

[0181] In practical applications, target users may belong to multiple groups. Therefore, in some embodiments, according to the attribute data and connection relationships in the rule-arranged information, the execution operations corresponding to multiple target nodes are performed respectively to achieve the target processing operations for the target user, including:

[0182] Based on the target user's affiliation to multiple groups, determine at least one rule arrangement information that the target user matches;

[0183] For any given rule arrangement information, according to the attribute data and connection relationships in the rule arrangement information, execute the corresponding execution operations of multiple target nodes respectively, so as to achieve the target processing operation for the target user.

[0184] In other words, it can orchestrate information for each rule matched by the target user and execute the corresponding target processing operation.

[0185] In addition, to improve usability, in some embodiments, the method may further include:

[0186] Based on the rules, the attribute data and connection relationships in the information are arranged, and for the test user, the corresponding execution operations of multiple target nodes are executed to obtain the test results.

[0187] Optionally, the test results can be sent to the target personnel for review and analysis to determine whether to adjust the rule arrangement information.

[0188] Alternatively, the above-mentioned correspondence between rule arrangement information and target users that meet the target population can be established as follows: when the test results meet the test requirements, the correspondence between rule arrangement information and target users that meet the target population can be established.

[0189] In some embodiments, for any target node to be executed, performing the corresponding execution operation according to the node attributes to obtain the execution result may include:

[0190] For any target node to be executed, if the execution conditions configured in the node attributes are met, the corresponding execution operation is executed to obtain the execution result.

[0191] The execution condition could be, for example, the occurrence of a target event, such as displaying a certain page; or it could include the execution time; or it could be that a target user performs a target action. The corresponding operation is executed only if the current time meets the execution time requirement. Of course, the execution condition can be set according to the actual situation.

[0192] To facilitate execution, the server can cache the target node where the target user is currently located, and can wait for the execution conditions to be met before triggering the corresponding execution operation. It can also perform judgment logic based on connection attributes to determine the next target node to be executed.

[0193] Figure 3 A flowchart illustrating an embodiment of an orchestration method provided in this application is shown. The technical solution of this embodiment can be executed by a client, and the method may include the following steps:

[0194] 301: In response to the orchestration operations of the target personnel, determine the configured multiple target nodes, the connection relationships between the multiple target nodes, and the attribute data of the multiple target nodes.

[0195] 302: Sends multiple target nodes, the connection relationships between the multiple target nodes, and attribute data as rule orchestration information to the server.

[0196] Among them, the rule orchestration information is used to establish the correspondence between the rule orchestration information and the target users that meet the target group, and to trigger the execution of multiple target nodes according to the attribute data and connection relationship in the rule orchestration information, so as to realize the target processing operation for the target users.

[0197] The specific execution of the rule arrangement information can be found in the above embodiments, and will not be repeated here.

[0198] In this embodiment, the target personnel can perform orchestration operations through the client based on their actual processing needs for the target population. This generates rule orchestration information consisting of multiple target nodes, the connection relationships between these nodes, and the attribute data of the target nodes. The server can establish a correspondence between the rule orchestration information and target users that match the target population. Therefore, according to the attribute data and connection relationships in the rule orchestration information, the execution operations corresponding to each target node can be executed to achieve the target processing operation for the target user. In this embodiment, the target personnel can generate rule orchestration information by performing orchestration operations on the target nodes on the client based on actual needs, thus ensuring processing effectiveness. Furthermore, no coding is required, making the operation simple and the development cost low.

[0199] In some embodiments, to further improve operational convenience, in response to the arrangement operations of target personnel, determining the configured multiple target nodes, the connection relationships between the multiple target nodes, and the attribute data of the multiple target nodes may include:

[0200] Displays the rule arrangement interface;

[0201] Multiple node controls are provided in the rule orchestration results;

[0202] In response to selection operations for multiple node controls, multiple target nodes are displayed in the rule orchestration interface;

[0203] In response to connection operations targeting multiple target nodes, the connection relationships between the multiple target nodes are determined;

[0204] In response to configuration operations targeting multiple target nodes, determine the attribute data.

[0205] These multiple node controls can be categorized by node type, such as start nodes, end nodes, branching nodes, and processing nodes. Processing nodes can be further divided into reach nodes, delay nodes, filter nodes, marker nodes, and experiment nodes. Users can select target nodes based on their actual needs and understanding, and perform connection operations to establish connections between target nodes, as well as perform configuration operations to configure attribute data.

[0206] In some embodiments, the rule orchestration interface may include a selection area, an editing area, and a configuration area;

[0207] The rule arrangement results provide multiple node controls, including providing multiple node controls in the selected area;

[0208] In response to a selection operation on multiple node controls, displaying multiple target nodes in the rule orchestration interface includes: in response to a drag operation on multiple node controls from the selection area to the editing area, displaying the dragged target nodes in the editing area;

[0209] Determining the connection relationship between multiple target nodes in response to a connection operation targeting multiple target nodes includes: determining the connection relationship between multiple target nodes in response to a connection operation targeting multiple target nodes in the editing area;

[0210] In response to configuration operations targeting multiple target nodes, the attribute data determined includes:

[0211] In response to the first configuration operation in the configuration area, determine the orchestration attributes;

[0212] In response to a touch operation on any target node, display node configuration prompts for the target node in the configuration area;

[0213] Based on the second configuration operation triggered by the configuration prompt information, determine the node attributes corresponding to the target node;

[0214] In response to a touch operation on any connection relationship, display connection attribute configuration prompts for the connection relationship in the configuration area;

[0215] Based on the third configuration operation triggered by the connection attribute configuration prompt information, the node attributes corresponding to the connection relationship are determined.

[0216] For ease of understanding, such as Figures 4a-4bThe diagram illustrates a rule arrangement interface, which may include a selection area 401, an editing area 402, and a configuration area 403. The selection area 401 provides multiple node controls 404, which users can drag and drop to display the selected target nodes in the editing area 402. In the editing area 402, users can perform a connection operation on any two target nodes to establish a connection relationship between them, which can be represented by a connecting line between the two target nodes.

[0217] In some embodiments, a directed connection line can be established between the first target node and the second target node for any two target nodes out of a plurality of target nodes, such that the rule arrangement information can be stored on the server in the form of a directed acyclic graph.

[0218] In configuration area 403, such as Figure 4a As shown, a layout attribute configuration control 405 can be displayed, allowing the target user to perform a first configuration operation to determine the layout attributes. Global configuration prompts can be displayed in the configuration area 403; when these global configuration prompts are triggered, the layout attribute configuration control 405 can be displayed.

[0219] For any touch operation on a target node, in configuration area 403, such as Figure 4b As shown, a node attribute configuration control 405 can be displayed for the target node. This allows the target user to perform a second configuration operation to confirm the node attributes.

[0220] Furthermore, for any touch operation related to a connection, configuration controls for the connection attributes can be displayed in configuration area 403. This allows the user to perform a third configuration operation to determine the connection attributes.

[0221] In some embodiments, sending multiple target nodes, the connection relationships between the multiple target nodes, and attribute data as rule orchestration information to the server may include:

[0222] In response to the save operation performed on the rule orchestration interface, multiple target nodes, the connection relationships between the multiple target nodes, and attribute data are sent to the server as rule orchestration information.

[0223] like Figures 4a-4b As described above, the rule arrangement interface can also display a save prompt message 406. The save operation can be triggered by the save prompt message 406, and the save prompt message can be implemented in the form of a control.

[0224] In some embodiments, determining the connection relationship between multiple target nodes in response to a connection operation targeting multiple target nodes may include:

[0225] In response to a connection operation that points from the first target node to the second target node among any two target nodes, the connection relationship between the two target nodes is determined if preset rules are met.

[0226] The preset rule could be, for example, that the first target node is the starting node, and the second target node is not the starting node, etc., to ensure that the rule arrangement information can be executed.

[0227] In practical applications, the technical solutions of this application embodiment can be applied to object recommendation scenarios. For ease of understanding, the following is combined with... Figure 5 The scene interaction diagram shown illustrates the technical solution of the embodiments of this application.

[0228] Client 101 can display a rule orchestration interface, providing multiple node controls. Users can select target nodes based on their understanding and actual needs, and execute connection operations to establish directed connections between multiple target nodes. Configuration operations can also be performed to define attribute data.

[0229] For example, a target audience of new computer users might want to recommend products via instant messaging. After a 60-second delay, the system checks if the user has viewed the initial message. If not, it checks if the user has linked their email account. If so, a second message is sent via email. The process ends if the user has viewed the initial message and if they haven't linked their email account. Based on this requirement, the target audience can perform corresponding selection and connection actions, ultimately achieving the following: Figure 6 The diagram shows a directed acyclic graph.

[0230] The orchestration attributes configured for the target personnel can include the audience identifier of "new installers". In addition, the orchestration period and the predetermined time range can be configured. The predetermined time range can be an unlimited time range or a specified limited actual range.

[0231] right Figure 6 The node attributes configured for the middle reach node 601 may include, for example, the first reach message, the reach method being instant messaging and providing an instant messaging account, and may also include the reach timing.

[0232] right Figure 6 The connection properties configured in Connection Relationship 1 can be in normal mode.

[0233] right Figure 6 The node attributes configured for the delay node 602 may include, for example, the delay time.

[0234] right Figure 6 The connection properties configured in connection relationship 2 can be in normal mode.

[0235] right Figure 6 The node attributes configured for the middle routing node 603 may include, for example, routing conditions: view the first contact text.

[0236] right Figure 6 The connection attribute configured for connection relationship 3 can be in conditional matching mode with a matching line value of "yes". The connection attribute configured for connection relationship 4 can also be in conditional matching mode with a matching line value of "no".

[0237] right Figure 6 The node attributes configured for the 604 routing node can include, for example, routing conditions such as binding an email account.

[0238] right Figure 6 The connection attribute configured for connection relationship 5 can be in conditional matching mode with a matching line value of "yes". The connection attribute configured for connection relationship 6 can also be in conditional matching mode with a matching line value of "no".

[0239] right Figure 6 The node attributes configured for the middle-reach node 605 may include, for example, the second reach message, the reach method as email, and the reach timing.

[0240] right Figure 6 The connection attribute configured in connection relationship 7 can be in conditional matching mode with a matching line value of "yes". The connection attribute configured in connection relationship 8 can be in conditional matching mode with a matching line value of "no".

[0241] By using the above-mentioned rules to arrange information, multiple outreach rules (sending outreach text via email and sending outreach text via instant messaging) can be linked together. Furthermore, users can be categorized and outreached based on traffic distribution conditions to achieve personalized outreach and a unique experience for each individual. This makes outreach operations more accurate and has low development costs. Target users only need to perform drag-and-drop operations, without the need for developers to write scripts.

[0242] The rule arrangement information generated by client 101 can be sent to server 102.

[0243] The server 102 can determine the directed acyclic graph corresponding to the rule arrangement information, and thus use the directed acyclic graph method to save the rule arrangement information for each user in the new installation group.

[0244] The server 102 can orchestrate information for each rule matched by each user and execute corresponding operations for each rule orchestration information to achieve different target processing operations for the user.

[0245] In this embodiment of the application, the rule arrangement interface is graphical and visual, which has a low learning cost for the target users. They can set rules by simply operating the interface and do not need to write script code. This not only reduces the development cost and allows the target users to quickly set rules, but also improves development efficiency.

[0246] Furthermore, the embodiments of this application maintain rule arrangement information for each user, which can fully realize user reach. Through the condition settings of different node types mentioned above, the understanding of user status can be enhanced, repeated reach can be avoided, and the execution result of the previous target node can guide the execution of the current target node. The execution results for different users may be different, so personalized triggering can also be realized, and the content and timing of reach can be tailored to each individual.

[0247] Figure 7 This application provides a schematic diagram of the structure of a processing apparatus according to one embodiment. The apparatus may include:

[0248] The information acquisition module 701 acquires the rule orchestration information sent by the client; the rule orchestration information includes multiple target nodes configured for the target audience, the connection relationships between the multiple target nodes, and the attribute data corresponding to the multiple target nodes;

[0249] The relationship establishment module 702 is used to establish the correspondence between rule arrangement information and target users that match the target audience.

[0250] The rule processing module 703 is used to execute the corresponding execution operations of multiple target nodes according to the attribute data and connection relationships in the rule arrangement information, so as to realize the target processing operation for the target user.

[0251] In some embodiments, the device may further include:

[0252] The module provides a rule orchestration interface to the client; the rule orchestration interface provides multiple node controls; multiple target nodes are determined based on the target user's selection operations on the multiple node controls; the connection relationship is determined based on the target user's connection operations on the multiple target nodes; and the attribute data is determined based on the target user's configuration operations.

[0253] In some embodiments, the attribute data includes node attributes and connection attributes corresponding to multiple target nodes respectively;

[0254] Specifically, the rule processing module performs corresponding execution operations according to the node attributes for any target node to be executed, and obtains the execution result; based on the execution result and the matching results of different connection attributes, it determines the next target node to be executed.

[0255] In some embodiments, the rule processing module performs corresponding execution operations according to the node attributes for any target node to be executed to obtain the execution result, including:

[0256] For any target node to be executed, if the target node is the starting node, the processing flow corresponding to the rule orchestration information is initiated; if the target node is the ending node, the processing flow corresponding to the rule orchestration information is terminated; if the target node is a routing node, the status data corresponding to the target user is detected according to the routing conditions configured in the node attributes, and the status data is matched with the routing conditions to obtain the execution result; if the target node is a processing node, the corresponding processing operation is executed according to the processing method configured in the node attributes.

[0257] In some embodiments, the processing node may include an reach node, a delay node, a filter node, a marker node, or an experiment node; when the target node is a processing node, the rule processing module performs the corresponding processing operation according to the processing method configured in the node attributes, including:

[0258] When the target node is a reach node, the reach timing is configured in the node attributes, and the reach method corresponding to the target node is used to send the reach text configured in the node attributes to the target user in order to recommend the target object to the target user.

[0259] If the target node is a delayed node, perform the timing operation according to the delay time configured in the node properties;

[0260] If the target node is a filter node, the target user is matched with the filter conditions configured in the node attributes.

[0261] If the target node is an experimental node, determine the experimental group to which the target user belongs according to the experimental attributes configured in the node attributes;

[0262] If the target node is a tag node, set the tag attributes for the target user according to the tag information configured in the node attributes.

[0263] In some embodiments, the offloading conditions include any of the following implementations:

[0264] Meets the predetermined user level; executes the predetermined user behavior; a predetermined event occurs; the user's rights usage status is in the predetermined state; the target behavior is executed a predetermined number of times.

[0265] In some embodiments, the attribute data includes programming attributes; programming attributes include target audience, programming cycle, and predetermined time range;

[0266] The rule processing module performs corresponding execution operations according to the node attributes for any target node to be executed, including: periodically executing rule orchestration information within a predetermined time range according to the orchestration cycle; and performing corresponding execution operations according to the node attributes for any target node to be executed, in order to obtain the execution result.

[0267] In some embodiments, the rule processing module performs corresponding execution operations according to the node attributes to obtain execution results for any target node to be executed, including: for any target node to be executed, if the execution conditions configured in the node attributes are met, performing corresponding execution operations to obtain execution results.

[0268] In some embodiments, the relationship establishment module specifically generates a directed acyclic graph based on the attribute data of multiple target nodes in the rule arrangement information and the connection relationship between the multiple target nodes; and establishes the correspondence between the directed acyclic graph and the target users that match the target group.

[0269] Figure 7 The processing device can perform Figure 2 The implementation principle and technical effects of the processing method described in the illustrated embodiments will not be repeated here. The specific methods by which each module and unit of the processing device in the above embodiments performs its operations have been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0270] Figure 8 This application provides a schematic diagram of the structure of an arrangement apparatus according to one embodiment. The apparatus may include:

[0271] The orchestration module 801 is used to respond to the orchestration operation of the target personnel, determine the configured multiple target nodes, the connection relationship between the multiple target nodes, and the attribute data of the multiple target nodes; the attribute data includes the target group that the multiple target nodes are targeting;

[0272] The sending module 802 is used to send multiple target nodes, the connection relationships between the multiple target nodes, and attribute data as rule orchestration information to the server. The rule orchestration information is used to establish the correspondence between the rule orchestration information and the target users that meet the target group, and to trigger the execution of the execution operations corresponding to the multiple target nodes according to the attribute data and connection relationships in the rule orchestration information, so as to realize the target processing operation for the target users.

[0273] In some embodiments, the orchestration module may specifically display a rule orchestration interface; provide multiple node controls in the rule orchestration results; display multiple target nodes in the rule orchestration interface in response to a selection operation on the multiple node controls; determine the connection relationship between the multiple target nodes in response to a connection operation on the multiple target nodes; and determine attribute data in response to a configuration operation on the multiple target nodes.

[0274] In some embodiments, the rule orchestration interface includes a selection area, an editing area, and a configuration area;

[0275] The orchestration module provides multiple node controls in the rule orchestration results, including multiple node controls in the selection area;

[0276] The orchestration module responds to selection operations for multiple node controls by displaying multiple target nodes in the rule orchestration interface, including responding to drag operations for multiple node controls from the selection area to the editing area by displaying the dragged target nodes in the editing area.

[0277] The orchestration module responds to connection operations for multiple target nodes and determines the connection relationships between multiple target nodes, including: responding to connection operations for multiple target nodes in the editing area and determining the connection relationships between multiple target nodes;

[0278] The orchestration module responds to configuration operations for multiple target nodes and determines attribute data including: responding to a first configuration operation in the configuration area to determine orchestration attributes; responding to a touch operation for any target node to display node configuration prompts for the target node in the configuration area; responding to a second configuration operation triggered by the configuration prompts to determine the node attributes corresponding to the target node; responding to a touch operation for any connection relationship to display connection attribute configuration prompts for the connection relationship in the configuration area; and responding to a third configuration operation triggered by the connection attribute configuration prompts to determine the node attributes corresponding to the connection relationship.

[0279] Figure 8 The aforementioned arrangement device can perform Figure 3 The implementation principle and technical effects of the arrangement method described in the illustrated embodiments will not be repeated here. The specific methods by which each module and unit of the arrangement device in the above embodiments performs its operations have been described in detail in the embodiments related to this method, and will not be elaborated upon here.

[0280] This application also provides a computing device, such as... Figure 9 As shown, the computing device may include a storage component 901 and a processing component 902;

[0281] Storage component 901 stores one or more computer instructions, wherein the one or more computer instructions are invoked and executed by processing component 902 to achieve, for example, Figure 2 The processing method or implementation described in the illustrated embodiment is as follows: Figure 3 The arrangement method described in the illustrated embodiment.

[0282] Of course, computing devices may also include other components, such as input / output interfaces and communication components.

[0283] In the case where the processing component in the computing device is used to implement the information display method shown in Figure 4, the computing device may also include a display component to perform the corresponding display operation.

[0284] Input / output interfaces provide interfaces between processing components and peripheral interface modules, which can be output devices, input devices, etc. Communication components are configured to facilitate wired or wireless communication between computing devices and other devices.

[0285] The processing component 902 may include one or more processors to execute computer instructions to complete all or part of the steps in the above-described method. Alternatively, the processing component may be implemented as one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the above-described method.

[0286] Storage component 901 is configured to store various types of data to support operations at the terminal. The storage component can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0287] The display component can be an electroluminescent (EL) element, a liquid crystal display or a microdisplay with a similar structure, or a retina-direct display or a similar laser scanning display.

[0288] It should be noted that the above-mentioned computing devices implement Figure 2 In the case of the processing method described in the illustrated embodiment, it can be a physical device or an elastic computing host provided by a cloud computing platform. It can be implemented as a distributed cluster composed of multiple servers or terminal devices, or as a single server or a single terminal device.

[0289] The above computing devices achieve Figure 3 In the case of the arrangement method shown, it can be specifically implemented as an electronic device. An electronic device can refer to a device used by a user that has the computing, internet access, communication and other functions required by the user, such as a mobile phone, tablet computer, personal computer, wearable device, etc.

[0290] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a computer, can perform the above-described functions. Figure 2 The processing method or implementation of the above embodiments is shown. Figure 3 The arrangement method of the illustrated embodiment. The computer-readable medium may be included in the electronic device described in the above embodiments; or it may exist independently and not assembled into the electronic device.

[0291] This application also provides a computer program product, which includes a computer program carried on a computer-readable storage medium, and the computer program, when executed by a computer, can perform the above-described functions. Figure 2 The processing method or implementation of the above embodiments is shown. Figure 3 The illustrated embodiment describes an arrangement method. In such an embodiment, the computer program may be downloaded and installed from a network, and / or installed from a removable medium. When the computer program is executed by a processor, it performs various functions defined in the system of this application.

[0292] It should be noted that the embodiments of this application may involve the use of user data. In practical applications, user-specific personal data may be used in the scheme described herein within the scope permitted by applicable laws and regulations, provided that it complies with the applicable laws and regulations of the country (e.g., with the user's explicit consent, with the user being properly notified, etc.).

[0293] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0294] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0295] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0296] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A processing method, characterized in that, include: Obtain the rule orchestration information sent by the client; The rule orchestration information includes multiple target nodes configured for the target audience, the connection relationships between the multiple target nodes, and the attribute data corresponding to the multiple target nodes; the target audience includes a set of users with the same characteristics, and the users are classified into one or more groups based on characteristics in the online system, and the characteristics change with the user's behavior in the online system; Establish the correspondence between the rule arrangement information and the target users who conform to the target group; According to the attribute data in the rule-arranged information and the connection relationship, the execution operations corresponding to the multiple target nodes are executed respectively to realize the target processing operation for the target user.

2. The method according to claim 1, characterized in that, Also includes: Provide a rule orchestration interface to the client; The rule arrangement interface provides multiple node controls; the multiple target nodes are determined based on the selection operations of the target personnel on the multiple node controls; the connection relationships are determined based on the connection operations of the target personnel on the multiple target nodes; and the attribute data are determined based on the configuration operations of the target personnel.

3. The method according to claim 1, characterized in that, The attribute data includes the node attributes and connection attributes corresponding to the plurality of target nodes respectively; The step of executing the execution operations corresponding to the multiple target nodes according to the attribute data and the connection relationship, so as to realize the target processing operation for the target user, includes: For any target node to be executed, perform the corresponding execution operation according to the node attributes to obtain the execution result; Based on the execution results and the matching results of different connection attributes, the next target node to be executed is determined.

4. The method according to claim 3, characterized in that, The step of performing corresponding execution operations according to the node attributes to obtain execution results for any target node to be executed includes: For any target node to be executed, if the target node is the starting node, the processing flow corresponding to the rule orchestration information is initiated. If the target node is an end node, the processing flow corresponding to the rule arrangement information is terminated. If the target node is a traffic splitting node, the status data corresponding to the target user is detected according to the traffic splitting conditions configured in the node attributes, and the status data is matched with the traffic splitting conditions to obtain the execution result; If the target node is a processing node, the corresponding processing operation is performed according to the processing method configured in the node attributes.

5. The method according to claim 4, characterized in that, The processing nodes include reach nodes, delay nodes, filter nodes, tag nodes, or experiment nodes; When the target node is a processing node, the corresponding processing operation is performed according to the processing method configured in the node attributes, including: When the target node is a reach node, according to the reach timing configured in the node attributes, the reach method corresponding to the target node is used to send the reach text configured in the node attributes for the target object to the target user, so as to recommend the target object to the target user; If the target node is a delayed node, a timing operation is performed according to the delay time configured in the node attributes; If the target node is a filter node, the target user is matched with the filter conditions configured in the node attributes. If the target node is an experimental node, the experimental group to which the target user belongs is determined according to the experimental attributes configured in the node attributes; If the target node is a tag node, the tag attributes are set for the target user according to the tag information configured in the node attributes.

6. The method according to claim 4, characterized in that, The traffic splitting conditions include any of the following implementation methods: Meets the predetermined user level; executes the predetermined user behavior; a predetermined event occurs; the user's rights usage status is in the predetermined state; the target behavior is executed a predetermined number of times.

7. The method according to claim 3, characterized in that, The attribute data includes programming attributes; the programming attributes include the target audience, programming cycle, and predetermined time range. The step of performing corresponding execution operations according to the node attributes to obtain execution results for any target node to be executed includes: According to the aforementioned arrangement cycle, the rule arrangement information is periodically executed within the predetermined time range; For any target node to be executed, perform the corresponding execution operation according to the node attributes to obtain the execution result.

8. The method according to claim 1, characterized in that, The step of arranging the attribute data in the information according to the rules and the connection relationships, and executing the execution operations corresponding to the multiple target nodes respectively, to realize the target processing operation for the target user, includes: Based on the multiple groups to which the target user belongs, determine at least one rule arrangement information that the target user matches; For any rule arrangement information, according to the attribute data and connection relationship in the rule arrangement information, the execution operations corresponding to the multiple target nodes are executed respectively to realize the target processing operation for the target user.

9. The method according to claim 1, characterized in that, The process of establishing the correspondence between the rule arrangement information and the target users who fit the target group includes: Based on the attribute data of multiple target nodes in the rule arrangement information and the connection relationships between the multiple target nodes, a directed acyclic graph is generated; Establish the correspondence between the directed acyclic graph and the target users that match the target population.

10. An arrangement method, characterized in that, include: In response to the arrangement operation of the target personnel, the system determines the configured multiple target nodes, the connection relationships between the multiple target nodes, and the attribute data of the multiple target nodes; the attribute data includes the target population targeted by the multiple target nodes; the target population includes a set of users with the same characteristics, the users are classified into one or more groups according to characteristics in the online system, and the characteristics change with the user's behavior in the online system; The multiple target nodes, the connection relationships between the multiple target nodes, and the attribute data are sent to the server as rule orchestration information. The rule orchestration information is used to establish the correspondence between the rule orchestration information and the target users that conform to the target group, and to trigger the execution of the execution operations corresponding to the multiple target nodes according to the attribute data and the connection relationships in the rule orchestration information, so as to realize the target processing operation for the target users.

11. The method according to claim 10, characterized in that, The process of determining the configured multiple target nodes, the connection relationships between the multiple target nodes, and the attribute data of the multiple target nodes in response to the arrangement operation of the target personnel includes: Displays the rule arrangement interface; The rule arrangement interface provides multiple node controls; In response to a selection operation on the plurality of node controls, a plurality of target nodes are displayed on the rule orchestration interface; In response to connection operations targeting the plurality of target nodes, the connection relationships between the plurality of target nodes are determined; In response to configuration operations for the plurality of target nodes, attribute data is determined.

12. The method according to claim 11, characterized in that, The rule arrangement interface includes a selection area, an editing area, and a configuration area; The provision of multiple node controls in the rule arrangement interface includes: providing multiple node controls in the selection area; The step of displaying multiple target nodes in the rule arrangement interface in response to a selection operation of the multiple node controls includes: displaying the dragged multiple target nodes in the editing area in response to a drag operation of the multiple node controls from the selection area to the editing area; Determining the connection relationship between the plurality of target nodes in response to a connection operation for the plurality of target nodes includes: determining the connection relationship between the plurality of target nodes in response to a connection operation for the plurality of target nodes in the editing area; The determination of attribute data in response to the configuration operation for the plurality of target nodes includes: In response to a first configuration operation in the configuration area, orchestration attributes are determined; In response to a touch operation on any target node, a node configuration prompt message for the target node is displayed in the configuration area; Based on the second configuration operation triggered in response to the configuration prompt information, the node attributes corresponding to the target node are determined; In response to a touch operation for any connection relationship, a connection attribute configuration prompt message for the connection relationship is displayed in the configuration area; Based on the third configuration operation triggered by the configuration prompt information for the connection attribute, the node attribute corresponding to the connection relationship is determined.

13. A computing device, characterized in that, It includes a processing component and a storage component; the storage component stores one or more computer instructions; the one or more computer instructions are invoked and executed by the processing component to implement the processing method as described in any one of claims 1 to 9 or the orchestration method as described in any one of claims 10 to 12.

14. A computer-readable storage medium, characterized in that, The computer program is stored thereon, and when executed by a computer, the computer program implements the processing method as described in any one of claims 1 to 9 or the arrangement method as described in any one of claims 10 to 12.

Images