IP Library Granted Patent US 12,425,696
Granted Patent B2
US 12,425,696 · App. 18/443,059 · Granted Sep 23, 2025

Emulated television tuner

Inventors: Paul R. Cooper (San Jose, CA); Yvonne N. Ellefson (Ben Lomond, CA); Arleen Camaganacan Fernando (Redwood City, CA); Imran Arif Maskatia (Palo Alto, CA); Matthew Ryan Patterson (Mountain View, CA); Matt Henry Van der Staay (San Jose, CA); Chad Michael Williams (San Mateo, CA)
Assignee: Adeia Technologies Inc.
H04N21/6125H04N21/4143H04N21/4263H04N21/443
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 12,425,696
App. No.
18/443,059
Granted
Sep 23, 2025
Kind
B2
Abstract

Television tuner emulation techniques are described. In an implementation, a television tuner is emulated through execution of software on a processing system by a computing device, the emulated television tuner includes functionality to obtain television content over an Internet Protocol (IP) based network. The functionality of the emulated television tuner is exposed to one or more applications that are executed by the computing device such that the application is not aware that the television tuner is emulated through execution of the software.

Claims (43)

1. A method comprising:

receiving, a channel tuning request from an application for a legacy tuner interface, wherein the channel tuning request comprises data indicative of a channel's frequency and a request to configure a physical tuner to the channel's frequency;

transferring, by the legacy tuner interface, the channel tuning request to a tuner emulator;

accessing, by the tuner emulator, a network address corresponding to the channel's frequency using a mapping that maps frequencies to network addresses;

accessing video data using a network protocol from the network address corresponding to the channel's frequency;

formatting video data into a format suitable for the application; and

delivering reformatted video data to the application, wherein the application is not aware that the tuner emulator is emulated.

2. The method of claim 1 , wherein the application is one of: a digital video recorder (DVR), a program guide, a program that translates, or an application synchronizes television content to mobile devices.

3. The method of claim 2 , wherein the application and the tuner emulator are executing on an operating system of a computing device, wherein the operating system of the computing device is configured to communicate to a distribution system that receives television content from a content provider over an IP-based network.

4. The method of claim 1 , wherein the tuner emulator is configured to establish and maintain connections to a plurality of servers in a distribution system that combine their video streams.

5. The method of claim 4 , wherein the application is not configured to directly process network-IP-based unicast streams and is not configured to directly process network-IP-based multicast streams.

6. The method of claim 5 , wherein formatting of video data comprises removing packet headers from the video data received via the network protocol and assembling processed packets of the video data into a payload that is consistent with traditional broadcast TV feeds.

7. The method of claim 1 , wherein the receiving the channel tuning request from the application comprises receiving, from the application, a standard API request that is configured for tuning a non-IP based television tuner.

8. A system comprising:

a processing circuitry configured to:

receive, a channel tuning request from an application for a legacy tuner interface, wherein the channel tuning request comprises data indicative of a channel's frequency and a request to configure a physical tuner to the channel's frequency;

transfer, via the legacy tuner interface, the channel tuning request to a tuner emulator;

a networking circuitry configured to:

access, at direction of the tuner emulator, a network address corresponding to the channel's frequency using a mapping that maps frequencies to network addresses;

access video data using a network protocol from the network address corresponding to the channel's frequency;

wherein the processing circuitry is further configured to:

format video data into a format suitable for the application; and

deliver reformatted video data to the application, wherein the application is not aware that the tuner emulator is emulated.

9. The system of claim 8 , wherein the application is one of: a digital video recorder (DVR), a program guide, a program that translates, or an application synchronizes television content to mobile devices.

10. The system of claim 9 , wherein the application and the tuner emulator are executing on an operating system of the system, wherein the operating system of the system is configured to communicate to a distribution system that receives television content from a content provider over an IP-based network.

11. The system of claim 8 , wherein the networking circuitry is configured to, at direction of the tuner emulator, establish and maintain connections to a plurality of servers in a distribution system that combine their video streams.

12. The system of claim 11 , wherein the application is not configured to directly process network-IP-based unicast streams and is not configured to directly process network-IP-based multicast streams.

13. The system of claim 12 , wherein the processing circuitry is configured to remove packet headers from the video data received via the network protocol and assemble processed packets of the video data into a payload that is consistent with traditional broadcast TV feeds.

14. The processing circuitry of claim 8 , wherein the processing circuitry is configured to: receive, the channel tuning request from the application by receiving, from the application, a standard API request that is configured for tuning a non-IP based television tuner.

15. A non-transitory computer-readable medium having non-transitory computer-readable instructions encoded thereon that, when executed by a processing circuitry, cause the processing circuitry to:

receive, a channel tuning request from an application for a legacy tuner interface, wherein the channel tuning request comprises data indicative of a channel's frequency and a request to configure a physical tuner to the channel's frequency;

transfer, by the legacy tuner interface, the channel tuning request to a tuner emulator; and

wherein the non-transitory computer-readable instructions, when executed by the processing circuitry, further cause networking circuitry to:

access, by the tuner emulator, a network address corresponding to the channel's frequency using a mapping that maps frequencies to network addresses;

access video data using a network protocol from the network address corresponding to the channel's frequency; and

