# US 2026/0099320 A1 · Telecom Microservice Rolling Upgrades

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0099320 A1
- Document ID: US20260099320A1
- Status: Published application
- Kind: A1
- Application number: 19/406,546
- Filed: 2025-12-02
- Published: 2026-04-09
- Earliest claimed: 2022-01-17
- Assignees: Parallel Wireless, Inc.
- Applicants: Parallel Wireless, Inc.
- Inventors: Mukesh Singhal
- Web page: https://patentgrep.com/patent/US20260099320A1

## CPC

- G06F 8/656: while running
- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method is disclosed for providing a telecom microservice rolling upgrade, the method comprising: providing, by a Service Management and Orchestration (SMO), a new instance of F1 demux in a same cluster and namespace; advertising the new instance of the F1 demux to all PODs and micro services; informing, by the SMO, an old F1 demux to start a version upgrade to a new instance; sending, by the old F1 demux, a trigger to start a reconcile procedure to a new F1 demux; advertising that the old instance of the F1 demux is not available to take up new calls from internal PODs and micro-service, and is accepting traffic via the new F1 demux only; routing, by the old F1 demux, all incoming F1 traffic from a Distributed Unit (DU) to the new F1 demux; and instructing the DU, by the old F1 demux, to add a Transport Network Layer (TNL) association of the new F1 demux.

## Claims

### Claim 1

A method for providing a telecom microservice rolling upgrade, the method comprising:
providing, by a Service Management and Orchestration (SMO), a new instance of F1 demux in a same cluster and namespace;
advertising the new instance of the F1 demux to all PODs and micro services;
informing, by the SMO, an old F1 demux to start a version upgrade to a new instance;
sending, by the old F1 demux, a trigger to start a reconcile procedure to a new F1 demux;
advertising that the old instance of the F1 demux is not available to take up new calls from internal PODs and micro-service, and is accepting traffic via the new F1 demux only;
routing, by the old F1 demux, all incoming F1 traffic from a Distributed Unit
(DU) to the new F1 demux; and
instructing the DU, by the old F1 demux, to add a Transport Network Layer (TNL) association of the new F1 demux.
