Object Property Setter for Client Server Data Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current web-based software applications face inefficiencies in managing data transmission between clients and servers, as they often require proactive user actions and do not effectively validate user inputs, leading to unnecessary data communication and potential errors.

Innovation Solution

The implementation of an object property setter within a visual development environment that identifies business objects on a server and client, allowing for automatic validation and processing of updated properties according to business rules, ensuring only valid data is transmitted and minimizing client-side processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the server processes all data changes and sends complete responses, then data integrity is maintained, but data transmission efficiency deteriorates due to unnecessary data communication

Engineering Contradiction:
Improvedata integrityVSAvoiddata transmission efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent extracts only the changed properties from the complete business object and transmits them separately to the server. Instead of sending the entire object with all its properties, the system identifies and transmits only the delta (changed fields), reducing data transmission volume while maintaining integrity through selective processing on the server side.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The server processes the changed properties according to business rules and returns feedback information to the client. This feedback mechanism allows the client to update only the necessary properties in the business object, creating an efficient feedback loop that maintains data integrity while minimizing transmission overhead.

Inventive Principle:
Principle #23Feedback

2Speed

If the client validates data locally, then validation speed improves, but data consistency with server business rules deteriorates

Engineering Contradiction:
Improvevalidation speedVSAvoiddata consistency
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The client performs preliminary validation of data against basic constraints before transmission to the server. This preliminary action filters out obviously invalid data early in the process, improving validation speed by catching errors before they reach the server, while the server maintains final authority on business rule compliance.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary validation layer where the client validates data against local constraints and the server validates against business rules. This intermediary approach distributes validation responsibilities, allowing fast local validation while maintaining server-enforced consistency through the business rule processing layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If the system processes all property changes, then data completeness is maintained, but processing time increases due to unnecessary computations

Engineering Contradiction:
Improvedata completenessVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system extracts and processes only the changed properties rather than reprocessing the entire business object. The server identifies which properties were modified and applies business rule processing only to those specific properties, significantly reducing processing time while maintaining completeness through targeted updates.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements partial processing by handling only the necessary properties that changed, rather than processing all properties even if they remained unchanged. This partial action approach optimizes processing time by avoiding unnecessary computations on unchanged data while ensuring completeness through selective processing of modified fields.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS8402060B2Software for managing data between a client and server
Publication Date: 2013.03.19 SAP SE
  • US8402060B2 patent drawing
  • US8402060B2 patent drawing
  • US8402060B2 patent drawing

AI summary

Various techniques and components are provided for managing data between a client and server. In one example embodiment, software is operable to receive an updated business object property at a server, process the updated property with a business object residing on the server, and communicate an updated business object from the server to the client. In certain implementations, this allows for the server to update a complete business object, including properties requiring recalculation based on the updated business object property, through a targeted communication from the client, namely, the single updated business object property. Additionally, the software may provide for the identification and automatic updated of server-side business objects or business object properties related to the received updated business object property.