Methods, devices, equipment and storage media for controlling meeting minutes

Abstract

This application discloses a meeting recording control method, apparatus, device, and storage medium, relating to the field of intelligent control technology. The method includes: acquiring an interaction signal generated by an attached mobile power supply device and acquiring the current control state of a mobile terminal; jointly determining the interaction signal and the current control state, and generating a meeting recording intent recognition result based on the joint determination; when the meeting recording intent recognition result meets preset activation conditions, creating a meeting task and starting the meeting recording of the meeting task; monitoring the current control state, switching the recording mode of the meeting recording based on the monitoring result of the current control state, and outputting recording feedback. This application, by jointly determining the interaction signal and the current control state and continuously monitoring the current control state, accurately identifies the true meeting recording intent, avoids accidental touches and invalid activations, thereby significantly improving the reliability of meeting recording control.

Description

Technical Field

[0001] This application relates to the field of intelligent control technology, and in particular to meeting recording control methods, devices, equipment and storage media. Background Technology

[0002] Current methods for initiating recording on mobile devices primarily rely on manual interface clicks or sending simple control commands via a common Bluetooth peripheral. For adhesive-powered devices attached to the back of the mobile terminal, ordinary button events are prone to accidental touches, missed touches, or invalid triggers when held, carried in a pocket, placed on a table, or operated with one hand. Furthermore, because button events are treated as direct command execution without considering the device's attachment status, connection status, recording permission status, current meeting task status, and the mobile terminal's recording capability, users may mistakenly believe they have started recording when they have not actually entered an effective recording state.

[0003] Therefore, how to effectively distinguish between presses indicating genuine meeting recording intent and those indicating non-meeting intent, and improve the reliability of meeting recording control, has become a technical problem that this application urgently needs to solve. Summary of the Invention

[0004] The main objective of this application is to provide a meeting recording control method, apparatus, device, and storage medium, aiming to solve the technical problem of how to effectively distinguish between genuine meeting recording intentions and non-meeting intentions in pressing, thereby improving the reliability of meeting recording control.

[0005] To achieve the above objectives, this application proposes a meeting minutes control method, the method comprising: Acquire the interactive signals generated by the attached mobile power supply device and acquire the current control status of the mobile terminal; The interaction signal and the current control state are jointly determined, and a meeting recording intent recognition result is generated based on the joint determination; When the meeting recording intent recognition result meets the preset activation conditions, a meeting task is created and the meeting recording of the meeting task is started; Monitor the current control status, switch the recording mode of the meeting minutes based on the monitoring results of the current control status, and output recording feedback.

[0006] In one embodiment, the step of acquiring the interactive signal generated by the attached mobile power supply device includes: Detect user press operations on the attached mobile power supply device, and generate interactive signals based on the user press operations; The interaction signal is sent to the mobile terminal to obtain the current control status of the mobile terminal.

[0007] In one embodiment, the interaction signal includes one or more of the following: a press event, a press duration, a press count, a device attachment status, and a device connection status; the current control status includes one or more of the following: an application availability status, a recording permission status, a meeting task status, an audio resource availability status, a storage status, and a battery status.

[0008] In one embodiment, the step of jointly determining the interaction signal and the current control state, and generating a meeting recording intent recognition result based on the joint determination, includes: The accidental touch risk is determined based on the preset accidental touch risk conditions of the interaction signal and the current control state; When the accidental touch risk is determined to be non-compliant with the accidental touch risk conditions, the executability of the interaction signal and the current control state is determined based on preset executable normal conditions; When the executability determination is that it meets the normal executability conditions, the interactive signal and the current control state are determined to be recordable based on the preset normal recordability conditions; When the recordability determination meets the normal recordability conditions, the interaction signal and the current control state are determined to pass the joint determination, and a valid meeting recording intent recognition result is generated; When the accidental touch risk is determined to meet the accidental touch risk conditions, and / or the executability is determined to not meet the normal executability conditions, and / or the recordability is determined to not meet the normal recordability conditions, the interaction signal and the current control state are determined not to pass the joint determination, and an invalid meeting record intent identification result is generated.

[0009] In one embodiment, the step of creating a meeting task and starting the meeting recording of the meeting task when the meeting recording intent recognition result meets the preset activation conditions includes: If the meeting recording intent recognition result is a valid meeting recording intent recognition result, then the meeting recording intent recognition result is determined to meet the preset activation conditions; When the meeting recording intent recognition result meets the activation conditions, a meeting task is created; Initialize the recording segment based on the task identifier of the meeting task, and configure the audio recording parameters; The meeting recording of the meeting task is initiated based on the initial recording segment and the audio recording parameters.

[0010] In one embodiment, after the step of jointly determining the interaction signal and the current control state, and generating a meeting recording intent recognition result based on the joint determination, the method further includes: If the meeting recording intent recognition result is an invalid meeting recording intent recognition result, then it is determined that the meeting recording intent recognition result does not meet the preset start conditions; When the meeting recording intent recognition result does not meet the activation conditions, a blocking control command is generated; Based on the blocking control command, the initiation of the meeting record and / or the creation of the meeting task are blocked, and a status prompt corresponding to the invalid meeting record intent identification result is generated.

[0011] In one embodiment, the steps of monitoring the current control state, switching the recording mode of the meeting minutes based on the monitoring result of the current control state, and outputting recording feedback include: Monitor the current control state, and determine whether the current control state meets the preset continuous recording conditions based on the monitoring results of the current control state; When the current control state does not meet the continuous recording conditions, the recording mode is switched to one or more of the following: recording protection mode, recovery waiting mode, and status prompt mode; The final control result of the meeting recording is determined based on the switched recording mode; The final control result is used to output a recording feedback, which includes one or more of the following: recording start, recording failure, recording protection, recording saved, waiting to be restored, and unavailable.

[0012] Furthermore, to achieve the above objectives, this application also proposes a meeting recording control device, which includes: The acquisition module is used to acquire the interactive signals generated by the attached mobile power supply device and to acquire the current control status of the mobile terminal. The determination module is used to jointly determine the interaction signal and the current control state, and generate a meeting recording intent recognition result based on the joint determination; The recording module is used to create a meeting task and start the meeting recording of the meeting task when the meeting recording intent recognition result meets the preset start conditions; The switching module is used to monitor the current control status, switch the recording mode of the meeting minutes based on the monitoring results of the current control status, and output recording feedback.

