IP Library Granted Patent US 12,289,381
Granted Patent B2
US 12,289,381 · App. 17/868,516 · Granted Apr 29, 2025

System and method for continuous tracking of media playback using blockchain

Inventors: Pouria Assadipour (Burnaby, CA); Andrew Batey (Vancouver, CA); Morgan Hayduk (Toronto, CA)
Assignee: Beatdapp Software, Inc.
H04L67/535H04L65/612H04L67/1097
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,289,381
App. No.
17/868,516
Granted
Apr 29, 2025
Kind
B2
Abstract

Systems and methods for continuous tracking of media file playback. First, transaction data from a platform stream is received. The transaction data corresponds to a request to play a media file from an end user, as well as continuous play information. Next, the transaction data is verified. Then, the verified transaction data is signed using a cryptographic signature. Next, it is determined whether the transaction data corresponds to a valid blockchain transaction. If the transaction data corresponds to a valid blockchain transaction, the valid blockchain transaction is recorded to a blockchain. Last, the transaction data and the cryptographic signature are transmitted to one or more validation nodes.

Claims (34)

1. A system for continuous tracking of media file or media stream playback via a blockchain based platform, the system comprising:

a processor; and

memory, the memory storing instructions to cause a processor to execute a method, the method comprising:

receiving a user initiated request to play a media file or media stream via an application;

transmitting segments of the media file or media stream to a user device;

transmitting the request and streaming data for recording on a blockchain, the streaming data corresponding to which segments of the media file or media stream have been transmitted to the user device; and

determining that the request is not considered a valid request unless the streaming data corresponds to streaming the media file or media stream for a predetermined threshold duration of time and the request is validated by the blockchain.

2. The system of claim 1 , wherein the request includes one or more of the following: a media file or media stream name, a rights holder name, and metadata associated with the media file or the media stream.

3. The system of claim 1 , wherein any request to play more content must specify which part of the content needs to be streamed.

4. The system of claim 1 , wherein any requests to play more content is signed by a user's private key.

5. The system of claim 1 , wherein the request includes reference data to the media file or media stream, the reference data being signed by a user's private key.

6. The system of claim 5 , wherein the reference data is a unique identifier of the media file or media stream.

7. The system of claim 1 , wherein the request is transmitted to the platform stream along with signatures and a user public key.

8. A method for continuous tracking of media file or media stream playback via a blockchain platform, the method comprising:

receiving a user initiated request to play a media file or media stream via an application;

transmitting segments of the media file or media stream to a user device;

transmitting the request and streaming data for recording on a blockchain, the streaming data corresponding to which segments of the media file or media stream have been transmitted to the user device; and

determining that the request is not considered a valid request unless the streaming data corresponds to streaming the media file or media stream for a predetermined threshold duration of time and the request is validated by the blockchain.

9. The method of claim 8 , wherein the request includes one or more of the following: a media file or media stream name, a rights holder name, and metadata associated with the media file or the media stream.

10. The method of claim 8 , wherein any request to play more content must specify which part of the content needs to be streamed.

11. The method of claim 8 , wherein any requests to play more content is signed by a user's private key.

12. The method of claim 8 , wherein the request includes reference data to the media file or media stream, the reference data being signed by a user's private key.

13. The method of claim 12 , wherein the reference data is a unique identifier of the media file or media stream.

14. The method of claim 8 , wherein the request is transmitted to the platform stream along with signatures and a user public key.

15. A non-transitory computer readable medium storing instructions to execute a method, the method comprising:

receiving a user initiated request to play a media file or media stream via an application;

transmitting segments of the media file or media stream to a user device;

transmitting the request and streaming data for recording on a blockchain, the streaming data corresponding to which segments of the media file or media stream have been transmitted to the user device; and

determining that the request is not considered a valid request unless the streaming data corresponds to streaming the media file or media stream for a predetermined threshold duration of time and the request is validated by the blockchain.

16. The non-transitory computer readable medium of claim 15 , wherein the request includes one or more of the following: a media file or media stream name, a rights holder name, and metadata associated with the media file or the media stream.

17. The non-transitory computer readable medium of claim 15 , wherein any request to play more content must specify which part of the content needs to be streamed.

18. The non-transitory computer readable medium of claim 15 , wherein any requests to play more content is signed by a user's private key.

19. The non-transitory computer readable medium of claim 15 , wherein the request includes reference data to the media file or media stream signed, the reference data being by a user's private key.

