Conference message notification method and electronic equipment

Abstract

The invention provides a conference message notification method and electronic equipment. The conference message notification method comprises the following steps: receiving a first text message from a first application; based on the first character message, obtaining a first PCM data stream corresponding to the first character message; writing the first PCM data stream into a sound mixer of the electronic equipment; and transmitting an audio data stream through the second application, wherein the audio data stream comprises the first PCM data stream.

Description

Technical Field

[0001] This application relates to the field of electronic technology, and more particularly to a method and electronic device for notifying conference messages. Background Technology

[0002] In recent years, with the widespread adoption of online meetings, the demand for intelligent meeting assistants has continued to grow. Currently, most meeting systems natively integrate AI assistants, such as Microsoft Teams Copilot and Tencent Meeting AI Assistant. These AI assistants can provide functions such as meeting minutes generation and content Q&A. However, this function requires uploading meeting data to cloud servers, which may pose a data breach risk to enterprises with high data security requirements.

[0003] In related technologies, third-party meeting AI assistants can be deployed on users' local devices. By running locally, the risk of data leakage is avoided. However, because third-party meeting AI assistants are independent of the meeting system, they cannot send real-time notifications to other meeting participants through the meeting platform when taking meeting notes or activating AI-powered automatic responses. This also affects the user experience. Therefore, there is an urgent need for a new way to improve these issues. Summary of the Invention

[0004] In view of this, embodiments of this application provide at least one method and electronic device for notifying meeting messages.

[0005] The technical solution of this application embodiment is implemented as follows: In a first aspect, embodiments of this application provide a method for notifying meeting messages, the method comprising: Receive the first text message from the first application; Based on the first text message, obtain the first PCM data stream corresponding to the first text message; Write the first PCM data stream into the mixer of the electronic device; An audio data stream is sent via a second application, the audio data stream including a first PCM data stream.

[0006] Secondly, embodiments of this application provide an electronic device, which includes a sound card driver component; A sound card driver component is used to receive a first text message from a first application; obtain a first PCM data stream corresponding to the first text message based on the first text message; write the first PCM data stream into the mixer of an electronic device; and send an audio data stream, the audio data stream including the first PCM data stream, through a second application.

[0007] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory, and are not intended to limit the technical solutions of this application. Attached Figure Description

[0008] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with this application and, together with the specification, serve to explain the technical solutions of this application.

[0009] Figure 1 A schematic diagram of the structure of a conference system provided in this application embodiment; Figure 2 A schematic diagram of the implementation process of a meeting message notification method provided in this application embodiment. Figure 1 ; Figure 3 A schematic diagram of the implementation process of a meeting message notification method provided in this application embodiment. Figure 2 ; Figure 4 A schematic diagram of the implementation process of a meeting message notification method provided in this application embodiment. Figure 3 ; Figure 5 A schematic diagram of the implementation process of a meeting message notification method provided in this application embodiment. Figure 4 ; Figure 6 A schematic diagram of another conference system provided in this application embodiment; Figure 7 This is a schematic diagram of a hardware entity of an electronic device in an embodiment of this application. Detailed Implementation

[0010] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application are further described in detail below with reference to the accompanying drawings and embodiments. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0011] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0012] The terms “first / second / third” are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that “first / second / third” may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0013] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. The terminology used herein is for descriptive purposes only and is not intended to limit the scope of this application.

[0014] To address the problems in related technologies, embodiments of this application provide a method for notifying meeting messages. This method can be applied to electronic devices. Exemplarily, the electronic devices include, but are not limited to, smartphones, tablets, wearable devices, personal computers (PCs), netbooks, etc. The implementation form of this application is not fixed or limited.

[0015] Figure 1 This is a schematic diagram of a conference system provided as an embodiment of this application. Figure 1 As shown, the conference system includes a conference cloud service 101, a conference machine 102, and multiple electronic devices 103.

[0016] Here, the conference cloud service 101 is used to synchronize data between multiple electronic devices to support real-time communication between conference participants. In some examples, the conference cloud service 101 receives voice, video, or text data from different electronic devices and performs routing and forwarding operations to ensure smooth multi-party communication.

[0017] Conference machine 102 is a dedicated conference room terminal device used to provide full-featured audio and video processing capabilities. Conference machine 102 is equipped with a second application. For example, the second application is a conference application, which performs audio and video data acquisition, encoding, transmission, decoding, and playback to realize conference functions.