[0013] In addition, to achieve the above objectives, this application also proposes a meeting recording control device, the device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the meeting recording control method as described above.

[0014] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and which, when executed by a processor, implements the steps of the meeting recording control method described above.

[0015] One or more technical solutions proposed in this application have at least the following technical effects: First, the system acquires the interactive signals generated by the attached mobile power supply device and the current control state of the mobile terminal, providing a multi-dimensional data foundation for subsequent judgments. Furthermore, it jointly determines the interactive signals and the current control state to generate a meeting recording intent recognition result. Instead of directly mapping peripheral button events to recording commands, it comprehensively judges whether the interaction signals and the current control state represent a genuine meeting intent. Further, only when the meeting recording intent recognition result meets preset activation conditions is a meeting task created and recording initiated, thus blocking invalid activations due to unintended presses or unmet terminal conditions at the source. Finally, after recording begins, the system continuously monitors the mobile terminal's control state, switches recording modes based on the monitoring results, and outputs feedback, further ensuring the continuity and reliability of the recording process. In summary, this application, by jointly determining the interactive signals and the current control state and continuously monitoring the current control state, accurately identifies genuine meeting recording intents, avoids accidental touches and invalid activations, and thus significantly improves the reliability of meeting recording control. Attached Figure Description

[0016] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0017] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 A flowchart illustrating the first embodiment of the meeting record control method of this application; Figure 2 A flowchart illustrating the second embodiment of the meeting record control method of this application; Figure 3 This is a flowchart illustrating the third embodiment of the meeting record control method of this application. Figure 4 This is a flowchart illustrating the fourth embodiment of the meeting record control method of this application. Figure 5This is a flowchart illustrating the fifth embodiment of the meeting record control method of this application. Figure 6 The meeting recording system interaction architecture diagram provided for the meeting recording control method of this application; Figure 7 This is a schematic diagram of the module structure of the meeting recording control device according to an embodiment of this application; Figure 8 This is a schematic diagram of the device structure of the hardware operating environment involved in the meeting recording control method in this application embodiment.

[0019] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0020] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0021] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0022] The main solution of this application embodiment is as follows: acquire the interaction signal generated by the attached mobile power supply device and acquire the current control state of the mobile terminal; jointly determine the interaction signal and the current control state, and generate a meeting recording intent recognition result based on the joint determination; when the meeting recording intent recognition result meets the preset start conditions, create a meeting task and start the meeting recording of the meeting task; monitor the current control state, switch the recording mode of the meeting recording based on the monitoring result of the current control state, and output recording feedback.

[0023] In this embodiment, for ease of description, the meeting record control system will be used as the execution subject in the following description.

[0024] This application's embodiments take into account that: Existing mobile terminal recording initiation methods primarily rely on manually clicking the interface or sending simple control commands via a general Bluetooth peripheral. For adhesive mobile power supply devices attached to the back of the mobile terminal, ordinary button events are prone to accidental touches, missed touches, or invalid triggers under various conditions such as handheld, pocket-carried, desktop-placed, and one-handed operation. Furthermore, because button events are treated as direct command execution without considering the device's attachment status, connection status, recording permission status, current meeting task status, and the mobile terminal's recordable state, users may mistakenly believe that recording has been started when it has not actually entered an effective recording state.

[0025] Therefore, this application provides a solution. First, it acquires the interactive signals generated by the attached mobile power supply device and the current control state of the mobile terminal, providing a multi-dimensional data foundation for subsequent judgment. Further, it jointly judges the interactive signals and the current control state to generate a meeting recording intent recognition result. Instead of directly mapping peripheral button events to recording commands, it comprehensively judges whether the interaction signals and the current control state represent a genuine meeting intent. Furthermore, only when the meeting recording intent recognition result meets preset activation conditions is a meeting task created and recording initiated, thereby blocking invalid activations due to unintended presses or unmet terminal conditions at the source. Finally, after recording starts, it continuously monitors the control state of the mobile terminal, switches the recording mode based on the monitoring results, and outputs feedback, further ensuring the continuity and reliability of the recording process. In summary, this application, by jointly judging the interactive signals and the current control state and continuously monitoring the current control state, accurately identifies genuine meeting recording intents, avoids accidental touches and invalid activations, and thus significantly improves the reliability of meeting recording control.

[0026] It should be noted that the executing entity in this embodiment can be a computing service device with data processing, network communication, and program execution functions, such as a tablet computer, personal computer, or mobile phone, or an electronic device or meeting recording control system capable of performing the above functions. The following description uses a meeting recording control system as an example to illustrate this embodiment and the subsequent embodiments.

[0027] Based on this, embodiments of this application provide a meeting record control method, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the meeting record control method of this application.

[0028] In this embodiment, the meeting recording control method includes steps S10 to S40: Step S10: Obtain the interactive signal generated by the attached mobile power supply device and obtain the current control status of the mobile terminal; Attachable mobile power supply devices refer to devices that attach to the back of a mobile terminal and supply power to it through magnetic attraction, contact, or other means, such as magnetic power banks. Interaction signals include press events, press duration, number of presses, device attachment status, and device connection status.

[0029] The current control state of a mobile terminal refers to the internal operating conditions of terminals such as mobile phones, including application availability, recording permission status, meeting task status, audio resource availability, storage status, and battery status.

[0030] Specifically, the attachable mobile power supply device detects user pressing actions through a button sensor, records the start and end timestamps of the press to calculate the press duration, and counts the number of presses within a specified time window. An accelerometer or magnetometer is used to detect the device's attachment status and pocket compression posture, and the device's connection status is obtained via a Bluetooth module.

[0031] Furthermore, the system uses an attached mobile power supply device to package the aforementioned press event, press duration, number of presses, device attachment status, and device connection status according to the BLE (Bluetooth Low Energy) protocol and sends them to the mobile terminal. After receiving the signal, the system synchronously calls the interface to query the mobile terminal's recording permissions, audio resource usage, storage space, battery level, and its own conference task status, thereby determining the current control status of the mobile terminal.

