Connectivity Service for Cross-Platform Application Communication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current connectivity services in computer systems face challenges in efficiently handling communication between network applications across different operating system platforms, leading to complex processes, high resource consumption, and limitations in providing secure services, especially for remote applications.

Innovation Solution

Implementing a method that associates application interfaces (APIs) between network applications to package and process messages across platforms, maintains session ownership, avoids orphaned sessions, and authenticates credentials securely, enabling seamless and secure communication between network applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If current connectivity services handle communication between network applications on different OS platforms, then communication capability is provided, but the process becomes complex and consumes significant computing resources

Engineering Contradiction:
Improvecommunication capability between different OS platformsVSAvoidcommunication process complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a connectivity service as an intermediary component that mediates between network applications on different operating systems. This mediator handles the complexity of cross-platform communication by providing a standardized interface, thereby enabling communication capability while managing the inherent complexity through a dedicated service layer rather than direct application-to-application integration.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The communication handling is segmented into distinct functional components: a connectivity service that manages communication protocols, a session manager that handles connection states, and application interfaces that provide standardized access points. This segmentation allows each component to specialize in specific tasks, reducing overall system complexity while maintaining versatile cross-platform communication capability.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If current connectivity services handle communication between network applications, then communication is enabled, but a significant amount of time and computing resources are consumed

Engineering Contradiction:
Improvecommunication capabilityVSAvoidcommunication processing time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The connectivity service performs preliminary actions by pre-establishing communication protocols, authentication mechanisms, and session states before actual data transmission occurs. This includes pre-configuring security parameters and validating communication paths in advance, which reduces the time required for subsequent communication operations and resource-intensive processing during data transfer.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The session manager implements self-service mechanisms to automatically manage connection states, retry failed transmissions, and handle protocol transitions without requiring extensive manual intervention or complex coordination between applications. This autonomous management reduces processing time and computing resources while maintaining reliable communication capability.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If current connectivity services are used, then communication between network applications is provided, but secure services and user authentication are not reliably available

Engineering Contradiction:
Improvecommunication capabilityVSAvoidsecurity and authentication availability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The connectivity service is designed with universal functionality that integrates multiple security and authentication mechanisms within a single framework. It provides standardized interfaces for various authentication methods (OAuth, SAML, Kerberos) and security protocols (TLS, SSL, IPsec), enabling reliable secure services across different OS platforms without requiring separate specialized solutions for each security requirement.

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

4Adaptability or versatility

If connectivity services handle cross-platform communication, then communication is enabled, but the system becomes less optimal for computer system consumers

Engineering Contradiction:
Improvecross-platform communication capabilityVSAvoiduser experience
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The connectivity service acts as a transparent intermediary that abstracts the complexity of cross-platform communication from the user perspective. Applications interact with a unified, standardized interface regardless of the underlying operating system, and the connectivity service handles all platform-specific details, protocol conversions, and security operations automatically, thereby improving ease of operation while maintaining versatile cross-platform communication capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9454413B1Systems and methods for handling communications between network applications
Publication Date: 2016.09.27 UNISYS CORP
  • US9454413B1 patent drawing
  • US9454413B1 patent drawing
  • US9454413B1 patent drawing

AI summary

Systems and methods for improving the handing of communications between network applications in a computer system with connectivity services interfaces that seamlessly handle the communications in an easy-to-use, secure, message-oriented environment are disclosed. Embodiments of systems and methods for maintaining ownership of sessions by applications, and for avoiding the orphaning of communication sessions when activities are terminated are also disclosed. Also disclosed are embodiments of systems and methods for accessing data using authentication credentials different than the authentication credentials associated with a user that is requesting access to the data. Embodiments of systems and methods for authenticating credentials for establishing a secure communication connection between applications executing on different platforms are also disclosed.