[0018] Multiple electronic devices 103 correspond to multiple meeting participants and are used to input and output multimedia data during the meeting. For example, electronic devices 103 can be terminal devices such as computers or mobile phones. Each of the multiple electronic devices has a first application and a second application installed. For example, the first application is a meeting assistant application, which is used to assist in implementing additional meeting functions beyond basic communication.

[0019] During the meeting, when a user corresponding to any electronic device 103 speaks, the second application installed on that electronic device 103 collects the corresponding meeting data stream (such as audio, video, and text data) and uploads it to the meeting cloud service 101. After processing the meeting data stream, the meeting cloud service 101 distributes the processing results to other electronic devices 103 and the meeting machine 102, so that all meeting participants can receive clear audio and video content and shared materials in real time, realizing remote collaborative meetings.

[0020] However, in Figure 1 In the conference system shown, each electronic device needs to upload conference data to the conference cloud service, posing a risk of privacy leakage. Although a conference assistant application can be used to protect some data, it does not support sending system notifications to conference participants or providing automatic responses based on the conference audio stream, thus limiting the system's functional integrity and impacting the user experience.

[0021] In view of the above problems, such as Figure 2 As shown, some embodiments of this application provide a method for notifying the meeting message, which can be implemented through steps S201-S204: S201, Receive the first text message from the first application.

[0022] Here, the first application can be a meeting assistant application or a third-party application such as an AI meeting assistant application; this application does not impose any restrictions on this.

[0023] The first text message can be a text message generated by the first application in different scenarios. For example, in a scenario where a user leaves; or in a scenario where meeting content needs to be recorded. This application does not limit the scenario in which the first text message is generated.

[0024] In some examples, the electronic device includes a first application and a second application. Here, the second application is a conferencing application, such as Zoom, Microsoft Teams, Webex, etc.

[0025] During the meeting, the first application can monitor the entire meeting process in real time. When the first application recognizes that a message needs to be sent to other meeting participants, it can first generate a first text message corresponding to that message and send the first text message to the electronic device.

[0026] S202. Based on the first text message, obtain the first PCM data stream corresponding to the first text message.

[0027] Typically, the second application (i.e., the conferencing application) uses the electronic device's mixer (also known as an audio mixer) to acquire the input data stream from the microphone, and then sends the acquired audio data stream to other meeting participants. In order for the first text message to be sent to all meeting participants via the second application, it is necessary to ensure that the first text message can be properly processed by the mixer.

[0028] Since the mixer processes and temporarily stores only audio data, it cannot directly recognize or store the original text information. Therefore, to achieve the above objective, the first text message needs to be converted into its corresponding audio format. That is, the electronic device converts the first text message into a corresponding first PCM data stream. The generated first PCM data stream can then be fed into the mixer, and the second application can acquire it like a regular input audio stream and send it to all participants in the conference.

[0029] S203, Write the first PCM data stream into the mixer of the electronic device.

[0030] After obtaining the first PCM data stream, the first PCM data stream can be written into the mixer of the electronic device.

[0031] In some examples, the process of writing a first PCM data stream to the mixer of an electronic device may include: the electronic device calling its underlying audio interface (e.g., the audio API provided by the Windows operating system (Windows AudioSession API, WASAPI)) to write the first PCM data stream to the mixer of the electronic device. Specifically, the electronic device may write the first PCM data stream into the mixer's buffer.

[0032] Furthermore, the process of writing the first PCM data stream into the mixer of the electronic device can also be as follows: the electronic device calls the audio interface and writes the first PCM data stream into a buffer managed by the mixer (e.g., KMixer in the Windows kernel audio engine) according to the preset sampling rate, bit depth and number of channels.

[0033] For example, KMixer is an audio mixing component. KMixer continuously polls the buffer, and if it detects the first PCM data stream in the buffer, it acquires the first PCM data stream. Subsequently, KMixer processes the acquired first PCM data stream together with other audio streams playing on the electronic device (such as data from a media player, system notifications, or microphone), and finally outputs an audio data stream.

[0034] S204. Send an audio data stream via a second application, the audio data stream including a first PCM data stream.

[0035] After the electronic device stores the first PCM data stream into the mixer, the second application can retrieve the audio data stream from the mixer. Subsequently, the electronic device can use the second application to send the audio data stream to all participants in the meeting, thus ensuring that the first PCM data stream in the audio data stream is also successfully sent to all participants.

