Metadata-Driven Software Localization via User Contribution Matching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software solutions struggle to efficiently customize products for global markets due to varying regional regulations and user requirements, making it difficult for providers to compete with locally focused products.

Innovation Solution

A Market Acceleration Platform (MAP) that performs market requirements analysis across related markets, uses metadata-driven configuration, and leverages user contributions to create scalable, configurable software solutions, enabling decentralized localization and parallelized market entry.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a product is customized to support a wide range of regional requirements and user types, then the product can compete globally, but the customization process becomes time-consuming

Engineering Contradiction:
Improveproduct adaptability to regional requirementsVSAvoidcustomization time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-configuring the software platform with metadata schemas, configuration templates, and localization frameworks before market entry. This allows the system to rapidly adapt to regional requirements without time-consuming customization during deployment

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent utilizes parameter changes by implementing a metadata-driven configuration system where regional and user-specific requirements are managed through configurable parameters and metadata attributes. This enables dynamic adaptation to different markets by modifying configuration parameters rather than rewriting code

Inventive Principle:
Principle #35Parameter changes

2Reliability

If customization is performed for each market individually, then local requirements are met, but the process is not scalable to global markets

Engineering Contradiction:
Improvecompliance with local requirementsVSAvoidmarket entry scalability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements universality by creating a single configurable software platform that serves multiple markets simultaneously. The system uses universal metadata schemas and configuration templates that can be adapted to any regional requirement, eliminating the need for separate customization processes for each market

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

Solution Approach 2:

The patent applies segmentation by dividing the configuration process into independent metadata elements and configuration components. This allows the system to handle different regional requirements through modular configuration rather than monolithic customization, enabling parallel market entry

Inventive Principle:
Principle #1Segmentation

3Ease of manufacture

If a monolithic, everything-in-code implementation approach is used, then the product is simple to implement, but it becomes inflexible and non-extensible for global markets

Engineering Contradiction:
Improveimplementation simplicityVSAvoidproduct flexibility
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamics by transitioning from static code-based configuration to dynamic metadata-driven configuration. The system allows configuration parameters and metadata to be modified at runtime without code changes, providing both implementation simplicity and ongoing flexibility for global market adaptation

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP3759661B1Matching adopting users and contributing users for decentralized software localization
Publication Date: 2025.08.20 INTUIT INC
  • EP3759661B1 patent drawingFigure 1A
  • EP3759661B1 patent drawingFigure 1B
  • EP3759661B1 patent drawingFigure 2A

AI summary

A method to configure a software solution may include receiving a first specification of a type of configuration data items and a second specification of system selected user attributes associated with the type of configuration data items, and receiving a configuration data item that is used to configure a first localized version of the software solution. The method may further include receiving a contributing user attribute specification that specifies a first user attribute and a second user attribute of the system selected user attributes, and generating a search tag assigned to the configuration data item. The method may further include receiving a search request to search the configuration data items, selecting, in response to the search request, the configuration data item based on the search tag, and configuring, in response to selecting the configuration data item, a second localized version of the software solution based on the configuration data item.