Patent Description:
In the following description, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration specific embodiments which may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, and it is to be understood that other embodiments may be utilized, and that structural, logical, and electrical changes may be made without departing from the scope of the present invention. The following description of example embodiments is, therefore, not to be taken in a limited sense, and the scope of the present invention is defined by the appended claims.

The functions or algorithms described herein may be implemented in software in one embodiment. The software may comprise computer executable instructions stored on computer-readable media or computer-readable storage device such as one or more non-transitory memories or other type of hardware-based storage devices, either local or networked. Further, such functions correspond to modules, which may be software, hardware, firmware or any combination thereof. Multiple functions may be performed in one or more modules as desired, and the embodiments described are merely examples. The software may be executed on a digital signal processor, ASIC, microprocessor, or other type of processor operating on a computer system, such as a personal computer, server or other computer system, turning such computer system into a specifically programmed machine.

The functionality can be configured to perform an operation using, for instance, software, hardware, firmware, or the like. For example, the phrase "configured to" can refer to a logic circuit structure of a hardware element that is to implement the associated functionality. The phrase "configured to" can also refer to a logic circuit structure of a hardware element that is to implement the coding design of associated functionality of firmware or software. The term "module" refers to a structural element that can be implemented using any suitable hardware (e.g., a processor, among others), software (e.g., an application, among others), firmware, or any combination of hardware, software, and firmware. The term, "logic" encompasses any functionality for performing a task. For instance, each operation illustrated in the flowcharts corresponds to logic for performing that operation. An operation can be performed using, software, hardware, firmware, or the like. The terms, "component," "system," and the like may refer to computer-related entities, hardware, and software in execution, firmware, or combination thereof. A component may be a process running on a processor, an object, an executable, a program, a function, a subroutine, a computer, or a combination of software and hardware. The term, "processor," may refer to a hardware component, such as a processing unit of a computer system.

Furthermore, the claimed subject matter may be implemented as a method, apparatus, or article of manufacture using standard programming and engineering techniques to produce software, firmware, hardware, or any combination thereof to control a computing device to implement the disclosed subject matter. The term, "article of manufacture," as used herein is intended to encompass a computer program accessible from any computer-readable storage device or media.

Individuals, referred to as users, can start a conversation or meeting at any time. If a meeting has been scheduled, arrangements can be made to record the conversation and create a transcript of the conversation for later reference. However, ad-hoc meetings do not generally involve such preparation. Stopping the meeting, or otherwise devoting time to set up a method to record the conversation and arrange for a transcript to be created may be distracting or may not be thought of during the meeting. In addition, the ad-hoc meetings often take place outside conference rooms. In these cases, recording devices specifically designed for meetings are not available.

During the conversation, the audio of the conversation may be captured by devices the users are carrying, referred to as distributed devices. In example embodiments, the captured audio signals are transmitted to a meeting system over wireless channels to recognize that multiple users are having a conversation, referred to as a meeting, which may or may not have been planned. If the meeting is unplanned, it is referred to as an ad-hoc meeting.

In response to a meeting having been detected or otherwise arranged, a meeting instance is generated on the meeting system to recognize speech from users that are speaking and to generate a transcript of the meeting. Multiple signals of speech from multiple distributed devices are received as separate audio channels and used to generate the transcript. Distributed devices may include personal user devices (e.g., smartphone) as well as other devices including digital assistants, cameras, and any type of device that is capable of receiving audio and/or video within range of the conversation.

In some embodiments, a meeting can be created with a single press of a button on a single device via a meeting application. Other devices and users with devices can join the meeting either through the press of a button presented on their user device via the meeting application, or by being recruited while not in use (e.g., an existing conferencing device that is present in the room). Meeting participants may be inferred (e.g., identified) by voice fingerprint, by being an owner of a participating device, by facial recognition, or by manually adding a user via a meeting application on their device at any point (e.g. for remote participants).

There are many ways that a meeting may be established. In some embodiments, the distributed devices, such as smartphones, are associated with respective users and include a meeting application used to stream audio received from a microphone on the device to the meeting system or server. The audio received from nearby devices will have an audio signature based on a combination of ambient noise and/or any sound generated near the device. In response to two user devices providing a similar audio signature via their respective audio streams (audio channels), the meeting system recognizes that a meeting may be occurring and creates a meeting instance to process the received audio. Users may be prompted via their meeting applications to join the meeting. Alternatively, other information, such as location information, prior interactions, calendar information, or recent email interactions, for example, may be used to confirm that both users or yet a third user should be added to the meeting instance.

According to the invention, an audio watermark is generated by one or more of the user devices. The audio watermark comprises the audio signature or the audio signature may be separately detected. The audio watermark may be a sound pattern having a frequency above the normal hearing range of a user, such as <NUM> or higher. According to the invention, it is a sound that is inconspicuous to users so as not to interfere with the conversation. The watermark may be selected to be sent by a user desiring to ensure that a meeting instance is created during a conversation in some embodiments. The watermark is received by distributed devices within range and automatically or optionally added to a meeting instance. Devices within range of the watermark sound may also have their audio streams added to the meeting instance as additional audio channels.

In some embodiments, a conference code is generated and sent to other users to add them to a planned or ad-hoc meeting. The conference code may also be selected ahead of a scheduled meeting and used in a meeting invitation. The meeting system, upon receiving the conference code from a user device, adds the audio stream from such user device to the meeting once instantiated.

Example embodiments provide systems and methods for providing customized output based on a user preference in a distributed system are provided. In example embodiments, the meeting server or system receives audio streams from a plurality of distributed devices involved in an intelligent meeting. According to the invention, the meeting system identifies a user corresponding to a distributed device of the plurality of distributed devices and determines a preferred language of the user. A transcript from the received audio streams is generated as the meeting occurs. The meeting system translates the transcript into the preferred language of the user to form a translated transcript. The translated transcript is provided to the distributed device of the user. The translated transcript is provided in real-time (or near real-time) as the meeting is occurring. The translated transcript can be provided via text (e.g., displayed on a device of the user) or outputted as audio (e.g., via a speaker, hearing aid, earpiece). In some embodiments, in addition to translation, other types of transformation may be applied to the original transcript, translated transcript, or translated speech audio.

<FIG> is a perspective view of a meeting <NUM> between multiple users. A first user <NUM> has a first device <NUM> that includes a microphone to capture audio, including speech. A second user <NUM> has a second device <NUM> that is also capable of capturing audio, including speech. The users may be seated at a table <NUM> in one example meeting <NUM>.

The first and second devices <NUM> and <NUM> (also referred to as "multiple distributed devices" or "plurality of distributed devices") transmit the captured audio to a meeting server <NUM> for processing and generation of a transcript. The meeting may be ad-hoc, in that it was unplanned. For example, the users may have run into each other on break or happened to meet each other in a hallway and decide to talk about a project they are working on. A meeting application (also referred to as a "meeting app") may be running on both the first and second devices <NUM> and <NUM>. The meeting app may be used to provide the audio to the meeting server <NUM>.

The meeting server <NUM> detects that both devices are sending: audio with a similar audio signature, a similar audio watermark, a similar meeting code provided by both devices, or other information indicative of an ongoing discussion between the users. In response, the meeting server <NUM> generates a meeting instance to process the received audio and generate a transcript.

In various embodiments, a watermark may be any type of sound having energies only above the human auditory range, which is about <NUM>, or is otherwise inaudible, inconspicuous, or non-distracting that identifies a meeting instance or meeting code corresponding to the meeting <NUM>. The watermark may be a sound encoding the meeting code or other identification of the meeting instance in further embodiments.

The meeting <NUM> may involve more than two people, whether planned or ad-hoc. A third user <NUM> with a third device <NUM> may also join in the meeting <NUM>. The third device <NUM> also provides audio to the distributed meeting server <NUM>. The audio is recognized as involved in the meeting <NUM> by one or more of the same mechanisms described for recognizing that the first two users/devices are involved in the meeting <NUM>.

