Visualizing conversations across conference calls
11 claims: 6 independent, 5 dependent
- 1複数の関連する会議通話を行うステップと、 各会議通話のビジュアライゼーションを生成するステップであって、各会議通話のトランスクリプトを処理したテキスト表現を生成することと、前記複数の会議通話のそれぞれの前記ビジュアライゼーションの一部として前記テキスト表現を含めることとを含む、ステップと、 前記複数の会議通話の参加者のコンピューティング・デバイスに前記ビジュアライゼーションを送信するステップと、 前記複数の会議通話の うちの第1の会議通話の 選択された参加者の コンピューティング ・デバイスから、前記 第1 の会議通話に関連する新しい第2の会議通話を開始する要求を受信するステップと、 前記要求に応答して、前記第2の会議通話を開始するステップと、 前記第2の会議通話のビジュアライゼーションを生成するステップであって、前記第2の会議通話のトランスクリプトを処理したテキスト表現を生成することと、前記第2の会議通話の前記ビジュアライゼーションの一部として前記第2の会議通話のトランスクリプトを処理したテキスト表現を含めることとを含む、ステップと、 前記複数の会議通話の各参加者の前記コンピューティング・デバイスに送信される前記ビジュアライゼーションの一部として、前記第2の会議通話の前記ビジュアライゼーションを提供するステップと、を含む、方法。
- 2前記複数の会議通話のうち前記第1の会議通話の選択された参加者の コンピューティング ・デバイスから、前記第2の会議通話を指定する要求を受信するステップと、 前記 第2の会議通話を指定する 要求に応答して、前記第1の会議通話から前記選択された参加者の接続を切り、前記選択された参加者を前記第2の会議通話に接続するステップとをさらに含む、請求項1に記載の方法。
- 3ユーザの属性を判断するステップと、 前記属性を各会議通話の前記テキスト表現と比較するステップと 前記比較するステップに従って前記複数の会議通話の選択された1つを推奨するステップとをさらに含む、請求項1に記載の方法。
- 4前記 第2の会議通話の参加者は、前記第1の会議通話の参加者のサブセットである 、請求項1に記載の方法。
- 5各会議通話の前記ビジュアライゼーション内に、前記会議通話の前記参加者のリストを含めるステップをさらに含む、請求項1に記載の方法。
- 6複数の関連する会議通話を行うステップと、各会議通話のビジュアライゼーションを生成するステップであって、各会議通話のトランスクリプトを処理したテキスト表現を生成することと、前記複数の会議通話のそれぞれの前記ビジュアライゼーションの一部として前記テキスト表現を含めることとを含む、ステップと、 前記複数の会議通話の参加者のコンピューティング・デバイスに前記ビジュアライゼーションを送信するステップと、 前記複数の会議通話の うちの第1の会議通話の 選択された参加者の コンピューティング ・デバイスから、前記 第1 の会議通話に関連する 新しい第2の 会議通話を開始する要求を受信するステップと、 前記要求に応答して、前記第2の会議通話を開始するステップと、 前記第2の会議通話のビジュアライゼーションを生成するステップであって、前記第2の会議通話のトランスクリプトを処理したテキスト表現を生成することと、前記第2の会議通話の前記ビジュアライゼーションの一部として前記第2の会議通話のトランスクリプトを処理したテキスト表現を含めることとを含む、ステップと、 前記複数の会議通話の各参加者の前記コンピューティング・デバイスに送信される前記ビジュアライゼーションの一部として、前記第2の会議通話の前記ビジュアライゼーションを提供するステップとを含む実行可能な動作を開始するように構成されたプロセッサを含む、システム。
- 7前記プロセッサが、 前記複数の会議通話のうち前記第1の会議通話の選択された参加者の コンピューティング ・デバイスから、前記第2の会議通話を指定する要求を受信するステップと、 前記 第2の会議通話を指定する 要求に応答して、前記第1の会議通話から前記選択された参加者の接続を切り、前記選択された参加者を前記第2の会議通話に接続するステップとを含む実行可能な動作を開始するようにさらに構成された、請求項6に記載のシステム。
- 8前記プロセッサが、 ユーザの属性を判断するステップと、 前記属性を各会議通話の前記テキスト表現と比較するステップと、 前記比較するステップに従って、前記複数の会議通話のうちの選択された1つを推奨するステップとを含む実行可能な動作を開始するようにさらに構成された、請求項6に記載のシステム。
- 9コンピュータ可読プログラム・コードが、 複数の関連する会議通話を行うステップと、 各会議通話のビジュアライゼーションを生成するステップであって、各会議通話のトランスクリプトを処理したテキスト表現を生成することと、前記複数の会議通話のそれぞれの前記ビジュアライゼーションの一部として前記テキスト表現を含めることとを含む、ステップと、 前記複数の会議通話の参加者のコンピューティング・デバイスに前記ビジュアライゼーションを送信するステップと、 前記複数の会議通話の うちの第1の会議通話の 選択された参加者の コンピューティング ・デバイスから、前記 第1 の会議通話に関連する 新しい第2の 会議通話を開始する要求を受信するステップと、 前記要求に応答して、前記第2の会議通話を開始するステップと、 前記第2の会議通話のビジュアライゼーションを生成するステップであって、前記第2の会議通話のトランスクリプトを処理したテキスト表現を生成することと、前記第2の会議通話の前記ビジュアライゼーションの一部として前記第2の会議通話のトランスクリプトを処理したテキスト表現を含めることとを含む、ステップと、 前記複数の会議通話の各参加者の前記コンピューティング・デバイスに送信される前記ビジュアライゼーションの一部として、前記第2の会議通話の前記ビジュアライゼーションを提供するステップとを含む実行可能な動作を実行するように構成された、コンピュータ・プログラム。
- 10前記実行可能な動作が、 前記複数の会議通話のうち前記第1の会議通話の選択された参加者の コンピューティング ・デバイスから、前記第2の会議通話を指定する要求を受信するステップと、 前記 第2の会議通話を指定する 要求に応答して、前記第1の会議通話から前記選択された参加者の接続を切り、前記選択された参加者を前記第2の会議通話に接続するステップとをさらに含む、請求項9に記載のコンピュータ・プログラム。
- 11前記実行可能な動作が、 ユーザの属性を判断するステップと、 前記属性を各会議通話の前記テキスト表現と比較するステップと、 前記比較するステップに従って、前記複数の会議通話のうちの選択された1つを推奨するステップとをさらに含む、請求項9に記載のコンピュータ・プログラム。
Independent claims11
78 paragraphs, as filed
One or more embodiments disclosed herein relate to managing conference calls.
Modern organizations rely heavily on conference calls as a means of communication and cooperation between people in different locations. In some examples, the scope of topics discussed in a given conference call can vary significantly. You can initiate one or more additional conference calls to avoid confusion in the conference call. Each additional conference call is initiated with the purpose of continuing the discussion of one selected topic from the first conference call.
<p> Using multiple conference calls facilitates targeted conversations on multiple topics, but sharing information between conference calls becomes a problem.</p>
<p> One or more embodiments disclosed herein relate to managing conference calls and, more specifically, to visualizing conversations throughout the conference call.</p><p> One embodiment can include a method. The method can include making multiple related conference calls and generating a visualization of each conference call. Visualizations can be sent to the computing devices of multiple conference call participants at the same time as multiple conference calls.</p><p> Another embodiment can include a method. This method can include making a first conference call and a second conference call, the first conference call and the second conference call are related. A first textual representation of a first conference call can be generated. A second textual representation of the second conference call can be generated. The first textual representation can be sent to each participant's computing device in the second conference call.</p><p> Another embodiment can include a system. The system may include a processor configured to initiate one or more viable operations described herein.</p><p> Another embodiment can include a computer program product. This computer program product can include a computer-readable storage medium that incorporates computer-readable program code. The computer-readable program code can be configured to perform one or more executable actions described herein.</p>
<figref num="1">It is a block diagram which shows the system for making a conference call according to one Embodiment disclosed in this specification.</figref><figref num="2">It is a block diagram which shows the telephone conferencing system of FIG. 1 according to another embodiment disclosed in this specification.</figref><figref num="3">It is a block diagram which shows an example of the system according to another embodiment disclosed in this specification.</figref><figref num="4">FIG. 6 is a block diagram showing a view presented by a computing device in a user system according to another embodiment disclosed herein.</figref><figref num="5">FIG. 6 is a block diagram showing a window presented by a computing device in a user system according to another embodiment disclosed herein.</figref><figref num="6">It is a block diagram which shows the operation of the telephone conferencing system of FIG. 1 according to another embodiment disclosed in this specification.</figref><figref num="7">It is a flowchart which shows the method of providing the visualization according to another embodiment disclosed in this specification.</figref><figref num="8">It is a flowchart which shows the method of participating in a conference call according to another embodiment disclosed in this specification.</figref><figref num="9">It is a flowchart which shows the method of management of a conference call according to another embodiment disclosed in this specification.</figref>
As will be appreciated by those skilled in the art, aspects of the invention can be embodied as systems, methods, or computer program products. Accordingly, aspects of the present invention are complete hardware embodiments, complete software embodiments (including firmware, resident software, microcode, etc.), or combinations of software and hardware embodiments. Can take the form of, all of which are commonly referred to herein as "circuits," "modules," or "systems." Further, aspects of the invention can take the form of a computer program product embodied in one or more computer-readable media incorporating, eg, stored, computer-readable program code.
Any combination of one or more computer-readable media can be used. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any suitable combination of the above, but is not limited thereto. More specific examples (non-exhaustive lists) of computer-readable storage media include electrical connections with one or more wires, portable computer diskettes, hard disk drives (HDDs), and solid state drives. (SSD), Random Access Memory (RAM), Read Only Memory (ROM), Erasable Programmable Read Only Memory (EPROM or Flash Memory), Fiber Optic, Portable Compact Disk Read Includes only memory (CD-ROM), digital multipurpose disk (DVD), optical storage, magnetic storage, or any suitable combination of the above. In the context of this document, the computer-readable storage medium may be any tangible medium capable of accommodating or storing programs for use by, or in connection with, instruction execution systems, devices, or devices. it can.
Computer-readable signal media can include propagated data signals incorporating computer-readable program code, eg, in baseband or as part of a carrier wave. Such propagating signals can take any of various forms, including but not limited to electromagnetic, light, or any suitable combination thereof. A computer-readable signal medium is not a computer-readable storage medium, but any computer-readable medium that can convey, propagate, or transmit a program for use by, or in connection with, an instruction execution system, device, or device. It can be a medium.
Program code embedded in a computer-readable medium may include, but is not limited to, wireless, wired, fiber optic cable, RF, or any suitable combination described above, using any suitable medium. Can be sent. Computer program code for performing operations for aspects of the invention can be object-oriented programming languages such as Java (R), Smalltalk (R), C ++, and "C" programming languages or the like. It can be written in any combination of one or more programming languages, including traditional procedural programming languages such as programming languages. The program code is entirely on the user's computer, partly on the user's computer, partly as a stand-alone software package, partly on the user's computer and partly on the remote computer, or It can be run entirely on a remote computer or server. In the latter scenario, the remote computer can connect to the user's computer over any type of network, such as a local area network (LAN) or wide area network (WAN), or ( For example, you can connect to an external computer (over the Internet using an Internet service provider).
Aspects of the present invention will be described below with reference to flow charts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It will be appreciated that each block of the flow chart and / or block diagram, as well as the combination of blocks in the flow chart and / or block diagram, can be executed by computer program instructions. These computer program instructions are provided to the processor of a general purpose computer, dedicated computer, or other programmable data processor to create a machine that is executed by the processor of the computer, other programmable data processor, or other device. Instructions can provide a means for performing a function / operation specified in one or more blocks of a flowchart, a block diagram, or both.
These computer program instructions are also stored on a computer-readable medium that can instruct a computer, other programmable data processor, or other device to function in a particular way, and are stored on the computer-readable medium. Instructions can be made to produce a product that incorporates instructions that perform a function / operation specified in one or more blocks of a flowchart, a block diagram, or both.
Computer program instructions are also loaded onto a computer, other programmable data processor, or other device to perform a series of operating steps on the computer, other programmable device, or other device to perform a computer execution process. The instructions that are executed on a computer or other programmable device can provide the process for performing the functions / operations specified in one or more blocks of the flowchart and / or block diagram. it can.
One or more embodiments disclosed herein relate to managing conference calls and, more specifically, to visualizing conversations throughout the conference call. According to the mechanism of the invention disclosed herein, it is possible to provide participants in a plurality of conference calls with a visualization of the conversation taking place within each of the plurality of conference calls. While the conference call is in progress, each participant can see a visualization of multiple conference calls out of multiple conference calls. The visualization can, for example, present the subject of the conversation between the participants in each conference call in real time, or near real time.
Each participant can use the computing device to view the visualization. In addition, each participant can call the conference call management function through a computing device. In this regard, each participant can not only visually monitor the conversation taking place within each of the multiple conference calls, eg, throughout, but also through the computing device. You can manage specific conference calls (s) that are connected.
FIG. 1 is a block diagram showing a system 100 for performing a conference call according to one embodiment disclosed in the present specification. As shown, FIG. 1 shows a plurality of user systems 105, 110, 115, 120, and 125, each of which is communicably linked to the conference call system 135 over network 130. For illustration purposes, the terms "user" and "participant" are sometimes used interchangeably herein. In addition, references to specific users or participants may be used as a means of referring to a user system associated with or used by the mentioned user. Similarly, references to a particular user system may be used as a means of referring to a user or participant associated with the mentioned user system.
Continuing with Figure 1, each user system 105-125 can be associated with a particular participant. In general, each user system 105-125 can represent a participant's computing device and telephone associated with it. The computing devices in each user system 105-125 can execute program code, such as an application, thereby presenting a visualization of a conference call. In addition, each participant can make requests related to managing conference calls through the computing device of the user system. The telephones of each user system 105-125 can be configured to play audio from the conference call system 135 to the participants, capture the audio from the participants, and send the audio to the conference call system 135. The user system telephone can function as a mechanical device for a participant to actually participate in one or more conference calls as described herein.
Not surprisingly, each computing device and telephone in user systems 105-125 can be embodied in any of a variety of different formats. In one aspect, the computing device can be implemented independently of the telephone. For example, a computing device can be implemented as a computer, whether it is a desktop computer, a tablet computer, or a portable laptop computer. Thus, a computing device can be communicably linked to the conference call system 135 via the Internet, WAN, LAN, or any combination thereof, as represented by network 130. The telephone can be implemented as an analog telephone. In that case, the telephone can be communicably linked to the conference call system 135, for example via a public switched telephone system (PSTN). Telephones can also be implemented in the form of Voice Over Internet Protocol (VOIP) telephones. In that case, the telephone can also be coupled to the conference call system 135 via the Internet, WAN, LAN, or PSTN, or a combination thereof, as represented by network 130.
In another aspect, the computing device and the telephone can be implemented as a single device. For example, the computing device can be any of a variety of computing devices, and the phone can be implemented in the form of a software phone running on the computing device. Similarly, a computing device can be implemented, for example, in the form of a smart phone running a client application, and the phone can be implemented as part of the mobile phone of the smart phone. Obviously, when using a mobile phone, the mobile phone can be communicably linked to the conference call system 135 via a mobile communication network, also represented by network 130.
The various examples presented herein are for illustration purposes only and are not intended to limit the embodiments disclosed herein. For example, participants can use a smart phone as a computing device while using an analog phone or a separate VOIP phone as a user system in combination.
As shown, the user systems 105 and 110 are connected to a first conference call, called "conference call 1", made by the conference call system 135. The user systems 115-125 are connected to a second, different conference call made by the conference call system 135, called "conference call 2." For illustration purposes, conference call 1 and conference call 2 can be considered as related conference calls.
In one aspect, the conference call 2 can be a conference call initiated from the conference call 1. For example, conference call 1 can be a primary conference call, conference call 2 can be a secondary conference call, and participants in conference call 2 are a subset of the participants who were initially involved in conference call 1. In that respect, it is also called a "breakout" conference call. In this sense, conference call 1 and conference call 2 can be considered to be related. Each additional conference call that begins with conference call 1 or conference call 2 also derives from, or originally this, the same primary conference call, eg conference call 1 in this example, each of the resulting conference calls. Since it is related to, it can be regarded as a related conference call.
The telephone system 135 can include a number of different modules. In one aspect, the conference call system 135 is implemented in the form of one or more computer systems, such as a server, that execute computer program code configured to perform the functions described herein. can do. The conference call system 135 can include a call control module 140, a call processor 145, a speech-to-text (STT) processor 150, and a visualization processor 155.
The call control module 140 can be configured to receive requests from the computing devices of participants participating in a conference call. For example, referring to FIG. 1, the call control module 140 can receive a request to specify a conference call management instruction from a computing device in user systems 105-125. In response to the request, the call control module 140 sends a command to the call processor 145 to perform the actions necessary to perform the request received from the participant, eg, the participant in conference call 1 or conference call 2. , And / or implementation.
In general, the call processor 145 can be configured to manage audio streams to or from each of the participants corresponding to user systems 105-125. In general, the call processor 145 can perform functions such as combining audio streams to form conference call 1, conference call 2, etc. in response to commands received from call control module 140, for example. The call processor 145 also disconnects the participant from the current conference call to which the participant is joining, connects the participant to a different conference call, and initiates a new conference call in response to a command from the call control module 140. Or can interrupt an existing conference call.
The SST processor 150 can receive an audio stream of each of a plurality of conference calls, such as related conference calls such as conference calls 1 and 2, and perform voice recognition on each received audio stream. Therefore, the SST processor 150 can generally output a transcript of each audio stream (each associated conference call), such as speech recognized text. The visualization processor 155 can be configured to process a transcript of each conference call and generate a visualization that can include a textual representation of the conversation taking place in each conference call.
When a participant participates in one of the associated conference calls, such as a primary conference call, the participant can identify himself / herself to the conference call system 135. For example, each participant can call the conference call system 135 via the user system's telephone and connect to the conference call system 135 through the user system's computing device. For each participant, associate voice and data connections so that the conference call system 135 can correlate the audio stream sent to each participant with any visualization generated and transmitted. be able to.
In another embodiment, a directory service or other database containing a list of potential and / or actual participants in conference call 1 and conference call 2 is combined with the telephone conference system 135. be able to. Depending on determining the participant's identity, the conference call system 135 can query the directory service to determine one or more attributes of the participant. Examples of attributes can include, for example, a user's role or position, scope or subject of expertise, etc. within a company or other organization. Attributes can be compared to transcripts and / or visualizations of each associated conference call.
Depending on the match between the (one or more) attributes and the transcript, or visualization, or both, the conference call system 135 is one of several related conference calls for participants to join. Alternatively, multiple conference calls can be proposed. Participants can answer suggestions with a selected one of several related conference calls. The conference call system 135 can connect a participant to a conference call selected by the participant. In another aspect, the conference call system 135 can automatically connect a participant to a particular conference call that is determined to match or most closely match the participant's (s) attributes. ..
FIG. 2 is a block diagram showing a teleconferencing system 135 according to another embodiment disclosed herein. FIG. 2 provides an exemplary implementation of the conference call system 135. Therefore, FIG. 2 does not limit the embodiments disclosed herein. The same items are referred to throughout the specification using similar numbers.
As mentioned, the conference call system 135 can optionally be implemented in the form of one or more computing systems or servers. As shown, the call control module 140 can receive call control data 205 from one or more participants who are participating in or connected to one of a plurality of related conference calls. Call control data 205 can include one or more conference call management requests from one or more participants in a plurality of related conference calls. The call control module 140 can interpret the received request and issue a command to the call processor 145 to execute the received request.
The call processor 145 can receive audio streams 210 of one or more participants, as shown. The call processor 145 executes a plurality of related conference calls in response to a command received from the call control module 140, and processes various audio streams of the participant's audio stream 210 according to the command received from the call control module 140. , Can be connected to multiple related conference calls, such as selected conference calls. The call processor 145 can output a conference call audio stream 215 that represents the audio of each call in the associated conference call so that it can be delivered or distributed to the appropriate participants.
For illustration purposes, it can be assumed that there are three related conference calls. Thus, the SST processor 150 includes, for example, three SST modules 220, 225, and 230, for example instantiated. Each of the SST modules 220-230 can receive an audio stream of a conference call, for example the audio of a single conference call. Therefore, each SST module 220-230 can be configured to generate a text transcript that can be provided to each of the visualization modules 235-245 from the received audio stream.
Within the visualization processor 155, visualization modules 235 to 245 are instantiated to process the received text transcript. Each of the visualization modules 235-245 parses the incoming text transcription of the conversation taking place within a given conference call and produces one of each of the visualizations 250-260. Can be configured to: In one example, each of the visualizations 250-260 can contain a textual representation of the received audio stream. Each textual representation can be implemented as a summary of the text, eg, a processed or shortened version of the text transcript from which the visualization was derived. In one example, each text representation can be implemented as a tag cloud. In another example, each of the visualizations 250-260 can contain a text representation implemented as an edit of a text fragment, keyword, etc. Each of the visualizations 250-260 represents a conversation taking place in the corresponding one of the related conference calls.
Each of the visualizations 250-260 can be provided to the transmit module for transmission to each participant or selected participant in a plurality of related conference calls. In the example shown in FIG. 2, each of the visualizations 250-260 can be provided to the call control module 140. The call control module 140 can transmit each of the visualizations 250-260 to each of the participants in the associated conference call or to selected participants.
In one aspect, the text transcripts and visualizations generated and described with reference to FIG. 2 can be continuously updated and modified. For example, the SST module works continuously when it receives an audio stream, so instead of generating a static text transcript, the generated and output text transcript is real-time or near. It can be a stream of text provided in real time. Similarly, the visualizations generated can be real-time, or near-real-time, continuously updated or changing representations of conversations taking place in each conference call. In this regard, the state of the visualization reflects the state of the conversation in a given conference call at a particular point in time and changes as the conversation within the conference call changes. As used herein, the term "real time" means that the user or system detects that a particular action, or decision made, is sufficiently immediate, or causes the processor to maintain some external action. It can refer to the level of processing responsiveness that can be achieved.
Not surprisingly, Figure 2 is presented solely for illustration purposes. For example, the SST processor 150 and the visualization processor 155 have each been shown to contain multiple instances of a module, but in another embodiment a single module or processor, in some cases multiple audio streams. , And / or text transcripts can be processed. Such variations may depend on the speed of the computing system used and the amount or size of conference calls managed, made, or both. Therefore, the number of instances and the presence of a plurality of instances are not limited to the embodiments disclosed herein.
FIG. 3 is a block diagram showing an example of a system 300 according to another embodiment disclosed herein. In one aspect, the system 300 can represent the respective computing device of the various user systems described with reference to FIG. In another aspect, the system 300 can represent an implementation of the conference call system 135 of FIGS. 1 and 2, eg, a server data processing system. Not surprisingly, the size of the components described, as well as the particular operational software, application software, or both, will vary in System 300 depending on its use and implementation.
The system 300 may include at least one processor 305 coupled to the memory element 310 via system bus 315 or other suitable circuitry. Therefore, the system 300 can store the program code in the memory element 310. Processor 305 can execute program code accessed from memory element 310 via system bus 315. For example, in one embodiment, the system 300 can be implemented as a computer suitable for storing and / or executing program code. However, it will be appreciated that the system 300 can be implemented in the form of any system, including a processor and memory, capable of performing the functions and / or operations described herein.
The memory element 310 can include one or more physical memory devices, such as, for example, a local memory 320 and one or more mass storage devices 325. Local memory 320 refers to random access memory, or other non-persistent memory device (s) commonly used during the actual execution of program code. Mass storage (s) 325 can be implemented as a hard drive or other persistent data storage. System 300 also provides one or more cache memories that provide temporary storage of at least some program code in order to reduce the number of times program code must be retrieved from mass storage 325 during execution. (Not shown) can be included.
Input / output (I / O) devices such as keyboard 330, display 335, and pointing device 340 can optionally be combined with system 300. The I / O device can be coupled to the system 300 either directly or through an intervening I / O controller. One or more network adapters 345 are also coupled to system 300, where system 300 intervenes over a private or public network to another system, computer system, remote printer, or remote storage device. , Or a combination thereof. Examples of various types of network adapters 345 that can be used within System 300 include modems, cable modems, wireless transceivers, and Ethernet (R) cards.
FIG. 4 is a block diagram showing a view 400 presented by a computing device in a user system according to another embodiment disclosed herein. View 400 can be presented on the display of a participant's computing device while engaging in one of several related conference calls. In general, the data presented in view 400 can be data received from a conference call server, such as a call control module, as described with reference to FIGS. 1 and 2.
For the sake of explanation, consider the case where a primary conference call is in progress and includes multiple participants. At some point, a first breakout call, called "breakout call 1", is initiated. Several participants in the primary conference call leave the primary conference call and are connected to breakout call 1. In addition, at some point during the primary conference call, a second breakout call, called "breakout call 2", is initiated. Breakout call 2 begins with breakout call 1 or with a primary conference call. Therefore, the participants in breakout call 2 may be a subset of the participants in the primary conference call, or a subset of the participants in breakout call 1. In either case, the primary conference call, breakout call 1, and breakout call 2 can be considered as related conference calls.
View 400 shows an example of an interface that can be presented to one participant in a primary conference call, breakout call 1, or breakout call 2. In one aspect, each participant in a related conference call, ie, primary conference call, breakout call 1, or breakout call 2, or a combination thereof, is presented with view 400 through the participant's computing device. be able to. Thus, each participant can see and monitor conversations taking place within other related conference calls.
As shown, each conference call is represented in view 400 by one of windows 405, 410, and 415. Each of the windows 405 to 415 can include areas 420, 425, and 430, within which the visualization received from the conference call server can be displayed for the corresponding conference call. Therefore, within region 420, a visualization of the primary conference call is displayed. Within area 425, a visualization of Breakout Call 1 is displayed. Within area 430, a visualization of Breakout Call 2 is displayed. Each associated conference call can be represented by a view that presents a visualization of the call.
Each of windows 405-415 can also include areas 435, 440, and 445, respectively. Each of the regions 435-445 can display another aspect of the visualization of the corresponding conference call. A list of participants in each conference call can be displayed within each of the areas 435-445. Therefore, the participants of the primary conference call can be displayed in the area 435. Participants in breakout call 1 can be displayed in area 440. Participants in breakout call 2 can be displayed in area 445. In general, each of windows 405 to 415 can accommodate one conference call, and thus a visualization of that conference call (eg, one visualization).
As mentioned above, the visualizations presented inside each of the regions 420-430 can be dynamically updated over time to reflect the current state of the conversation as the conference call continues. Similarly, the list of participants displayed in each of regions 435-445 is dynamically updated over time as a conference call continues and participants move from one conference call to another. It can accurately reflect the participants of each conference call at a given time.
Each of windows 405 to 415 can contain a plurality of controls illustrated as activable buttons. In general, the "Close This Call" button in window 405 causes the user's computing device to respond to a participant's selection of the button and make a request to end the primary conference call in the conference call system. Can be sent to. The "Create Breakout Call" button inside each of windows 405-415 allows the participant's computing device to send a request to create a breakout call to the conference call system. The conference call system can respond to the request and make a breakout call as instructed.
The "Join this call" button inside each of windows 405-415 causes the user's computing device to request the conference call system to allow the user to join a particular conference call corresponding to the selected button. Can be sent. For example, in response to a participant selecting the "Join this call" button for Breakout Call 1, the participant's computing device will have a conference call for the participant to join Breakout Call 1. Requests can be sent to the system. In response to the request, the conference call system can disconnect the participant from the conference call to which the participant is currently connected, such as a primary conference call or breakout call 2, and connect the participant to breakout call 1. ..
As illustrated, using the visualizations and controls provided through View 400, each participant visually monitors the content of each of the relevant conference calls, such as the conversation, and between the relevant conference calls as desired. You can move freely. In one aspect, it is not necessary to include a specific control for disconnecting the conference call. For example, a conference call ends when there are no participants left in the conference call, whether it is a primary conference call or one of the breakout calls, or when, for example, only one user remains in the conference call. be able to. In the latter case, the conference call system can contact the user as to which of the related conference calls he / she wants to connect to or participate in the primary conference call. Participants can end a particular conference call by disconnecting the conference call system or by joining a different call.
FIG. 5 is a block diagram showing a window 500 according to another embodiment disclosed herein. Window 500 shows an interface that can be presented to participants by the computing device of the user system in response to selecting the "Create Breakout Call" button described with reference to FIG. ..
Using Window 500, participants who select the "Create Breakout Call" button can select a specific participant to include or invite to join the breakout call that will be created. can do. In one aspect, it can be selected from it, and the list of participants presented in window 500 can be the participants of a particular conference call with the "Create Breakout Call" button selected. .. For example, when the "Create Breakout Call" button corresponding to Breakout Call 1 is selected, the list of participants shown in area 505 of window 500 is assumed to be the participants connected in Breakout Call 1. be able to.
In response to selecting "Make a call", the participant's computing device can send a request to the conference call system to make a new breakout call. The conference call system can create a new breakout call and connect the selected participants, highlighted, to the newly created breakout call. In one aspect, the participant requesting the breakout call can be automatically included in the breakout call being created. In another aspect, participants are included only if they select themselves from the list of participants available in area 505.
In yet another embodiment, the list of participants available to connect to a new breakout call, as represented in Region 505, can be each participant across each of the existing and related conference calls. For example, the participants shown in region 505 can include each participant connected to a primary call, a breakout call 1, or a breakout call 2.
FIG. 6 is a block diagram showing the operation of the conference call system of FIG. 1 according to another embodiment disclosed herein. As shown, a primary conference call 605 is made with the associated conference calls shown as breakout call 610, breakout call 615, and breakout call 620. Each conference call has two or more participants, each associated with the user system as described.
Each participant in the primary conference call 605 can receive a visualization of the other related conference call shown in block 640. For example, each participant connected to primary conference call 605 can receive a visualization of breakout call 610, a visualization of breakout call 615, and a visualization of breakout call 620. In the embodiment shown in FIG. 6, the participant does not receive a visualization of the particular conference call to which the participant is currently connected. Therefore, participants in primary conference call 605 do not receive a visualization of primary conference call 605. However, as mentioned above, it will be appreciated that it is possible to present a visualization of the particular call to which the participant is currently connected so that each participant can see a visualization of each related call.
Each participant in the breakout call 610 can receive the visualization shown in block 625. For example, each participant in breakout call 610 can receive a visualization of primary conference call 605, a visualization of breakout call 615, and a visualization of breakout call 620. Each participant in the breakout call 615 can receive the visualization shown in block 630. For example, each participant in breakout call 615 can receive a visualization of primary conference call 605, a visualization of breakout call 610, and a visualization of breakout call 620. Finally, each participant in the breakout call 620 can receive the visualization shown in block 635. For example, each participant in breakout call 620 can receive a visualization of primary conference call 605, a visualization of breakout call 610, and a visualization of breakout call 615.
FIG. 7 is a flow chart illustrating method 700 to provide visualization according to another embodiment disclosed herein. Method 700 can be performed by a system such as the conference call system described with reference to FIGS. 1 and 2 herein. Method 700 can be initiated in a state in which a plurality of related conference calls have been initiated and are in progress.
At step 705, the conference call system can determine the participants in each associated conference call. For example, each participant can connect to the conference call system via the telephone and computing device portion of the user system described herein. In one aspect, the phone number each participant is talking to or other identity of each participant's audio stream can be associated with the address of each participant's computing device or other identity. , Thereby allowing the telephone conferencing system to associate each participant with a telephone and computing device. This interrelationship or association allows the conference call system to send accurate audio streams and accurate visualizations to each participant.
At step 710, the conference call system can generate an audio stream for each associated conference call. At step 715, the conference call system can generate a text transcript of each audio stream. At step 720, the conference call system can generate a visualization of each text transcript. For example, the visualization can be a text summary, a tag cloud, and so on. At step 725, the conference call system can send the visualization to the participants of the relevant conference call as described. As mentioned, for each conference call, the visualization can specify a list of participants in the conference call.
FIG. 8 is a flow chart illustrating a method 800 of participating in a conference call according to another embodiment disclosed herein. Method 800 can be implemented by a system such as the conference call system described with reference to FIGS. 1 and 2 herein. Further, Method 800 can be initiated with a plurality of related conference calls in progress.
At step 805, the user can connect to the conference call system. As mentioned, users can connect via telephone and via computing devices. For example, a user may attempt to connect to, eg, make, or join a primary conference call in a plurality of related conference calls.
In step 810, the conference call system can determine one or more attributes of the user based on the user's identification information. As described, the conference call system can access directory services, such as databases such as human resources databases. At step 815, the conference call system can compare a user's (s) attributes with their respective transcripts and / or visualizations of multiple related conference calls.
At step 820, the conference call system can propose a particular one (or more) of related conference calls for the user to join. Proposals can be made over the phone, for example using an interactive voice response system, or presented via the user's computing device. As described, in another embodiment, the conference call system can automatically connect the user to the conference call proposed in step 820. Alternatively, the conference call system can connect the user to this selected conference call, whether or not the conference call selected by the user is the same as the proposed conference call.
In another example, the user can be automatically connected to a primary conference call. Once the user's computing device begins to present management controls for visualization and conference calls, the user can move to any one of several related conference calls, as described herein. ..
In yet another example, a user can use a computing device to join a conference call. The user can connect to the conference call system to receive one audio portion of the call, or receive a visualization of the associated conference call without first joining it. Thus, the user may be presented with a visualization of one or more of the associated conference calls, or each of them, via a computing device. The user can then select, for example, a conference call among the related conference calls, and respond to that selection to be connected to the selected conference call, via, for example, the interface described herein. Is. More specifically, selecting a particular conference call allows the user to be connected to the audio portion of the selected call. The user can move from call to call as described.
FIG. 9 is a flowchart showing a conference call management method 900 according to another embodiment disclosed in the present specification. Method 900 can be implemented by a system such as the conference call system described with reference to FIGS. 1 and 2 herein. Method 900 can be initiated with multiple participants connected to the system and participating in multiple related conference calls. Of course, the system can be configured to continuously monitor the conference call management requests received from the participants. Method 900 can be initiated in response to receiving such a request.
At step 905, the system can receive a request from one participant in the associated conference call. As mentioned, participants can initiate a request by activating one of the conference call management buttons described with reference to Figure 4. At step 910, the system can determine the identity of the participant making the request.
At step 915, the system can determine the type of request received. For example, the system can determine whether the request is to join a different conference call among the associated conference calls or to create a breakout call. Method 900 can continue to step 925 in response to determining that the request is to join a different conference call of the associated conference calls. Method 900 can proceed to step 940 in response to determining that the request is to create a breakout call.
At step 925, the system can determine the current conference call for a plurality of related conference calls to which the participant issuing the request is connected. At step 930, the system can determine the target conference call. The target conference call can be a specific conference call among a plurality of related conference calls that the participant wishes to join. The target conference call can be specified in the request received by the system. At step 935, the system can disconnect the participant from the current conference call and connect the participant to the target conference call.
Not surprisingly, the conference call system can update the visualization provided to the requesting participant if necessary. For example, if a participant is provided with a visualization of each associated conference call, the visualization sent to the participant by the conference call system and thus received by the participant's computing system does not change. .. If the participant is not provided with a visualization of the conference call to which the participant is connected, the conference call system will stop sending the visualization of the conference call to which the participant is connected and the target conference call to which the participant is connected. Will start sending visualizations of.
Continuing step 940, the conference call system can determine the participants in the breakout call. Participants can be designated by the requesting participant, for example, as described with reference to FIG. At step 945, the conference call system can create or initiate a new breakout call. In step 950, the conference call system disconnects each participant identified in step 940 from the conference call to which that participant is connected (the current conference call), and each participant identified in step 940. Can be connected to a newly created breakout call.
Creating a breakout call as described, the conference call system determines the specific visualization to be provided to each of the participants identified in step 940 and sends the exact visualization as described above. can do. As mentioned, the visualization is continually updated with respect to the textual representation and the list of participants contained therein.
The flow charts and block diagrams in the figure show the architecture, function, and operation of possible executions of systems, methods, and computer program products according to various embodiments of the present invention. In this context, each block in a flowchart or block diagram contains a module, segment, or portion of code that contains one or more executable instructions to perform a specified logical function (s). Can be represented. Also note that in some alternative implementations, the functions shown in the blocks may be performed out of the order shown in the figure. For example, two blocks shown in succession may actually occur at substantially the same time, or the blocks may sometimes occur in reverse order, depending on the functionality involved. Also, each block of a block diagram and / or flowchart diagram, and / or a combination of blocks in a block diagram or flowchart diagram, or both, is a special purpose hardware-based system or special purpose hardware that performs a specified function or operation. Note that it can be executed by a combination of hardware and computer instructions.
The terms used herein are intended to describe a particular embodiment and are not intended to limit the invention. As used herein, the singular forms "a," "an," and "the" shall also include the plural, unless the context clearly indicates otherwise. The terms "include," "include," or "include," or a combination thereof, as used herein, are the features, or completeness, or steps, or actions, or elements, or configurations that they present. Specify the existence of an element, or a combination thereof, but exclude the existence or addition of one or more other features, or completeness, or steps, or actions, or elements, or components, or groups thereof, or a combination thereof. Please understand further that you do not.
References to "one embodiment," "one embodiment," or similar terms throughout this specification are described in connection with this embodiment in at least one embodiment disclosed herein. Means that it contains a particular feature, structure, or property. Thus, the phrase "in one embodiment", "in one embodiment", and similar terms throughout the specification may all refer to the same embodiment, but not necessarily.
The term "plurality" as used herein is defined as 2 or more. The term "another" as used herein is defined as at least a second or higher. As used herein, the term "or ... or both" refers to and includes any and all possible combinations of one or more of the related items listed. The present specification may use terms such as first, second, etc. to describe various elements, but these terms are used merely to distinguish one element from another. So it will also be understood that these elements should not be limited by these terms.
The term "case" may be interpreted to mean "sometimes," or "when," or "according to judgment," or "according to detection," depending on the context. it can. Similarly, the phrase "when judged" or "when [specified conditions or events] are detected" may be "in judgment" or "in judgment", depending on the context. , Or "when detecting [specified conditions or events]", or "in response to the detection of [specified conditions or events]" can be interpreted to mean.
The corresponding structures, materials, acts, and equivalents of all Means Plus Function Elements or Step Plus Function Elements within the appended claims are other claims as specifically claimed. It shall include any structure, material, or act to perform a function in combination with the elements. The description of the present invention has been presented for purposes of illustration and illustration, but is not intended to be exhaustive or limited to the disclosed forms of the invention. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and gist of the present invention. Embodiments are provided to best illustrate the principles and practical applications of the invention and to help those skilled in the art understand the invention for various embodiments with various modifications suitable for the particular application expected. Selected and explained.
9 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9
Every citation, both ways
| Document | Relation | Office |
|---|---|---|
| JP2006237864A | Cites | Japan |
| WO2008114811A1 | Cites | World Intellectual Property Organization (WIPO) |
| WO2008050649A1 | Cites | World Intellectual Property Organization (WIPO) |
10 members in 4 offices
Priority claims9
| Document | Office | Kind | Date |
|---|---|---|---|
| 13361124 | United States of America | – | |
| 201213361124 | United States of America | A | |
| 201213361124 | United States of America | A | |
| 2013050069 | Canada | W | |
| 2013050069 | Canada | W | |
| 13361124 | – | – | – |
| CA2013050069 | – | – | – |
| US201213361124 | – | – | – |
| WO2013CA50069 | – | – | – |
Members10
| Document | Office | Kind | |
|---|---|---|---|
| US2013195259A1 | United States of America | A1 | |
| US2013195260A1 | United States of America | A1 | |
| WO2013113118A1 | World Intellectual Property Organization (WIPO) | A1 | |
| CN104067603A | China | A | |
| JP2015510716A | Japan | A | |
| US10177926B2 | United States of America | B2 | |
| US10200205B2 | United States of America | B2 | |
| JP6468842B2This record | Japan | B2 | |
| US2019103985A1 | United States of America | A1 | |
| US10574473B2 | United States of America | B2 |
13 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Re-examination (zenchi) completed and case transferred to appeal boardAppealJAPANESE INTERMEDIATE CODE: A912A912 | A912 | |
| Transfer to examiner for re-examination before appeal (zenchi)AppealJAPANESE INTERMEDIATE CODE: A911A911 | A911 | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Decision of refusalJAPANESE INTERMEDIATE CODE: A02A02 | A02 | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Report on retrievalJAPANESE INTERMEDIATE CODE: A971007A977 | A977 | |
| Written request for application examinationJAPANESE INTERMEDIATE CODE: A621A621 | A621 |
Numbers
- Publication
- 6468842
- Publication, DOCDB
- 6468842
- Publication, EPODOC
- JP6468842B
- Application
- 2014553591
- Application, DOCDB
- 2014553591
- Application, EPODOC
- JP20140553591
Titles2
- Japanese
- 会議通話全体の会話を視覚化する方法、システム、およびコンピュータ・プログラム製品
- English
- How to visualize conversations throughout a conference call, systems, and computer program products
Classification
- CPC, 3
- H04L12/1822
- H04L65/403
- H04L65/1083
- IPC, 3
- H04M3 56
- H04L12 18
- H04M3 42
