Scene processing method, electronic device and storage medium

Abstract

The present application provides a scene processing method, an electronic device and a storage medium, and relates to the field of computer technology. The method includes: when a touch start event is detected, a recording start event is detected within a preset time interval, and a first application and a second application are detected to be consistent, determining that the current scene is a voice input scene; in the voice input scene, reducing the power consumption parameter of the electronic device, or increasing the power consumption parameter to a first value. When identifying the voice input scene, the scene processing method does not rely on layout information and Activity information, but identifies the voice input scene according to the logic of generating the voice input scene, thereby accurately identifying the voice input scene. Reducing the power consumption of the electronic device in the voice input scene can reduce the loss of each component of the electronic device without affecting the user experience, thereby improving the battery life and life of the electronic device.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a scene processing method, an electronic device and a storage medium. Background Art

[0002] With the rapid development of electronic technology, the penetration rate of electronic devices such as mobile phones and tablet computers is getting higher and higher, and with the development of network technology, the application functions of electronic devices are becoming more and more abundant.

[0003] For example, current electronic devices are all installed with instant messaging (IM) software, and the voice chat function supported in the IM software is very popular among users.

[0004] During voice chat, the animation drawing / synthesis during voice input / recording will cause power consumption waste, which is usually solved by identifying the voice input scene and reducing the power consumption in the voice input scene. However, in the related art, it is impossible to accurately identify the voice input scene, resulting in an inability to accurately reduce the power consumption in the voice input scene. Summary of the invention

[0005] The present application provides a scene processing method, an electronic device, and a storage medium. When identifying a voice input scene, the scene processing method does not rely on layout information and Activity information, but identifies the voice input scene according to the logic of generating the voice input scene, thereby accurately identifying the voice input scene. Reducing the power consumption of the electronic device in the voice input scene can reduce the loss of each component of the electronic device without affecting the user experience, thereby improving the battery life and life of the electronic device.

[0006] In a first aspect, the present application provides a scene processing method, the method comprising: when a touch start event is detected, and a recording start event is detected within a preset time interval, and when it is detected that a first application and a second application are consistent, determining that the current scene is a voice input scene; in the voice input scene, reducing the power consumption parameter of the electronic device, or increasing the power consumption parameter to a first value, the first value is less than a second value, and the second value is the power consumption parameter increased to the electronic device when a touch start event is detected.

[0007] The first application is the application corresponding to the touch-initiated event. It can be understood that the first application is the application currently receiving the user's touch operation, or the first application is the application that generates the touch-initiated event.

[0008] The second application is the application corresponding to the recording start event. It can be understood that the second application is the application that calls the recording start interface, or the second application is the application that generates the recording start event.

[0009] The current scenario is the current usage scenario of the electronic device.

[0010] Optionally, the power consumption parameter includes any one or any combination of CPU frequency, screen refresh rate, screen brightness, double data rate (DoubleData Rate, DDR) frequency, touch screen (Touch Panel, TP) reporting rate, application drawing frame rate and system synthesis frame rate.

[0011] It should be understood that when the power consumption parameter includes any one of the above, the power consumption parameter is increased to the first value, and the first value includes a value.

[0012] When the power consumption parameter includes any combination of the above, that is, when the power consumption parameter includes at least two of the above parameters, the power consumption parameter is increased to a first value, and the first value includes at least two values.

[0013] The scene processing method provided in the first aspect determines that the current scene is a voice input scene when a touch start event is detected, a recording start event is detected within a preset time interval, and the first application and the second application are detected to be consistent; in the voice input scene, the power consumption parameter of the electronic device is reduced, or the power consumption parameter is increased to a first value, the first value is less than the second value, and the second value is the power consumption parameter increased to the electronic device when the touch start event is detected.

[0014] Since the logic of generating a voice input scene is that a touch start event occurs first and then a recording start event occurs, and the time interval between the touch start event and the recording start event is within a preset time interval, and the application in which the touch start event occurs is consistent with the application in which the recording start event occurs. The scene processing method provided in the present application does not rely on layout information and Activity information when identifying a voice input scene, but identifies the voice input scene according to the logic of generating a voice input scene, thereby accurately identifying the voice input scene.

[0015] Compared with the related art in which power consumption parameters are increased when a touch start event is detected, the scene processing method provided in the present application reduces the power consumption parameters of the electronic device in the voice input scene, or increases the power consumption parameters to a first value, thereby effectively reducing the power consumption of the electronic device in the voice input scene. While not affecting the user experience, it reduces the loss of various components of the electronic device and improves the battery life and life of the electronic device.

[0016] In one possible implementation, the scene processing method provided by the present application, before determining that the current scene is a voice input scene, further includes: when a touch start event is detected, recording the first time of the touch start event; when a recording start event is detected, recording the second time of the recording start event; when the difference between the second time and the first time is less than a preset time interval, determining that the recording start event is detected within the preset time interval.

[0017] In this implementation, the time of the touch start event and the recording start event is recorded, the difference between the two times is calculated and compared with the preset time interval, so as to determine that the recording start event is detected within the preset time interval. This can prove that the touch start event occurred first, followed by the recording start event, and the time interval between the touch start event and the recording start event is within the preset time interval, which meets the situation of the voice input scenario, and provides a guarantee for the subsequent accurate recognition of the voice input scenario.

[0018] In one possible implementation, the scene processing method provided by the present application, before determining that the current scene is a voice input scene, further includes: obtaining first identification information of the first application; obtaining second identification information of the second application; and when it is detected that the first identification information is the same as the second identification information, determining that the first application and the second application are consistent.

[0019] In this implementation, by comparing the first identification information of the first application with the second identification information of the second application, it is determined that the first application and the second application are the same. This can prove that the application where the touch start event occurs and the application where the recording start event occurs are the same, which meets the situation of the voice input scenario and provides a guarantee for the subsequent accurate recognition of the voice input scenario.

[0020] Optionally, the first identification information may include a first UID and / or a first application package name, and the second identification information may include a second UID and / or a second application package name.

[0021] In one possible implementation, when the first identification information includes a first UID and the second identification information includes a second UID, determining that the first application and the second application are consistent includes: when it is detected that the first UID is the same as the second UID, determining that the first application and the second application are consistent.

[0022] In one possible implementation, when the first identification information includes a first application package name and the second identification information includes a second application package name, determining that the first application and the second application are consistent includes: when it is detected that the first application package name is the same as the second application package name, determining that the first application and the second application are consistent.

[0023] In one possible implementation, when the first identification information includes a first UID and a first application package name, and the second identification information includes a second UID and a second application package name, determining that the first application and the second application are consistent includes: when it is detected that the first UID is the same as the second UID, and the first application package name is the same as the second application package name, determining that the first application and the second application are consistent.

[0024] In one possible implementation, the scenario processing method provided in the present application also includes: in a voice input scenario, after reducing the power consumption parameters of the electronic device, when a touch end event and / or a recording end event is detected, the power consumption parameters of the electronic device are not reduced.

[0025] In this implementation, when a touch end event and / or a recording end event is detected, the power consumption parameters of the electronic device are not reduced. In other words, when a touch end event and / or a recording end event is detected, the method of adjusting the power consumption parameters in the non-voice input scenario is restored. For example, the power consumption parameters are increased when a touch event is detected. This is beneficial for improving the fluency of the electronic device in the non-voice input scenario and providing a better experience for the user.

[0026] In one possible implementation, the scenario processing method provided in the present application also includes: in a voice input scenario, after the power consumption parameter is increased to a first value, when a touch end event and / or a recording end event is detected, the power consumption parameter is not increased to the first value.

[0027] In this implementation, when a touch end event and / or a recording end event is detected, the power consumption parameter is not increased to the first value. In other words, when a touch end event and / or a recording end event is detected, the method of adjusting the power consumption parameter in a non-voice input scenario is restored. For example, the power consumption parameter is increased when a touch event is detected. This is beneficial for improving the fluency of the electronic device in a non-voice input scenario and providing a better experience to the user.

[0028] In one possible implementation, the electronic device provided by the present application includes a touch screen driver, and the scene processing method provided by the present application also includes: detecting a touch start event and / or a touch end event through the touch screen driver or the input scheduling thread module.

[0029] In this implementation, touch start events and / or touch end events are detected through a touch screen driver or input scheduling thread module, which enriches the methods of detecting touch start events and / or touch end events and provides multiple implementation methods for subsequently accurately identifying voice input scenarios.

[0030] In a possible implementation, the electronic device provided in the present application includes a microphone driver, and the scene processing method provided in the present application also includes: detecting a recording start event and / or a recording end event through the microphone driver.

[0031] In this implementation, the recording start event and / or the recording end event are detected by driving the microphone, which enriches the methods of detecting the recording start event and / or the recording end event and provides multiple implementation methods for subsequently accurately identifying the voice input scenario.

[0032] In a second aspect, the present application provides an electronic device, comprising: one or more processors; one or more memories; a module with multiple applications installed; the memory stores one or more programs, and when one or more programs are executed by the processor, the electronic device executes the method in the above-mentioned first aspect and any possible implementation thereof.

[0033] In a third aspect, the present application provides a chip, including a processor. The processor is used to read and execute a computer program stored in a memory to perform the method in the first aspect and any possible implementation thereof.

[0034] Optionally, the chip also includes a memory, and the memory is connected to the processor via a circuit or wire.

[0035] Optionally, the chip also includes a communication interface.

[0036] In a fourth aspect, the present application provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the processor executes the method in the first aspect and any possible implementation thereof.

[0037] In a fifth aspect, the present application provides a computer program product, which includes: a computer program code, which, when executed on an electronic device, enables the electronic device to execute the method in the first aspect and any possible implementation thereof.

[0038] The technical effects obtained by the above-mentioned second, third, fourth and fifth aspects are similar to the technical effects obtained by the corresponding technical means in the above-mentioned first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 A schematic diagram of a voice chat operation shown as an exemplary embodiment of the present application;

[0040] Figure 2 Another voice chat operation schematic diagram shown as an exemplary embodiment of the present application;

[0041] Figure 3 This is another voice chat operation schematic diagram shown as an exemplary embodiment of the present application;

[0042] Figure 4This is another voice chat operation schematic diagram shown as an exemplary embodiment of the present application;

[0043] Figure 5 A schematic diagram of the hardware structure of an electronic device shown as an exemplary embodiment of the present application;

[0044] Figure 6 A software structure block diagram of an electronic device shown as an exemplary embodiment of the present application;

[0045] Figure 7 A flowchart of a scene processing method provided in an embodiment of the present application;

[0046] Figure 8 A flowchart of another scene processing method provided in an embodiment of the present application;

[0047] Fig. 9 A schematic diagram of another scene processing method provided in an embodiment of the present application;

[0048] Fig.10 A flowchart of another scene processing method provided in an embodiment of the present application;

[0049] Fig.11 A schematic diagram of the structure of a chip provided in an embodiment of the present application. DETAILED DESCRIPTION

[0050] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0051] In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "multiple" means two or more than two.

[0052] In the following, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this embodiment, unless otherwise specified, "plurality" means two or more.

[0053] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0054] It should be noted that the scene processing method provided in the embodiment of the present application can be applied to any electronic device with a voice processing function.

