Stateless Object Property Management for WAN Latency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing PDM systems face performance and resource challenges in global WAN deployments due to high latency and bandwidth demands, particularly in browser-based clients with hundreds of object properties, where current object property management approaches are either bloated or stateful, failing to adapt dynamically to client needs.

Innovation Solution

A client-driven, adaptive object property policy management system that allows for stateless optimization of property handling, where the client system registers, updates, and manages its property requirements through a policy manager module, ensuring only necessary properties are requested from the server, optimizing bandwidth and computation costs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all object properties are transmitted to the client in global WAN deployments, then the client has access to complete data, but bandwidth consumption and latency increase significantly

Engineering Contradiction:
Improvedata completenessVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts only the necessary object properties required by the client from the complete set of server properties. The client specifies which properties it needs, and the server transmits only those selected properties, eliminating unnecessary data transmission and reducing bandwidth consumption while maintaining data completeness for required fields.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the object properties into two categories: those required by the client and those not required. This segmentation allows the system to transmit only the relevant subset of properties over the WAN connection, reducing overall data transmission volume and latency while ensuring the client receives complete information for its specific needs.

Inventive Principle:
Principle #1Segmentation

2Productivity

If stateful property management is used to track client property requirements, then property handling can be optimized, but system complexity and server resource demands increase

Engineering Contradiction:
Improveproperty handling efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements self-service property management where the client autonomously specifies its own property requirements through policy definitions. The client sends requests with explicit property requirements, and the server processes these requests without needing to maintain stateful tracking of client needs. This approach maintains property handling efficiency while reducing system complexity by eliminating the need for stateful management infrastructure.

Inventive Principle:
Principle #25Self-service

3Loss of energy

If minimal object properties are transmitted to reduce bandwidth usage, then bandwidth consumption decreases, but the client may lack necessary data for complete functionality

Engineering Contradiction:
Improvebandwidth consumptionVSAvoiddata completeness
Core Design Contradiction:
Loss of energyVSReliability

Solution Approach 1:

The patent implements dynamic property selection where the client can adaptively specify which properties it needs based on its current operational context and requirements. The property requirements are not fixed but can be dynamically adjusted, allowing the system to transmit the precise amount of data needed for complete client functionality while minimizing bandwidth consumption by excluding unnecessary properties.

Inventive Principle:
Principle #15Dynamics

4Productivity

If the system maintains stateful information about client property needs, then subsequent requests can be optimized, but the system becomes vulnerable to server reassignment issues

Engineering Contradiction:
Improverequest optimizationVSAvoidserver reassignment resilience
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies preliminary action by having the client explicitly specify its property requirements in advance with each service request. Rather than relying on stateful information that may be lost during server reassignment, the client includes its property policy requirements in each request, ensuring that the server can always fulfill the client's needs regardless of which server instance handles the request. This approach maintains request optimization while providing resilience to server reassignment.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10091064B2Systems and methods for stateless management of object properties
Publication Date: 2018.10.02 SIEMENS INDUSTRY SOFTWARE INC
  • US10091064B2 patent drawing
  • US10091064B2 patent drawing
  • US10091064B2 patent drawing

AI summary

Methods for stateless management of object properties and corresponding systems and computer-readable mediums. A method includes executing a presenter module that manages interactions with a user via a view module, and identifying a required object property for the presenter module. The method includes registering the required object property, by the presenter module, in a policy manager module as a property policy. The method includes building a request for a service based on the property policy, sending the request to the service, and receiving a response to the request from the service.