Push Communications Control Manager for Secure Multi-Client Messaging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing push communications systems face issues with complexity, scalability, security, limited support for voice and video data, high overhead in data transmission, and lack of a trust model, leading to vulnerabilities and inefficiencies in message delivery across networks.

Innovation Solution

A Control Manager system comprising trusted modules for encryption, authentication, and secure connection management, which enables secure, scalable, and efficient message transmission between local and remote client modules, including voice, video, text, and data communications, with features like message receipt verification and fail-over mechanisms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple clients subscribe to the same source in existing push communications systems, then the system can serve multiple users, but the server must iteratively push information to each client increasing system complexity and overhead

Engineering Contradiction:
Improvemulti-client supportVSAvoidserver complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a subscription manager as an intermediary component that handles client subscriptions and message distribution. This mediator manages the subscription state and coordinates push operations to multiple clients, reducing the complexity burden on the server by centralizing subscription management logic in a dedicated module.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the push communications functionality into distinct modules: a subscription manager for handling subscriptions, a message source for generating content, and push generators for distribution. This segmentation allows each component to operate independently and simplifies the overall system architecture by dividing complex tasks into manageable units.

Inventive Principle:
Principle #1Segmentation

2Device complexity

If existing push communications systems provide limited security measures, then the system remains simple, but vulnerabilities such as forged messages and falsified data can occur

Engineering Contradiction:
Improvesecurity architectureVSAvoidmessage authenticity
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where the subscription manager receives acknowledgment signals from clients confirming successful message receipt. This feedback loop ensures reliable delivery and allows the system to track which clients have received which messages, enhancing both security and reliability without significantly increasing complexity.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary authentication and authorization actions before allowing message transmission. The subscription manager verifies client identities and validates subscription permissions in advance, preventing forged messages and unauthorized access before they can compromise system reliability.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If push communications systems use basic textual data only, then the system remains simple, but voice and video information delivery is not supported

Engineering Contradiction:
Improvedata type supportVSAvoidclient software complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal push communications system where the same core infrastructure handles multiple data types including text, voice, video, and binary data. The subscription manager and push generators are designed to accommodate various message formats through a common interface, enabling multi-functional operation without requiring separate specialized systems for each data type.

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

Solution Approach 2:

The system adapts to different data types by changing transmission parameters such as message encoding, data formatting, and protocol configuration. Rather than modifying the fundamental architecture, the system adjusts parameters like data encoding schemes and message structure to accommodate voice, video, and other non-textual data types through the existing framework.

Inventive Principle:
Principle #35Parameter changes

4Productivity

If large amounts of textual data are transmitted in segments, then data can be delivered efficiently, but large overhead is required to properly rebuild the message

Engineering Contradiction:
Improvedata delivery efficiencyVSAvoidtransmission overhead
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The patent extracts and removes unnecessary overhead components from the message transmission process. By implementing a streamlined push mechanism that sends data in efficient segments without redundant acknowledgment protocols and minimizes header information, the system reduces the overhead required for message reconstruction while maintaining delivery efficiency.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of using traditional pull-based systems where clients request data and receive full messages, the patent inverts the approach by pushing segmented data directly to clients who have pre-established subscriptions. This inversion eliminates the need for complex request-response cycles and reduces overhead by sending only the necessary data segments directly to interested parties.

Inventive Principle:
Principle #13The other way round (Inversion)

5Adaptability or versatility

If no trust model exists between network peers, then the system remains open and simple, but scalability and network availability are limited

Engineering Contradiction:
Improvenetwork scalabilityVSAvoidtrust management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The subscription manager acts as a trusted intermediary that mediates between network peers and manages trust relationships. It maintains a database of authorized clients and subscriptions, verifying identities and validating permissions before allowing communications. This intermediary approach enables scalable operation with multiple trusted parties without requiring direct trust establishment between each peer pair.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary trust verification and authorization actions before allowing any message transmission between network peers. The subscription manager pre-validates client identities and subscription permissions, establishing trust relationships in advance. This preliminary action enables scalable network operation by pre-establishing trust frameworks that simplify subsequent communications without requiring complex real-time trust negotiations.

Inventive Principle:
Principle #10Preliminary action

6Adaptability or versatility

If data leaves the private network to enter the public Internet, then network connectivity expands, but routing control is lost and must follow paths deemed appropriate by traversed sub-networks

Engineering Contradiction:
Improvenetwork connectivityVSAvoidrouting control
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The subscription manager serves as a gateway intermediary that manages the transition of data between private and public networks. It handles routing decisions and protocol conversions at the boundary, maintaining control over message routing while enabling connectivity to external networks. The intermediary coordinates communication with external sub-networks, ensuring that routing requirements are met even when data must traverse public Internet infrastructure.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8453229B2Push type communications system
Publication Date: 2013.05.28 SCHWESINGER EDMUND JR
  • US8453229B2 patent drawing
  • US8453229B2 patent drawing
  • US8453229B2 patent drawing

AI summary

Systems and methods for pushing messages, arbitrated by a Control Manager, to local and remote client computer modules in a networked architecture. The messages may include voice, video, text and data communications. The system provides a Control Manager, which comprises the Event Manager, the Authentication Manager, and the Secure Connection Maintainer. The Event Manager, a trusted module, passes messages between local and remote modules using established, and possibly secure, connections, and provides message receipt verification and reply/return message capabilities to the event-triggering module. Messages may be also encrypted. The Authentication Manager, also a trusted module, provides authentication and authorization services. The Authentication Manager is responsible for handling client identification, authorization, and authentication across a secured communications channel. The Secure Connection Maintainer monitors the connections between the Control Manager and its trusted modules and the remote modules.