[0055] In some embodiments of the present application, the electronic device may be a mobile phone, a tablet computer, a wearable device, a television, a vehicle-mounted device, an augmented reality (AR) / virtual reality (VR) device, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), etc., or may be other devices or apparatuses capable of performing scene recognition. The embodiments of the present application do not impose any restrictions on the specific type of the electronic device.

[0056] In order to better understand the scene processing method provided in the embodiments of the present application, some terms involved in the embodiments of the present application are first explained below to facilitate understanding by those skilled in the art.

[0057] 1. Instant Messaging (IM)

[0058] Instant messaging is the most popular communication method on the Internet, which uses instant messaging technology to achieve online chatting and communication.

[0059] 2. Instant Messaging (IM) Application

[0060] An application that uses instant messaging technology to achieve online chatting and communication.

[0061] In the embodiment of the present application, the IM application may include Etc., no limitation is made to this.

[0062] 3. System on Chip (SoC)

[0063] Also known as system on chip, it means that it is a product, an integrated circuit with a dedicated purpose, which contains the complete system and all the contents of embedded software. At the same time, it is also a technology used to realize the entire process from determining the system function to the software / hardware division and completing the design.

[0064] 4. Touch Event

[0065] It is used to respond to the operation of the user's finger on the screen, providing reliable support for the touch-based user interface. The user's operation can be monitored through the touch event, so that the system of the electronic device can respond to the user's operation.

[0066] Touch events are triggered when the user places a finger on the screen, slides it across the screen, or removes it from the screen.

[0067] 5. Touch Panel (TP)

[0068] Also known as a touch panel, it is an inductive liquid crystal display device that can receive input signals such as contacts. When the graphic button on the screen is touched, the tactile feedback system on the screen can drive various connected devices according to the pre-programmed program, which can be used to replace the mechanical button panel and create vivid audio and video effects through the liquid crystal display screen.

[0069] 6. Touch Down Event

[0070] A touch press event is the start of a touch action.

[0071] In the embodiment of the present application, a Touch Down event is generated when a user touches the screen with a finger.

[0072] 7. Touch Up Event

[0073] The touch up event is the end of a touch action.

[0074] In the embodiment of the present application, a Touch Up event is generated when a user lifts a finger on the touch screen.

[0075] 8. Activity

[0076] Activity is one of the four major components of Android. It is a visual interface for user operations, providing users with a window to complete operation instructions. In Android Apps, almost all visible interfaces rely on Activity, so Activity is the most frequently used component in development.

[0077] 9. Layout

[0078] The layout defines the interface structure of the application (for example, the interface structure of an Activity).

[0079] All elements in a layout are built using a hierarchy of visual components (Views) and container (ViewGroup) objects that hold Views. Views typically draw content that users can see and interact with.

[0080] The above is a brief introduction to the terms involved in the embodiments of the present application, which will not be repeated below.

[0081] With the rapid development of electronic technology, the penetration rate of electronic devices such as mobile phones, tablets, and wearable devices is increasing, and with the development of network technology, the application functions of electronic devices are becoming more and more abundant.

[0082] For example, current electronic devices are all equipped with instant messaging (IM) applications, and most of the IM applications support voice chat functions. Since the voice chat function is easy to operate and can quickly transmit information, it is deeply loved by users.

[0083] The operation method of the voice chat function is usually to long press the "press and hold to speak" button to input / record voice, and release the "press and hold to speak" button to end recording after the voice input / recording is completed. At the same time, the IM application sends the input / recorded voice to the recipient.

[0084] The operation method of the voice chat function is described below in conjunction with the accompanying drawings.

[0085] See also Figure 1 and Figure 2 , Figure 1 This is a schematic diagram of a voice chat operation shown as an exemplary embodiment of the present application. Figure 2 Another voice chat operation diagram is shown as an exemplary embodiment of the present application.

[0086] In the embodiment of the present application, the electronic device is a mobile phone and the IM application is For example, Figure 1 As shown, Figure 1 The figure (a) shows Chat main interface, the The chat main interface displays multiple chat partners. In the chat main interface, click on chat object 101, and the mobile phone display interface changes from Figure 1 As shown in (a) Jump to the chat main interface Figure 1 The personal chat interface shown in (b) in FIG. The personal chat interface displays the chat history between the user and the chat object 101. It is worth noting that at this time, the area below the personal chat interface displays a voice input icon 102 and a text input box 103.

[0087] For example, if a user clicks Figure 1 The voice input icon 102 shown in (b) of the mobile phone is displayed from Figure 1 The personal chat interface shown in (b) is displayed as Figure 1 Specifically, in the area below the voice input interface, Figure 1 The voice input icon 102 shown in (b) is changed into a keyboard input icon 104, and the text input box 103 is changed into a voice input box 105. The voice input box 105 also includes a "press and speak" button 1051. Long pressing the "press and speak" button 1051 can realize voice input / recording.

[0088] In one possible implementation, Figure 2 As shown, for example, if the user long presses Figure 2 The "Press and hold to speak" button 1051 in the voice input interface shown in (a) of FIG. 10 is displayed on the mobile phone. Figure 2 The voice input interface shown in (a) is displayed as Figure 2 The voice chat interface shown in (b) is worth noting that at this time, Figure 2 The area below the voice chat interface shown in (b) displays the voice input area 106.

[0089] Among them, the voice input area 106 displays a drawn / synthesized voice animation 1061, a "cancel send" button 1062, a "voice to text" button 1063, a voice recording area 1064 and a prompt message "release to send".

[0090] The user can long press any position in the voice recording area 1064 to trigger the voice input / recording function, and the voice animation 1061 is dynamically displayed. When the user releases the finger touching the voice recording area 1064, the voice recording ends, and The input / recorded voice is sent to the chat object 101. Figure 2 The voice input interface shown in (c) The input / recorded 5-second voice is successfully sent to the chat partner 101. It is worth noting that at this time, Figure 2 The area below the voice input interface shown in (c) is again displayed as a keyboard input icon 104 and a voice input box 105, and the voice input box 105 includes a "press and speak" button 1051. The user can long press the "press and speak" button 1051 again to implement voice input / recording.

[0091] In another possible implementation, when the user long presses the voice recording area 1064, if the user slides the finger toward the "cancel send" button 1062, the voice recording is terminated and the The input / recorded voice will not be sent to the chat partner 101.

[0092] For easier understanding, see Figure 3 , Figure 3 The present invention is a schematic diagram of another voice chat operation shown as an exemplary embodiment of the present application.

[0093] like Figure 3 As shown, when the user long presses the voice recording area 1064, the finger slides toward the "Cancel Send" button 1062, and a drawn / synthesized voice animation 107 and a prompt message "Release to Cancel" are displayed above the "Cancel Send" button 1062. When the user slides the finger toward the "Cancel Send" button 1062 and releases the finger touching the "Cancel Send" button 1062, the voice recording ends, the voice animation 107 disappears, and The input / recorded voice will not be sent to the chat partner 101.

[0094] It is worth mentioning that Figure 2 The voice effect 1061 shown in (b) and Figure 3 The voice animation 107 shown is different. Figure 2 The animation area corresponding to the voice animation 1061 shown in (b) is Figure 3 The animation area corresponding to the voice animation 107 shown is large.

[0095] In another possible implementation, when the user long presses the voice recording area 1064, if the user slides the finger toward the "voice to text" button 1063, the voice recording is terminated, and at the same time Convert input / recorded speech to text.

[0096] For easier understanding, see Figure 4 , Figure 4 The present invention is a schematic diagram of another voice chat operation shown as an exemplary embodiment of the present application.

[0097] like Figure 4As shown in (a), when the user long presses the voice recording area 1064, the finger slides toward the "voice to text" button 1063, and the drawn / synthesized text effect 108 is displayed in the area where the voice effect 1061 was originally displayed. When the user slides the finger toward the "voice to text" button 1063 and releases the finger touching the "voice to text" button 1063, The input / recorded voice is converted into text and displayed in the text animation 108 .

[0098] like Figure 4 As shown in (b), the text converted from the input / recorded speech is displayed in the text effect 108. At the same time, the area below the text effect 108 displays an "OK" button 109, a "Cancel" button, and a "Send Original Voice" button.

[0099] It should be understood that if the user clicks the "OK" button 109, The converted text is sent to the chat partner 101. If the user clicks the "Cancel" button, Cancel sending, that is The converted text will not be sent to the chat partner 101. If the user clicks the "Send Original Voice" button, The input / recorded voice will still be sent to the chat partner 101.

[0100] From the above-mentioned application scenarios, it can be seen that during the voice chat process, the animation will be drawn / synthesized when the voice is input / recorded. The animation can include Figure 2 The voice animation shown in (b) 1061, Figure 3 The voice animation 107 shown, and Figure 4 The text animation 108 shown in (b) is also the source of most of the power consumption during the entire voice chat. In other words, during the voice chat, the power consumption of the electronic device system due to recording is actually very small, and most of the power consumption comes from the animation drawing / synthesis during voice input / recording.

[0101] The reason is that most of the screens of the electronic devices (such as mobile phones) we currently use support multiple refresh rate settings (for example, the current settings are 30Hz, 60Hz, 90Hz, 120Hz, 144Hz, etc.), which means that the screens of electronic devices (such as mobile phones) can adjust the refresh rate to different settings according to different scenarios. In order to improve the smoothness of electronic devices (such as mobile phones) and enhance the user experience, the Touch Down event of TP is usually bound to the frequency increase of the central processing unit (CPU) and the screen refresh rate increase. For example, in When you long-press the "Press and Hold to Speak" button for voice input / recording, the CPU frequency will generally increase from 1.5GHz to 2.1GHz, and / or the screen refresh rate will increase from 60Hz to 120Hz.

[0102] It can be understood that in some application scenarios (such as voice input scenarios), when the screen of an electronic device (such as a mobile phone) detects a Touch Down event, it will perform operations such as increasing the CPU frequency and screen refresh rate. This operation will increase the power consumption of the SoC and screen of the electronic device (such as a mobile phone).

[0103] However, in some application scenarios (such as voice input scenarios), since the animations drawn / synthesized during voice input / recording are simple, the demand for resources such as CPU and SoC is not large, and users do not pay attention to the animation frame rate and smoothness of the screen display content, even if the screen refresh rate is reduced to 30Hz or maintained at 60Hz in this application scenario, it will have no effect on the animations drawn / synthesized. This results in a waste of power consumption when increasing the CPU frequency and / or the screen refresh rate in this application scenario. Therefore, it is very necessary to reduce the power consumption in these application scenarios (such as voice input scenarios).

[0104] In the related art, the voice input scene is usually identified first, and then the power consumption in the voice input scene is reduced. Therefore, how to accurately identify the voice input scene is very important. However, in the related art, whether the current scene is a voice input scene is usually determined by layout information or Activity information.

[0105] Regarding the implementation method of judging whether the current scene is a voice input scene through layout information, on the one hand, the voice input interfaces of different IM applications may be different. When the voice input interfaces are different, it is not possible to judge whether the current scene is a voice input scene in a timely manner through unified layout information, resulting in inaccurate recognition of the voice input scene. On the other hand, for new IM applications, a preliminary test must be conducted first, and then the corresponding layout information is configured. The whole process is labor-intensive, information-intensive, inconvenient to maintain, and prone to errors, which ultimately leads to inaccurate recognition of the voice input scene.

