Voice interaction method and device, computer device and storage medium

Abstract

The application relates to a voice interaction method and device, computer equipment and a storage medium, and relates to the technical field of computer programs. The visible control and the invisible control triggered by the same trigger event are set, the visible control is not provided with a hotword attribute, and the invisible control is provided with a hotword attribute. Since the control carrying the hotword can be separated from the visible control of the interface, when multiple functions are realized for the visible control, the hotword attribute of each invisible control can be set to realize the corresponding function, so that the complicated and error-prone situation caused by repeatedly setting the hotword attribute through code logic can be improved. In addition, since the control carrying the hotword can be separated from the visible control of the interface, the visible control is specially used for responding to manual click triggering, and the invisible control is specially used for responding to visible voice input triggering, so that the source of the current control response triggering can be distinguished in real time, and diversified needs can be met.

Description

Technical Field

[0001] This application relates to the field of computer program technology, and in particular to a voice interaction method, apparatus, computer device and storage medium. Background Technology

[0002] Most in-vehicle smart cockpit systems on the market now come equipped with voice assistant functionality. Among these, the "what you see is what you speak" technology refers to the ability to directly control and access corresponding UI controls on the in-vehicle system's interface elements through voice activation and input, thereby enabling interface operation. This technology registers and scans text on the interface using Android Accessibility Services, and when the user activates the system with their voice, it matches the user's input with UI controls that have been registered with relevant keywords, thus accurately responding to the specified control.

[0003] However, since each control can only set one hot word attribute to implement one voice function, when multiple voice functions need to be implemented through one control, processing logic needs to be added to the code logic to repeatedly change the hot word attribute of the control to implement multiple voice functions. This makes the logic cumbersome and prone to errors. Summary of the Invention

[0004] Therefore, it is necessary to provide a voice interaction method, device, computer equipment, storage medium, and computer program product that simplifies the implementation logic of multiple functions to address the above-mentioned technical problems.

[0005] Firstly, this application discloses a voice interaction method applied to a voice interaction interface. The voice interaction interface contains matching visible and invisible controls. The visible controls do not have a hot word attribute set. The trigger event of a visible control after being touched is the same as the trigger event of the matching invisible control after being triggered by a hot word. The method includes:

[0006] Obtain the target hot words carried by voice interaction commands;

[0007] Match the target hot words with the hot word attributes of invisible controls on the voice interaction interface to determine the target invisible controls that match the target hot words;

[0008] Based on the trigger event of the invisible target control after being triggered by a hot word, the corresponding voice interaction process is executed.

[0009] In one embodiment, when a visible control is used to implement multiple functions, the number of functions implemented by the visible control is the same as the number of matching invisible controls. The hot word attribute of each invisible control that matches the visible control corresponds to one function, and the invisible controls that match the visible control are stacked on the voice interaction interface.

[0010] In one embodiment, invisible controls have their touch events disabled.

[0011] In one embodiment, the process of disabling touch events for invisible controls includes:

[0012] For touch event handling methods used by invisible controls, set the return value of the handling method to false.

[0013] In one embodiment, the method further includes:

[0014] In response to voice interaction commands, display corresponding animations based on the position of invisible controls within the voice interaction interface.

[0015] In one embodiment, the display size of the invisible control is set to 0 to 2 pixels, and the type of the invisible control is one of the following control types, including image controls, text controls, and button controls.

[0016] Secondly, this application also provides a voice interaction device, which includes:

[0017] The acquisition module is used to acquire the target hot words carried by the voice interaction commands;

[0018] The matching module is used to match the target hot words with the hot word attributes of invisible controls on the voice interaction interface, and to determine the target invisible controls that match the target hot words.

[0019] The execution module is used to execute the corresponding voice interaction process based on the trigger event of the target invisible control after it is triggered by a hot word.

