Audio conferencing utilizing packets with unencrypted power level information

TECHNICAL FIELD

0001The present disclosure relates to the field of audio transmissions over a communications network.

BACKGROUND

0002Modem conferencing systems facilitate communications among multiple participants over telephone lines, Internet protocol (IP) networks, and other data networks. The use of conferencing systems is becoming more prevalent, especially as the cost of transmissions over IP networks has dropped. As usage has increased, the number of participants that attend a given conference has also increased. One consequence is that audio mixers must now be capable of processing a large number of Real-Time Protocol (RTP) audio packet streams from the various participants to a given conference. This increase in the number of packet streams input to the audio mixer (or bridge) results in an increase in the number of computations and processing steps that must be performed. The increased number of conference participants also increases the overall noise that is sent to the audio mixer.

0003Many conferencing mixers are configured to identify and mix only the loudest few speakers participating in discussions during a conference session. By discarding or ignoring all but the loudest streams, conference quality is improved due to the elimination of extraneous noise in the audio mix. In a typical secure conferencing application, however, the audio mixer is required to first decrypt the Secure Real-Time Protocol packet (SRTP) packets received, and then partially or fully decode all of the audio payloads of each incoming stream before determining the average power level of each stream. Even in a regular RTP application with no encryption, the average power level must still be computed. Once the streams have been decrypted, decoded, and the audio power levels determined, the mixer must then compare all of the audio streams to determine the loudest speakers. For relatively large conferences where numerous RTP streams are input to the audio mixer this is a highly computer-intensive process that can overwhelm the processing capacity and bandwidth of the audio mixer.

0004<patcit id="pcit0001" dnum="US20060146735A1"><text>US-A1-2006/0146735</text></patcit> describes a method and system for providing a conference service using speaker selection, wherein a plurality of media streams received from a plurality of end points each include a power indicator.

0005Aspects of the invention are set out in the independent claims and preferred features are set out in the dependent claims.

BRIEF DESCRIPTION OF THE DRAWINGS

0006The present invention will be understood more fully from the detailed description that follows and from the accompanying drawings, which however, should not be taken to limit the invention to the specific embodiments shown, but are for explanation and understanding only.

0007<figref idref="f0001"><b>Figure 1</b></figref> illustrates an example conferencing system with multiple endpoints.

0008<figref idref="f0002"><b>Figure 2</b></figref> illustrates an example audio packet that contains power level and time base information sent to the audio mixer.

0009<figref idref="f0003"><b>Figure 3</b></figref> illustrates an example operation wherein incoming audio streams from multiple endpoints are mixed, with the mixed output streams sent to the endpoints.

0010<figref idref="f0004"><b>Figure 4</b></figref> illustrates an example method for performing computations on audio communications to be sent over a network by an endpoint device.

0011<figref idref="f0005"><b>Figure 5</b></figref> illustrates an example method for mixing audio packet streams from multiple conference participants.

0012<figref idref="f0006"><b>Figure 6</b></figref> illustrates an example format of a SRTP packet with an RTP extension that includes unencrypted power level and time base information.

DESCRIPTION OF EXAMPLE EMBODIMENTS

0013In the following description specific details are set forth, such as device types, system configurations, protocols, applications, methods, etc., in order to provide a thorough understanding of the present invention. However, persons having ordinary skill in the relevant arts will appreciate that these specific details may not be needed to practice the present invention.

0014<figref idref="f0001">Figure 1</figref> illustrates an example conferencing system 10 with multiple endpoints 14, 16 and 18. Each of the endpoints is shown connected with a conferencing server 12 and a mixer 13 via Internet Protocol (IP) network 11. In this example, endpoints 14, 16 and 18 are sources and receivers of audio content - that is, they send audio from their microphones to an audio mixer 13, and receive back a customized mixed audio stream. The endpoint devices are shown comprising personal computers (PCs) 14 with softphone capabilities for placing/receiving calls, voice over IP (VoIP) phones 16, and a conventional telephone device 16 connected to a Public Switched Telephone Network (PSTN) line that communicates with IP network 11 via a voice VoIP gateway 17. Each of endpoint devices 14-16 and VoIP gateway 17 includes a processor and executable code that supports the functionality described below. Other endpoint devices not specifically shown in <figref idref="f0001">Figure 1</figref> that may be used to initiate or participate in a conference session include a personal digital assistant (PDA), a laptop or notebook computer, or any other device, component, element, or object capable of initiating or participating in voice or packet-data exchanges with system 10 in accordance with the protocols and methods described herein.