20. The non-transitory computer readable medium of claim 19 , wherein the reference data is a unique identifier of the media file or media stream.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 19, 2022
From: ASSADIPOUR, POURIA; BATEY, ANDREW; HAYDUK, MORGAN
To: BEATDAPP SOFTWARE INC.
Reel/Frame 061283/0518 →
Continuity (5)
Continuation 16911297 · Jun 24, 2020
Continuation In Part 16586876 · Sep 27, 2019
Continuation In Part 16557941 · Aug 30, 2019
Continuation 16457663 · Jun 28, 2019
Related Publication 20220353346A1 · Nov 3, 2022
References Cited (45)
US 9122844B2 · Trimper · 2015 [cited by examiner]
US 10469605B1 · Batey et al. · 2019 [cited by applicant]
US 10600009B1 · Augustine · 2020 [cited by examiner]
US 11381653B2 · Assadipour et al. · 2022 [cited by applicant]
US 11503132B2 · Assadipour et al. · 2022 [cited by applicant]
US 11606426B1 · Cascioli et al. · 2023 [cited by applicant]
US 20030018931A1 · Ueda · 2003 [cited by examiner]
US 20080010372A1 · Khedouri et al. · 2008 [cited by applicant]
US 20130042298A1 · Plaza et al. · 2013 [cited by applicant]
US 20130326569A1 · Kuo · 2013 [cited by examiner]
US 20160196105A1 · Vartakavi · 2016 [cited by examiner]
US 20170116693A1 · Rae · 2017 [cited by examiner]
US 20170147830A1 · Park et al. · 2017 [cited by applicant]
US 20180039942A1 · Rogers et al. · 2018 [cited by applicant]
US 20180352268A1 · O'hanlon et al. · 2018 [cited by applicant]
US 20190020480A1 · Camenisch et al. · 2019 [cited by applicant]
US 20190057115A1 · Liu et al. · 2019 [cited by applicant]
US 20190215564A1 · Webb · 2019 [cited by examiner]
US 20190215565A1 · Webb · 2019 [cited by examiner]
US 20200052917A1 · Corral · 2020 [cited by examiner]
US 20200137440A1 · Zavesky · 2020 [cited by examiner]
US 20200250683A1 · Padmanabhan et al. · 2020 [cited by applicant]
US 20220337674A1 · Assadipour et al. · 2022 [cited by applicant]
US 20230083052A1 · Assadipour et al. · 2023 [cited by applicant]
CN 109102272A · 2018 [cited by applicant]
MX 2021001757 · 2022 [cited by applicant]
WO 2018142948A1 · 2018 [cited by applicant]
WO WO2020037139A1 · 2020 [cited by examiner]
U.S. Appl. No. 18/054,865, USPTO e-Office Action: CTNF—Non-Final Rejection, May 11, 2023, 8 pages. [cited by applicant]
Canadian Office Action, Applicatin No. 3,107,813, mailed Nov. 3, 2022, 4 pages. [cited by applicant]
Information Processing Society of Japan Journal, vol. 60, pp. 130-146, dated Jan. 15, 2019. [cited by applicant]
Int'l Application No. PCT/US20/43593, IPRP mailed 1/5/236 pgs. [cited by applicant]
Japanese Office Action, Application No. 2021-50569, dated Apr. 5, 2023, 8 pages. [cited by applicant]
Japanese Office Action, Rejection Notice, Application No. 2021-506397, dated Jan. 10, 2023, 13 pages. [cited by applicant]
U.S. Appl. No. 17/857,979, USPTO e-Office Action: CTNF—Non-Final Rejection, Nov. 29, 2023, 10 pages. [cited by applicant]
U.S. Appl. No. 18/054,865, USPTO e-Office Action: CTFR—Final Rejection, Aug. 31, 2023, 7 pages. [cited by applicant]
Candian Office Action, dated Aug. 25, 2023, CA Application No. 3,107,813, 3 pages. [cited by applicant]
European Examination Report, dated Oct. 31, 2023, for Application No. EP19935654.4, 7 pages. [cited by applicant]
U.S. Appl. No. 17/857,979, USPTO e-Office Action: NOA—Notice of Allowance And Fees Due (Ptol-85), Jul. 22, 2024, 7 pages. [cited by applicant]
U.S. Appl. No. 18/054,865, USPTO e-Office Action: CTFR—Final Rejection, Jun. 21, 2024, 7 pages. [cited by applicant]
U.S. Appl. No. 18/054,865, USPTO e-Office Action: CTNF—Non-Final Rejection, Feb. 1, 2024, 6 pages. [cited by applicant]
Communication pursuant to Article 94(3) for European Application No. 20842546.2, dated Jul. 11, 2024, 5 pgs. [cited by applicant]
First Office Action for Mexican Application No. MX/a/2021/001757, dated Jun. 19, 2024, 3 pgs. [cited by applicant]
First Office Action for Mexican Patent Application No. MX/a/2021/001759, dated Jul. 24, 2024, 10 pgs. [cited by applicant]
Rejection notice for JP Application No. 2023126656, dated Oct. 1, 2024, 12 pgs. [cited by applicant]