Peer to Patent, Community Patent Review

APPLICATION LIST|ARCHIVED APPLICATIONS|US PATENT CLASSIFICATIONS

Home > Archived Applications > 20070282832 > Discussion

Pre-Grant Publication Number: 20070282832

Automatic tracking of user data and reputation checking

Collaborate on the process of community review for this application. Posting will not be forwarded to the USPTO. Flagging a post as an ACTION ITEM signals further research. Flagging SPAM and ABUSE helps to manage discussion. Placing double brackets around a reference to a claim or prior art will create a hyperlink to the original ex. [[claim 1]] and [[prior art 2]].

Please review the Community Code of Conduct prior to posting

Discussion (8)

View: Date|Claims|Prior Art|Action Item|

Facilitator's Comment

Action Item

Show without Noise

Chad Zhong (8 months ago)

Hello all, I have just submitted two potential prior arts thats associated with the current patent application. I will try to submit more within the next couple of weeks so that everyone can get an opportunity to take a look at them, give comments, and annotate them. If you can please review the prior art submitted in this applicaiton and give me your annotations and feedbacks that would be excellent. If you know someone else that are interested to join this peer review process, by all means, ask them to join. Again, if you have any questions or comments or concerns, please let me know. Thank you.

Chad Zhong (9 months ago)

Hello, my name is Chad Zhong, I am the new moderator for this discussion group. If any of you have any questions about the technology as well as USPTO procedural matters regarding this patent application that would be greatly appreciated. Also, as you may know, in order to ensure the success of the P2P project, we are trying to get as much input as possible from our colleagues. If you know someone who is interested in participating in the project, by all means, inputs and prior art submissions are greatly appreciated.

Karen Hofmann (9 months ago)

Illustration #5 Utility: Algorithm to identify potentially fraudulent transactions may need to be more robust since there may be many patterns that thieves use:

Pattern 1: The billing address will match the shipping address.

Pattern 2: The billing address and shipping address will be different, so that the unauthorized person billing the purchase can receive the shipment at 1 or many locations (possible that there would be no repeat Ship-Tos).

Pattern 3: The billing address will almost be the shipping address, and each entry of addresses may have allowable abbreviations such at St., ST, and Street, which may foil simple exact match or partial match algorithms.

etc.

I would suggest checking with Verisign PayFlowPro and other secure payment toolkits to verify how much variance they allow in data before verifying a credit transaction. It may vary based on credit authorization tool.

Chad Zhong (9 months ago)

Paypal's PayFlowPro appears to be letting users (buyers/sellers) register first with Paypal, and then Paypal does its own verification with the end user (buyers/sellers) to verify thate they are safe through thourgh background checks and bank account checks. The current application appears to track user information as he/she browses the web and before the user clicks "send" the sensitive information such as credit card, the system automatically checks the reputation of the seller. If the reputation for the seller is bad, it may discourage the buyer from buying in the first place. This is similar to the feedback system in Ebay/Paypal, only this is automatic and apparently applicable to any merchant in any website.

Karen Hofmann (9 months ago)

Illustration #5 Uniqueness: String checking for personal data is not unique.

AOL has a very similar feature that can be turned on using the AOL portal that when personal data is sent via web, back-end process, or e-mail to any site external to the PC, that the user is notified to where the data is being sent and which data is being sent.

The user can configure within the AOL administration screens, which credit card and other personal data to verify recipient before sending. The check is done only on the user's client, before submitting data to the server.

To make ensure uniqueness, you may want to emphasize a server-side component.

Chad Zhong (9 months ago)

Hello Karen, could you please submit the AOL reference throught the upload system or provide me with a link to it? I don't use AOL myself, this could be interesting. Thank you.

Abhijit Telang (10 months ago)

The concept of keystroke monitoring is not novel atall and there have been a number of patents/research papers about monitoring user actions. For instance,

US20070033166A1-System and method of searching for information based on prior user actions talks about tracking and maintaining a chronological list of user actions including the websites visited, transactions performed, even clicking on menu options and so on..

In the same context there is also a paper published by Microsoft in around 2002,titled " Desktop history tool : Time based interaction summaries to restore context"

Again, the complex algorithmic processing requirements to decipher the data such as credit cards, social security number, debit card number is not furnished. deciphering needs would be particularly challenging in multi user environments.

Chad Zhong (9 months ago)

This reference is a good background reference to get started on. But it does not cover all aspect of the present invention. Specifically, itis lacking the particular extrapolation of data from the string and forumlating the data into a substring. This application does discuss the keeping track of the user event such as the keyboard stroke.

0 days left