[0032] Step S20: Perform a joint determination on the interaction signal and the current control state, and generate a meeting recording intent recognition result based on the joint determination; Joint judgment refers to combining interactive signals with the control status of the mobile terminal and conducting comprehensive analysis through multi-layered rules or models. Specifically, it includes accidental touch risk judgment, executability judgment, and recordability judgment.

[0033] Specifically, the system takes the acquired interaction signals (such as press duration, number of presses, device attachment status, and Bluetooth connection status) and the current control status of the mobile terminal (such as recording permission status, meeting task status, battery status, storage status, and audio resource usage status) as input, and performs a three-layer joint judgment in sequence: the first layer is the accidental touch risk judgment; if the first layer of accidental touch risk judgment is passed, it proceeds to the second layer of executability judgment; if the second layer of executability judgment is passed, it proceeds to the third layer of recordability judgment. Only when all three layers of joint judgment are passed will a valid meeting recording intent recognition result be generated; otherwise, an invalid meeting recording intent recognition result will be generated.

[0034] Step S30: When the meeting recording intent recognition result meets the preset start conditions, a meeting task is created and the meeting recording of the meeting task is started; The preset start conditions refer to a set of hard requirements that must be met simultaneously as defined by the system. When all three layers of joint judgment pass, the meeting record intent recognition result is considered to meet the preset start conditions.

[0035] Specifically, when the meeting recording intent recognition result is valid, the system determines that the preset start conditions are met and then performs the following operations: First, a meeting task object is created, a unique meeting task ID is generated by using a timestamp and a random number, the current system time is recorded as the start time, the status of the meeting task is set to "recording", and the task is saved to the local database; further, the recording segment is initialized based on the meeting task ID, the segment index is set to 1, the starting offset is 0, and the audio recording parameters are configured, thereby starting the meeting recording of the meeting task.

[0036] Step S40: Monitor the current control status, switch the recording mode of the meeting minutes based on the monitoring result of the current control status, and output recording feedback.

[0037] Recording mode refers to the recording working mode that the system dynamically switches according to the current control state. There are three main types: recording protection mode, recovery waiting mode, and status prompt mode.

[0038] Recorded feedback refers to the information output by the system to the user based on the final control result. Feedback forms include the indicator light color and flashing pattern of the attached mobile power supply device, the vibration pattern of the vibration motor, and pop-up windows, status bar notifications or voice prompts on the mobile terminal. Its core principle is "result feedback" rather than "button feedback", that is, the actual status is only informed to the user after the control is actually executed.

[0039] Specifically, after recording is started, the system continuously monitors the current control status in the background. When it detects that any continuous recording condition is not met, the system immediately performs a mode switch, switching to the corresponding recording mode according to the condition type of the unmet continuous recording condition.

[0040] Furthermore, the system determines the final control result of the meeting recording based on the switching mode after the final switch, and outputs recording feedback to the user based on the final control result, ensuring that the user always clearly understands the actual operating status of the recording.

[0041] This embodiment provides a meeting recording control method. First, it acquires the interaction signals generated by the attached mobile power supply device and the current control state of the mobile terminal, providing a multi-dimensional data foundation for subsequent judgment. Further, it jointly judges the interaction signals and the current control state to generate a meeting recording intent recognition result. Instead of directly mapping peripheral button events to recording commands, it comprehensively judges whether the interaction signals and the current control state represent a genuine meeting intent. Furthermore, only when the meeting recording intent recognition result meets preset activation conditions is a meeting task created and recording initiated, thereby blocking invalid starts due to unintended presses or unmet terminal conditions at the source. Finally, after recording starts, it continuously monitors the control state of the mobile terminal, switches the recording mode based on the monitoring results, and outputs feedback, further ensuring the continuity and reliability of the recording process. In summary, this application, by jointly judging the interaction signals and the current control state and continuously monitoring the current control state, accurately identifies genuine meeting recording intents, avoids accidental touches and invalid starts, and thus significantly improves the reliability of meeting recording control.

[0042] Based on the first embodiment of this application, a second embodiment of this application is proposed. In the second embodiment of this application, content that is the same as or similar to that in the first embodiment described above can be referred to the above description and will not be repeated hereafter.

[0043] Based on this, please refer to Figure 2 , Figure 2 This is a flowchart illustrating the second embodiment of this application, as shown below. Figure 2 As shown, step S10, which involves acquiring the interactive signal generated by the attached mobile power supply device and acquiring the current control state of the mobile terminal, may include steps S11 to S12: Step S11: Detect user pressing operations on the attached mobile power supply device, and generate an interactive signal based on the user pressing operations; User pressing operation refers to the user's action of pressing the physical button or touch area set on the attached mobile power supply device with their finger. The system will detect the start and end time of the press and record parameters such as the press duration, number of presses, and press interval.

[0044] Specifically, the system continuously samples the physical state of the button area through a touch sensor or pressure sensor on the attached mobile power supply device. When the signal is detected to change from an idle level to a trigger level, the current timestamp is recorded as the start time of the press, and a timer is started at the same time. When the signal is detected to return to an idle level, the end timestamp is recorded and the press duration is calculated.

[0045] Furthermore, the system uses a state machine to count the number of presses within a preset time window, determining whether it is a single click, double click, or triple click. The system also collects real-time attitude data of the attached mobile power supply device using an accelerometer and magnetometer: if a large, irregular fluctuation in the Z-axis acceleration value is detected and the magnetometer displays the magnetic field characteristics of the device in a closed space (such as a pocket), the current attachment state is determined to be "pocket compression"; if the attitude is stable and the magnetometer data matches the magnetic stripe on the back of the phone, it is determined to be "normal attachment".

[0046] The system uses the microcontroller unit on the attached mobile power supply device to package the collected pressing events, pressing duration, pressing count, device attachment status, and device connection status into an interactive signal data frame according to a predetermined protocol, and temporarily stores it in the transmission buffer for transmission.

[0047] Step S12: Send the interaction signal to the mobile terminal to obtain the current control status of the mobile terminal.

