Ledger-Based Contract Validation Server for Fairness

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for individual contracts between business operators and users, such as electric power companies and car sharing services, lack mechanisms to ensure fairness, allowing for potential collusion that results in preferential contract terms for some users at the expense of others.

Innovation Solution

A control method executed by a server that involves receiving contract information, identifying a second user from a ledger, transmitting this information, obtaining confirmation and digital signatures from the second user, and validating the contract only when consent is given, ensuring fairness by storing validated contracts in a ledger.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If individual contracts are entered between business operators and users, then contract flexibility and user-specific terms are improved, but fairness and reliability of contract terms deteriorate due to potential collusion

Engineering Contradiction:
Improvecontract flexibilityVSAvoidfairness of contract terms
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a server as an intermediary that manages and stores contract information in a ledger. This server acts as a neutral mediator that receives contract information from both the business operator and users, ensuring transparency and preventing collusion by making contract terms visible to all parties through the ledger system.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements a feedback mechanism where contract information is stored in a ledger that is accessible to all users. This creates a feedback loop where users can view and compare contract terms, providing social oversight that discourages unfair contract practices and ensures reliability of contract terms.

Inventive Principle:
Principle #23Feedback

2Reliability

If contract information is made visible to all users, then transparency and fairness are improved, but user privacy and information security worsen due to increased exposure

Engineering Contradiction:
Improvetransparency of contractsVSAvoidinformation security risk
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent creates a digital copy of contract information stored in a ledger on the server. Instead of sharing sensitive original information directly between users, the system stores standardized contract terms in the ledger that can be viewed by all users without exposing personal or sensitive data, thus maintaining transparency while protecting information security.

Inventive Principle:
Principle #26Copying

3Reliability

If a server manages contract information centrally, then contract validation and fairness assurance are improved, but system complexity and operational overhead worsen

Engineering Contradiction:
Improvecontract validationVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent designs the server to perform multiple functions: storing contract information in the ledger, validating contract terms, managing user interactions, and providing transparency. This multi-functional approach consolidates complexity into a single universal system rather than requiring separate mechanisms for each function, making the overall system more manageable despite the increased reliability requirements.

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

Data Source

PatentUS11973882B2Control method, server, and recording medium
Publication Date: 2024.04.30 PANASONIC INTELLECTUAL PROPERTY CORP OF AMERICA
  • US11973882B2 patent drawing
  • US11973882B2 patent drawing
  • US11973882B2 patent drawing

AI summary

A control method includes: receiving first information pertaining to a first contract from a first terminal used by a first user who is one of two parties who have agreed to the first contract; when consent of a party aside from the two parties is required to validate the first contract, identifying a second user as the party aside from the two parties with reference to a ledger storing information pertaining to a past contract, and transmitting the first information to a second terminal operated by the second user; obtaining second information in which a confirmation result indicating whether the second user consents to the first contract and a digital signature of the second user are added to the first information; and confirming the second information, and when the confirmation result indicates consent, setting the first contract as a valid contract and storing the second information in the ledger.