[0020] Thirdly, this application also provides a computer device, which includes a memory and a processor. The memory stores a computer program applied to a voice interaction interface. The voice interaction interface contains matching visible and invisible controls. The visible controls do not have a hot word attribute set. The trigger event of the visible control after being touched is the same as the trigger event of the matching invisible control after being triggered by a hot word. When the processor executes the computer program, it implements the following steps:

[0021] Obtain the target hot words carried by voice interaction commands;

[0022] Match the target hot words with the hot word attributes of invisible controls on the voice interaction interface to determine the target invisible controls that match the target hot words;

[0023] Based on the trigger event of the invisible target control after being triggered by a hot word, the corresponding voice interaction process is executed.

[0024] Fourthly, this application also provides a computer-readable storage medium storing a computer program applied to a voice interaction interface. The voice interaction interface contains matching visible and invisible controls. The visible controls do not have a hot word attribute set. The trigger event of a visible control after being touched is the same as the trigger event of the matching invisible control after being triggered by a hot word. When the computer program is executed by a processor, it performs the following steps:

[0025] Obtain the target hot words carried by voice interaction commands;

[0026] Match the target hot words with the hot word attributes of invisible controls on the voice interaction interface to determine the target invisible controls that match the target hot words;

[0027] Based on the trigger event of the invisible target control after being triggered by a hot word, the corresponding voice interaction process is executed.

[0028] Fifthly, this application also provides a computer program product. This computer program product includes a computer program applied to a voice interaction interface. The voice interaction interface contains matching visible and invisible controls. The visible controls do not have a hot word attribute set. The trigger event of the visible controls after being touched is the same as the trigger event of the matching invisible controls after being triggered by a hot word. When the computer program is executed by a processor, it implements the following steps:

[0029] Obtain the target hot words carried by voice interaction commands;

[0030] Match the target hot words with the hot word attributes of invisible controls on the voice interaction interface to determine the target invisible controls that match the target hot words;

[0031] Based on the trigger event of the invisible target control after being triggered by a hot word, the corresponding voice interaction process is executed.

[0032] The aforementioned voice interaction methods, devices, computer equipment, storage media, and computer program products, by setting visible and invisible controls that have the same triggering event after being triggered, do not set hot word attributes for visible controls, but set hot word attributes for invisible controls. Since the control carrying the hot word can be separated from the visible controls on the interface, when implementing multiple functions for a visible control, multiple matching invisible controls can be set for that visible control, and the corresponding function can be achieved by setting the hot word attribute for each invisible control separately. This improves the cumbersome and error-prone situation caused by repeatedly setting hot word attributes through code logic.

[0033] In addition, since the control that carries hot words can be separated from the visible controls on the interface, the visible controls are dedicated to responding to manual clicks, while the invisible controls are dedicated to responding to voice input that can be spoken as long as it is visible. This allows for real-time differentiation of the source of the control response trigger, thus meeting diverse needs. Attached Figure Description

[0034] Figure 1 This is a schematic diagram illustrating an implementation scenario of the voice interaction method in one embodiment;

[0035] Figure 2 This is a flowchart illustrating a voice interaction method in one embodiment;

[0036] Figure 3 This is a flowchart illustrating the voice interaction method in another embodiment;

[0037] Figure 4 This is a schematic diagram illustrating the functional implementation of the UI control and the View control in one embodiment;

[0038] Figure 5 This is a structural block diagram of a voice interaction device in one embodiment;

[0039] Figure 6 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0040] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0041] It is understood that the terms "first," "second," etc., used in this application may be used to describe various technical terms, but unless otherwise specified, these technical terms are not limited to these terms. These terms are only used to distinguish one technical term from another. For example, without departing from the scope of this application, the third preset threshold and the fourth preset threshold may be the same or different.