[0048] After the system completes the packaging of the interaction signal, it checks the current BLE connection status and sends the packaged interaction signal to the mobile terminal according to the BLE connection status. When the mobile terminal receives the interaction signal sent from the attached mobile power supply device, it calls multiple system interfaces of the mobile operating system in parallel to obtain the current control status.

[0049] In this embodiment, by collecting user pressing operations on the attached device in real time and converting them into interactive signals, the current control state of the mobile terminal is obtained synchronously. This provides a two-dimensional data foundation of "operation intention" and "terminal environment" for subsequent joint judgment, thereby enabling the system to distinguish between genuine meeting recording intentions and non-intentional pressing, and to assess whether the terminal has the conditions for recording.

[0050] Based on the first and / or second embodiments of this application, a third embodiment of this application is proposed. In the third embodiment of this application, content that is the same as or similar to the first and / or second embodiments described above can be referred to the above description and will not be repeated hereafter.

[0051] Based on this, please refer to Figure 3 , Figure 3 A flowchart illustrating the third embodiment of the meeting record control method provided in this application is shown below. Figure 3 As shown, step S20, which involves jointly determining the interaction signal and the current control state and generating a meeting recording intent recognition result based on the joint determination, may include steps S21 to S25: Step S21: Determine the risk of accidental touch based on the preset accidental touch risk conditions for the interaction signal and the current control state; Accidental touch risk conditions refer to a set of predefined rules and thresholds used by the system to identify unintentional presses by the user. For example, accidental touch risk conditions may include pressing time that is too short (e.g., less than 100ms), repeated pressing intervals that are too close (e.g., the interval between two presses is less than 500ms), the device being attached to a "pocket squeeze" device, or the Bluetooth connection being invalid.

[0052] Specifically, the accidental touch risk assessment aims to quickly identify and filter out invalid presses that are clearly caused by environmental factors or misoperation. The system compares specific data such as press duration, number of presses, and device connection status in the interaction signal and current control state with the corresponding thresholds or features in the accidental touch risk conditions. If any item meets the accidental touch risk conditions (e.g., press duration <100ms), an accidental touch risk is determined to exist, and the subsequent process is blocked. If none of the specific data in the interaction signal and current control state triggers the risk conditions, the accidental touch risk conditions are determined not to exist, and the system proceeds to the executability assessment.

[0053] For example, in one specific implementation, Manager Wang puts his mobile phone in his pocket on his way to work, along with a magnetic power bank attached to the back of the phone. As Manager Wang walks, the pocket presses against the surface of the power bank, triggering a short press event (press duration 50ms). The power bank sends the press event to the mobile app via the BLE protocol. Upon receiving the event, the app performs a joint determination: The press duration of 50ms is less than the 100ms threshold set in the accidental touch risk conditions, meeting the accidental touch risk criteria and being judged as a suspected accidental touch. Furthermore, the device's attachment status—detecting pocket compression (abnormal fluctuation of the accelerometer Z-axis)—matches the pocket scenario set in the accidental touch risk conditions. Therefore, it is judged as meeting the accidental touch risk conditions, and blocking control is implemented; no meeting task is created, and it does not proceed to subsequent executability assessments. Further, after receiving the blocking feedback from the APP, the power bank vibrates (a short 100ms vibration) to alert the user that "the button is not responding." If Manager Wang truly intends to record, he will remove his phone from his pocket, and the attached power bank will return to its normal orientation. Pressing the button again at this time (press duration 300ms) does not meet the 100ms threshold set in the preset accidental touch risk conditions. The system judges this as a genuine intent, initiates recording, and proceeds to subsequent executability assessments.

[0054] Step S22: When the accidental touch risk is determined to be inconsistent with the accidental touch risk conditions, the executability of the interaction signal and the current control state is determined based on the preset executable normal conditions. The executable normal conditions refer to a set of mobile terminal operation requirements predefined by the system to ensure that the meeting recording function can be basically started. For example, the executable normal conditions may include the application availability status being running (the APP has not been forcibly terminated by the system), the recording permission status being authorized, the meeting task status being no ongoing meeting, and the audio resource availability status being not occupied by other applications.

[0055] Specifically, the system compares the interactive signals and the specific data contained in the current control state with the preset thresholds or conditions existing in the normal executable conditions one by one to determine whether the normal executable conditions are met. If the interactive signals and the specific data contained in the current control state both meet the preset thresholds or conditions existing in the normal executable conditions, the executability determination is passed; otherwise, it is not passed.

[0056] For example, in one specific implementation, Mr. Zhang is preparing to record in the conference room, but the APP has not yet obtained microphone permission. Mr. Zhang double-clicks the power bank button (press duration 300ms), which does not meet the preset accidental touch risk condition of 100ms. The system determines this as a genuine intention and performs an executability judgment. Since the microphone permission is not granted, it does not meet the preset normal executability condition of the recording permission status being authorized. Therefore, the system performs blocking control, does not create a meeting task, and simultaneously provides dual prompts through the power bank indicator light and a pop-up window on the phone: Power bank: red light flashes twice; Phone: pop-up permission request dialog box "Microphone permission is required to record". Mr. Zhang clicks "Authorize" in the pop-up window. After the permission is successfully obtained, pressing the power bank button again will start recording and perform subsequent recordability judgments.

[0057] Step S23: When the executability determination is that it meets the normal executability conditions, the recordability determination of the interaction signal and the current control state is performed based on the preset normal recordability conditions; Normal recordable conditions refer to a set of predefined resource capacity requirements that ensure continuous and stable writing of recordings to files without interruption. In one specific implementation, normal recordable conditions mainly include: storage capacity greater than 100MB to ensure at least several hours of high-quality audio recording, and battery level above 10% to avoid file corruption caused by sudden shutdown during recording.

[0058] Furthermore, the system calls the audio management interface to determine whether the microphone is occupied, queries the remaining storage space through the file system, and obtains the current battery percentage; compares the above three values ​​with the preset thresholds in the normal recording conditions; and determines that the normal recording conditions are met only when the audio resources are idle, the storage is sufficient, and the battery is sufficient.

