System, method and computer readable medium for determining an event generator type
Human interaction with a webpage may be determined by processing an event stream generated by the client device during the webpage interaction. A classification server receives the event stream and compares components of the event stream, including components of an event header message, with prerecorded datasets. The datasets include prerecorded event streams having a known interaction type. Training clients may be provided for generating the prerecorded datasets.
1. A method for determining an event generator type of an interaction between a client and a web server, the method comprising:
receiving an event stream generated by the client during the interaction of arbitrary unmodified web pages or web page application code between the client and the web server;
comparing at least a portion of a received event stream with a dataset comprising a plurality of prerecorded event streams having a known event generator type;
recording client data from an event header message of the event stream comprising an interaction ID uniquely identifying the interaction between the client and the web server and aids to identify a particular event stream of at least one of an operating system, browser type, client device type, and screen size; and
determining an event generator type of the received event stream from the comparison.
2. The method according to claim 1 comprising selecting at least one prerecorded event stream that substantially correlates to the received event stream and determining the event generator type of the received event stream to be the same as an event generator type of an at least one selected prerecorded event stream.
3. The method according to claim 1 comprising receiving an event stream header message generated by the client and comparing at least one component of the event stream header message with the prerecorded event streams.
4. The method according to claim 3 comprising:
receiving an event stream message comprising events generated by the client during the interaction between the client and the web server;
selecting a plurality of events from the event stream message;
forming an instance from the selected plurality of events and at least one component of the event header message; and
comparing the formed instance with a plurality of prerecorded instances in the dataset.
5. The method according to claim 4 wherein the at least one component of the event header message comprises at least one of a Uniform Resource Locator, a browser type and an operating system type.
6. The method according to claim 1 comprising generating the dataset using at least one training client.
7. The method according to claim 6 comprising:
receiving an training event stream from the at least one training client;
receiving an event generator type associated with the training event stream; and
storing at least a portion of the training event stream and the associated event generator type in the dataset.
8. The method of claim 7 wherein the training event stream comprises an event header message and at least one event stream message comprising a plurality of events generated by the at least one training client during the interaction between the training client and the web server, the method comprising:
selecting a plurality of events from the training event stream;
forming an instance from the selected plurality of events and at least one component of the event header message; and
storing the formed instance in the dataset.
9. The method of claim 8 wherein the at least one component of the event header message comprises at least one of a Uniform Resource Locator, a browser type and an operating system type.
10. The method of claim 9 comprising:
receiving a second training event stream from the at least one training client generated during a second interaction between the at least one training client and the web server;
forming a second instance from the second training event stream; and
storing the second instance in the dataset.
11. The method of claim 10 wherein the second event training stream comprises a second event header message indicating the Uniform Resource Locator and a different one of the browser type or the operating system type.
12. The method of claim 1 wherein the event generator type indicates whether the interaction is a human based interaction.
13. The method of claim 1 comprising continuously determining the event generator type of the interaction.
14. The method of claim 1 comprising determining the event generator type in response to a request from the web server.
15. A system for classifying an interaction type of an interaction between a client and a web server, the system comprising:
a classification server; and
a prerecorded dataset comprising a plurality of interactions of arbitrary unmodified web pages or web page application code, each interaction comprising an interaction type;
wherein the classification server is configured to receive an event stream in respect of the interaction and to classify the interaction using at least one component of the event stream and the prerecorded dataset and record client data from an event header message of the event stream comprising an interaction ID that uniquely identifies the interaction between the client and the web server and aids to identify a particular event stream of at least one of an operating system, browser type, client device type, and screen size.
16. The system of claim 15 comprising at least one training client configured to generate known interactions with the web server and to provide data in respect of the known interactions to the dataset, the data comprising an interaction type.
17. The system of claim 15 wherein the classification server is configured to receive a classification request from the web server and to provide a classification of the interaction to the web server in response to the request.
18. A non-transitory computer-readable medium comprising computer-executable instructions for execution by a first processor and a second processor in communication with the first processor, that, when executed:
cause the first processor to:
generate an interaction status request related to an interaction of arbitrary unmodified web pages or web page application code in respect of a client; and
provide the interaction status request to the second processor; and cause the second processor to:
determine the interaction status of the client from an event stream generated by the client;
record client data from an event header message of the event stream comprising an interaction ID that uniquely identifies the interaction in respect of the client and aids to identify the event stream of at least one of an operating system, browser type, client device type, and screen size; and
provide the interaction status to the first processor.
19. The non-transitory computer readable medium of claim 18 comprising instructions, that, when executed, cause the second processor to determine the interaction status of the client from an interaction buffer that stores event streams generated by the client.
20. The non-transitory computer readable medium of claim 18 comprising instructions, that, when executed, cause the second processor to compare at least a portion of the interaction in respect of the client with a dataset of prerecorded interactions having a known interaction type.