[0106] For the implementation method of determining whether the current scene is a voice input scene by using the activity information, since it is necessary to record various different activity information, it is easy to make mistakes when there is too much activity information, which leads to misrecognition results. For example, the voice input scene is not recognized, or a scene that is not a voice input scene is recognized as a voice input scene.

[0107] It can be seen that the voice input scenario cannot be accurately identified through either layout information or Activity information, which also makes it impossible to accurately reduce the power consumption in the voice input scenario.

[0108] In view of this, an embodiment of the present application provides a scene processing method, which determines that the current scene is a voice input scene when a touch start event is detected, a recording start event is detected within a preset time interval, and a first application and a second application are detected to be consistent; in the voice input scenario, the power consumption parameter of the electronic device is reduced, or the power consumption parameter is increased to a first value, the first value is less than the second value, and the second value is the power consumption parameter increased to which the electronic device is when a touch start event is detected.

[0109] Since the logic of generating a voice input scene is that a touch start event occurs first and then a recording start event occurs, and the time interval between the touch start event and the recording start event is within a preset time interval, and the application in which the touch start event occurs is consistent with the application in which the recording start event occurs. The scene processing method provided in the present application does not rely on layout information and Activity information when identifying a voice input scene, but identifies the voice input scene according to the logic of generating a voice input scene, thereby accurately identifying the voice input scene.

[0110] Compared with the related art in which power consumption parameters are increased when a touch start event is detected, the scene processing method provided in the present application reduces the power consumption parameters of the electronic device in the voice input scene, or increases the power consumption parameters to a first value, thereby effectively reducing the power consumption of the electronic device in the voice input scene. While not affecting the user experience, it reduces the loss of various components of the electronic device and improves the battery life and life of the electronic device.

[0111] And because there are many IM applications that support voice chat functions, it is difficult to adapt the voice input scenarios of these IM applications one by one through layout information or Activity information in the related technology, and many IM applications will not develop corresponding Activities for the voice input scenarios, resulting in the inability to cover the voice input scenarios of all IM applications through layout information or Activity information, and it is also impossible to accurately identify the voice input scenarios of each IM application through layout information or Activity information. However, the scenario processing method provided in the embodiment of the present application can cover all IM applications, accurately identify the voice input scenarios of all IM applications, and has wider applicability.

[0112] The hardware structure of the electronic device involved in the embodiments of the present application is briefly introduced below with reference to the accompanying drawings.

[0113] In some embodiments of the present application, the electronic device may be a mobile phone, a tablet computer, a wearable device, a television, a vehicle-mounted device, an augmented reality (AR) / virtual reality (VR) device, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), etc., or may be other devices or apparatuses capable of performing scene recognition. The embodiments of the present application do not impose any restrictions on the specific type of the electronic device.

[0114] Please refer to Figure 5 , Figure 5 The figure is a schematic diagram of the hardware structure of an electronic device according to an exemplary embodiment of the present application.

[0115] like Figure 5 As shown, the electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0116] It is to be understood that the structure shown in the embodiment of the present application does not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include Figure 5 More or fewer components than those shown, or the electronic device 100 may include Figure 5 Combinations of some of the components shown, or the electronic device 100 may include Figure 5 Subassemblies of some of the components shown. Figure 5The components shown may be implemented in hardware, software, or a combination of software and hardware.

[0117] The processor 110 may include one or more processing units, for example, the processor 110 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0118] The controller may be the nerve center and command center of the electronic device 100. The controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

[0119] The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may store instructions or data that the processor 110 has just used or cyclically used. If the processor 110 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0120] In an embodiment of the present application, the processor 110 may perform the steps of determining that the current scene is a voice input scene when a touch start event is detected, a recording start event is detected within a preset time interval, and the first application and the second application are detected to be consistent; in the voice input scene, reducing the power consumption parameter of the electronic device, or increasing the power consumption parameter to a first value. For example, the processor 110 may run the software code of the scene processing method provided in the embodiment of the present application, thereby identifying the voice input scene and reducing the power consumption of the electronic device in the voice input scene.

[0121] In some embodiments, the processor 110 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI) interface, a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0122] It is understandable that the interface connection relationship between the modules shown in this embodiment is only a schematic illustration and does not constitute a structural limitation on the electronic device 100. In other embodiments, the electronic device 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

[0123] The charging management module 140 is used to receive charging input from a charger. While the charging management module 140 is charging the battery 142 , it can also supply power to the electronic device 100 through the power management module 141 .

[0124] The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, and supplies power to the processor 110, the internal memory 121, the external memory, the display screen 194, the camera 193, and the wireless communication module 160. In some other embodiments, the power management module 141 may also be provided in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may also be provided in the same device.

[0125] Figure 5 The connection relationship between the modules shown is only a schematic illustration and does not constitute a limitation on the connection relationship between the modules of the electronic device 100. Optionally, the modules of the electronic device 100 may also adopt a combination of multiple connection modes in the above embodiments.

[0126] The wireless communication function of the electronic device 100 can be implemented through components such as the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor, and the baseband processor.

[0127] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of antennas. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0128] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 2G / 5G, etc., applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0129] The modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be sent into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to a speaker 170A, a receiver 170B, etc.), or displays an image or video through a display screen 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

[0130] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the electronic device 100. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the frequency of the electromagnetic wave signal and performs filtering, and sends the processed signal to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, modulate the frequency of it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0131] In some embodiments, the antenna 1 of the electronic device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the electronic device 100 can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology, etc. GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), Beidou navigation satellite system (BDS), quasi-zenith satellite system (QZSS) and / or satellite based augmentation system (SBAS). It is understood that in the embodiments of the present application, the hardware module in the positioning or navigation system may be referred to as a positioning sensor.

[0132] The electronic device 100 can realize the display function through the GPU, the display screen 194 and the application processor. The GPU is a microprocessor for image processing, which connects the display screen 194 and the application processor. The GPU can also be used to perform mathematical and posture calculations for graphics rendering, etc. The processor 110 may include one or more GPUs, which can generate or change display information by executing program instructions.

[0133] The display screen 194 can be used to display images or videos, and can also display a series of graphical user interfaces (GUIs), which are the main screens of the electronic device 100. Generally speaking, the size of the display screen 194 of the electronic device 100 is fixed, and only limited controls can be displayed on the display screen 194 of the electronic device 100. A control is a GUI element, which is a software component included in an application program, and controls all data processed by the application program and interactive operations on the data. Users can interact with the control through direct manipulation to read or edit relevant information of the application program. Generally speaking, a control can include visual interface elements such as icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, etc.

[0134] In the embodiment of the present application, the display screen 194 can be used to display various interfaces involved in the voice chat process.

[0135] The display screen 194 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include 1 or N display screens 194, where N may be a positive integer greater than 1.

[0136] The display screen 194 in the embodiment of the present application may be a touch screen. A touch sensor 180K may be integrated in the display screen 194. The touch sensor 180K may also be referred to as a "touch panel". In other words, the display screen 194 may include a display panel and a touch panel, and the touch sensor 180K and the display screen 194 form a touch screen, also known as a "touch screen". The touch sensor 180K is used to detect touch operations acting on or near it. After the touch operation detected by the touch sensor 180K, it can be passed to the upper layer by the driver of the kernel layer (such as the TP driver) to determine the type of touch event. Visual output related to the touch operation can be provided by the display screen 194. In other embodiments, the touch sensor 180K may also be arranged on the surface of the electronic device 100, which is different from the position of the display screen 194.

[0137] In an embodiment of the present application, the touch sensor 180K detects a user's touch operation. For example, when a user touches the display screen 194, the touch sensor 180K detects the user's touch operation, which is passed to the upper layer by the driver of the kernel layer (such as the TP driver) to determine the type of touch event, such as a Touch Down event. For another example, when the user no longer touches the display screen 194, the touch sensor 180K detects that the user has lifted his finger, which is passed to the upper layer by the driver of the kernel layer (such as the TP driver) to determine the type of touch event, such as a Touch Up event. In response to the user's touch operation, the processor 110 provides visual output related to the touch operation through the display screen 194, such as the display screen 194 displays a personal chat interface, a voice input interface, a voice chat interface, various drawn / synthesized animations, etc.

[0138] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function, such as storing music, video and other files in the external memory card.

[0139] The internal memory 121 can be used to store computer executable program codes, and the executable program codes include instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by running the instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an APP required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the electronic device 100 (such as audio data, a phone book, etc.), etc.

[0140] In addition, the internal memory 121 may include a high-speed random access memory; the internal memory 121 may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (Universal Flash Storage, UFS), etc.

[0141] The pressure sensor 180A is used to sense the pressure signal and can convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A can be set on the display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. A capacitive pressure sensor can be a parallel plate including at least two conductive materials. When a force acts on the pressure sensor 180A, the capacitance between the electrodes changes. The electronic device 100 determines the intensity of the pressure based on the change in capacitance. When a touch operation acts on the display screen 194, the electronic device 100 detects the intensity of the touch operation based on the pressure sensor 180A. The electronic device 100 can also calculate the touch position based on the detection signal of the pressure sensor 180A. In some embodiments, acting on different touch positions but different touch durations can correspond to different operation instructions.

[0142] The acceleration sensor 180E can detect the magnitude of the acceleration of the electronic device 100 in various directions (generally the x-axis, y-axis and z-axis). When the electronic device 100 is stationary, the magnitude and direction of gravity can be detected. The acceleration sensor 180E can also be used to identify the posture of the electronic device 100 as an input parameter for applications such as horizontal and vertical screen switching and pedometers.

[0143] The ambient light sensor 180L is used to sense the ambient light brightness. The electronic device 100 can adaptively adjust the brightness of the display screen 194 according to the perceived ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180L can also cooperate with the proximity light sensor 180G to detect whether the electronic device 100 is in a pocket to prevent accidental touches.

[0144] The fingerprint sensor 180H is used to collect fingerprints. The electronic device 100 can use the collected fingerprint characteristics to realize functions such as unlocking, accessing application locks, taking photos, and answering calls.

[0145] The key 190 includes a power key, a volume key, etc. The key 190 may be a mechanical key or a touch key. The electronic device 100 may receive key input and generate key signal input related to user settings and function control of the electronic device 100.

[0146] Motor 191 can generate vibration prompts. Motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback.

[0147] The indicator 192 may be an indicator light, which may be used to indicate the charging status, power change, message, missed call, notification, etc. The SIM card interface 195 is used to connect the SIM card. The SIM card may be connected to or disconnected from the electronic device 100 by inserting the SIM card interface 195 or pulling the SIM card interface 195 out. The electronic device 100 may support 1 or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 may support Nano SIM card, Micro SIM card, SIM card, etc.

[0148] In addition, various types of operating systems are running on the above components, such as Android system, IOS operating system, Symbian operating system, BlackBerry operating system, Linux operating system, Windows operating system, etc. This is only an exemplary description and is not limited to this. Different applications can be installed and run on these operating systems, such as any application that supports voice chat function.

