Reputation Reciprocity via Anonymous Identity Tokens

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing Internet reputation systems are limited by their inability to share reputation information across different platforms, lack verification mechanisms for real identities, and fail to incentivize maintaining a clean reputation due to easy pseudonym creation and lack of reciprocity in feedback mechanisms.

Innovation Solution

A method for providing reciprocal reputation services that allows reputation information to be shared anonymously across communities, using a Reputation Guarantee (RG) token that includes reputation information and policies, enabling entities to maintain anonymous identities while ensuring reputation reciprocity and accuracy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If localized feedback mechanisms are used to track reputation, then reputation information can be supplied and stored for transacting parties, but the system cannot share reputation information across different platforms and is tightly bound to system-specific identifiers

Engineering Contradiction:
Improvereputation trackingVSAvoidcross-platform compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent creates a universal reputation system where reputation information is stored in a standardized format that can be accessed across multiple platforms. The reputation server acts as a central hub that different systems can query, allowing the same reputation data to serve multiple communities and transaction types without being bound to a single platform's identifiers

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent introduces a reputation server as an intermediary component that mediates between different transaction systems. This server stores reputation information in a standardized format and provides it to various platforms through standardized interfaces, enabling cross-platform reputation sharing without requiring direct integration between platforms

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If pseudonyms are used to protect user anonymity, then user privacy is maintained, but there is no incentive to maintain a clean reputation since new pseudonyms can be easily created

Engineering Contradiction:
ImproveanonymityVSAvoidreputation maintenance incentive
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent requires users to establish their reputation before engaging in transactions by creating a pseudonym with verified identity information stored in the reputation database. This preliminary establishment of reputation creates a foundation that users must maintain, as their future transaction capabilities depend on the reputation accumulated under their pseudonym

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements a feedback mechanism where transaction outcomes are recorded and associated with pseudonyms in the reputation database. This feedback loop creates accountability, as users receive reputation consequences for their actions, incentivizing them to maintain clean reputations despite using anonymous identifiers

Inventive Principle:
Principle #23Feedback

3Reliability

If reputation information is shared across communities, then trust is enhanced and good behavior is incentivized, but user anonymity within communities may be compromised

Engineering Contradiction:
ImprovetrustVSAvoidanonymity protection
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent segments identity information from reputation information. Users are assigned pseudonyms that serve as their community identifiers, while their real identity information is stored separately in the reputation database. This segmentation allows reputation to be shared across communities through pseudonyms without exposing actual user identities, maintaining anonymity while enabling trust

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The reputation server acts as an intermediary that facilitates anonymous reputation sharing. It stores and manages the mapping between pseudonyms and identity information, allowing communities to verify reputations through pseudonyms without direct access to users' real identities, thus protecting anonymity while enabling trust

Inventive Principle:
Principle #24Intermediary (Mediator)

4Measurement precision

If verification mechanisms for real identities are implemented, then reputation accuracy is improved, but system complexity increases

Engineering Contradiction:
Improvereputation verificationVSAvoidverification mechanism
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent performs identity verification in advance during pseudonym creation, before the user engages in any transactions. This preliminary verification ensures that each pseudonym is associated with a verified real identity, improving reputation accuracy without requiring complex verification processes during each transaction

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8793773B2System and method for providing reputation reciprocity with anonymous identities
Publication Date: 2014.07.29 APPLE INC
  • US8793773B2 patent drawing
  • US8793773B2 patent drawing
  • US8793773B2 patent drawing

AI summary

System and method for providing reciprocity in a reputation system are described. In one embodiment, the method comprises: responsive to receipt by a first entity of a Reputation Guarantee (“RG”) request from a second entity, creating a token in accordance with specifications set forth in the RG request and forwarding the token to the second entity, wherein the token may include reputation information developed using reputation forming information (“RFI”) of the second entity and policies concerning treatment of the RFI of the second entity; forwarding the token to a third entity by at least one of the first and second entities; responsive to the token received by the third entity not including the reputation information of the second entity: forwarding from the third entity to the first entity the token and an assertion request; and responsive to receipt of the token and the assertion request, forwarding by the first entity to the third entity an assertion including the reputation information in accordance with the policies concerning treatment of the RFI of the second entity.