Secure Messaging System with Asynchronous Batch Processing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing secure messaging systems face challenges in providing uninterrupted and secure user experiences due to latency issues and lack of modular subsystem isolation, especially when dealing with data-intensive operations across multiple user accounts.

Innovation Solution

A secure messaging system with a data retention and predictive analytics subsystem in secure isolation, utilizing a web services layer for goal-based planning, an application server layer for asynchronous processing, and multiple security tokens to ensure secure access and reduce latency through asynchronous batch processing and granular data updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If data-intensive operations are performed across multiple user accounts, then processing capability is improved, but latency increases

Engineering Contradiction:
Improveprocessing capabilityVSAvoidlatency
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system divides data processing into separate batches organized by user account. Each batch contains operations for a specific user, allowing independent processing and reducing the impact of data-intensive operations on overall system response time. This segmentation enables parallel processing across multiple users while maintaining low latency for each individual user's operations.

Inventive Principle:
Principle #1Segmentation

2Speed

If security tokens are cached on web browsers, then user access speed is improved, but security vulnerability increases

Engineering Contradiction:
Improveuser access speedVSAvoidsecurity vulnerability
Core Design Contradiction:
SpeedVSObject-affected harmful factors

Solution Approach 1:

The security architecture is segmented into multiple independent security tokens: browser-based tokens for user authentication and server-based tokens for API authentication. This segmentation isolates security responsibilities, allowing the browser to cache user authentication tokens for speed while maintaining separate, more secure server-based tokens that are not vulnerable to browser-based security issues.

Inventive Principle:
Principle #1Segmentation

3Reliability

If modular subsystem isolation is implemented, then security is improved, but system complexity increases

Engineering Contradiction:
ImprovesecurityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The web services layer is designed as a universal interface that handles multiple functions: user authentication, API authentication, data retrieval, and batch processing. This multi-functional design provides modular subsystem isolation for security while avoiding the complexity of separate dedicated components for each function, as the web services layer unifies these operations into a single accessible interface.

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

Data Source

PatentUS11095623B2Secure messaging systems and methods
Publication Date: 2021.08.17 BRIGHTPLAN LLC
  • US11095623B2 patent drawing
  • US11095623B2 patent drawing
  • US11095623B2 patent drawing

AI summary

Systems and methods for secure messaging and automation are disclosed herein. An example method includes providing, by an application server layer, a user-facing application that accesses a data retention system and a predictive analytics system through a web services layer, the user-facing application being secured through use of a security token cached on a web browser that provides the user-facing application, establishing a security protocol or security token utilized between the application server layer and the web services layer that is different from the security token cached on the web browser; and performing asynchronous processing based on user interaction with a goal-based planning application that processes data from a plurality of user accounts.