WO2018188102A1 - Flow monitoring system - Google Patents

Abstract

A flow monitoring system (100), comprising: a monitoring module (10), used to periodically monitor a log generated during data interaction carried out by a user terminal; a determination module (20), used to determine whether there is a traffic sharing indication in the log, and if so, to output a prompt signal; and a prompt module (30), used to control the user terminal to issue reminder information according to the prompt signal.

Description

Traffic monitoring system Technical field

The present invention relates to the field of Internet, and in particular, to a traffic monitoring system.

Background technique

Social platforms such as WeChat, Weibo, and Facebook have become important tools for real-time communication between people. Moreover, on these platforms, more and more software that changes people's habits has been developed, such as sharing traffic software. . However, actions such as grabbing shared traffic can consume the user's attention, and users prefer to have a tool that automatically grabs traffic. However, in the two popular operating systems, Andriod and iOS, it is difficult to achieve fast and accurate traffic grabbing. The reasons are as follows: 1. When Andriod obtains the traffic request, there is no obvious text packet passing, and it is difficult to capture the required judgment signal. Second, although the iOS system has packets for each received message, it is binary, and it is difficult to Disassemble and parse in a short time.

Summary of the invention

The embodiment of the present invention provides a traffic monitoring system, including: a monitoring module, configured to periodically monitor a log generated when a user terminal performs data interaction; and a determining module, configured to determine whether a traffic sharing identifier exists in the log, and if yes, outputting a prompt And a prompting module, configured to control the user terminal to send reminding information according to the prompting signal.

The traffic monitoring system provided by the present invention can determine whether the user terminal receives the traffic sharing identifier according to the log generated during the data interaction, so that a corresponding response, such as prompting or triggering, can be performed. Thereby, the time for the user's operation can be saved, and the accuracy is high.

DRAWINGS

FIG. 1 is a system architecture diagram of a traffic monitoring system according to an embodiment of the present invention.

2 is a system architecture diagram of a traffic monitoring system according to another embodiment of the present invention.

detailed description

The technical solutions of the present invention are further described in detail below with reference to the accompanying drawings and specific embodiments. It is apparent that the described embodiments are only a part of the embodiments of the invention, and not all of them. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the scope of the present invention.

The technical solution of the present invention will be further described in detail below through the accompanying drawings and embodiments.

Referring to FIG. 1 , the present invention provides a traffic monitoring system 100 including at least a monitoring module 10 , a determining module 20 , and a prompting module 30 . In this embodiment, the traffic monitoring system 100 is configured to monitor whether the user terminal receives the electronic traffic.

Specifically, the monitoring module 10 is configured to periodically monitor a log generated when the user terminal performs data interaction. In this embodiment, each time the user terminal receives a traffic message, the user terminal acquires a picture file from the server, for example, a cover icon of the traffic, that is, when the user terminal and the server perform data interaction, The log is written according to the send/receive request, thereby being read by the listening module 10. In this embodiment, the traffic monitoring system 100 is applied to an open source proxy environment in order to enable the system to be commonly used in systems such as iOS and Android. Therefore, the monitoring module 10 includes the following configuration code:

Worker_processes_1;

Events{worker_connections 1024;}

Http{server{listen 9999;

Location/{proxy_pass http://$http_host$request_uri ;}}}, where the code is stored in the objs directory.

The determining module 20 is configured to determine whether a traffic sharing identifier exists in the log, and if yes, output a prompt signal. In this embodiment, the traffic sharing identifier is a picture identifier of the electronic traffic. The prompting module 30 is configured to control the user terminal to send reminding information according to the prompting signal. More specifically, in this embodiment, the event monitoring system includes the following code:

<? Php$lastline=””;

While(1)

{$line=‘tail-1/user/local/nginx/logs/access.log’;

If(($lastline!=$line)&&strops($line,"flow")!==false)

{$cmd=”say–v Bells\”dong\””;

System($cmd);

$cmd=”osascript-e’tell app\”system event;

$lastline=$line;}

Through the above code, the monitoring of the log is realized, and when there is traffic, an alarm can be sounded. It can be understood that the prompting module 30 can also provide the function of pop-up dialog box according to the needs of the user. In addition, the number of alarms and the like is not limited to one time, and the time of staying may be adjusted according to actual needs, which is 0.5 second in this embodiment.

Referring to FIG. 2, in another embodiment, the traffic monitoring system 100 further includes a positioning module 40 and a triggering module 50 to directly provide a corresponding operation signal when determining to generate a specific event.

Specifically, the positioning module 40 is configured to: when determining that the traffic sharing identifier exists in the log, locate the trigger signal to the corresponding interaction data interface. For example, when there is a traffic sharing identifier, a dialog box is located according to the identified path, and then a trigger signal is provided in the dialog box.

The triggering module 50 is configured to trigger a signal equivalent to clicking on the interactive interface according to the positioning module 40. In this embodiment, when the traffic dialog interface is located, the signal that the traffic is turned on is automatically triggered, that is, the signal corresponding to the user clicking the traffic. Thereby, the operation of receiving the flow rate can be automatically completed.

The traffic monitoring system 100 provided by the present invention can determine whether the user terminal receives the traffic sharing identifier according to the log generated during the data interaction, so that a corresponding response, such as prompting or triggering, can be performed. Thereby, the time for the user's operation can be saved, and the accuracy is high.

It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to be limiting, and the present invention will be described in detail with reference to the preferred embodiments. The technical solutions of the present invention may be modified or equivalently substituted, and the modified technical solutions may not deviate from the spirit and scope of the technical solutions of the present invention.

Claims (6)

A traffic monitoring system includes: a monitoring module, configured to periodically monitor a log generated when the user terminal performs data interaction; a judging module, configured to determine whether a traffic sharing identifier exists in the log, and if yes, outputting a prompt signal; The prompting module is configured to control the user terminal to send reminding information according to the prompting signal. The traffic monitoring system of claim 1 further comprising: The positioning module is configured to: when determining that the traffic sharing identifier exists in the log, locate the trigger signal to the corresponding interaction data interface; And a triggering module, configured to trigger a signal equivalent to clicking on the interactive interface according to the positioning module. The traffic monitoring system of claim 1 wherein said traffic monitoring system is applied to an open source proxy environment. The traffic monitoring system according to claim 1, wherein the monitoring module comprises the following configuration code: Worker_processes_1; Events{worker_connections 1024; Http{server{listen 9999; Location/{proxy_pass http://$http_host$request_uri ;}}}, where the code is stored in the objs directory. The traffic monitoring system of claim 1 wherein the event monitoring system comprises the following code: <? Php$lastline=””; While(1) {$line=‘tail-1/user/local/nginx/logs/access.log’; If(($lastline!=$line)&&strops($line,"flow")!==false) {$cmd=”say–v Bells\”dong\””; System($cmd); $cmd=”osascript-e’tell app\”system event; $lastline=$line;} The traffic monitoring system according to claim 1, wherein said traffic sharing identifier is Image identification of electronic traffic.

Images