wherein the non-transitory computer-readable instructions, when executed by the processing circuitry, further cause the processing circuitry to:

format video data into a format suitable for the application; and

deliver reformatted video data to the application, wherein the application is not aware that the tuner emulator is emulated.

16. The non-transitory computer-readable medium of claim 15 , wherein the application is one of: a digital video recorder (DVR), a program guide, a program that translates, or an application synchronizes television content to mobile devices.

17. The non-transitory computer-readable medium of claim 16 , wherein the application and the tuner emulator are executing on an operating system of a computing device, wherein the operating system of the computing device is configured to communicate to a distribution system that receives television content from a content provider over an IP-based network.

18. The non-transitory computer-readable medium of claim 15 , wherein the tuner emulator is configured to establish and maintain connections to a plurality of servers in a distribution system that combine their video streams.

19. The non-transitory computer-readable medium of claim 18 , wherein the non-transitory computer-readable instructions cause the processing circuitry to remove packet headers from the video data received via the network protocol and assemble processed packets of the video data into a payload that is consistent with traditional broadcast TV feeds.

20. The non-transitory computer-readable medium of claim 15 , wherein the non-transitory computer-readable instructions cause the processing circuitry to receive the channel tuning request from the application comprising a standard API request that is configured for tuning a non-IP based television tuner.

Assignments (3)
CHANGE OF NAME Recorded Sep 25, 2024
From: ROVI TECHNOLOGIES CORPORATION
To: ADEIA TECHNOLOGIES INC.
Reel/Frame 069047/0828 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 16, 2024
From: COOPER, PAUL R.; ELLEFSON, YVONNE N.; FERNANDO, ARLEEN CAMAGANACAN; MASKATIA, IMRAN ARIF; PATTERSON, MATTHEW RYAN; VAN DER STAAY, MATT HENRY; WILLIAMS, CHAD MICHAEL
To: MICROSOFT CORPORATION
Reel/Frame 066477/0051 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 16, 2024
From: MICROSOFT CORPORATION
To: ROVI TECHNOLOGIES CORPORATION
Reel/Frame 066615/0362 →
Continuity (4)
Continuation 17716883 · Apr 8, 2022
Continuation 15972945 · May 7, 2018
Continuation 12719813 · Mar 8, 2010
Related Publication 20240259648A1 · Aug 1, 2024
References Cited (38)
US 5768539A · Metz et al. · 1998 [cited by applicant]
US 6614809B1 · Verma et al. · 2003 [cited by applicant]
US 7209475B1 · Shaffer et al. · 2007 [cited by applicant]
US 7372843B1 · Asawa et al. · 2008 [cited by applicant]
US 9681169B1 · Neill et al. · 2017 [cited by applicant]
US 9934519B2 · Alexander et al. · 2018 [cited by applicant]
US 9967632B2 · Cooper et al. · 2018 [cited by applicant]
US 11323779B2 · Cooper et al. · 2022 [cited by applicant]
US 11936959B2 · Cooper et al. · 2024 [cited by applicant]
US 20010049718A1 · Ozawa · 2001 [cited by applicant]
US 20020099854A1 · Jorgensen · 2002 [cited by applicant]
US 20040120285A1 · Paila et al. · 2004 [cited by applicant]
US 20050204391A1 · Hunleth et al. · 2005 [cited by applicant]
US 20060184973A1 · De et al. · 2006 [cited by applicant]
US 20060212902A1 · Seo et al. · 2006 [cited by applicant]
US 20060291507A1 · Sarosi et al. · 2006 [cited by applicant]
US 20070043847A1 · Carter et al. · 2007 [cited by applicant]
US 20070044130A1 · Skoog · 2007 [cited by applicant]
US 20070050836A1 · Stanek et al. · 2007 [cited by applicant]
US 20070079325A1 · De · 2007 [cited by applicant]
US 20070118866A1 · Chen · 2007 [cited by applicant]
US 20070192810A1 · Pritchett et al. · 2007 [cited by applicant]
US 20070286420A1 · Maclean et al. · 2007 [cited by applicant]
US 20080219268A1 · Dennison · 2008 [cited by applicant]
US 20080285579A1 · Vare et al. · 2008 [cited by applicant]
US 20080301744A1 · Hutchings · 2008 [cited by applicant]
US 20090147804A1 · Wang et al. · 2009 [cited by applicant]
US 20090161678A1 · Huang et al. · 2009 [cited by applicant]
US 20090175294A1 · Orr et al. · 2009 [cited by applicant]
US 20090316709A1 · Polcha et al. · 2009 [cited by applicant]
US 20100034201A1 · Barave et al. · 2010 [cited by applicant]
US 20100053435A1 · Goziker et al. · 2010 [cited by applicant]
US 20100153995A1 · Belz et al. · 2010 [cited by applicant]
US 20100272257A1 · Beals · 2010 [cited by applicant]
US 20110075572A1 · Serbest · 2011 [cited by applicant]
US 20110119546A1 · Ver et al. · 2011 [cited by applicant]
US 20120011224A1 · Casey · 2012 [cited by applicant]
US 20230062943A1 · Cooper et al. · 2023 [cited by applicant]