WO2019019373A1 - Event processing method and terminal device - Google Patents

Event processing method and terminal device Download PDF

Info

Publication number
WO2019019373A1
WO2019019373A1 PCT/CN2017/104540 CN2017104540W WO2019019373A1 WO 2019019373 A1 WO2019019373 A1 WO 2019019373A1 CN 2017104540 W CN2017104540 W CN 2017104540W WO 2019019373 A1 WO2019019373 A1 WO 2019019373A1
Authority
WO
WIPO (PCT)
Prior art keywords
event
rule
preset
user
condition
Prior art date
Application number
PCT/CN2017/104540
Other languages
French (fr)
Chinese (zh)
Inventor
南菊松
张宇
Original Assignee
平安科技(深圳)有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技(深圳)有限公司 filed Critical 平安科技(深圳)有限公司
Publication of WO2019019373A1 publication Critical patent/WO2019019373A1/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • G06Q30/0201Market modelling; Market analysis; Collecting market data

Definitions

  • This application belongs to the field of data processing, and in particular, to an event processing method and a terminal device.
  • Events refer to the user's operating behavior on a specified page or client. Event marketing is in the forefront of the Internet, finance, etc. The industry generally collects user events and customizes marketing campaigns based on these events.
  • the current event processing method is generally directed to an individual event.
  • the action corresponding to the event is performed. Since the obtained information is one-sided, the effectiveness of the marketing activity is relatively better. Low, the user gets a poor experience.
  • the embodiment of the present application provides an event processing method and a terminal device, so as to solve the problem that the existing marketing event for a single event has low effectiveness and a poor user experience. problem.
  • a first aspect of the embodiments of the present application provides an event processing method, which may include:
  • the executing the event processing procedure according to the target event rule includes:
  • the target event rule is a first type of event rule, determining whether the first event and the second event in the acquired respective events satisfy the first condition, the first condition being the first
  • the second event is also triggered in the preset first inter-day interval after the event is triggered, and the first event and the second event are both corresponding to the first user;
  • the target event rule is a second type of event rule, determining whether the third event and the fourth event in the acquired respective events satisfy the second condition, and the second condition is the third The fourth event is not triggered in the preset second interval after the event is triggered, and the third event and the fourth event are both corresponding to the second user;
  • a second aspect of the embodiments of the present application provides a computer readable storage medium, where the computer readable storage medium stores computer readable instructions, and the computer readable instructions are executed by a processor, and the following steps are implemented:
  • the executing the event processing procedure according to the target event rule includes:
  • the target event rule is a first type of event rule, determining whether the first event and the second event in the acquired respective events satisfy the first condition, where the first condition is the first
  • the second event is also triggered within a preset first inter-day interval after the event is triggered, the first event and the second event Each piece corresponds to the first user;
  • the target event rule is a second type of event rule, determining whether the third event and the fourth event in the acquired respective events satisfy the second condition, and the second condition is the third The fourth event is not triggered in the preset second interval after the event is triggered, and the third event and the fourth event are both corresponding to the second user;
  • a third aspect of an embodiment of the present application provides an event processing terminal device including a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, the processing The computer executes the computer readable instructions to implement the following steps:
  • the executing the event processing procedure according to the target event rule includes:
  • the target event rule is a first type of event rule, determining whether the first event and the second event in the acquired respective events satisfy the first condition, where the first condition is the first
  • the second event is also triggered in the preset first inter-day interval after the event is triggered, and the first event and the second event are both corresponding to the first user;
  • the target event rule is a second type of event rule, determining whether the third event and the fourth event in the acquired respective events satisfy the second condition, and the second condition is the third Event is triggered The fourth event is not triggered in the second preset interval, and the third event and the fourth event are both corresponding to the second user;
  • a fourth aspect of the embodiments of the present application provides an event processing program, including:
  • an event obtaining module configured to acquire each event that is triggered within a preset processing interval
  • a target event rule selection module configured to select an event rule from the preset event rule base as the current target event rule, where the event rule is a sequential dependency relationship between the two events;
  • an event processing module configured to execute an event processing process according to the target event rule
  • the event processing module includes:
  • a first condition determining unit configured to determine, if the target event rule is a first type of event rule, determining whether the first event and the second event in the acquired respective events satisfy the first condition,
  • the first condition is that the second event is also triggered in the preset first inter-day interval after the first event is triggered, and the first event and the second event are both corresponding to the first user;
  • a first action execution unit configured to execute a preset first action for the first user if the first event and the second event satisfy the first condition
  • a second condition determining unit configured to determine, if the target event rule is a second type of event rule, determining whether the third event and the fourth event in the acquired respective events satisfy the second condition, The second condition is that the fourth event is not triggered in the preset second interval after the third event is triggered, and the third event and the fourth event are both corresponding to the second user;
  • the second action execution unit is configured to execute a second action preset for the second user if the third event and the fourth event satisfy the second condition.
  • the embodiment of the present application acquires each event that is triggered within a preset processing interval, and traverses each event rule from a preset event rule base.
  • the current target event rule performs an event processing flow according to the target event rule.
  • the executing the event processing process according to the target event rule includes: if the target event rule is the first type of event a rule, and the first event and the second event satisfy the first condition, and then perform a preset first action; if the target event rule is a second type event rule, and the third event and the fourth event satisfy the second condition , the second action of the preset is executed.
  • two events with dependencies are successively triggered (ie, the second event is also triggered in the first inter-time interval after the first event is triggered). And two events with dependencies are not triggered (ie, the fourth event is not triggered during the second inter-day interval after the third event is triggered).
  • the event rule type when the event rule in the preset event rule base is satisfied, the corresponding action is performed for the marketing activity, and the marketing activity performed by the two events is fully considered due to the sequential relationship between the two events. It has higher effectiveness and can also give users a better experience.
  • FIG. 1 is a flow chart of an embodiment of an event processing method according to an embodiment of the present application.
  • FIG. 2 is a schematic flow chart of an event processing method step 103 in an application scenario according to an embodiment of the present application
  • FIG. 3 is a flow chart of an event processing method step 1032 in an application scenario according to an embodiment of the present application.
  • FIG. 4 is a flow chart of an event processing method step 1034 in an application scenario according to an embodiment of the present application.
  • FIG. 5 is a schematic block diagram of an event processing terminal device according to an embodiment of the present disclosure.
  • FIG. 6 is a functional block diagram of an event processing program according to an embodiment of the present application.
  • the embodiment of the present application mainly performs a corresponding marketing action for the sequential dependency relationship between two events. For example, the user first clicks the verification code button on a company webpage to verify, and then one minute later. By clicking the registration button to register, you can determine that the user may have a greater interest in the company's services or products. You can then send the text message to welcome the user to join and introduce the user to the company's services or product information.
  • the user has clicked on a company's registration button, but in the next two hours, the user has not further logged into the company's home page for browsing, then it can be judged that the user may have encountered some problems or generated Some doubts, you can arrange customer service staff to follow up, and actively contact the user to help users solve problems and eliminate their doubts.
  • an embodiment of an event processing method in an embodiment of the present application may include:
  • Step S101 Acquire various events that are triggered within a preset processing interval.
  • an intermittent centralized processing manner is adopted for the event, and the events accumulated in the processing interval are collectively processed at regular processing intervals.
  • an event corresponding to a preset event code is captured by a preset plug-in.
  • a lightweight, non-intrusive front-end javascript capture plugin can be used to obtain operational events of the user on the corporate web page or client.
  • the event code is a unique identifier of the event, and the event codes of different events are different from each other.
  • Each event code may have an event description to indicate its business meaning. For example, a button on the enterprise webpage is configured with an event code of abc, the same ⁇ also configures the event description as "click the login button", then once the user clicks the button, the plugin will be triggered to capture the user's click event.
  • the event event is encoded as abc and the description is "click the login button" .
  • the user identification, the event encoding, and the event trigger are added to the captured event.
  • the user identifier is a unique identifier of the user, and the user identifiers of different users are different from each other.
  • the mobile phone number, the email address, the ID card, the micro signal, and the like can be used as the user identifier.
  • the event is stored in a preset event library.
  • the event library is a set of events that are updated, and the event record may be arranged according to the event triggering time, or may be arranged according to the event code or the user identifier. record.
  • Step S102 Select an event rule from the preset event rule base as the current target event rule.
  • the event rule is a sequential dependency relationship between two events, and is a criterion by which the acquired event is processed.
  • the event rule base is a set of preset event rules. In this embodiment, the event rule base may be adjusted according to actual conditions. For example, an event rule may be added, an event rule may be deleted, or an event rule may be modified.
  • Step S103 Perform an event processing procedure according to the target event rule.
  • step S103 may include:
  • Step S1031 Determine whether the target event rule is a first type event rule.
  • the event rules are divided into two types, that is, a first type event rule and a second type event rule, and the first type event rule is directed to two events having a dependency relationship being successively
  • the pre-event is triggered and the post-event is triggered.
  • the second type of event rule is directed to the case where two events with dependencies are not triggered consecutively, that is, the pre-event is triggered, and the post-event is not triggered.
  • step S1032 is performed; if the target event rule is the second type event rule, step S1034 is performed.
  • Step S1032 Determine whether the first event and the second event in the acquired respective events satisfy the first condition.
  • the first condition is that the second event is also triggered in a preset first inter-time interval after the first event is triggered, and the first event and the second event are both first User correspondence.
  • step S1032 may specifically include:
  • Step S10321 Search for the second event in the acquired respective events.
  • Step S10322 determining whether the second event is found in the acquired respective events. [0073] If the second event is not found in the acquired respective events, step S10326 is performed, and if the second event is found in the event library, step S10323 is performed.
  • Step S10323 Search for the first event that is the same as the user identifier of the second event in the obtained each event.
  • Step S10324 Determine whether a first event that is the same as the user identifier of the second event is found in the acquired respective events.
  • the first event and the second event are two different events.
  • the first event is a pre-event
  • the second event is a post-event, that is, the first event should be before the second event.
  • the first event may be an event that the user clicks the verification code button
  • the second event may be an event that the user clicks the registration button.
  • the inter-turn interval between the two should be less than or equal to a predetermined inter-turn interval, that is, the first inter-turn interval.
  • the first inter-turn interval a specific inter-segment
  • the event triggering time of the second event is 11:00:00
  • the first inter-day interval is 2 hours, and only the period of 9:00:00 to 11:00:00 is needed. Find the first event in between.
  • step S 10325 if the first event that is the same as the user identifier of the second event is found in the obtained each event, and the interval between the first event and the second event is less than or equal to In the first inter-turn interval, step S 10325 is performed, otherwise, step S 10326 is performed.
  • Step S10325 determining that the first type of event rule has been satisfied, that is, the first event and the second event satisfy the first condition.
  • Step S10326 determining that the first type of event rule is not satisfied.
  • step S1033 According to the determination result of the above step S1032, if the first event and the second event satisfy the first condition in the processing interval, step S1033 is performed, otherwise, no action is required.
  • Step S1033 Perform a preset first action for the first user.
  • the first action may be set according to an actual situation, for example, sending a short message notification, a pop-up prompt window, and the like, which is not specifically limited in this embodiment.
  • Step S1034 Determine whether the third event and the fourth event in the acquired respective events satisfy the second condition.
  • the second condition is that the fourth event is not triggered in the preset second inter-time interval after the third event is triggered, and the third event and the fourth event are both second and second. User correspondence.
  • step S1034 may specifically include:
  • Step S10341 Search for the third event in the acquired respective events.
  • Step S10341 is similar to step S10321.
  • Step S10342 determining whether the third event is found in the acquired respective events.
  • step S10346 is performed, and if the third event is found in the acquired respective events, step S10343 is performed.
  • Step S10343 Search for the fourth event that is the same as the user identifier of the third event in the obtained each event.
  • Step S10344 Determine whether a fourth event that is the same as the user identifier of the third event is found in the acquired respective events.
  • the third event and the fourth event are two different events.
  • the third event is a pre-event
  • the fourth event is a post-event, that is, the third event should be before the fourth event.
  • the third event may be an event that the user clicks the registration button
  • the fourth event may be an event that the user logs in to the home page.
  • the inter-turn interval should be less than or equal to a predetermined inter-turn interval, that is, the second inter-turn interval.
  • the fourth event there is no need to look up the fourth event throughout the processing interval, and it is only necessary to perform a lookup within a specific interval (i.e., the second inter-turn interval) after the event triggering of the third event.
  • a specific interval i.e., the second inter-turn interval
  • the event triggering time of the third event is 11:00:00
  • the second inter-day interval is 2 hours, and only the period of 11:00:00 to 13:00:00 is needed. Find the fourth event in between.
  • step S1064 first searches for a post event (ie, the second event) and then searches for a preamble event (ie, the first event), and Step S1064: first searching for a pre-event (ie, the third event) and then searching for a post-event (ie, the fourth event is not found in the respective events acquired, and the same as the user identifier of the third event is not found.
  • the fourth event, or the inter-turn interval from the third event to the fourth event is greater than the second inter-turn interval
  • step S10345 is performed, otherwise, step S10346 is performed.
  • Step S10345 determining that the second type of event rule has been satisfied, that is, the third event and the fourth event satisfy the second condition.
  • Step S10346 determining that the second type of event rule is not satisfied.
  • step S1035 According to the determination result of the above step S1034, if the third event and the fourth event satisfy the second condition, step S1035 is performed, otherwise, no action is required.
  • Step S1035 Perform a second action preset for the second user.
  • the second action may be set according to an actual situation.
  • the primary service personnel may be arranged to contact the second user, etc., which is not specifically limited in this embodiment.
  • the event processing method may further include:
  • Step S1036 Count the total number of times the second action for the second user is performed within the preset third inter-day interval from the historical action record.
  • Step S1037 Determine whether the total number of times is greater than a preset threshold.
  • the threshold may be set according to an actual situation, for example, it may be set to 3, 5, or 10, etc., which is not specifically limited in this embodiment.
  • step S1038 is performed.
  • Step S1038 Perform a preset third action for the second user.
  • the third action may be set according to an actual situation.
  • the advanced service personnel may be arranged to contact the second user, etc., which is not specifically limited in this embodiment.
  • Step S104 Determine whether there is an event rule that has not been selected in the event rule base. If yes, execute step S105. If not, execute step S106.
  • Step S105 Select an event rule from the unselected event rules of the event rule base as the current target event rule, and then return to step S103.
  • Step S106 End processing of the acquired event.
  • the embodiment of the present application acquires each event that is triggered within a preset processing interval, from a preset.
  • the event rule base traverses each event rule as a current target event rule, and executes an event processing flow according to the target event rule.
  • the executing the event processing procedure according to the target event rule includes: if the target event rule is the first type event rule, and the first event and the second event satisfy the first condition, performing the preset first action;
  • the target event rule is a second type event rule, and the third event and the fourth event satisfy the second condition, and the preset second action is performed.
  • two events with dependencies are successively triggered (ie, the second event is also triggered in the first inter-time interval after the first event is triggered). And two events with dependencies are not triggered (ie, the fourth event is not triggered during the second inter-day interval after the third event is triggered).
  • the event rule type when the event rule in the preset event rule base is satisfied, the corresponding action is performed for the marketing activity, and the marketing activity performed by the two events is fully considered due to the sequential relationship between the two events. It has higher effectiveness and can also give users a better experience.
  • FIG. 5 is a schematic block diagram of the event processing terminal device provided by the embodiment of the present application. For the convenience of description, only the related to the embodiment of the present application is shown. section.
  • the event processing terminal device may be a computing device such as a desktop computer, a notebook, a palmtop computer, or a cloud server.
  • the event processing terminal device can include: a processor 50, a memory 51, and computer readable instructions 52 stored in the memory 51 and executable on the processor 50.
  • the processor 50 may be a central processing unit (CPU), or may be another general-purpose processor, a digital signal processor (DSP), or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), field programmable gate array
  • CPU central processing unit
  • DSP digital signal processor
  • ASIC Application Specific Integrated Circuit
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory 51 may be an internal storage unit of the event processing terminal device 5, such as event processing The hard disk or memory of the terminal device 5.
  • the memory 51 may also be an external storage device of the event processing terminal device 5, such as a plug-in hard disk equipped on the event processing terminal device 5, a smart memory card (SMC), and a secure digital (Secure) Digital, SD) cards, flash cards, etc.
  • the memory 51 may also include both an internal storage unit of the event processing terminal device 5 and an external storage device.
  • the memory 51 is used to store the computer readable instructions and other programs and data required by the event processing terminal device 5.
  • the memory 51 can also be used to temporarily store data that has been output or is about to be output.
  • FIG. 6 is a functional block diagram of computer readable instructions 52 provided by an embodiment of the present application.
  • the computer readable instructions 52 may be divided into one or more modules, and the one or more modules are stored in the memory 51 and executed by the processor 50.
  • the computer readable instructions 52 may be partitioned into an event acquisition module 601, a target event rule selection module 602, and an event processing module 603.
  • a module as referred to in this application refers to a series of computer readable instructions that are capable of performing a particular function, and is more suitable than the program to describe the execution of the computer readable instructions 52 in the event processing terminal. The following description will specifically describe the functions of the modules 601-603.
  • an event obtaining module 601 configured to acquire each event that is triggered within a preset processing interval
  • the target event rule selection module 602 is configured to select an event rule from the preset event rule base as the current target event rule, where the event rule is a sequential dependency relationship between the two events;
  • the event processing module 603 may include:
  • the first condition determining unit 6031 is configured to determine, if the target event rule is a first type of event rule, determine whether the first event and the second event in the acquired each event meet the first condition, The first condition is that the second event is also triggered in the preset first inter-day interval after the first event is triggered, and the first event and the second event are both corresponding to the first user;
  • the first action execution unit 6032 is configured to: if the first event and the second event satisfy the first condition, perform a preset first action for the first user;
  • the second condition determining unit 6033 is configured to determine, if the target event rule is the second type event rule, whether the third event and the fourth event in the acquired each event meet the second condition, Narrative The second condition is that the fourth event is not triggered in the preset second inter-second interval after the third event is triggered, and the third event and the fourth event are both corresponding to the second user;
  • the second action execution unit 6034 is configured to perform a second action preset for the second user if the third event and the fourth event satisfy the second condition.
  • the first condition determining unit 6031 may include:
  • a second event search subunit configured to search for the second event in the acquired respective events
  • a first event search subunit configured to: if found in the obtained each event And the second event, in the obtained each event, searching for the first event that is the same as the user identifier of the second event, where the user identifier is a unique identifier of the user;
  • a first determining subunit configured to: if the first event that is the same as the user identifier of the second event is found in the acquired respective events, and from the first event to the first If the inter-time interval of the two events is less than or equal to the first inter-turn interval, it is determined that the first event and the second event satisfy the first condition.
  • the first condition determining unit 6033 may include:
  • a third event search subunit configured to search for the third event in the acquired respective events
  • a fourth event search subunit configured to: if found in the obtained each event And the third event, in the obtained each event, searching for the fourth event that is the same as the user identifier of the third event, where the user identifier is a unique identifier of the user;
  • a second determining subunit configured to: if the fourth event that is the same as the user identifier of the third event is not found in the acquired respective events, or from the third event to the If the inter-turn interval of the fourth event is greater than the second inter-turn interval, it is determined that the third event and the fourth event satisfy the second condition.
  • the event obtaining module 601 may include:
  • an event capture unit configured to capture an event corresponding to the preset event code by using a preset plugin
  • an event adding unit configured to add a user identifier, an event code, and an event trigger to the capture In the event
  • an event storage unit configured to store the event in a preset event library.
  • the event processing module 603 may further include: [0140] an action statistics unit, configured to count, from the historical action record, a total number of times the second action for the second user is performed within a preset third inter-day interval;
  • the third action execution unit is configured to execute a preset third action for the second user if the total number of times is greater than a preset threshold.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • a computer readable storage medium A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like, which can store program codes. .

