Automated Radio Software Upgrade via Kubernetes Jobs

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network node software upgrade procedures in wireless communication networks are cumbersome, time-consuming, and require specific vendor element managers and trained personnel, leading to service interruptions and a lack of automation, which does not align with cloud native principles.

Innovation Solution

The implementation of Radio Software Upgrade Job Controller (RSUJC) and Radio Software Upgrade Job Engine (RSUJE) systems, which allow for automated software version management across network nodes, enabling job requests to execute software upgrade actions, prechecks, and post-checks, reducing the need for manual intervention and vendor-specific tools.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If vendor-specific element managers and manual procedures are used for software upgrades, then software can be upgraded, but the process becomes cumbersome, time-consuming, and requires trained personnel

Engineering Contradiction:
Improvesoftware upgrade automationVSAvoidupgrade procedure complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The system enables self-service automation through Kubernetes Jobs that automatically execute software upgrade procedures without requiring vendor-specific element managers or trained personnel. The Job controller autonomously manages the upgrade process, including downloading software, validating compatibility, and coordinating upgrades across multiple network nodes, thereby eliminating manual intervention while simplifying the procedure.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces the mechanical/manual system of vendor-specific element managers with an automated software-based solution using Kubernetes Jobs and custom resource definitions. This substitution eliminates the need for manual operations and proprietary management tools, achieving full automation through standardized cloud-native technologies.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If traditional software upgrade procedures are implemented, then software updates can be deployed, but service interruptions occur during the upgrade process

Engineering Contradiction:
Improveservice continuityVSAvoidupgrade speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary actions by downloading and validating software packages before initiating upgrades. The Job controller checks software compatibility, validates prerequisites, and prepares upgrade packages in advance, ensuring that upgrades can be executed smoothly without service interruptions during the actual deployment phase.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements periodic action through staged rollout procedures where upgrades are deployed sequentially to different network nodes rather than simultaneously. The Job controller manages phased updates across multiple nodes, allowing continuous service operation while progressively upgrading the system, thus maintaining productivity without compromising reliability.

Inventive Principle:
Principle #19Periodic action

3Adaptability or versatility

If manual software management procedures are used, then software can be updated, but the process lacks alignment with cloud native principles and scalability

Engineering Contradiction:
Improvecloud native compatibilityVSAvoidupgrade time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system achieves universality by implementing a vendor-agnostic software upgrade management solution using standardized Kubernetes Jobs and custom resource definitions. This universal approach replaces proprietary vendor-specific element managers with a portable, cloud-native framework that can manage software upgrades across diverse network equipment from different vendors, enhancing adaptability while reducing upgrade time through automation.

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

Data Source

PatentUS20240241711A1Physical radio software management in clouds
Publication Date: 2024.07.18 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US20240241711A1 patent drawing
  • US20240241711A1 patent drawing
  • US20240241711A1 patent drawing

AI summary

A first network node is described. The first network node is configured to communicate at least with a second network node. The first network node comprises processing circuitry configured to control at least a software version associated with at least a fourth network node by sending a job request that causes the second network 5 node to execute at least a job action associated with a software upgrade for at least the fourth network node. Other apparatuses, methods, and systems are disclosed.