Record Security Architecture for Ownership Transfer Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current computing systems face issues with record hijacking, where non-owner users can inadvertently or intentionally modify or cancel event records by asserting ownership privileges, leading to unauthorized changes and data loss.

Innovation Solution

A computing system record security architecture that includes a record generation component, a record security component, and a record ownership transfer component, which generates records with an owner property, controls modifications based on ownership, and facilitates secure ownership transfers, using unique identifiers and verification mechanisms to prevent unauthorized access and hijacking.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If non-owner users can modify records by asserting ownership privileges, then ease of operation is improved, but reliability deteriorates due to record hijacking and unauthorized changes

Engineering Contradiction:
Improverecord modification accessibilityVSAvoidrecord ownership security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces an intermediary verification mechanism that checks the owner property against the user's actual identity before allowing record modification. This mediator prevents direct unauthorized access while maintaining legitimate operational ease, resolving the contradiction between accessibility and security.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback by continuously verifying user ownership status before permitting record modifications. This feedback loop ensures that only authenticated owners can modify records, preventing hijacking while maintaining operational reliability for legitimate users.

Inventive Principle:
Principle #23Feedback

2Productivity

If ownership transfer is facilitated without verification, then productivity is improved, but reliability deteriorates due to unauthorized ownership claims

Engineering Contradiction:
Improveownership transfer efficiencyVSAvoidownership transfer security
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies preliminary action by requiring verification of the transferor's ownership status and the transferee's identity before completing the ownership transfer. This preliminary verification ensures security while maintaining transfer efficiency, preventing unauthorized ownership claims.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If record modification is allowed without owner verification, then ease of operation is improved, but loss of information increases due to unauthorized changes and data loss

Engineering Contradiction:
Improverecord modification convenienceVSAvoiddata loss from unauthorized changes
Core Design Contradiction:
Ease of operationVSLoss of substance

Solution Approach 1:

The verification mechanism acts as an intermediary that prevents unauthorized modifications before they can cause data loss. By checking ownership credentials, the system maintains operational convenience for legitimate users while blocking potential data loss from unauthorized changes.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP3341886B1Secure computing system record transfer control
Publication Date: 2020.07.22 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP3341886B1 patent drawingFigure 1
  • EP3341886B1 patent drawingFigure 2
  • EP3341886B1 patent drawingFigure 3

AI summary

A computing system record security architecture comprises, in one example, a record generation component configured to generate a record in a computing system, the record having an owner property that identifies a first user as an owner of the record, a record security component configured to control modification of the record based on the owner property of the record, and a record ownership transfer component configured to receive an indication of an ownership transfer of the record from the first user to a second user and to modify the owner property to identify the second user as the owner of the record.