WS-Man Request Optimization via Statistical Tracking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The Common Information Model (CIM)-based Web Services-Management (WS-Man) protocol is verbose, leading to inefficient data collection and management in Information Handling Systems (IHS), particularly when compared to other protocols like SNMP or IPMI, necessitating optimization for faster and more efficient data transfer.

Innovation Solution

Implementing a system and method within an IHS to provide a management console that collects CIM statistics such as host identifier, remote agent version, CIM Object Manager version, data requested, time of request, network latency, and network bandwidth to calculate an optimum transfer rate, allowing for the adjustment of the maximum number of elements in WS-Man requests to prevent timeouts and optimize data collection, including the ability to split requests and preemptively back off from calculated maximums in case of errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the WS-Man protocol is used for CIM-based management communications, then standardization and interoperability are improved, but communication efficiency and data transfer speed deteriorate due to verbose payload

Engineering Contradiction:
Improveprotocol interoperabilityVSAvoiddata transfer efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent segments the data collection process into multiple batches, where each batch contains a controlled number of CIM elements. The management console divides the total requested elements into batches and sends them sequentially to remote agents, preventing timeout errors while maintaining efficient use of network resources.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent dynamically adjusts the maximum number of elements per request based on observed network conditions and timeout patterns. The system learns from previous request outcomes and adapts the batch size to optimize between sending enough data efficiently and avoiding timeout errors, creating a dynamic adaptation mechanism.

Inventive Principle:
Principle #15Dynamics

2Productivity

If the maximum number of elements in WS-Man requests is increased to reduce the number of requests, then request overhead is reduced, but timeout errors increase due to network latency and bandwidth constraints

Engineering Contradiction:
Improvenumber of requestsVSAvoidrequest success rate
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where the management console monitors the outcomes of data collection requests, including timeout errors and successful completions. This feedback is used to adjust the maximum number of elements in subsequent requests, creating a closed-loop system that optimizes request parameters based on actual network performance.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent uses a challenge cycle approach where it temporarily sends requests with more elements than the current maximum to test network capacity. If these excessive requests succeed, the system raises its maximum; if they timeout, it lowers the maximum. This partial/excessive action allows the system to probe and adapt to network capabilities.

Inventive Principle:
Principle #16Partial or excessive action

3Quantity of substance

If the maximum number of elements is set too high, then data collection completeness is improved, but timeout errors occur due to network bandwidth and latency limitations

Engineering Contradiction:
Improvedata collection completenessVSAvoidrequest timeout
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by sending test requests or challenge cycles before full data collection to probe network capacity and determine the appropriate maximum number of elements. This preliminary probing allows the system to set optimal parameters in advance, avoiding timeout errors during actual data collection while ensuring completeness.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If the maximum number of elements is set too low, then timeout errors are avoided, but the number of requests increases leading to reduced efficiency

Engineering Contradiction:
Improverequest success rateVSAvoiddata collection efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent makes the maximum number of elements dynamic rather than static, adjusting it based on observed network conditions, request outcomes, and challenge cycle results. This dynamic adjustment allows the system to maximize element counts when network conditions permit (improving efficiency) while maintaining reliability when conditions are poor.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9596158B2Common information model (CIM) object transfer via requestor statistical tracking
Publication Date: 2017.03.14 DELL PROD LP
  • US9596158B2 patent drawing
  • US9596158B2 patent drawing
  • US9596158B2 patent drawing

AI summary

Systems and methods for Common Information Model (CIM) object transfer via requestor statistical tracking. In an illustrative, non-limiting embodiment, a computer-implemented method may include providing, via an Information Handling System (IHS), a management console for a CIM environment, wherein the CIM environment includes a plurality of hosts accessible to the console via a network, and wherein each of the hosts has remote agent(s); creating a request to collect data from the remote agent(s), wherein the request follows a Web Services-Management (WS-Man) protocol, the request specifies a timeout and a maximum number of elements to be included in the remote agent(s)' responses, and the maximum number of elements is calculated to allow the remote agent(s) sufficient time to respond to the request prior to expiration of the timeout; and transmitting the request to the remote agent(s).