[0042] Most in-vehicle smart cockpit systems on the market now come equipped with voice assistant functionality. Among these, the "what you see is what you speak" technology refers to the ability to directly control and access corresponding UI controls on the in-vehicle system's interface elements through voice activation and input, thereby enabling interface operation. This technology registers and scans text on the interface using Android Accessibility Services, and when the user activates the system with their voice, it matches the user's input with UI controls that have been registered with relevant keywords, thus accurately responding to the specified control.

[0043] In related technologies, the common practice is to directly write the required voice-enabled commands for a UI control into its `android:contentDescription` attribute within the Android layout file. This allows the voice accessibility server to scan the interface and match the control's `android:contentDescription` attribute with the user's preferred keywords for the desired response. For example:

[0044] <Button < / button>

[0045] android:id="@+id / pause_button"

[0046] android:src=”@drawable / pause”

[0047] android:contentDescription="Pause" / >

[0048] In other words, this button control can be configured to respond when the user voice inputs the keyword "pause," thereby pausing the music.

[0049] Several defects may exist in the above process:

[0050] (1) For controls with multiple functions, it is impossible to distinguish the attribute settings of hot words. For example, the pause button mentioned above needs to respond to the "play" command when paused. When playing, the button needs to respond to the "pause" command. However, in the layout, the button can only set one instruction related to android:contentDescription, which means that the hot word attribute of contentDescription needs to be reset repeatedly in the code logic according to whether the current audio is playing or paused, making the logic cumbersome and error-prone.

[0051] (2) It is impossible to distinguish between the user's manual click response and the user's voice input response that is visible and can be spoken. Because hot words are set, after the voice accessibility service scans and matches successfully, it will directly trigger a click event to respond to the hot word. However, the user's manual click will also trigger the same click event. This makes it impossible for the interface to distinguish the triggering method of the click event, and therefore impossible to design targeted interactions for the two triggering methods. For example, if the interaction wants to provide voice TTS feedback to the user when the hot word is triggered by voice, but not when the manual click is triggered, it is impossible to distinguish between them.

[0052] ​(3) The trigger position of the visible-to-speak animation cannot be accurately located. Currently, when adding animations to the visible-to-speak control response, such as a water ripple animation, the animation is usually achieved by extracting the center coordinates of the hot word control on the voice accessibility service scanning end. The animation is generally not implemented by the controls on the interface, firstly because the above-mentioned defect (2) cannot distinguish between voice response and manual click response. Secondly, it is a lot of repetitive work to make the animation for each app application, but the scanning end can only determine the position of the animation by pre-defining an extraction rule, such as extracting the center position. However, based on the user's interaction experience, not all interface designs need to respond to the center position, thus failing to meet the differentiated animation trigger position.

[0053] In related technologies, the android:contentDescription attribute of a control can be defined more complexly using a JSON string, thus expanding the control's response methods to be more diverse. For example:

[0054] <Button < / button>

[0055] android:id="@+id / pause_button"

[0056] android:src=”@drawable / pause”

[0057] android:contentDescription=”{"func":"open","value":["favorites","favorite music","my favorites"]}” / >

[0058] In the code above, by specifying the `func` field as `open`, the specified hot word can be generalized and expanded to "open xxx", and the `value` field can have three hot words. Therefore, the button can respond to three types of voice input: "open favorites", "open favorite music", and "open my favorites". The above process, through preset JSON rules, allows for more flexible hot word settings and supports multiple hot word responses.

[0059] However, the above process still has the defects mentioned in (3), that is, even if multiple hot words can be responded to, it is still impossible to accurately locate the trigger position of the visible and talkable animation.

[0060] To address the aforementioned problems, this application provides a voice interaction method that can be used between a terminal and a server, specifically for applications such as... Figure 1 ​In the application environment shown, terminal 102 can acquire the target hot word carried by the voice interaction command. It matches the target hot word with the hot word attributes of invisible controls on the voice interaction interface to determine the target invisible control that matches the hot word. Based on the trigger event of the target invisible control after being triggered by the hot word, it sends a voice interaction request to server 104. Server 104 returns a feedback result to the terminal, allowing terminal 102 to execute the corresponding voice interaction process based on the feedback result. Terminal 102 can be a mobile terminal, personal computer, smart TV, tablet, or in-vehicle infotainment system, etc., while server 104 can be implemented as a server cluster consisting of multiple servers; this embodiment does not specifically limit this.

