# US 2016/0253368 A1 · Forum inspection based on correlation rating of response poster

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2016/0253368 A1
- Document ID: US20160253368A1
- Status: Published application
- Kind: A1
- Application number: 15/033,577
- Filed: 2013-11-05
- Published: 2016-09-01
- Earliest claimed: 2013-11-05
- Assignees: Hewlett Packard Interprise Development LP
- Applicants: Hewlett Packard Interprise Development LP
- Inventors: Vinay Deolalikar; Heman Laffitte
- Web page: https://patentgrep.com/patent/US20160253368A1

## CPC

- G06Q 10/107: Computer-aided management of electronic mailing [e-mailing]
- G06F 16/23: Updating
- G06F 16/285: {Clustering or classification}
- G06N 20/00: Machine learning
- G06Q 10/40: Business processes related to social networking or social networking services
- H04L 51/216: Handling conversation history, e.g. grouping of messages in sessions or threads
- 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
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

In one implementation, a poster engine may maintain a thread history associated with a response poster, a status engine may maintain a potential thread status of a thread of a forum based on the thread history, and a pool engine may maintain an inspection pool based on the potential thread status. In another implementation, a thread status of a thread of the forum may be maintained based on a correlation rating of a response poster and a pool having a number of threads based on the thread status may be provided.

## Claims

### Claim 1

A system for inspecting a forum comprising:
a poster engine to maintain a thread history associated with a response poster;
a status engine to maintain a potential thread status of a thread of the forum based on the thread history, the thread associated with the response poster; and
a pool engine to maintain an inspection pool based on the potential thread status, the inspection pool to contain the thread for review.

### Claim 2 (depends on 1)

The system of claim 1, wherein the pool engine is to at least one of:
add the thread to the inspection pool when the potential thread status is unknown; and
remove the thread from the inspection pool when the potential thread status is non-urgent.

### Claim 3 (depends on 1)

The system of claim 1, wherein the pool engine is to at least one of:
add the thread to a verification pool when the potential thread status is urgent; and
remove the thread from inspection pool when the thread receives a confirmed thread status.

### Claim 4 (depends on 1)

The system of claim 1, wherein the poster engine is to maintain a first frequency table associated with the response poster based on a first number of response posts made by the response poster and a second number of response posts made by the response poster confirmed to be urgent.

### Claim 5 (depends on 4)

The system of claim 4, comprising an accuracy engine to maintain a rating threshold to represent a level of correlation achievable based on the thread history and a status threshold to represent a level of status based on a correlation rating, the accuracy engine to:
modify at least one of the rating threshold and the status threshold based on a number of potentially urgent threads and a number of confirmed urgent threads; and
update the first frequency table when the thread is confirmed to be urgent.

### Claim 6

A machine readable storage medium comprising a set of instructions executable by a processor resource to:
maintain a correlation rating of a response poster based on a thread history associated with the response poster;
maintain a potential thread status of a thread of the forum based on the correlation rating, the thread to include a response post associated with the response poster; and
maintain an inspection pool based on the potential thread status, the inspection pool to contain the thread for review.

### Claim 7 (depends on 6)

The medium of claim 6, wherein the set of instructions is to at least one of:
add the thread to the inspection pool when the potential thread status is unknown; and
remove the thread from the inspection pool when the potential thread status is non-urgent.

### Claim 8 (depends on 6)

The medium of claim 6, wherein the set of instructions is to at least one of:
add the thread to a verification pool when the potential thread status is urgent; and
remove the thread from inspection pool when the thread receives a confirmed thread status.

### Claim 9 (depends on 6)

The medium of claim 6, wherein the set of instructions is to maintain a first frequency table associated with the response poster based on a first number of response posts made by the response poster and a second number of response posts made by the response poster confirmed to be urgent.

### Claim 10 (depends on 9)

The medium of claim 9, wherein the set of instructions is to:
maintain a rating threshold to represent a level of correlation achievable based on the confirmed thread status and the status threshold to represent a level of status based on the correlation rating;
modify at least one of the rating threshold and the status threshold based on a number of potentially urgent threads and a number of confirmed urgent threads; and
update the first frequency table when the thread is confirmed to be urgent.

### Claim 11

A method for inspecting a forum comprising:
obtaining a correlation rating of a response poster, the correlation rating to represent whether the response poster is associated with a first number of threads of the forum, the first number of threads having a first thread status to achieve a rating threshold;
maintaining a second thread status of a thread of the forum based on the correlation rating and a status threshold, the thread including a response post associated with the response poster and the second thread status to represent a potential status level of the thread; and
providing a pool having a second number of threads of the forum based on the second thread status.

### Claim 12 (depends on 11)

The method of claim 11, comprising:
grouping a plurality of threads of the forum into the pool for inspection, the plurality of threads having a confirmation status of unconfirmed and the thread being one of the plurality of threads;
maintaining the correlation rating to non-urgent based on the first thread status being non-urgent, the correlation rating associated with urgency;
maintaining the second thread status as non-urgent based on the correlation rating being non-urgent; and
removing the thread from the pool.

### Claim 13 (depends on 11)

The method of claim 11, comprising:
maintaining a frequency table associated with the response poster, the frequency table including:
a first column to represent a third number of threads responded to by the response poster; and
a second column to represent a fourth number of threads responded to by the response poster and having the first thread status confirmed to be urgent.

### Claim 14 (depends on 13)

The method of claim 13, comprising:
filling the frequency table with data based on a set of history data of the response poster, the set of history data associated with the first thread status of the first number of threads previously responded to by the response poster; and
changing at least one of the rating threshold and a status threshold, the status threshold to represent a number of response posters having the correlation rating to achieve the potential status level, the potential status level associated with a level of urgency.

### Claim 15 (depends on 13)

The method of claim 13, comprising filling the frequency table of the response poster based on a second frequency table of a second response poster, wherein the response poster has not previously responded in the forum and is associated with the second response poster.
