Compilation Deployment Service Software Build Load

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current software build and load processes are inadequate for dynamic environments like large data-centers and cloud deployments, where frequent software changes and complex applications spanning multiple processing units require more sophisticated compatibility checks and deployment management to avoid errors and downtime.

Innovation Solution

A compilation and deployment service acts as an intermediary that inspects and merges new software with existing software, ensuring compatibility and deploying it to target processing units, using a database to manage active software and constraints, and automating the deployment process to handle complex dependencies and compatibility checks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If new load modules are deployed frequently in dynamic environments, then software adaptability and responsiveness to changes improve, but the risk of compatibility errors and system downtime increases

Engineering Contradiction:
Improvesoftware adaptabilityVSAvoidsystem reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary compatibility checks and dependency verification before deploying new load modules. The build service validates new modules against the existing software stack, framework versions, and dependencies in advance, preventing compatibility errors before they occur in production environments.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

A build service acts as an intermediary between the deployment system and the processing units. This intermediary validates, compiles, and verifies load modules before they reach the target system, mediating between the need for frequent deployment and the requirement for system stability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If comprehensive compatibility checks are performed before deployment, then software reliability improves, but deployment time and process complexity increase

Engineering Contradiction:
Improvesoftware compatibilityVSAvoiddeployment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Compatibility checks, dependency verification, and validation processes are performed in advance during the build phase. By completing these checks before deployment, the system ensures software compatibility without delaying the actual deployment execution, as validation results are cached and reused.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The build service automatically performs dependency resolution, compatibility validation, and conflict detection without requiring manual intervention. The system self- verifies load module compatibility against the software stack and framework versions, eliminating the need for time-consuming manual checking while maintaining comprehensive validation.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If manual software deployment processes are used, then deployment control and accuracy improve, but productivity and automation level decrease

Engineering Contradiction:
Improvedeployment controlVSAvoiddeployment efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The build service automatically manages the entire deployment pipeline including dependency resolution, compatibility validation, compilation, and load module generation. The system self-service validates constraints, resolves conflicts, and produces deployable artifacts without requiring manual intervention at each step, maintaining control while dramatically improving productivity.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The build service acts as an automated intermediary that bridges manual deployment requests and system execution. It accepts deployment specifications, automatically performs validation and compilation, and delivers verified load modules, reducing manual effort while maintaining precise control over the deployment process through programmable constraints and rules.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If software from multiple suppliers is integrated, then system versatility and functionality improve, but complexity of merging and compatibility management increases

Engineering Contradiction:
Improvesoftware integration capabilityVSAvoidsoftware merging complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The build service serves as a central intermediary that manages the integration of load modules from multiple suppliers. It automatically resolves dependencies between different software components, validates compatibility across diverse sources, and coordinates merging conflicts, simplifying the complexity of multi-vendor software integration into a unified deployable system.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The build service implements a universal validation framework that handles load modules from any supplier through a common interface and constraint system. It universally applies dependency resolution, compatibility checking, and conflict detection across diverse software sources, making the integration process consistent and manageable regardless of the number or type of suppliers involved.

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

Data Source

PatentEP2932374B1Systems, methods, and computer program products for a software build and load process using a compilation and deployment service
Publication Date: 2023.11.15 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • EP2932374B1 patent drawingFigure 1
  • EP2932374B1 patent drawingFigure 2
  • EP2932374B1 patent drawingFigure 3

AI summary

Systems, methods, and computer program products for a software build and load process using a compilation and deployment service(300). A method for a software build and load process using a compilation and deployment service(300) includes receiving, at the service,new software. The method further includes comparing, at the service (300),the received new software with data in a database(525, 725), wherein the data comprises active software. The method further includes merging, at the service(300),said new software and active software into one or more load modules (330, 550a, 550b) based on the comparison. The method further includes deploying the one or more load modules to one or more target processing units(340, 400, 410).