[0061] In some embodiments, see Figure 2 This provides a voice interaction method. This method is applied to... Figure 1 The method is illustrated using terminal 102 as an example. Accordingly, this method can be applied to a voice interaction interface, which contains matching visible and invisible controls. The visible controls do not have a hot word attribute set, and the trigger event of the visible control after being touched is the same as the trigger event of the matching invisible control after being triggered by a hot word.

[0062] The voice interaction interface can be a mobile terminal interface or a vehicle-mounted terminal interface; this application embodiment does not specifically limit this. Visible controls refer to controls that the user can visually perceive in the interface, while invisible controls refer to controls that the user cannot visually perceive in the interface. Visible controls are mainly provided for user touch responses, while invisible controls are mainly provided for user voice input responses; both can correspond to the same trigger event when triggered. Hot word attributes can be set through `contentDescription`. In this application embodiment, to prevent visible controls from responding to hot words, hot word attributes can be set only for invisible controls, not visible controls.

[0063] For ease of understanding, this application uses a vehicle-to-machine (V2M) interaction scenario and a voice interaction interface as an example for explanation. Therefore, the method includes the following steps:

[0064] 202. Obtain the target hot words carried by the voice interaction command.

[0065] Among these features, voice interaction commands can be triggered by the user. After receiving the voice interaction command, the in-vehicle terminal can perform voice recognition to obtain the target hot words.

[0066] 204. Match the target hot words with the hot word attributes of invisible controls on the voice interaction interface to determine the target invisible controls that match the target hot words.

[0067] Specifically, the voice interaction interface can have multiple visible controls. For each visible control, at least one matching invisible control can be set, but this embodiment does not specifically limit this. "Matching" means that the visible and invisible controls correspond to the same triggering event when triggered. By performing text or direct voice matching between the target hot word and the hot word attributes of the invisible controls on the voice interaction interface, it can be determined which invisible control on the voice interaction interface matches the target hot word.

[0068] 206. Based on the trigger event of the invisible target control after being triggered by a hot word, execute the corresponding voice interaction process.

[0069] In this application, the trigger event for an invisible target control after being triggered by a hot word can be an onClick event, but this embodiment does not specifically limit this. The corresponding voice interaction process can be achieved by executing the corresponding logic of the trigger event.

[0070] The aforementioned voice interaction method sets visible and invisible controls that share the same trigger event when activated. It does not set hotword attributes for visible controls, but sets them for invisible controls. Because the control carrying the hotword can be separated from the visible controls, multiple matching invisible controls can be set for a visible control when implementing multiple functions. The corresponding function can be achieved by setting the hotword attribute for each invisible control separately. This improves upon the tedious and error-prone process of repeatedly setting hotword attributes through code logic.

[0071] In addition, since the control that carries hot words can be separated from the visible controls on the interface, the visible controls are dedicated to responding to manual clicks, while the invisible controls are dedicated to responding to voice input that can be spoken as long as it is visible. This allows for real-time differentiation of the source of the control response trigger, thus meeting diverse needs.

[0072] In some embodiments, when a visible control is used to implement multiple functions, the number of functions implemented by the visible control is the same as the number of matching invisible controls. The hot word attribute of each invisible control that matches the visible control corresponds to one function. The invisible controls that match the visible control are stacked on the voice interaction interface.

[0073] As mentioned earlier, each visible control has multiple matching invisible controls, each invisible control corresponds to a function that needs to be implemented, and the corresponding hot word attributes of each invisible control can be set based on the function to be implemented. In addition, since invisible controls do not need to respond to manual clicks, in order to save space on the control layout of the voice interaction interface, invisible controls can be stacked on top of each other.