[0036] In this embodiment, by leveraging the characteristics of a mixer in an electronic device, the first text message of the first application is first converted into a first PCM data stream, then integrated into an audio data stream and sent to all meeting participants. This allows for the proactive transmission of the first PCM data stream without relying on open interfaces of the conferencing software. Furthermore, it eliminates the need to bind to specific conferencing tools, possessing broad cross-platform and cross-software compatibility, and enables message synchronization via audio, preventing privacy data leaks and comprehensively enhancing the flexibility and practicality of meeting communication.

[0037] In some examples, S201 receives a first text message from the first application, including: S2011. During the meeting, the meeting audio data instructs the meeting participants to send an inquiry to the user. If the user does not respond to the inquiry within a preset time, the first text message from the first application is received.

[0038] In some examples, the process by which the first application identifies inquiries from meeting participants to the user may include: the first application acquiring meeting audio data during the meeting via a speaker, parsing the meeting audio data, and determining, based on the parsing results, inquiries from other meeting participants to the user during the meeting.

[0039] The process by which the first application identifies when a user leaves may include: the first application continuously monitors the user's interaction with the electronic device, and if no interaction is detected within a preset time period, the application determines that the user has left.

[0040] The process by which the first application identifies when a user leaves may also include: the user clicking on a managed control in the first application's display interface; and the first application determining that the user has left in response to the click on the managed control in the first application's display interface. For example, in the first application's display interface, the user can click on the icon of the managed control with the mouse or use a shortcut key to activate the corresponding managed function of the managed control.

[0041] The process by which the first application identifies a user leaving may include: when the meeting audio data during the meeting instructs a participant to send an inquiry to the user; if the first application does not detect that the user has not responded to the inquiry within a preset time, then it determines that the user has left. Of course, the first application may also identify a user's temporary departure through other means, and this application does not impose any restrictions on this.

[0042] The application monitors the entire meeting in real time. When a user leaves and other participants ask them a question, the application generates a first text message. This message can include messages such as: "User is temporarily away. Your question will be recorded and answered when they return." This timely notification to other participants ensures the meeting proceeds efficiently and smoothly.

[0043] In this embodiment, if a user does not respond for an extended period after a meeting inquiry, an automatic response is provided via a first text message. This solves the problem of users being unable to respond promptly when temporarily absent, while also ensuring that all meeting participants are aware of the situation and maintaining the continuity of meeting communication.

[0044] In some examples, S201 receives a first text message from the first application, including: S2012. When the meeting audio data during the meeting indicates that the meeting content should be recorded, receive the first text message corresponding to the recorded meeting content.

[0045] In some examples, when the meeting audio data during a meeting indicates that the meeting content should be recorded, the process of receiving a first text message corresponding to the recorded meeting content may include: a first application acquiring the meeting audio data during the meeting in real time through a speaker and parsing the meeting audio data; determining, based on the parsing result, that the meeting audio data during the meeting indicates that the meeting content should be recorded; the first application generating a first text message corresponding to the recorded meeting content based on the meeting audio data; and sending the first text message corresponding to the recorded meeting content to an electronic device, which then receives the first text message corresponding to the recorded meeting content.

[0046] In this embodiment of the application, in the scenario of recording meeting content, the recording-related information is synchronized to all meeting participants through a first text message. This not only solves the problem of notifying all participants of the recorded content, but also avoids the risk of data privacy leakage that may be caused by relying on software interfaces, thus enriching the application scenarios and security of meeting recording.

[0047] In some examples, S202 obtains the first PCM data stream corresponding to the first text message based on the first text message, including: S2021. Input the first text message into the text-to-speech conversion model to obtain the first PCM data stream corresponding to the first text message.

[0048] Here, the Text-to-Speech (TTS) model is used to convert text information into speech signals for output. This TTS model can be implemented through various architectures, such as end-to-end deep learning-based models (e.g., Tacotron, VITS), or traditional pipeline models that combine acoustic models with vocoders.

[0049] In addition, the TTS model supports generating various forms of voice output. Depending on the application scenario, it can output directly playable audio stream formats (such as PCM data streams) or compressed audio formats suitable for storage or network transmission (such as MP3 and WAV files), thus adapting to diverse application scenarios.

