US 2019/0156433 A1 · EVENT PROCESSING AND ALLOCATION

Abstract

Techniques for processing events in a network community are described herein. The disclosed techniques include receiving an event from a user account, the event comprising at least one reason for submitting the event and at least one attribute of content associated with the event; determining whether the event is to be crowd discussed based on at least in part on the at least one reason and the at least one attribute of content; and assigning the event in the crowd discussion list to a zone based at least in part on the at least one attribute of content associated with the event. The event may be a report from the user account. The disclosed techniques further include determining whether the report is to be crowd adjudicated based at least in part on a report weigh value corresponding to the user account and determining whether to allocate any report in the crowd adjudication list to a review account based on a plurality of predetermined rules.

Claims20

Dependent claims

A computer-implemented method of processing events, comprising:

receiving an event from a first user account, the event comprising information indicative of at least one reason for submitting the event and at least one attribute of content associated with the event;
determining whether the event is to be crowd discussed based on at least in part on the information indicative of at least one reason and the at least one attribute of content, wherein the determining whether the event is to be crowd discussed further comprises determining a crowd discussion value of the event by weighing the at least one reason and the at least one attribute of content;
in response to a determination that the event is to be crowd discussed, updating a crowd discussion list in an event pool and storing the event in the crowd discussion list;
and
in response to a determination that the event is not to be crowd discussed, updating a filter or block list in the event pool and storing the event in the crowd filter or block list.

2 more elements

A computing system of processing reports, comprising:

a processor;
and
a memory communicatively coupled to the processor to configure the processor at least to:
receive an event from a first user account, the event comprising information indicative of at least one reason for submitting the event and at least one attribute of content associated with the event;
determine whether the event is to be crowd discussed based on at least in part on the information indicative of at least one reason and the at least one attribute of content, wherein the determining whether the event is to be crowd discussed further comprises determining a crowd discussion value of the event by weighing the at least one reason and the at least one attribute of content;
in response to a determination that the event is to be crowd discussed, update a crowd discussion list in an event pool and store the event in the crowd discussion list;
and
in response to a determination that the event is not to be crowd discussed, update a filter or block list in the event pool and store the event in the crowd filter or block list.

5 more elements

A non-transitory computer-readable storage medium bearing computer-readable instructions that upon execution on a computing device cause the computing device at least to:

receive an event from a first user account, the event comprising information indicative of at least one reason for submitting the event and at least one attribute of content associated with the event;
determine whether the event is to be crowd discussed based on at least in part on the information indicative of at least one reason and the at least one attribute of content, wherein the determining whether the event is to be crowd discussed further comprises determining a crowd discussion value of the event by weighing the at least one reason and the at least one attribute of content;
in response to a determination that the event is to be crowd discussed, update a crowd discussion list in an event pool and store the event in the crowd discussion list;
and
in response to a determination that the event is not to be crowd discussed, update a filter or block list in the event pool and store the event in the crowd filter or block list.

2 more elements

Dependencies are inferred from the claim text.

Event processing and allocation

Life of this patent

Event processing and allocation

Life of this patent

Abstract

Claims20