Cloud 5G Network Patching Across Staggered Availability Zones

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Patching in cloud-based 5G networks is unwieldy due to the dynamic nature of virtual assets being constantly commissioned and decommissioned, making it difficult to track and manage patch status across large-scale networks.

Innovation Solution

An automated patch deployment system creates staggered maintenance windows for different availability zones, using agents to identify instances and apply patches based on baselines, and filters instances with tags to ensure orderly and resilient patching.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If manual patching methods are used in cloud-based 5G networks, then patching can be applied to virtual assets, but the process becomes unwieldy and difficult to manage due to the dynamic commissioning and decommissioning of virtual assets

Engineering Contradiction:
Improveautomatic patch deploymentVSAvoidpatching management complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The patent segments the patching process into distinct maintenance windows for different availability zones. Each maintenance window independently manages patching for specific virtual assets in a particular zone, dividing the overwhelming global patching task into manageable regional units that can be executed and tracked separately

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by pre-defining maintenance windows with target lists of instances before patching execution. The patching function is pre-configured with baseline patch information and automatically invoked when maintenance windows are created, preparing the patching infrastructure in advance rather than reacting to each patching need individually

Inventive Principle:
Principle #10Preliminary action

2Reliability

If patching is applied to all virtual assets simultaneously, then comprehensive security coverage is achieved, but system-wide outages may occur and network resilience is reduced

Engineering Contradiction:
Improvenetwork resilienceVSAvoidpatching efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent divides the network into multiple availability zones, each with its own maintenance window and target instance list. Patching is executed sequentially across zones rather than simultaneously across the entire network, isolating potential failures to individual zones and preventing system-wide outages while maintaining overall network functionality

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements periodic maintenance windows scheduled at different times for different availability zones. This staggered periodic execution allows the network to maintain operational continuity by keeping zones that are not currently being patched available to serve traffic, thereby preserving productivity while improving reliability

Inventive Principle:
Principle #19Periodic action

3Ease of operation

If maintenance windows are created for each availability zone, then patching can be managed in a controlled manner, but the system complexity increases due to multiple scheduled tasks

Engineering Contradiction:
Improvepatching controlVSAvoidmaintenance window management
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patching function is designed as a universal multi-functional component that can be invoked by any maintenance window across different availability zones. This single patching function handles patch assessment, baseline comparison, and patch application universally, reducing the need for zone-specific patching logic and simplifying overall system management despite the presence of multiple maintenance windows

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

Data Source

PatentUS20260037250A1Patching for cloud-based 5g networks
Publication Date: 2026.02.05 BOOST SUBSCRIBERCO LLC
  • US20260037250A1 patent drawing
  • US20260037250A1 patent drawing
  • US20260037250A1 patent drawing

AI summary

An automated patching system for a cloud-based network includes an instance of a network function running on cloud-based hardware. An agent retrieves a baseline and a list of installed software for the instance. A patching function is in communication with the agent and runs at a first scheduled time in response to a first maintenance window starting at the first scheduled time. The first maintenance window comprises a first target list of instances running in a first availability zone. The patching function also runs at a second scheduled time in response to a second maintenance window. The patching function polls the agent to add the instance to the first target list of the first maintenance window. A first task launched by the patching function runs a patching executable that applies a patch to the instance in response to the patch missing from the list of installed software.