[0059] Step S24: When the recordability determination meets the normal recordability conditions, the interaction signal and the current control state are determined to pass the joint determination, and a valid meeting recording intent recognition result is generated; The valid meeting recording intent recognition result refers to the positive result label output by the system after three layers of verification: accidental touch risk judgment, executability judgment, and recordability judgment, confirming that the user's pressing behavior is a genuine meeting recording intent and that the mobile terminal has all the conditions required to start recording.

[0060] After the system determines the interaction signal and the current control state through joint judgment, it generates a preset valid intent identifier. This valid intent identifier, together with the interaction signal and the current control state, is packaged into a valid meeting record intent recognition result.

[0061] Understandably, the recording of normal conditions, the execution of normal conditions, and the accidental touch risk conditions can be set differently according to specific application scenarios. For example, the corresponding preset thresholds or matching rules can be dynamically adjusted for different mobile terminal models, different user operating habits, or different usage environments.

[0062] Step S25: When the accidental touch risk determination meets the accidental touch risk condition, and / or the executability determination does not meet the normal executability condition, and / or the recordability determination does not meet the normal recordability condition, the interaction signal and the current control state are determined not to pass the joint determination, and an invalid meeting record intent recognition result is generated.

[0063] When any of the following situations occur during the joint determination process, the system will determine that the interaction signal and the current control state have not passed the joint determination and generate the corresponding invalid meeting record intent recognition result: the accidental touch risk determination meets the preset accidental touch risk conditions; the executability determination does not meet the normal executability conditions; the recordability determination does not meet the normal recordability conditions.

[0064] In this embodiment, by using a three-tiered progressive judgment of accidental touch risk, executability, and recordability, the peripheral device pressing signal and terminal status are analyzed together to effectively distinguish between pressing with the real intention of meeting recording and pressing with non-meeting intention, and to eliminate invalid triggers in scenarios where accidental touch conditions are not met, thereby significantly improving the accuracy of recording initiation and control reliability.

[0065] Based on the above embodiments of this application, a fourth embodiment of this application is proposed. In this fourth embodiment, content that is the same as or similar to that in the above embodiments can be referred to the above description, and will not be repeated hereafter.

[0066] Based on this, please refer to Figure 4 , Figure 4 This is a flowchart illustrating the fourth embodiment of this application, as shown below. Figure 4 As shown, when the meeting recording intent recognition result meets the preset activation conditions, step S30, which creates a meeting task and starts the meeting recording of the meeting task, may include steps S31 to S34: Step S31: If the meeting recording intent recognition result is the valid meeting recording intent recognition result, then it is determined that the meeting recording intent recognition result meets the preset activation conditions; Specifically, the system obtains the meeting recording intent recognition result. If the meeting recording intent recognition result is a valid meeting recording intent recognition result, it is determined that the meeting recording intent recognition result meets the preset start conditions. Otherwise, it is determined that the start conditions are not met, and blocking control is executed instead.

[0067] Step S32: When the meeting recording intent recognition result meets the activation conditions, a meeting task is created; Once the startup conditions are met, the system calls the Task Manager module to perform the following operations: generate a globally unique task identifier ID, which typically includes the date, time, and a random number; record the current system time as the start time; initialize the task status to "recording"; persistently store the meeting task in the local database, and choose to synchronize it to the cloud server.

[0068] In addition, the system can also create a corresponding meeting record entry on the UI interface, displaying the start time and status, which facilitates subsequent management by the user.

[0069] Step S33: Initialize the recording segment based on the task identifier of the meeting task, and configure the audio recording parameters; Audio segments are sub-units within a conference task, used to manage continuous segments of audio data. It's understandable that a conference task may generate multiple segments due to pauses, interruptions, or manual splitting. Each segment contains attributes such as segment index, start offset, segment start time, and file path.

[0070] Audio recording parameters are the technical parameters required to configure a recorder, including audio source, sampling rate, number of channels, encoding format, bit rate, output file format, and the complete storage path of the output file.