[0149] The scene processing method provided in the embodiment of the present application can be implemented in the electronic device 100 having the above-mentioned hardware structure.

[0150] The above briefly introduces the structure of the electronic device 100 involved in the embodiment of the present application. The following briefly introduces the software structure involved in the embodiment of the present application. Figure 6 , Figure 6 The software structure block diagram of the electronic device shown in an exemplary embodiment of the present application. The layered architecture divides the software into several layers, each layer has a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the electronic device 100 is an Android system as an example for explanation. The Android system is divided into four layers, from top to bottom, respectively, the application layer, the application framework layer, the Android runtime (Android runtime) and the system library, and the kernel layer.

[0151] The application layer can include a series of application packages. Figure 6 As shown, the application package may include camera, calendar, map, wireless local area network (WLAN), music, short message, various IM applications (such as etc.), scene recognition services, etc.

[0152] Among them, IM application is an application that uses instant messaging technology to achieve online chatting and communication.

[0153] The scene recognition service is an application that resides in the application layer and is usually invisible to users.

[0154] The scene recognition service is used to identify the voice input scene and determine a method for reducing power consumption. The method for reducing power consumption may be to reduce a power consumption parameter of the electronic device, or to increase the power consumption parameter to a first value, the first value being less than a second value, the second value being the power consumption parameter to which the electronic device increases when a touch start event is detected.

[0155] Optionally, in a possible implementation, the scene recognition service may also be an integrated unit, module, chip, etc., for identifying voice input scenes and determining a method for reducing power consumption.

[0156] The application framework layer provides an application programming interface (API) and a programming framework for the applications in the application layer. The application framework layer includes some predefined functions.

[0157] As an example of the present application, the application framework layer may include an input dispatch thread (InputDispatcher) module, an audio recording service (Audio Record) module, a window manager (WindowManager) and a power consumption parameter adjustment module.

[0158] In the embodiment of the present application, the Input Dispatcher module can process all TP-related events.

[0159] A trigger function is pre-added in the Input Dispatcher module. When a Touch Down event is detected, the Input Dispatcher module is triggered to pass the Touch Down event to the IM application, which then receives the Touch Down event. At the same time, the Input Dispatcher module also passes the Touch Down event to the scene recognition service, which receives the Touch Down event and records the identification information, event type, touch start / start time, touch position, and other information of the Touch Down event.

[0160] When a Touch Up event is detected, the Input Dispatcher module is triggered to pass the Touch Up event to the IM application, which receives the Touch Up event. At the same time, the Input Dispatcher module also passes the Touch Up event to the scene recognition service, which receives the Touch Up event and records the identification information, event type, touch end time, finger leaving position, and other information of the Touch Up event.

[0161] In an embodiment of the present application, the Audio Record module can process all audio-related events.

[0162] The Audio Record module may include an Audio Record.start interface and an Audio Record.stop interface.

[0163] The IM application calls the Audio Record.start interface in the system, after which the Audio Record module starts voice recording and generates a recording start event.

[0164] A trigger function is pre-added in the Audio Record module. When the IM application calls the Audio Record.start interface, the Audio Record module is triggered to notify the scene recognition service. The scene recognition service records information about the recording start event, such as the recording start time, the second UID of the second application that calls the Audio Record.start interface, and the second application package name.

[0165] When the IM application calls the Audio Record.stop interface, the Audio Record module is triggered to notify the scene recognition service. The scene recognition service records the information of the Audio Record stop event, such as the recording end time, recording duration, the second UID of the second application that calls the Audio Record.stop interface, and the second application package name.

[0166] The window manager (WindowManager) is used to send the UID and application package name of the window of the focus application to the scene recognition service.

[0167] The power consumption parameter adjustment module is used to adjust the power consumption parameters of the electronic device, for example, to reduce the power consumption parameters of the electronic device, or to increase the power consumption parameters to a first value.

[0168] It is worth noting that the scene recognition service only determines a method for reducing power consumption, and the execution of the method for reducing power consumption is achieved by adjusting the power consumption parameter module.

[0169] Optionally, in a possible implementation manner, the power consumption parameter adjustment module may include a system service (SurfaceFlinger) module.

[0170] Among them, SurfaceFlinger is a local process of Android, which is responsible for synthesizing layers, and the layers are superimposed to form the interface we see. In the embodiment of the present application, the SurfaceFlinger module can be used to adjust the screen refresh rate.

[0171] Optionally, the application framework layer may also include a content provider, a telephony manager, a resource manager, a notification manager, and the like.

[0172] Content providers are used to store and retrieve data and make it accessible to applications. These data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0173] The view system may include visual controls, such as controls for displaying text, controls for displaying images, etc. The view system may be used to construct the display interface of an application, and the display interface may be composed of one or more views, for example, a view for displaying a text message notification icon, a view for displaying text, and a view for displaying images.

[0174] The phone manager is used to provide communication functions for the electronic device 200, such as management of call status (including answering, hanging up, etc.).

[0175] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, etc.

[0176] The notification manager enables applications to display notification information in the status bar. It can be used to convey notification-type messages and can disappear automatically after a short stay without user interaction. For example, the notification manager is used to notify the completion of downloads, message reminders, etc. The notification manager can also be a notification that appears in the system top status bar in the form of an icon or scroll bar text, such as notifications from applications running in the background. The notification manager can also be a notification that appears on the screen in the form of a dialog window, such as a text message prompt in the status bar, a beep, an electronic device vibrates, an indicator light flashes, etc.

[0177] Android Runtime includes core libraries and virtual machines. Android runtime is responsible for scheduling and management of the Android system. The core library consists of two parts: one is the function that the Java language needs to call, and the other is the Android core library. The application layer and the application framework layer run in the virtual machine. The virtual machine executes the Java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform object life cycle management, stack management, thread management, security and exception management, and garbage collection.

[0178] The system library can include multiple functional modules, such as: surface manager, media library, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.

[0179] The surface manager is used to manage the display subsystem and provide the fusion of 2D and 3D layers for multiple applications.

[0180] The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0181] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing, etc. The 2D graphics engine is a drawing engine for 2D drawing.

