Transaction Services Hub VPN Session Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current transaction services face challenges in providing secure, efficient, and scalable network solutions for short-duration transactions across various networks, particularly in credit/debit card authorizations and other inquiry-response applications, which require low bandwidth and quick call setups.

Innovation Solution

The implementation of a transaction services hub that establishes virtual private network (VPN) sessions between merchant devices and host devices, enabling secure data communication and report retrieval through a public network connection, while managing traffic and providing redundancy for load balancing and failover services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a transaction services hub establishes VPN sessions between merchant devices and host devices, then security of data communication is improved, but device complexity increases

Engineering Contradiction:
Improvesecurity of data communicationVSAvoidcomplexity of transaction services hub
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The transaction services hub acts as an intermediary component between merchant devices and host devices, establishing VPN sessions to secure communications. This mediator approach allows the hub to manage security protocols and encryption without requiring complex security implementations at each endpoint device.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If the transaction services hub manages traffic and provides redundancy for load balancing, then productivity of transaction processing is improved, but device complexity increases

Engineering Contradiction:
Improvetransaction processing throughputVSAvoidcomplexity of transaction services hub
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The transaction services hub performs multiple functions including VPN session management, traffic management, load balancing, and failover services. By consolidating these diverse functions into a single multi-functional hub, the system achieves high productivity without proportionally increasing overall system complexity.

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

Solution Approach 2:

The hub combines traffic management, load balancing, and redundancy management into unified processes. Multiple merchant devices are merged into a single pool of resources that the hub manages collectively, improving throughput while avoiding the complexity of individual device management.

Inventive Principle:
Principle #5Merging (Combining)

3Adaptability or versatility

If the system supports multiple merchants with short sessions and low bandwidth requirements, then adaptability of the network solution is improved, but device complexity increases

Engineering Contradiction:
Improveability to support multiple merchantsVSAvoidcomplexity of network configuration
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The transaction services hub provides a universal platform that can serve multiple merchants with different requirements through standardized VPN sessions. The hub adapts to various merchant needs without requiring custom configurations at each device, maintaining simplicity while achieving versatility.

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

Data Source

PatentUS9892383B2Transactional services platform
Publication Date: 2018.02.13 VERIZON PATENT & LICENSING INC
  • US9892383B2 patent drawing
  • US9892383B2 patent drawing
  • US9892383B2 patent drawing

AI summary

One or more devices within a transaction services hub receive, via an internal distribution network interface, configuration settings for a network connection between merchant devices and a host device and establish, based on the configuration settings, a virtual private network (VPN) session between the one or more devices within the transaction services hub and the host device. The one or more devices receive, from a first merchant device, a first transaction authorization request originating via a voice network and receive, from second merchant transaction device, a second transaction authorization request originating via an Internet Protocol network. The one or more devices route, via the VPN session, the first and the second transaction authorization requests to the host device, collect data regarding the first and the second transaction authorization requests, and provide, via a public network connection, an interface to retrieve reports based on the collected data.