An owner/user of a distributed device may enroll himself/herself via the app to be recognized by the meeting server <NUM>. The user may have or create a voice profile, referred to as a voice thumbprint or fingerprint, to help the meeting server <NUM> associate an incoming speech sound with the user. If a random person joins the meeting <NUM>, the meeting server <NUM> recognizes that the person is not known and prompts one or more of the users already in a meeting for the person's name. Alternatively, the meeting server <NUM> searches a database in an organization associated with known users in the meeting to match the person with a profile. If the person is not known or otherwise identified, the person is identified with a label or tag such as speaker <NUM>, speaker <NUM>, and so forth. in a generated transcript, making it easier to modify the transcript if the person is later named. Any of the users may assign a name to the speaker label at any time during or after the meeting. Known or frequent contacts of those already in the meeting may be used to reduce the pool/database used to initially check for the person to optimize the process of identifying the person.

There may be additional devices that are within audio or visual range of the meeting <NUM>, such as a digital assistant <NUM> or a dedicated meeting device <NUM>, both of which are shown on the table <NUM>, but can be anywhere within audio range of the meeting <NUM>. Such additional devices may be connected to the distributed meeting server <NUM> and have their audio streams added to the meeting instance for processing to further enhance the audio and speech-to-text processing capabilities of the meeting instance running on the meeting server <NUM>. Such additional devices may be detected by the meeting server <NUM> and added to the meeting as described above or may be presented to one or more of the users as an option to add to the meeting.

A video camera <NUM> or other image capturing device may have a field of view that encompasses the meeting <NUM> (or a portion of the meeting <NUM>). The meeting server <NUM> is aware of the camera <NUM> being near the meeting <NUM> and may provide an indication to one or more of the users, providing an option to obtain information from the camera <NUM> and provide the information to the meeting instance to further enhance the processing and provision of a transcript. For instance, the camera <NUM> may be used to detect which user is speaking, or at least provide information that a user is likely to be speaking at any particular point in time.

<FIG> is a block diagram of a user device <NUM> for use in meetings. Other devices that participate in the meeting may have a similar set of components. The device <NUM> includes at least one microphone <NUM> and a processor <NUM> for executing a meeting app <NUM> that is stored on memory <NUM>. A transceiver <NUM> is used for streaming audio and/or video from a camera <NUM> to the distributed meeting server <NUM>. The user device <NUM> may also have a display screen, such as a touch screen <NUM>, a portion of which is shown.

Devices that may be participating in the meeting can be identified via calendar entries, current location, NFC (bring phones very close together), Bluetooth® advertising, and direct invitation via the conference code or other code that may be generated and associated with the meeting <NUM>.

The meeting server <NUM> may be processing several meetings at the same time via multiple meeting instances. Each meeting instance may include a meeting identifier, such as the meeting code, identifications of devices that are streaming audio, identifications of users that are participating in the meeting (either via a user associated device), or otherwise recognized by the meeting server <NUM> by facial recognition, voice recognition, or other means of recognizing users.

<FIG> is a flowchart illustrating a method <NUM> of initiating an intelligent meeting between two users with associated distributed devices. At operation <NUM>, an audio watermark is received at a first distributed device via a microphone associated with the first distributed device. In one embodiment, the audio watermark is transmitted by a speaker associated with a second distributed device during a meeting.

Data corresponding to the received audio watermark is transmitted via the first distributed device to a distributed device meeting server at operation <NUM>. In some embodiments, the received audio watermark is first converted to digital form, which may simply be a direct conversion of the audio watermark into a digital representation of the sound or may include a decoding of the audio watermark to obtain data identifying a meeting or the second distributed device that emitted the audio watermark.

An indication is received from the distributed meeting server, at operation <NUM>, that the first distributed device has been accepted to a meeting instance on the distributed device meeting server.

The first distributed device, at operation <NUM>, streams audio of the meeting to the meeting instance on the distributed device meeting server in response to the received indication. The received indication may include information identifying a communication channel to use, or the audio stream may simply identify the streaming device which the meeting server uses to direct the audio stream to the correct meeting instance.

<FIG> is a flowchart illustrating a method <NUM> of adding distributed devices to an intelligent meeting by use of a conference code. In some embodiments, the conference code is encoded in a watermark as discussed in method <NUM>. At operation <NUM>, a conference code is received or generated for a meeting between users by a first distributed user device. The first distributed user device may receive the code from a meeting server executing a meeting instance, or the first distributed user device generates the meeting code via a meeting app running on the first distributed user device.

The code is sent to a second distributed user device at operation <NUM>. The code may be sent via email, text, or other means of sending data electronically, or may be encoded as an audible signal (audio watermark) and transmitted acoustically to the rest of the participating devices, such as via a speaker of one of the user devices, such as the first distributed user device.

The second distributed user provides the conference code to the meeting server meeting instance whereby the meeting code is used, at operation <NUM>, to identify at least one second distributed user device. The second distributed user device streams audio at operation <NUM> to the meeting server meeting instance from both the first and second distributed user devices.

The meeting may be an ad-hoc meeting between multiple users or multiple user devices and the conference code is generated after the ad-hoc meeting has started. Note that there may also be users without an associated user device that are participating in the meeting. Other user devices and devices not associated with a user may be identified based on the detected location of devices. Data from such devices may have their data streams added to the meeting instance by providing a list of other nearby devices to user(s) and allow selection of such devices via a user interface of the app to add to the meeting instance. Devices that may be participating in the meeting can be identified via calendar entries, current location, NFC (bring phones very close together), Bluetooth advertising, and direct invitation.

In further embodiments, the meeting is a planned meeting between multiple users or multiple user devices and the conference code is generated before the planned meeting has started. The conference code may be sent to each of the user devices and used by the corresponding apps to identify the devices to the meeting server meeting instance for adding data streams from such devices during the meeting.

<FIG> is a computer-implemented method <NUM> of adding further devices to an intelligent meeting. At operation <NUM>, a meeting server receives audio streams from a group of distributed devices, wherein the audio streams comprise speech detected by such group of distributed devices during a meeting of two or more users.

The meeting server receives meeting information at operation <NUM> corresponding to the meeting from an additional or new distributed device. The new device may be a user device of a user that has just joined the meeting, or the new device may be a device that is in a room or otherwise within range of the intelligent meeting.

At operation <NUM>, the additional distributed device is added to the meeting server meeting instance. A stream of information from the additional distributed device is received at operation <NUM> in response to adding the additional distributed device.

<FIG> is a flowchart illustrating a computer-implemented method <NUM> of detecting that an ad-hoc meeting is occurring. At operation <NUM>, audio streams are received at a meeting server from at least two distributed devices that are streaming audio detected during an ad-hoc meeting between two users.

The audio streams are compared at operation <NUM> to determine that the audio streams are representative of sound from the ad-hoc meeting. The audio streams may be compared, for example, by calculating the normalized cross correlation coefficients between two signals. If the results are above a predetermined threshold, the audio streams are most likely from the same ad-hoc meeting. The selected threshold may be a number between <NUM> and <NUM> and may be selected empirically based on tests conducted during a number of meeting scenarios in different environments. The selection may be performed to obtain a desired balance of false negatives and false positives. Other indications that the streams are from the same meeting include the location of the devices being the same. Further indications include users that have had multiple interactions in the past, are in the same organization, and other indications that the users are likely to meet. Further verification can be obtained by comparing the text generated from the audio streams.

Once the streams are successfully compared, a meeting ID/code may be generated and used to add more participants. Other participants may be added in response to further devices streaming audio that are successfully compared to the audio streams already in the meeting. Once a device is added, the device may generate a signal indicative of j oining the meeting, such as a ping.

The meeting server generates a meeting instance at operation <NUM> to process the audio streams in response to determining that the audio streams are representative of sound from the ad-hoc meeting. In some embodiments, users are authenticated prior to audio streams from their respective devices being added to the meeting instance. Authentication may be based on user confirmation from the meeting app, calendar information, organization chart, use of the meeting code, extent of contact/relationship with users already in the meeting, and other means of authentication.

At operation <NUM>, the audio streams are processed to generate a transcript of the ad-hoc meeting. In one embodiment, the meeting server <NUM> detects when a device and/or an associated user has left the meeting and removes the audio stream/channel from that device from the meeting instance. When a participant associated with a device leaves a meeting, the meeting server <NUM> detects the absence of the audio signal associated with the device in the meeting and removes the device from the meeting. Alternatives include the user signaling leaving via the meeting app, closing the meeting app, detecting that the location of the device is no longer near the location of the meeting, detecting the absence of the corresponding audio watermark in the video stream from the device, detecting that the audio signature received by the device no longer matches that of other device audio streams, or performing image recognition on images from video signals to detect that the user is leaving or has left a conference room or area where the meeting is taking place. Similarly, the meeting instance can be concluded in response to a single user remaining or single user device remaining.

