WO2019019373A1 - Event processing method and terminal device - Google Patents
Event processing method and terminal device Download PDFInfo
- 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
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION 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/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION 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/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0201—Market 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
Description
Claims
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)
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)
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)
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 |
-
2017
- 2017-07-27 CN CN201710624517.1A patent/CN107481039A/en active Pending
- 2017-09-29 WO PCT/CN2017/104540 patent/WO2019019373A1/en active Application Filing
Patent Citations (4)
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 |