Runtime Function Metadata Verification for Nano Functions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional software development is time-consuming, error-prone, and costly, requiring skilled teams and extensive resources, making it difficult for smaller entities or solo developers to create reliable, enterprise-scale web applications that meet quality and security standards.

Innovation Solution

A platform for runtime management of application components that allows users to configure and deploy applications by determining functions to be executed as nano functions, verifying compliance with license terms and versioning, and employing containerized execution to ensure deterministic behavior and efficient resource usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional software development methods are used, then applications can be developed with full functionality, but the development process becomes time-consuming, error-prone, and expensive requiring large teams

Engineering Contradiction:
Improveapplication development speedVSAvoidapplication quality and security
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments applications into reusable functions that can be independently developed, verified, and combined. Functions are broken down into smaller executable units with defined interfaces, allowing parallel development and reducing overall development time while maintaining quality through modular verification processes

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary verification of function compliance with license terms and version requirements before execution. Metadata is prepared in advance containing verification rules, and the system performs automated checks before functions are executed, ensuring quality and security requirements are met prior to deployment

Inventive Principle:
Principle #10Preliminary action

2Reliability

If skilled development teams are assembled to ensure quality and security, then reliable applications can be created, but the cost and complexity of the project increases significantly

Engineering Contradiction:
Improveapplication quality and securityVSAvoiddevelopment team structure and resources
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements self-service verification where the system automatically checks function compliance with license terms, version requirements, and security policies without requiring manual review by skilled personnel. The automated verification process using metadata reduces dependency on expert teams while maintaining high reliability standards

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent incorporates feedback mechanisms where verification results from automated checks are used to guide function execution and deployment decisions. The system provides feedback on compliance status and adjusts execution based on verification outcomes, ensuring quality requirements are met through automated control loops rather than manual inspection

Inventive Principle:
Principle #23Feedback

3Productivity

If functions are executed without verification, then development and deployment is faster, but compliance with license terms and version control cannot be ensured

Engineering Contradiction:
Improvedeployment speedVSAvoidcompliance with license terms and versioning
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent performs preliminary verification of license terms and version compliance before function execution. Metadata containing verification rules is prepared in advance, and automated checks are conducted prior to deployment, ensuring compliance requirements are met before functions are executed, thus maintaining both speed and adaptability

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces metadata as an intermediary layer between function execution and compliance verification. The metadata contains verification rules and requirements, acting as a mediator that enables automated checking of license terms and version control without slowing down the execution process, thus maintaining both productivity and adaptability

Inventive Principle:
Principle #24Intermediary (Mediator)

4Quantity of substance

If resource requirements are reduced for smaller teams, then development becomes more accessible, but the ability to create enterprise-scale applications is compromised

Engineering Contradiction:
Improveresource requirementsVSAvoidcapability to create enterprise-scale applications
Core Design Contradiction:
Quantity of substanceVSAdaptability or versatility

Solution Approach 1:

The patent merges multiple functions into composite applications through a standardized framework. Reusable functions are combined to build enterprise-scale applications, allowing smaller teams to leverage pre-developed functionality rather than building everything from scratch, thus reducing resource requirements while maintaining the capability to create complex applications

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates universal functions with standardized interfaces that can be used across multiple applications. A single function can serve multiple purposes and be reused in different contexts, increasing the versatility and capability of smaller teams to create enterprise-scale applications without proportionally increasing resource requirements

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

Data Source

PatentUS11762963B1Runtime management of application components
Publication Date: 2023.09.19 BILDR INC
  • US11762963B1 patent drawing
  • US11762963B1 patent drawing
  • US11762963B1 patent drawing

AI summary

Techniques are described for runtime checking of function metadata prior to execution of a function in an environment. An application may include any appropriate number of components at one or more levels in a hierarchical arrangement, and each component may be packaged with metadata that describes the component. A function, or any component, may be packaged with metadata that includes term(s) governing the usage of the function. The term(s) may be checked, at runtime, during execution of the application to determine whether the function is to be executed. A function may also be hashed at runtime for verification of function version. Function(s) may be individually and independently executed as containerized nano functions within the environment.