[0074] In the above embodiments, since the control carrying the hot words can be separated from the visible controls on the interface, when implementing multiple functions for the visible controls, multiple matching invisible controls can be set for the visible controls, and the corresponding functions can be achieved by setting the hot word attributes of each invisible control separately. This can improve the tedious and error-prone situation caused by repeatedly setting hot word attributes through code logic.

[0075] In some embodiments, touch events are disabled for invisible controls.

[0076] In practice, invisible controls can be configured to either disable touch events or not. However, if touch events are not disabled, invisible controls may still be accidentally triggered.

[0077] In the above embodiments, since touch events of invisible controls can be disabled, visible controls can be dedicated to responding to manual click triggers, and invisible controls can be dedicated to responding to voice input triggers that are visible and can be spoken, thereby reducing the possibility of invisible controls being accidentally triggered and improving operation accuracy.

[0078] In some embodiments, the process of disabling touch events for invisible controls includes:

[0079] For touch event handling methods used by invisible controls, set the return value of the handling method to false.

[0080] Specifically, the method for handling touch events can be `onTouchEvent`. In practice, the `onTouchEvent` method can be rewritten to return `false`. It returns `true` when the `onTouchEvent` method has fully processed the event and does not want other callback methods to process it again; otherwise, it returns `false`.

[0081] In the above embodiments, since the return value of the processing method for handling touch events can be set to false, visible controls can be dedicated to responding to manual click triggers, and invisible controls can be dedicated to responding to voice input triggers that are visible and can be spoken, thereby reducing the possibility of invisible controls being accidentally triggered and improving operation accuracy.

[0082] In some embodiments, the method further includes:

[0083] In response to voice interaction commands, display corresponding animations based on the position of invisible controls within the voice interaction interface.

[0084] The position of each invisible control can be set according to the animation effect requirements. When implementing the animation effect, the animation trigger position can be determined based on the position of each invisible control according to the extraction rules for each invisible control, so that the animation effect can be displayed at the corresponding position.

[0085] In the above embodiments, since multiple matching invisible controls can be set for visible controls, and the position of each invisible control can be set according to the animation requirements, instead of extracting the animation trigger position based only on the position of the visible control during the voice accessibility service scanning process as before, the differentiated animation trigger position requirements can be met.

[0086] In some embodiments, the display size of the invisible control is set to 0 to 2 pixels. The type of the invisible control is one of the following control types, including image control, text control and button control.

[0087] The display size of the invisible control can be set to 0 to 2 pixels. In practice, the invisible control can also be set to other display sizes, as long as it is invisible to the user. Furthermore, the type of the invisible control can be a control with customizable keyword attributes; this application does not specifically limit this.

[0088] In the above embodiments, since the controls can be made invisible by setting their display size, the interference caused by the controls carrying hot words to the voice interaction interface can be reduced. Furthermore, since multiple control types can be used as invisible controls, versatility can be improved.

[0089] For ease of understanding, this paper takes an in-vehicle infotainment system using Android as an example. The method flow provided in this application embodiment will be described below. See also... Figure 3 The specific implementation can be shown in the following steps:

[0090] 302. Add a 0px or 1px View control to the Android layout file, set the View control's android:contentDescription to the hot word that needs to be responded to, and place the View control in the position where the animation effect needs to be displayed in the voice interaction interface.

[0091] In addition to using the View control, other sub-controls under the View class, such as TextView, ImageView, and Button, can also be used. Since accessibility scanning does not filter the display size of the View, even if the display size is 0px or 1px, it will not affect the response to trending words.

[0092] 304. Disable touch events for this View control and set the trigger source to only trigger from voice hot words so as not to affect manual clicks by the user.

[0093] One way to achieve this is to override the onTouchEvent method of the View control and make it return false, so that the View control is only triggered by voice hot words.