[0050] In some examples, the process of inputting a first text message into a text-to-speech conversion model to obtain the corresponding first PCM data stream may include: inputting the first text message into the text-to-speech conversion model, and the text-to-speech conversion model outputting the corresponding first PCM data stream. Of course, the first text message can also be converted into a first PCM data stream in other ways, and this application does not impose any limitations on this.

[0051] In this embodiment, a first PCM data stream corresponding to the first text message is generated through a text-to-speech conversion model, ensuring the accuracy of the conversion from the first text message to the first PCM data stream. This method requires no manual intervention and can complete the conversion quickly and automatically, improving conversion efficiency while ensuring the quality of the audio data stream.

[0052] In some examples, after S203 writes the first PCM data stream to the mixer of the electronic device, the notification method for the conference message also includes: S205. Perform audio processing on the first PCM data stream and the input data stream from the microphone to obtain an audio data stream.

[0053] Typically, a mixer stores not only the first PCM data stream but also the input data stream from the microphone. Therefore, after the first PCM data stream is written to the mixer, the mixer processes the first PCM data stream and the microphone input data stream together to obtain an audio data stream, which is then output to the second application.

[0054] In this embodiment, after writing the first PCM data stream into the mixer, the first PCM data stream and the microphone input data stream are processed to generate the final audio data stream, thus achieving the fusion transmission of the first PCM data stream corresponding to the first text message and the user's input data stream. This simplifies the operation process, integrates the first PCM data stream and the input data stream for transmission, ensures the naturalness and effectiveness of the first PCM data stream, and improves the continuity of meeting communication.

[0055] In some examples, S205 performs audio processing on the first PCM data stream and the input data stream from the microphone to obtain an audio data stream, including: S2051. Mix and echo cancel the first PCM data stream and the input data stream to obtain an audio data stream.

[0056] In some examples, the process of mixing and echo-cancelling the first PCM data stream and the input data stream to obtain an audio data stream may include: mixing the first PCM data stream and the input data stream to obtain a mixed data stream; and performing echo-cancelling on the mixed data stream to obtain an audio data stream.

[0057] Specifically, the mixing process for the first PCM data stream and the input data stream can be as follows: the amplitude values ​​of the two audio signals, the first PCM data stream and the input data stream, are superimposed to generate a mixed data stream containing all audio elements.

[0058] Echo cancellation processing is applied to the mixed data stream to obtain the audio data stream. Specifically, this involves using adaptive filtering technology, with the first PCM data stream as a reference signal, to analyze the echo features in the mixed data stream, and then canceling them based on the analysis results to obtain the audio data stream. In this way, the resulting audio data stream retains the speech components from both the input data stream and the first PCM data stream while effectively removing echo interference, thus providing high-quality audio transmission for remote communication.

[0059] In this embodiment, the first PCM data stream and the input data stream are fused through mixing processing, and then the audio quality of the audio data stream can be improved through echo cancellation processing. This ensures that both audio streams are clearly presented while avoiding the impact of noise and echo on meeting communication, thus improving the quality and experience of meeting communication.

[0060] Figure 3 A schematic diagram of the implementation process of a meeting message notification method provided in this application embodiment. Figure 2 ,like Figure 3 As shown, step S204, sending the audio data stream through the second application, includes: S301, In response to an audio acquisition request triggered when the second application is in a non-mute state, read the audio data stream from the mixer.

[0061] In some examples, the process of reading an audio data stream from a mixer in response to an audio retrieval request triggered by a second application being in a non-mute state may include: the second application, being in a non-mute state, sending an audio retrieval request to an electronic device; and the electronic device, in response to the second application's audio retrieval request, reading an audio data stream from the mixer.

[0062] The specific process by which an electronic device reads an audio data stream from a mixer in response to an audio acquisition request from a second application can be as follows: by calling the audio interface of the electronic device (such as WASAPI) to read the audio data stream from the mixer.

[0063] When the second application is not muted, it actively sends an audio acquisition request to the electronic device to obtain the input audio stream captured by the microphone. Typically, the input audio stream captured by the microphone is written to the mixer in real time by the electronic device's audio service. Since the first PCM data stream has also been written to the mixer, the audio data stream obtained by the electronic device from the mixer includes both the input audio stream from the microphone and the first PCM data stream.

