IP Library Granted Patent US 9,729,497
Granted Patent B2
US 9,729,497 · App. 15/048,480 · Granted Aug 8, 2017

System and method for implementing a subscription-based social media platform

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 9,729,497
App. No.
15/048,480
Granted
Aug 8, 2017
Kind
B2
Abstract

Systems and methods for implementing a subscription-based social media or fan club platform are provided. A content creator generates live content on a mobile device and sends requests to a server for initializing a live stream from the mobile device. The server sends requests to encoding service providers. The encoded live content is send to a content storage server. Subscribers of the social media or fan club platform can access the live content on their mobile devices from the content storage server.

Claims (69)

1. A method for implementing a subscription-based social media platform comprising the steps of:

a server receiving from at least one of a computer and a mobile device of a content creator, a first REpresentational State Transfer (REST) application programming interface (API) request for initializing a live stream from the mobile device, the first REST API request generated by an application running on the mobile device;

the server storing metadata information of the received first REST API request in a database coupled to the server;

the server sending a second REST request to an encoding service provider, the second REST request comprising a request for a plurality of bitrate Real Time Messaging Protocol (“RTMP”) stream configurations;

the server receiving an RTMP protocol location from the encoding service provider;

the server storing RTMP stream information in the database;

the server sending the RTMP protocol location to the mobile device;

the server receiving a first notification from the mobile device that the mobile device has initiated the live stream; and

the server sending a second notification to the database that the mobile device has initiated the live stream.

2. The method of claim 1 , further comprising:

the server determining a plurality of subscribers from users of the social media platform; and

the server sending notifications about the live stream to the plurality of subscribers with privileges to receive the live stream.

3. A method for implementing a subscription-based social media platform comprising the steps of:

a mobile device sending to a server a first REST API request for initializing a live stream, the first REST API request generated by an application running on the mobile device, the first REST API request having metadata information configured to be stored to a database;

the mobile device receiving a second REST protocol location by the server, in response to a request for a plurality of bitrate Real Time Messaging Protocol (“RTMP”) stream configurations;

the mobile device sending a first notification to the server that the mobile device has initiated the live stream;

the mobile device encoding the live stream;

the mobile device generating packets of encoded live stream data from the encoded live stream; and

the mobile device sending the encoded live stream packets to an encoding service provider.

4. The method of claim 3 , further comprising:

the encoding service provider encoding the encoded live stream packets into at least one encoded stream;

the encoding service provider sending the at least one encoded stream to at least one of a content delivery network and an RTMP server;

the server determining a plurality of subscribers with privileges to receive the at least one encoded stream;

the server sending notifications about the at least one encoded stream to the plurality of subscribers with privileges to receive the at least one encoded stream; and

receiving by at least one subscriber mobile device the at least one encoded stream from the at least one of a content delivery network and an RTMP server.

5. The method of claim 4 , wherein the notifications about the at least one encoded stream are PUSH notifications.

6. The method of claim 3 , further comprising:

the encoding service provider encoding the encoded live stream packets into at least one encoded stream;

the encoding service provider sending the at least one encoded stream to at least one of a content delivery network and an RTMP server;

the server receiving a plurality of requests to receive live stream information from a plurality of subscribers;

the server collecting the live stream information from the database, in response to the received plurality of requests;

the server sending the live stream information to the plurality of subscribers; and

enabling access to the plurality of subscribers to the live stream based on the live stream information.

7. The method of claim 6 , wherein the notifications about the at least one encoded stream are PUSH notifications.

8. The method of claim 6 , wherein the live stream information includes at least one of a stream RTMP Universal Resource Location (“URL”) and a m3u8 location.

9. A method for implementing a subscription-based social media platform comprising the steps of:

a server receiving from at least one of a computer and a mobile device of a content creator, a first REpresentational State Transfer (REST) application programming interface (API) request for initializing a live stream from the mobile device, the first REST API request generated by an application running on the mobile device;

the server storing metadata information of the received first REST API request in a database coupled to the server;

the server sending a request for a plurality of bitrate Real Time Messaging Protocol (“RTMP”) stream configurations;

the server receiving an RTMP protocol location from an encoding service provider;

the server storing RTMP stream information in the database;

the server sending the RTMP protocol location to the mobile device;

the server receiving a first notification from the mobile device that the mobile device has initiated the live stream; and

the server sending a second notification to the database that the mobile device has initiated the live stream.

10. The method of claim 9 , further comprising:

the server determining a plurality of subscribers from users of the social media platform; and

the server sending notifications about the live stream to the plurality of subscribers with privileges to receive the live stream.

11. A method for implementing a subscription-based social media platform comprising the steps of:

a mobile device sending to a server a first REST API request for initializing a live stream, the first REST API request generated by an application running on the mobile device, the first REST API request having metadata information configured to be stored to a database;

the mobile device sending a first notification to the server that the mobile device has initiated the live stream;

the mobile device encoding the live stream;

the mobile device generating packets of encoded live stream data from the encoded live stream; and

the mobile device sending the encoded live stream packets to an encoding service provider.

12. The method of claim 11 , further comprising:

the encoding service provider encoding the encoded live stream packets into at least one encoded stream;

the encoding service provider sending the at least one encoded stream to at least one of a content delivery network and an RTMP server;

the server determining a plurality of subscribers with privileges to receive the at least one encoded stream;

the server sending notifications about the at least one encoded stream to the plurality of subscribers with privileges to receive the at least one encoded stream; and

receiving by at least one subscriber mobile device the at least one encoded stream from the at least one of a content delivery network and an RTMP server.

13. The method of claim 12 , wherein the notifications about the at least one encoded stream are PUSH notifications.

14. The method of claim 11 , further comprising:

the encoding service provider encoding the encoded live stream packets into at least one encoded stream;

the encoding service provider sending the at least one encoded stream to at least one of a content delivery network and an RTMP server;

the server receiving a plurality of requests to receive live stream information from a plurality of subscribers;

the server collecting the live stream information from the database, in response to the received plurality of requests;

the server sending the live stream information to the plurality of subscribers; and

enabling access to the plurality of subscribers to the live stream based on the live stream information.

15. The method of claim 14 , wherein the notifications about the at least one encoded stream are PUSH notifications.

16. The method of claim 15 , wherein the live stream information includes at least one of a stream RTMP Universal Resource Location (“URL”) and a m3u8 location.

Assignments (6)
CHANGE OF NAME Recorded Mar 31, 2026
From: ADEIA MEDIA HOLDINGS LLC
To: ADEIA MEDIA HOLDINGS INC.
Reel/Frame 075304/0073 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 25, 2024
From: SGPH, LLC
To: ADEIA MEDIA HOLDINGS LLC
Reel/Frame 067221/0938 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 21, 2023
From: VERTIGO MEDIA, INC.
To: SGPH, LLC
Reel/Frame 064981/0982 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 24, 2023
From: REMOTE MEDIA, LLC
To: VERTIGO MEDIA, INC.
Reel/Frame 062470/0293 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 11, 2016
From: UPFRONT MEDIA GROUP, INC.
To: REMOTE MEDIA, LLC
Reel/Frame 039126/0308 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 13, 2016
From: LEE, RAY; KING, JEFFREY SHAUN; TUSCANO, VINCENT
To: UPFRONT MEDIA GROUP, INC.
Reel/Frame 038583/0624 →