Transaction-Level QoS Monitoring via Adaptive Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for managing Quality of Service (QoS) in electronic service environments lack focused measurement and control capabilities, particularly in service-based systems hosting multiple services, leading to suboptimal performance and reliability.

Innovation Solution

A measurement engine and adaptive controller system that acquires transaction data, compares it to predefined QoS standards, and dynamically adjusts operational parameters to ensure compliance with service level agreements, prioritizing transaction types and load distribution among application servers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If existing QoS management systems are used, then general service level monitoring is provided, but focused transaction-level measurement and control is insufficient

Engineering Contradiction:
Improvetransaction-level measurement precisionVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system segments QoS measurement at the transaction level by introducing a measurement engine that captures individual transaction instances rather than aggregate service metrics. This allows precise measurement of specific transaction types (e.g., login, search, checkout) while maintaining manageable system architecture through modular transaction type definitions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A measurement engine is introduced as an intermediary component between the service layer and QoS management layer. This mediator collects transaction data from various services, processes it according to predefined transaction type definitions, and provides focused measurement results without requiring complex changes to the underlying services.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple services are hosted in a service-based system, then service versatility is improved, but QoS compliance control becomes difficult

Engineering Contradiction:
Improveservice versatilityVSAvoidQoS compliance control
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system defines transaction types in a universal manner that applies across multiple services. A single transaction type definition (e.g., 'search') can be used to monitor the same operation across different services (e-service A, e-service B), enabling consistent QoS control without requiring service-specific monitoring logic.

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

Solution Approach 2:

The system changes the monitoring parameters from service-level aggregates to transaction-level metrics. By focusing on transaction types and instances rather than service implementations, the system maintains ease of operation across versatile service environments while achieving precise QoS compliance control.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If real-time QoS monitoring is implemented, then service reliability is improved, but processing overhead increases

Engineering Contradiction:
Improveservice reliabilityVSAvoidprocessing overhead
Core Design Contradiction:
ReliabilityVSPower

Solution Approach 1:

The system performs preliminary actions by pre-defining transaction types and their associated QoS parameters before actual monitoring occurs. This allows the measurement engine to process transactions efficiently using predefined schemas rather than dynamically analyzing each transaction, reducing processing overhead while maintaining real-time monitoring capability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The measurement engine operates autonomously by self-managing the collection, processing, and analysis of transaction data according to predefined transaction type definitions. This self-service approach eliminates the need for complex external intervention and reduces overall system processing overhead while ensuring continuous reliability monitoring.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS7349340B2System and method of monitoring e-service Quality of Service at a transaction level
Publication Date: 2008.03.25 HEWLETT PACKARD ENTERPRISE DEV LP
  • US7349340B2 patent drawing
  • US7349340B2 patent drawing
  • US7349340B2 patent drawing

AI summary

Quality of Service (QoS) management in a service-based system may be provided by adaptively adjusting system operational parameters in response to real time relationships between QoS specifications and measurements. A QoS manager may include a measurement engine configured to acquire real time data that is specific to transaction instances of various transaction types. The manager also may include a controller for comparing transaction data from the measurement engine to the guaranteed QoS standards. Depending upon the results of the comparison, the controller may invoke control actions.