0015Conferencing server 12 may comprise a conferencing or meeting scheduling system application that includes software (or firmware) plug-ins, modules, or enhancements that implement the various features and functions described herein. In a specific implementation, for example, conferencing server 12 may run a modified or enhanced IP communication system software product such as Cisco's MeetingPlace™ conferencing application that allows users to schedule and attend meeting conferences. In the embodiment shown, conference server 12 handles all of the control plane functions of the conference session and manages audio transmissions and communications from the endpoints.

0016Mixer 13 is coupled to conferencing server 12 and is responsible for receiving audio packet streams from the plurality of endpoints, processing and mixing the streams and sending back to the plurality of endpoints a mixed stream. It should be further understood that audio mixer 13 represents any device or component that combines more than one audio input stream to produce a composite audio output stream. By way of example, mixer 13 may include a digital signal processor (DSP) or firmware/software-based system that mixes and/or switches audio (and possibly video) signals received at its input ports under the control of conferencing server 12. It should be further understood that conference server 12 and mixer 13 comprise logical entities which may be implemented on a single hardware unit or box.

0017The audio signals received at the conference server ports originate from each of the conference or meeting participants (e.g., individual conference participants using endpoint devices 14, 16 and 18) and possibly from an interactive voice response (IVR) system (not shown). Conference server 12 may also incorporate or be associated with a natural language automatic speech recognition (ASR) module for interpreting and parsing speech of the participants, as well as standard speech-to-text (STT) and text-to-speech (TTS) converter modules. It should be understood that in some embodiments, mixer 13 and server 12 may be combined or incorporated in a single unit.

0018Practitioners in the art will appreciate that the actual media paths to the endpoint devices are normally established by conferencing server 12. In other words, conferencing server 12 is responsible for engaging the necessary media components / resources to satisfy the media requirements of each of the endpoints participating in a given conference session. In operation, each of the endpoint devices shown in <figref idref="f0002">Figure 2</figref> may join a conference session by calling into a conferencing application running on conferencing server 12.

0019In the example of <figref idref="f0001">Figure 1</figref>, normalized audio power level data across multiple frequency bands is stored in an unencrypted portion of the audio packets received at mixer 13. This means that the audio power level information of each stream is directly accessible without the need for packet decryption such that the mixer can readily determine which audio packet streams comprise the N (where N is an integer) loudest speakers. Mixer 13 decrypts the audio streams of the N loudest speakers and discards the remaining input streams. After mixing, the resulting audio streams are output back to the various endpoint devices. It is appreciated that different endpoints may receive different output audio streams from mixer 13. For instance, a participant who is one of the N loudest speakers is normally sent a stream that includes the other (N-1) loudest speakers, but does not include his own speech.

0020The audio power level data included in the audio packet streams is generated by the encoder normally associated with each of endpoint devices 14, 16 and VoIP gateway 17. According to one embodiment, during processing of the audio input received at each endpoint, a moving average of the normalized power levels of the audio input at multiple frequencies is computed and included or embedded within the audio packets. The multiple frequencies represent different types of audio input and are subsequently used by mixer 13 to distinguish which audio packets represent speech. The multi-frequency power level information also allows mixer 13 to quickly assess and compare the incoming audio packets to determine which streams contain the loudest speech. The encoder associated with each endpoint may also include timebase information used to obtain or generate the moving average.

0021In another embodiment, packets of each of the multiple audio streams generated by the various endpoints include header and payload portions, the header portion containing audio power level information that includes power levels for each of a respective plurality of frequencies. The header portion may or may not include portions that are encrypted. The audio power level information contained in the packets of each of the packet streams is compared by the mixer to select N, where N is an integer greater than or equal to one, packet streams having the loudest speech. The mixer decodes the N packet streams to obtain the audio content contained in the payload portion of each of the N packet streams. The mixer then mixes the audio content of the N packet streams to produce one or more output packet streams.

