Customer Profile Code Encoding via Segmentation Rules

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems face challenges in securely and efficiently communicating customer data due to its susceptibility to security breaches and resource-intensive requirements, as they rely on uncoded data and substantial bandwidth and memory usage.

Innovation Solution

A system comprising a rules engine that transforms customer data into code segments using rules, combining them to form a customer profile code, which is then communicated securely through a decision engine and interface engine, reducing resource usage and enhancing data security by encoding the data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If uncoded customer data is communicated in conventional systems, then data accessibility and processing are straightforward, but security breaches become susceptible and resource consumption increases

Engineering Contradiction:
Improvedata securityVSAvoiddata encoding system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments customer data into multiple code segments based on different rules (e.g., demographic data, transaction data, behavioral data), then combines these segments into a unified customer profile code. This segmentation allows for targeted encoding strategies that balance security requirements with system complexity management.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The customer profile code serves as an intermediary representation between the raw uncoded data and external systems. It encodes customer information in a secured format that can be communicated to third parties without exposing the full raw data, thus mediating between data accessibility and security requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If uncoded customer data is used, then data processing is simple, but bandwidth and memory resources are substantially consumed

Engineering Contradiction:
Improveresource efficiencyVSAvoiddata accessibility
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The patent transforms customer data from its original uncoded format into an encoded customer profile code format. This parameter change in data representation reduces the amount of data that needs to be stored and transmitted, thereby improving resource efficiency while maintaining data accessibility through the encoded profile.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The system extracts only the essential customer information needed for profiling and encoding it into the customer profile code. This extraction process removes unnecessary data details while retaining the core customer identity and characteristic information, reducing resource consumption without losing critical data accessibility.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If customer data is encoded into customer profile codes, then security is enhanced and resource usage is reduced, but the encoding and decoding process adds system complexity

Engineering Contradiction:
Improvedata securityVSAvoidencoding system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The customer profile code serves multiple functions simultaneously: it encodes customer data for security, compresses data to reduce resource usage, and provides a standardized interface for data exchange with third parties. This multi-functionality justifies the added system complexity by delivering multiple benefits through a single encoding mechanism.

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

Solution Approach 2:

The system performs preliminary encoding of customer data into profile codes before any external communication or processing occurs. This preliminary action secures the data in advance and prepares it for efficient transmission, reducing the complexity of handling unencoded data in subsequent operations.

Inventive Principle:
Principle #10Preliminary action

4Productivity

If centralized customer data consolidation is implemented, then resource consumption is reduced, but data processing time may increase

Engineering Contradiction:
Improveresource efficiencyVSAvoiddata processing time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary encoding of customer data into compact profile codes during data collection and storage phases. This preliminary action consolidates and secures data in advance, reducing the need for resource-intensive processing during subsequent operations and minimizing overall processing time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent merges multiple customer data attributes and historical records into a single integrated customer profile code. This merging process consolidates scattered data into a unified representation, reducing the total data volume that needs to be processed and improving resource efficiency while managing processing time through optimized consolidation algorithms.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS9443251B2System for encoding customer data
Publication Date: 2016.09.13 BANK OF AMERICA CORP
  • US9443251B2 patent drawing
  • US9443251B2 patent drawing
  • US9443251B2 patent drawing

AI summary

A system for authenticating a customer includes a network interface and a processor. The network interface communicates a request for customer data associated with a particular customer. It also receives a customer profile code associated with the customer, wherein the customer profile code comprises a first code segment and a second code segment. It further receives first and second rules associated with the customer profile code. The processor transforms the first and second code segments into customer data using the rules. It further authenticates the customer using the customer data.