Web Service Platform On-Demand Message Handling Threads

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current web services lack the capability for schedule-based, background processing, which is essential for handling client messages efficiently and managing processing threads based on future workload, leading to suboptimal resource utilization and potential performance issues.

Innovation Solution

Implementing a web service platform with on-demand message handling threads that perform schedule-based processing and manage threads based on estimated future workload, using non-terminating processing threads to handle client messages as service-initiated on-demand tasks and suspend background processing when necessary to optimize resource allocation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If web services use traditional on-demand message handling threads, then processing speed is improved, but resource utilization deteriorates during low workload periods

Engineering Contradiction:

Improveprocessing speedVSAvoidresource utilization

Core Design Contradiction:

SpeedVSLoss of energy

Solution Approach 1:

The system dynamically adjusts the state of message handling threads based on workload conditions. Threads can be suspended during low workload periods to conserve resources and reactivated when needed, transforming the static thread model into a dynamic one that adapts to changing conditions.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system changes the operational parameters of message handling threads by introducing suspend and resume capabilities. This allows the threads to transition between active and suspended states, effectively changing their resource consumption parameters based on current workload demands.

Inventive Principle:

Principle #35Parameter changes

2Loss of energy

If web services suspend background processing to optimize resources, then resource utilization is improved, but processing reliability deteriorates

Engineering Contradiction:

Improveresource utilizationVSAvoidprocessing reliability

Core Design Contradiction:

Loss of energyVSReliability

Solution Approach 1:

The system implements feedback mechanisms that monitor workload conditions and thread states. This feedback enables the system to make informed decisions about suspending and resuming threads, ensuring that reliability is maintained by only suspending threads when appropriate and resuming them when needed.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system performs preliminary actions by suspending threads in advance during low workload periods while preserving their state. This allows the system to prepare for future workload increases by having threads ready to resume quickly, maintaining reliability while optimizing resource usage.

Inventive Principle:

Principle #10Preliminary action

3Duration of action of stationary object

If web services use non-terminating processing threads for background work, then processing continuity is improved, but system complexity deteriorates

Engineering Contradiction:

Improveprocessing continuityVSAvoidsystem complexity

Core Design Contradiction:

Duration of action of stationary objectVSDevice complexity

Solution Approach 1:

The system implements periodic suspension and resumption of background processing threads based on workload conditions. This periodic action pattern allows threads to remain non-terminating for continuity while introducing regular pauses to reduce complexity and resource consumption during low-demand periods.

Inventive Principle:

Principle #19Periodic action

4Adaptability or versatility

If web services handle all client messages as on-demand tasks, then processing flexibility is improved, but workload management capability deteriorates

Engineering Contradiction:

Improveprocessing flexibilityVSAvoidworkload management capability

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The system segments message handling into different categories: on-demand tasks that require immediate attention and background tasks that can be processed later. This segmentation allows the system to apply different management strategies to different types of messages, improving both flexibility and workload management capability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system creates a universal message handling framework that can accommodate both on-demand and background processing needs. The same thread infrastructure supports multiple processing modes, providing versatility while enabling sophisticated workload management through the ability to switch between processing types.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS8473957B2Architecture for providing on-demand and background processing

Publication Date: 2013.06.25 ZESTY AI INC

AI summary

Embodiments are directed to providing schedule-based processing using web service on-demand message handling threads and to managing processing threads based on estimated future workload. In an embodiment, a web service platform receives a message from a client that is specified for schedule-based, background handling. The web service platform includes an on-demand message handling service with processing threads that are configured to perform on-demand message processing. The web service platform loads the on-demand message handling service including the on-demand message handling threads. The web service platform implements the on-demand message handling service's threads to perform background processing on the received client message. The client messages specified for background handling are thus handled as service-initiated on-demand tasks.