[0064] Based on the above, in order for the first text message from the first application to be sent to all meeting participants as a first PCM data stream, the second application needs to be in an unmute state. When the second application is muted, it will not acquire the input audio stream through the microphone, and correspondingly, it will not acquire the audio data stream through the mixer. Ultimately, the first PCM data stream will not be sent to any meeting participants during the meeting.

[0065] S302, Send an audio data stream to the second application.

[0066] After reading the audio data stream from the mixer, the electronic device can send the audio data stream to the second application in response to an audio acquisition request triggered when the second application is in a non-mute state. Upon receiving the audio data stream, the second application can send it to all meeting participants in the form of voice or text.

[0067] In this embodiment, the audio acquisition request is responded to and data is sent only when the second application is not in a silent state. This avoids the problem of message sending failure in a silent state, ensures that the first PCM data stream can be accurately transmitted to all participants, and guarantees the effectiveness and timeliness of meeting communication.

[0068] Figure 4 A schematic diagram of the implementation process of a meeting message notification method provided in this application embodiment. Figure 3,like Figure 4 As shown, before the audio acquisition request triggered when the second application is in a non-mute state in step S301, the method further includes: S401: The second application was detected to be in a silent state.

[0069] As described in S301 above, the first PCM data stream can only be sent to all meeting participants when the second application is in a non-mute state. Therefore, after receiving the first text message from the first application, the electronic device needs to periodically monitor whether the second application is in a non-mute state to ensure that the first PCM data stream can be sent normally to all meeting participants.

[0070] S402: Send a mute control command to the second application to control the second application to switch from a mute state to a non-mute state.

[0071] When the second application is in a silent state, it can be switched from a silent state to a non-silent state by using the mute control command.

[0072] In some examples, the process of sending a mute control command to a second application to control the second application to switch from a mute state to a non-mute state may include: the electronic device sending a mute control command to the second application, the second application receiving the mute control command; and the second application responding to the mute control command by switching from a mute state to a non-mute state.

[0073] For example, in a Windows operating system environment, the mute control command can be implemented by calling the IAudioSessionControl::SetMute(false) interface. In a macOS operating system environment, it can be implemented using the corresponding function provided by the Core Audio audio framework.

[0074] When the system-level audio interface cannot be directly invoked, the mute control command can also use the UI automation framework to locate and simulate the triggering of the "unmute" button in the second application interface; or send a preset shortcut key signal to the display window of the second application to control the second application to switch from a mute state to a non-mute state.

[0075] In this embodiment, when the second application is detected to be muted, the user can switch to a non-mute state via a mute control command, eliminating the need for manual operation and further improving ease of use. This also solves the problem of messages failing to send due to the user forgetting to unmute, ensuring the smooth transmission of the first PCM data stream and guaranteeing the continuity of meeting communication.

[0076] Figure 5A schematic diagram of the implementation process of a meeting message notification method provided in this application embodiment. Figure 4 ,like Figure 5 As shown, the notification methods for this meeting message also include: S501, Convert the audio data stream into a second text message.

[0077] In some examples, when a participant is speaking during a meeting, to avoid privacy breaches or disruption to the user's participation due to playback, the electronic device can convert the audio data stream from the mixer into a second text message and display it as text on the second application's screen. This achieves message notification while also meeting user needs.

[0078] S502, Send a second text message through the second application.

[0079] Once the electronic device converts the audio data stream into a second text message, it can send the second text message to a second application, which can then send the second text message to all meeting participants.

[0080] When the second application receives the second text message, the second text message can be displayed in a specific area of ​​the second application's interface, such as a sidebar or a floating window, thus ensuring that it does not interfere with the normal progress of the meeting.

[0081] Of course, electronic devices can send a second text message to a second application while simultaneously sending an audio data stream, enabling multi-type transmission of audio and text messages to meet the needs of different scenarios. For example, if no participant speaks during a meeting, the audio data stream can be played through the speaker; if a participant speaks normally during a meeting, the second text message can be displayed in the second application.

[0082] In this embodiment, by converting the audio data stream into a second text message and sending it, text-based transmission can be achieved. This ensures that all meeting participants can accurately obtain the information, while also solving the notification problem in privacy protection scenarios and improving the flexibility and coverage of message delivery.

