Proxy UDM Scaling for 5G Security Provisioning Load

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current provisioning systems for combined security services in 5G networks face challenges in handling a large quantity of provisioning events, leading to resource consumption issues and inability to provision services for additional subscribers when the quantity exceeds a particular threshold.

Innovation Solution

A proxy Unified Data Management (UDM) device is used to receive control traffic with provisioning events, identify events associated with a service, calculate the quantity of these events, and determine if it satisfies a quantity threshold. If not, it causes another proxy UDM to be added to handle the remaining events, thereby conserving resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a single proxy UDM device handles all provisioning events, then the system structure remains simple, but the system cannot handle large quantities of provisioning events and resources are exhausted

Engineering Contradiction:
Improvehandling capacity of provisioning eventsVSAvoidsystem structure complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system segments the provisioning event handling by introducing multiple proxy UDM devices that work in parallel. Each proxy UDM device handles a portion of the provisioning events, distributing the load across multiple instances rather than concentrating all handling capacity in a single device, thereby increasing overall productivity while maintaining manageable complexity through standardized modular units

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If the proxy UDM handles increasing quantities of provisioning events, then more subscribers can be served, but computing resources are exhausted and the system fails

Engineering Contradiction:
Improvecapacity to serve increasing subscribersVSAvoidsystem stability under load
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system implements dynamic scalability by allowing proxy UDM devices to be added or removed based on the quantity of provisioning events and subscriber load. This dynamic architecture enables the system to adapt to increasing subscriber numbers while maintaining reliability, as each proxy UDM device operates independently with defined capacity thresholds that trigger automated scaling decisions

Inventive Principle:
Principle #15Dynamics

3Productivity

If multiple proxy UDM devices are added to handle more events, then the handling capacity increases, but the system complexity and coordination overhead increase

Engineering Contradiction:
Improveprovisioning event processing capacityVSAvoidmulti-device coordination complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

Each proxy UDM device is designed as a universal, multi-functional unit capable of handling various types of provisioning events independently. This standardization allows multiple devices to work in parallel without requiring complex customization or inter-device coordination, as each unit can autonomously process any provisioning event within its capacity, thereby increasing productivity while minimizing coordination overhead

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

Data Source

PatentUS20250184701A1Systems and methods for network-based provisioning of combined security services for subscribers
Publication Date: 2025.06.05 VERIZON PATENT & LICENSING INC
  • US20250184701A1 patent drawing
  • US20250184701A1 patent drawing
  • US20250184701A1 patent drawing

AI summary

A device may receive control traffic that includes a plurality of provisioning events associated with a network, and may identify provisioning events, of the plurality of provisioning events, that are associated with a service. The device may calculate a quantity of the provisioning events that are associated with the service, and may determine whether the quantity of the provisioning events satisfies a quantity threshold. The device may provide the quantity of the provisioning events to network devices that provide the service to subscribers based on the quantity of the provisioning events failing to satisfy the quantity threshold, or may calculate a remaining quantity of the provisioning events that are associated with the service based on the quantity of the provisioning events satisfying the quantity threshold.