IP Library Granted Patent US 11,394,809
Granted Patent B2
US 11,394,809 · App. 16/911,297 · Granted Jul 19, 2022

System and method for continuous tracking of media playback using blockchain

Inventors: Pouria Assadipour (Burnaby, CA); Andrew Batey (Vancouver, CA); Morgan Hayduk (Vancouver, 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 11,394,809
App. No.
16/911,297
Granted
Jul 19, 2022
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 (37)

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;

recording streaming data corresponding to which segments of the media file or media stream have been transmitted to the user device, the streaming data including current play positions of the media file or the media stream in multiple intervals;

transmitting the request and recorded streaming data for recording on a blockchain; and

determining that the request qualifies as a play count only if the streaming data recorded on the blockchain includes a plurality of current play positions that demonstrates that the media file has been streaming for a predetermined threshold duration of time.

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;

recording streaming data corresponding to which segments of the media file or media stream have been transmitted to the user device, the streaming data including current play positions of the media file or the media stream in multiple intervals;

transmitting the request and recorded streaming data for recording on a blockchain; and

determining that the request qualifies as a play count only if the streaming data recorded on the blockchain includes a plurality of current play positions that demonstrates that the media file has been streaming for a predetermined threshold duration of time.

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;

recording streaming data corresponding to which segments of the media file or media stream have been transmitted to the user device, the streaming data including current play positions of the media file or the media stream in multiple intervals;

transmitting the request and recorded streaming data for recording on a blockchain; and

determining that the request qualifies as a play count only if the streaming data recorded on the blockchain includes a plurality of current play positions that demonstrates that the media file has been streaming for a predetermined threshold duration of time.

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 Jun 30, 2020
From: ASSADIPOUR, POURIA; BATEY, ANDREW; HAYDUK, MORGAN
To: BEATDAPP SOFTWARE, INC.
Reel/Frame 053084/0538 →
Continuity (4)
Continuation In Part 16586876 · Sep 27, 2019
Continuation In Part 16557941 · Aug 30, 2019
Continuation 16457663 · Jun 28, 2019
Related Publication 20200412819A1 · Dec 31, 2020
Cited By (1)
US 12,684,047