[0083] Combination Figure 1 , Figure 6 A schematic diagram of another conference system provided in this application embodiment. See also... Figure 6 It can be seen that the conference system includes a conference cloud service 101, a conference machine 102, and multiple electronic devices 103. The functions of the conference cloud service 101, the conference machine 102, and the multiple electronic devices 103 are similar to... Figure 1 The descriptions in the corresponding embodiments are similar and will not be repeated here.

[0084] It should be noted that each electronic device 103 also includes a sound card driver component 601 and a microphone 603, and the sound card driver component 601 includes a mixer 602.

[0085] The sound card driver component 601 is located in the hardware abstraction layer of the electronic device and is used to control physical hardware such as the microphone 603 and the speaker, and to perform mixing and encoding / decoding processing on the audio data stream.

[0086] During the meeting, electronic device 103 acquires the input audio stream via microphone 603 and writes it to mixer 602 via sound card driver component 601. Simultaneously, sound card driver component 601 in electronic device 103 can also receive a first text message from the first application, convert the first text message into a first PCM data stream, and write it to mixer 602 as well. Mixer 602 mixes the input audio stream and the first PCM data stream to generate a unified audio data stream. The second application can then read the audio data stream through the audio interface and send it via the network to meeting cloud service 101, which then distributes the audio data stream to all meeting participants.

[0087] In some examples, the sound card driver component 601 is used to receive a first text message from a first application; obtain a first PCM data stream corresponding to the first text message based on the first text message; write the first PCM data stream into the mixer of an electronic device; and send an audio data stream, including the first PCM data stream, through a second application.

[0088] In some examples, the sound card driver component 601 is also used to instruct meeting participants to send an inquiry to the user during the meeting audio data, and to receive a first text message from the first application if the user does not respond to the inquiry within a preset time.

[0089] In some examples, the sound card driver component 601 is also used to receive a first text message corresponding to the recorded meeting content when the meeting audio data during the meeting indicates that the meeting content should be recorded.

[0090] In some examples, the sound card driver component 601 is also used to input the first text message into a speech conversion model to obtain the first PCM data stream corresponding to the first text message.

[0091] In some examples, the sound card driver component 601 is also used to perform audio processing on the first PCM data stream and the input data stream from the microphone to obtain an audio data stream.

[0092] In some examples, the sound card driver component 601 is also used to perform mixing and echo cancellation processing on the first PCM data stream and the input data stream to obtain an audio data stream.

[0093] In some examples, the sound card driver component 601 is also configured to read an audio data stream from the mixer and send an audio data stream to the second application in response to an audio acquisition request triggered when the second application is in a non-mute state.

[0094] In some examples, the sound card driver component 601 is also used to detect that the second application is in a muted state; and to send a mute control command to the second application to control the second application to switch from a muted state to a non-mute state.

[0095] In some examples, the sound card driver component 601 is also used to convert the audio data stream into a second text message; and to send the second text message through a second application.

[0096] The descriptions of the above device embodiments are similar to those of the above method embodiments, and have similar beneficial effects. In some embodiments, the electronic device provided in this application may have functions or include modules that can be used to perform the methods described in the above method embodiments. For technical details not disclosed in the device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0097] It should be noted that, in the embodiments of this application, if the above-mentioned meeting message notification method is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, or the part that contributes to the related technology, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, mobile hard drives, read-only memory (ROM), magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware, software, or firmware, or any combination of hardware, software, and firmware.

[0098] This application provides a computer device including a memory and a processor. The memory stores a computer program that can run on the processor. When the processor executes the program, it implements some or all of the steps in the above-described method.

[0099] This application provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements some or all of the steps in the above-described method. The computer-readable storage medium can be transient or non-transient.

[0100] This application provides a computer program including computer-readable code. When the computer-readable code is run in a computer device, the processor in the computer device performs some or all of the steps for implementing the above-described method.

[0101] This application provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program. When the computer program is read and executed by a computer, it implements some or all of the steps in the above-described method. This computer program product can be implemented specifically through hardware, software, or a combination thereof. In some embodiments, the computer program product is specifically embodied as a computer storage medium; in other embodiments, the computer program product is specifically embodied as a software product, such as a software development kit (SDK), etc.

