Systems and methods for shared broadcasting
US-10674187-B2 · Jun 2, 2020 · US
US11425439B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11425439-B2 |
| Application number | US-201615736654-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jun 15, 2016 |
| Priority date | Jun 15, 2015 |
| Publication date | Aug 23, 2022 |
| Grant date | Aug 23, 2022 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A system for providing streaming services. The system includes a plurality of users each for generating a stream of an event on a connection of a public network. The system also includes a server configured to receive a plurality of the generated streams, determine content for at least one output stream, and output the at least one output stream on a connection of a public network, with at least one user receiving the at least one output stream. The content is determined based on one or more of content received from input streams, content requested by a viewer, and the user profiles of the contributors.
Opening claim text (preview).
The invention claimed is: 1. A system for providing a streaming services platform, the system comprising: a plurality of capture devices each comprising one or more applications and/or one or more products, each application and/or product for generating a media stream on a connection of a public network; and a server for receiving the generated media streams on the connection of the public network and for generating at least one output stream on a connection of the public network, the server configured such that each individual generated media stream is allocated to an event in accordance with its metadata, and the server configured to receive a request for a new event from an event owner, wherein in response to the request from the event owner: metadata for the new event is submitted to a grouping service; any existing streams overlapping with the new event are identified based on the metadata for the new event, wherein if any overlapping streams are identified, then the server is further configured to: retrieve a list of the overlapping streams; send the retrieved list of overlapping streams to the event owner of the new event; wait for the event owner of the new event to select the identified overlapping streams to invite; and send an invitation to owners of the selected overlapping streams to join the new event, and any existing events overlapping with the new event are identified based on the metadata for the new event, wherein if any existing overlapping events are identified the server is configured to: retrieve a list of overlapping events; send the list of overlapping events to the event owner of the new event; wait for the event owner of the new event to select the identified overlapping streams to invite to merge; and send an invitation to owners of the selected overlapping events to merge with the new event. 2. The system of claim 1 wherein the server includes: an aggregated API comprising an aggregation of services for each application and/or product of each of the plurality of capture devices, configured to: manage metadata of the platform and interface with a collection of services contributing to the aggregated API; to authenticate or authorize, or both authenticate and authorize, each input media stream; to provide functionality associated with streaming services; and to receive using requests for one or more streams such that the aggregated API is responsible for the management and control of services, features, and functionalities; and a media gateway configured to manage the flow of media from receipt of the input media streams, and to generate the at least one output stream, such that the media gateway is responsible for the flow of various data between the collection of services. 3. The system of claim 2 wherein the media gateway is configured to receive data, metadata, and data with embedded metadata. 4. The system of claim 3 further comprising an aggregated API, and wherein the media gateway is further configured to process one of streamed time dependent data and metadata and the API is configured to process control related data, derived from the metadata, which is not time dependent. 5. The system of claim 3 further comprising an aggregated API, and wherein a request from a user is received by the API, and the request defines rules which are applied to the media gateway and the individual generated media streams that come into it. 6. The system of claim 5 wherein rights holders can create rules that one or both of instruct the server to store content and assign rights to the individual generated media streams. 7. The system of claim 2 , wherein the server is configured, on determination of provision of one of an invitation key and a password with the individual generated media stream, to join the individual generated media stream to an associated event. 8. The system of claim 1 wherein: if it is determined that an individual generated media stream is associated with an existing event, the individual generated media stream is allocated to the existing event, and the metadata for the existing event is updated, and if it is determined that the individual generated media stream is not associated with an existing event, then metadata for a new event is created and the individual generated media stream is associated with the new event such that the created new event comprises one generated media stream. 9. The system of claim 8 wherein allocating the individual generated media stream to an existing event is dependent upon initially identifying a plurality of potential events. 10. The system of claim 9 wherein the server is further configured to subsequently receive a selection from a user associated with the individual generated media stream allocated to one of the events, and join the allocated media stream to the event. 11. The system of claim 10 wherein if the user does not select an event, the server is further configured to subsequently create a new event. 12. The system of claim 8 wherein allocating the individual generated media stream to an event is dependent upon determining if the generated media stream is allowed to join the event. 13. The system of claim 12 wherein if the individual generated media stream is not allowed to join an event, the server is further configured to create a new event. 14. The system of claim 8 wherein if the individual generated media stream is added to an event, existing event members providing input streams to the event are notified. 15. The system of claim 1 wherein the server is further configured to determine of any of the overlapping events are rights holder events, and if so to filter those rights holder events and notify the owner associated with an overlapping stream that the event may be subject to rights restrictions, and add the new event to moderation queues for each possible rights holder event. 16. The system of claim 1 wherein the server is further configured to determine if the event owner is a rights holder, and if so: creating a moderation queue for the event; submitting the event to a metadata grouping service; and identifying any potentially infringing streams or events, wherein if potentially infringing streams or events are identified, then: notifying the owner associated with the potentially infringing streams or events that the content may be subject to rights restrictions; and adding the potentially infringing streams or events to the moderation queue. 17. The system of claim 1 wherein when the individual generated media stream includes a request to join an identified existing event, the server is configured to: retrieve details of the identified, existing event; and determine if the individual generated media stream is allowed to join the identified, existing event; responsive to the user not being allowed to join the identified, existing event, notify the use of rejection of the request to join the existing event; responsive to the user being allowed to join the identified, existing event: update the metadata of the identified, existing event by adding the individual generated media stream; notify the media gateway of the change to the identified, existing event; notify any members of the identified, existing event of the addition of the individual generated media stream; and deliver the identified, existing event to members based on media streams allocated to that event, including the newly added individual generated media stream. 18. A method for providing a streaming services platform, the method comprising: g
Monitoring of the downstream path of the transmission network, e.g. bandwidth available (traffic monitoring in data switching networks H04L43/00; monitoring data switching networks utilization H04L43/0876) · CPC title
Monitoring of transmitted content, e.g. distribution time, number of downloads (arrangements for monitoring programmes for broadcast or for distribution combined with broadcast H04H20/14) · CPC title
involving operations for analysing video streams, e.g. detecting features or characteristics (television picture signal circuitry for scene change detection H04N5/147; filtering for image enhancement G06T5/00; methods or arrangements for recognising scenes G06V20/00; arrangements characterised by components specially adapted for monitoring, identification or recognition of video in broadcast systems H04H60/59) · CPC title
of multiple content streams on the same device · CPC title
Cameras (H04N23/00 takes precedence) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.