[0094] 306. Set the onClick event of the View control and the onClick event of the UI control that matches the View control to the same response event as the hot word function, and do not set android:contentDescription for the UI control that matches the View control.

[0095] In cases involving multiple functions, multiple 0px View controls can be stacked and arranged, each with different keyword attributes set for its function. It should be noted that in practice, a single custom control can be defined to encapsulate the keyword button functionality, making it a generic custom control and avoiding redundant logic. The above process can be referenced. Figure 4 ,exist Figure 4 In the interface, users can trigger functions through two methods: manual clicking and speaking when the view is visible. View1 to View3, each 0px in size, can be bound to visible UI controls on the page for layout and placement. These three controls can trigger different hotword responses to achieve different voice functions.

[0096] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0097] Based on the same inventive concept, this application also provides a voice interaction device for implementing the voice interaction method described above. The solution provided by this device is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more voice interaction device embodiments provided below can be found in the limitations of the voice interaction method described above, and will not be repeated here.

[0098] In one embodiment, such as Figure 5 As shown, a voice interaction device is provided for use in a voice interaction interface. The voice interaction interface contains matching visible and invisible controls. The visible controls do not have a hot word attribute set. The trigger event of a visible control after being touched is the same as the trigger event of the matching invisible control after being triggered by a hot word. The device includes: an acquisition module 502, a matching module 504, and an execution module 506, wherein:

[0099] The acquisition module 502 is used to acquire the target hot words carried by the voice interaction command;

[0100] The matching module 504 is used to match the target hot words with the hot word attributes of invisible controls on the voice interaction interface, and to determine the target invisible controls that match the target hot words.

[0101] The execution module 506 is used to execute the corresponding voice interaction process based on the trigger event of the target invisible control after being triggered by a hot word.

[0102] In some embodiments, when a visible control is used to implement multiple functions, the number of functions implemented by the visible control is the same as the number of matching invisible controls. The hot word attribute of each invisible control that matches the visible control corresponds to one function. The invisible controls that match the visible control are stacked on the voice interaction interface.

[0103] In some embodiments, touch events are disabled for invisible controls.

[0104] In some embodiments, the execution module 506 is further configured to set the return value of the processing method for handling touch events corresponding to the invisible control to false.

[0105] In some embodiments, the execution module 506 is further configured to respond to a voice interaction command by displaying a corresponding animation based on the position of the invisible control in the voice interaction interface.

[0106] In some embodiments, the display size of the invisible control is set to 0 to 2 pixels. The type of the invisible control is one of the following control types, including image control, text control and button control.

[0107] The aforementioned voice interaction device sets visible and invisible controls that share the same trigger event when activated. It does not set hotword attributes for visible controls, but sets them for invisible controls. Because the control carrying the hotword can be separated from the visible controls, when implementing multiple functions for a visible control, multiple matching invisible controls can be set for that visible control. The corresponding function can be achieved by setting the hotword attribute for each invisible control separately. This improves upon the tedious and error-prone process of repeatedly setting hotword attributes through code logic.

[0108] In addition, since the control that carries hot words can be separated from the visible controls on the interface, the visible controls are dedicated to responding to manual clicks, while the invisible controls are dedicated to responding to voice input that can be spoken as long as it is visible. This allows for real-time differentiation of the source of the control response trigger, thus meeting diverse needs.

[0109] For specific limitations regarding the voice interaction device, please refer to the limitations on the voice interaction method above, which will not be repeated here. Each module in the aforementioned voice interaction device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in the computer device in hardware form, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0110] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 6As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a voice interaction method. The display unit is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0111] Those skilled in the art will understand that Figure 6 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0112] In one embodiment, a computer device is provided, including a memory and a processor. The memory stores a computer program applied to a voice interaction interface. The voice interaction interface has matching visible and invisible controls. The visible controls do not have a hot word attribute set. The trigger event of a visible control after being touched is the same as the trigger event of the matching invisible control after being triggered by a hot word. When the processor executes the computer program, it performs the following steps:

