Frontend Page Generation via Metadata Mapping and Unified Modules

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing frontend page generation solutions require separate design, content management, and feed generation systems that lack communication and necessitate manual resource-intensive intervention, leading to inefficiencies and high costs, especially when UI components change frequently.

Innovation Solution

A system that integrates design, content management, and feed generation modules via a metadata bus, enabling users to make changes with minimal coding by annotating UI components, mapping design element attributes to database object attributes, and using a metadata bus for centralized communication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If separate design, content management, and feed generation systems are used, then each system can be developed and maintained independently, but manual intervention and resource consumption increase significantly

Engineering Contradiction:

ImproveIndependent system developmentVSAvoidManual intervention efficiency

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent merges design system, content management system, and feed generation system into a unified platform where components communicate through a standardized metadata bus. This integration eliminates manual intervention between systems while preserving independent development capabilities through modular architecture.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The metadata bus serves as an intermediary communication layer between design, content management, and feed generation modules. It enables automated data exchange and coordination without requiring manual intervention, resolving the contradiction between system independence and operational efficiency.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Device complexity

If manual intervention is required for system collaboration, then system complexity can be managed through clear interfaces, but time and resource consumption increase

Engineering Contradiction:

ImproveSystem interface clarityVSAvoidManual collaboration time

Core Design Contradiction:

Device complexityVSLoss of time

Solution Approach 1:

The system enables self-service automation where the metadata bus automatically coordinates between design, content management, and feed generation modules. Components automatically discover and communicate with each other through published metadata, eliminating manual collaboration time while maintaining clear interfaces.

Inventive Principle:

Principle #25Self-service

3Adaptability or versatility

If UI components change frequently, then system adaptability improves, but manual updates across multiple systems become more time-consuming

Engineering Contradiction:

ImproveUI component flexibilityVSAvoidUpdate time across systems

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The metadata bus implements real-time feedback mechanisms where changes to UI components are automatically propagated through the system. When design elements are updated, the system automatically detects and communicates these changes to content management and feed generation modules, enabling rapid adaptation without manual updates.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system establishes preliminary metadata schemas and communication protocols in advance, allowing UI components to be designed and updated independently. The standardized metadata bus is pre-configured to automatically handle changes, so no manual coordination is needed when UI components evolve frequently.

Inventive Principle:

Principle #10Preliminary action

4Ease of manufacture

If three separate systems are used for design, content management, and feed generation, then each system can be optimized for its specific function, but integration requires significant manual effort

Engineering Contradiction:

ImproveSystem-specific optimizationVSAvoidIntegration efficiency

Core Design Contradiction:

Ease of manufactureVSProductivity

Solution Approach 1:

The system maintains segmentation into distinct design, content management, and feed generation modules, each optimized for its specific function. However, these segments are connected through the metadata bus which enables automated integration, resolving the contradiction between functional optimization and integration efficiency.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS12536244B2System, method, and computer program for providing an end-to-end solution for frontend page generation

Publication Date: 2026.01.27 RAKUTEN GROUP INC

AI summary

The present invention provides an end-to-end solution for frontend page generation. The system includes a design module that enables a user to design UI components, an annotation submodule that enables a user to annotate the UI components with design element attributes, a database that stores database objects having database object attributes according to a data schema, a mapper module that enables a user to map design element attributes of the UI components to database object attributes without coding via a graphical user interface, a content management module that enables a user to add mapped UI components to a frontend page feed and to associate the mapped UI components with instances of the database objects, a feed generation module that retrieves instance-specific values for the database object attributes of mapped UI components in frontend page feeds, and a metadata bus that enables the modules and database to communicate.