[0182] The kernel layer is the layer between hardware and software. The kernel layer may include a touch panel driver (TouchPanelDriver), which is used to collect touch start events generated after a user (such as a user's finger or a touch object such as a stylus) touches the touch panel of an electronic device. Afterwards, the touch panel driver uploads the collected touch start events to the Input Dispatcher.

[0183] The kernel layer may also include a display driver, which may be used to display different display windows, such as an IM application window.

[0184] The kernel layer can also include camera drivers, audio drivers, sensor drivers, etc.

[0185] The above briefly introduces the software structure involved in the embodiments of the present application. Figure 5 and Figure 6 Taking the electronic device with the shown structure as an example, the scene processing method provided in the embodiment of the present application is specifically described in combination with the accompanying drawings and application scenarios.

[0186] See also Figure 7 , Figure 7 A schematic diagram of a scene processing method provided in an embodiment of the present application. The method includes:

[0187] S101: When a touch start event is detected, a recording start event is detected within a preset time interval, and a first application and a second application are detected to be consistent, determining that the current scene is a voice input scene.

[0188] The first application is the application corresponding to the touch start event. It can be understood that the first application is the application currently receiving the long press operation, click / touch operation by the user, or it can be understood that the application belongs to the area / position where the user currently performs the long press operation, click / touch operation. Alternatively, it can also be understood that the first application is the application that generates the touch start event.

[0189] The second application is the application corresponding to the recording start event. It can be understood that the second application is the application that calls the recording start interface, or the second application is the application that generates the recording start event.

[0190] It should be understood that usually the first application and the second application are specifically IM applications that support voice chat functions.

[0191] In one example, when a touch start event is detected but a recording start event is not detected, it is determined that the current scene is a non-voice input scene.

[0192] In another example, when a touch start event is detected and a recording start event is not detected within a preset time interval, it is determined that the current scene is a non-voice input scene.

[0193] In yet another example, when a recording start event is detected and the recording start event is detected within a preset time interval, but when it is detected that the first application and the second application are inconsistent, it is determined that the current scene is a non-voice input scene.

[0194] In another example, when a recording start event is detected first and a touch start event is detected later, even if the first application and the second application are the same, the current scene is determined to be a non-voice input scene.

[0195] In another example, when a touch start event is detected, and a recording start event is detected within a preset time interval, and when it is detected that the first application corresponding to the touch start event and the second application corresponding to the recording start event are consistent, the current scene is determined to be a voice input scene.

[0196] In this implementation, when a touch start event is detected, a recording start event is detected within a preset time interval, and the first application and the second application are detected to be consistent, the current scene is determined to be a voice input scene; in the voice input scene, the power consumption parameter of the electronic device is reduced, or the power consumption parameter is increased to a first value, the first value is less than the second value, and the second value is the power consumption parameter to which the electronic device is increased when a touch start event is detected.

[0197] Since the logic of generating a voice input scene is that a touch start event occurs first and then a recording start event occurs, and the time interval between the touch start event and the recording start event is within a preset time interval, and the application in which the touch start event occurs is consistent with the application in which the recording start event occurs. The scene processing method provided in the present application does not rely on layout information and Activity information when identifying a voice input scene, but identifies the voice input scene according to the logic of generating a voice input scene, thereby accurately identifying the voice input scene.

[0198] And because there are many IM applications that support voice chat functions, it is difficult to adapt the voice input scenarios of these IM applications one by one through layout information or Activity information in the related technology, and many IM applications will not develop corresponding Activities for the voice input scenarios, resulting in the inability to cover the voice input scenarios of all IM applications through layout information or Activity information, and it is also impossible to accurately identify the voice input scenarios of each IM application through layout information or Activity information. However, the scenario processing method provided in the embodiment of the present application can cover all IM applications, accurately identify the voice input scenarios of all IM applications, and has wider applicability.

[0199] S102: In a voice input scenario, reducing a power consumption parameter of the electronic device, or increasing the power consumption parameter to a first value.

[0200] The first value is smaller than the second value, and the second value is a power consumption parameter increased when the electronic device detects a touch start event.

[0201] The power consumption parameters may include any one or any combination of CPU frequency, screen refresh rate, screen brightness, double data rate (DDR) frequency, touch panel (TP) reporting rate, application drawing frame rate and system synthesis frame rate.

[0202] Among them, DDR frequency refers to the frequency of double data transmission. TP reporting rate refers to the rate at which TP reports the touch screen position to the CPU. Application drawing frame rate refers to the frequency at which the IM application draws bitmap images in frames and appears continuously on the display screen.

[0203] The content displayed on the screen of the electronic device is synthesized into a frame by the Android system's SurfaceFlinger, which combines the information that needs to be displayed by all processes in the current system into one frame, and then submits it to the screen for display. The system synthesis frame rate refers to the number of frames submitted to the screen by SurfaceFlinger in one second.

[0204] For example, in the related art, when the electronic device detects a touch start event, it increases the current power consumption parameter of the electronic device to a second value. Optionally, in a possible implementation, the scene processing method provided in the embodiment of the present application reduces the power consumption parameter of the electronic device when determining that the current scene is a voice input scene.

[0205] When the power consumption parameter includes any one of the CPU frequency, screen refresh rate, screen brightness, DDR frequency, TP reporting rate, application drawing frame rate and system synthesis frame rate, reduce any one of the power consumption parameters.

[0206] When the power consumption parameters include any combination of CPU frequency, screen refresh rate, screen brightness, DDR frequency, TP reporting rate, application drawing frame rate and system synthesis frame rate, each power consumption parameter in the arbitrary combination is reduced.

[0207] In this implementation, compared with the related art in which power consumption parameters are increased when a touch start event is detected, the scene processing method provided in the present application reduces the power consumption parameters of electronic devices in voice input scenarios, effectively reducing the power consumption of electronic devices in voice input scenarios, while not affecting the user experience, reducing the loss of various components of electronic devices, and improving the battery life and life of electronic devices.

[0208] Optionally, in another possible implementation, the scene processing method provided in the embodiment of the present application increases the power consumption parameter to a first value when determining that the current scene is a voice input scene, and the first value is less than the second value.

[0209] When the power consumption parameter includes any one of CPU frequency, screen refresh rate, screen brightness, DDR frequency, TP reporting rate, application drawing frame rate and system synthesis frame rate, the first value includes a value, and the any one of the power consumption parameters is increased to the first value.

[0210] When the power consumption parameter includes any combination of CPU frequency, screen refresh rate, screen brightness, DDR frequency, TP reporting rate, application drawing frame rate, and system synthesis frame rate, the first value includes the value corresponding to each power consumption parameter in the any combination. Each power consumption parameter in the any combination is increased to its corresponding value.

[0211] In this implementation, compared with the related art that increases the power consumption parameters when a touch start event is detected, the scene processing method provided by this application improves the power consumption parameters of the electronic device in the voice input scenario, but the increase is small, that is, the first value corresponding to the increased power consumption parameter is not as large as the second value corresponding to the increased power consumption parameter in the related art. Therefore, compared with the related art, the scene processing method provided by this application effectively reduces the power consumption of the electronic device in the voice input scenario, reduces the loss of each component of the electronic device without affecting the user experience, and improves the battery life and life of the electronic device.

[0212] In a possible implementation, in the related art, when the electronic device detects a touch start event, it adjusts the power consumption parameter of the electronic device within a first value range. It is worth noting that in the related art, the adjusted power consumption parameter is greater than the power consumption parameter before adjustment.

[0213] The scenario processing method provided by the present application reduces the range of the power consumption parameter of the electronic device to a second numerical range in the voice input scenario, and the maximum value of the second numerical range is less than the maximum value of the first numerical range. It is worth noting that in the scenario processing method provided by the present application, the adjusted power consumption parameter may be greater than the power consumption parameter before adjustment, or may be equal to the power consumption parameter before adjustment, or may be less than the power consumption parameter before adjustment, but no matter how it is adjusted, it is less than the adjusted power consumption parameter in the related art.

[0214] Take the power consumption parameter as CPU frequency as an example. For example, the first value range is 1.8 GHz to 2.1 GHz, and the second value range can be 1.5 GHz to 1.7 GHz, 1.5 GHz to 1.8 GHz, 1.5 GHz to 1.9 GHz, 1.8 GHz to 2.0 GHz, 1.5 GHz to 2.0 GHz, etc. This is only an exemplary description and is not limited to this.

[0215] In this implementation, compared with the related art of increasing power consumption parameters when a touch start event is detected, the scene processing method provided in the present application effectively reduces the power consumption of electronic devices in voice input scenarios, reduces the loss of various components of electronic devices without affecting the user experience, and improves the battery life and life of electronic devices.

[0216] The above is an overview of the scene processing method provided by this application. The following is a detailed description of the scene processing method provided by this application with a complete process. Figure 8 , Figure 8 A flowchart of another scene processing method provided in an embodiment of the present application. The method includes:

[0217] S201: Detect a touch start event.

[0218] In the implementation manner of the present application, a touch start event is also called a Touch Down event, and the Touch Down event is taken as an example for description below.

[0219] The screen / touch screen of an electronic device (such as a mobile phone) is composed of a touch sensor and a display screen, wherein the touch sensor is used to detect a touch operation / touch operation acting on or near it.

[0220] For example, when a user touches / clicks the screen of an electronic device (such as a mobile phone), the touch sensor detects the user's touch / click operation and generates a corresponding Touch Down event. It is worth noting that each time a user touches / clicks the screen of an electronic device (such as a mobile phone), the touch sensor detects the user's touch / click operation and generates a corresponding Touch Down event, and assigns different identification information to each Touch Down event to distinguish different Touch Down events.

[0221] The Touch Down event may carry information such as event type, touch start / start time, touch position, etc. The event type may include a tap type, a long press type, etc.

[0222] In the embodiment of the present application, the IM application is used as For example, a user opens an IM application and enters a personal chat interface. Figure 1 The user clicks the voice input icon 102 in the personal chat interface. At this time, a corresponding Touch Down event is generated based on this click operation, and the mobile phone display interface changes from Figure 1 The personal chat interface shown in (b) is displayed as Figure 1 The voice input interface shown in (c) is shown in the figure. Figure 1 As shown in (b), the voice input icon 102 changes to a keyboard input icon 104, and the text input box 103 changes to a voice input box 105, which also includes a "press and speak" button 1051. The user long presses the "press and speak" button 1051, and a corresponding Touch Down event is generated based on this long press operation.

[0223] Each Touch Down event generated is passed to TP, and TP receives these Touch Down events.

[0224] It is worth noting that in order to improve the fluency of electronic devices and bring better experience to users, usually after detecting a Touch Down event, the power consumption parameters of the electronic device will be increased. However, in the scene processing method provided by this application, when the current scene is subsequently determined to be a voice input scene, the power consumption of the electronic device will be reduced. Therefore, even compared with related technologies, the power consumption of electronic devices in voice input scenarios is effectively reduced, and while not affecting the user experience, the loss of various components of the electronic device is reduced, and the battery life and life of the electronic device are improved.

[0225] S202: Transmit a touch start event.

[0226] After receiving the Touch Down event, TP passes the Touch Down event to the Input Dispatcher module. Since the trigger function is pre-added in the Input Dispatcher module, when the Touch Down event is detected, the Input Dispatcher module is triggered to pass the Touch Down event to the IM application, and the IM application receives the Touch Down event.

[0227] At the same time, the Input Dispatcher module will also pass the Touch Down event to the scene recognition service. The scene recognition service receives the Touch Down event and records the identification information, event type, touch start / start time, touch position and other information of the Touch Down event.

[0228] It is worth noting that, in order to facilitate the subsequent calculation of the time difference, in this implementation, the touch start / start time of the Touch Down event is recorded as the first time.

[0229] Among them, the scene recognition service is an application resident in the application layer and is usually invisible to users.

[0230] Optionally, in a possible implementation, the scene recognition service can also obtain TouchDown events from other modules, and record the identification information, event type, touch start / start time, touch position, etc. of the TouchDown event. For example, the electronic device may include a touch screen driver, and the TouchDown event is transmitted from the TP driver to the application framework layer, and then to the application layer. In other words, the TP driver, the application framework layer, and the application layer can all detect the TouchDown event, and the scene recognition service can obtain the TouchDown event from the TP driver, the application framework layer, or the application layer.

[0231] S203: The IM application calls the recording service module.

[0232] The recording service (Audio Record) module is a module in the application framework layer of the electronic device (such as a mobile phone) system. The Audio Record module may include an Audio Record.start interface.

[0233] Exemplarily, the IM application calls the Audio Record.start interface in the system, after which the Audio Record module starts voice recording, and the Audio Record module generates a recording start event.

[0234] Since a trigger function is pre-added in the Audio Record module, when the IM application calls the AudioRecord.start interface, the Audio Record module is triggered to notify the scene recognition service. The scene recognition service records the information of the recording start event, that is, the recording start time, the second UID of the second application that calls the Audio Record.start interface, and the second application package name.

[0235] It is worth noting that, in order to facilitate the subsequent calculation of the time difference, in this implementation, the recording start time of the recording start event is recorded as the second time.

[0236] Optionally, in one possible implementation, the scene recognition service can detect the AudioRecord event in other ways. For example, the electronic device may include a microphone driver, and the scene recognition service can also detect the Audio Record event through the microphone driver. Specifically, when it is detected that the output voltage of the microphone driver is within the voltage range corresponding to the recorded voice, it can be determined that the current electronic device (such as a mobile phone) is using the microphone to record voice, thereby determining that there is currently an AudioRecord event. The recording start time of the Audio Record event is obtained and recorded as the second time.

[0237] For another example, the scene recognition service can also detect the Audio Record event through the state of the Audio In lock. Since the Audio In lock in the standby state indicates that it is currently in the recording state, when it is detected that the Audio In lock is in the standby state, it is determined that there is currently an Audio Record event. The recording start time of the Audio Record event is obtained and recorded as the second time.

[0238] S204: Determine whether the caller of the recording service module is a focus application.

[0239] In the implementation of the present application, the focus application refers to the application that the user currently performs a long press operation, click / touch operation, and can also be understood as the application to which the area / position where the user currently performs a long press operation, click / touch operation belongs.

[0240] The scene recognition service determines whether the caller of the Audio Record module is the focus application, that is, the scene recognition service determines whether the application that calls the Audio Record.start interface is the focus application. In other words, the scene recognition service determines whether the first application that currently generates the Touch Down event is consistent with the second application that calls the Audio Record.start interface.

[0241] In one example, a user Long press the "Press and Speak" button to input / record voice, which generates a Touch Down event. The application corresponding to this Touch Down event is because To record audio, the Audio Record.start interface in the Audio Record module is called. The caller of the Audio Record module is In this application scenario, the first application that generates the Touch Down event is the same as the second application that calls the Audio Record.start interface, that is, the caller of the Audio Record module is the application that the user currently performs a long press operation on. This is consistent with the situation of the voice input scenario, but it only proves that the current scenario may be a voice input scenario, not necessarily a voice input scenario.

[0242] In another example, for example, a user sets up a split screen in an electronic device (such as a mobile phone) and uses While using the camera, the user Clicking the "Press and hold to speak" button generates a Touch Down event. The application corresponding to this TouchDown event is The detection found that the application calling the Audio Record module is a camera. In this application scenario, the first application that generates the Touch Down event is inconsistent with the second application that calls the Audio Record module. In other words, the caller of the Audio Record module is not the application that the user is currently clicking on, proving that the current scenario must not be a voice input scenario.

[0243] If you do not determine whether the first application that generates the Touch Down event is consistent with the second application that calls the Audio Record module, misrecognition may occur, that is, a scene that is not a voice input scene is mistakenly identified as a voice input scene. For example, a Touch Down event is generated on a split-screen application, and another split-screen application calls the AudioRecord module, misrecognizing the scene of the latter split-screen application as a voice input scene. Performing a power reduction operation in the case of such a misrecognition as a voice input scene will reduce the power consumption of at least two current split-screen applications of the electronic device (such as a mobile phone), seriously affecting the user experience. Therefore, it is very important to determine whether the caller of the Audio Record module is the focus application, that is, to determine whether the first application that currently generates the Touch Down event is consistent with the second application that calls the Audio Record.start interface, in order to accurately identify the voice input scene.

[0244] The specific method for determining whether the first application that currently generates the Touch Down event is consistent with the second application that calls the Audio Record.start interface is as follows:

[0245] Optionally, in a possible implementation, obtain a first unique identifier (UID) of the first application, and obtain a second UID of the second application that calls the Audio Record.start interface. Determine whether the first UID and the second UID are consistent. If the first UID and the second UID are consistent, then determine that the first application that currently generates the Touch Down event is consistent with the second application that calls the AudioRecord.start interface, that is, the current Touch Down event is a Touch Down event generated by the IM application, and the caller of the Audio Record module is the focus application. If the first UID and the second UID are inconsistent, then determine that the first application that currently generates the Touch Down event is inconsistent with the second application that calls the Audio Record.start interface, that is, the current Touch Down event is not a Touch Down event generated by the IM application, and the caller of the Audio Record module is not the focus application.

[0246] Optionally, in another possible implementation, obtain the first application package name of the first application, and obtain the second application package name of the second application that calls the Audio Record.start interface. Determine whether the first application package name and the second application package name are consistent. If the first application package name and the second application package name are consistent, then determine that the first application that currently generates the Touch Down event is consistent with the second application that calls the Audio Record.start interface, that is, the current Touch Down event is a Touch Down event generated by the IM application, and the caller of the Audio Record module is the focus application. If the first application package name and the second application package name are inconsistent, then determine that the first application that currently generates the Touch Down event is inconsistent with the second application that calls the AudioRecord.start interface, that is, the current Touch Down event is not a Touch Down event generated by the IM application, and the caller of the Audio Record module is not the focus application.

[0247] Optionally, in another possible implementation, the first UID and the first application package name of the first application are obtained, and the second UID and the second application package name of the second application that calls the Audio Record.start interface are obtained. It is determined whether the first UID and the second UID are consistent, and whether the first application package name and the second application package name are consistent. If the first UID and the second UID are consistent, and the first application package name and the second application package name are consistent, then it is determined that the first application that currently generates the Touch Down event is consistent with the second application that calls the Audio Record.start interface, that is, the current Touch Down event is a Touch Down event generated by the IM application, and the caller of the Audio Record module is the focus application. Otherwise, it is determined that the first application that currently generates the Touch Down event is inconsistent with the second application that calls the Audio Record.start interface, that is, the current TouchDown event is not a Touch Down event generated by the IM application, and the caller of the Audio Record module is not the focus application.

[0248] It is worth noting that when the result of executing step S204 is that the caller of the recording service module is not the focus application, step S205 is executed. When the result of executing step S204 is that the caller of the recording service module is the focus application, step S206 is executed. That is, step S205 and step S206 are parallel, and one is executed according to the actual situation, and step S206 is not executed after step S205.

[0249] S205: When it is determined that the caller of the recording service module is not the focus application, the increase of the power consumption parameter of the electronic device is not restricted.

[0250] Exemplarily, when it is determined that the caller of the Audio Record module is not the focus application, it is proved that the current scene must not be a voice input scene.

[0251] In a possible implementation, when it is determined that the caller of the recording service module is not the focus application, not restricting the increase of the power consumption parameters of the electronic device means that the current power consumption parameters of the electronic device are maintained without adjustment.

[0252] In another possible implementation, when it is determined that the caller of the recording service module is not the focus application, not limiting the increase in the power consumption parameters of the electronic device means increasing the power consumption parameters of the current electronic device. For example, in order to improve the fluency of electronic devices (such as mobile phones) and enhance user experience, when a Touch Down event is detected, any one or any combination of multiple power consumption parameters such as CPU frequency, screen refresh rate, screen brightness, DDR frequency, TP reporting rate, application drawing frame rate, system synthesis frame rate, etc. can be increased.

[0253] S206: When it is determined that the caller of the recording service module is the focus application, determine the sequence of the touch start event and the recording start event.

[0254] When the scene recognition service determines that the caller of the Audio Record module is the focus application, the scene recognition service continues to determine the order of the Touch Down event and the recording start event, or in other words, the scene recognition service determines the order of calling the AudioRecord.start interface and the Touch Down event.

[0255] Optionally, in a possible implementation, the Audio Record.start interface is called first, and then the Touch Down event occurs, that is, the Audio Record.start interface is called first, and the Touch Down event occurs later. In layman's terms, the voice recording is performed first, and then the long press operation occurs.

[0256] In this case, it proves that the current scene must not be a voice input scene. It may be that some applications used by the user (such as navigation applications) automatically start recording, and then the user performs a long press operation, and the recording is not started by the user operation. In this application scenario, in order to improve the fluency of electronic devices (such as mobile phones) and enhance the user experience, when a Touch Down event is detected, an operation to increase power consumption can be performed. Specifically, any one or any combination of multiple power consumption parameters such as CPU frequency, screen refresh rate, screen brightness, DDR frequency, TP reporting rate, application drawing frame rate, system synthesis frame rate, etc. can be increased.

[0257] Alternatively, in another possible implementation, the Touch Down event occurs first, and then the Audio Record.start interface is called, that is, the Touch Down event occurs first, and the Audio Record.start interface is called later. In layman's terms, the long press operation occurs first, and then the voice recording is performed.

[0258] In this case, the sequence of the recording start event and the Touch Down event conforms to the situation of the voice input scenario, but it can only prove that the current scenario may be a voice input scenario, not necessarily a voice input scenario, and further judgment is needed.

[0259] It is worth noting that step S206 may be performed first and then step S204, that is, the order of the touch start event and the recording start event is first determined, and when the order of the touch start event and the recording start event is that the touch start event occurs first and then the recording start event occurs, it is determined whether the caller of the recording service module is the focus application. When it is determined that the caller of the recording service module is the focus application, step S207 is executed.

[0260] If the touch start event and the recording start event occur in the order of recording start event first and then touch start event, the power consumption parameter of the electronic device is not limited to increase. If the caller of the recording service module is not the focus application, the power consumption parameter of the electronic device is not limited to increase.

[0261] S207: Determine whether the time interval between the touch start event and the recording start event is less than a preset time interval.

[0262] When the Touch Down event and the recording start event occur in a sequence of the Touch Down event first and the recording start event later, the scene recognition service determines whether the time interval between the Touch Down event and the recording start event is less than a preset time interval.

[0263] The preset time interval can be set and adjusted by the user according to actual conditions. For example, in the embodiment of the present application, the preset time interval can be 200 milliseconds (ms), 300 milliseconds (ms), etc., and there is no limitation on this.

[0264] Exemplarily, when a Touch Down event is detected, the scene recognition service records the touch start / start time of the Touch Down event, i.e., the first time. When a recording start event is detected, the scene recognition service records the recording start time of the recording start event, i.e., the second time. The difference between the second time and the first time is calculated, and the difference is compared with the preset time interval.

[0265] Optionally, in a possible implementation, the difference is greater than or equal to a preset time interval. In layman's terms, after a Touch Down event is generated, a long time (greater than or equal to the preset time interval) passes before a recording start event occurs. For example, after a Touch Down event is generated, a recording start event passes half a minute before a recording start event occurs. In this case, it is proven that the current scene is definitely not a voice input scene.

[0266] In this application scenario, in order to improve the smoothness of electronic devices (such as mobile phones) and enhance user experience, when a Touch Down event is detected, power consumption can be increased. Specifically, any one or any combination of multiple power consumption parameters such as CPU frequency, screen refresh rate, screen brightness, DDR frequency, TP reporting rate, application drawing frame rate, system synthesis frame rate, etc. can be increased.

[0267] Optionally, in another possible implementation, the difference is less than a preset time interval. In layman's terms, after a Touch Down event is generated, a recording start event occurs soon (less than the preset time interval), which is consistent with the situation of a voice input scenario, proving that the current scenario is a voice input scenario.

[0268] That is to say, when the current scene meets the three conditions, the current scene is determined to be a voice input scene. The three conditions are that the first application that generates the Touch Down event is consistent with the second application that calls the Audio Record.start interface, the Touch Down event and the recording start event are in the order of Touch Down event first and recording start event later, and the difference between the second time of the recording start event and the first time of the Touch Down event is less than the preset time interval. The implementation of this application does not limit the order of judging these three conditions.

[0269] S208: In a voice input scenario, reduce a power consumption parameter of the electronic device, or increase the power consumption parameter to a first value.

[0270] Exemplarily, in the voice input scenario, the scene recognition service determines a method for reducing power consumption, and sends the method for reducing power consumption to the power consumption parameter adjustment module, which is then specifically executed by the power consumption parameter adjustment module.

[0271] Among them, the method of reducing power consumption can be to reduce the power consumption parameter of the electronic device, or to increase the power consumption parameter to a first value, the first value is less than a second value, and the second value is the power consumption parameter increased to the electronic device when a touch start event is detected.

[0272] It is worth noting that the reduction in power consumption in the embodiments of the present application is relative to the related art.

[0273] Take reducing the CPU frequency as an example for explanation. For example, in the related art, the CPU frequency changes within a range in a normal scenario (a scenario where the Touch Down event is not detected), and the CPU frequency is greatly increased after the Touch Down event is detected. Since the CPU frequency is greatly increased on the original frequency in the related art, in the embodiment of the present application, reducing the CPU frequency can be to maintain the original frequency of the CPU, to reduce the frequency based on the original frequency of the CPU, or to increase the frequency slightly based on the original frequency of the CPU.

[0274] For example, in the related art, the CPU frequency varies between 0.9 GHz and 1.5 GHz in a normal scenario. After a Touch Down event is detected, the CPU frequency is increased to 2.1 GHz.

[0275] In an embodiment of the present application, after the voice input scenario is recognized, the original frequency of the CPU can be maintained without being increased, for example, the CPU frequency is maintained at 1.5 GHz. Alternatively, the first preset amplitude (such as 10%, 20%, 30%, etc.) is increased based on the original frequency of the CPU, for example, the CPU frequency is increased from 1.5 GHz to 1.7 GHz. Alternatively, the frequency is reduced based on the original frequency of the CPU, for example, the CPU frequency is reduced from 1.5 GHz to 1.3 GHz. This is only an exemplary description and is not limited to this.

[0276] Similarly, the reduction of the screen refresh rate in the embodiments of the present application is also relative to the related art. For example, in the related art, the screen refresh rate supports multiple gears (for example, the current gears are 30Hz, 60Hz, 90Hz, 120Hz, 144Hz, etc.) of refresh rate adjustment. In conventional scenarios (scenarios where the Touch Down event is not detected), the screen refresh rate is maintained at a low gear (such as 60Hz). After the Touch Down event is detected, the screen refresh rate will be greatly increased. Since the related art has greatly increased the original screen refresh rate, in the embodiments of the present application, reducing the screen refresh rate can be to maintain the original screen refresh rate, or to reduce the screen refresh rate based on the original screen refresh rate, or to increase it slightly based on the original screen refresh rate.

[0277] For example, in the related art, the screen refresh rate supports multiple levels of refresh rate adjustment, and the screen refresh rate may be 60Hz in a normal scenario. After a Touch Down event is detected, the screen refresh rate will be increased to 120Hz or 144Hz.

[0278] In an embodiment of the present application, after recognizing the voice input scenario, the original screen refresh rate can be maintained without increasing it, for example, the screen refresh rate is maintained at 60Hz. Alternatively, the screen refresh rate can be increased by one gear on the basis of the original screen refresh rate, for example, the screen refresh rate is increased from 60Hz to 90Hz. Alternatively, the screen refresh rate can be reduced on the basis of the original screen refresh rate, for example, the screen refresh rate is reduced from 60Hz to 30Hz. This is only an exemplary description and is not limited to this.

[0279] Similarly, the reduction of screen brightness in the embodiments of the present application is also relative to the related art. For example, in the related art, the screen brightness changes within a range in a normal scenario (a scenario where a Touch Down event is not detected), and after a Touch Down event is detected, the screen brightness is greatly increased. Since the related art greatly increases the original screen brightness, in the embodiments of the present application, reducing the screen brightness can be to maintain the original screen brightness, to reduce the frequency based on the original screen brightness, or to increase the original screen brightness slightly.

[0280] For example, in the related art, the screen brightness varies between 100 nits and 300 nits in normal scenarios. After a Touch Down event is detected, the screen brightness is increased to 500 nits.

[0281] In an embodiment of the present application, after the voice input scene is recognized, the original screen brightness can be maintained without being increased, for example, the original screen brightness is maintained at 300nit. Alternatively, the second preset amplitude (such as 20% to 40%) is increased on the basis of the original screen brightness, for example, the original screen brightness is increased from 300nit to 400nit. Alternatively, the original screen brightness is reduced, for example, the original screen brightness is reduced from 300nit to 200nit. This is only an exemplary description and is not limited to this.

[0282] S209: When an end event is detected, the increase of the power consumption parameter of the electronic device is not restricted.

[0283] The end event may include a Touch Up event and / or an Audio Record stop event.

[0284] Among them, the Touch Up event refers to a touch up event, for example, a Touch Up event is generated when a user lifts a finger on the screen of an electronic device (such as a mobile phone). The Touch Up event can carry information such as event type, touch end time, and finger leaving position.

[0285] The Audio Record stop event is also called the recording end event. The Audio Record stop event can carry information such as the recording end time, recording duration, the second UID of the second application that calls the Audio Record.stop interface, and the second application package name.

[0286] For example, when a user's finger leaves the screen of an electronic device (such as a mobile phone), the touch sensor detects the user's finger lifting operation and generates a corresponding Touch Up event. It is worth noting that each time a user's finger leaves the screen of an electronic device (such as a mobile phone), the touch sensor detects the user's finger lifting operation and generates a corresponding Touch Up event, and assigns different identification information to each Touch Up event to distinguish different Touch Up events.

[0287] In the embodiment of the present application, the IM application is used as For example, a user long presses the "Press and Speak" button in the voice input box and starts to speak. Then the user lifts his finger, and a corresponding Touch Up event is generated based on the finger lift operation. The generated Touch Up event is passed to TP, and TP receives the Touch Up event.

[0288] After receiving the Touch Up event, TP passes the Touch Up event to the Input Dispatcher module. Since the trigger function is pre-added in the Input Dispatcher module, when the Touch Up event is detected, the Input Dispatcher module is triggered to pass the Touch Up event to the IM application, and the IM application receives the Touch Up event.

[0289] The Input Dispatcher module also passes the Touch Up event to the scene recognition service. The scene recognition service receives the Touch Up event and records the identification information, event type, touch end time, finger leave position and other information of the Touch Up event.

[0290] At the same time, after receiving the Touch Up event, the scene recognition service determines that the power consumption parameter of the electronic device is not restricted. Not restricting the increase of the power consumption parameter of the electronic device may be not reducing the power consumption parameter of the electronic device, or not increasing the power consumption parameter to the first value. The scene recognition service sends the information to the power consumption parameter adjustment module, which is specifically executed by the power consumption parameter adjustment module.

[0291] For example, the Audio Record module includes not only the Audio Record.start interface but also the Audio Record.stop interface. The IM application calls the Audio Record.stop interface in the system, and then the Audio Record module ends the voice recording, that is, the Audio Record module generates an Audio Record stop event. The Audio Record stop event indicates the end of the recording.

[0292] Since a trigger function is pre-added in the Audio Record module, when the IM application calls the AudioRecord.stop interface, the Audio Record module is triggered to notify the scene recognition service. The scene recognition service records the AudioRecord stop event, that is, records the recording end time, recording duration, the second UID of the second application that calls the Audio Record.stop interface, and the second application package name and other information.

[0293] At the same time, the Audio Record module sends the recorded voice to the IM application. After receiving the recorded voice, the IM application sends the recorded voice to the chat partner.

[0294] Similarly, after receiving the Audio Record stop event, the scene recognition service determines that the power consumption parameters of the electronic device are not restricted. Not restricting the increase of the power consumption parameters of the electronic device may mean not reducing the power consumption parameters of the electronic device, or not increasing the power consumption parameters to the first value. The scene recognition service sends this information to the power consumption parameter adjustment module, which is specifically executed by the power consumption parameter adjustment module.

[0295] It is worth noting that, usually, the Touch Up event occurs first, and the Audio Record stop event occurs later. For example, the user long presses the "Press and Talk" button to input / record voice, and releases the "Press and Talk" button after the voice input / recording is completed. At this time, the Touch Up event is generated first, and then the recording ends, and the Audio Record stop event is generated.

[0296] Of course, there are exceptions. For example, some IM applications have a limited recording time for a single voice recording. When the recording time is exceeded, the Audio Record stop event occurs first, followed by the Touch Up event. The duration of a single voice recording is 60 seconds. When the recording duration reaches 60 seconds and the user is still pressing the "Press and Speak" button, an Audio Recordstop event is generated first, and then a Touch Up event is generated as the user releases the "Press and Speak" button.

[0297] Optionally, in a possible implementation, the scene recognition service can also obtain TouchUp events from other modules, and record the identification information, event type, touch end time, finger leaving position, etc. of the TouchUp event. For example, the electronic device may include a touch screen driver, and the TouchUp event is transmitted from the TP driver to the application framework layer, and then to the application layer. In other words, the TP driver, the application framework layer, and the application layer can all detect the TouchUp event, and the scene recognition service can obtain the TouchUp event from the TP driver, the application framework layer, or the application layer.

[0298] The scene processing method provided in the embodiment of the present application determines that the current scene is a voice input scene when a touch start event is detected, a recording start event is detected within a preset time interval, and a first application and a second application are detected to be consistent; in the voice input scene, the power consumption parameter of the electronic device is reduced, or the power consumption parameter is increased to a first value, the first value is less than the second value, and the second value is the power consumption parameter increased to the electronic device when the touch start event is detected.

[0299] Since the logic of generating a voice input scene is that a touch start event occurs first and then a recording start event occurs, and the time interval between the touch start event and the recording start event is within a preset time interval, and the application in which the touch start event occurs is consistent with the application in which the recording start event occurs. The scene processing method provided in the present application does not rely on layout information and Activity information when identifying a voice input scene, but identifies the voice input scene according to the logic of generating a voice input scene, thereby accurately identifying the voice input scene.

[0300] Compared with the related art in which power consumption parameters are increased when a touch start event is detected, the scene processing method provided in the present application reduces the power consumption parameters of the electronic device in the voice input scene, or increases the power consumption parameters to a first value, thereby effectively reducing the power consumption of the electronic device in the voice input scene. While not affecting the user experience, it reduces the loss of various components of the electronic device and improves the battery life and life of the electronic device.

[0301] And because there are many IM applications that support voice chat functions, it is difficult to adapt the voice input scenarios of these IM applications one by one through layout information or Activity information in the related technology, and many IM applications will not develop corresponding Activities for the voice input scenarios, resulting in the inability to cover the voice input scenarios of all IM applications through layout information or Activity information, and it is also impossible to accurately identify the voice input scenarios of each IM application through layout information or Activity information. However, the scenario processing method provided in the embodiment of the present application can cover all IM applications, accurately identify the voice input scenarios of all IM applications, and has wider applicability.

[0302] The scene processing method provided by the embodiment of the present application, in a possible implementation, starts timing when a TouchDown event is detected, and at the same time determines whether the application that generates the Touch Down event is the focus application. If a recording start event is detected during the timing process, the scene recognition service will execute the steps of determining whether the caller of the Audio Record module is the focus application, determining the sequence of the recording start event and the Touch Down event, and determining whether the time interval between the Touch Down event and the recording start event is less than a preset time interval. If the Touch Down event is not detected when the timing reaches a preset time length (such as 300ms), the subsequent judgment process is abandoned, that is, the subsequent steps of determining whether the caller of the AudioRecord module is the focus application, determining the sequence of the recording start event and the Touch Down event, and determining whether the time interval between the Touch Down event and the recording start event is less than a preset time interval are not executed.

[0303] In another possible implementation, when a recording start event is detected, the scene recognition service executes the steps of determining whether the caller of the Audio Record module is a focus application, determining the sequence of the recording start event and the Touch Down event, and determining whether the time interval between the Touch Down event and the recording start event is less than a preset time interval.

[0304] In this implementation, since there are usually few recording start events, the subsequent judgment process is executed after the recording start event is detected, and there is no need to continuously judge the Touch Down event, which avoids power consumption and effectively reduces power consumption.

[0305] The scenario processing method provided by the present application is described in detail above with a complete process. The scenario processing method provided by the present application is described below with IM application as the main body.

[0306] See also Fig. 9 , Fig. 9 A schematic diagram of another scene processing method provided in an embodiment of the present application. The method includes:

[0307] S301, switch the voice input interface.

[0308] For example, the user opens the IM application and enters the personal chat interface, such as Figure 1 The user clicks the voice input icon 102 in the personal chat interface, and the mobile phone display interface changes from Figure 1 The personal chat interface shown in (b) is displayed as Figure 1 The voice input interface shown in (c) is shown in the figure. Figure 1 The voice input icon 102 shown in (b) is changed into a keyboard input icon 104 , and the text input box 103 is changed into a voice input box 105 , which also includes a “press and speak” button 1051 .

[0309] S302: Receive a long press operation of the recording button.

[0310] Exemplarily, the recording button is a “press and speak” button 1051. The user long presses the “press and speak” button 1051, and the IM application receives the user's long press recording button operation.

[0311] S303: Call the recording start interface.

[0312] Exemplarily, the IM application calls the Audio Record.start interface in the system, after which the Audio Record module starts voice recording, and the Audio Record module generates a recording start event.

[0313] S304: Receive a recording button release operation.

[0314] Exemplarily, when the user releases his finger, the IM application receives the user's release recording button operation.

[0315] S305: Call the recording end interface.

[0316] Exemplarily, the IM application calls the Audio Record.stop interface in the system, and then the Audio Record module ends the voice recording to obtain the recorded voice.

[0317] S306: Send the recorded voice.

[0318] Exemplarily, the Audio Record module sends the recorded voice to the IM application, and after receiving the recorded voice, the IM application sends the recorded voice to the chat partner.

[0319] In this implementation, the IM application receives various operations from users, implements the voice chat function, and gives users feedback in a timely manner, bringing users a good experience.

[0320] The above describes the scenario processing method provided by the present application with IM application as the main body. The following describes the scenario processing method provided by the present application in combination with the software structure.

[0321] For easier understanding, see Fig.10 , Fig.10 A flowchart of another scene processing method provided in an embodiment of the present application. The method includes:

[0322] S401: The IM application displays a voice input interface.

[0323] S402: The user clicks on the voice input interface, generating a Touch Down event.

[0324] For example, the user opens the IM application and enters the personal chat interface, such as Figure 1 The user clicks the voice input icon 102 in the personal chat interface, and the mobile phone display interface changes from Figure 1 The personal chat interface shown in (b) is displayed as Figure 1 The voice input interface shown in (c) is shown in the figure. Figure 1 The voice input icon 102 shown in (b) is changed into a keyboard input icon 104 , and the text input box 103 is changed into a voice input box 105 , which also includes a “press and speak” button 1051 .

[0325] The user long presses the “Press and Talk” button 1051 to generate a Touch Down event.

[0326] S403: The IM application receives the Touch Down event and displays a voice chat interface.

[0327] Exemplarily, a trigger function is pre-added in the Input Dispatcher module. When a Touch Down event is detected, the Input Dispatcher module is triggered to transfer the Touch Down event to the IM application, and the IM application receives the Touch Down event.

[0328] At the same time, the IM application displays the voice chat interface, such as Figure 2 The voice chat interface shown in (b).

[0329] It is worth noting that in order to improve the fluency of electronic devices and bring better experience to users, after detecting the Touch Down event, the InputDispatcher module sends the information of the Touch Down event to the power consumption parameter adjustment module. The power consumption parameter adjustment module will increase the power consumption parameters of the electronic device. However, in the scene processing method provided by this application, when the current scene is subsequently determined to be a voice input scene, the power consumption of the electronic device will be reduced. Therefore, even compared with the relevant technology, the power consumption of electronic devices in the voice input scene is effectively reduced, and the loss of various components of the electronic device is reduced without affecting the user experience, thereby improving the battery life and life of the electronic device.

[0330] S404: The scene recognition service records the first time of the Touch Down event.

[0331] Exemplarily, the scene recognition service receives the Touch Down event and records the identification information, event type, touch start / start time, touch position, etc. of the Touch Down event. In this embodiment, the touch start / start time of the Touch Down event is recorded as the first time.

[0332] S405: The IM application calls the Audio Record module and starts recording.

[0333] The Audio Record module may include an Audio Record.start interface.

[0334] Exemplarily, the IM application calls the Audio Record.start interface in the system, after which the Audio Record module starts voice recording, and the Audio Record module generates a recording start event.

[0335] S406. The scene recognition service records the second time of the sound start event and the second identification information of the second application.

[0336] Exemplarily, the scene recognition service records the recording start time of the recording start event, the second UID of the second application that calls the AudioRecord.start interface, and the second application package name, etc. In this embodiment, the recording start time of the recording start event is recorded as the second time.

[0337] S407: The scene recognition service obtains first identification information of the first application from the window manager.

[0338] Exemplarily, the window manager (WindowManager) is used to send the first UID and the first application package name to which the window of the first application belongs to the scene recognition service. The scene recognition service receives the first UID and the first application package name sent by the window manager.

[0339] S408: When the scene recognition service detects a touch start event, detects a recording start event within a preset time interval, and detects that the first application and the second application are consistent, it determines that the current scene is a voice input scene.

[0340] S409: In a voice input scenario, reduce a power consumption parameter of the electronic device, or increase the power consumption parameter to a first value.

[0341] Step S408 and step S409 may refer to the description of the above-mentioned step S101 and step S102, which will not be repeated here.

[0342] Optionally, in a possible implementation, in a voice input scenario, the scene recognition service may also set the upper limit of CPU frequency, screen refresh rate, screen brightness, DDR frequency, TP reporting rate, network resources, application drawing frame rate, system synthesis frame rate, etc., and send the upper limit to the power consumption parameter adjustment module. When the power consumption parameter adjustment module adjusts the CPU frequency, screen refresh rate, screen brightness, DDR frequency, TP reporting rate, application drawing frame rate, system synthesis frame rate, etc., the upper limit corresponding to each is used as the limit.

[0343] S410: Detecting a recording end event and / or detecting a Touch Up event.

[0344] S411. Do not limit the increase of power consumption parameters of the electronic device.

[0345] Step S410 and step S411 may refer to the description of the above step S209 and will not be repeated here.

[0346] Optionally, in a possible implementation, when a recording end event is detected and / or a Touch Up event is detected, the scene recognition service may cancel the upper limits of the CPU frequency, screen refresh rate, screen brightness, DDR frequency, TP reporting rate, network resources, application drawing frame rate, system synthesis frame rate, etc., and send the cancellation operation to the power consumption parameter adjustment module. When the power consumption parameter adjustment module adjusts the CPU frequency, screen refresh rate, screen brightness, DDR frequency, TP reporting rate, application drawing frame rate, system synthesis frame rate, etc., it is not limited by the corresponding upper limits.

[0347] This implementation method does not rely on layout information and Activity information when identifying voice input scenarios, but identifies voice input scenarios based on the logic of generating voice input scenarios, thereby accurately identifying voice input scenarios. Reducing the power consumption of electronic devices in this voice input scenario can reduce the loss of various components of electronic devices without affecting user experience, thereby improving the battery life and life of electronic devices.

[0348] The scene processing method provided in the embodiment of the present application can also be applied to other scenes that require improving power consumption to increase fluency.

[0349] The above describes in detail an example of a scene processing method provided by an embodiment of the present application. It is understandable that, in order to implement the above functions, the electronic device includes hardware and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in combination with the embodiments, but such implementation should not be considered to exceed the scope of the present application.

[0350] The embodiment of the present application can divide the functional modules of the electronic device according to the above method example. For example, each function can be divided into various functional modules, such as a first determination unit, a second determination unit, and an interpolation unit, etc., or two or more functions can be integrated into one module. The above integrated module can be implemented in the form of hardware or in the form of a software functional module. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0351] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0352] The electronic device provided in this embodiment is used to execute the above-mentioned scene processing method, and thus can achieve the same effect as the above-mentioned implementation method.

