IP Library Granted Patent US 11,949,945
Granted Patent B2
US 11,949,945 · App. 17/942,909 · Granted Apr 2, 2024

Dynamic creation of low latency video streams in a live event

Inventors: Bo Zhang (Boston, MA); Yuriy Reznik (Seattle, WA)
Assignee: Brightcove Inc.
H04N21/4384H04L67/02H04N21/4402H04N21/8456
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 11,949,945
App. No.
17/942,909
Granted
Apr 2, 2024
Kind
B2
Abstract

A method for creating a low latency DASH (LL-DASH) video stream from a Low latency HLS video stream (LL-HLS) is provided. The LL-HLS video stream corresponding to a live event is retrieved. The LL-HLS video stream is converted to a LL-DASH video stream. This conversion of the LL-DASH stream from the LL-HLS stream provides reformatting without encoding of the LL-DASH stream.

Claims (41)

1. A method for creating low latency video streams corresponding to a live event, the method comprising:

retrieving a first low-latency video stream corresponding to the live event, wherein:

the first low-latency video stream uses a low-latency HTTP live streaming (LL-HLS); and

the first low-latency video stream comprises a first plurality of video chunk files;

converting the first low-latency video stream into a second low-latency video stream, wherein:

the second low-latency video stream uses a low-latency Dynamic Adaptive Streaming over HTTP (LL-DASH);

the converting the first low-latency video stream into a second low-latency video stream comprises:

reformatting without reencoding the first plurality of video chunk files into a second plurality of video chunk files.

2. The method for creating low latency video streams for a live event, as recited in claim 1 , wherein the first low-latency video stream and the second low-latency video stream indicate a delay between receiving the first low latency video stream and the second low-latency video stream and rendering the low latency video streams on a user device.

3. The method for creating low latency video streams for a live event, as recited in claim 1 , wherein the first low-latency video stream comprises a first manifest file and the second low-latency video stream comprises a second manifest file.

4. The method for creating low latency video streams for a live event, as recited in claim 1 , wherein the LL-HLS stream is used by a plurality of user devices.

5. The method for creating low latency video streams for a live event, as recited in claim 3 , wherein the LL-HLS stream uses the first manifest file called m3u8 file.

6. The method for creating low latency video streams for a live event, as recited in claim 5 , wherein the m3u8 file describes the LL-HLS stream.

7. A system for creating a low latency video streams for a live event, the system comprising:

a low-latency HLS converter configured to retrieve a first low-latency video stream corresponding to the live event, wherein:

the first low-latency video stream uses a low-latency HTTP live (streaming (LL-HLS) format; and

the first low-latency video stream comprises a first plurality of video chunk files; and

a LL-HLS to LL-DASH converter configured to convert the first low-latency video stream into a second low-latency video stream, wherein:

the second low-latency video stream uses a low-latency Dynamic Adaptive Streaming over HTTP (LL-DASH) stream;

the converting the first low-latency video stream into a second low-latency video stream comprises:

reformatting without reencoding the first plurality of video chunk files into a second plurality of video chunk files.

8. The system for creating low-latency video streams for the live event, as recited in claim 7 , wherein the first low-latency video stream and the second low-latency video stream indicate a delay between receiving the first low-latency video stream and the second low-latency video stream and rendering the low-latency video streams on a user device.

9. The system for creating low-latency video streams for a live event, as recited in claim 7 , wherein the first low-latency video stream comprises a first manifest file and the second low-latency video stream comprises a second manifest file.

10. The system for creating low-latency video streams for the live event, as recited in claim 7 , wherein the LL-HLS stream is used by a plurality of user devices.

11. The system for creating low latency video streams for the live event, as recited in claim 9 , wherein the LL-HLS stream uses the first manifest file called m3u8 file.

12. The system for creating low latency video streams for the live event, as recited in claim 11 , wherein the m3u8 file describes the LL-HLS stream.

13. The system for creating low latency video streams for the live event, as recited in claim 12 , wherein the conversion is performed by converting the m3u8 file of the LL-HLS stream to a metadata file, called the Media Presentation Description (MPD) file for the LL-DASH stream.

14. A non-transitory computer-readable medium having instructions embedded thereon for creating low latency video streams for a live event, wherein the instructions, when executed by one or more computers, cause the one or more computers to:

retrieving a first low-latency video stream corresponding to the live event, wherein:

the first low-latency video stream uses a low-latency HTTP live streaming (LL-HLS); and

the first low-latency video stream comprises a first plurality of video chunk files;

convert the first low-latency video stream into a second low-latency video stream, wherein:

the second low-latency video stream uses a low-latency Dynamic Adaptive Streaming over HTTP (LL-DASH) stream;

the converting the first low-latency video stream into the second low-latency video stream comprises:

reformatting without reencoding the first plurality of video chunk files into a second plurality of video chunk files.

15. The non-transitory computer-readable medium as recited in claim 14 , wherein the first low-latency video stream and the second low-latency video stream indicate a delay between receiving the first low-latency video stream and the second low-latency video stream and rendering the low latency video streams on a user device.

16. The non-transitory computer-readable medium as recited in claim 14 , wherein the first low-latency video stream comprises a first manifest file and the second low-latency video stream comprises a second manifest file.

17. The non-transitory computer-readable medium as recited in claim 14 , wherein the LL-HLS stream is used by a plurality of user devices.

18. The non-transitory computer-readable medium as recited in claim 16 , wherein the LL-HLS stream uses the first manifest file called m3u8 file.

19. The non-transitory computer-readable medium as recited in claim 18 , wherein the m3u8 file describes the LL-HLS stream.

20. The non-transitory computer-readable medium as recited in claim 19 , wherein the conversion is performed by converting the m3u8 file of the LL-HLS stream to a metadata file, called the Media Presentation Description (MPD) file for the LL-DASH stream.

Assignments (4)
PATENT SECURITY AGREEMENT Recorded Jun 12, 2025
From: BRIGHTCOVE INC.
To: INTESA SANPAOLO S.P.A., AS SECURITY AGENT
Reel/Frame 071575/0646 →
CORRECTIVE ASSIGNMENT TO CORRECT THE THE SECOND INVENTORS NAME PREVIOUSLY RECORDED AT REEL: 061215 FRAME: 0427. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Nov 30, 2023
From: ZHANG, BO; REZNIK, YURITY
To: BRIGHTCOVE, INC.
Reel/Frame 065723/0787 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 4, 2022
From: ZHANG, BO; REZNIK, YURIY
To: BRIGHTCOVE, INC.
Reel/Frame 061305/0115 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 26, 2022
From: ZHANG, BO; RENZNIK, YURIY
To: BRIGHTCOVE, INC.
Reel/Frame 061215/0427 →