DCT

3:26-cv-10855

Vixly As v. Microsoft Corp

Key Events

Complaint

complaint Intelligence

I. Executive Summary and Procedural Information

Parties & Counsel:
- Plaintiff: Vixly AS (Norway)
- Defendant: Microsoft Corporation (Washington)
- Plaintiff’s Counsel: Villegas & Cefo, LLP
Case Identification: 3:26-cv-10855, N.D. Cal., 09/23/2026
Venue Allegations: Venue is based on allegations that Microsoft maintains a regular and established place of business in the district at its Silicon Valley office and has committed acts of infringement within the district.
Core Dispute: Plaintiff alleges that Defendant’s Microsoft Teams service, specifically its system for routing media traffic, infringes a patent related to selective forwarding of data over a private transport network.
Technical Context: The technology addresses quality-of-service issues for real-time internet communications (e.g., video conferencing) by creating a managed, high-quality network path to bypass the unpredictable public internet.
Key Procedural History: The complaint notes that the patent-in-suit was assigned by the inventors to Media Network Services AS, which subsequently changed its name to Plaintiff Vixly AS. The complaint also extensively references technical literature to distinguish the patented invention from prior art, a common theme in patent validity disputes.

Case Timeline

Date	Event
2008-01-02	Priority Date for ’902 Patent
2010-08-05	Inventors assign rights to Media Network Services AS
2019-04-16	U.S. Patent 10,263,902 issues
2023-04-06	Date of Microsoft documentation (Microsoft Global Network)
2023-12-05	Media Network Services AS changes name to Vixly AS
2026-03-30	Date of Microsoft documentation (Teams Call Flows)
2026-07-16	Date of Microsoft documentation (Teams Security Guide)
2026-09-23	Complaint filed

II. Technology and Patent(s)-in-Suit Analysis

U.S. Patent No. 10,263,902 - Device and System for Selective Forwarding

Patent Identification: U.S. Patent No. 10,263,902, "Device and System for Selective Forwarding," issued April 16, 2019.

The Invention Explained

Problem Addressed: The patent's background section describes the shortcomings of the "best-effort" public internet for real-time applications like VoIP, which are sensitive to delay, jitter, and packet loss Compl. ¶9 It notes that prior quality-of-service frameworks (like IntServ and DiffServ) and routing practices (like "hot-potato" routing) failed to provide reliable, end-to-end performance guarantees, especially across different administrative domains Compl. ¶¶12-13 ’902 Patent, col. 1:25-2:11
The Patented Solution: The invention proposes a system architecture to overcome these issues. It uses a "private transport network" with multiple Points of Presence (PoPs) connected by "guaranteed bandwidth channels" ’902 Patent, abstract A terminal seeking to send latency-sensitive data first communicates with a "control server" to gain admission to this private network Compl. ¶24 Then, instead of addressing the data to the final recipient, the terminal addresses it to a "transport relay" within the private network. This addressing scheme forces the data to travel over the controlled, high-quality network for the majority of its path, bypassing the congestion and unpredictability of the public internet before being delivered to the second terminal Compl. ¶24 ’902 Patent, col. 10:43-53
Technical Importance: This architecture provides a method for delivering enhanced quality of service for over-the-top applications without requiring fundamental changes to the underlying internet infrastructure, effectively creating a premium transport overlay.

Key Claims at a Glance

The complaint asserts infringement of at least independent method claim 11 Compl. ¶1 Compl. ¶53
The essential elements of independent claim 11 include:
- A first data terminal sending authorization information to a control server to gain admission to a private transport network.
- The first data terminal sending latency-sensitive data by addressing it to a transport relay within the private transport network.
- This addressing causes the data to travel from the first terminal, through the private transport network via the relay over a guaranteed bandwidth channel, and finally to the second data terminal.

III. The Accused Instrumentality

Product Identification

The Accused Instrumentalities are "relayed Microsoft Teams audio and video sessions" that utilize Teams applications, Teams Transport Relays, and the "Microsoft Global Network" Compl. ¶38 Compl. ¶6

Functionality and Market Context

The complaint alleges that in certain Microsoft Teams calls, media traffic does not flow directly between users over the public internet Compl. ¶42 Instead, when a "relay path" is selected, a Teams client sends real-time audio and video media to a "Teams Transport Relay" Compl. ¶41 This relay is part of the "Microsoft Global Network," which the complaint characterizes as a worldwide private network with globally distributed PoPs designed to keep traffic on its own backbone "as long as possible" to optimize performance Compl. ¶39 Compl. ¶45 Access to these relays is allegedly controlled through authentication mechanisms like Microsoft Entra ID and OAuth, which the complaint frames as an admission control step Compl. ¶43 The complaint references Microsoft's own call-flow diagrams, which allegedly show media traversing a Teams Transport Relay within the Microsoft 365 network segment Compl. ¶49

IV. Analysis of Infringement Allegations

’902 Patent Infringement Allegations