<FIG> is a flowchart illustrating a computer-implemented method <NUM> of removing an audio channel of a user device and other device in response to a corresponding user leaving a meeting. At operation <NUM>, multiple audio signals on corresponding multiple audio channels received from a group of distributed devices receiving audio from a distributed device meeting are processed by a meeting server instance. The meeting server instance is used at operation <NUM> to detect that a first user associated with a first device of the group of distributed devices has left the distributed device meeting, as discussed above. At operation <NUM>, the audio channel of the first distributed device is removed from the multiple audio channels being processed by the meeting server instance in response.

<FIG> is a flowchart illustrating a computer-implemented method <NUM> of authenticating a device and adding an audio stream from the device to audio channels being processed by a meeting server instance. Method <NUM> begins at operation <NUM> by receiving audio streams at a meeting server from multiple distributed devices receiving speech from multiple users during a meeting. The received audio streams are processed at operation <NUM> via a meeting instance executing on the meeting server to generate a transcript based on speech included in the audio streams.

At operation <NUM>, information is received at the meeting server from a first additional distributed device associated with a first additional user, the information corresponding to the meeting between users. The information may correspond to a request to add the user's device or may be an implied request by noting that an audio stream from such device includes a watermark or audio signature.

At operation <NUM>, the first additional distributed device or associated user is authenticated or otherwise authorized to join the meeting. A participant may be authorized to join a meeting based on a voice fingerprint, meeting organizer acceptance, using a meeting code and/or new code, detected location of the device of the participant, comparison of the device ID and/or associated user ID to an authorized list, organization member check, use of a closed meeting flag to require acceptance by the organizer, or combinations of one or more of the above. Note that method <NUM> may also be applied to the first two devices to join the meeting and may also be applied to devices that are not directly associated with a user, such as a meeting assistant type of device in a conference room or video camera having a field of view of a meeting.

In response to authentication of the additional distributed device or associated user, the first additional distributed device has its audio stream added to the meeting instance at operation <NUM>.

In some embodiments, remote participants may be connected into a meeting via a communications platform such as Microsoft Skype or Teams, telephone dial-in, or any other teleconference application. If a remote conferencing platform like Skype is used, the meeting may be joined by following a link sent out ahead of time. For dial-in, a unique phone number or access code such as the meeting code may be shared. Once the remote audio channel is connected to the server for the meeting, it is processed in a way similar to audio streams from the meeting area. The speaker ID is known based on the sign-in process. The audio stream may be for a single user/speaker, which means that no speech separation is required unless a speakerphone is used with multiple remote users. The audio being played by the speakerphone and detected by nearby distributed devices in the meeting may be cancelled from the audio streams of such nearby distributed devices.

<FIG> is a high-level block flow diagram of a system <NUM> for generating a transcript for a meeting with multiple users. The users each may have an associated (distributed) device <NUM>, <NUM>, <NUM> that are equipped with microphones to capture audio, including speech by the various users at the meeting and provide the captured audio as audio signals to a meeting server, which includes at least a meeting transcriber <NUM>, via audio channels <NUM>, <NUM>, and <NUM>, respectively. Different devices may have slightly different clock cycles and different amounts of processing latency. In addition, each device-to-server connection channel may have a distinct latency. Thus, the audio signals from the audio channels <NUM>, <NUM>, and <NUM> are not necessarily synchronized.

The meeting transcriber <NUM> includes a synchronization module or function in addition to a speech recognition module or function. The audio signals from the audio channels <NUM>, <NUM>, and <NUM> are first synchronized and then recognized, resulting in texts associated with each of the channels according to one embodiment. The recognition outputs are then fused (by fusion <NUM>) or otherwise processed to generate a transcript <NUM>. The transcript <NUM> may then be provided back to the users. In other embodiments, the audio signals from the audio channels <NUM>, <NUM>, and <NUM> are fused before speech recognition. The audio signal obtained after the fusion is recognized, resulting in a single version of text. In some embodiments, the transcript may be provided with very little delay.

In various embodiments, the conversion of the audio signals to text that is used in conjunction with speaker identification and generation of the transcript that is diarized to identify speakers are provided by the meeting server <NUM>. The functions performed by the meeting server <NUM> include the synchronization, recognition, fusion, and diarization functions. While such functions are shown in a particular order in <FIG>, in different embodiments, the functions may be performed in varying orders. For example, fusion may be performed prior to recognition and may also be performed at various other points as described below.

