Real-time transport protocol (RTP) media conference server routing engine
First Claim
1. A method for routing RTP (Real-time Transport Protocol) media streams in a standards based Routed RTP Media Conferencing System, the method comprising:
- managing a list of conferences using an RTP Media Conference Routing Engine wherein each conference contains a Conference Profile, a list of participant RTP endpoints with associated participant profiles, and a list of RTP media sessions; and
managing routing of RTP media streams amongst the list of participant RTP endpoints within each conference RTP session according to routing logic algorithms based on data provided by the RTP packet header, the list of RTP session participant RTP endpoints, and a Conference Database within the Routed RTP Media Conferencing System,wherein the RTP media streams can be multiple streams from the same media generator source where at least two streams of a particular media type during a single conference RTP session are encoded with a different format according to the media attributes with the associated conference RTP media session list element and such streams can be properly routed to participant RTP endpoints according to the routing logic and data,wherein the data provided by the RTP packet header to the routing logic algorithms includes the SSRC (Synchronization Source) Identifier, the X (Extension) flag, and the Extension header; and
wherein the RTP media stream includes data in the RTP Extension header that signals the routing logic that the media stream contains composite streams from a participant RTP endpoint performing the services of a media mixing MCU and that the composite streams can be routed to participant devices that are only able to process single media streams.
1 Assignment
0 Petitions
Accused Products
Abstract
The RTP Media Conference Server Routing Engine (“MCSRE”) integrates into a standards based RTP Media Server to improve server data throughput of RTP conference routing by factors of tens to hundreds while simultaneously decreasing real-time media delivery delays and significantly decreasing server resource requirements. The RTP MCSRE maintains a conference routing database used to manage a large number of conferences with a list of associated RTP sessions and conference participants. The routing engine also includes a Conference Session Routing Filter (“CSRF”) and a Routing Logic Processor (“RLP”) that selectively route received media streams to each participant in a given RTP conference. The behavior of both the CSRF and the RLP can be modified by executable scripts. The RTP MCSRE imposes floor control rules and packet filtering with regard to both network bandwidth and hardware resources specific to conference participant endpoint devices.
14 Citations
12 Claims
-
1. A method for routing RTP (Real-time Transport Protocol) media streams in a standards based Routed RTP Media Conferencing System, the method comprising:
managing a list of conferences using an RTP Media Conference Routing Engine wherein each conference contains a Conference Profile, a list of participant RTP endpoints with associated participant profiles, and a list of RTP media sessions; and managing routing of RTP media streams amongst the list of participant RTP endpoints within each conference RTP session according to routing logic algorithms based on data provided by the RTP packet header, the list of RTP session participant RTP endpoints, and a Conference Database within the Routed RTP Media Conferencing System, wherein the RTP media streams can be multiple streams from the same media generator source where at least two streams of a particular media type during a single conference RTP session are encoded with a different format according to the media attributes with the associated conference RTP media session list element and such streams can be properly routed to participant RTP endpoints according to the routing logic and data, wherein the data provided by the RTP packet header to the routing logic algorithms includes the SSRC (Synchronization Source) Identifier, the X (Extension) flag, and the Extension header; and wherein the RTP media stream includes data in the RTP Extension header that signals the routing logic that the media stream contains composite streams from a participant RTP endpoint performing the services of a media mixing MCU and that the composite streams can be routed to participant devices that are only able to process single media streams. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
-
12. A method for managing a series of real time conferences, each compliant with the Real-time Transport Protocol (RTP), the method comprising:
-
maintaining a list of conferences, wherein each conference within the list contains a conference profile including a list of participant RTP endpoints including associated participant profiles, and associated RTP media sessions; routing RTP media streams amongst the list of participant RTP endpoints within each conference based on data provided by the RTP packet header, the RTP Packet header including a synchronization source (SSRC) identifier, an extension (X) flag, and an extension header, the data further including the associated RTP media sessions for the list of participant RTP endpoints; wherein the RTP media streams can be multiple streams from the same media generator source where a least two of the RTP media streams of a particular media type during a single conference RTP session are encoded using different encoding formats dependent upon attributes of a media type being transmitted in the RTP media streams and the participant profiles, the RTP media streams properly routed to appropriate participant RTP endpoints; and wherein the RTP media streams include data in the RTP Extension header that signals the routing logic that the media stream contains composite streams from a participant RTP endpoint performing the services of a media mixing MCU and that the composite streams can be routed to participant devices that are only able to process single media streams.
-
Specification