SD-PMN Control Plane Integration for Resilient SD-WAN Failover

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current approaches to private mobile networks based on cellular technology have not been seamlessly integrated into enterprise cloud-native technologies such as Software Defined WAN (SD-WAN), Edge compute, and Secure Services Edge (SSE), and lack global management of dispersed network elements, system resiliency, and end-to-end quality assurance, particularly for use cases requiring specific coverage, reliability, and latency.

Innovation Solution

A software-defined private mobile network (SD-PMN) architecture is implemented, deploying control plane components like security gateways, UPFs, AMFs, and SMFs at physical locations and SD-WAN POPs, with IPsec tunnels, DMPO tunnels, and centralized management by a PMNO, ensuring seamless failover and resiliency through shared IP addresses across SD-WAN PoPs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If private mobile network based on cellular technology is deployed, then coverage and reliability are improved, but integration with enterprise cloud-native technologies is lacking

Engineering Contradiction:
Improvenetwork reliabilityVSAvoidintegration with enterprise cloud-native technologies
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the private mobile network into distinct functional components (RAN, UPF, AMF, SMF, UDM) that can be independently deployed and integrated with enterprise cloud-native technologies. This modular segmentation allows each component to be selectively integrated with SD-WAN, edge compute, and SASE technologies while maintaining overall network reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a universal architecture where the private mobile network components can serve multiple functions and integrate with various enterprise technologies. The network elements are designed to work across different deployment scenarios (rural FWA, urban private networks, hybrid architectures) and can be integrated with multiple enterprise cloud-native technologies simultaneously.

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

2Area of stationary object

If cellular-based private mobile network is implemented, then coverage is improved, but global management of dispersed network elements becomes complex

Engineering Contradiction:
Improvenetwork coverage areaVSAvoidmanagement complexity
Core Design Contradiction:
Area of stationary objectVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary management system that coordinates between dispersed network elements and enterprise systems. This intermediary layer provides standardized interfaces and protocols that simplify the management of distributed components, enabling global management without proportionally increasing complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent manages dispersed network elements by adding a virtualization dimension, where physical network elements are abstracted into virtual network functions. This dimensional transformation allows centralized management of geographically distributed components through virtualized resource orchestration, reducing management complexity while maintaining wide coverage.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Reliability

If integrated architecture with SD-WAN and edge compute is deployed, then system resiliency is improved, but architectural complexity increases

Engineering Contradiction:
Improvesystem resiliencyVSAvoidarchitectural complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the private mobile network architecture with SD-WAN, edge compute, and SASE into a unified integrated system. By combining these technologies into a single cohesive architecture rather than separate systems, the patent achieves improved resiliency through mutual support while managing overall complexity through unified design principles and common management interfaces.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent implements beforehand cushioning by designing redundant paths and failover mechanisms into the integrated architecture from the outset. The system includes pre-configured resiliency features such as backup communication paths, redundant network elements, and automatic failover capabilities that are built into the architectural design, allowing the system to maintain resiliency without requiring complex reactive measures.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

4Ease of manufacture

If Wi-Fi and access technologies are used for private mobile networks, then ease of deployment is improved, but coverage and reliability for specific use cases are insufficient

Engineering Contradiction:
Improvedeployment easeVSAvoidcoverage and reliability
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The patent applies parameter changes by transitioning from Wi-Fi based access (lower reliability parameters) to cellular-based access (higher reliability parameters) for private mobile networks. This parameter change in the underlying access technology enables the network to meet stringent coverage and reliability requirements for specific use cases while maintaining deployment advantages through standardized cellular infrastructure.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20260025663A1SASE services for private mobile network
Publication Date: 2026.01.22 VELOCLOUD NETWORKS LLC
  • US20260025663A1 patent drawing
  • US20260025663A1 patent drawing
  • US20260025663A1 patent drawing

AI summary

Some embodiments provide a method for implementing a software-defined private mobile network (SD-PMN) for an entity. At a physical location of the entity, the method deploys a first set of control plane components for the SD-PMN, the first set of control plane components including a security gateway, a user-plane function (UPF), an AMF (access and mobility management function), and an SMF (session management function). At an SD-WAN (software-defined wide area network) PoP (point of presence) belonging to a provider of the SD-PMN, the method deploys a second set of control plane components for the SD-PMN that includes a subscriber database that stores data associated with users of the SD-PMN. The method uses an SD-WAN edge router located at the physical location of the entity and a SD-WAN gateway located at the SD-WAN POP to establish a connection from the physical location of the entity to the SD-WAN POP.