Priority-Based Network Function Routing for 5G Canary Releases

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In 5G wireless network architectures, the rapid development and deployment of network functions pose challenges in ensuring stability and reliability, particularly due to short development times and lifecycle, necessitating continuous integration and delivery practices like Canary releases, which require controlled routing of messages and transactions to manage risk and prioritize user exposure.

Innovation Solution

Implementing a priority-based routing system within the Service-Based Architecture (SBA) for 5G networks, where network functions and services are assigned priorities, allowing messages and transactions to be routed to instances with equal or higher priority, thereby controlling exposure to Canary releases and ensuring stable operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If new software versions are deployed rapidly to meet user demands, then productivity and service improvement speed increase, but system reliability and stability deteriorate

Engineering Contradiction:

Improvesoftware deployment speedVSAvoidnetwork stability

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent segments the user base into different priority groups (high-priority and low-priority users) and routes messages differently based on user priority. Canary releases are deployed to low-priority users first, while high-priority users continue receiving messages from stable versions. This segmentation allows rapid software deployment to test new versions without compromising overall system reliability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent applies partial action by routing only a subset of messages (those from low-priority users) to the Canary release instances, while the majority of messages (from high-priority users) continue to be routed to stable versions. This partial deployment allows the system to benefit from new software features and bug fixes while maintaining stability for critical operations.

Inventive Principle:

Principle #16Partial or excessive action

2Reliability

If Canary releases are used to test new software versions, then system reliability improves through controlled testing, but device complexity increases due to routing logic

Engineering Contradiction:

Improvesoftware testing safetyVSAvoidrouting system complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a message broker as an intermediary component that handles the complexity of routing logic. The broker receives messages, determines their priority based on user information, and routes them to appropriate instances (Canary or stable versions). This intermediary approach centralizes the routing complexity in a single component rather than distributing it throughout the system, making the overall architecture more manageable.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback mechanisms where message brokers continuously monitor instance health and performance metrics. Based on this feedback, the brokers dynamically adjust routing decisions, routing messages away from instances that are performing poorly or experiencing issues. This feedback loop allows the system to maintain reliability while managing the complexity of multiple instances through adaptive routing.

Inventive Principle:

Principle #23Feedback

3Productivity

If all users are exposed to new software versions simultaneously, then deployment efficiency increases, but risk of widespread failures increases

Engineering Contradiction:

Improvedeployment efficiencyVSAvoidfailure propagation risk

Core Design Contradiction:

ProductivityVSObject-affected harmful factors

Solution Approach 1:

The patent segments the user population into high-priority and low-priority groups, routing messages from low-priority users to Canary release instances first. This segmentation creates a controlled rollout strategy where new software versions are tested on a limited subset of users before potential full deployment, preventing widespread failure propagation while maintaining deployment efficiency.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system prepares cushioning measures by maintaining both Canary and stable version instances simultaneously. Before fully deploying new software versions to all users, the system has stable versions ready as a fallback option. This prior cushioning allows the system to absorb potential failures from Canary releases without affecting overall service availability.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS11026074B2Rolling out updated network functions and services to a subset of network users

Publication Date: 2021.06.01 VERIZON PATENT & LICENSING INC

AI summary

A system includes an updated network function and a consumer network function. The updated network function includes a recent update and is configured to register at a Network Repository Function (NRF) using a Network Function (profile (NF profile). The NF profile indicates a network function type (NF type) and a first priority associated with the update. The consumer network function is configured to: receive a message from a network component; determine to engage a service of a network function of the NF type based on the message; determine a desired priority for the service; and send a discovery request to the NRF in response to the message; receive a search result from the NRF in response to the discovery request. The search result has a list of candidate network functions of the NF type.