Claim Element (from Independent Claim 11)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
the first data terminal sending authorization information to the control server in order to gain admission to the private transport network;	A Teams client uses credentials-based tokens and authentication services (Microsoft Entra ID, OAuth) to secure access to media relays, which allegedly functions as gaining admission to the accused private transport path Compl. ¶43	¶43	col. 10:40-42
and the first data terminal sending latency-sensitive data to the second data terminal by addressing the latency-sensitive data to the transport relay in the private transport network,	For a relayed session, a Teams client addresses "highly latency sensitive" media packets to the destination IP address and port of a selected "Teams Transport Relay" within the Microsoft 365 network, rather than to the remote user's IP address Compl. ¶42	¶42	col. 10:43-46
to cause the latency-sensitive data (i) to travel from the first data terminal to the private transport network via the first ISP network,	Media from the first Teams terminal travels via its local ISP to an edge node of the Microsoft Global Network Compl. ¶45 Compl. ¶54	¶54	col. 10:46-48
and then (ii) to travel through the private transport network, via the transport relay, over a guaranteed bandwidth channel of the guaranteed bandwidth channels,	The media then travels through the Microsoft Global Network, which the complaint alleges includes "multiple PoPs connected by physical or virtual links with provisioned transmission capacity," constituting "guaranteed bandwidth channels" Compl. ¶48	¶48	col. 10:49-51
and then (iii) to travel from the private transport network to the second data terminal via the second ISP network.	The media exits the Microsoft Global Network and travels through the second terminal's ISP network to reach the second user Compl. ¶54	¶54	col. 10:52-53

Identified Points of Contention:
- Scope Questions: A central question may be whether Microsoft's "Global Network"—a multi-purpose, multi-tenant cloud backbone—qualifies as a "private transport network" as contemplated by the patent. Similarly, the court may need to determine if Microsoft's use of "provisioned transmission capacity" and "software-defined traffic engineering" Compl. ¶48 meets the "guaranteed bandwidth channel" limitation.
- Technical Questions: The analysis may focus on whether the application-layer authentication for a Teams service Compl. ¶43 is functionally the same as the claimed "admission control to the private transport network." A question for the court will be whether authenticating to use a service is equivalent to gaining admission to the underlying network infrastructure for the purpose of protecting its capacity, as the complaint alleges Compl. ¶25

V. Key Claim Terms for Construction

The Term: "private transport network"
- Context and Importance: The definition of this term is fundamental. Its construction will determine whether Microsoft's "Global Network" infrastructure can be considered an infringing system.
- Evidence for a Broader Interpretation: The specification describes the network as comprising "retransmission devices (20) at multiple points of presence (PoPs), internally connected by guaranteed bandwidth channels (50), owned or rented from transport providers (12)" ’902 Patent, col. 10:57-61 Plaintiff may argue that Microsoft's network, with its global PoPs and owned fiber, fits this functional description.
- Evidence for a Narrower Interpretation: Defendant may argue that the patent envisions a dedicated network distinct from the general internet, not a shared, multi-tenant cloud backbone that also carries non-real-time traffic. The patent distinguishes its invention from prior art based on specific network architectures, which may suggest a more limited scope ’902 Patent, col. 2:12-50
The Term: "guaranteed bandwidth channel"
- Context and Importance: This term is critical for the quality-of-service aspect of the invention. Whether Microsoft's network provides this "guarantee" will be a key point of dispute.
- Evidence for a Broader Interpretation: Plaintiff alleges Microsoft's network has "provisioned transmission capacity" and uses "centralized software-defined traffic engineering" Compl. ¶48, which it argues constitutes a functional guarantee. The patent's claims use the term without extensive definition, potentially leaving it open to a broader, functional interpretation ’902 Patent, col. 10:30
- Evidence for a Narrower Interpretation: Defendant may argue that this term implies a hard, circuit-like reservation of capacity for a given flow, which its packet-switched network does not provide. The patent's contrast with DiffServ, which only prioritizes traffic, could support an argument that "guarantee" requires more than just high-quality, managed transport ’902 Patent, col. 2:55-3:8

VI. Other Allegations

Indirect Infringement: The complaint alleges that Microsoft directs or controls the actions of the first data terminal (the user's device) Compl. ¶55 The theory is that Microsoft conditions the receipt of the relayed Teams service on the user's client performing the claimed steps of authorization and addressing, using software and protocols dictated by Microsoft Compl. ¶55 This raises a question of divided infringement.
Willful Infringement: The complaint does not contain a specific count for willful infringement or allege pre-suit knowledge of the patent. However, it requests a finding that the case is "exceptional" under 35 U.S.C. § 285 and an award of attorneys' fees, which is relief often predicated on a finding of willfulness or other inequitable conduct Compl. Prayer for Relief E

VII. Analyst’s Conclusion: Key Questions for the Case

This case appears to center on the application of patent claims, drafted in the context of 2008-era networking, to the realities of a modern, hyperscale cloud provider's infrastructure. The key questions for the court will likely include:

A core issue will be one of definitional scope: Can terms like "private transport network" and "guaranteed bandwidth channel", originating from a patent with a 2008 priority date, be construed to read on a sophisticated, multi-tenant, software-defined network like the Microsoft Global Network?
A second key question will be one of functional equivalence: Does Microsoft's application-layer authentication process for its Teams service perform the same function as the claimed "admission control to the private transport network"? This will require a detailed analysis of whether controlling access to a service is legally and technically equivalent to controlling admission to a network resource as claimed.
Finally, a central liability question will be one of attribution: Since the claimed method involves steps performed by both Microsoft's servers and its users' devices, the court will have to decide if Microsoft "directs or controls" its users' actions to a degree sufficient to be held liable for direct infringement of the entire method claim.