[0353] In the case of an integrated unit, the electronic device may further include a processing module, a storage module and a communication module. The processing module may be used to control and manage the actions of the electronic device. The storage module may be used to support the electronic device to execute stored program codes and data, etc. The communication module may be used to support the electronic device to communicate with other devices.

[0354] Among them, the processing module can be a processor or a controller. It can implement or execute various exemplary logic boxes, modules and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of digital signal processing (DSP) and a microprocessor, etc. The storage module can be a memory. The communication module can specifically be a device that interacts with other electronic devices, such as a radio frequency circuit, a Bluetooth chip, a WiFi chip, etc.

[0355] In one embodiment, when the processing module is a processor and the storage module is a memory, the electronic device involved in this embodiment may be a Figure 5 Device of the structure shown.

[0356] An embodiment of the present application also provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the processor executes the scene processing method of any of the above embodiments.

[0357] The embodiment of the present application also provides a computer program product. When the computer program product is run on a computer, the computer is enabled to execute the above-mentioned related steps to implement the scene processing method in the above-mentioned embodiment.

[0358] The present application also provides a chip. Fig.11 , Fig.11 A schematic diagram of the structure of a chip provided in an embodiment of the present application. Fig.11 The chip shown may be a general-purpose processor or a dedicated processor. The chip includes a processor 510. The processor 510 is used to execute the scene processing method of any of the above embodiments.