0022<figref idref="f0002">Figure 2</figref> illustrates an example audio packet 20 that contains power level and timebase information sent by an endpoint device to the audio mixer. It should be understood that any transport protocol consistent with the general packet format shown in <figref idref="f0002">Figure 2</figref> may be used for the audio stream communications from the individual endpoints to mixer 13. Packet 20 includes a header section 21, a header extension section 22, and a payload section 25, the latter including the encrypted and encoded audio media content. Header 21 provides information to the mixer regarding the type and name of the packet being sent, the type, name and format of the payload, and other identifier information, such as a timestamp or source and destination location. Header extension 22 includes normalized power level and timebase information (represented by ellipses 24 and 23, respectively) of the audio communication produced at the corresponding endpoint. In one embodiment, the normalized power level and timebase information may be transported as an extension to known RTP payload specifications such as G.711, G.729, G.723, etc. Alternatively, the power level and time base information may be carried in a separate but related payload type.

0023In one embodiment, normalized power level information 24 comprises a current moving average of the normalized power level at a small number of key frequencies. By transporting multi-frequency power level information the audio mixer can readily distinguish between loud speech and loud noise (e.g., wind, heavy breathing, machinery, etc.) Timebase information 23 provides a timebase from which the moving average may be computed. Timebase information 23, as well as normalized power level information 24 included in header extension 22, is unencrypted and independent of the specific payload content in packet section 25.

0024Practitioners in the art will appreciate that the normalized power level information may be computed by the endpoint in the course of encoding the RTP packet. Upon receiving packet 20, audio mixer 13 may determine the normalized power levels at the various frequencies without having to decrypt the packet. Using a standard algorithm, the N loudest speakers may then be computed based on the normalized power level information obtained from all of the incoming streams. Once the streams having the N loudest speakers have been identified, mixer 13 may discard the other remaining RTP audio packet streams without decoding or decrypting them.

0025In another embodiment, the audio mixer sends back a RTP Control Protocol (RTCP) receiver report to adjust the time base of the moving average computation. This enhancement allows the mixer to control the sensitivity of the stream selection process, e.g., avoiding transient voice spikes on the input RTP streams.

0026<figref idref="f0006">Figure 6</figref> illustrates an example format of an SRTP packet 60 that includes a RTP extension 64 into which is placed the multi-frequency power level and timebase information. Note that the unencrypted portion of packet 60 includes the time stamp 61, the synchronization source identifier (SSRC) 62, the contributing source identifier (CSRC) 63 and RTP extension 64. The SSRC 62 identifies the immediate source of the packet stream. If the RTP stream has been previously mixed or modified, the CSRC 63 identifies the original sources of the RTP streams that now comprise the current stream. In one embodiment, the multi-frequency power level and timebase information is intentionally placed into RTP extension 64 so that it remains unencrypted and unencoded. The encrypted portion 68 of packet 60 includes the payload 65 (including RTP padding and pad count, when present), SRTP Master Key Identifier (MKI) 66 and the authentication tag 67.

0027Payload 65 contains the actual audio media content, converted into the appropriate format for the conferencing mixer. In one embodiment, SRTP packet 60 may be any one of a number of payload types, such as G.711, G.729, iLBC, G.722, etc. The information to be included within RTP extension 64 is not specific to a particular payload and no additional information is required to be included in encrypted portion 68 of SRTP packet 60.

0028<figref idref="f0003">Figure 3</figref> illustrates an example operation wherein incoming audio streams 31a-31x originating from corresponding endpoints 30a-30x are mixed, with the mixed output streams being sent back to the endpoints. Mixer 36 receives a plurality of packets 32 associated with each stream 31. The packets originate from the endpoints participating in the conference session. An encoder associated with or incorporated into each endpoint changes the audio communications contained within packets 32 into a format readable by mixer 36. Each packet contains, in part, audio communications that have been encrypted and encoded. Each packet also contains normalized power levels represented in <figref idref="f0003">Figure 3</figref> by boxes or bins 34a-34m. Each box represents a normalized power level (NPL) taken at a different, discrete frequency. The encoder inputs the normalized power levels during the same process of encoding the audio communications. Upon arrival, the normalized power levels at the various frequencies in the unencrypted portion of the incoming packets of each stream 31 are examined by mixer 36. This frequency bin information may be used by mixer 36 to distinguish a participant's speech from background noise. For instance, during the course of a conference there are many background noises (e.g., from cars, construction, wind, etc.) that can interfere with the communication between the participants. Sometimes, these background noises can actually be louder than the participant's speech.