<FIG> is a detailed block flow diagram illustrating meeting server processing of information, generally at method <NUM>, including audio streams from distributed devices. Multiple audio data streams <NUM> are received from multiple distributed devices. The streams include A independent sequences of data packets. Each packet of the mth sequence contains a segment of a digitized audio signal captured by the mth device. The received packets are unpacked and the data from the packets are reformed to create a multi-channel signal. The multi-channel signal may be represented as: {[x<NUM>(t),. , xM-<NUM>(t)]; t=<NUM>, <NUM>,.

The digitized signals of different channels in the multi-channel signal are likely not synchronized, since many of the distributed devices are subject to digital signal processing differences, subject to on-device software latency differences, and subject to signal transmission speed differences. All of these differences can add up, making it difficult to consolidate the information from the different devices to create an accurate transcript. A stream synchronization module <NUM> receives the multi-channel signal and selects one of the channels as a reference channel. Without loss of generality, the first channel can be used as the reference channel. For the reference channel, the output is the same as the input (i.e., y<NUM>(t) = x<NUM>(t)). For the mth channel (<NUM> < m < M), the amount of misalignment between xm(t) and x<NUM>(t) is estimated and corrected to generate ym(t).

The degree of misalignment can be estimated by calculating the normalized cross correlation coefficients between two signals using a sliding window for the non-reference channel signal and picking up the lag that provides the maximum coefficient value. This can be implemented by using a buffer to temporarily store acoustic signal segments over which the cross-correlation analysis is performed individually between the reference channel and each of the other channels. Instead of the normalized cross-correlation, any score function that measures the degree of alignment between the two signals can be used.

In one embodiment, the relationship between adjacent synchronization cycles is taken into account. The misalignment is caused by two factors: a device/channel-dependent offset and a device-dependent clock drift. Even when two devices are capturing an acoustic event at the same time, the signals captured by the individual devices may arrive at the meeting server at different times, due to digital signal processing differences, on-device software latency differences, signal transmission speed differences, and so on. This is the device/channel-dependent offset. Also, different devices inevitably have slightly different clocks due to manufacturing variability. Therefore, even if two devices claim to support, for example, a <NUM> sampling rate, the signals recorded by these devices are not <NUM>% aligned and the amount of mismatch linearly grows as time goes on. This is device dependent clock drift. The device/channel-dependent offset and the device-dependent clock drift are denoted as S and D. The time difference at the kth synchronization cycle is represented as S + kD. Thus, estimates of S and D, provide a robust estimate of the degree of misalignment, S + kD.

The amount of misalignment may be corrected by periodically detecting misalignment using the above described cross-correlation and correcting for such detected misalignment. In addition, to reduce the amount of measured misalignment, a global offset (device/channel-dependent) and device dependent clock drift is calculated to estimate a degree of misalignment. The global offset may be used to correct global misalignment prior to measuring and correcting the misalignment by cross-correlation. The global offset may be determined as an average of measured misalignment over time and is likely the result of clock drift in the device. The degree of misalignment is thus estimated and corrected by simply accounting for the difference from the reference channel in accordance with one embodiment. Stream synchronization may be performed at varying intervals, such as every <NUM> seconds. Other intervals less than or greater than <NUM> seconds may be used in further embodiments, as network latencies may change.

Stream synchronization module <NUM> provides a multi-channel synchronized signal, {[y<NUM>(t),. , yM-<NUM>(t)]; t=<NUM>, <NUM>,. } to a beamforming module <NUM>. The beamforming module <NUM> functions to separate overlapping speech. Overlapping speech occurs when two people in the meeting speak at the same time. Prior to recognizing the speech and converting the speech to text, the speech is first separated into separate channels. Thus with an M-channel input, the output is N-channels, and is referred to as an N-channel beamformed signal, {[z<NUM>(t),. , zN-<NUM>(t)]; t=<NUM>, <NUM>,. The stream synchronization module <NUM> acts as a first fusion point, where multiple outputs are generated to retain the diversity of the input information. Where no speech overlaps, such fusion is optional.

<FIG> is a flowchart illustrating a computer-implemented method <NUM> of synchronizing multiple audio channels received from multiple distributed devices during an intelligent meeting. At operation <NUM>, audio signals representative of streamed speech are received from multiple distributed devices to generate multiple audio channels. A selected one of the audio channels is designated at operation <NUM> as a reference channel.

Once the reference channel is designated, the following operations are performed for each of the remaining audio channels. At operation <NUM>, a difference in time from the reference channel is determined. Each remaining audio channel's time is corrected by aligning the remaining audio channels with the reference channel as a function of the corresponding difference in time at operation <NUM>. This can be done by simply dropping extraneous samples, appending zeros, or using resampling techniques.

Method <NUM> may be performed periodically to correct the timing of the remaining audio channels, such as every <NUM> seconds. In one embodiment, method <NUM> includes further operations to correct for the global offset caused at least by different clocks in the distributed devices. At operation <NUM>, a global offset is determined for each of the remaining audio channels. The remaining audio channels are then corrected at operation <NUM> by each corresponding remaining audio channel global offset prior to correcting each remaining audio channel for the determined difference in time.

Acoustic beamforming, or simply beamforming, is a technique to enhance target speech by reducing unwanted sounds such as background noise from multi-channel audio signals. Beamforming can improve accuracy of downstream speech processing, such as speech recognition and speaker diarization.

For an intelligent meeting with audio streamed from multiple distributed devices whose exact positions relative to one another are not known, traditional beamforming algorithms, such as delay-and-sum beamforming, superdirective beamforming, and differential beamforming do not work. Such algorithms rely on prior knowledge about the arrangement of microphone devices, which is not available for distributed devices.

In one embodiment, an approach called geometry-agnostic beamforming, or blind beamforming, is used to perform beamforming for distributed recording devices. Given M microphone devices, corresponding to M audio channels, M-dimensional spatial covariance matrices of speech and background noise are directly estimated. The matrices capture spatial statistics of the speech and the noise, respectively. To form an acoustic beam, the M-dimensional spatial covariance matrices are inverted.

A drawback of the beamforming approach, be it traditional geometry-based beamforming or blind beamforming, is that it typically reduces the number of information streams from M to one, which means the downstream modules cannot take advantage of the acoustic diversity provided by the spatially distributed devices. In order to generate M beamformed signals and retain the acoustic diversity, a leave-one-out approach can be taken. With this approach, the first output signal is generated by performing beamforming with Microphone <NUM>-M. The second output signal is generated with Microphone <NUM>-M and <NUM>-M. This can be repeated M times so that M different output signals are obtained. For each beamforming, (M-<NUM>)-dimensional spatial covariance matrices are computed and inverted, which is very computational demanding. Fortunately, the computational cost can be significantly reduced by deriving all the (M-<NUM>)-dimensional inverse matrices from the original M-dimensional inverse matrices.

In some embodiments, the beamforming module <NUM> may be configured to separate overlapped speech signals of different users. This can make speech recognition and speaker attribution more accurate. In one embodiment, continuous speech separation for a distributed microphone recording system is performed via a neural network that is trained using permutation invariant training or its variant such as deep clustering or attractor network. To potentially save on computation, overlap detection may be used to determine whether or not the speech separation neural network should be executed for each period of time. If overlapped speech is not detected for a selected period of time, the neural network is not executed, saving processing resources and allowing the transcript to be produced more quickly in real time.

The speech separation neural network model is executed to perform continuous speech separation for distributed microphone recording system, where the number of input microphones can be arbitrary and vary through time. The model outputs two continuous streams of speech. When there is one active speaker, one of the outputting streams will be silent, while when there is overlapping speech between two speakers, each speaker will occupy a distinct output stream.

In example embodiments, the speech separation neural network model contains three submodules: a local observer, a global summarizer, and a mask reconstructor. The multi-channel input is processed by these three submodules sequentially. Firstly, the same local observer is applied to each input microphone. The local observer comprises a set of stacked attention layers that maps each microphone input into a high dimension representation, where each channel will cross compare and extract the information from all other channels. Two different types of attention are implemented, which are the self attention and feedforward attention.

Next, the global summarizer is applied to summarize information from each observer to form a global representation across different input channel. Two options for the global summarizer are contemplated - a mean pooling and a permutation invariant sorting algorithm - where the representation of each channel is compared with permutation invariant loss to align their local permutation and the global permutation. When there is no summarization layer, the network is reduced with a channel-wise speech separation network, where each channel has its own separation (i.e., no global separation agreement between channels).

Lastly, the mask reconstructor sorts two mask outputs at the same time for any arbitrary time. The mask reconstructor comprises a stack of long short-term memory network and generates the final two channel output from the summarization at each time point.

After getting the two-channel output from the mask reconstructor, permutation invariant training objective function is applied between the reconstructed mask and the clean reference, where the Euclidean distance of each permutation pair of output and clean reference are measured first, and then minimum distance and corresponding permutation is selected to update the neural network.

The network is trained with simulated multi-channel data, where the number of input channel are randomly picked for each sample (e.g., from <NUM> to <NUM> channels). Libri speech dataset is applied as source data in the simulation. In each simulated sentence, two utterances from two random users/speakers are first selected. Then each utterance is processed with room acoustic simulation with room impulse responses from image method with random room and location setting.

One variation of speech separation is speech overlap detection, where the task is reduced to just detect the overlap region in recorded speech. The algorithm operates in a similar way, where the network receives N channels as input, and continuously outputs two channels as output. In the overlap detector, the network does not output masks. Instead, the network outputs two <NUM>-dimension indicator functions, where <NUM> means there is one active speaker in that channel, and <NUM> means silence. Therefore, when there are two active speakers, the two outputting streams will each have <NUM> as output. When there is one active speaker, one arbitrary channel will have <NUM> as output and the other will have <NUM>. The network is also trained with permutation invariant training objective, between the output of the network (i.e., indicator function) and the reference indicator.

<FIG> is a flowchart illustrating a computer-implemented method of separating overlapped speech in a distributed device intelligent meeting. At operation <NUM>, audio signals representative of speech are received via multiple audio channels corresponding to streaming audio transmitted from corresponding multiple distributed devices.

Continuous speech separation is performed at operation <NUM> on the received audio signals to separate speech from different speakers speaking at the same time into separate audio channels. In one embodiment, speech separation at operation <NUM> is performed by a trained neural network model. The neural network model is trained using permutation invariant training or its variant.

At operation <NUM>, the separated audio channels are provided for speech recognition and generation of a transcript. Operation <NUM>, in one embodiment, provides a fixed number of separate output channels. Since there may be a varying number of microphone inputs and the number of outputs is fixed in advance, there may be instances where a limited number of audio channels can be accommodated, since for each audio channel with multiple overlapping speakers, each speaker results in a separate audio channel. Thus, if the number of output audio channels is limited, not all channels may have speakers separated.

The N different outputs of the beamforming module <NUM> in <FIG> are provided to N acoustic models <NUM> and <NUM> that produce a sequence of senone posterior probabilities. Such models are well known and are typically neural network based. The use of an acoustic model for each of multiple audio channels from distributed devices and/or beamformer outputs provides N scores for each senone.

The scores, including those for the senones, are provided to an acoustic model score fusion module <NUM>. The audio of the individual input channels may be processed conventionally to provide a sequence of senones and their posterior probabilities. The results are combined using the model score fusion module <NUM>, before applying the result to multiple speech recognition (SR) decoders <NUM>, <NUM>. The score fusion module <NUM> operates as a second fusion point that combines multiple information sources and, at the same time, generates multiple outputs to retain the diversity of the input information. The two-step process involves two different neural nets (or classifiers): a vanilla-flavor acoustic model and a new, more targeted acoustic model. The output is a sequence of 1x the number of senones. Note that the score fusion module <NUM> uses the output of the last layer of the acoustic model (neural net) as input. In further embodiments, the score fusion module <NUM> can use the output of any layer before the last. The size of the input may be different than the size of the output.

The sequences of senones from the acoustic model score fusion module <NUM> are provided to the SR decoders <NUM> and <NUM>, each of which utilizes standard speech recognition processing to provide an n-best list of words for each segment of senones. A beginning time and a duration are provided for each word. Segmentation may be performed based on voice activity detection, speaker change detection, a fixed interval, or some other suitable method. Rescoring may be performed by using a neural network language model (NNLM) on the decoder output to generate better n-best lists of word hypotheses.

Multiple speaker diarization modules <NUM>, <NUM> receive the outputs of the SR decoder modules <NUM>, <NUM> as an N-best list for each segment. In one implementation, only the top word sequence hypothesis is used. A first operation extracts speaker embeddings, such as d-vectors (hidden layer activations of a deep neural network for speaker verification), at fixed intervals. A second operation factorizes the word sequence into speaker-homogeneous subsegments. This can be performed with variants of agglomerative clustering, BIC (Bayesian Information Criterion), or other methods by using the embedding features. A third operation assigns a speaker identifier to each of the subsegments obtained above by comparing the proximity (e.g., cosine similarity, negative Euclidian distance) of the speaker embeddings of the subsegment and those of each candidate speaker. The resulting output is an assignment of a speaker label to each recognized word of the top SR hypothesis.

A hypothesis combination module <NUM> receives as input, n-best lists from N SR decoder modules <NUM>, <NUM> (e.g., beamformed audio channels), and speaker recognition output from N sources such as the beamformed/separated audio channels. Hypothesis combination module <NUM> processes the n-best scores from each channel by scaling and normalizing them and thus computing utterance-level posterior probabilities. The n-best hypotheses are aligned into word confusion networks. By adding the utterance-level posteriors pertaining to a given word hypothesis, word-level posterior probabilities are obtained. The speaker recognition outputs from each channel are formatted as confusion networks with alternating speaker and word labels. The word labels are from the <NUM>-best recognition hypotheses, whereas the speaker labels represent <NUM>-best or n-best speaker model matching to the speech segments. Posterior probabilities for the speaker hypotheses represent normalized speaker model likelihoods. Posteriors on word hypotheses are scaled down by two orders of magnitude so as to not affect the final word recognition, thus affecting only the proper alignment of word and speaker labels. The confusion networks thus obtained from each channel are truncated and/or concatenated, as necessary, so as to cover the same time window, as dictated by online processing constraints. The output comprises a confusion network (CN) encoding both word and speaker hypotheses and their posterior probabilities.

The word and speaker confusion networks are aligned according to a minimum edit distance criterion, as well as a penalty for time discrepancies between aligned nodes. This effectively merges the speaker and word hypotheses into a single network, summing the posteriors of matching labels. If desired, the top speaker and word hypotheses are read off from the combined CN by picking the highest-posterior label at each position. The word confusion networks may be built from word lattices instead of n-best lists, depending on what the speech decoder outputs.

The output from combination module <NUM> is the result of a third fusion, referred to as a late fusion, to produce text and speaker identification for generation of a speaker-attributed transcript of the meeting. Note that the first two fusion steps at beamforming module <NUM> and acoustic model score fusion module <NUM>, respectively, are optional in various embodiments. In some embodiments, one or more audio channels may be provided directly to an acoustic model scoring module <NUM> without beamforming or speech separation. Speech recognition is then performed on one or more audio channels via SR decoder <NUM>, followed by speaker diarization module <NUM>, with the output provided directly to the combination module <NUM>.

Audio streams may be fused early, following synchronization of digital audio streams, by geometry-agnostic beam forming or continuous speech separation. Multiple outputs may be generated to retain input information diversity. Late fusing may be done at an acoustic model score level and/or text level/diarization level to leverage speaker information and diverse model hypotheses. In one embodiment, late fusion over a word or two is performed by use of a fixed time window. The time window, in one embodiment, corresponds to salient audio events, and may be fixed at, for example, two seconds. Such a time window is selected to be fairly short to enable the provision of real-time (or close to real-time) transcripts with low latency.

In one embodiment, real-time transcripts are generated based on short word sequences. Late fusion of data is performed by speech recognition for multiple audio channels being processed in parallel to produce phrases. The phrases derived from the multiple audio channels are combined in real-time. In one embodiment, approximately two seconds of speech is combined at hypothesis combination module <NUM>. Thus, the audio streams are processed as they are received. A non-overlapping sliding window of two seconds is used to process the audio streams, decreasing the latency of the meeting system <NUM> transcript generation to close to zero.

The individual speech recognition decoders continuously output some results and based on the hypothesis combination module <NUM>, the results are processed immediately. A special provision is provided for the alignment of the individual systems at stream synchronization module <NUM>, otherwise the final results may contain multiple instances of the same events (due to misalignment). A post-processing step removes any duplicates that may exist regardless of the signal and/or speech recognition output alignment. Alignment may be performed on either the word level or on the sample level of the signals. Note also that different versions of audio are received by the speech recognition decoders. Each SR decoder may hear something different. By combining the SR results (late fusion) with low latency, a highly accurate transcript is produced. Every SR outputs a word or two with a confidence level. The time, such as two seconds, is long enough to obtain some salient output - in other words, an output having a word or two that can be recognized with some confidence. A fixed window of time, such as two seconds is found to work better. If the time is too short, there is no salient event, and if the time is too long, latency becomes too long and the transcript is delayed, making the transcript of less utility during a meeting.

Another version of this approach is to wait for time points in the audio stream where either (<NUM>) all streams contain no speech with high confidence or (<NUM>) have a single word hypothesis with high confidence. In those places, the hypothesis space can be pinched to a single hypothesis, which makes it possible to perform combination without loss of accuracy as a result of incorrect word segmentation.

The transcript is provided to one or more of the meeting participants based on the output indicated at <NUM>. A single meeting transcript is provided based on the output of the meeting system. The transcript is composed of individual utterances and associated media, such as slides or photos of drawings. Each utterance is assigned a universal timestamp, attributed speaker, associated text, and/or an associated audio segment, where the audio is extracted from the synchronized input streams from all participating clients.

Additional media or content such as images, notes, and other abstract objects can be associated with the transcript inline through a timestamp (e.g., a picture of a whiteboard is captured and uploaded at time t) or to the whole meeting without a specific timestamp (e.g., a file was uploaded after the meeting and associated with this meeting instance). All attendees can have access to the meeting and associated data. Ad-hoc meetings can be viewed and modified by meeting owner, all attendees, or anyone depending on the permissions set by the entity that created the meeting. Additional services such as meeting summarization, action item identification, and topic modeling may be provided using the transcript and other associated meeting data.

<FIG> is a flowchart illustrating a computer-implemented method <NUM> of fusing audio streams at multiple selected points during processing. The audio streams are recorded during a meeting by a plurality of distributed devices. Method <NUM> is performed by one or more processers performing operations. An operation <NUM> performs speech recognition on each audio stream by a corresponding speech recognition system executing on the one or more processors to generate utterance-level posterior probabilities as hypotheses for each audio stream. The hypotheses are aligned and formatted at operation <NUM> as word confusion networks with associated word-level posterior probabilities. Operation <NUM> performs speaker recognition on each audio stream by execution of a speaker identification algorithm that generates a stream of speaker-attributed word hypotheses. The speaker hypotheses are formatted with associated posterior speaker label posterior probabilities and speaker-attributed hypotheses for each audio stream as a confusion network at operation <NUM>. Operation <NUM> aligns the word and speaker confusion networks from all audio streams to each other to merge the posterior probabilities and align word and speaker labels. A best speaker-attributed word transcript is created at operation <NUM> by reading off the sequence of word and speaker labels with the highest posterior probabilities.

In one embodiment, a special approximate version is obtained when only a single word hypothesis from each stream is generated, possibly even without posterior probabilities, and where simple voting among all streams is used.

Method <NUM> operations may be performed on successive time windows applied to the audio streams such that the processing is performed incrementally so as to enable production of speaker-attributed word recognition hypotheses in real-time. The input hypotheses are truncated in time to a common time window applied to all audio streams based on the time marks associated with the word hypotheses generated for each audio stream.

The input speaker and/or word hypotheses streams may originate from multiple partial combination of input audio streams via fusion of K out of N, where K < N, audio streams. Alternatively, the input speaker and/or word hypotheses streams originate not from different audio streams, but from multiple partial combination of acoustic models applied to K out of N audio streams, which in turn could result from raw audio signals or fusion of audio signals.

In yet a further embodiment, the input hypotheses are truncated in time to a common time window applied to all audio streams based on the time marks associated with the word hypotheses generated for each audio stream. The combination of K out of N raw audio signals or fusion of the audio signals may be based on audio-quality criteria and/or based on the relative position of the speakers with respect to the distributed devices.

In one embodiment, the input speaker and/or word hypotheses streams originate from multiple partial combination of input audio streams via fusion of K out of N audio streams, where K < N. The combination of K out of N acoustic model outputs may be based on audio-quality criteria of the input signals and/or based on the relative position of the speakers with respect to the distributed devices. Alternatively, the input speaker and/or word hypotheses streams may originate from multiple partial combinations of acoustic models applied to K out of N audio streams where K < N, which in turn results from raw audio streams or fusion of audio streams. In yet a further embodiment, the output of multiple acoustic models may be applied to K out of N audio streams, where K < N, which in turn results from raw audio streams or fusion of audio streams that are combined as input to M speech recognition decoders.

<FIG> illustrate an example ambient capture device <NUM>. In one embodiment, ambient capture device <NUM> is cylindrical in shape with a fisheye camera <NUM> at the top of and facing up with respect to the device <NUM>. A microphone array <NUM> is coupled to the device <NUM> below the camera <NUM> and placed around the cylinder to capture audio in <NUM>°. It should be noted that the device in <FIG> may not be drawn to scale. In order to capture optimal <NUM>° vision (e.g., video or still images), it may be desirable for the fisheye camera to be close to a floor or table surface <NUM>. In an embodiment, the device may be short and squat to avoid blind spots below the camera <NUM>. In an embodiment, the fisheye camera may be placed in close proximity to a microphone array <NUM>.

Capture device <NUM> may be used with distributed devices in capturing audio and video from a distributed device meeting. Device <NUM> may itself be one of the distributed devices. The identification of users associated with speech may be performed solely by the capture device <NUM> in one embodiment, or the information streams collected from the capture device <NUM> may be used together with information streams collected from the other distributed devices to generate speaker attributed transcripts in various embodiments.

In the example illustrated in <FIG>, seven microphones 1423A-G are included in the microphone array <NUM>. As shown, six microphones 1423A-F is placed around the device in a plane and more or less equidistant from the center of the device, and a seventh microphone <NUM> is placed in the center. It will be understood that the device may be made of audio penetrable material, such as a light fabric, grille, or mesh, and that the microphones <NUM> are not blocked by the fisheye camera <NUM> or other structural portions of the device <NUM>, so that the sound is not obstructed.

In one embodiment, the fisheye camera may be approximately <NUM> from the base of the device <NUM>, and the microphone array <NUM> may be affixed approximately <NUM> above the base <NUM>. When in operation, the device <NUM> may sit on, or be affixed to, the floor or table <NUM> in an environment. As the device <NUM> is placed closer to the floor, the <NUM>° horizontal field of view (HFOV) may include more of the environment. The fisheye camera <NUM> is typically affixed to the device <NUM> facing up, so the ceiling may be in the field of view. It will be understood that other shapes, sizes, or configurations of the device <NUM> and placement of the fisheye camera <NUM> and microphone array <NUM> may be implemented, with some adaptation to provide both similar and varying results.

In one embodiment, acoustic parameters for audio capture vary depending on the specifications of the microphones. An example of acoustic specifications for an embodiment is shown below in Table <NUM>. In an embodiment, the acoustic parameters apply to the whole audio subsystem (e.g., captured pulse code modulation (PCM) data) not just the microphones. The captured audio may produce adequate speech recognition accuracy for use in an AI application. One of ordinary skill in the art, with the benefit of the present disclosure, will appreciate that various acoustic parameters may be utilized to achieve speech recognition accuracy, and that the example parameters in Table <NUM> are for illustrative purposes.

<FIG> illustrates an example placement of the microphone array <NUM>, according to one embodiment. In an embodiment, the device includes seven microphones placed in the same plane. Six microphones 1523A-F are placed in a circular or hexagonal pattern in the plane, approximately <NUM> from a center point. A seventh microphone <NUM> is placed at the center point. In an embodiment, the configuration of seven microphones comprise microphones of similar specification. It will be understood that additional processing of the audio data received from the microphone array may be necessary to normalize or adjust the audio when the microphones are dissimilar. In an example implementation, the microphone array <NUM> may comprise seven digital microelectromechanical systems (MEMS) microphones with ports facing upwards. It will be understood that better performance may result when the microphones are not obstructed by sound absorbing or blocking components, such as a circuit board or device case.

In one embodiment, similar microphones are clocked using the same clock source in the device (not shown). The clocking or timestamping of the audio may assist with synchronization and fusion of the audiovisual data.

The ambient capture device may decimate all microphone signals to <NUM>-bit <NUM> PCM data. In this context, decimation is the process of reducing the sampling rate of the signal. For automatic speech recognition, frequency bands higher than <NUM> may be unnecessary. Therefore, a sampling rate of <NUM> may be adequate. Decimation reduces bit rate without compromising required accuracy. In an embodiment, the capture device may support additional bit depths and sampling frequencies. In an embodiment, the capture device may not allow changing data width and sampling frequency, to reduce driver complexity and improve stability. The microphones may be mounted using any adequate mechanical dampening mechanism, for instance, rubber gaskets, to reduce vibrations and noise.

It will be understood that more or fewer microphones may be present in the microphone array. However, fewer microphones may introduce some uncertainty of speaker location. Additional microphones may provide increased certainty or resolution of the audio, but at a cost of more hardware and additional complexity of calculation.

In one embodiment, an audio speaker is located at the bottom or base of the device for audio feedback to the user. The audio speaker may be used for feedback announcements or be an integral part of the AI application. For instance, in an AI application for conference management, a user may request meeting minutes to be read back to the attendees. An integrated speaker in the device provides feedback or requests instructions or commands for operations. If a spoken command is not understood, a request to repeat the command may be played through the audio speaker. To reduce acoustic feedback, the audio speaker may face the opposite direction from the microphone array. Audio played back via the audio speaker may be looped back as an additional synchronized microphone channel.

Referring back to <FIG>, in an embodiment, the fisheye camera <NUM> receives <NUM>° HFOV, and at least <NUM>° vertical field of view (VFOV) above, and <NUM>° VFOV below a horizontal axis, resulting in a <NUM>° VFOV, or approximately <NUM>° diagonal field of view (DFOV). In practice, the capture device <NUM> may be placed on a table of floor, so a vertical view below the surface is not needed. Thus, in discussion herein, the VFOV is identified as approximately <NUM>° to indicate a view above the horizontal base plane of the device.

In one embodiment, the fisheye camera <NUM> includes one fisheye sensor of <NUM> megapixels (MP) (e.g., providing a <NUM> resolution). The camera lens may be mounted with respect to its image sensor, so that the optical center aligns with the center of the image sensor, and the optical axis is perpendicular to the image sensor. The relative position of the camera lens to the microphone array may be fixed and known. In particular, the optical center may align with the center of the microphone array with the optical axis perpendicular to the microphone array.

<FIG> illustrates an AI system <NUM> with an ambient capture device <NUM>, as described above, and a meeting server, referred to as a cloud server <NUM>. In an example, user <NUM> interacts with an AI application <NUM>. It will be understood that the AI application <NUM> may reside on the cloud server <NUM> or on a local device (not shown). Audiovisual data may be captured in <NUM>° by the AI capture device <NUM>. As discussed above, the capture device <NUM> may include a fisheye camera <NUM> providing a <NUM>° HFOV and approximately a <NUM>° VFOV. The capture device <NUM> may also include a microphone array <NUM> to capture audio in <NUM>°.

Video compression of the images and video stream received by the camera <NUM> may be performed by a processor <NUM> on the device. Video modes and compression protocols and criteria may be controlled by user selectable software controls. In addition to compression, the audiovisual data may be protected by encryption, to prevent unauthorized persons from obtaining the data. In an embodiment, compression <NUM> may be performed by circuitry on the device and controlled by software switches.

Pre-processing <NUM> (e.g., cropping of images based on image content, or noise reduction) may be performed by logic executed by the processor, before compression <NUM>. In an embodiment, pre-processing may include acoustic echo cancellation (AEC) to reduce feedback, noise, and echo caused by a speaker <NUM> coupled to the device.

In an embodiment, a local process for keyword spotting (KWS) may be included in order to listen for device commands for the ambient capture device, such as to wake or turn off the device. The local KWS may favor recall versus precision, and it may be based on a reduced microphone array (e.g., two microphones rather than the full array).

When AEC is performed on the device <NUM>, the acoustic channel including the speaker audio may not need to be sent to the models to perform sensor fusion <NUM>. The compressed audiovisual data may be sent to a cloud server <NUM> by a transmission unit <NUM>. Transmission unit <NUM> may include one or more of: a network interface card for wired communication, such as an Ethernet connection; a wireless transceiver using a wireless protocol such as for WiFi®, Bluetooth®, NFC; or other communication means. In an embodiment, audio feedback may be sent to the device via one of the wireless channels. The cloud server <NUM> may perform sensor fusion <NUM> for the AI application <NUM>. Therefore, compression may be performed to reduce bandwidth of the transmission to the cloud via a transmission unit <NUM>.

<FIG> is a flowchart illustrating a computer-implemented method <NUM> of reducing the number of audio streams sent over a network to the meeting server for use in generating a transcript. Method <NUM> begins by receiving multiple channels of audio at operation <NUM> from a plurality (e.g., three or more) of microphones detecting speech from a meeting of multiple users. At operation <NUM>, directions of active speakers are estimated. A speech unmixing model is used to select two channels corresponding to a primary and a secondary microphone at operation <NUM> or may correspond to a fused audio channel. The two selected channels are sent at operation <NUM> to a meeting server for generation of an intelligent meeting transcript. By reducing the amount of data sent to the meeting server, bandwidth is conserved. Since the data selected is arguably the best data, little if any accuracy is lost.

In one embodiment, the microphones are supported by a device in a fixed configuration. The fixed configuration may include a camera having a field of view configured to include the multiple users. Localizing sound sources may be performed by executing a model trained on channels of audio and video from the camera. For example, if one user is using a laptop computer with a camera, the laptop may provide both an audio and video channel. The audio channel may be synchronized with respect to the reference audio channel, and the same time difference may be used to synchronize the video channel. Image recognition may be used on the video channel to identify the user as the speaker for diarization in producing the transcript. In a further embodiment, the laptop computer performs image processing to determine that the user is speaking and provide a tag on the audio channel identifying the user as the speaker. The tag may then be used for diarization without the need to transmit the video channel from the laptop.

In a further embodiment, the microphones are associated with multiple distributed devices. The distributed devices may include wireless devices respectively associated with the multiple users. At least one of the distributed devices may include a camera providing video of at least one of the users.

In yet a further embodiment, the microphones include microphones supported in a fixed configuration and microphones associated with distributed devices associated with users. The method may be performed by one or more of a device supporting the microphones in a fixed position or an edge device receiving the multiple channels of audio. The speech unmixing model may be executed on the edge device.

In further embodiments, client-side processing (processing on one or more of the distributed devices, ambient capture device, and/or edge server) is used to reduce the computational resources required by the meeting server as well as to reduce the amount of network bandwidth utilized for processing distributed meeting information streams from the distributed devices. In addition to the reduction in the number of streams sent via network to the meeting server as described above, beamforming may be performed on the client side, as well as generation of audio watermarks and meeting codes. In further embodiments, model sizes may be reduced and quantized to better run on the client side. The objective function may also be modified to better run on the client size. Instead of outputting a speech mask, sound source localization may be used with commensurate less computations.

Both audio and video channels may be used to attribute speech to users for creation of the diarized transcript. An audiovisual diarization approach allows the combining of voice identification, sound source localization, face tracking/identification, and visual active speaker detection from distributed sensors to achieve robust diarization.

<FIG> is a flowchart illustrating a computer-implemented method <NUM> for using both video and audio channels, audiovisual data, from distributed devices to provide better speaker identification. Method <NUM> begins by receiving, at operation <NUM>, information streams on a meeting server from a set of multiple distributed devices included in an intelligent meeting. At operation <NUM>, audio signals representative of speech by at least two users in at least two of the information streams are received. At operation <NUM>, at least one video signal of at least one user in the information streams is received. The received audio and video signals are used to associate speech in the received audio signals with a specific user as a function of the received audio and video signals at operation <NUM>. A transcript of the intelligent meeting is generated at operation <NUM> with an indication of the user associated with the speech.

The multiple distributed devices, in one embodiment, are mobile wireless devices associated with users in the intelligent meeting. The mobile wireless devices may include a microphone and a camera that provides the at least one video signal. In further embodiments, the multiple distributed devices include a device having multiple microphones supported in a fixed configuration, each microphone providing one of the received audio signals. The device may include a camera having a field of view configured to include multiple users in the intelligent meeting and provide the at least one video signal.

In one embodiment, a fusion model is used on the received audio and video signals to associate the specific user with the speech. In an embodiment, the audiovisual data may be analyzed by the meeting server. The audiovisual data may first be compressed prior to sending to the meeting server via a network. In another embodiment, the fusion model is coupled to the capture device as an integrated system. Discussions herein describe the meeting server for illustration purposes and not as a limitation.

The meeting server decompresses, decodes, or decrypts the data, as necessary. The audiovisual data may be fused and analyzed by an AI application utilizing an LSTM model, for example, to identify or infer features in the audiovisual data such as, but not limited to: audio direction; speaker location in an image; speaker movement; voice signature; facial signature; gesture; and/or object. In an example, an AI application requires speech recognition or facial recognition. The LSTM model may be trained with data specific to the AI application using the sensor data. In an embodiment, more than one model or analysis engine may be used, as discussed above.

In an embodiment, speech may be identified and gesture recognition using the video data may be performed. The LSTM model may use the identified speech and the recognized gesture to provide a probable fusion of the data and send the probable outcomes to the AI application. In an example, a gesture combined with a voice command provides specific control commands to the AI application. In an example, analysis of video data indicates an eye gaze or track eye movements to infer where a user is looking. Eye gaze analysis may result in control commands for the AI application, and may differ based on fusion with audio data.

In an embodiment, the LSTM model is trained for a specific AI application and provides the control or commands for that application, based on the fused data. In another embodiment, the LSTM model may be more generic and provide probable correlated data, such as audio streams for each speaker with a speaker ID and location in the environment, and a video stream, to the AI application for further processing and interpretation of the inputs. In this example, the AI application uses the audio and video stream input to derive the appropriate commands or perform actions.

One embodiment utilizes a fisheye camera with a 12MP sensor. Another embodiment includes an infrared (IR) or other depth sensor to provide three dimensional (3D) or depth information. Depth information may not be available in <NUM>° if there are not enough depth sensors to cover the entire HFOV. Variations of the capture device may be provided to accommodate various price points acceptable to a wide range of users, or for different applications. For instance, inclusion of the depth sensors or higher resolution sensors may increase the cost or complexity of the device beyond what is necessary for the selected AI application.

<FIG> is a flowchart illustrating a computer-implemented method <NUM> for customizing output based on a user preference according to an example embodiment. Operations in the method <NUM> are performed by the meeting server or system (e.g., meeting server <NUM>), using components described above. Accordingly, the method <NUM> is described by way of example with reference to the meeting server. However, it shall be appreciated that at least some of the operations of the method <NUM> may be deployed on various other hardware configurations or be performed by similar components residing elsewhere in a network environment. Therefore, the method <NUM> is not intended to be limited to the meeting server.

In operation <NUM>, the meeting server receives audio streams from a plurality of distributed devices. In example embodiments, the audio streams comprise speech detected by one or more of the plurality of distributed devices during a meeting of two or more users. In some embodiments, the meeting is an ad-hoc meeting. In these embodiments, the server can perform blind beamforming or continuous speech separation on the received audio streams to separate speech from background noise or different speakers speaking at the same time into separate audio channels. According to the invention, the audio streams are compared to determine that the audio streams represent sound from the (same) ad-hoc meeting. A meeting instance is then generated to process the audio streams identified as being from the ad-hoc meeting.

In operation <NUM>, an identity of a user of one of the distributed devices is identified by the meeting server. In one embodiment, the user is identified based on a video signal captured by a camera (e.g., camera <NUM>, camera <NUM>) associated with the meeting. The video signal is transmitted to the meeting server. The meeting server compares an image of the user from the video signal with stored images of known (e.g., registered) users to determine a match. If a stored image matches a captured image of the user in the video signal, then the user is identified. In one embodiment, the image of the user is stored or associated with a user profile of the user.

In an alternative embodiment, the user is identified based on a voice signature. In this embodiment, speech from the audio stream is parsed or diarized and compared to stored voice signatures of known users. If a stored voice signature matches the parsed/diarized speech from the audio stream, then the user is identified. In one embodiment, the voice signature of the user is stored or associated with a user profile of the user.

In operation <NUM>, a language preference of the identified user is determined. In some embodiments, a user profile of the identified user is accessed. The user profile comprises at least a predetermined preference for a language of the user. In some cases, the predetermined preference is established (e.g., explicitly indicated) by the user. In other cases, the predetermined preference is determined based on a device configuration of the device (e.g., distributed device, such as a cell phone or a laptop) associated with the user. For example, the device may be configured to function in English or Chinese.

In operation <NUM>, the meeting server generates a transcript as discussed above. In example embodiments, speech from the audio streams are converted to text in order to generate a text-based transcript or digital transcript. In one embodiment, as discussed above, a real-time transcript is generated based on short word sequences. In some embodiments, late fusion of data may be performed by speech recognition for multiple audio channels being processed in parallel to produce phrases. The phrases derived from the multiple audio channels are combined in real-time or near real-time. In one embodiment, approximately two seconds of speech is combined. As a result, the audio streams are essentially processed as they are received. A non-overlapping sliding window of a few (e.g., two) seconds is used to process the audio streams, decreasing latency for transcript generation.

In operation <NUM>, the meeting server translates the transcript according to the language preference of the user. The meeting server takes the generated transcript from operation <NUM> and translates the text in the generated transcript into text in the preferred language. Some embodiments may perform both text translation and speech translation. In example embodiments, a user (e.g., speaker) identity for each translated utterance from the transcript is provided with the translated transcript. In some cases, the user identity is obtained from a user identifier associated with the distributed device.

In operation <NUM>, the translated transcript is provided to a device (e.g., distributed device) of the user. In some embodiments, the device comprises a same device that is used to capture audio from the user. The translated transcript can be provided, for example, as a text displayed on a display device (e.g., screen) of the device, or as speech audio via speaker devices (e.g., earpieces, hearing aids, or loudspeakers) by using text-to-speech. In some embodiments, the diarization results may also be provided.

While the method <NUM> of <FIG> is described having operations in a particular order, alternative embodiments may perform the method <NUM> with operations in a different order. For example, identifying the user (operation <NUM>) and determining the language preference (operation <NUM>) can occur after or while the transcript is generated (operation <NUM>) and prior to translating the transcript (operation <NUM>).

<FIG> is a block schematic diagram of a computer system <NUM> to implement and manage the handling of intelligent meetings via multiple distributed devices, edge devices, and cloud-based devices and for performing methods and algorithms according to example embodiments. All components need not be used in various embodiments.

One example computing device in the form of a computer <NUM> includes a processing unit <NUM>, memory <NUM>, removable storage <NUM>, and non-removable storage <NUM>. Although the example computing device is illustrated and described as computer <NUM>, the computing device may be in different forms in different embodiments. For example, the computing device may, instead, be a smartphone, a tablet, smartwatch, or other computing device including the same or similar elements as illustrated and described with regard to <FIG>. Devices, such as smartphones, tablets, and smartwatches, are generally collectively referred to as mobile devices, distributed devices, or user equipment.

Although the various data storage elements are illustrated as part of the computer <NUM>, the storage may also or alternatively include cloud-based storage accessible via a network, such as the Internet, server-based storage, or a smart storage device (SSD). Note also that an SSD may include a processor on which the parser may be run, allowing transfer of parsed, filtered data through I/O channels between the SSD and main memory.

Memory <NUM> may include volatile memory <NUM> and non-volatile memory <NUM>. Computer <NUM> may include - or have access to a computing environment that includes - a variety of computer-readable media, such as volatile memory <NUM> and non-volatile memory <NUM>, removable storage <NUM> and non-removable storage <NUM>. Computer storage includes random access memory (RAM), read only memory (ROM), erasable programmable read-only memory (EPROM) or electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD ROM), Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium capable of storing computer-readable instructions.

Computer <NUM> may include or have access to a computing environment that includes input interface <NUM>, output interface <NUM>, and a communication interface <NUM>. Output interface <NUM> may include a display device, such as a touchscreen, that also may serve as an input device. The input interface <NUM> may include one or more of a touchscreen, touchpad, mouse, keyboard, camera, one or more device-specific buttons, one or more sensors integrated within or coupled via wired or wireless data connections to the computer <NUM>, and other input devices. The computer may operate in a networked environment using a communication connection to connect to one or more remote computers, such as database servers. The remote computer may include a personal computer (PC), server, router, network PC, a peer device or other common data flow network switch, or the like. The communication connection may include a Local Area Network (LAN), a Wide Area Network (WAN), cellular, Wi-Fi, Bluetooth, or other networks. According to one embodiment, the various components of computer <NUM> are connected with a system bus <NUM>.

Computer-readable instructions stored on a computer-readable medium are executable by the processing unit <NUM> of the computer <NUM>, such as a program <NUM>. The program <NUM> in some embodiments comprises software to implement one or more methods for implementing the meeting app and meeting server, as well as the modules, methods, and algorithms described herein. A hard drive, CD-ROM, and RAM are some examples of articles including a non-transitory computer-readable device such as a storage device. The term computer-readable storage device does not include carrier waves to the extent carrier waves are deemed too transitory. Storage can also include networked storage, such as a storage area network (SAN). Computer program <NUM> along with the workspace manager <NUM> may be used to cause processing unit <NUM> to perform one or more methods or algorithms described herein.

As used herein, the terms "machine-storage medium," "device-storage medium," "computer-storage medium", "computer-readable storage medium," "computer-readable storage device" (referred to collectively as "machine-storage medium") mean the same thing and may be used interchangeably in this disclosure. The terms refer to a single or multiple storage devices and/or media (e.g., a centralized or distributed database, and/or associated caches and servers) that store executable instructions and/or data, as well as cloud-based storage systems or storage networks that include multiple storage apparatus or devices. The terms shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media, including memory internal or external to processors. Specific examples of machine-storage media, computer-storage media, and/or device-storage media include non-volatile memory, including by way of example semiconductor memory devices, e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), FPGA, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The terms machine-storage media, computer-storage media, and device-storage media specifically exclude carrier waves, modulated data signals, and other such media, to the extent such media are deemed too transitory. Other such media are also covered under the term "signal medium" discussed below. In this context, the machine-storage medium is non-transitory.

The term "signal medium" or "transmission medium" shall be taken to include any form of modulated data signal, carrier wave, and so forth. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a matter as to encode information in the signal.

Claim 1:
A computer-implemented method comprising:
receiving audio streams captured by a plurality of distributed devices (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>);
comparing the audio streams captured by the plurality of devices to determine whether the audio streams are representative of sound from a same meeting;
based on the comparing indicating the audio streams are representative of sound from the same meeting, establishing a meeting instance for a meeting, wherein the sound has an audio signature, the audio signature comprises an audio watermark generated by one or more of the distributed devices and having a sound that is inconspicuous to the user to cause a distributed device within range of the audio watermark to be added to the meeting instance;
identifying a user corresponding to a distributed device of the plurality of distributed devices (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>) in the meeting;
determining a preferred language of the user;
generating, by a hardware processor (<NUM>, <NUM>), a transcript from the received audio streams as the meeting is occurring;
translating the transcript into the preferred language of the user to form a translated transcript as the meeting is occurring; and
providing the translated transcript to the distributed device (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>) as the meeting is occurring.