Multi-Party Interchange Management via SDK Hierarchy

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current connected ecosystems, especially those involving client computers and the Internet of Things, face challenges in managing and securing multi-party interchanges, including client integrity verification, downloadable code management, SDK selection, server-initiated connections, controlled access to rich data, and privacy, which are inadequately addressed by existing technologies.

Innovation Solution

A system utilizing a hierarchy of SDK managers to catalog and manage entities, software capabilities, and data exchange processes, ensuring secure and controlled interactions between client application owners, third-party services, and client computers, employing Application Network Access Control (ANAC), well-defined operational primitives, and privacy regulations to facilitate secure data access and collection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If unmanaged ad hoc multi-party interchanges are used (as in prior browser-based systems), then ease of operation is improved, but security and reliability deteriorate

Engineering Contradiction:
Improveease of operationVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces an intermediary management system that sits between client applications and third-party services. This intermediary validates client integrity, manages downloadable code, controls SDK selection, and regulates data access. By inserting this mediating layer, the system maintains ease of multi-party interaction while establishing security controls that prevent the chaos and risks of unmanaged interchanges.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If mobile operating systems digitally sign apps and create permissions, then security is improved, but adaptability to multi-party interchanges deteriorates

Engineering Contradiction:
ImprovesecurityVSAvoidadaptability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic permission management that adapts to multi-party interchange requirements. Instead of static app-signed permissions, the system dynamically evaluates client integrity, adjusts SDK selections based on interchange needs, and regulates data access in real-time. This dynamic approach maintains security while enabling the adaptability needed for complex multi-party services involving multiple clients and third parties.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If browser downloads code dynamically to client computer, then adaptability is improved, but reliability deteriorates due to unmanaged and risky results

Engineering Contradiction:
ImproveadaptabilityVSAvoidreliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent applies preliminary action by validating client integrity before allowing any code downloads or executions. The management system pre-establishes trust relationships, pre-approves SDK selections, and pre-configures permission structures. This preliminary validation ensures that subsequent dynamic code downloads and multi-party interchanges occur within a trusted framework, maintaining both adaptability and reliability.

Inventive Principle:
Principle #10Preliminary action

4Adaptability or versatility

If additional IoT devices are deployed to extend the ecosystem, then versatility is improved, but device complexity and management difficulty increase

Engineering Contradiction:
ImproveversatilityVSAvoidcomplexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal management framework that handles multiple device types (mobile devices, PCs, IoT devices) through a single integrated system. The intermediary management layer provides uniform integrity verification, code management, and permission control across all device categories. This universal approach enables the ecosystem to expand to diverse IoT devices without proportionally increasing management complexity, as the same management principles apply across all device types.

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

Data Source

PatentUS11461498B2Systems and methods for secured, managed, multi-party interchanges with a software application operating on a client device
Publication Date: 2022.10.04 MSIGNIA
  • US11461498B2 patent drawing
  • US11461498B2 patent drawing
  • US11461498B2 patent drawing

AI summary

A system and methods which manage and secure the interaction between (1) the owner of a client application and third-parties, and (2) between the third-parties and the client application while the client application is operating on a user's client computer. The invention enables interactive primitives such as ensuring the integrity of the client environment, reading data from the client, writing data to the client, collecting data from the user, and ensuring privacy. All functionality is done through the client application and under management and control of the owner of the client application.