[0102] It should be noted that the descriptions of the various embodiments above tend to emphasize the differences between them, while their similarities or commonalities can be referred to interchangeably. The descriptions of the above embodiments of the device, storage medium, computer program, and computer program product are similar to the descriptions of the above method embodiments and have similar beneficial effects. For technical details not disclosed in the embodiments of the device, storage medium, computer program, and computer program product of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0103] Figure 7 This is a schematic diagram of a hardware entity of an electronic device in an embodiment of this application, such as... Figure 7 As shown, the hardware entity of the electronic device 700 includes: a processor 701, a communication interface 702, and a memory 703. Wherein: The processor 701 typically controls the overall operation of the electronic device 700, which may be the method for notifying meeting messages provided in the embodiments of this application.

[0104] The communication interface 702 enables the electronic device 700 to communicate with other terminals or servers via a network.

[0105] The memory 703 is configured to store instructions and applications executable by the processor 701, and can also cache data to be processed or already processed (e.g., image data, audio data, voice communication data, and video communication data) in the processor 701 and various modules in the electronic device 700. It can be implemented using flash memory or random access memory (RAM). Data transfer between the processor 701, the communication interface 702, and the memory 703 can be performed via bus 704.

[0106] This application provides a computer storage medium storing one or more programs that can be executed by one or more processors to implement the steps of the meeting message notification method as described in any of the above embodiments.

[0107] It should be noted that the descriptions of the storage medium and device embodiments above are similar to the descriptions of the method embodiments above, and have similar beneficial effects. For technical details not disclosed in the storage medium and device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0108] The aforementioned processor can be at least one of the following: Application Specific Integrated Circuit (ASIC), Digital Signal Processor (DSP), Digital Signal Processing Device (DSPD), Programmable Logic Device (PLD), Field Programmable Gate Array (FPGA), Central Processing Unit (CPU), Controller, Microcontroller, and Microprocessor. It is understood that other electronic devices can also implement the functions of the aforementioned processor, and this application does not specifically limit the specific implementation.

[0109] The aforementioned computer storage media / memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM), etc.; or it can be various terminals that include one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc.

[0110] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence numbers of the above steps / processes do not imply a sequential order of execution; the execution order of each step / process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The sequence numbers of the above embodiments of this application are merely descriptive and do not represent the superiority or inferiority of the embodiments.

[0111] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0112] The above are merely embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1.A method for notifying a conference message, the method comprising: receiving a first text message from a first application; obtaining a first PCM data stream corresponding to the first text message based on the first text message; writing the first PCM data stream to a mixer of an electronic device; sending an audio data stream including the first PCM data stream through a second application. 2.The method of claim 1, wherein the receiving a first text message from a first application comprises: receiving the first text message from the first application if conference audio data during a conference indicates that a conference participant asks a question and a user does not reply to the question within a preset time period. 3.The method of claim 1, wherein the receiving a first text message from a first application comprises: receiving the first text message corresponding to recorded conference content if the conference audio data during the conference indicates that the conference content is recorded. 4.The method of any one of claims 1-3, wherein the obtaining a first PCM data stream corresponding to the first text message based on the first text message comprises: inputting the first text message into a text-to-speech conversion model to obtain the first PCM data stream corresponding to the first text message. 5.The method of claim 1, wherein after the writing the first PCM data stream to the mixer of the electronic device, the method further comprises: performing audio processing on the first PCM data stream and an input data stream from a microphone to obtain the audio data stream. 6.The method of claim 5, wherein the performing audio processing on the first PCM data stream and the input data stream from the microphone to obtain the audio data stream comprises: performing mixing processing and echo cancellation processing on the first PCM data stream and the input data stream to obtain the audio data stream. 7.The method of claim 1, wherein the sending an audio data stream through a second application comprises: reading the audio data stream from the mixer in response to an audio acquisition request triggered by the second application in a non-mute state; and sending the audio data stream to the second application. 8.The method of claim 7, wherein before the responding to the audio acquisition request triggered by the second application in the non-mute state, the method further comprises: detecting that the second application is in a mute state; and sending a mute control instruction to the second application to control the second application to switch from the mute state to the non-mute state. 9.The method of claim 1, wherein the method further comprises: converting the audio data stream into a second text message; and sending the second text message through the second application. 10.An electronic device comprising a sound card driving component, wherein the sound card driving component is configured to: receive a first text message from a first application; obtain a first PCM data stream corresponding to the first text message based on the first text message; and writing the first PCM data stream to a mixer of the electronic device; sending, by a second application, an audio data stream, the audio data stream comprising the first PCM data stream.

Images