Widget Delivery Workflow System Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Integrating software widgets into cloud-based deployment environments is challenging due to the lack of a systematic integration process, particularly when services like authentication, authorization, metering, billing, and task management need to operate seamlessly with the widgets.

Innovation Solution

A method is introduced that involves receiving and storing software widget source code, determining the appropriate version and view for a deployment environment, constructing a build that includes both application and software widget source code, and deploying it within the environment, ensuring seamless integration with services such as authentication and authorization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If software widgets are integrated into cloud-based deployment environments without a systematic process, then integration flexibility is maintained, but integration reliability and compatibility deteriorate

Engineering Contradiction:
Improveintegration reliabilityVSAvoidintegration process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the integration process into distinct phases: widget development environment setup, cloud deployment environment configuration, version mapping, and build construction. Each phase handles specific tasks independently, improving reliability without overwhelming complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary actions by pre-configuring the widget development environment with necessary services (authentication, authorization, metering, billing, notification, task management) before integration. Version mappings and compatibility checks are established in advance, ensuring reliable integration when deployment occurs.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If multiple services (authentication, authorization, metering, billing, notification, task management) are integrated with software widgets, then functionality and versatility improve, but system complexity increases

Engineering Contradiction:
Improveservice integration versatilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal widget development environment that incorporates multiple services (authentication, authorization, metering, billing, notification, task management) as standardized components. This multi-functional platform allows widgets to access various services through consistent interfaces, enhancing versatility while managing complexity through standardization.

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

Solution Approach 2:

The patent introduces an intermediary widget development environment that mediates between the software widget and cloud-based services. This intermediary layer handles service integration, version mapping, and compatibility management, allowing widgets to interact with multiple services without direct complex connections to each service.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Manufacturing precision

If version matching between application source code and software widget source code is enforced, then compatibility improves, but build time and processing complexity increase

Engineering Contradiction:
Improveversion compatibilityVSAvoidbuild time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent performs preliminary version mapping and compatibility determination before the actual build process. Version relationships are pre-analyzed and stored, allowing the system to quickly retrieve compatibility information during deployment without performing complex version matching calculations at build time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates a copy or representation of version mapping relationships in a structured format that can be quickly queried during the build process. This pre-processed version information allows rapid compatibility verification without re-analyzing the entire version hierarchy during each build operation.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12073211B2Widget delivery workflow system and method
Publication Date: 2024.08.27 SCHLUMBERGER TECH CORP
  • US12073211B2 patent drawing
  • US12073211B2 patent drawing
  • US12073211B2 patent drawing

AI summary

A method may include receiving a version of software widget source code, storing the version of software widget source code, and determining that a version of application source code and a view of software widget source code are used in a deployment environment. The version of application source code may call the version of software widget source code. The method may further include determining that the version of software widget source code corresponds to the view of software widget source code, constructing a build including the version of application source code and the version of software widget source code, and deploying the build in the deployment environment.