[0113] Obtain the target hot words carried by voice interaction commands;

[0114] Match the target hot words with the hot word attributes of invisible controls on the voice interaction interface to determine the target invisible controls that match the target hot words;

[0115] Based on the trigger event of the invisible target control after being triggered by a hot word, the corresponding voice interaction process is executed.

[0116] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, applied to a voice interaction interface. The voice interaction interface contains matching visible and invisible controls. The visible controls do not have a hot word attribute set. The trigger event of a visible control after being touched is the same as the trigger event of the matching invisible control after being triggered by a hot word. When the computer program is executed by a processor, it performs the following steps:

[0117] Obtain the target hot words carried by voice interaction commands;

[0118] Match the target hot words with the hot word attributes of invisible controls on the voice interaction interface to determine the target invisible controls that match the target hot words;

[0119] Based on the trigger event of the invisible target control after being triggered by a hot word, the corresponding voice interaction process is executed.

[0120] In one embodiment, a computer program product is provided, including a computer program applied to a voice interaction interface. The voice interaction interface contains matching visible and invisible controls. The visible controls do not have a hot word attribute set. The trigger event of a visible control after being touched is the same as the trigger event of the matching invisible control after being triggered by a hot word. When the computer program is executed by a processor, it implements the following steps:

[0121] Obtain the target hot words carried by voice interaction commands;

[0122] Match the target hot words with the hot word attributes of invisible controls on the voice interaction interface to determine the target invisible controls that match the target hot words;

[0123] Based on the trigger event of the invisible target control after being triggered by a hot word, the corresponding voice interaction process is executed.

[0124] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0125] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0126] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A voice interaction method, characterized in that, The method is applied to a voice interaction interface, which contains matching visible and invisible controls. The visible controls do not have a hot word attribute set, and the trigger event of the visible control after being touched is the same as the trigger event of the matching invisible control after being triggered by a hot word. The method includes: Obtain the target hot words carried by voice interaction commands; The target hot word is matched with the hot word attribute of the invisible control on the voice interaction interface to determine the target invisible control that matches the target hot word; Based on the trigger event of the target invisible control after being triggered by a hot word, the corresponding voice interaction process is executed; When the visible control is used to implement multiple functions, the number of functions implemented by the visible control is the same as the number of matching invisible controls. The hot word attribute of each invisible control that matches the visible control corresponds to one function. The invisible controls that match the visible control are stacked on the voice interaction interface.

2. The method according to claim 1, characterized in that, The invisible control has its touch events disabled.

3. The method according to claim 2, characterized in that, The process of disabling touch events for the invisible control includes: For the handling method used to process touch events for the invisible control, set the return value of the handling method to false.

4. The method according to claim 1, characterized in that, The method further includes: In response to the voice interaction command, corresponding animation effects are displayed based on the position of the invisible control in the voice interaction interface.

5. The method according to any one of claims 1 to 4, characterized in that, The display size of the invisible control is set to 0 to 2 pixels. The type of the invisible control is one of the following control types, which include image control, text control and button control.

6. A voice interaction device, characterized in that, The device includes: The acquisition module is used to acquire the target hot words carried by the voice interaction commands; The matching module is used to match the target hot word with the hot word attributes of invisible controls on the voice interaction interface, and to determine the target invisible control that matches the target hot word; The execution module is used to execute the corresponding voice interaction process based on the trigger event of the target invisible control after being triggered by a hot word; When the visible control is used to implement multiple functions, the number of functions implemented by the visible control is the same as the number of matching invisible controls. The hot word attribute of each invisible control that matches the visible control corresponds to one function. The invisible controls that match the visible control are stacked on the voice interaction interface.

7. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 5.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 5.

9. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 5.

Images