Landscapes

  • Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Development Economics (AREA)
  • Finance (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Economics (AREA)
  • Game Theory and Decision Science (AREA)
  • Marketing (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • User Interface Of Digital Computer (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

Disclosed are an event processing method and a terminal device. The method comprises: acquiring each event triggered in a pre-set processing interval (S101); traversing each event rule from a pre-set event rule library as a current target event rule (S102); and according to the target event rule, executing an event processing flow (S103), wherein the step of executing an event processing flow according to the target event rule comprises: if the target event rule is a first type of event rule, and a first event and a second event meet a first condition, executing a first pre-set action; and if the target event rule is a second type of event rule, and a third event and a fourth event meet a second condition, executing a second pre-set action. Since a dependency relationship of a sequential order of two events is taken into full consideration, marketing activities executed thereby are more effective, and a user can have a better experience.

Description

一种事件处理方法及终端设备  Event processing method and terminal device
[0001] 本申请申明享有 2017年 7月 27日递交的申请号为 201710624517.1、 名称为 "一种 事件处理方法及终端设备"中国专利申请的优先权, 该中国专利申请的整体内容 以参考的方式结合在本申请中。  [0001] The present application claims priority to the Chinese Patent Application No. 201710624517., entitled "An Event Processing Method and Terminal Equipment", filed on July 27, 2017, the entire contents of which are incorporated by reference. Combined in this application.
技术领域  Technical field
[0002] 本申请属于数据处理领域, 尤其涉及一种事件处理方法及终端设备。  [0002] This application belongs to the field of data processing, and in particular, to an event processing method and a terminal device.
背景技术  Background technique
[0003] 事件指的是用户在指定页面或客户端上的操作行为, 事件营销在互联网、 金融 等领域方兴未艾, 业界一般会收集用户的事件, 基于这些事件对用户做定制化 的营销活动。  [0003] Events refer to the user's operating behavior on a specified page or client. Event marketing is in the forefront of the Internet, finance, etc. The industry generally collects user events and customizes marketing campaigns based on these events.
[0004] 但目前的事件处理方法针对的对象一般都是独立的单个事件, 收集到某个事件 , 便执行与该事件对应的动作, 由于获取到的信息较片面, 其营销活动的有效 性较低, 用户获得的体验也较差。  [0004] However, the current event processing method is generally directed to an individual event. When an event is collected, the action corresponding to the event is performed. Since the obtained information is one-sided, the effectiveness of the marketing activity is relatively better. Low, the user gets a poor experience.
技术问题  technical problem
[0005] 有鉴于此, 本申请实施例提供了一种事件处理方法及终端设备, 以解决现有的 针对单个事件的事件处理方法所出现的营销活动有效性较低, 用户体验也较差 的问题。  In view of this, the embodiment of the present application provides an event processing method and a terminal device, so as to solve the problem that the existing marketing event for a single event has low effectiveness and a poor user experience. problem.
问题的解决方案  Problem solution
技术解决方案  Technical solution
[0006] 本申请实施例的第一方面提供了一种事件处理方法, 可以包括:  A first aspect of the embodiments of the present application provides an event processing method, which may include:
[0007] 获取在预设的处理间隔内被触发的各个事件; [0007] acquiring respective events that are triggered within a preset processing interval;
[0008] 从预设的事件规则库中选取一个事件规则作为当前的目标事件规则, 所述事件 规则为两个事件之间先后顺序的依赖关系;  [0008] selecting an event rule from the preset event rule base as the current target event rule, where the event rule is a sequential dependency relationship between the two events;
[0009] 根据所述目标事件规则执行事件处理流程; [0009] executing an event processing flow according to the target event rule;
[0010] 从所述事件规则库的未被选取过的事件规则中选取一个事件规则作为当前的目 标事件规则, 然后返回执行所述根据所述目标事件规则执行事件处理流程的步 骤, 直至所述事件规则库中所有事件规则均被选取过; [0010] selecting an event rule from the unselected event rules of the event rule base as the current target event rule, and then returning to executing the step of executing the event processing flow according to the target event rule All the event rules in the event rule base are selected;
[0011] 所述根据所述目标事件规则执行事件处理流程包括:  [0011] The executing the event processing procedure according to the target event rule includes:
[0012] 若所述目标事件规则为第一类型事件规则, 则判断在获取的所述各个事件中的 第一事件与第二事件是否满足第一条件, 所述第一条件为所述第一事件被触发 后预设的第一吋间间隔内所述第二事件也被触发, 所述第一事件和所述第二事 件均与第一用户对应;  [0012] if the target event rule is a first type of event rule, determining whether the first event and the second event in the acquired respective events satisfy the first condition, the first condition being the first The second event is also triggered in the preset first inter-day interval after the event is triggered, and the first event and the second event are both corresponding to the first user;
[0013] 若所述第一事件与所述第二事件满足所述第一条件, 则执行针对所述第一用户 的预设的第一动作;  [0013] if the first event and the second event satisfy the first condition, performing a preset first action for the first user;
[0014] 若所述目标事件规则为第二类型事件规则, 则判断在获取的所述各个事件中的 第三事件与第***是否满足第二条件, 所述第二条件为所述第三事件被触发 后预设的第二吋间间隔内所述第***未被触发, 所述第三事件和所述第四事 件均与第二用户对应;  [0014] if the target event rule is a second type of event rule, determining whether the third event and the fourth event in the acquired respective events satisfy the second condition, and the second condition is the third The fourth event is not triggered in the preset second interval after the event is triggered, and the third event and the fourth event are both corresponding to the second user;
[0015] 若所述第三事件与所述第***满足所述第二条件, 则执行针对所述第二用户 的预设的第二动作。  And [0015] if the third event and the fourth event satisfy the second condition, performing a second action preset for the second user.
[0016] 本申请实施例的第二方面提供了一种计算机可读存储介质, 所述计算机可读存 储介质存储有计算机可读指令, 所述计算机可读指令被处理器执行吋实现如下 步骤:  [0016] A second aspect of the embodiments of the present application provides a computer readable storage medium, where the computer readable storage medium stores computer readable instructions, and the computer readable instructions are executed by a processor, and the following steps are implemented:
[0017] 获取在预设的处理间隔内被触发的各个事件;  [0017] acquiring respective events that are triggered within a preset processing interval;
[0018] 从预设的事件规则库中选取一个事件规则作为当前的目标事件规则, 所述事件 规则为两个事件之间先后顺序的依赖关系;  [0018] selecting an event rule from the preset event rule base as the current target event rule, where the event rule is a sequential dependency relationship between the two events;
[0019] 根据所述目标事件规则执行事件处理流程; [0019] executing an event processing flow according to the target event rule;
[0020] 从所述事件规则库的未被选取过的事件规则中选取一个事件规则作为当前的目 标事件规则, 然后返回执行所述根据所述目标事件规则执行事件处理流程的步 骤, 直至所述事件规则库中所有事件规则均被选取过;  [0020] selecting an event rule from the unselected event rules of the event rule base as the current target event rule, and then returning to perform the step of executing the event processing flow according to the target event rule until the All event rules in the event rule base have been selected;
[0021] 所述根据所述目标事件规则执行事件处理流程包括:  [0021] The executing the event processing procedure according to the target event rule includes:
[0022] 若所述目标事件规则为第一类型事件规则, 则判断在获取的所述各个事件中的 第一事件与第二事件是否满足第一条件, 所述第一条件为所述第一事件被触发 后预设的第一吋间间隔内所述第二事件也被触发, 所述第一事件和所述第二事 件均与第一用户对应; [0022] if the target event rule is a first type of event rule, determining whether the first event and the second event in the acquired respective events satisfy the first condition, where the first condition is the first The second event is also triggered within a preset first inter-day interval after the event is triggered, the first event and the second event Each piece corresponds to the first user;
[0023] 若所述第一事件与所述第二事件满足所述第一条件, 则执行针对所述第一用户 的预设的第一动作;  [0023] if the first event and the second event satisfy the first condition, performing a preset first action for the first user;
[0024] 若所述目标事件规则为第二类型事件规则, 则判断在获取的所述各个事件中的 第三事件与第***是否满足第二条件, 所述第二条件为所述第三事件被触发 后预设的第二吋间间隔内所述第***未被触发, 所述第三事件和所述第四事 件均与第二用户对应;  [0024] if the target event rule is a second type of event rule, determining whether the third event and the fourth event in the acquired respective events satisfy the second condition, and the second condition is the third The fourth event is not triggered in the preset second interval after the event is triggered, and the third event and the fourth event are both corresponding to the second user;
[0025] 若所述第三事件与所述第***满足所述第二条件, 则执行针对所述第二用户 的预设的第二动作。  And [0025] if the third event and the fourth event satisfy the second condition, performing a second action preset for the second user.
[0026] 本申请实施例的第三方面提供了一种事件处理终端设备, 包括存储器、 处理器 以及存储在所述存储器中并可在所述处理器上运行的计算机可读指令, 所述处 理器执行所述计算机可读指令吋实现如下步骤:  A third aspect of an embodiment of the present application provides an event processing terminal device including a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, the processing The computer executes the computer readable instructions to implement the following steps:
[0027] 获取在预设的处理间隔内被触发的各个事件;  [0027] acquiring respective events that are triggered within a preset processing interval;
[0028] 从预设的事件规则库中选取一个事件规则作为当前的目标事件规则, 所述事件 规则为两个事件之间先后顺序的依赖关系;  [0028] selecting an event rule from the preset event rule base as the current target event rule, where the event rule is a sequential dependency relationship between the two events;
[0029] 根据所述目标事件规则执行事件处理流程; [0029] executing an event processing flow according to the target event rule;
[0030] 从所述事件规则库的未被选取过的事件规则中选取一个事件规则作为当前的目 标事件规则, 然后返回执行所述根据所述目标事件规则执行事件处理流程的步 骤, 直至所述事件规则库中所有事件规则均被选取过;  [0030] selecting an event rule from the unselected event rules of the event rule base as the current target event rule, and then returning to performing the step of executing the event processing flow according to the target event rule until the All event rules in the event rule base have been selected;
[0031] 所述根据所述目标事件规则执行事件处理流程包括:  [0031] The executing the event processing procedure according to the target event rule includes:
[0032] 若所述目标事件规则为第一类型事件规则, 则判断在获取的所述各个事件中的 第一事件与第二事件是否满足第一条件, 所述第一条件为所述第一事件被触发 后预设的第一吋间间隔内所述第二事件也被触发, 所述第一事件和所述第二事 件均与第一用户对应;  [0032] if the target event rule is a first type of event rule, determining whether the first event and the second event in the acquired respective events satisfy the first condition, where the first condition is the first The second event is also triggered in the preset first inter-day interval after the event is triggered, and the first event and the second event are both corresponding to the first user;
[0033] 若所述第一事件与所述第二事件满足所述第一条件, 则执行针对所述第一用户 的预设的第一动作;  [0033] if the first event and the second event satisfy the first condition, performing a preset first action for the first user;
[0034] 若所述目标事件规则为第二类型事件规则, 则判断在获取的所述各个事件中的 第三事件与第***是否满足第二条件, 所述第二条件为所述第三事件被触发 后预设的第二吋间间隔内所述第***未被触发, 所述第三事件和所述第四事 件均与第二用户对应; [0034] if the target event rule is a second type of event rule, determining whether the third event and the fourth event in the acquired respective events satisfy the second condition, and the second condition is the third Event is triggered The fourth event is not triggered in the second preset interval, and the third event and the fourth event are both corresponding to the second user;
[0035] 若所述第三事件与所述第***满足所述第二条件, 则执行针对所述第二用户 的预设的第二动作。  And [0035] if the third event and the fourth event satisfy the second condition, performing a second action preset for the second user.
[0036] 本申请实施例的第四方面提供了一种事件处理程序, 包括: [0036] A fourth aspect of the embodiments of the present application provides an event processing program, including:
[0037] 事件获取模块, 用于获取在预设的处理间隔内被触发的各个事件; [0037] an event obtaining module, configured to acquire each event that is triggered within a preset processing interval;
[0038] 目标事件规则选取模块, 用于从预设的事件规则库中选取一个事件规则作为当 前的目标事件规则, 所述事件规则为两个事件之间先后顺序的依赖关系; [0038] a target event rule selection module, configured to select an event rule from the preset event rule base as the current target event rule, where the event rule is a sequential dependency relationship between the two events;
[0039] 事件处理模块, 用于根据所述目标事件规则执行事件处理流程; [0039] an event processing module, configured to execute an event processing process according to the target event rule;
[0040] 具体地, 所述事件处理模块包括: [0040] Specifically, the event processing module includes:
[0041] 第一条件判断单元, 用于若所述目标事件规则为第一类型事件规则, 则判断在 获取的所述各个事件中的第一事件与第二事件是否满足第一条件, 所述第一条 件为所述第一事件被触发后预设的第一吋间间隔内所述第二事件也被触发, 所 述第一事件和所述第二事件均与第一用户对应;  [0041] a first condition determining unit, configured to determine, if the target event rule is a first type of event rule, determining whether the first event and the second event in the acquired respective events satisfy the first condition, The first condition is that the second event is also triggered in the preset first inter-day interval after the first event is triggered, and the first event and the second event are both corresponding to the first user;
[0042] 第一动作执行单元, 用于若所述第一事件与所述第二事件满足所述第一条件, 则执行针对所述第一用户的预设的第一动作; a first action execution unit, configured to execute a preset first action for the first user if the first event and the second event satisfy the first condition;
[0043] 第二条件判断单元, 用于若所述目标事件规则为第二类型事件规则, 则判断在 获取的所述各个事件中的第三事件与第***是否满足第二条件, 所述第二条 件为所述第三事件被触发后预设的第二吋间间隔内所述第***未被触发, 所 述第三事件和所述第***均与第二用户对应; [0043] a second condition determining unit, configured to determine, if the target event rule is a second type of event rule, determining whether the third event and the fourth event in the acquired respective events satisfy the second condition, The second condition is that the fourth event is not triggered in the preset second interval after the third event is triggered, and the third event and the fourth event are both corresponding to the second user;
[0044] 第二动作执行单元, 用于若所述第三事件与所述第***满足所述第二条件, 则执行针对所述第二用户的预设的第二动作。 [0044] The second action execution unit is configured to execute a second action preset for the second user if the third event and the fourth event satisfy the second condition.
发明的有益效果  Advantageous effects of the invention
有益效果  Beneficial effect
[0045] 本申请实施例与现有技术相比存在的有益效果是: 本申请实施例获取在预设的 处理间隔内被触发的各个事件, 从预设的事件规则库中遍历各个事件规则作为 当前的目标事件规则, 根据所述目标事件规则执行事件处理流程。 其中, 根据 所述目标事件规则执行事件处理流程包括: 若所述目标事件规则为第一类型事 件规则, 且第一事件与第二事件满足第一条件, 则执行预设的第一动作; 若所 述目标事件规则为第二类型事件规则, 且第三事件与第***满足第二条件, 则执行预设的第二动作。 本申请实施例根据实际应用场景, 制定出了两个存在 依赖关系的事件相继被触发 (即在所述第一事件被触发后的所述第一吋间间隔 内所述第二事件也被触发) , 及两个存在依赖关系的事件未相继被触发 (即在 所述第三事件被触发后的所述第二吋间间隔内所述第***未被触发) 这两种 典型的营销场景的事件规则类型, 当预设的事件规则库中的事件规则得到满足 吋, 则执行对应的动作进行营销活动, 由于充分考虑了两个事件之间先后顺序 的依赖关系, 其所执行的营销活动具有更高的有效性, 也能使用户获得较好的 体验。 [0045] The beneficial effects of the embodiment of the present application are compared with the prior art: the embodiment of the present application acquires each event that is triggered within a preset processing interval, and traverses each event rule from a preset event rule base. The current target event rule performs an event processing flow according to the target event rule. The executing the event processing process according to the target event rule includes: if the target event rule is the first type of event a rule, and the first event and the second event satisfy the first condition, and then perform a preset first action; if the target event rule is a second type event rule, and the third event and the fourth event satisfy the second condition , the second action of the preset is executed. In the embodiment of the present application, according to the actual application scenario, two events with dependencies are successively triggered (ie, the second event is also triggered in the first inter-time interval after the first event is triggered). And two events with dependencies are not triggered (ie, the fourth event is not triggered during the second inter-day interval after the third event is triggered). These two typical marketing scenarios The event rule type, when the event rule in the preset event rule base is satisfied, the corresponding action is performed for the marketing activity, and the marketing activity performed by the two events is fully considered due to the sequential relationship between the two events. It has higher effectiveness and can also give users a better experience.
对附图的简要说明  Brief description of the drawing
附图说明  DRAWINGS
[0046] 为了更清楚地说明本申请实施例中的技术方案, 下面将对实施例或现有技术描 述中所需要使用的附图作简单地介绍, 显而易见地, 下面描述中的附图仅仅是 本申请的一些实施例, 对于本领域普通技术人员来讲, 在不付出创造性劳动性 的前提下, 还可以根据这些附图获得其他的附图。  [0046] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are merely Some embodiments of the present application can also obtain other figures from those skilled in the art without departing from the drawings.
[0047] 图 1为本申请实施例中一种事件处理方法的一个实施例流程图;  1 is a flow chart of an embodiment of an event processing method according to an embodiment of the present application;
[0048] 图 2为本申请实施例中一种事件处理方法步骤 103在一个应用场景下的流程示意 图; [0048] FIG. 2 is a schematic flow chart of an event processing method step 103 in an application scenario according to an embodiment of the present application;
[0049] 图 3为本申请实施例中一种事件处理方法步骤 1032在一个应用场景下的流程示  [0049] FIG. 3 is a flow chart of an event processing method step 1032 in an application scenario according to an embodiment of the present application.
[0050] 图 4为本申请实施例中一种事件处理方法步骤 1034在一个应用场景下的流程示 [0050] FIG. 4 is a flow chart of an event processing method step 1034 in an application scenario according to an embodiment of the present application.
[0051] 图 5为本申请实施例提供的事件处理终端设备的示意框图; [0051] FIG. 5 is a schematic block diagram of an event processing terminal device according to an embodiment of the present disclosure;
[0052] 图 6为本申请实施例提供的事件处理程序的功能模块图。 FIG. 6 is a functional block diagram of an event processing program according to an embodiment of the present application.
本发明的实施方式 Embodiments of the invention
[0053] 为使得本申请的发明目的、 特征、 优点能够更加的明显和易懂, 下面将结合本 申请实施例中的附图, 对本申请实施例中的技术方案进行清楚、 完整地描述, 显然, 下面所描述的实施例仅仅是本申请一部分实施例, 而非全部的实施例。 基于本申请中的实施例, 本领域普通技术人员在没有做出创造性劳动前提下所 获得的所有其它实施例, 都属于本申请保护的范围。 [0053] In order to make the object, features and advantages of the present invention more obvious and easy to understand, the following will be combined The technical solutions in the embodiments of the present application are clearly and completely described in the drawings, and the embodiments described below are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.
[0054] 本申请实施例主要针对两个事件之间先后顺序的依赖关系来执行对应的营销动 作, 例如, 用户在某公司的网页上首先点击了验证码按钮进行了验证, 然后在 一分钟后又点击注册按钮进行注册, 则可以判断该用户对该公司的服务或产品 可能会有较大的兴趣, 此吋可以通过发送短信的方式, 欢迎用户的加入, 并向 用户介绍该公司的服务或产品信息。 又如, 用户已经点击了某公司的注册按钮 , 但在之后的两个小吋内, 用户都没有进一步地登录该公司的首页进行浏览, 则可以判断该用户可能遇到了某些问题或者产生了某些疑虑, 此吋可以安排客 服人员跟进, 主动与该用户联系以便帮助用户解决问题, 消除其疑虑。  [0054] The embodiment of the present application mainly performs a corresponding marketing action for the sequential dependency relationship between two events. For example, the user first clicks the verification code button on a company webpage to verify, and then one minute later. By clicking the registration button to register, you can determine that the user may have a greater interest in the company's services or products. You can then send the text message to welcome the user to join and introduce the user to the company's services or product information. For another example, the user has clicked on a company's registration button, but in the next two hours, the user has not further logged into the company's home page for browsing, then it can be judged that the user may have encountered some problems or generated Some doubts, you can arrange customer service staff to follow up, and actively contact the user to help users solve problems and eliminate their doubts.
[0055] 请参阅图 1, 本申请实施例中一种事件处理方法的一个实施例可以包括:  [0055] Referring to FIG. 1, an embodiment of an event processing method in an embodiment of the present application may include:
[0056] 步骤 S101、 获取在预设的处理间隔内被触发的各个事件。  [0056] Step S101: Acquire various events that are triggered within a preset processing interval.
[0057] 本实施例中, 对事件采取了一种间歇性的集中式处理方式, 每隔一定的处理间 隔, 对该段处理间隔所累积的事件集中进行处理。  [0057] In this embodiment, an intermittent centralized processing manner is adopted for the event, and the events accumulated in the processing interval are collectively processed at regular processing intervals.
[0058] 首先, 通过预设的插件实吋捕获与预设的事件编码对应的事件。 在本实施例中 , 可以使用轻量级无侵入性的前端 javascript捕获插件来获取用户在企业网页或者 客户端的操作事件。 所述事件编码为事件的唯一标识, 不同事件的事件编码互 不相同, 每个事件编码都可以有一个事件描述来表示其业务含义, 例如企业网 页上某个按钮配置了事件编码为 abc, 同吋也将事件描述配置为"点击了登录按钮 ", 那么一旦用户点击了该按钮, 则会触发该插件捕获用户的点击事件, 这个事 件的事件编码为 abc, 描述信息为"点击了登录按钮"。  [0058] First, an event corresponding to a preset event code is captured by a preset plug-in. In this embodiment, a lightweight, non-intrusive front-end javascript capture plugin can be used to obtain operational events of the user on the corporate web page or client. The event code is a unique identifier of the event, and the event codes of different events are different from each other. Each event code may have an event description to indicate its business meaning. For example, a button on the enterprise webpage is configured with an event code of abc, the same吋 also configures the event description as "click the login button", then once the user clicks the button, the plugin will be triggered to capture the user's click event. The event event is encoded as abc and the description is "click the login button" .
[0059] 然后, 将用户标识、 事件编码和事件触发吋间添加入捕获的所述事件中。 所述 用户标识为用户的唯一标识, 不同用户的用户标识互不相同, 在实际应用中, 手机号、 邮箱地址、 身份证、 微信号等都可以作为所述用户标识。 对于一条事 件而言, 需要明确该事件是什么 (即所述事件编码) 、 由谁触发了该事件 (即 所述用户标识) 以及在何吋触发了该事件 (即所述事件触发吋间) , 因此, 这 三个信息是一条事件的必备要素, 除此之外, 还可以在所述事件中添加用户 IP地 址、 浏览器版本等信息。 [0059] Then, the user identification, the event encoding, and the event trigger are added to the captured event. The user identifier is a unique identifier of the user, and the user identifiers of different users are different from each other. In actual applications, the mobile phone number, the email address, the ID card, the micro signal, and the like can be used as the user identifier. For an event, it is necessary to clarify what the event is (ie, the event code), who triggered the event (ie, the user identity), and when the event was triggered (ie, the event triggered the day) So, this The three pieces of information are essential elements of an event. In addition, information such as the user IP address and browser version can be added to the event.
[0060] 最后, 将所述事件存储入预设的事件库中。 所述事件库为实吋更新的事件集合 , 在所述事件库中, 可以根据所述事件触发吋间来排列所述事件记录, 也可以 根据所述事件编码或所述用户标识来排列所述事件记录。  [0060] Finally, the event is stored in a preset event library. The event library is a set of events that are updated, and the event record may be arranged according to the event triggering time, or may be arranged according to the event code or the user identifier. record.
[0061] 步骤 S102、 从预设的事件规则库中选取一个事件规则作为当前的目标事件规则  [0061] Step S102: Select an event rule from the preset event rule base as the current target event rule.
[0062] 所述事件规则为两个事件之间先后顺序的依赖关系, 是对获取的所述事件进行 处理所依据的标准。 所述事件规则库为预先设置的各个事件规则的集合。 在本 实施例中, 可以根据实际情况调整所述事件规则库, 例如, 可以在其中新增某 个事件规则、 刪除某个事件规则或者修改某个事件规则。 [0062] The event rule is a sequential dependency relationship between two events, and is a criterion by which the acquired event is processed. The event rule base is a set of preset event rules. In this embodiment, the event rule base may be adjusted according to actual conditions. For example, an event rule may be added, an event rule may be deleted, or an event rule may be modified.
[0063] 步骤 S103、 根据所述目标事件规则执行事件处理流程。 [0063] Step S103: Perform an event processing procedure according to the target event rule.
[0064] 具体地, 如图 2所示, 步骤 S103可以包括: [0064] Specifically, as shown in FIG. 2, step S103 may include:
[0065] 步骤 S1031、 判断所述目标事件规则是否为第一类型事件规则。 [0065] Step S1031: Determine whether the target event rule is a first type event rule.
[0066] 在本实施例中, 将事件规则分为两种类型, 即第一类型事件规则和第二类型事 件规则, 所述第一类型事件规则针对的是两个存在依赖关系的事件相继被触发 的情况, 即前置事件被触发, 后置事件也被触发。 所述第二类型事件规则针对 的是两个存在依赖关系的事件未相继被触发的情况, 即前置事件被触发, 后置 事件未被触发。 [0066] In this embodiment, the event rules are divided into two types, that is, a first type event rule and a second type event rule, and the first type event rule is directed to two events having a dependency relationship being successively In the triggered case, the pre-event is triggered and the post-event is triggered. The second type of event rule is directed to the case where two events with dependencies are not triggered consecutively, that is, the pre-event is triggered, and the post-event is not triggered.
[0067] 若所述目标事件规则为第一类型事件规则, 则执行步骤 S1032; 若所述目标事 件规则为第二类型事件规则, 则执行步骤 S1034。  [0067] If the target event rule is the first type event rule, step S1032 is performed; if the target event rule is the second type event rule, step S1034 is performed.
[0068] 步骤 S1032, 判断在获取的所述各个事件中的第一事件与第二事件是否满足第 一条件。 [0068] Step S1032: Determine whether the first event and the second event in the acquired respective events satisfy the first condition.
[0069] 所述第一条件为所述第一事件被触发后预设的第一吋间间隔内所述第二事件也 被触发, 所述第一事件和所述第二事件均与第一用户对应。  [0069] the first condition is that the second event is also triggered in a preset first inter-time interval after the first event is triggered, and the first event and the second event are both first User correspondence.
[0070] 如图 3所示, 步骤 S 1032具体可以包括: [0070] As shown in FIG. 3, step S1032 may specifically include:
[0071] 步骤 S10321 , 在获取的所述各个事件中査找所述第二事件。 [0071] Step S10321: Search for the second event in the acquired respective events.
[0072] 步骤 S10322, 判断在获取的所述各个事件中是否査找到所述第二事件。 [0073] 若在获取的所述各个事件中未査找到所述第二事件, 则执行步骤 S10326 , 若在 所述事件库中査找到所述第二事件, 则执行步骤 S10323。 [0072] Step S10322, determining whether the second event is found in the acquired respective events. [0073] If the second event is not found in the acquired respective events, step S10326 is performed, and if the second event is found in the event library, step S10323 is performed.
[0074] 步骤 S10323 , 在获取的所述各个事件中査找与所述第二事件的用户标识相同的 第一事件。 [0074] Step S10323: Search for the first event that is the same as the user identifier of the second event in the obtained each event.
[0075] 步骤 S10324, 判断在获取的所述各个事件中是否査找到与所述第二事件的用户 标识相同的第一事件。  [0075] Step S10324: Determine whether a first event that is the same as the user identifier of the second event is found in the acquired respective events.
[0076] 在本实施例中, 所述第一事件和所述第二事件为两个不同的事件。 所述第一事 件为前置事件, 所述第二事件为后置事件, 也即所述第一事件应在所述第二事 件之前。 例如, 所述第一事件可以为用户点击验证码按钮的事件, 所述第二事 件可以为用户点击注册按钮的事件, 一般地, 这两个事件之间还存在着吋间上 的限定, 即两者的吋间间隔应小于等于某一预设的吋间间隔, 也即第一吋间间 隔。 因此, 无需在整个所述处理间隔中査找所述第一事件, 只需在所述第二事 件的事件触发吋间之前的特定吋间段 (即所述第一吋间间隔) 内进行査找。 例 如, 已知所述第二事件的事件触发吋间为 11:00:00, 所述第一吋间间隔为 2小吋 , 则只需 9:00:00到 11:00:00这一段吋间内査找所述第一事件。  [0076] In this embodiment, the first event and the second event are two different events. The first event is a pre-event, and the second event is a post-event, that is, the first event should be before the second event. For example, the first event may be an event that the user clicks the verification code button, and the second event may be an event that the user clicks the registration button. Generally, there is still a limitation between the two events, that is, The inter-turn interval between the two should be less than or equal to a predetermined inter-turn interval, that is, the first inter-turn interval. Therefore, it is not necessary to look up the first event throughout the processing interval, and it is only necessary to perform a lookup within a specific inter-segment (i.e., the first inter-turn interval) before the event triggering of the second event. For example, it is known that the event triggering time of the second event is 11:00:00, and the first inter-day interval is 2 hours, and only the period of 9:00:00 to 11:00:00 is needed. Find the first event in between.
[0077] 若在获取的所述各个事件中査找到与所述第二事件的用户标识相同的所述第一 事件, 且从所述第一事件到所述第二事件的吋间间隔小于等于所述第一吋间间 隔, 则执行步骤 S 10325, 反之, 则执行步骤 S 10326。  [0077] if the first event that is the same as the user identifier of the second event is found in the obtained each event, and the interval between the first event and the second event is less than or equal to In the first inter-turn interval, step S 10325 is performed, otherwise, step S 10326 is performed.
[0078] 步骤 S10325 , 判定所述第一类型事件规则已得到满足, 也即所述第一事件与所 述第二事件满足所述第一条件。  [0078] Step S10325, determining that the first type of event rule has been satisfied, that is, the first event and the second event satisfy the first condition.
[0079] 步骤 S10326 , 判定所述第一类型事件规则未得到满足。  [0079] Step S10326, determining that the first type of event rule is not satisfied.
[0080] 根据以上步骤 S1032的判断结果, 若在所述处理间隔内所述第一事件与所述第 二事件满足所述第一条件, 则执行步骤 S 1033, 反之, 则无需执行任何动作。  [0080] According to the determination result of the above step S1032, if the first event and the second event satisfy the first condition in the processing interval, step S1033 is performed, otherwise, no action is required.
[0081] 步骤 S1033 , 执行针对所述第一用户的预设的第一动作。 [0081] Step S1033: Perform a preset first action for the first user.
[0082] 所述第一动作可以根据实际情况来设置, 例如, 发送短信通知、 弹出提示窗口 等等, 本实施例对此不作具体限定。  [0082] The first action may be set according to an actual situation, for example, sending a short message notification, a pop-up prompt window, and the like, which is not specifically limited in this embodiment.
[0083] 步骤 S1034, 判断在获取的所述各个事件中的第三事件与第***是否满足第 二条件。 [0084] 所述第二条件为所述第三事件被触发后预设的第二吋间间隔内所述第***未 被触发, 所述第三事件和所述第***均与第二用户对应。 [0083] Step S1034: Determine whether the third event and the fourth event in the acquired respective events satisfy the second condition. [0084] the second condition is that the fourth event is not triggered in the preset second inter-time interval after the third event is triggered, and the third event and the fourth event are both second and second. User correspondence.
[0085] 如图 4所示, 步骤 S1034具体可以包括: [0085] As shown in FIG. 4, step S1034 may specifically include:
[0086] 步骤 S10341 , 在获取的所述各个事件中査找所述第三事件。 [0086] Step S10341: Search for the third event in the acquired respective events.
[0087] 步骤 S10341与步骤 S10321类似, 具体过程可参照步骤 S10321的描述, 本实施例 在此不再赘述。 [0087] Step S10341 is similar to step S10321. For the specific process, reference may be made to the description of step S10321.
[0088] 步骤 S10342, 判断在获取的所述各个事件中是否査找到所述第三事件。  [0088] Step S10342, determining whether the third event is found in the acquired respective events.
[0089] 若在获取的所述各个事件中未査找到所述第三事件, 则执行步骤 S10346, 若在 获取的所述各个事件中査找到所述第三事件, 则执行步骤 S10343。  [0089] If the third event is not found in the acquired respective events, step S10346 is performed, and if the third event is found in the acquired respective events, step S10343 is performed.
[0090] 步骤 S10343 , 在获取的所述各个事件中査找与所述第三事件的用户标识相同的 第***。 [0090] Step S10343: Search for the fourth event that is the same as the user identifier of the third event in the obtained each event.
[0091] 步骤 S10344, 判断在获取的所述各个事件中是否査找到与所述第三事件的用户 标识相同的第***。  [0091] Step S10344: Determine whether a fourth event that is the same as the user identifier of the third event is found in the acquired respective events.
[0092] 在本实施例中, 所述第三事件和所述第***为两个不同的事件。 所述第三事 件为前置事件, 所述第***为后置事件, 也即所述第三事件应在所述第四事 件之前。 例如, 所述第三事件可以为用户点击注册按钮的事件, 所述第*** 可以为用户登录首页的事件, 一般地, 这两个事件之间还存在着吋间上的限定 , 即两者的吋间间隔应小于等于某一预设的吋间间隔, 也即第二吋间间隔。 因 此, 无需在整个所述处理间隔中査找所述第***, 只需在所述第三事件的事 件触发吋间之后的特定吋间段 (即所述第二吋间间隔) 内进行査找。 例如, 已 知所述第三事件的事件触发吋间为 11:00:00, 所述第二吋间间隔为 2小吋, 则只 需 11:00:00到 13:00:00这一段吋间内査找所述第***。  [0092] In this embodiment, the third event and the fourth event are two different events. The third event is a pre-event, and the fourth event is a post-event, that is, the third event should be before the fourth event. For example, the third event may be an event that the user clicks the registration button, and the fourth event may be an event that the user logs in to the home page. Generally, there is a limitation between the two events, that is, both. The inter-turn interval should be less than or equal to a predetermined inter-turn interval, that is, the second inter-turn interval. Therefore, there is no need to look up the fourth event throughout the processing interval, and it is only necessary to perform a lookup within a specific interval (i.e., the second inter-turn interval) after the event triggering of the third event. For example, it is known that the event triggering time of the third event is 11:00:00, and the second inter-day interval is 2 hours, and only the period of 11:00:00 to 13:00:00 is needed. Find the fourth event in between.
[0093] 特别需要注意的是, 步骤 S1064与步骤 S1044最根本的区别在于, 步骤 S1044先 査找后置事件 (即所述第二事件) 再査找前置事件 (即所述第一事件) , 而步 骤 S1064先査找前置事件 (即所述第三事件) 再査找后置事件 (即所述第*** 若在获取的所述各个事件中未査找到与所述第三事件的用户标识相同的所述第 ***, 或从所述第三事件到所述第***的吋间间隔大于所述第二吋间间隔 , 则执行步骤 S 10345, 反之, 则执行步骤 S 10346。 [0093] It is particularly noted that the most fundamental difference between step S1064 and step S1044 is that step S1044 first searches for a post event (ie, the second event) and then searches for a preamble event (ie, the first event), and Step S1064: first searching for a pre-event (ie, the third event) and then searching for a post-event (ie, the fourth event is not found in the respective events acquired, and the same as the user identifier of the third event is not found. The fourth event, or the inter-turn interval from the third event to the fourth event is greater than the second inter-turn interval Then, step S10345 is performed, otherwise, step S10346 is performed.
[0095] 步骤 S10345 , 判定所述第二类型事件规则已得到满足, 也即所述第三事件与所 述第***满足所述第二条件。 [0095] Step S10345, determining that the second type of event rule has been satisfied, that is, the third event and the fourth event satisfy the second condition.
[0096] 步骤 S10346, 判定所述第二类型事件规则未得到满足。 [0096] Step S10346, determining that the second type of event rule is not satisfied.
[0097] 根据以上步骤 S1034的判断结果, 若所述第三事件与所述第***满足所述第 二条件, 则执行步骤 S 1035, 反之, 则无需执行任何动作。  [0097] According to the determination result of the above step S1034, if the third event and the fourth event satisfy the second condition, step S1035 is performed, otherwise, no action is required.
[0098] 步骤 S1035 , 执行针对所述第二用户的预设的第二动作。 [0098] Step S1035: Perform a second action preset for the second user.
[0099] 所述第二动作可以根据实际情况来设置, 例如, 可以安排初级服务人员与所述 第二用户进行联系等等, 本实施例对此不作具体限定。  [0099] The second action may be set according to an actual situation. For example, the primary service personnel may be arranged to contact the second user, etc., which is not specifically limited in this embodiment.
[0100] 优选地, 在步骤 S1035之后, 所述事件处理方法还可以包括: [0100] Preferably, after the step S1035, the event processing method may further include:
[0101] 步骤 S1036, 从历史动作记录中统计在预设的第三吋间间隔内针对所述第二用 户的所述第二动作被执行的总次数。 [0101] Step S1036: Count the total number of times the second action for the second user is performed within the preset third inter-day interval from the historical action record.
[0102] 步骤 S1037 , 判断所述总次数是否大于预设的阈值。 [0102] Step S1037: Determine whether the total number of times is greater than a preset threshold.
[0103] 所述阈值可以根据实际情况进行设置, 例如, 可以将其设置为 3、 5或 10等等, 本实施例对此不作具体限定。  [0103] The threshold may be set according to an actual situation, for example, it may be set to 3, 5, or 10, etc., which is not specifically limited in this embodiment.
[0104] 若所述总次数小于等于所述阈值, 则无需执行进一步的操作。 [0104] If the total number of times is less than or equal to the threshold, no further operations need to be performed.
[0105] 若所述总次数大于所述阈值, 则执行步骤 S1038。 [0105] If the total number of times is greater than the threshold, step S1038 is performed.
[0106] 步骤 S1038 , 执行针对所述第二用户的预设的第三动作。 [0106] Step S1038: Perform a preset third action for the second user.
[0107] 所述第三动作可以根据实际情况来设置, 例如, 可以安排高级服务人员与所述 第二用户进行联系等等, 本实施例对此不作具体限定。  [0107] The third action may be set according to an actual situation. For example, the advanced service personnel may be arranged to contact the second user, etc., which is not specifically limited in this embodiment.
[0108] 步骤 S104、 判断所述事件规则库中是否存在未被选取过的事件规则, 若存在, 则执行步骤 S 105, 若不存在, 则执行步骤 S 106。 [0108] Step S104: Determine whether there is an event rule that has not been selected in the event rule base. If yes, execute step S105. If not, execute step S106.
[0109] 步骤 S105、 从所述事件规则库的未被选取过的事件规则中选取一个事件规则作 为当前的目标事件规则, 然后返回执行步骤 S103。 [0109] Step S105: Select an event rule from the unselected event rules of the event rule base as the current target event rule, and then return to step S103.
[0110] 步骤 S106、 结束对获取的所述事件的处理。 [0110] Step S106: End processing of the acquired event.
[0111] 容易理解地, 以上过程完成了对所述事件规则库中的各个事件规则的遍历, 分 别根据各个事件规则执行了事件处理流程。  [0111] It is easy to understand that the above process completes the traversal of each event rule in the event rule base, and the event processing flow is executed according to each event rule.
[0112] 综上所述, 本申请实施例获取在预设的处理间隔内被触发的各个事件, 从预设 的事件规则库中遍历各个事件规则作为当前的目标事件规则, 根据所述目标事 件规则执行事件处理流程。 其中, 根据所述目标事件规则执行事件处理流程包 括: 若所述目标事件规则为第一类型事件规则, 且第一事件与第二事件满足第 一条件, 则执行预设的第一动作; 若所述目标事件规则为第二类型事件规则, 且第三事件与第***满足第二条件, 则执行预设的第二动作。 本申请实施例 根据实际应用场景, 制定出了两个存在依赖关系的事件相继被触发 (即在所述 第一事件被触发后的所述第一吋间间隔内所述第二事件也被触发) , 及两个存 在依赖关系的事件未相继被触发 (即在所述第三事件被触发后的所述第二吋间 间隔内所述第***未被触发) 这两种典型的营销场景的事件规则类型, 当预 设的事件规则库中的事件规则得到满足吋, 则执行对应的动作进行营销活动, 由于充分考虑了两个事件之间先后顺序的依赖关系, 其所执行的营销活动具有 更高的有效性, 也能使用户获得较好的体验。 [0112] In summary, the embodiment of the present application acquires each event that is triggered within a preset processing interval, from a preset. The event rule base traverses each event rule as a current target event rule, and executes an event processing flow according to the target event rule. The executing the event processing procedure according to the target event rule includes: if the target event rule is the first type event rule, and the first event and the second event satisfy the first condition, performing the preset first action; The target event rule is a second type event rule, and the third event and the fourth event satisfy the second condition, and the preset second action is performed. In the embodiment of the present application, according to the actual application scenario, two events with dependencies are successively triggered (ie, the second event is also triggered in the first inter-time interval after the first event is triggered). And two events with dependencies are not triggered (ie, the fourth event is not triggered during the second inter-day interval after the third event is triggered). These two typical marketing scenarios The event rule type, when the event rule in the preset event rule base is satisfied, the corresponding action is performed for the marketing activity, and the marketing activity performed by the two events is fully considered due to the sequential relationship between the two events. It has higher effectiveness and can also give users a better experience.
[0113] 应理解, 上述实施例中各步骤的序号的大小并不意味着执行顺序的先后, 各过 程的执行顺序应以其功能和内在逻辑确定, 而不应对本申请实施例的实施过程 构成任何限定。  It should be understood that the size of the serial number of each step in the foregoing embodiment does not mean the order of execution sequence, and the execution order of each process should be determined by its function and internal logic, and should not be implemented by the implementation process of the embodiment of the present application. Any restrictions.
[0114] 对应于上文实施例所述的事件处理方法, 图 5示出了本申请实施例提供的事件 处理终端设备的示意框图, 为了便于说明, 仅示出了与本申请实施例相关的部 分。  [0114] Corresponding to the event processing method described in the foregoing embodiment, FIG. 5 is a schematic block diagram of the event processing terminal device provided by the embodiment of the present application. For the convenience of description, only the related to the embodiment of the present application is shown. section.
[0115] 在本实施例中, 所述事件处理终端设备可以是桌上型计算机、 笔记本、 掌上电 脑及云端服务器等计算设备。 该事件处理终端设备可包括: 处理器 50、 存储器 5 1以及存储在所述存储器 51中并可在所述处理器 50上运行的计算机可读指令 52。  [0115] In this embodiment, the event processing terminal device may be a computing device such as a desktop computer, a notebook, a palmtop computer, or a cloud server. The event processing terminal device can include: a processor 50, a memory 51, and computer readable instructions 52 stored in the memory 51 and executable on the processor 50.
[0116] 所述处理器 50可以是中央处理单元 (Central Processing Unit, CPU) , 还可以是其 他通用处理器、 数字信号处理器(Digital Signal Processor, DSP)、 专用集成电路 (Application Specific Integrated Circuit, ASIC)、 现场可编程门阵列  [0116] The processor 50 may be a central processing unit (CPU), or may be another general-purpose processor, a digital signal processor (DSP), or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), field programmable gate array
(Field-Programmable Gate Array , FPGA)或者其他可编程逻辑器件、 分立门或者 晶体管逻辑器件、 分立硬件组件等。 通用处理器可以是微处理器或者该处理器 也可以是任何常规的处理器等。  (Field-Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
[0117] 所述存储器 51可以是所述事件处理终端设备 5的内部存储单元, 例如事件处理 终端设备 5的硬盘或内存。 所述存储器 51也可以是所述事件处理终端设备 5的外 部存储设备, 例如所述事件处理终端设备 5上配备的插接式硬盘, 智能存储卡 ( Smart Media Card, SMC) , 安全数字 (Secure Digital, SD) 卡, 闪存卡 (Flash Card) 等。 进一步地, 所述存储器 51还可以既包括所述事件处理终端设备 5的内 部存储单元也包括外部存储设备。 所述存储器 51用于存储所述计算机可读指令 以及所述事件处理终端设备 5所需的其它程序和数据。 所述存储器 51还可以用于 暂吋地存储已经输出或者将要输出的数据。 [0117] The memory 51 may be an internal storage unit of the event processing terminal device 5, such as event processing The hard disk or memory of the terminal device 5. The memory 51 may also be an external storage device of the event processing terminal device 5, such as a plug-in hard disk equipped on the event processing terminal device 5, a smart memory card (SMC), and a secure digital (Secure) Digital, SD) cards, flash cards, etc. Further, the memory 51 may also include both an internal storage unit of the event processing terminal device 5 and an external storage device. The memory 51 is used to store the computer readable instructions and other programs and data required by the event processing terminal device 5. The memory 51 can also be used to temporarily store data that has been output or is about to be output.
[0118] 请参阅图 6, 是本申请实施例提供的计算机可读指令 52的功能模块图。 在本实 施例中, 所述的计算机可读指令 52可以被分割成一个或多个模块, 所述一个或 者多个模块被存储于所述存储器 51中, 并由所述处理器 50所执行, 以完成本申 请。 例如, 在图 5中, 所述的计算机可读指令 52可以被分割成事件获取模块 601 、 目标事件规则选取模块 602和事件处理模块 603。 本申请所称的模块是指能够 完成特定功能的一系列计算机可读指令的指令段, 比程序更适合于描述所述计 算机可读指令 52在所述事件处理终端设备中的执行过程。 以下描述将具体介绍 所述模块 601-603的功能。  [0118] Please refer to FIG. 6, which is a functional block diagram of computer readable instructions 52 provided by an embodiment of the present application. In this embodiment, the computer readable instructions 52 may be divided into one or more modules, and the one or more modules are stored in the memory 51 and executed by the processor 50. To complete this application. For example, in FIG. 5, the computer readable instructions 52 may be partitioned into an event acquisition module 601, a target event rule selection module 602, and an event processing module 603. A module as referred to in this application refers to a series of computer readable instructions that are capable of performing a particular function, and is more suitable than the program to describe the execution of the computer readable instructions 52 in the event processing terminal. The following description will specifically describe the functions of the modules 601-603.
[0119] 事件获取模块 601, 用于获取在预设的处理间隔内被触发的各个事件;  [0119] an event obtaining module 601, configured to acquire each event that is triggered within a preset processing interval;
[0120] 目标事件规则选取模块 602, 用于从预设的事件规则库中选取一个事件规则作 为当前的目标事件规则, 所述事件规则为两个事件之间先后顺序的依赖关系; [0120] The target event rule selection module 602 is configured to select an event rule from the preset event rule base as the current target event rule, where the event rule is a sequential dependency relationship between the two events;
[0121] 事件处理模块 603, 用于根据所述目标事件规则执行事件处理流程; [0121] an event processing module 603, configured to execute an event processing process according to the target event rule;
[0122] 具体地, 所述事件处理模块 603可以包括:  [0122] Specifically, the event processing module 603 may include:
[0123] 第一条件判断单元 6031, 用于若所述目标事件规则为第一类型事件规则, 则判 断在获取的所述各个事件中的第一事件与第二事件是否满足第一条件, 所述第 一条件为所述第一事件被触发后预设的第一吋间间隔内所述第二事件也被触发 , 所述第一事件和所述第二事件均与第一用户对应;  [0123] The first condition determining unit 6031 is configured to determine, if the target event rule is a first type of event rule, determine whether the first event and the second event in the acquired each event meet the first condition, The first condition is that the second event is also triggered in the preset first inter-day interval after the first event is triggered, and the first event and the second event are both corresponding to the first user;
[0124] 第一动作执行单元 6032, 用于若所述第一事件与所述第二事件满足所述第一条 件, 则执行针对所述第一用户的预设的第一动作;  [0124] The first action execution unit 6032 is configured to: if the first event and the second event satisfy the first condition, perform a preset first action for the first user;
[0125] 第二条件判断单元 6033, 用于若所述目标事件规则为第二类型事件规则, 则判 断在获取的所述各个事件中的第三事件与第***是否满足第二条件, 所述第 二条件为所述第三事件被触发后预设的第二吋间间隔内所述第***未被触发 , 所述第三事件和所述第***均与第二用户对应; [0125] The second condition determining unit 6033 is configured to determine, if the target event rule is the second type event rule, whether the third event and the fourth event in the acquired each event meet the second condition, Narrative The second condition is that the fourth event is not triggered in the preset second inter-second interval after the third event is triggered, and the third event and the fourth event are both corresponding to the second user;
[0126] 第二动作执行单元 6034, 用于若所述第三事件与所述第***满足所述第二条 件, 则执行针对所述第二用户的预设的第二动作。  [0126] The second action execution unit 6034 is configured to perform a second action preset for the second user if the third event and the fourth event satisfy the second condition.
[0127] 进一步地, 所述第一条件判断单元 6031可以包括: [0127] Further, the first condition determining unit 6031 may include:
[0128] 第二事件査找子单元, 用于在获取的所述各个事件中査找所述第二事件; [0129] 第一事件査找子单元, 用于若在获取的所述各个事件中査找到所述第二事件, 则在获取的所述各个事件中査找与所述第二事件的用户标识相同的第一事件, 所述用户标识为用户的唯一标识;  [0128] a second event search subunit, configured to search for the second event in the acquired respective events; [0129] a first event search subunit, configured to: if found in the obtained each event And the second event, in the obtained each event, searching for the first event that is the same as the user identifier of the second event, where the user identifier is a unique identifier of the user;
[0130] 第一判定子单元, 用于若在获取的所述各个事件中査找到与所述第二事件的用 户标识相同的所述第一事件, 且从所述第一事件到所述第二事件的吋间间隔小 于等于所述第一吋间间隔, 则判定所述第一事件与所述第二事件满足所述第一 条件。 [0130] a first determining subunit, configured to: if the first event that is the same as the user identifier of the second event is found in the acquired respective events, and from the first event to the first If the inter-time interval of the two events is less than or equal to the first inter-turn interval, it is determined that the first event and the second event satisfy the first condition.
[0131] 进一步地, 所述第一条件判断单元 6033可以包括:  [0131] Further, the first condition determining unit 6033 may include:
[0132] 第三事件査找子单元, 用于在获取的所述各个事件中査找所述第三事件; [0133] 第***査找子单元, 用于若在获取的所述各个事件中査找到所述第三事件, 则在获取的所述各个事件中査找与所述第三事件的用户标识相同的第***, 所述用户标识为用户的唯一标识;  [0132] a third event search subunit, configured to search for the third event in the acquired respective events; [0133] a fourth event search subunit, configured to: if found in the obtained each event And the third event, in the obtained each event, searching for the fourth event that is the same as the user identifier of the third event, where the user identifier is a unique identifier of the user;
[0134] 第二判定子单元, 用于若在获取的所述各个事件中未査找到与所述第三事件的 用户标识相同的所述第***, 或从所述第三事件到所述第***的吋间间隔 大于所述第二吋间间隔, 则判定所述第三事件与所述第***满足所述第二条 件。 [0134] a second determining subunit, configured to: if the fourth event that is the same as the user identifier of the third event is not found in the acquired respective events, or from the third event to the If the inter-turn interval of the fourth event is greater than the second inter-turn interval, it is determined that the third event and the fourth event satisfy the second condition.
[0135] 进一步地, 所述事件获取模块 601可以包括:  [0135] Further, the event obtaining module 601 may include:
[0136] 事件捕获单元, 用于通过预设的插件实吋捕获与预设的事件编码对应的事件; [0137] 事件添加单元, 用于将用户标识、 事件编码和事件触发吋间添加入捕获的所述 事件中;  [0136] an event capture unit, configured to capture an event corresponding to the preset event code by using a preset plugin; [0137] an event adding unit, configured to add a user identifier, an event code, and an event trigger to the capture In the event;
[0138] 事件存储单元, 用于将所述事件存储入预设的事件库中。  [0138] an event storage unit, configured to store the event in a preset event library.
[0139] 进一步地, 所述事件处理模块 603还可以包括: [0140] 动作统计单元, 用于从历史动作记录中统计在预设的第三吋间间隔内针对所述 第二用户的所述第二动作被执行的总次数; [0139] Further, the event processing module 603 may further include: [0140] an action statistics unit, configured to count, from the historical action record, a total number of times the second action for the second user is performed within a preset third inter-day interval;
[0141] 第三动作执行单元, 用于若所述总次数大于预设的阈值, 则执行针对所述第二 用户的预设的第三动作。 [0141] The third action execution unit is configured to execute a preset third action for the second user if the total number of times is greater than a preset threshold.
[0142] 另外, 在本申请各个实施例中的各功能单元可以集成在一个处理单元中, 也可 以是各个单元单独物理存在, 也可以两个或两个以上单元集成在一个单元中。 上述集成的单元既可以采用硬件的形式实现, 也可以采用软件功能单元的形式 实现。 In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
[0143] 所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用 吋, 可以存储在一个计算机可读取存储介质中。 基于这样的理解, 本申请的技 术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分 可以以软件产品的形式体现出来, 该计算机软件产品存储在一个存储介质中, 包括若干指令用以使得一台计算机设备 (可以是个人计算机, 服务器, 或者网 络设备等) 执行本申请各个实施例所述方法的全部或部分步骤。 而前述的存储 介质包括: U盘、 移动硬盘、 只读存储器 (ROM, Read-Only Memory) 、 随机 存取存储器 (RAM, Random Access Memory) 、 磁碟或者光盘等各种可以存储 程序代码的介质。  [0143] The integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application, in essence or the contribution to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium. A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application. The foregoing storage medium includes: a U disk, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like, which can store program codes. .
[0144] 以上所述, 以上实施例仅用以说明本申请的技术方案, 而非对其限制; 尽管参 照前述实施例对本申请进行了详细的说明, 本领域的普通技术人员应当理解: 其依然可以对前述各实施例所记载的技术方案进行修改, 或者对其中部分技术 特征进行等同替换; 而这些修改或者替换, 并不使相应技术方案的本质脱离本 申请各实施例技术方案的精神和范围。  The above embodiments are only used to explain the technical solutions of the present application, and are not limited thereto; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that The technical solutions described in the foregoing embodiments may be modified, or some of the technical features may be equivalently replaced; and the modifications or substitutions do not deviate from the spirit and scope of the technical solutions of the embodiments of the present application. .

Claims

权利要求书 Claim
[权利要求 1] 一种事件处理方法, 其特征在于, 包括:  [Claim 1] An event processing method, comprising:
获取在预设的处理间隔内被触发的各个事件;  Obtaining individual events that are triggered within a preset processing interval;
从预设的事件规则库中选取一个事件规则作为当前的目标事件规则, 所述事件规则为两个事件之间先后顺序的依赖关系;  Selecting an event rule from the preset event rule base as the current target event rule, and the event rule is a sequential dependency relationship between the two events;
根据所述目标事件规则执行事件处理流程;  Performing an event processing flow according to the target event rule;
从所述事件规则库的未被选取过的事件规则中选取一个事件规则作为 当前的目标事件规则, 然后返回执行所述根据所述目标事件规则执行 事件处理流程的步骤, 直至所述事件规则库中所有事件规则均被选取 过;  Selecting an event rule from the unselected event rule of the event rule base as the current target event rule, and then returning to execute the step of executing the event processing flow according to the target event rule until the event rule base All event rules have been selected;
所述根据所述目标事件规则执行事件处理流程包括:  The executing the event processing procedure according to the target event rule includes:
若所述目标事件规则为第一类型事件规则, 则判断在获取的所述各个 事件中的第一事件与第二事件是否满足第一条件, 所述第一条件为所 述第一事件被触发后预设的第一吋间间隔内所述第二事件也被触发, 所述第一事件和所述第二事件均与第一用户对应; 若所述第一事件与所述第二事件满足所述第一条件, 则执行针对所述 第一用户的预设的第一动作;  If the target event rule is a first type of event rule, determining whether the first event and the second event in the acquired respective events meet the first condition, where the first condition is that the first event is triggered The second event is also triggered in the first preset interval, the first event and the second event are both corresponding to the first user; if the first event and the second event are satisfied The first condition, performing a preset first action for the first user;
若所述目标事件规则为第二类型事件规则, 则判断在获取的所述各个 事件中的第三事件与第***是否满足第二条件, 所述第二条件为所 述第三事件被触发后预设的第二吋间间隔内所述第***未被触发, 所述第三事件和所述第***均与第二用户对应; 若所述第三事件与所述第***满足所述第二条件, 则执行针对所述 第二用户的预设的第二动作。  If the target event rule is a second type of event rule, determining whether the third event and the fourth event in the acquired respective events satisfy the second condition, where the second condition is that the third event is triggered The fourth event is not triggered in the second preset interval, the third event and the fourth event are both corresponding to the second user; if the third event and the fourth event are satisfied The second condition then performs a second action preset for the second user.
[权利要求 2] 根据权利要求 1所述的事件处理方法, 其特征在于, 所述判断在获取 的所述各个事件中的第一事件与第二事件是否满足第一条件包括: 在获取的所述各个事件中査找所述第二事件;  [Claim 2] The event processing method according to claim 1, wherein the determining whether the first event and the second event in the acquired respective events satisfy the first condition comprises: Finding the second event in each event;
若在获取的所述各个事件中査找到所述第二事件, 则在获取的所述各 个事件中査找与所述第二事件的用户标识相同的第一事件, 所述用户 标识为用户的唯一标识; If the second event is found in the obtained each event, searching for the first event that is the same as the user identifier of the second event in the obtained each event, the user A unique identifier identified as a user;
若在获取的所述各个事件中査找到与所述第二事件的用户标识相同的 所述第一事件, 且从所述第一事件到所述第二事件的吋间间隔小于等 于所述第一吋间间隔, 则判定所述第一事件与所述第二事件满足所述 第一条件。  If the first event that is the same as the user identifier of the second event is found in the obtained each event, and the interval between the first event and the second event is less than or equal to the first event An inter-time interval determines that the first event and the second event satisfy the first condition.
[权利要求 3] 根据权利要求 1所述的事件处理方法, 其特征在于, 所述判断在获取 的所述各个事件中的第三事件与第***是否满足第二条件包括: 在获取的所述各个事件中査找所述第三事件;  [Claim 3] The event processing method according to claim 1, wherein the determining whether the third event and the fourth event in the acquired respective events satisfy the second condition comprises: Finding the third event in each event;
若在获取的所述各个事件中査找到所述第三事件, 则在获取的所述各 个事件中査找与所述第三事件的用户标识相同的第***, 所述用户 标识为用户的唯一标识;  If the third event is found in the obtained event, the fourth event that is the same as the user identifier of the third event is searched for, and the user identifier is unique to the user. Identification
若在获取的所述各个事件中未査找到与所述第三事件的用户标识相同 的所述第***, 或从所述第三事件到所述第***的吋间间隔大于 所述第二吋间间隔, 则判定所述第三事件与所述第***满足所述第 二条件。  If the fourth event that is the same as the user identifier of the third event is not found in the obtained respective events, or the interval between the third event and the fourth event is greater than the first And the second event determines that the third event and the fourth event satisfy the second condition.
[权利要求 4] 根据权利要求 1中所述的事件处理方法, 其特征在于, 所述获取在预 设的处理间隔内被触发的各个事件包括:  [Claim 4] The event processing method according to claim 1, wherein the acquiring each event triggered within a preset processing interval comprises:
通过预设的插件实吋捕获与预设的事件编码对应的事件;  The event corresponding to the preset event code is captured by a preset plug-in;
将用户标识、 事件编码和事件触发吋间添加入捕获的所述事件中; 将所述事件存储入预设的事件库中。  User identification, event encoding, and event triggering are added to the captured event; the event is stored in a preset event library.
[权利要求 5] 根据权利要求 1至 4中任一项所述的事件处理方法, 其特征在于, 在执 行针对所述第二用户的预设的第二动作之后, 还包括:  [Claim 5] The event processing method according to any one of claims 1 to 4, further comprising: after performing the second action preset for the second user, further comprising:
从历史动作记录中统计在预设的第三吋间间隔内针对所述第二用户的 所述第二动作被执行的总次数;  Counting, from the historical action record, the total number of times the second action for the second user is performed within a preset third inter-day interval;
若所述总次数大于预设的阈值, 则执行针对所述第二用户的预设的第 三动作。  If the total number of times is greater than a preset threshold, a third action preset for the second user is performed.
[权利要求 6] —种计算机可读存储介质, 所述计算机可读存储介质存储有计算机可 读指令, 其特征在于, 所述计算机可读指令被处理器执行吋实现如下 步骤: [Claim 6] A computer readable storage medium storing computer readable instructions, wherein the computer readable instructions are executed by a processor and implemented as follows Steps:
获取在预设的处理间隔内被触发的各个事件;  Obtaining individual events that are triggered within a preset processing interval;
从预设的事件规则库中选取一个事件规则作为当前的目标事件规则, 所述事件规则为两个事件之间先后顺序的依赖关系;  Selecting an event rule from the preset event rule base as the current target event rule, and the event rule is a sequential dependency relationship between the two events;
根据所述目标事件规则执行事件处理流程;  Performing an event processing flow according to the target event rule;
从所述事件规则库的未被选取过的事件规则中选取一个事件规则作为 当前的目标事件规则, 然后返回执行所述根据所述目标事件规则执行 事件处理流程的步骤, 直至所述事件规则库中所有事件规则均被选取 过;  Selecting an event rule from the unselected event rule of the event rule base as the current target event rule, and then returning to execute the step of executing the event processing flow according to the target event rule until the event rule base All event rules have been selected;
所述根据所述目标事件规则执行事件处理流程包括:  The executing the event processing procedure according to the target event rule includes:
若所述目标事件规则为第一类型事件规则, 则判断在获取的所述各个 事件中的第一事件与第二事件是否满足第一条件, 所述第一条件为所 述第一事件被触发后预设的第一吋间间隔内所述第二事件也被触发, 所述第一事件和所述第二事件均与第一用户对应; 若所述第一事件与所述第二事件满足所述第一条件, 则执行针对所述 第一用户的预设的第一动作;  If the target event rule is a first type of event rule, determining whether the first event and the second event in the acquired respective events meet the first condition, where the first condition is that the first event is triggered The second event is also triggered in the first preset interval, the first event and the second event are both corresponding to the first user; if the first event and the second event are satisfied The first condition, performing a preset first action for the first user;
若所述目标事件规则为第二类型事件规则, 则判断在获取的所述各个 事件中的第三事件与第***是否满足第二条件, 所述第二条件为所 述第三事件被触发后预设的第二吋间间隔内所述第***未被触发, 所述第三事件和所述第***均与第二用户对应; 若所述第三事件与所述第***满足所述第二条件, 则执行针对所述 第二用户的预设的第二动作。  If the target event rule is a second type of event rule, determining whether the third event and the fourth event in the acquired respective events satisfy the second condition, where the second condition is that the third event is triggered The fourth event is not triggered in the second preset interval, the third event and the fourth event are both corresponding to the second user; if the third event and the fourth event are satisfied The second condition then performs a second action preset for the second user.
[权利要求 7] 根据权利要求 6所述的计算机可读存储介质, 其特征在于, 所述判断 在获取的所述各个事件中的第一事件与第二事件是否满足第一条件包 括: The computer readable storage medium according to claim 6, wherein the determining whether the first event and the second event in the acquired respective events satisfy the first condition comprises:
在获取的所述各个事件中査找所述第二事件;  Finding the second event in the obtained respective events;
若在获取的所述各个事件中査找到所述第二事件, 则在获取的所述各 个事件中査找与所述第二事件的用户标识相同的第一事件, 所述用户 标识为用户的唯一标识; If the second event is found in the obtained each event, searching for the first event that is the same as the user identifier of the second event in the obtained each event, the user A unique identifier identified as a user;
若在获取的所述各个事件中査找到与所述第二事件的用户标识相同的 所述第一事件, 且从所述第一事件到所述第二事件的吋间间隔小于等 于所述第一吋间间隔, 则判定所述第一事件与所述第二事件满足所述 第一条件。  If the first event that is the same as the user identifier of the second event is found in the obtained each event, and the interval between the first event and the second event is less than or equal to the first event An inter-time interval determines that the first event and the second event satisfy the first condition.
[权利要求 8] 根据权利要求 6所述的计算机可读存储介质, 其特征在于, 所述判断 在获取的所述各个事件中的第三事件与第***是否满足第二条件包 括:  [Claim 8] The computer readable storage medium according to claim 6, wherein the determining whether the third event and the fourth event in the acquired respective events satisfy the second condition comprises:
在获取的所述各个事件中査找所述第三事件;  Finding the third event in the obtained respective events;
若在获取的所述各个事件中査找到所述第三事件, 则在获取的所述各 个事件中査找与所述第三事件的用户标识相同的第***, 所述用户 标识为用户的唯一标识;  If the third event is found in the obtained event, the fourth event that is the same as the user identifier of the third event is searched for, and the user identifier is unique to the user. Identification
若在获取的所述各个事件中未査找到与所述第三事件的用户标识相同 的所述第***, 或从所述第三事件到所述第***的吋间间隔大于 所述第二吋间间隔, 则判定所述第三事件与所述第***满足所述第 二条件。  If the fourth event that is the same as the user identifier of the third event is not found in the obtained respective events, or the interval between the third event and the fourth event is greater than the first And the second event determines that the third event and the fourth event satisfy the second condition.
[权利要求 9] 根据权利要求 6中所述的计算机可读存储介质, 其特征在于, 所述获 取在预设的处理间隔内被触发的各个事件包括: 通过预设的插件实吋捕获与预设的事件编码对应的事件;  [Claim 9] The computer readable storage medium according to claim 6, wherein the acquiring, the event that is triggered within a preset processing interval comprises: capturing and pre-presetting through a preset plug-in The event corresponding to the event code;
将用户标识、 事件编码和事件触发吋间添加入捕获的所述事件中; 将所述事件存储入预设的事件库中。  User identification, event encoding, and event triggering are added to the captured event; the event is stored in a preset event library.
[权利要求 10] 根据权利要求 6至 9中任一项所述的计算机可读存储介质, 其特征在于 , 在执行针对所述第二用户的预设的第二动作之后, 还包括: 从历史动作记录中统计在预设的第三吋间间隔内针对所述第二用户的 所述第二动作被执行的总次数;  [Claim 10] The computer readable storage medium according to any one of claims 6 to 9, wherein after performing the second action preset for the second user, further comprising: from history Counting, in the action record, the total number of times the second action for the second user is performed within a preset third inter-day interval;
若所述总次数大于预设的阈值, 则执行针对所述第二用户的预设的第 三动作。  If the total number of times is greater than a preset threshold, a third action preset for the second user is performed.
[权利要求 11] 一种事件处理终端设备, 包括存储器、 处理器以及存储在所述存储器 中并可在所述处理器上运行的计算机可读指令, 其特征在于, 所述处 理器执行所述计算机可读指令吋实现如下步骤: 获取在预设的处理间隔内被触发的各个事件; [Claim 11] An event processing terminal device including a memory, a processor, and a memory stored in the memory And computer readable instructions executable on the processor, wherein the processor executes the computer readable instructions to: obtain respective events that are triggered within a preset processing interval;
从预设的事件规则库中选取一个事件规则作为当前的目标事件规则, 所述事件规则为两个事件之间先后顺序的依赖关系;  Selecting an event rule from the preset event rule base as the current target event rule, and the event rule is a sequential dependency relationship between the two events;
根据所述目标事件规则执行事件处理流程;  Performing an event processing flow according to the target event rule;
从所述事件规则库的未被选取过的事件规则中选取一个事件规则作为 当前的目标事件规则, 然后返回执行所述根据所述目标事件规则执行 事件处理流程的步骤, 直至所述事件规则库中所有事件规则均被选取 过;  Selecting an event rule from the unselected event rule of the event rule base as the current target event rule, and then returning to execute the step of executing the event processing flow according to the target event rule until the event rule base All event rules have been selected;
所述根据所述目标事件规则执行事件处理流程包括:  The executing the event processing procedure according to the target event rule includes:
若所述目标事件规则为第一类型事件规则, 则判断在获取的所述各个 事件中的第一事件与第二事件是否满足第一条件, 所述第一条件为所 述第一事件被触发后预设的第一吋间间隔内所述第二事件也被触发, 所述第一事件和所述第二事件均与第一用户对应; 若所述第一事件与所述第二事件满足所述第一条件, 则执行针对所述 第一用户的预设的第一动作;  If the target event rule is a first type of event rule, determining whether the first event and the second event in the acquired respective events meet the first condition, where the first condition is that the first event is triggered The second event is also triggered in the first preset interval, the first event and the second event are both corresponding to the first user; if the first event and the second event are satisfied The first condition, performing a preset first action for the first user;
若所述目标事件规则为第二类型事件规则, 则判断在获取的所述各个 事件中的第三事件与第***是否满足第二条件, 所述第二条件为所 述第三事件被触发后预设的第二吋间间隔内所述第***未被触发, 所述第三事件和所述第***均与第二用户对应; 若所述第三事件与所述第***满足所述第二条件, 则执行针对所述 第二用户的预设的第二动作。  If the target event rule is a second type of event rule, determining whether the third event and the fourth event in the acquired respective events satisfy the second condition, where the second condition is that the third event is triggered The fourth event is not triggered in the second preset interval, the third event and the fourth event are both corresponding to the second user; if the third event and the fourth event are satisfied The second condition then performs a second action preset for the second user.
[权利要求 12] 根据权利要求 11所述的事件处理终端设备, 其特征在于, 所述判断在 获取的所述各个事件中的第一事件与第二事件是否满足第一条件包括 在获取的所述各个事件中査找所述第二事件; [Claim 12] The event processing terminal device according to claim 11, wherein the determining whether the first event and the second event in the acquired respective events satisfy the first condition is included in the acquired location Finding the second event in each event;
若在获取的所述各个事件中査找到所述第二事件, 则在获取的所述各 个事件中査找与所述第二事件的用户标识相同的第一事件, 所述用户 标识为用户的唯一标识; If the second event is found in each of the acquired events, the acquired Finding a first event that is the same as the user identifier of the second event, where the user identifier is a unique identifier of the user;
若在获取的所述各个事件中査找到与所述第二事件的用户标识相同的 所述第一事件, 且从所述第一事件到所述第二事件的吋间间隔小于等 于所述第一吋间间隔, 则判定所述第一事件与所述第二事件满足所述 第一条件。  If the first event that is the same as the user identifier of the second event is found in the obtained each event, and the interval between the first event and the second event is less than or equal to the first event An inter-time interval determines that the first event and the second event satisfy the first condition.
[权利要求 13] 根据权利要求 11所述的事件处理终端设备, 其特征在于, 所述判断在 获取的所述各个事件中的第三事件与第***是否满足第二条件包括 在获取的所述各个事件中査找所述第三事件;  [Claim 13] The event processing terminal device according to claim 11, wherein the determining whether the third event and the fourth event in the acquired respective events satisfy the second condition is included in the acquired location Finding the third event in each event;
若在获取的所述各个事件中査找到所述第三事件, 则在获取的所述各 个事件中査找与所述第三事件的用户标识相同的第***, 所述用户 标识为用户的唯一标识;  If the third event is found in the obtained event, the fourth event that is the same as the user identifier of the third event is searched for, and the user identifier is unique to the user. Identification
若在获取的所述各个事件中未査找到与所述第三事件的用户标识相同 的所述第***, 或从所述第三事件到所述第***的吋间间隔大于 所述第二吋间间隔, 则判定所述第三事件与所述第***满足所述第 二条件。  If the fourth event that is the same as the user identifier of the third event is not found in the obtained respective events, or the interval between the third event and the fourth event is greater than the first And the second event determines that the third event and the fourth event satisfy the second condition.
[权利要求 14] 根据权利要求 11所述的事件处理终端设备, 其特征在于, 所述获取在 预设的处理间隔内被触发的各个事件包括:  [Claim 14] The event processing terminal device according to claim 11, wherein the acquiring each event that is triggered within a preset processing interval comprises:
通过预设的插件实吋捕获与预设的事件编码对应的事件;  The event corresponding to the preset event code is captured by a preset plug-in;
将用户标识、 事件编码和事件触发吋间添加入捕获的所述事件中; 将所述事件存储入预设的事件库中。  User identification, event encoding, and event triggering are added to the captured event; the event is stored in a preset event library.
[权利要求 15] 根据权利要求 11至 14中任一项所述的事件处理终端设备, 其特征在于 , 在执行针对所述第二用户的预设的第二动作之后, 还包括: 从历史动作记录中统计在预设的第三吋间间隔内针对所述第二用户的 所述第二动作被执行的总次数;  [Claim 15] The event processing terminal device according to any one of claims 11 to 14, wherein after performing the second action preset for the second user, the method further comprises: Counting, in the record, the total number of times the second action for the second user is performed within a preset third inter-day interval;
若所述总次数大于预设的阈值, 则执行针对所述第二用户的预设的第 三动作。 If the total number of times is greater than a preset threshold, performing a preset third action for the second user.
[权利要求 16] —种事件处理程序, 其特征在于, 包括: [Claim 16] An event handler, comprising:
事件获取模块, 用于获取在预设的处理间隔内被触发的各个事件; 目标事件规则选取模块, 用于从预设的事件规则库中选取一个事件规 则作为当前的目标事件规则, 所述事件规则为两个事件之间先后顺序 的依赖关系;  An event obtaining module, configured to acquire each event that is triggered within a preset processing interval; a target event rule selecting module, configured to select an event rule from the preset event rule base as a current target event rule, where the event A rule is a sequential dependency between two events;
事件处理模块, 用于根据所述目标事件规则执行事件处理流程; 具体地, 所述事件处理模块包括:  An event processing module, configured to execute an event processing process according to the target event rule; specifically, the event processing module includes:
第一条件判断单元, 用于若所述目标事件规则为第一类型事件规则, 则判断在获取的所述各个事件中的第一事件与第二事件是否满足第一 条件, 所述第一条件为所述第一事件被触发后预设的第一吋间间隔内 所述第二事件也被触发, 所述第一事件和所述第二事件均与第一用户 对应;  a first condition determining unit, configured to determine, if the target event rule is a first type of event rule, determining whether the first event and the second event in the acquired respective events satisfy the first condition, the first condition The second event is also triggered in the first inter-time interval preset after the first event is triggered, and the first event and the second event are both corresponding to the first user;
第一动作执行单元, 用于若所述第一事件与所述第二事件满足所述第 一条件, 则执行针对所述第一用户的预设的第一动作;  a first action execution unit, configured to execute a preset first action for the first user if the first event and the second event satisfy the first condition;
第二条件判断单元, 用于若所述目标事件规则为第二类型事件规则, 则判断在获取的所述各个事件中的第三事件与第***是否满足第二 条件, 所述第二条件为所述第三事件被触发后预设的第二吋间间隔内 所述第***未被触发, 所述第三事件和所述第***均与第二用户 对应;  a second condition determining unit, configured to determine, if the target event rule is a second type of event rule, whether the third event and the fourth event in the acquired respective events satisfy the second condition, the second condition The fourth event is not triggered in the second inter-time interval preset after the third event is triggered, and the third event and the fourth event are both corresponding to the second user;
第二动作执行单元, 用于若所述第三事件与所述第***满足所述第 二条件, 则执行针对所述第二用户的预设的第二动作。  a second action execution unit, configured to execute a second action preset for the second user if the third event and the fourth event satisfy the second condition.
[权利要求 17] 根据权利要求 16所述的事件处理程序, 其特征在于, 所述第一条件判 断单元包括: [Claim 17] The event processing program according to claim 16, wherein the first condition determining unit comprises:
第二事件査找子单元, 用于在获取的所述各个事件中査找所述第二事 件;  a second event finding subunit, configured to search for the second event in the obtained each event;
第一事件査找子单元, 用于若在获取的所述各个事件中査找到所述第 二事件, 则在获取的所述各个事件中査找与所述第二事件的用户标识 相同的第一事件, 所述用户标识为用户的唯一标识; 第一判定子单元, 用于若在获取的所述各个事件中査找到与所述第二 事件的用户标识相同的所述第一事件, 且从所述第一事件到所述第二 事件的吋间间隔小于等于所述第一吋间间隔, 则判定所述第一事件与 所述第二事件满足所述第一条件。 a first event finding subunit, configured to: if the second event is found in the obtained each event, searching for the first event that is the same as the user identifier of the second event in the obtained each event The user identifier is a unique identifier of the user; a first determining subunit, configured to: if the first event that is the same as the user identifier of the second event is found in the acquired respective events, and from the first event to the second event If the inter-turn interval is less than or equal to the first inter-turn interval, it is determined that the first event and the second event satisfy the first condition.
[权利要求 18] 根据权利要求 16所述的事件处理程序, 其特征在于, 所述第一条件判 断单元包括:  [Claim 18] The event processing program according to claim 16, wherein the first condition determining unit comprises:
第三事件査找子单元, 用于在获取的所述各个事件中査找所述第三事 件;  a third event finding subunit, configured to search for the third event in the obtained each event;
第***査找子单元, 用于若在获取的所述各个事件中査找到所述第 三事件, 则在获取的所述各个事件中査找与所述第三事件的用户标识 相同的第***, 所述用户标识为用户的唯一标识;  a fourth event finding subunit, configured to: if the third event is found in the obtained each event, searching for the fourth event that is the same as the user identifier of the third event in the obtained each event The user identifier is a unique identifier of the user;
第二判定子单元, 用于若在获取的所述各个事件中未査找到与所述第 三事件的用户标识相同的所述第***, 或从所述第三事件到所述第 ***的吋间间隔大于所述第二吋间间隔, 则判定所述第三事件与所 述第***满足所述第二条件。  a second determining subunit, configured to: if the fourth event that is the same as the user identifier of the third event is not found in the acquired respective events, or from the third event to the fourth event The inter-turn interval is greater than the second inter-turn interval, and it is determined that the third event and the fourth event satisfy the second condition.
[权利要求 19] 根据权利要求 16所述的事件处理程序, 其特征在于, 所述事件获取模 块包括: [Claim 19] The event processing program according to claim 16, wherein the event acquisition module comprises:
事件捕获单元, 用于通过预设的插件实吋捕获与预设的事件编码对应 的事件;  An event capture unit, configured to capture an event corresponding to the preset event code by using a preset plug-in;
事件添加单元, 用于将用户标识、 事件编码和事件触发吋间添加入捕 获的所述事件中;  An event adding unit, configured to add a user identifier, an event code, and an event trigger to the captured event;
事件存储单元, 用于将所述事件存储入预设的事件库中。  An event storage unit, configured to store the event in a preset event library.
[权利要求 20] 根据权利要求 16至 19中任一项所述的事件处理程序, 其特征在于, 所 述事件处理模块还包括: [Claim 20] The event processing program according to any one of claims 16 to 19, wherein the event processing module further comprises:
动作统计单元, 用于从历史动作记录中统计在预设的第三吋间间隔内 针对所述第二用户的所述第二动作被执行的总次数;  An action statistics unit, configured to count, from the historical action record, a total number of times the second action for the second user is performed within a preset third inter-day interval;
第三动作执行单元, 用于若所述总次数大于预设的阈值, 则执行针对 所述第二用户的预设的第三动作。  And a third action execution unit, configured to execute a preset third action for the second user if the total number of times is greater than a preset threshold.
PCT/CN2017/104540 2017-07-27 2017-09-29 Event processing method and terminal device WO2019019373A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710624517.1A CN107481039A (en) 2017-07-27 2017-07-27 A kind of event-handling method and terminal device
CN201710624517.1 2017-07-27

Publications (1)

Publication Number Publication Date
WO2019019373A1 true WO2019019373A1 (en) 2019-01-31

Family

ID=60597731

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/104540 WO2019019373A1 (en) 2017-07-27 2017-09-29 Event processing method and terminal device

Country Status (2)

Country Link
CN (1) CN107481039A (en)
WO (1) WO2019019373A1 (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111291774B (en) * 2018-12-07 2022-08-23 国网江苏省电力有限公司南京供电分公司 Power grid event sorting method and device based on Bayesian statistical decision
CN111309290B (en) * 2019-11-29 2023-05-26 上海金融期货信息技术有限公司 Flexible and extensible business rule matrix system
CN111125476A (en) * 2019-12-23 2020-05-08 北京每日优鲜电子商务有限公司 Event data processing method and device
CN113806113B (en) * 2021-09-28 2023-09-01 山东中创软件商用中间件股份有限公司 Event processing method, device, equipment and storage medium

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1372214A (en) * 2001-02-19 2002-10-02 意蓝科技股份有限公司 User's behaviour led network sale system and treatment method
CN102004983A (en) * 2009-08-31 2011-04-06 埃森哲环球服务有限公司 Web site trigger optimization system driving cross-channel operations
CN103580900A (en) * 2012-08-01 2014-02-12 上海宝信软件股份有限公司 Association analysis system based on event chains
CN103581824A (en) * 2012-08-10 2014-02-12 华为技术有限公司 Method and device for pushing user message

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050222996A1 (en) * 2004-03-30 2005-10-06 Oracle International Corporation Managing event-condition-action rules in a database system
US8762395B2 (en) * 2006-05-19 2014-06-24 Oracle International Corporation Evaluating event-generated data using append-only tables
CN101034974A (en) * 2007-03-29 2007-09-12 北京启明星辰信息技术有限公司 Associative attack analysis and detection method and device based on the time sequence and event sequence
CN102346894B (en) * 2010-08-03 2017-03-01 阿里巴巴集团控股有限公司 The output intent of recommendation information, system and server
CN105741507A (en) * 2014-12-08 2016-07-06 西安天动数字科技有限公司 Screen distance detection prevention shortsightedness prompting device
WO2016128121A1 (en) * 2015-02-12 2016-08-18 Amadeus S.A.S. Methods, systems, and computer program products for implementing a classification database
CN104616116A (en) * 2015-02-13 2015-05-13 武汉金锐达科技有限公司 Bank client service system and method
CN106327032A (en) * 2015-06-15 2017-01-11 阿里巴巴集团控股有限公司 Data analysis method used for customer loss early warning and data analysis device thereof
US10977748B2 (en) * 2015-09-24 2021-04-13 International Business Machines Corporation Predictive analytics for event mapping
CN106022900B (en) * 2016-08-08 2021-09-03 北京京东尚科信息技术有限公司 User risk data mining method and device
CN106355420A (en) * 2016-08-30 2017-01-25 江苏车置宝信息科技股份有限公司 Customer data quality identification and automatic order distribution system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1372214A (en) * 2001-02-19 2002-10-02 意蓝科技股份有限公司 User's behaviour led network sale system and treatment method
CN102004983A (en) * 2009-08-31 2011-04-06 埃森哲环球服务有限公司 Web site trigger optimization system driving cross-channel operations
CN103580900A (en) * 2012-08-01 2014-02-12 上海宝信软件股份有限公司 Association analysis system based on event chains
CN103581824A (en) * 2012-08-10 2014-02-12 华为技术有限公司 Method and device for pushing user message

Also Published As

Publication number Publication date
CN107481039A (en) 2017-12-15

Similar Documents

Publication Publication Date Title
AU2019232865B2 (en) Systems and methods for detecting and scoring anomalies
US10867034B2 (en) Method for detecting a cyber attack
US10069857B2 (en) Performing rule-based actions based on accessed domain name registrations
US10243967B2 (en) Method, apparatus and system for detecting fraudulant software promotion
WO2017113677A1 (en) User behavior data processing method and system
CN108304410B (en) Method and device for detecting abnormal access page and data analysis method
WO2019019373A1 (en) Event processing method and terminal device
US20170187737A1 (en) Method and electronic device for processing user behavior data
TW201737072A (en) Application program project evaluation method and system
CN108011752A (en) Fault locating analysis method and device, computer-readable recording medium
US9355250B2 (en) Method and system for rapidly scanning files
CN110781372B (en) Method and device for optimizing website, computer equipment and storage medium
US9866454B2 (en) Generating anonymous data from web data
CN110941738A (en) Recommendation method and device, electronic equipment and computer-readable storage medium
CN108664492B (en) Method and device for pushing content to user, electronic equipment and storage medium
Khan et al. The presence of Twitter bots and cyborgs in the# FeesMustFall campaign
US20140351005A1 (en) Data Collection Method and Apparatus
CN114900356A (en) Malicious user behavior detection method and device and electronic equipment
CN113127767B (en) Mobile phone number extraction method and device, electronic equipment and storage medium
CN104125105B (en) The method and apparatus classified to the Internet, applications place
CN111612550A (en) Advertisement trigger cheating identification method and device, electronic equipment and storage medium
CN110674386A (en) Resource recommendation method, device and storage medium
CN106484744B (en) Keyword uploading method and device
Perdeck ASP. NET Site Performance Secrets: Simple and Proven Techniques to Quickly Speed Up Your ASP. NET Web Site
CN116260601A (en) Network threat monitoring method and device, storage medium and terminal

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17919531

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17919531

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 05/08/2020)

122 Ep: pct application non-entry in european phase

Ref document number: 17919531

Country of ref document: EP

Kind code of ref document: A1