[0071] Specifically, the system first creates an audio recording segment object based on the task ID of the meeting and the current time: setting the segment index to 1 (if it's the first time starting), the starting offset to 0, and the segment start time to the current timestamp. Then, it configures the audio recording parameters according to user instructions. After configuration, it passes the audio recording parameters and the initialized audio recording segment to the recorder instance, waiting for the start command.

[0072] Step S34: Start the meeting recording of the meeting task according to the initial recording segment and the audio recording parameters.

[0073] Specifically, after passing the audio recording parameters and initial recording clips to the recorder instance, the system calls the recorder instance to officially start audio recording. In one feasible implementation, the system starts a background monitoring thread to monitor abnormal states during the recording process (such as disk full, loss of audio focus, etc.). In addition, the system updates the UI display to show visual feedback such as recording duration and waveform animation, and sends a "recording started" feedback command (such as a green light or a short vibration) to the attached mobile power supply device via the BLE protocol.

[0074] In this embodiment, after confirming the true intent to record the meeting, a meeting task and recording segment are automatically created, audio parameters are configured, and recording is started. This achieves a complete closed loop from intent recognition to recording execution, ensuring that recording is started only under valid intent, avoiding unnecessary resource consumption, and improving the automation and reliability of meeting recording startup.

[0075] Based on the above embodiments of this application, a fifth embodiment of this application is proposed. In this fifth embodiment, content that is the same as or similar to that in the above embodiments can be referred to the above description, and will not be repeated hereafter.

[0076] Based on this, please refer to Figure 5 , Figure 5 This is a schematic flowchart of the fifth embodiment of this application, as shown below. Figure 5 As shown, after step S20, which involves jointly determining the interaction signal and the current control state and generating a meeting recording intent recognition result based on the joint determination, steps S231 to S233 are further included: Step S231: If the meeting recording intent recognition result is the invalid meeting recording intent recognition result, then it is determined that the meeting recording intent recognition result does not meet the preset start conditions; The system first receives the meeting recording intent recognition result generated by the joint judgment. If the result is "invalid" (that is, the system determines that the current pressing behavior does not belong to the real meeting recording intent), the system performs a conditional logic judgment and determines that the result does not meet the preset start conditions.

[0077] Step S232: When the meeting recording intent recognition result does not meet the activation conditions, a blocking control command is generated; If the system determines that the intent recognition result for the meeting recording does not meet the activation conditions, it immediately generates a blocking control command. The generation of this command is based on a rule engine or conditional judgment logic, and is essentially a negative response to the joint judgment result.

[0078] It should be noted that the blocking control command is generated automatically and in real time by the system without waiting for secondary user confirmation or timeout judgment, ensuring rapid response. This blocking control command will be transmitted to the lower-level control execution module of the system as the driving signal for subsequent blocking actions.

[0079] Step S233: Based on the blocking control command, block the initiation of the meeting record and / or the creation of the meeting task, and generate a status prompt corresponding to the invalid meeting record intent identification result.

[0080] The lower-level control execution module of the system first performs blocking operations on the meeting recording process based on the blocking control command. Specifically, this includes: preventing the start of meeting recording, preventing the creation of meeting task objects, preventing the allocation of audio recording resources, and preventing the switching of recording status, among other low-level operations.

[0081] Furthermore, based on the specific invalidation reasons generated during the joint determination phase (such as accidental touch type, state non-compliance type, etc.), the system maps and generates a distinctive state prompt message, and outputs the prompt to the user through a pre-set feedback channel (such as mobile terminal pop-up, vibration, light flashing or sound prompt).

[0082] In this embodiment, when an invalid meeting recording intent is identified, the recording start is promptly blocked and a targeted status prompt is output to avoid erroneous recording start due to accidental touch or unmet terminal conditions. At the same time, the user is made clear about the reason for the failure, thereby improving the accuracy of control and the transparency of user operation.

[0083] Based on the above embodiments of this application, a sixth embodiment of this application is proposed. In the sixth embodiment of this application, content that is the same as or similar to the above embodiments can be referred to the above description, and will not be repeated hereafter.

[0084] In this embodiment, step S40, which involves monitoring the current control state, switching the recording mode of the meeting minutes based on the monitoring result of the current control state, and outputting recording feedback, may include steps S41 to S44: Step S41: Monitor the current control state, and determine whether the current control state meets the preset continuous recording conditions based on the monitoring results of the current control state; Continuous recording conditions refer to a set of pre-defined gating rules used by the system to determine whether the current environment is suitable for continuing recording. Unlike start conditions, continuous recording conditions determine whether the current environment can maintain the necessary conditions for recording for a future period of time. For example, in one specific implementation, continuous recording conditions may include a battery threshold >10%, remaining storage space >100MB, normal Bluetooth connection (or disconnection not exceeding 30 seconds), and audio resources not being preempted.

[0085] It is understandable that if any continuous recording condition is not met, it is determined that the continuous recording condition is not met.

[0086] Specifically, after recording begins, the system enters a continuous monitoring loop. Through the system service interface and broadcast listening mechanism provided by the operating system, the system acquires changes in various control states in real time using a combination of event-driven and timed polling. Whenever the system receives a status change notification (such as a low battery broadcast triggered when the battery drops to 15%, a storage space alarm triggered, or a Bluetooth disconnection callback), it summarizes all relevant current states and compares them one by one with the preset set of continuous recording condition rules.

[0087] If each threshold or rule in the preset continuous recording conditions is met, the system determines that the continuous recording conditions are met, and the recording continues normally; if any condition is not met, the mode switch is triggered.

[0088] Step S42: When the current control state does not meet the continuous recording conditions, the recording mode is switched to one or more of the following: recording protection mode, recovery waiting mode, and status prompt mode; It should be noted that the recording protection mode refers to an emergency operating state that prioritizes the protection of the integrity of recorded data. When the system detects an irreversible anomaly that may lead to data loss (such as the battery being about to run out or the storage space being about to reach zero), it immediately performs a save operation on the current recording segment, writes the recorded audio data to persistent storage, and then closes the recording file handle to prevent data corruption.

[0089] The recovery waiting mode refers to a system that pauses recording but retains recording resources and session context when the control state temporarily does not meet the conditions for continuous recording (such as a brief disconnection of Bluetooth connection or temporary preemption of the microphone), but it is expected that the conditions may recover on their own in a short time. Recording will resume automatically after the conditions are restored, avoiding frequent start-stop operations that could cause a gap in the user experience.

[0090] Status alert mode refers to the operating state where the primary task is to output feedback information. When the system determines that the current anomaly requires user awareness or intervention (such as when an application is switched to the background or a minor anomaly warning), the system does not perform recording or protection actions, but instead focuses on outputting clear prompts to the user, informing them of the current status and suggesting actions.

[0091] Specifically, when it is determined that the current control state no longer meets the conditions for continuous recording, the system will not abruptly terminate the recording. Instead, it will select one or more recording modes to switch based on the specific type of the non-compliant continuous recording conditions.

[0092] For example, if the current control state does not meet the specific conditions for continuous recording, such as: battery level ≤ 10%, storage space < 100MB, or audio resources being preempted, the system determines that the specific type of the non-compliant continuous recording conditions is irreversible or at risk of data loss. The system will then prioritize switching to the recording protection mode: immediately stop the current recording, write the recorded audio segments to a file and save them to the database, and record the timestamp of the interruption position so that recording can be resumed from the breakpoint when the recording is restored later.

[0093] For example, in one specific implementation, Mr. Li is recording audio, but after 30 minutes, the phone's battery drops to 20%. The system detects this low battery event, which does not meet the preset continuous recording conditions. The recording manager switches to recording protection mode and immediately saves the current recording segment, displaying a low battery warning: "Battery low, recording has been paused, please continue after charging." The indicator light changes from solid green to a breathing orange. After Mr. Li plugs in the charging cable, the battery begins to recover. When the battery level exceeds 25% and the user clicks "Continue," the system automatically resumes recording from the last interrupted point.

[0094] Step S43: Determine the final control result of the meeting recording based on the switched recording mode; The final control result refers to the deterministic state conclusion that the system reaches regarding the entire meeting recording process after completing the recording mode switch.

[0095] For example, if the system successfully executes the recording protection mode and completes data saving, the final control result is "recording has been terminated and data has been protected"; if the conditions are restored before the timeout after entering the recovery waiting mode and recording is successfully resumed, the final control result is "recording has been restored"; if the conditions are not restored after the timeout, the result is "waiting for timeout, recording has been terminated"; when multiple modes are executed in combination (such as recording protection mode first and recovery waiting mode later), the final stable state is used as the basis for determining the final control result.

[0096] Step S44: Output recording feedback based on the final control result. The recording feedback includes one or more of the following: recording start, recording failure, recording protection, recording saved, waiting to be restored, and unavailable prompt.

[0097] Based on the determined final control result, the system outputs a uniquely matching record feedback to the user through a preset multi-channel feedback mechanism. Specific forms of feedback include: Feedback from the attached mobile power supply device: through the color changes and flashing patterns of LED indicator lights (e.g., solid green light indicates recording, fast red light indicates insufficient permissions, breathing orange light indicates low battery protection, and flashing yellow light indicates waiting for recovery) and different vibration modes of the vibration motor (e.g., one short vibration indicates interruption, and one long vibration indicates successful start-up).

[0098] Mobile terminal feedback: Status prompts pop up in the system notification bar, pop-up windows in the application displaying specific reasons (such as "Microphone permission is required to record, click to authorize"), changes in status bar icons, etc.

[0099] In this embodiment, the terminal status is continuously monitored during the recording process. When the conditions are not met, the system automatically switches to protection, waiting, or prompt mode, saves existing data and waits for recovery, and outputs clear feedback based on the actual control results, thereby ensuring the continuity of recording and data integrity, and improving reliability and user experience in abnormal scenarios.

[0100] Based on this, in order to better understand the meeting minutes method proposed in this application, the following will be combined with... Figure 6 This paper describes the interactions involved in the meeting recording method of this application, specifically... Figure 6 The meeting recording system interaction architecture diagram provided for the meeting recording control method of this application is as follows: Figure 6 As shown, the attached mobile power supply device uses its built-in button sensor, accelerometer, magnetometer and other modules to collect the user's pressing operation (including pressing duration, pressing number, etc.) as well as the device's own attachment status and connection status in real time, generate interactive signals, and send the signals to the mobile terminal through the BLE protocol.

[0101] Furthermore, after receiving the interactive signal, the mobile terminal synchronously calls the operating system interface to obtain the local current control status, including application availability, recording permission status, meeting task status, audio resource availability, storage status, and battery status. The meeting recording control system performs a three-layer progressive joint determination based on the received interactive signal and the current control status: First layer: Accidental touch risk assessment, filtering out unintentional operations such as pocket squeezing and excessively short presses; The second layer: executability determination, checking whether the application is running, whether recording permissions are granted, whether there are ongoing meetings, etc. The third layer: Recordability determination, confirming whether the storage space, power, and audio resources meet the recording requirements.

[0102] When all three layers of checks pass, the system generates a valid meeting recording intent recognition result, meeting the startup conditions. It then creates a meeting task, initializes the recording segment, configures audio parameters, and officially starts the meeting recording. The system sends feedback commands (such as indicator lights illuminating or vibration alerts) to the attached mobile power supply device via BLE and outputs recording start status feedback on the mobile terminal interface.

[0103] After recording begins, the system continuously monitors the current control status of the mobile terminal. When it detects that the preset continuous recording conditions are not met (such as low battery, insufficient storage, Bluetooth disconnection, etc.), the system automatically switches to recording protection mode, recovery waiting mode, or status prompt mode, and outputs the final control result to the user through a two-way feedback mechanism (such as recording terminated and saved, waiting to be restored, unavailable prompt, etc.).

[0104] This application also provides a meeting recording control device, please refer to... Figure 7 The meeting recording control device includes: The acquisition module 10 is used to acquire the interactive signals generated by the attached mobile power supply device and to acquire the current control status of the mobile terminal. The determination module 20 is used to jointly determine the interaction signal and the current control state, and generate a meeting record intent recognition result based on the joint determination; The recording module 30 is used to create a meeting task and start the meeting recording of the meeting task when the meeting recording intent recognition result meets the preset start conditions; The switching module 40 is used to monitor the current control state, switch the recording mode of the meeting minutes based on the monitoring result of the current control state, and output recording feedback.

[0105] The meeting recording control device provided in this application, employing the meeting recording control method in the above embodiments, can solve the technical problem of meeting recording control. Compared with the prior art, the beneficial effects of the meeting recording control device provided in this application are the same as those of the meeting recording control method provided in the above embodiments, and other technical features in the meeting recording control device are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0106] This application provides a conference recording control device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the conference recording control method in Embodiment 1 above.

