Object-Oriented Configuration Data for Contextual Application Overrides

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for modifying software application functionality based on context require manual updates to large configuration files, which is a time-consuming and error-prone process, and disseminating these updates across multiple applications within a server system is burdensome.

Innovation Solution

Implementing object-oriented configuration data modeling, allowing developers to specify configuration data as objects, overrides, and extensions, which can be used to modify application functionality centrally, reducing the need for manual code modifications across multiple applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual updates to large configuration files are used to modify application functionality, then the application can be customized for different contexts, but the process becomes time-consuming and error-prone

Engineering Contradiction:
Improveapplication functionality customizationVSAvoidtime to modify configuration
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent segments the monolithic configuration file into multiple smaller, organized configuration files grouped by functionality. Each configuration file contains specific settings and rules relevant to particular application features, making it easier to locate and modify only the necessary portions without affecting the entire configuration.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces configuration templates as intermediary elements between the configuration files and application functionality. These templates provide pre-defined structures and valid options that guide the configuration process, reducing errors and accelerating the customization process by eliminating the need to manually create configurations from scratch.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If large configuration files are used to define application rules, then application functionality can be modified, but the process requires significant user time and effort

Engineering Contradiction:
Improverule modification capabilityVSAvoidease of configuration updates
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent divides the configuration system into modular components including configuration files, templates, and validation rules. This segmentation allows users to work with smaller, more manageable units rather than navigating through large monolithic files, significantly improving ease of operation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements configuration templates that define valid parameters and their acceptable values. Users can modify application behavior by changing parameters within predefined templates rather than editing raw configuration data, making the process more intuitive and easier to operate.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If configuration files are updated, then application functionality changes, but disseminating updates to multiple applications is burdensome and time-consuming

Engineering Contradiction:
Improveconfiguration update speedVSAvoidtime to disseminate updates
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent creates configuration templates that serve multiple applications simultaneously. A single template can be applied across numerous applications, allowing updates to be made once and automatically propagated to all relevant applications. This multi-functional approach eliminates the need to manually update each application's configuration separately.

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

Solution Approach 2:

The patent implements a system where configuration templates are prepared in advance with all necessary structures and validation rules. This preliminary preparation allows rapid deployment and dissemination of updates across multiple applications without requiring time-consuming manual configuration for each application during the update process.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11593101B2Modification of application functionality using object-oriented configuration data
Publication Date: 2023.02.28 PAYPAL INC
  • US11593101B2 patent drawing
  • US11593101B2 patent drawing
  • US11593101B2 patent drawing

AI summary

Techniques are disclosed relating to modifying the functionality of software applications using object-oriented configuration data. In some embodiments, a configuration module may receive, from an application hosted within a server system, a request for configuration data that is usable to modify the manner in which the application performs a computing operation. In some embodiments, the request may specify a particular data object and include contextual information. The configuration may receive, from a configuration service in the server system, a configuration data package that includes a default definition for the particular data object and an override definition for a contextual override of the particular data object. The configuration module may determine, based on the contextual information, that the contextual override applies and return the configuration data, including data from the override definition, to the application.