Personalized Page Composition via Central Component Repository

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data management platforms struggle with inefficiencies in creating personalized pages due to the need to access and combine components and microservices from multiple domains, leading to complexity and security concerns.

Innovation Solution

A central repository system that catalogs and registers components and microservices, allowing a locator to efficiently access, combine, and deploy personalized pages using a single source of information, ensuring consistency and security through a single origin.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If components and microservices are accessed from multiple domains to create personalized pages, then the system can provide diverse and customized content, but the complexity and security concerns increase

Engineering Contradiction:
Improvepersonalization capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a central repository as an intermediary system that mediates between multiple domains and the page composition process. The repository registers and stores components and microservices from various domains, providing a unified access point that simplifies the complexity of accessing resources from multiple sources while maintaining the diversity needed for personalization.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments components and microservices into registered entities within the central repository, allowing them to be independently managed and then composed into personalized pages. This segmentation enables the system to handle complexity by organizing resources into discrete, manageable units that can be selectively combined.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If components and microservices are accessed from multiple domains, then more resources are available for page creation, but security concerns increase

Engineering Contradiction:
Improveresource availabilityVSAvoidsecurity risks
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The central repository acts as a security intermediary that controls access to components and microservices from multiple domains. By registering all resources in a centralized location, the system can authenticate and authorize access uniformly, reducing security risks associated with direct access to multiple domain sources.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If a central repository system is used to catalog and register components, then deployment time is reduced and security is enhanced, but the system requires initial registration and mapping operations

Engineering Contradiction:
Improvedeployment speedVSAvoidregistration system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system performs preliminary registration and mapping of components and microservices in the central repository before they are needed for page creation. This preliminary action establishes the registry data structure and mappings in advance, allowing rapid deployment without repeating the registration process for each new page.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250370805A1Rapid development page solution
Publication Date: 2025.12.04 SCHLUMBERGER TECH CORP
  • US20250370805A1 patent drawing
  • US20250370805A1 patent drawing
  • US20250370805A1 patent drawing

AI summary

Apparatuses, systems, and methods can include a processing resource and a memory device storing instructions executable by the processing resource. The instructions can include hosting a plurality of domains and registering a plurality of components and/or microservices from the plurality of domains. In addition, the instructions can include locating a plurality of components and/or microservices from the plurality of domains, access one or more components and/or microservices from one or more domains, combining the one or more components and/or microservices on a page to create a personalized page, and deploy the personalized page. In some examples, a user deploys and operates the personalized page.