Secure User Address Management via Segmented Tables and Firewall

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Service providers face user dissatisfaction and data security breaches when user information, stored in a single table, is compromised, leading to the need for effective user information management and security measures.

Innovation Solution

Implementing a system that separates user information into multiple tables with varying security levels, where personal identifiable information (PII) is stored in a secure zone (User Authentication Zone) and non-PII is kept in a less stringent zone, with a firewall controlling access to prevent direct user access to PII, and using an address management service to manage and validate user addresses.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If user information is stored in a single table for ease of access, then ease of operation is improved, but security and reliability deteriorate because all user information is compromised when the table is breached

Engineering Contradiction:
Improveease of access to user informationVSAvoidsecurity of user information
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent divides user information storage into multiple separate tables (user profile table, address table, payment information table, etc.) instead of a single table. Each table stores specific types of information and can be accessed with appropriate security controls. This segmentation ensures that if one table is compromised, other user information remains protected.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies different security levels to different tables based on the sensitivity of the information they contain. Critical information like payment details and addresses are stored in separate tables with stricter access controls, while less sensitive profile information can be accessed more freely. This local differentiation of security quality optimizes both accessibility and protection.

Inventive Principle:
Principle #3Local quality

2Reliability

If user information is separated into multiple tables with different security levels, then security and reliability are improved, but device complexity increases due to multiple tables and access control mechanisms

Engineering Contradiction:
Improvesecurity of user informationVSAvoidcomplexity of data storage structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a user information management service that provides universal access to multiple separate tables through a single interface. This service handles authentication, authorization, and data retrieval across all tables, making the complex multi-table structure transparent to applications. The service acts as a universal gateway that simplifies access despite the underlying complexity.

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

Solution Approach 2:

The user information management service acts as an intermediary between applications and the distributed user information tables. It manages the complexity of accessing multiple tables with different security requirements by providing a unified access mechanism. The service handles authentication, validates requests, and retrieves data from appropriate tables, shielding applications from the complexity of the segmented storage structure.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If PII is stored in a secure zone with firewall control, then security is improved, but ease of operation deteriorates due to restricted direct access

Engineering Contradiction:
Improveprotection of PIIVSAvoiddirect access to user information
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The user information management service acts as an intermediary that mediates access to PII stored in the secure authentication zone. Applications cannot directly access PII tables; instead, they submit requests through the management service, which handles authentication, validates the request context, and retrieves data only when appropriate. This intermediary mechanism maintains security while enabling legitimate access operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements self-service authentication and authorization mechanisms where the user information management service automatically verifies credentials and determines access permissions without requiring manual security checks. The service autonomously manages the balance between security and accessibility by evaluating each request against stored authentication data and access policies.

Inventive Principle:
Principle #25Self-service

4Quantity of substance

If user information is kept in a single table, then storage efficiency is improved, but loss of information increases when breaches occur as all data is compromised

Engineering Contradiction:
Improvestorage efficiencyVSAvoiddata breach impact
Core Design Contradiction:
Quantity of substanceVSLoss of information

Solution Approach 1:

The patent segments user information into multiple specialized tables (profile information, addresses, payment details, etc.), each storing only specific types of data. This segmentation reduces the impact of data breaches because compromising one table exposes only a subset of user information rather than all data. The segmented structure inherently limits information loss potential while maintaining efficient storage for each data type.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11615201B2Secure management of user addresses in network service using firewall and tables
Publication Date: 2023.03.28 EBAY INC
  • US11615201B2 patent drawing
  • US11615201B2 patent drawing
  • US11615201B2 patent drawing

AI summary

Methods, systems, and programs are presented for securing user-address information. A first memory is configured according to a first table that does not include information about user identifiers. Each entry in the first table includes a physical location identifier and information about a physical location. A second memory is configured according to a second table, where each entry in the second table includes the physical location identifier and an account identifier of a user for accessing a service. The first and second tables are configured to separate profile information from the address information of the user. Additionally, a firewall is configured to control access to the second memory. The firewall defines an authentication zone including the second memory but not the first memory, where access to the second memory by internal services is allowed and direct access by the user to the second memory is denied.