Application Server for Mobile Commerce Transaction Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile electronic commerce faces challenges in integrating product catalogs, pricing, payment acceptance, and authentication, particularly for merchants, due to technical and financial barriers, and concerns over security and fraud, which deter them from adopting this emerging transaction channel.

Innovation Solution

An electronic platform with a user interface for setting parameters, a conversation tracking engine to monitor and manage messages, and a mobile content rendering engine to dynamically render content based on user requests, facilitating secure and efficient mobile commerce transactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If merchants integrate product catalogs, pricing, payment acceptance and authentication for m-commerce, then transaction capability is improved, but device complexity and integration difficulty increase

Engineering Contradiction:
Improvetransaction capabilityVSAvoidintegration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an application server as an intermediary component that mediates between mobile devices and merchants. The server handles conversation tracking, message routing, and coordination of transaction flows, allowing merchants to accept m-commerce transactions without directly implementing complex integration logic for catalog management, payment processing, and authentication.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the m-commerce functionality into distinct modular components: mobile device client, application server with conversation tracking engine, message routing engine, and merchant server. Each component has specialized responsibilities, allowing independent development, deployment, and maintenance while working together to provide complete transaction capability.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If traditional payment integration methods are used for m-commerce, then payment acceptance is enabled, but technical barriers and financial costs increase

Engineering Contradiction:
Improvepayment acceptance capabilityVSAvoidimplementation ease
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The application server provides universal payment acceptance capabilities that work across multiple mobile devices and merchants through standardized interfaces. The conversation tracking engine and message routing engine handle diverse transaction types and communication protocols uniformly, allowing merchants to accept payments without developing custom integration solutions for each payment method or device type.

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

3Productivity

If cardholder information is collected for transactions, then payment processing is enabled, but security risks and fraud concerns increase

Engineering Contradiction:
Improvetransaction processingVSAvoidsecurity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent extracts sensitive cardholder information handling from the merchant system and concentrates it in the secure application server environment. The server collects, validates, and processes payment information through encrypted communication channels, then transmits only essential transaction data to merchants, reducing the exposure of sensitive information across the distributed system and minimizing security risks.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS11270361B2Application server and/or method for supporting mobile electronic commerce
Publication Date: 2022.03.08 CARDINALCOMMERCE CORP
  • US11270361B2 patent drawing

AI summary

An electronic platform (10) for facilitating mobile commerce transactions includes: a user interface (20) that is provided to a user (60), the user interface (20) being operable to retrieve from the user (60) a plurality of settings for different parameters that regulate a manner in which the platform (10) operates for a given entity that is being served by the platform (10); a conversation tracking engine (40) that monitors messages exchanged between the platform (10) and mobile device users (72) accessing the platform (10), the conversation tracking engine (40) being operative to recognize which ones of selected monitored messages together form a common conversation and keep track of a current state of that conversation; and, a mobile content rendering engine (30) that is operable to dynamically render mobile content in response to the platform (10) receiving a request from a mobile device (74) for mobile content, the mobile content being rendered in accordance with the parameter settings entered via the user interface (20).