Multi-Channel Embedded API for Cross-Platform Connectivity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems lack efficient and adaptive methods for increasing connectivity and productivity across multiple electronic communication channels, particularly in leveraging APIs for secure and seamless data access across diverse platforms and devices.

Innovation Solution

A multi-channel, embedded API that includes libraries of operating system communication protocols and user credentials for adaptive access, enabling secure communication initiation, authentication, and data retrieval across various channels, while supporting seamless transitions between devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a multi-channel API system is implemented to increase connectivity across multiple electronic communication channels, then connectivity and productivity are enhanced, but system complexity increases

Engineering Contradiction:
Improveconnectivity across multiple channelsVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal API architecture that can communicate across multiple electronic channels (messaging, social media, email, voice) through a single unified interface. The system includes multiple channel adapters that translate different communication protocols into a common internal format, allowing one API to serve multiple functions and channels without requiring separate integration for each channel type.

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

Solution Approach 2:

The patent employs a nested architecture where the core API engine is surrounded by channel-specific adapters, which in turn interface with various communication protocols. This layered nesting allows the system to maintain a simple core while accommodating complex multi-channel requirements through hierarchical organization of components.

Inventive Principle:
Principle #7Nested doll (Nesting)

2Productivity

If adaptive access is provided across multiple channels with authentication and data retrieval, then productivity and connectivity are improved, but processing time and operational overhead increase

Engineering Contradiction:
Improveapplication development productivityVSAvoidprocessing time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent implements preliminary authentication mechanisms where user credentials are verified and session tokens are established before actual data operations. The system pre-loads authentication contexts and maintains cached session information, so that subsequent data retrieval operations do not require repeated authentication processing, thereby reducing processing time for productive operations.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If secure authentication and data verification are implemented across multiple channels, then system security is enhanced, but ease of operation decreases

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

Solution Approach 1:

The patent implements self-service authentication where the system automatically manages credential verification, session management, and data validation without requiring manual intervention. The API handles authentication tokens, credential verification, and security protocols automatically, making the secure system transparent to users while maintaining high security standards through automated enforcement of authentication and authorization rules.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11947640B2Adaptive, multi-channel, embedded application programming interface (API)
Publication Date: 2024.04.02 BANK OF AMERICA CORP
  • US11947640B2 patent drawing
  • US11947640B2 patent drawing
  • US11947640B2 patent drawing

AI summary

A mobile device configured for communication with a multi-channel, operating-system (OS)-agnostic application programming interface (API) is provided. The API is configured to provide generic access to an OS-agnostic-device API output. The API may be coupled to a library of user credentials, and a library of data. The data provides information for one or more responses to a request from the user. The device may include an OS-based application and a translator. The translator translates communications between the OS-based application and said OS-agnostic API. The translator may convert an OS-compliant message header to a generic message header and to convert a generic message header to an OS-compliant message header. The OS-agnostic API may receive a communication initiation from the device. The device may be associated with a first channel. The API may request and receive 1) user credentials associated with the device and 2) data, authenticate the user credentials, and pull the data.