[0107] The following is for reference. Figure 8The diagram illustrates a structural schematic of a meeting recording control device suitable for implementing embodiments of this application. The meeting recording control device in these embodiments may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), tablets, PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 8 The meeting recording control device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0108] like Figure 8 As shown, the conference recording control device may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.) that can perform various appropriate actions and processes according to a program stored in a read-only memory 1002 or a program loaded from a storage device 1003 into a random access memory 1004. The random access memory 1004 also stores various programs and data required for the operation of the conference recording control device. The processing unit 1001, the read-only memory 1002, and the random access memory 1004 are interconnected via a bus 1005. An input / output interface 1006 is also connected to the bus. Typically, the following systems can be connected to the input / output interface 1006: input devices 1007 including, for example, a touchscreen, touchpad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage devices 1003 including, for example, magnetic tape, hard disk, etc.; and communication devices 1009. Communication device 1009 allows the conference recording control device to communicate wirelessly or wiredly with other devices to exchange data. While the figures show conference recording control devices with various systems, it should be understood that implementation or possession of all the systems shown is not required. More or fewer systems may be implemented alternatively.

[0109] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from read-only memory 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0110] The meeting recording control device provided in this application, employing the meeting recording control method in the above embodiments, can solve the technical problem of meeting recording control. Compared with the prior art, the beneficial effects of the meeting recording control device provided in this application are the same as those of the meeting recording control method provided in the above embodiments, and other technical features of the meeting recording control device are the same as those disclosed in the method of the previous embodiment, and will not be repeated here.