[0359] Optionally, the chip further includes a transceiver 520, which is used to accept control of the processor and to support the communication device in executing the technical solution shown above.

[0360] Optional, Fig.11 The chip shown may also include: a storage medium 530 .

[0361] It should be noted that Fig.11The chip shown can be implemented using the following circuits or devices: one or more field programmable gate arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits that can perform the various functions described throughout this application.

[0362] Among them, the electronic device, computer-readable storage medium, computer program product or chip provided in this embodiment are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above and will not be repeated here.

[0363] Through the description of the above implementation methods, technical personnel in the relevant field can understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0364] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of modules or units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0365] The units described as separate components may or may not be physically separated, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0366] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0367] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program code.

[0368] The above contents are only specific implementation methods of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A scene processing method, It is characterized in that Applied to instant messaging scenarios, the scenario processing method includes: When a touch start event is detected, and a recording start event is detected within a preset time interval, and when it is detected that the first application and the second application are consistent, it is determined that the current scene is a voice input scene, the first application is the application corresponding to the touch start event, and the second application is the application corresponding to the recording start event; In the voice input scenario, reducing a power consumption parameter of the electronic device, or increasing the power consumption parameter to a first value, the first value being less than a second value, the second value being the power consumption parameter increased to by the electronic device when the touch start event is detected; In the voice input scenario, after reducing the power consumption parameter of the electronic device, when a touch end event and / or a recording end event is detected, the power consumption parameter of the electronic device is not reduced; or, in the voice input scenario, after increasing the power consumption parameter to the first value, when a touch end event and / or a recording end event is detected, the power consumption parameter is not increased to the first value.

