Carrier Aggregator System for Pre-populating Transaction Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing transaction processes on client devices, such as mobile phones, are cumbersome due to the need for manual entry of information like payment details, which can be tedious and error-prone.

Innovation Solution

An aggregator system that identifies a client device and retrieves Customer Relationship Management (CRM) information from a carrier system, allowing it to pre-populate data fields during transactions, thereby reducing the need for manual input.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual entry of transaction information is required on client devices, then data accuracy can be verified, but transaction time and user effort increase significantly

Engineering Contradiction:
Improvedata accuracyVSAvoidtransaction time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by storing customer information (name, address, payment details) in the carrier system's CRM database before the transaction occurs. When a transaction is initiated, this pre-stored information is automatically retrieved and populated into the transaction form, eliminating the need for manual entry while ensuring data accuracy through verified CRM sources.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The carrier system acts as an intermediary between the customer and the merchant system. It receives authentication credentials from the client device, retrieves the corresponding CRM information, and provides the populated transaction data back to the merchant system. This intermediary role enables automatic information retrieval while maintaining security and data verification.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If manual entry of transaction information is required, then system security can be maintained through controlled data input, but ease of operation deteriorates

Engineering Contradiction:
Improvesystem securityVSAvoidease of transaction
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The carrier system serves as a secure intermediary that handles sensitive customer information. The client device sends only authentication credentials (device ID, carrier ID) to the carrier system, which then retrieves and returns the populated transaction information. This intermediary architecture maintains security by keeping sensitive CRM data in the controlled carrier environment while enabling easy operation through automatic information population.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system enables self-service by allowing the carrier system to automatically retrieve and populate customer information without requiring manual input from the user. The authenticated client device receives pre-filled transaction forms with accurate CRM data, making the transaction process convenient while security is maintained through the carrier's controlled data access.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If comprehensive customer information is collected and stored, then transaction convenience improves through pre-population, but information security risks increase

Engineering Contradiction:
Improvetransaction convenienceVSAvoidinformation security risks
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The carrier system acts as a secure intermediary that stores comprehensive CRM information in a controlled environment. Instead of storing sensitive data in the merchant system or client device, the carrier system maintains the information and provides selective access during transactions. This intermediary approach enables transaction convenience through pre-populated forms while mitigating security risks by keeping data in a trusted, centralized location with controlled access protocols.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Productivity

If automatic information retrieval is implemented, then productivity increases by reducing manual entry, but device complexity increases due to additional system components

Engineering Contradiction:
Improvetransaction throughputVSAvoidsystem architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The carrier system performs multiple functions: it stores comprehensive CRM information, authenticates client devices, retrieves appropriate customer data, and provides populated transaction information to merchant systems. By consolidating these functions in a single multi-functional carrier system rather than distributing complexity across multiple specialized components, the solution increases transaction productivity while minimizing overall system complexity.

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

Data Source

PatentUS10154082B2Providing customer information obtained from a carrier system to a client device
Publication Date: 2018.12.11 BOKU IDENTITY INC
  • US10154082B2 patent drawing
  • US10154082B2 patent drawing
  • US10154082B2 patent drawing

AI summary

Methods and systems are presented for accessing customer relationship management (CRM) information stored in a carrier system associated with a user of an identified client device. A client device is identified based on client device identification information received from a carrier system. CRM information associated with the identified client device is received from the carrier system, and data corresponding to at least a subset of the CRM information is output to the client device. The client device may be configured to pre-populate data fields of a transaction based on the data corresponding to at least a subset of the CRM information.