DECOUPLED CASCADED MIXERS ARCHITECHTURE AND RELATED METHODS
First Claim
1. A method for inter-node signaling in a conferencing network, the method comprising:
- at a first cascaded mixer node;
selecting a plurality of media flow payloads;
generating a set of conference payloads, wherein each conference payload includes media flow payloads from the plurality of media flow payloads that are part of the same conference call, an identifier for the conference call, and a node identifier for each media flow payload in the conference call, wherein each conference payload further identifies for each media flow payload in the conference call whether the first cascaded mixer node is a root node or a leaf node;
bundling the set of conference payloads into a single packet; and
sending the single packet to a second cascaded mixer node.
2 Assignments
0 Petitions
Accused Products
Abstract
Methods for inter-mixer communication enable a “self-formed” cascaded mixer node tree topology. One method enables inter-mixer node signaling and includes first selecting a plurality of media flow payloads at a first cascaded mixer node. A set of conference payloads are generated and each include the media flow payloads from the plurality of media flow payloads that are part of the same conference call, an identifier for the conference call, and a node identifier for each media flow in the conference call. For each media flow in the conference call, each conference payload further identifies whether the first cascaded mixer node is a root node or a leaf node. The set of conference payloads are bundled into a single packet and sent to a second cascaded mixer node. Another method enables the “self-forming” of the mixer node tree topology. Yet another method enables active talker identification within the “self-formed” tree topology.
138 Citations
20 Claims
-
1. A method for inter-node signaling in a conferencing network, the method comprising:
-
at a first cascaded mixer node; selecting a plurality of media flow payloads; generating a set of conference payloads, wherein each conference payload includes media flow payloads from the plurality of media flow payloads that are part of the same conference call, an identifier for the conference call, and a node identifier for each media flow payload in the conference call, wherein each conference payload further identifies for each media flow payload in the conference call whether the first cascaded mixer node is a root node or a leaf node; bundling the set of conference payloads into a single packet; and sending the single packet to a second cascaded mixer node. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A method for building a conference node tree for a conference call, the method comprising:
-
at a first cascaded mixer node of a plurality of cascaded mixer nodes; accepting a request to connect a participant to the conference call; determining that the participant is a first participant to join the conference call; and determining a state of the first cascaded mixer node as either a root node or a leaf node for the conference call; communicating the state of the first cascaded mixer node to the remaining cascaded mixer nodes in the plurality. - View Dependent Claims (9, 10, 11, 12, 13, 14, 15, 16)
-
-
17. A method for a talker identification for a conference call, the method comprising:
-
at a Focus server; receiving a root node report of talker identification events from a first cascaded mixer node, wherein the first cascaded mixer node is a root node for the conference call, wherein the root node report identifies an active talker connected to the root node by RTP IP/port information, and wherein the root node report identifies an active talker connected through a leaf node by one selected from the group consisting of;
a node identifier and a user identifier for a low bit rate/PTT conference; and
a node identifier for a high bit rate conference;receiving a leaf node report of talker identification events from a second cascaded mixer node, wherein the second cascaded mixer node is a leaf node for the conference call, and wherein the leaf node report identifies an active talker by RTP IP/port information, a node identifier, and a user identifier; correlating the root node report to the leaf node report; and based on the correlation, resolving an active talker identity for the conference call. - View Dependent Claims (18, 19, 20)
-
Specification