[0111] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0112] The above description is merely a specific embodiment 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. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0113] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, the computer-readable program instructions being used to execute the meeting recording control method in the above embodiments.

[0114] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems or devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0115] The aforementioned computer-readable storage medium may be included in the conference recording control device; or it may exist independently and not be assembled into the conference recording control device.

[0116] The aforementioned computer-readable storage medium carries one or more programs. When the one or more programs are executed by the conference recording control device, the conference recording control device causes the following: to acquire an interaction signal generated by the attached mobile power supply device and acquire the current control state of the mobile terminal; to jointly determine the interaction signal and the current control state, and generate a conference recording intent recognition result based on the joint determination; when the conference recording intent recognition result meets preset activation conditions, to create a conference task and start the conference recording of the conference task; to monitor the current control state, switch the recording mode of the conference recording based on the monitoring result of the current control state, and output recording feedback.

[0117] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a Local Area Network (LAN) or a Wide Area Network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0118] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0119] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0120] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described meeting recording control method, thereby solving the technical problem of meeting recording control. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the meeting recording control method provided in the above embodiments, and will not be repeated here.

[0121] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the meeting recording control method described above.

[0122] The computer program product provided in this application can solve the technical problem of meeting record control. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as the beneficial effects of the meeting record control method provided in the above embodiments, and will not be repeated here.

[0123] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.

Claims

1. A method for controlling meeting minutes, characterized in that, The meeting record control method includes: Acquire the interactive signals generated by the attached mobile power supply device and acquire the current control status of the mobile terminal; The interaction signal and the current control state are jointly determined, and a meeting recording intent recognition result is generated based on the joint determination; When the meeting recording intent recognition result meets the preset activation conditions, a meeting task is created and the meeting recording of the meeting task is started; Monitor the current control status, switch the recording mode of the meeting minutes based on the monitoring results of the current control status, and output recording feedback.

2. The meeting record control method as described in claim 1, characterized in that, The steps of acquiring the interactive signal generated by the attached mobile power supply device and acquiring the current control state of the mobile terminal include: Detect user press operations on the attached mobile power supply device, and generate interactive signals based on the user press operations; The interaction signal is sent to the mobile terminal to obtain the current control status of the mobile terminal.

3. The meeting record control method as described in claim 1, characterized in that, The interactive signals include one or more of the following: press event, press duration, number of presses, device attachment status, and device connection status; the current control status includes one or more of the following: application availability status, recording permission status, meeting task status, audio resource availability status, storage status, and battery status.

4. The meeting record control method as described in claim 1, characterized in that, The meeting recording intent recognition result includes valid meeting recording intent recognition result and invalid meeting recording intent recognition result. The step of jointly determining the interaction signal and the current control state, and generating the meeting recording intent recognition result based on the joint determination, includes: The accidental touch risk is determined based on preset accidental touch risk conditions for the interaction signal and the current control state; When the accidental touch risk is determined to be non-compliant with the accidental touch risk conditions, the executability of the interaction signal and the current control state is determined based on preset executable normal conditions; When the executability determination is that it meets the normal executability conditions, the interactive signal and the current control state are determined to be recordable based on the preset normal recordability conditions; When the recordability determination meets the normal recordability conditions, the interaction signal and the current control state are determined to pass the joint determination, and a valid meeting recording intent recognition result is generated; When the accidental touch risk is determined to meet the accidental touch risk conditions, and / or the executability is determined to not meet the normal executability conditions, and / or the recordability is determined to not meet the normal recordability conditions, the interaction signal and the current control state are determined not to pass the joint determination, and an invalid meeting record intent identification result is generated.

5. The meeting record control method as described in claim 4, characterized in that, The step of creating a meeting task and starting the meeting recording of the meeting task when the meeting recording intent recognition result meets the preset activation conditions includes: If the meeting recording intent recognition result is a valid meeting recording intent recognition result, then the meeting recording intent recognition result is determined to meet the preset activation conditions; When the meeting recording intent recognition result meets the activation conditions, a meeting task is created; Initialize the recording segment based on the task identifier of the meeting task, and configure the audio recording parameters; The meeting recording of the meeting task is initiated based on the initial recording segment and the audio recording parameters.

6. The meeting record control method as described in claim 4, characterized in that, After the step of jointly determining the interaction signal and the current control state, and generating a meeting recording intent recognition result based on the joint determination, the method further includes: If the meeting recording intent recognition result is an invalid meeting recording intent recognition result, then it is determined that the meeting recording intent recognition result does not meet the preset start conditions; When the meeting recording intent recognition result does not meet the activation conditions, a blocking control command is generated; Based on the blocking control command, the initiation of the meeting record and / or the creation of the meeting task are blocked, and a status prompt corresponding to the invalid meeting record intent identification result is generated.

7. The meeting record control method as described in claim 1, characterized in that, The steps of monitoring the current control state, switching the recording mode of the meeting minutes based on the monitoring result of the current control state, and outputting recording feedback include: Monitor the current control state, and determine whether the current control state meets the preset continuous recording conditions based on the monitoring results of the current control state; When the current control state does not meet the continuous recording conditions, the recording mode is switched to one or more of the following: recording protection mode, recovery waiting mode, and status prompt mode; The final control result of the meeting recording is determined based on the switched recording mode; The final control result is used to output a recording feedback, which includes one or more of the following: recording start, recording failure, recording protection, recording saved, waiting to be restored, and unavailable.

8. A meeting recording control device, characterized in that, The meeting recording control device includes: The acquisition module is used to acquire the interactive signals generated by the attached mobile power supply device and to acquire the current control status of the mobile terminal. The determination module is used to jointly determine the interaction signal and the current control state, and generate a meeting record intent recognition result based on the joint determination; The recording module is used to create a meeting task and start the meeting recording of the meeting task when the meeting recording intent recognition result meets the preset start conditions; The switching module is used to monitor the current control status, switch the recording mode of the meeting minutes based on the monitoring results of the current control status, and output recording feedback.

9. A meeting recording control device, characterized in that, The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the conference recording control method as described in any one of claims 1 to 7.

10. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the meeting recording control method as described in any one of claims 1 to 7.

Images