2. The scene processing method according to claim 1, It is characterized in that Before determining that the current scene is a voice input scene, the method further includes: When the touch start event is detected, recording the first time of the touch start event; When the recording start event is detected, recording a second time of the recording start event; When the difference between the second time and the first time is smaller than the preset time interval, it is determined that the recording start event is detected within the preset time interval.

3. The scene processing method according to claim 1 or 2, It is characterized in that Before determining that the current scene is a voice input scene, the method further includes: Obtaining first identification information of the first application; Acquire second identification information of the second application; When it is detected that the first identification information is the same as the second identification information, it is determined that the first application is consistent with the second application.

4. The scene processing method according to claim 3, It is characterized in that The first identification information includes a first UID and / or a first application package name, and the second identification information includes a second UID and / or a second application package name.

5. The scene processing method according to any one of claims 1 to 4, It is characterized in that The power consumption parameters include any one or any combination of CPU frequency, screen refresh rate, screen brightness, double data rate frequency, touch screen reporting rate, application drawing frame rate and system synthesis frame rate.

6. The scene processing method according to claim 1, It is characterized in that The electronic device includes a touch screen driver, and the method further includes: The touch start event and / or the touch end event is detected by the touch screen driver or input scheduling thread module.

7. The scene processing method according to claim 1, It is characterized in that The electronic device includes a microphone driver, and the method further includes: The recording start event and / or the recording end event is detected by the microphone driver.

8. An electronic device, It is characterized in that include: one or more processors; one or more memories; The memory stores one or more programs, and when the one or more programs are executed by the processor, the electronic device executes the method according to any one of claims 1 to 7.

9. A chip, It is characterized in that include: A processor, used to call and run a computer program from a memory, so that an electronic device equipped with the chip executes a method as claimed in any one of claims 1 to 7.

10. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the processor is caused to perform the method according to any one of claims 1 to 7.

Images