IP Library Granted Patent US 10,581,965
Granted Patent B2
US 10,581,965 · App. 15/859,329 · Granted Mar 3, 2020

Mirroring flow configurations for internet protocol receivers

Inventor: Duncan G. Millard (Portland, OR)
Assignee: PROJECT GIANTS, LLC
H04L67/1095G06F3/1454H04L43/10H04L65/4076H04L67/38G09G2370/02G09G2370/042G09G2370/10
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,581,965
App. No.
15/859,329
Granted
Mar 3, 2020
Kind
B2
Abstract

Disclosed is a mechanism of operating a Networked Media Open Specifications (NMOS) Application Programming Interface (API) at a node controlling a local device including a local receiver. A flow message is received via the NMOS API. The flow message contains a flow state of a target receiver at a remote node. A local receiver at the local device is configured to mirror the flow state of the target receiver at the remote node. The NMOS API then notifies a registry with an updated flow state of the local receiver at the local device.

Claims (24)

1. A computer readable storage medium having instructions stored thereon that, when executed by a processor of a node, cause the node to:

operate a Networked Media Open Specifications (NMOS) Application Programming Interface (API);

receive a flow message via the NMOS API, the flow message containing a flow state of a target receiver at a remote node;

configure a local receiver at a local device to mirror the flow state of the target receiver at the remote node; and

notify, via the NMOS API, a registry with an updated flow state of the local receiver at the local device.

2. The computer readable storage medium of claim 1 , wherein mirroring the flow state of the target receiver at the remote node includes obtaining, at the local receiver, a shared flow received by the target receiver, the shared flow received from a shared sender node.

3. The computer readable storage medium of claim 1 , wherein the processor further causes the node to periodically transmit poll messages to a registry, the poll messages requesting the flow state of the target receiver at the remote node.

4. The computer readable storage medium of claim 3 , wherein the flow message is received from the registry.

5. The computer readable storage medium of claim 1 , wherein the processor further causes the node to periodically transmit poll messages to the remote node, the poll messages requesting the flow state of the target receiver at the remote node.

6. The computer readable storage medium of claim 5 , wherein the flow message is received from the remote node.

7. The computer readable storage medium of claim 1 , wherein the processor further causes the node to transmit a mirror setup message to a connection manager.

8. The computer readable storage medium of claim 1 , wherein the flow message is received from a connection manager.

9. A method comprising:

operating a Networked Media Open Specifications (NMOS) Application Programming Interface (API) at a node controlling a local device including a local receiver;

receiving a flow message via the NMOS API, the flow message containing a flow state of a target receiver at a remote node;

configuring the local receiver at the local device to mirror the flow state of the target receiver at the remote node; and

notifying, via the NMOS API, a registry with an updated flow state of the local receiver at the local device.

10. The method of claim 9 , wherein mirroring the flow state of the target receiver at the remote node includes obtaining, at the local receiver, a shared flow received by the target receiver, the shared flow received from a shared sender node.

11. The method of claim 9 , further comprising periodically transmitting poll messages to a registry, the poll messages requesting the flow state of the target receiver at the remote node.

12. The method of claim 11 , wherein the flow message is received from the registry.

13. The method of claim 9 , further comprising periodically transmitting poll messages to the remote node, the poll messages requesting the flow state of the target receiver at the remote node.

14. The method of claim 13 , wherein the flow message is received from the remote node.

15. The method of claim 9 , further comprising transmitting a mirror setup message to a connection manager.

16. The method of claim 9 , wherein the flow message is received from a connection manager.

Assignments (7)
SECURITY INTEREST Recorded Jun 9, 2025
From: INEOQUEST TECHNOLOGIES, LLC; PROJECT GIANTS, LLC
To: FORTRESS CREDIT CORP.
Reel/Frame 071493/0030 →
CORRECTIVE ASSIGNMENT TO CORRECT THE MISSING PROPERTY AND GRANTOR NAME OF PROJECT GIANTS. LLC PREVIOUSLY RECORDED AT REEL: 054089 FRAME: 0786. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY INTEREST. Recorded Jun 1, 2021
From: PROJECT GIANTS, LLC
To: FORTRESS CREDIT CORP., AS AGENT
Reel/Frame 056442/0845 →
RELEASE OF SECURITY INTEREST Recorded Oct 16, 2020
From: SILICON VALLEY BANK
To: PROJECT GIANTS, LLC
Reel/Frame 054090/0934 →
SECURITY INTEREST Recorded Oct 15, 2020
From: PROJECT GIANT, LLC
To: FORTRESS CREDIT CORP., AS AGENT
Reel/Frame 054089/0786 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 25, 2019
From: TEKTRONIX, INC.
To: PROJECT GIANTS, LLC
Reel/Frame 049870/0073 →
PATENT SECURITY AGREEMENT Recorded Jul 22, 2019
From: PROJECT GIANTS, LLC
To: SILICON VALLEY BANK
Reel/Frame 049819/0702 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 10, 2018
From: MILLARD, DUNCAN G.
To: TEKTRONIX, INC
Reel/Frame 044583/0311 →
Continuity (2)
Provisional Application 62565891 · Sep 29, 2017
Related Publication 20190104176A1 · Apr 4, 2019