Processing high volume network data
First Claim
1. A system comprising:
- at least one processor and executable instructions accessible on a computer-readable medium that, when executed, cause the at least one processor to perform operations comprising;
receiving data, via a subscription interface and from a client device, indicative of a subscription request for sessionized data, the request data including a quantity of time defining a period of inactivity in which a session identifier is not received and signifying an end of a session;
allocating a sessionizer bank responsive to receiving the subscription request, the sessionizer bank comprising processing engines;
provisioning a first plurality of identifiers to each of the respective processing engines;
registering, with a collection server, the allocated sessionizer bank as available to process event messages matching the subscription request; and
receiving event messages from a transmitting device linked by the collection server at a selected one of the processing engines of the sessionizer bank, the selected one of the processing engines configured to process the received event messages in accordance with session rule data linked to the subscription request and the quantity of time defining the period of inactivity to generate the sessionized data, the subscription interface being further configured to provide the generated sessionized data to the client device.
1 Assignment
0 Petitions
Accused Products
Abstract
Disclosed are a system comprising a computer-readable storage medium storing at least one program, and a computer-implemented method for event messaging over a network. A subscription interface receives data indicative of a subscription request for sessionized data. An allocation module allocates a sessionizer bank linked to the subscription request. A messaging interface module provisions identifiers linked to the respective processing engines of the sessionizer bank. The messaging interface module registers the allocated sessionizer bank as available to process event messages matching the subscription request by providing the provisioned identifiers. The messaging interface module receives event messages from a producer device linked by a collection server to a selected one of the processing engines of the sessionizer bank. The selected one of the processing engine processes the received event messages in accordance with session rule data linked to the subscription request to generate sessionized data.
51 Citations
20 Claims
-
1. A system comprising:
-
at least one processor and executable instructions accessible on a computer-readable medium that, when executed, cause the at least one processor to perform operations comprising; receiving data, via a subscription interface and from a client device, indicative of a subscription request for sessionized data, the request data including a quantity of time defining a period of inactivity in which a session identifier is not received and signifying an end of a session; allocating a sessionizer bank responsive to receiving the subscription request, the sessionizer bank comprising processing engines; provisioning a first plurality of identifiers to each of the respective processing engines; registering, with a collection server, the allocated sessionizer bank as available to process event messages matching the subscription request; and receiving event messages from a transmitting device linked by the collection server at a selected one of the processing engines of the sessionizer bank, the selected one of the processing engines configured to process the received event messages in accordance with session rule data linked to the subscription request and the quantity of time defining the period of inactivity to generate the sessionized data, the subscription interface being further configured to provide the generated sessionized data to the client device. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. A method comprising:
-
receiving request data, from a client device, indicative of a subscription request for sessionized data, the request data including a quantity of time defining a period of inactivity in which a session identifier is not received and signifying an end of a session; allocating a sessionizer bank responsive to receiving the subscription request, the sessionizer bank comprising processing engines; provisioning a first plurality of identifiers to each of the respective processing engines; registering, with a collection server, the allocated sessionizer bank as available to process event messages matching the subscription request; receiving event messages from a transmitting device linked by the collection server to a selected one of the processing engines of the sessionizer bank; processing, using one or more computer processors, the received event messages in accordance with session rule data linked to the subscription request and the quantity of time defining the period of inactivity to generate the sessionized data; and providing the generated sessionized data to the client device. - View Dependent Claims (12, 13, 14, 15)
-
-
16. A non-transitory machine-readable storage medium having no transitory signals and embodying instructions that, when executed by a machine, cause the machine to perform operations comprising:
-
receiving request data, from a client device, indicative of a subscription request for sessionized data, the request data including a quantity of time defining a period of inactivity in which a session identifier is not received and signifying an end of a session; allocating a sessionizer bank responsive to receiving the subscription request, the sessionizer bank comprising processing engines; provisioning a first plurality of identifiers to each of the respective processing engines; registering, with a collection server, the allocated sessionizer bank as available to process event messages matching the subscription request; receiving event messages from a transmitting device linked by the collection server to a selected one of the processing engines of the sessionizer bank; processing the received event messages in accordance with session rule data linked to the subscription request and the quantity of time defining the period of inactivity to generate the sessionized data; and providing the generated sessionized data to the client device. - View Dependent Claims (17, 18, 19, 20)
-
Specification