0029Mixer 36 compares the packets that have the highest power levels at certain specified frequencies, i.e., those frequencies that correspond to human speech. Mixer 36 may quickly perform this comparison by examining the unencrypted header extension portion of the packet. In one embodiment, mixer 36 is capable of selecting up to N (where N is an integer) loudest packet streams, as specified by the conferencing server or as specified within the mixer itself. All the remaining, unselected packets are discarded without any decryption or decoding. Mixer 36 only decrypts and decodes the selected N packet streams. From the decrypted and decoded N streams, mixer 36 generates customized mixed output audio streams (e.g., shown in <figref idref="f0003">Figure 3</figref> as output streams 1, 2 ... N+1) that are then sent back to the endpoint devices of the conference.

0030Practitioners will appreciate that the output stream generated for a participant who currently is one of the loudest N speakers typically does not include that participant's speech. In other words, the customized stream generated for that participant will differ from the output stream send to the other participants. There are therefore N customized streams produced for the N loudest speakers, plus one additional stream containing a mix of all speakers, to be sent to all participants who are not currently one of the loudest speakers.

0031<figref idref="f0004">Figure 4</figref> illustrates an example method for performing computations on audio communications to be sent over a network by an endpoint device. The process begins with the encoder of an endpoint device performing multi-frequency power level computations on the audio communications received (e.g., from a microphone) during a conference session (block 41). After performing the multi-frequency power level computations on the received audio, the endpoint device encoder next computes a moving average of the normalized power levels at certain key frequencies, i.e., those frequencies that correspond to human speech. This step is shown by block 42 in <figref idref="f0004">Figure 4</figref>. Once the moving average values have been computed at the key frequencies, the results are transported to the mixer in an unencrypted portion of the packet (block 43). Note that timebase information utilized in the computation of the moving average may also be included in the unencrypted portion of the packet.

0032It should be understood that the timebase is ordinarily an unfixed value; that is, the timebase may be adjusted to meet the necessary sensitivity needs of the conferencing mixer to better distinguish speech from other noise. It is further appreciated that the audio communications may include human speech, noise, or both. As discussed previously, the normalized, multi-frequency power level information resulting from the computations is placed into the unencrypted portion of the outgoing packets.

0033<figref idref="f0005">Figure 5</figref> illustrates an example method for mixing audio packet streams from multiple conference participants. The example method shown begins with the conferencing mixer receiving the audio packet streams from the various endpoints associated with the participants to the conference session (block 51). Next, the mixer examines the unencrypted portion of the incoming packets in order to compare the power level information at the key frequencies for each stream (block 52). Since each packet stream represents audio received from a different endpoint, a comparison of the power levels of each stream allows the mixer to quickly identify which streams contain the loudest speech (block 53). After selecting the N loudest streams, the remaining packet streams are discarded or ignored (block 54) without being decrypted or decoded. Only the loudest N packet streams are decrypted /decoded, which step is shown occurring at block 55. The audio contained in the N loudest streams is then mixed (block 56) by the mixer to produce a set of customized output audio streams that are respectively sent to each of the endpoints associated with the corresponding conference participants, plus a single mixed stream containing all of the loudest participants, which is sent back to all participants who are not currently the loudest speakers (block 57).

0034In another embodiment, the mixer may create a receiver report on the power level results. The report can provide statistics on the audio packets sent from the endpoint encoder to the conferencing mixer. The mixer can then send the report to each endpoint along with the mixed output stream. The report may include information on an adjusted time base for the moving average computations. Adjusting the time base may sallow the mixer to control the sensitivity of the packet stream selection process. In the case where the audio packets are formatted as an SRTP packet, a RTCP receiver report may be generated by the mixer and sent back to the endpoints.

0035It should be understood that elements of the present invention may also be provided as a computer program product which may include a machine-readable medium having stored thereon instructions which may be used to program a computer (e.g., a processor or other electronic device) to perform a sequence of operations. Alternatively, the operations may be performed by a combination of hardware and software. The machine-readable medium may include, but is not limited to, floppy diskettes, optical disks, CD-ROMs, and magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, magnet or optical cards, propagation media or other type of media/machine-readable medium suitable for storing electronic instructions. For example, elements of the present invention may be downloaded as a computer program product, wherein the program may be transferred from a remote computer or telephonic device to a requesting process by way of data signals embodied in a carrier wave or other propagation medium via a communication link (e.g., a modem or network connection).

0036Additionally, although the present invention has been described in conjunction with specific embodiments, numerous modifications and alterations are well within the scope of the present invention. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.