Method for adjusting call volume, and electronic device

By displaying call scene options in electronic devices and playing background sounds, the problems of poor call volume adjustment and privacy leakage are solved, improving user experience and interactivity.

WO2024234983A1PCT designated stage expired Publication Date: 2024-11-21HUAWEI TECH CO LTD

Patent Information

Application Number
PCT/CN2024/090349
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-15
Filing Date
2024-04-28
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

The prior art is difficult to effectively adjust the call volume during the call, resulting in poor user experience and may disclose user privacy.

Method used

Provides a method of adjusting the call volume, allowing the user to select a call volume suitable for the current scene by displaying the call scene options in the electronic device, and plays a background sound during the call to protect user privacy.

Benefits of technology

It improves the interactivity between users and devices, simplifies call volume adjustment, improves user experience, and avoids privacy leakage through background sounds, meeting users' needs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024090349_21112024_PF_FP_ABST
    Figure CN2024090349_21112024_PF_FP_ABST
Patent Text Reader

Abstract

Provided in the present application are a method for adjusting a call volume, and an electronic device. The electronic device may be preset with a plurality of types of call scenarios, and may also be preset with call volumes and background sounds, which respectively correspond to the plurality of types of call scenarios. Before making a call with a peer electronic device, the electronic device may identify a plurality of current call scenarios. A user may select one call scenario from among the plurality of call scenarios. The electronic device may play a sound during a call by using the call volume corresponding to the call scenario, which is selected by the user. The peer electronic device and / or the electronic device may also play the background sound for the selected call scenario. By means of the technical solution of the present application, the interactivity between a user and a mobile phone can be improved, so as to simplify related operations of the user adjusting a call volume, thereby improving the user experience; and privacy leakage can also be avoided by means of playing a background sound.
Need to check novelty before this filing date? Find Prior Art

Description

Method for adjusting call volume and electronic device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on May 15, 2023, with application number 202310548455.6 and application name “Method and electronic device for adjusting call volume”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of electronic technology, and in particular to a method for adjusting call volume and an electronic device. Background Art

[0003] With the development of electronic devices, user demands are constantly increasing. Electronic devices must not only provide call functions but also consider the user experience during calls. Among these, call volume is one factor that influences user comfort during calls. The call volume of an electronic device during a call can be the volume provided by the device's current audio device. This volume may be too loud or too low, affecting the user experience and potentially leaking user privacy. Therefore, how to ensure that the call volume is satisfactory to the user from the moment the call is initiated is an urgent problem in this field.

[0004] Summary of the Invention

[0005] The present application provides a method and electronic device for adjusting call volume, which not only allows users to make calls at a volume that suits the current state, but also protects the user's privacy by avoiding privacy leakage by playing background sound, and can also meet the user's wishes so that the other end user can recognize the current call scene of the user.

[0006] In a first aspect, the present application provides a method for adjusting call volume, characterized in that the method is applied to an electronic device, and the method includes:

[0007] The electronic device receives a call request sent by a peer electronic device and displays a first interface, wherein the first interface includes a first call scenario option and a second call scenario option, wherein the first call scenario option corresponds to a first call scenario, and the second call scenario option corresponds to a second call scenario, wherein the first call scenario and the second call scenario are different. In response to an operation performed by selecting the first call scenario option, the electronic device establishes a call connection with the peer electronic device. The electronic device plays sound at a call volume corresponding to the first call scenario. The electronic device sends background sound corresponding to the first call scenario to the peer electronic device, and the background sound is played by the peer electronic device.

[0008] As can be seen from the above, during a call, the electronic device can play sound using the call volume corresponding to the call scenario selected by the user. The other electronic device and / or electronic device can also play background sound for the selected call scenario. This not only improves the interactivity between the user and the phone, simplifies the user's operation of adjusting the call volume, and enhances the user experience, but also prevents privacy leaks by playing background sound, further meeting user needs.

[0009] In combination with the first aspect, in some embodiments, after the electronic device establishes a call connection with the opposite electronic device, the method also includes: the electronic device displays a second interface, the second interface includes a second prompt information, and the first prompt information is used to prompt that the current call scene is the first call scene.

[0010] In a second aspect, the present application provides a method for adjusting call volume, characterized in that the method is applied to an electronic device, comprising: the electronic device displays a third interface in response to a user's operation of making a call, the third interface including a first call scene option and a second call scene option, the first call scene option corresponding to a first call scene, the second call scene option corresponding to a second call scene, and the first call scene is different from the second call scene. The electronic device initiates a call request to the opposite electronic device in response to the operation of selecting the first call scene option. After receiving the information from the opposite electronic device confirming the call request, the electronic device establishes a call connection with the opposite electronic device. The electronic device plays sound at the call volume corresponding to the first call scene. The electronic device sends the background sound corresponding to the first call scene to the opposite electronic device, and the background sound is played by the opposite electronic device.

[0011] As can be seen from the above, during a call, the electronic device can play sound using the call volume corresponding to the call scenario selected by the user. The other electronic device and / or electronic device can also play background sound for the selected call scenario. This not only improves the interactivity between the user and the phone, simplifies the user's operation of adjusting the call volume, and enhances the user experience, but also prevents privacy leaks by playing background sound, further meeting user needs.

[0012] In combination with the first and second aspects, in some embodiments, after the electronic device plays a sound at a call volume corresponding to the first call scenario, the method further includes: displaying, by the electronic device, a fourth interface, wherein the third interface includes second prompt information. The second prompt information is used to indicate that the current call scenario is the first call scenario.

[0013] In combination with the first and second aspects, in some embodiments, the method further includes: the peer electronic device includes multiple devices, the peer user information for the peer electronic device includes multiple devices, and the second call scenario is the call scenario corresponding to the peer user information with the highest priority among the multiple devices. In this way, the solution provided by this application can be implemented in a multi-person call scenario.

[0014] In combination with the first aspect and the second aspect, in some embodiments, the correspondence between the opposite-end user information and the second call scenario is set by the local user of the electronic device, or is preset by the electronic device.

[0015] In combination with the first aspect and the second aspect, in some embodiments, the first call scenario or the second call scenario is determined by the electronic device based on one or more of the following: the environment in which the local user is located, the status of the local user, the information of the opposite user, the relationship between the opposite user and the local user, and the current time.

[0016] In combination with the first and second aspects, in some embodiments, after the electronic device plays the sound at the call volume corresponding to the first call scenario, the method further includes: the electronic device playing the background sound. In this way, when other people other than the user may hear the user's call, they will mostly hear the background sound effects rather than the conversation content, thereby protecting the user's privacy.

[0017] In combination with the first and second aspects, in some embodiments, before the electronic device plays the sound at the call volume corresponding to the first call scenario, the method further includes: the electronic device performing voice modification processing on the sound. The electronic device playing the sound at the call volume corresponding to the first call scenario specifically includes: the electronic device playing the voice modified sound at the call volume corresponding to the first call scenario. This prevents others besides the user from determining the identity of the other user even if they may overhear the user's call, thereby protecting the user's privacy.

[0018] In a third aspect, the present application provides an electronic device comprising one or more processors and one or more memories. The one or more memories are coupled to the one or more processors, and the one or more memories are used to store computer program code, wherein the computer program code comprises computer instructions. When the one or more processors execute the computer instructions, the electronic device performs the method of the first aspect or any embodiment of the first aspect.

[0019] In a fourth aspect, an embodiment of the present application provides a computer storage medium comprising computer instructions, which, when executed on an electronic device, enables a vehicle to execute the method of the first aspect or any one of the embodiments of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] FIG1A is a schematic diagram of the structure of an electronic device provided in an implementation example of the present application.

[0021] FIG1B is a schematic diagram of the software structure of an electronic device provided in an implementation example of the present application.

[0022] FIG2 is a flowchart of a method for adjusting call volume of an electronic device provided in an implementation example of the present application.

[0023] 3A-5B are user interfaces of electronic devices provided in an implementation example of the present application.

[0024] FIG6 is a flowchart of a method for adjusting call volume of an electronic device provided in an implementation example of the present application.

[0025] 7A-9 are user interfaces of electronic devices provided in an implementation example of the present application. DETAILED DESCRIPTION

[0026] The following is a clear and detailed description of the technical solutions in the embodiments of the present application in conjunction with the accompanying drawings. 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 the text is only a description of the association relationship between related 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.

[0027] In the following, the terms "first" and "second" are used for descriptive purposes only and should not be understood to imply or suggest relative importance or implicitly indicate the number of the technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of the embodiments of this application, unless otherwise specified, "plurality" means two or more.

[0028] The term "user interface (UI)" in the following embodiments of this application refers to a medium interface for interaction and information exchange between an application or operating system and a user, which realizes the conversion between the internal form of information and the form acceptable to the user. The user interface is a source code written in a specific computer language such as Java and extensible markup language (XML). The interface source code is parsed and rendered on an electronic device and finally presented as content that the user can recognize. The commonly used form of user interface is graphical user interface (GUI), which refers to a user interface related to computer operations that is displayed in a graphical manner. It can be a visual interface element such as text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, etc. displayed on the display screen of an electronic device.

[0029] Calls are a convenient way for users to communicate. The call volume is one of the factors that influence the user experience during a call. There are several ways to adjust the call volume:

[0030] Method 1: The electronic device sets a volume for each of the three answering methods: answering with a handset, answering with a headset, and answering with a hands-free mode. When the electronic device uses different answering methods, the electronic device can detect the current answering method and set the corresponding volume to answer the call. The user can then manually adjust the volume of the answering call. In this way, the answering scenario is relatively simple, and the volume level is only divided into three levels, which is also relatively simple. In this way, method 1 is equivalent to a fixed volume as soon as the call is connected, regardless of when and where the user uses the handset to answer the call.

[0031] Method 2: The electronic device can adjust the call volume based on the current ambient noise level and the fit of the user's ear against the electronic device. If the ambient volume (i.e., noise) is loud or the fit is weak, the call volume is increased; if the ambient volume is quiet or the fit is strong, the call volume is decreased.

[0032] As can be seen from the two methods above, method 1 uses a fixed volume for calls, while method 2 adjusts the volume based on the current ambient noise and ear fit strength. Both methods fail to take into account the user's volume requirements in different scenarios. For example, a user may need a louder volume when working and a quieter volume when taking a break, and so on. Another example is a user who needs a louder volume when talking to colleagues and a quieter volume when talking to family.

[0033] In order to solve the problems arising from the above-mentioned methods, the present application provides a method and an electronic device for adjusting the call volume. Before specifically introducing the method provided in the embodiment of the present application, the following explanation is first given regarding the call:

[0034] In terms of call form, the calls provided in the embodiments of the present application may include but are not limited to: audio calls, video calls, etc.

[0035] From the perspective of application category, the call provided in the embodiment of the present application can be implemented based on a system application (such as a telephone application) or based on a third-party application (such as an instant messaging application).

[0036] From the perspective of communication technology, the calls provided in the embodiments of the present application can be implemented based on protocols such as the Global System for Mobile Communications (GSM) protocol or the Voice over Long-Term Evolution (VOLTE) protocol, or can be implemented based on technologies such as the fourth generation mobile communication technology (4G) or the fifth generation mobile communication technology (5G).

[0037] The call process involved in the embodiments of the present application mainly involves two electronic devices, one of which can be called the local electronic device and the other can be called the remote electronic device. The above call can be initiated by the local electronic device or the remote electronic device. In one possible implementation, the call process can also involve multiple electronic devices, one of which can be the local electronic device and the others can be remote electronic devices.

[0038] Based on the above-described method for adjusting the volume, some structural schematic diagrams of the local electronic device provided in the embodiments of the present application are introduced below.

[0039] FIG. 1A exemplarily shows a schematic structural diagram of an electronic device 100 .

[0040] The electronic device 100 may be equipped with Or a portable terminal device with other operating systems, the electronic device 100 can be a mobile phone, a tablet computer, a desktop computer, a laptop computer, a handheld computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a personal digital assistant (PDA), an augmented reality (AR) device, a virtual reality (VR) device, an artificial intelligence (AI) device, a wearable device, a vehicle, an in-vehicle device, a smart home device and / or a smart city device. Without limitation, the electronic device 100 can also include a laptop computer with a touch-sensitive surface or touch panel, a desktop computer with a touch-sensitive surface or touch panel, and other non-portable terminal devices. The embodiment of the present application does not impose any special restrictions on the specific type of the electronic device 100.

[0041] 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.

[0042] It should be understood that the structure illustrated in the embodiments of the present invention does not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0043] 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 processing unit (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). The different processing units may be independent devices or integrated into one or more processors.

[0044] In some implementations, the processor 110 can be used to identify the user information of the other electronic device and determine whether it is the target person. The processor 110 can also be used to determine the target call scene used for the current call based on the user information. The processor 110 can also be used to select a target call scene from multiple current call scenes in response to user operations. The processor 110 can also be used to adjust the default call volume to the first call volume. The processor 110 can also be used to determine the location information of the current electronic device 100 and determine the current call scene based on the location information. The processor 110 can also be used to adjust the call volume to the default call volume or the first call volume after determining the target call scene.

[0045] Processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 110. If processor 110 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 110 latency, and thus improves system efficiency.

[0046] In some embodiments, the memory can be used to store various call scenarios and their corresponding default call volumes or first call volumes. The memory can also be used to store contact information, such as contact avatars, contact names, contact notes, contact groups, contact numbers, and number locations. The memory can also be used to store historically selected call scenarios for the peer electronic device.

[0047] In some embodiments, the processor 110 may include one or more interfaces. The interfaces 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), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface.

[0048] The I2C interface is a bidirectional synchronous serial bus that includes a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple I2C bus lines. The processor 110 may be coupled to the touch sensor 180K, the charger, the flash, the camera 193, and the like via different I2C bus interfaces. For example, the processor 110 may be coupled to the touch sensor 180K via the I2C interface, enabling communication between the processor 110 and the touch sensor 180K via the I2C bus interface, thereby implementing the touch function of the electronic device 100.

[0049] The I2S interface can be used for audio communication. In some embodiments, the processor 110 can include multiple I2S buses. The processor 110 can be coupled to the audio module 170 via the I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the I2S interface, enabling the function of answering calls through a Bluetooth headset.

[0050] The PCM interface can also be used for audio communication, sampling, quantizing, and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 can be coupled via a PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 via the PCM interface, enabling the function of answering calls via a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

[0051] The UART interface is a universal serial data bus used for asynchronous communication. This bus can be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, the UART interface is typically used to connect the processor 110 and the wireless communication module 160. For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 via the UART interface to implement Bluetooth functionality. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the UART interface, enabling the function of playing music through Bluetooth headphones.

[0052] The MIPI interface can be used to connect the processor 110 with peripheral devices such as the display screen 194 and the camera 193.

[0053] The GPIO interface can be configured through software. The GPIO interface can be configured as a control signal or a data signal.

[0054] USB interface 130 is an interface that complies with USB standards and may be a Mini USB interface, a Micro USB interface, a USB Type-C interface, or the like. USB interface 130 can be used to connect a charger to charge electronic device 100, transfer data between electronic device 100 and peripheral devices, or connect headphones to play audio.

[0055] It is understood that the interface connection relationship between the modules illustrated in the embodiment of the present invention is merely an illustrative illustration and does not constitute a structural limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may also adopt different interface connection methods from the above embodiments, or a combination of multiple interface connection methods.

[0056] The charging management module 140 is configured to receive charging input from a charger. The charger can be either a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 can receive wireless charging input via the wireless charging coil of the electronic device 100. While charging the battery 142, the charging management module 140 can also provide power to the electronic device 100 via the power management module 141.

[0057] 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 provides power to the processor 110, the internal memory 121, the display 194, the camera 193, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage, impedance). In some other embodiments, the power management module 141 can also be set in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 can also be set in the same device.

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

[0059] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals.

[0060] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G 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.

[0061] The modulation and demodulation processor may include a modulator and a demodulator. The modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal.

[0062] 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 that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, demodulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0063] 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 a network and other devices through wireless communication technologies. The wireless communication technologies 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. The GNSS may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS) and / or a satellite based augmentation system (SBAS).

[0064] In some implementations, the mobile communication module 150 and the wireless communication module 160 may be used to determine the current location information of the electronic device 100 .

[0065] Electronic device 100 implements display functionality through a GPU, display screen 194, and an application processor. A GPU is a microprocessor for image processing that connects display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or modify display information.

[0066] Display screen 194 is used to display images, videos, and the like. Display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLED, a Micro-oLed, or a quantum dot light-emitting diode (QLED). In some embodiments, electronic device 100 may include one or N display screens 194, where N is a positive integer greater than one.

[0067] In some implementations, display screen 194 can be used to display a user interface for adjusting the volume of various call scenarios from a default call volume to a first call volume. Display screen 194 can also be used to display user interfaces for incoming and outgoing calls with multiple call scenario options available for user selection, such as a first interface, a second interface, a third interface, and a fourth interface. Display screen 194 can also be used to display a user interface for setting a call scenario corresponding to a contact in a contact-related user interface.

[0068] The electronic device 100 can implement a shooting function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, and an application processor.

[0069] The ISP processes data fed back by camera 193. For example, when taking a photo, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, which is then passed to the ISP for processing and converted into a visible image. The ISP can also perform algorithmic optimization on image noise and brightness. It can also optimize parameters such as exposure and color temperature of the captured scene. In some embodiments, the ISP can be located within camera 193.

[0070] The camera 193 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, and then passes the electrical signal to the ISP for conversion into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. In some embodiments, the electronic device 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.

[0071] The digital signal processor is used to process digital signals. In addition to processing digital image signals, it can also process other digital signals. For example, when the electronic device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

[0072] Video codecs are used to compress or decompress digital video. Electronic device 100 may support one or more video codecs. This allows electronic device 100 to play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, and MPEG4.

[0073] The NPU is a neural network (NN) computing processor. Drawing on the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it rapidly processes input information and can continuously self-learn. The NPU can enable intelligent cognitive applications in electronic device 100, such as image recognition, face recognition, speech recognition, and text comprehension.

[0074] The internal memory 121 may include one or more random access memories (RAM) and one or more non-volatile memories (NVM).

[0075] In some implementations, the internal memory 121 may store a volume adjustment process for adjusting the call volume according to a call scenario.

[0076] Random access memory may include static random-access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM, for example, the fifth generation DDR SDRAM is generally referred to as DDR5 SDRAM), etc.; non-volatile memory may include disk storage devices and flash memory.

[0077] Flash memory can be divided into NOR FLASH, NAND FLASH, 3D NAND FLASH, etc. according to the operating principle; single-level cell (SLC), multi-level cell (MLC), triple-level cell (TLC), quad-level cell (QLC), etc. according to the storage cell potential level; universal flash storage (UFS) and embedded multi media card (eMMC) can be divided into UFS and eMMC according to the storage specification.

[0078] The random access memory can be directly read and written by the processor 110, and can be used to store executable programs (such as machine instructions) of the operating system or other running programs, and can also be used to store user and application data.

[0079] The non-volatile memory may also store executable programs and user and application data, etc., and may be loaded into the random access memory in advance for direct reading and writing by the processor 110 .

[0080] The external memory interface 120 can be used to connect to an external non-volatile memory to expand the storage capacity of the electronic device 100. The external non-volatile memory communicates with the processor 110 via the external memory interface 120 to implement data storage. For example, files such as music and videos can be stored in the external non-volatile memory.

[0081] The electronic device 100 can implement audio functions such as music playback and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

[0082] The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The audio module 170 can also be used to encode and decode audio signals. In some embodiments, the audio module 170 can be provided in the processor 110, or some functional modules of the audio module 170 can be provided in the processor 110.

[0083] In some implementations, the audio module 170 can convert the sound data collected by the other electronic device into audio, and when the electronic device 100 selects the hands-free mode for a call, the audio is played through the speaker 170A. The audio module 170 can also be used to collect audio through the microphone 170C, such as the sound made by the user, and convert the audio into sound data. In one possible implementation, the audio module 170 can also play the background sound corresponding to the first call scene. The speaker 170A, also called a "speaker", is used to convert audio electrical signals into sound signals. The electronic device 100 can listen to music or listen to hands-free calls through the speaker 170A.

[0084] The receiver 170B, also called a "handset", is used to convert audio electrical signals into sound signals. When the electronic device 100 receives a call or a voice message, the user can place the receiver 170B close to the ear to hear the voice.

[0085] Microphone 170C, also known as "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can speak by putting their mouth close to the microphone 170C to input the sound signal into the microphone 170C. The electronic device 100 can be provided with at least one microphone 170C. In other embodiments, the electronic device 100 can be provided with two microphones 170C, which can not only collect sound signals but also realize noise reduction function. In other embodiments, the electronic device 100 can also be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify the source of sound, realize directional recording function, etc.

[0086] The headphone jack 170D is used to connect a wired headphone and can be a USB interface 130 or a 3.5mm open mobile terminal platform (OMTP) standard interface or a cellular telecommunications industry association of the USA (CTIA) standard interface.

[0087] In some implementations, the earphone interface 170D can be used to enable the electronic device 100 to make calls in earphone mode.

[0088] The pressure sensor 180A is used to sense pressure signals and convert the pressure signals into electrical signals.

[0089] The gyroscope sensor 180B can be used to determine the motion posture of the electronic device 100. In some embodiments, the angular velocity of the electronic device 100 around three axes (i.e., x, y, and z axes) can be determined by the gyroscope sensor 180B. The gyroscope sensor 180B can be used for anti-shake shooting. For example, when the shutter is pressed, the gyroscope sensor 180B detects the angle of the electronic device 100 shaking, calculates the distance that the lens module needs to compensate based on the angle, and allows the lens to offset the shaking of the electronic device 100 through reverse movement to achieve anti-shake. The gyroscope sensor 180B can also be used for navigation and somatosensory game scenes.

[0090] The air pressure sensor 180C is used to measure air pressure. In some embodiments, the electronic device 100 calculates the altitude using the air pressure value measured by the air pressure sensor 180C to assist in positioning and navigation.

[0091] The magnetic sensor 180D includes a Hall sensor. The electronic device 100 can use the magnetic sensor 180D to detect the opening and closing of the flip case. In some embodiments, when the electronic device 100 is a flip phone, the electronic device 100 can detect the opening and closing of the flip cover based on the magnetic sensor 180D. Based on the detected opening and closing status of the case or flip cover, features such as automatic unlocking of the flip cover can be configured.

[0092] Accelerometer 180E can detect the magnitude of acceleration of electronic device 100 in all directions (generally three axes). When electronic device 100 is stationary, it can detect the magnitude and direction of gravity. It can also be used to identify the posture of electronic device 100, enabling applications such as switching between landscape and portrait modes and pedometers.

[0093] The distance sensor 180F is used to measure distance. The electronic device 100 can measure distance using infrared or laser. In some embodiments, when shooting a scene, the electronic device 100 can use the distance sensor 180F to measure distance to achieve fast focusing.

[0094] The proximity light sensor 180G may include, for example, a light emitting diode (LED) and a light detector, such as a photodiode. The LED may be an infrared LED. The electronic device 100 emits infrared light through the LED. The electronic device 100 uses the photodiode to detect infrared reflected light from nearby objects.

[0095] Ambient light sensor 180L is used to sense ambient light brightness. Electronic device 100 can adaptively adjust the brightness of display screen 194 based on the perceived ambient light. Ambient light sensor 180L can also be used to automatically adjust white balance when taking photos. Ambient light sensor 180L can also work with proximity light sensor 180G to detect whether electronic device 100 is in a pocket to prevent accidental touches.

[0096] The fingerprint sensor 180H is used to collect fingerprints. The electronic device 100 can use the collected fingerprint characteristics to implement fingerprint unlocking, access application locks, fingerprint photography, fingerprint call answering, etc.

[0097] The temperature sensor 180J is used to detect temperature. In some embodiments, the electronic device 100 uses the temperature detected by the temperature sensor 180J to execute a temperature processing strategy.

[0098] The touch sensor 180K is also called a "touch-sensitive device." The touch sensor 180K can be disposed on the display screen 194. The touch sensor 180K and the display screen 194 form a touch screen, also called a "touch screen." The touch sensor 180K is used to detect touch operations applied thereto or in the vicinity thereof. The touch sensor can transmit the detected touch operations to the application processor to determine the type of touch event. Visual output related to the touch operations can be provided via the display screen 194. In other embodiments, the touch sensor 180K can also be disposed on the surface of the electronic device 100, at a location different from that of the display screen 194.

[0099] In some implementations, the touch sensor 180K can be used to detect a user's touch operation on a call scenario option in the incoming call interface, and send relevant information about the touch operation to the processor 110. The touch sensor 180K can also be used to detect a user's touch operation on a call scenario option in the outgoing call interface, and send relevant information about the touch operation to the processor 110.

[0100] The bone conduction sensor 180M can obtain a vibration signal. In some embodiments, the bone conduction sensor 180M can obtain a vibration signal of a vibrating bone in a human vocal part.

[0101] The buttons 190 include a power button, a volume button, and the like. The buttons 190 may be mechanical buttons or touch buttons. The electronic device 100 may receive key inputs and generate key signal inputs related to user settings and function control of the electronic device 100.

[0102] 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.

[0103] The indicator 192 may be an indicator light, which may be used to indicate the charging status, power level changes, messages, missed calls, notifications, etc.

[0104] The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to or disconnected from the electronic device 100 by inserting or removing the SIM card into or from the SIM card interface 195 .

[0105] The software system of the electronic device 100 can adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture. In the embodiment of the present invention, the Android system with a layered architecture is used as an example to illustrate the software structure of the electronic device 100.

[0106] FIG1B is a block diagram of the software structure of the electronic device 100 according to an embodiment of the present invention.

[0107] A layered architecture divides software into several layers, each with distinct roles and responsibilities. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0108] The application layer can include a series of application packages.

[0109] As shown in FIG1B , the application package may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, and short message.

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

[0111] As shown in FIG. 1B , the application framework layer may include a window manager, a content provider, a view system, a telephony manager, a resource manager, a notification manager, and the like.

[0112] The window manager is used to manage window programs. The window manager can obtain the display size, determine whether there is a status bar, lock the screen, take screenshots, etc.

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

[0114] The view system includes visual controls, such as those for displaying text and images. The view system is used to build applications. A display interface can consist of one or more views. For example, a display interface containing a text notification icon might include a view for displaying text and a view for displaying images.

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

[0116] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0117] The notification manager enables applications to display notification information in the status bar. This can be used to convey notification-type messages and can disappear automatically after a short period of time 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 used to display notifications in the form of icons or scrolling text in the top status bar of the system, such as notifications from applications running in the background, or notifications that appear on the screen in the form of dialog windows. For example, a text message can be displayed in the status bar, a notification sound can be emitted, the electronic device 100 can vibrate, an indicator light can flash, etc.

[0118] Android Runtime includes core libraries and a virtual machine. Android runtime is responsible for scheduling and management of the Android system.

[0119] The core library consists of two parts: one is the function that needs to be called by the Java language, and the other is the Android core library.

[0120] The application layer and application framework layer run in a virtual machine. The virtual machine executes Java files in the application layer and application framework layer as binary files. The virtual machine manages object lifecycles, stack management, thread management, security and exception management, and garbage collection.

[0121] 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.

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

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

[0124] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0125] A 2D graphics engine is a drawing engine for 2D drawings.

[0126] The kernel layer is the layer between hardware and software. The kernel layer includes at least display driver, camera driver, audio driver, and sensor driver.

[0127] The following describes the workflow of the software and hardware of the electronic device 100 in conjunction with capturing a photo scene.

[0128] When the touch sensor 180K receives a touch operation, the corresponding hardware interrupt is sent to the kernel layer. The kernel layer processes the touch operation into a raw input event (including touch coordinates, touch operation timestamp, and other information). The raw input event is stored in the kernel layer. The application framework layer obtains the raw input event from the kernel layer and identifies the control corresponding to the input event. For example, if the touch operation is a touch single-click operation and the control corresponding to the single-click operation is the control of the camera application icon, the camera application calls the interface of the application framework layer to start the camera application, and then starts the camera driver by calling the kernel layer to capture a still image or video through the camera 193.

[0129] The following describes in detail the method for adjusting the call volume provided in an embodiment of the present application in conjunction with the user interface exemplarily provided in the present application.

[0130] Example 1:

[0131] In the first embodiment, the electronic device 100 can be pre-set with multiple call scenarios, and can also pre-set the call volume and background sound corresponding to each of the multiple call scenarios. Before the electronic device 100 makes a call with the other electronic device 100, it can identify the multiple call scenarios it is currently in. The user can select a call scenario from the multiple call scenarios. During the call, the electronic device 100 can use the call volume corresponding to the call scenario selected by the user to play the sound collected by the other electronic device 100.

[0132] Of course, if the electronic device 100 only recognizes a current call scene before talking with the opposite device, there is no need for user selection, and the call volume corresponding to the call scene can be directly used to play the sound collected by the opposite device.

[0133] In some implementations, the current call scenario of the electronic device 100 can be determined based on any one or more of the following factors: the environment of the local user, the status of the local user, the relationship between the other user and the local user, the current time, etc.

[0134] The above-mentioned environment may include but is not limited to: the current location of the local user, the current size of the space, the current noise level, etc. The above-mentioned user status may include but is not limited to: the user's current action and emotion, etc.

[0135] The following describes in detail some of the various call scenarios preset in the electronic device 100.

[0136] For example, based on the user's environment, the call scenarios pre-set on the electronic device 100 may include, but are not limited to, subway scenarios, highway scenarios, cinema scenarios, home scenarios, underwater scenarios, mountaintop scenarios, and the like. The electronic device 100 may obtain its current location information using Global Positioning System (GPS) technology to identify the current call scenario. Specifically, when the user is on the subway or waiting for the subway, the electronic device 100 may identify the current call scenario as a subway scenario. When the user is walking on a highway or waiting on a highway, the electronic device 100 may identify the current call scenario as a highway scenario. When the user is in a movie theater, the electronic device 100 may identify the current call scenario as a theater scenario. When the user is inside a house, the electronic device 100 may identify the current call scenario as a home scenario. When the user is in water, the electronic device 100 may identify the current call scenario as an underwater scenario. When the user is at the top of a mountain, the electronic device 100 may identify the current call scenario as a mountaintop scenario.

[0137] Based on the user's status, the call scenarios preset by the electronic device 100 may include, but are not limited to, work scenarios, driving scenarios, exercise scenarios, fatigue scenarios, silent scenarios, and sleep scenarios. When the user is working, such as when the current time is working hours, the electronic device 100 may identify the current call scenario as a work scenario. When the user is driving, such as when the electronic device 100 determines the current location is inside a vehicle and establishes a communication connection with the vehicle, the electronic device 100 may identify the current call scenario as a driving scenario. When the user is exercising, such as when the electronic device 100 establishes a communication connection with a wearable device worn by the user and detects the user's exercise via an inertial sensor, the electronic device 100 may identify the current call scenario as an exercise scenario. When the user has finished work or exercise, such as when the current time is non-working hours, the electronic device 100 may identify the current call scenario as a fatigue scenario. When the user does not want to answer the call but is forced to do so for some reason, such as when the electronic device 100 has not received an answer request from the user for a long period of time, the electronic device 100 may identify the current call scenario as a silent scenario. When the user is in a sleeping state, for example, the electronic device 100 detects through a sensor that the user is in a sleeping state, the electronic device 100 can recognize that the current call scene is a sleeping scene.

[0138] Based on the relationship between the other user and the local user, the call scenario set by the electronic device 100 may include, but is not limited to, a colleague scenario, a family scenario, a friend scenario, and so on. When the other user and the local user are colleagues, the electronic device 100 may identify the current call scenario as a colleague scenario. When the other user and the local user are family, the electronic device 100 may identify the current call scenario as a family scenario. When the other user and the local user are friends, the electronic device 100 may identify the current call scenario as a friend scenario.

[0139] According to the current time, the call scene set by the electronic device 100 may include but is not limited to: a late night scene. If the current time is between 11 pm and 3 am, the electronic device 100 may identify the current call scene as a late night scene.

[0140] It is worth noting that the call scenarios introduced above are only exemplary. In the embodiments of the present application, more or fewer call scenarios may be included, and there is no limitation on this.

[0141] Refer to Figure 2, which is a flowchart of the method for adjusting call volume provided in Example 1 of the present application.

[0142] The method provided in Example 1 specifically includes:

[0143] S201: The electronic device 100 receives a call request sent by a peer electronic device, or the electronic device 100 receives a user operation for requesting a call with the peer electronic device.

[0144] In a possible implementation, the electronic device 100 may configure the call scenario before the call.

[0145] In some implementations, the electronic device 100 presets multiple call scenarios and default call volumes corresponding to the multiple call scenarios. Furthermore, the multiple call scenarios preset by the electronic device 100 are matched with preset background sounds.

[0146] The electronic device 100 has preset default call volumes corresponding to various call scenarios before leaving the factory. The default call volumes are set by the developer.

[0147] In some implementations, the electronic device 100 can set multiple call scenarios and the default call volumes corresponding to the multiple call scenarios in the system's own application (such as a settings application), or can set multiple call scenarios and the default call volumes corresponding to the multiple call scenarios in a third-party application (such as an instant messaging application).

[0148] The aforementioned call scenarios may include, but are not limited to, subway, highway, cinema, home, underwater, mountaintop, work, driving, exercise, fatigue, silent, sleeping, colleagues, family, friends, and late-night calls. For a detailed introduction to call scenarios, please refer to the above content and will not be elaborated here.

[0149] In a possible implementation, the call scene can also be added and set by the user, and a corresponding call volume can be set.

[0150] In some implementations, the electronic device 100 may preset corresponding default call volumes for various call scenarios.

[0151] Specifically, the default call volume corresponding to the call scenario can be obtained in the following ways:

[0152] 1. The server of the electronic device 100 can collect a large amount of noise in real scenarios and conduct multiple call experiments using call volumes of various levels to determine that the call content at a certain call volume is the clearest. This call volume is then the default call volume for calls in this call scenario.

[0153] 2. A large number of experimenters conduct calls at different call volumes in a certain call scenario, and the experimenters rate the comfort of different call volumes in a certain call scenario. The server of the electronic device 100 inputs a large amount of the comfort rating data and determines that the call volume with the highest comfort in a certain call scenario is the default call volume.

[0154] In the embodiment of the present application, there is no limitation on the method for obtaining the default call volume, and more methods may be included.

[0155] Optionally, after the electronic device 100 obtains the call scenario and the default call volume corresponding to the call scenario, the user can adjust the volume corresponding to the call scenario according to their needs. Specifically, upon receiving an operation for adjusting the call volume corresponding to a third call scenario, the electronic device 100 adjusts the call volume corresponding to the third call scenario from the default call volume to the first call volume.

[0156] In some implementations, the user can view various call scenarios and their corresponding default call volumes. If the user is dissatisfied with the default call volume, the electronic device 100 can adjust the call volume corresponding to the third call scenario from the default call volume to the first call volume based on the user's needs. The third call scenario can refer to a single call scenario from multiple call scenarios, or can refer to multiple call scenarios from the multiple call scenarios.

[0157] It is worth noting that the electronic device 100 can also store background sounds corresponding to a variety of call scenarios. The background sounds can be used to realistically simulate the noise in various call scenarios. The background sounds can be set by the electronic device 100 according to the characteristics of the call scenario. For example, the background sounds corresponding to the subway scene can be noises collected in a real subway scene, including the noise emitted by the subway, the noise of the crowd, and the sound of subway announcements, etc. The background sounds can be played when the electronic device 100 adjusts the call volume corresponding to the third call scenario, so that the user can adjust the call volume according to the background sounds instead of adjusting it arbitrarily.

[0158] In some implementations, the background sound may also be played by the electronic device 100 during the call and / or by the other party's electronic device.

[0159] In some implementations, the first call volume corresponding to the third call scenario can be stored in the electronic device 100 or in a server of the electronic device 100. That is, if a user owns multiple electronic devices 100, the other electronic devices 100 can simultaneously set the first call volume corresponding to the third call scenario after logging into the user account of the local electronic device 100. This eliminates the need for the user to adjust the call volume multiple times.

[0160] The following describes in detail the adjustment of the call volume corresponding to the third call scenario from the default call volume to the first call volume in conjunction with the relevant user interface.

[0161] Referring to FIG3A , FIG3A illustrates an exemplary user interface 200. User interface 200 may be a user interface within the system's built-in settings application or a user interface within a third-party application. In user interface 200, the user can view different call scenarios and their corresponding volume levels, and can also adjust the different call scenarios and their corresponding volume levels.

[0162] The user interface 200 includes but is not limited to: a call scene name 201, a volume adjustment control 202, a restore default control 203, a save configuration control 204, and the like.

[0163] 3A , the call scene names 201 include subway scene, highway scene, noisy scene, quiet scene, driving scene, theater scene, work scene, and fatigue scene, etc. In the embodiment of the present application, the call scene names are only for illustrative purposes, and more or fewer call scenes may be included.

[0164] As shown in FIG3A , the maximum volume of electronic device 100 is 100%, the minimum volume is 0%, and the default call volume corresponding to the subway scene is 80%. In response to a left swipe on volume adjustment control 202A by the user, electronic device 100 can adjust the call volume corresponding to the subway scene to 70% of the first call volume. In response to a right swipe on volume adjustment control 202A by the user, electronic device 100 can adjust the call volume corresponding to the subway scene to 90% of the first call volume. When the user performs the left or right swipe operations, electronic device 100 can simultaneously play background sound effects corresponding to the subway scene.

[0165] It should be noted that if the electronic device 100 adjusts the call volume corresponding to the subway scene from the default call volume to the first call volume in response to the user's left or right swipe operation on the volume adjustment control 202A, and then responds to the user's click operation on the save configuration control 204, the electronic device 100 can save the adjusted first call volume. When the electronic device 100 subsequently re-enters the user interface 200, the volume displayed by the volume adjustment control 202A is the first call volume corresponding to the subway scene.

[0166] If the electronic device 100 adjusts the call volume corresponding to the subway scene from the default call volume to the first call volume in response to the user's left or right swipe operation on the volume adjustment control 202A, and then responds to the user's click operation on the restore default control 203, it can be considered that the adjustment is not successful, and the call volume corresponding to the subway scene in the electronic device 100 remains at the default call volume. When the electronic device 100 subsequently re-enters the user interface 200, the volume displayed by the volume adjustment control 202A is still the default call volume corresponding to the subway scene.

[0167] The user interface 200 described above is based on the common adjustment of the call volume of the three call modes in the same call scene. The following describes a user interface for adjusting the call volume of the three call modes in the same call scene separately.

[0168] 3B , the user interface 210 includes but is not limited to: a call scenario name 211, a detail control 212, a restore default control 213, and a save configuration control 214. The electronic device 100 may enter the user interface 220 in response to a user clicking on the detail control 212A.

[0169] As shown in FIG3C , the user interface 220 includes three call mode names 221 and corresponding volume adjustment controls 222. The electronic device 100 can respond to the user's sliding operation on the volume adjustment control 222A, the volume adjustment control 222B, and the volume adjustment control 222C to adjust the call volume of the handset mode, the headset mode, and the hands-free mode in the subway scene from the default call volume to the first call volume. For a detailed introduction to the sliding operation, please refer to the relevant description of the sliding operation in FIG3A above and will not be repeated here.

[0170] When electronic device 100 receives a call request from a peer electronic device 100, it is considered the recipient of the call. When electronic device 100 receives a user operation requesting a call with a peer electronic device 100, it is considered the initiator of the call. The user of the peer electronic device 100 may or may not be a contact of the user.

[0171] In some implementations, electronic device 100 may receive a call request sent by a peer electronic device 100. The call request may include a call type identifier and a number identifier, among others. Call types may include, but are not limited to, voice calls and video calls. The number identifier is used by electronic device 100 to identify the phone number of the peer electronic device 100, thereby determining the user of the peer electronic device 100, i.e., the peer user.

[0172] In some implementations, the electronic device 100 may receive a user operation for requesting a call with the other electronic device 100 .

[0173] Referring to Figure 4A , FIG4A illustrates an exemplary user interface 300 for the system's built-in phone application. User interface 300 includes a recent call bar 301, a dial pad 302, and a call control 303. The electronic device 100 can select a desired number by selecting an item from the recent call bar 301 or directly using the dial pad 302. In response to a user clicking the call control 303, the electronic device 100 can identify the number identifier and request a call with the other electronic device 100 with the number identifier.

[0174] In the embodiment of the present application, the user operation for requesting a call with the other electronic device 100 is not limited to the above-mentioned click operation on the dial control 303, but may also include touch operation, voice command, gesture command, etc., which is not limited to this.

[0175] S202: The electronic device 100 identifies the current call scenario.

[0176] In some implementations, the electronic device 100 can identify the current call scenario based on the electronic device 100's current location, current time, whether it is connected to a wearable electronic device, and speed captured by sensors. Specifically, when the electronic device 100 is connected to a wearable device, the wearable device obtains relevant data about the current user through sensors and sends it to the electronic device 100. The electronic device 100 can determine that the current user is in motion based on the relevant data, and further determine that the current call scenario is a motion scenario.

[0177] In one possible implementation, the electronic device 100 may also use images captured by the camera to assist in identifying the call scene. For example, if the electronic device 100 analyzes the captured image and finds that it contains a subway, the electronic device 100 may determine that the current call scene is a subway scene.

[0178] In another possible implementation, the electronic device 100 can also determine the size of the current space based on GPS technology, Beidou navigation technology, and echolocation, and then assist in determining the current call scene. For example, the electronic device determines that the distance of obstacles in 360° around the current electronic device is less than 50cm by echolocation, and then determines that the current call scene may be an elevator scene, a subway scene, or a bus scene. Then the electronic device 100 can obtain the acceleration sensor that the current electronic device 100 has acceleration in the vertical direction (i.e., the direction perpendicular to the ground plane), and there is no acceleration in the horizontal direction (i.e., the direction parallel to the ground plane), and thus it can be determined that the current call scene is an elevator scene.

[0179] In another possible implementation, the electronic device may also combine factors such as signal strength and interference to assist in identifying the current call scenario.

[0180] Since call scenes can be presented from different angles, the electronic device 100 may recognize only one or multiple call scenes. When only one call scene is recognized, the options for multiple call scenes are not displayed in S203 below, and the user does not need to select one. Instead, the call scene is directly used.

[0181] For example, the current location of the electronic device 100 is an office building, and the current time is 3:00 p.m. on Monday. The electronic device 100 recognizes that the current call scene can be a work scene, a fatigue scene, a quiet scene, a sleep scene, etc.

[0182] In one possible implementation, in step S201, if the electronic device 100 receives a call request sent by the other electronic device 100 in the system application, or receives a user operation for requesting a call with the other electronic device 100 in the system application, then the electronic device 100 can directly identify the current call scenario by the system.

[0183] In another possible implementation, in step S201, if the electronic device 100 receives a call request sent by the opposite electronic device 100 in the third-party application, or receives a user operation for requesting a call with the opposite electronic device 100 in the third-party application, there are two ways to identify the current call scenario:

[0184] 1. The third-party application requests the system of the electronic device 100 to identify the current call scene. The system of the electronic device 100 identifies the current call scene and then sends relevant information of the identified call scene to the third-party application.

[0185] 2. The third-party application directly identifies the current call scenario.

[0186] S203. The electronic device 100 displays an incoming call interface, which includes options for multiple call scenarios identified by the electronic device 100; or displays an outgoing call interface, which includes options for multiple call scenarios identified by the electronic device 100.

[0187] In some implementations, the incoming call interface may refer to an answering interface that allows a user to select a call scenario from multiple call scenario options. The outgoing call interface may refer to a calling interface that allows a user to select a call scenario from multiple call scenario options.

[0188] Of course, the call scene options displayed in the incoming call interface or the outgoing call interface may include options of all call scenes set in the electronic device 100, or may be options of multiple call scenes identified in step S202.

[0189] When the electronic device 100 is located in different locations, the call scene options displayed on the incoming call interface or the outgoing call interface may be different. When the electronic device 100 is calling a different electronic device 100, the call scene options displayed on the incoming call interface or the outgoing call interface may also be different. The following describes the incoming call interface and the outgoing call interface in step S203 in conjunction with the relevant user interfaces.

[0190] Referring to Figure 5A, Figure 5A exemplifies an incoming call interface in a system application. When the electronic device 100 receives a call request sent by the other electronic device 100, the electronic device 100 identifies the current call scene. The electronic device 100 can display a user interface 400. The user interface 400 includes caller information 401, call scene options 402, and a hang-up control 403. The caller is a contact, and the caller information includes a contact avatar, contact name, contact group, contact number, and number location, etc. The call scene options 402 include a subway scene option 402A, a work scene option 402B, a quiet scene option 402C, a sleep scene option 402D, and an answer control 402E. The information displayed by the call scene option 402 indicates that the call scenes identified by the electronic device 100 in the current situation include: subway scene, work scene, quiet scene, and sleep scene.

[0191] In some implementations, the user interface 400 shown in FIG5A may be referred to as a first interface. In the embodiment of the present application, the user interface 400 is merely an example, and the user interface 400 may also include more or less content.

[0192] Referring to Figure 4B, Figure 4B exemplifies the outgoing call interface in the system application. In response to the user's click operation on the dial control 303 in Figure 4A, the electronic device 100 can display a user interface 410. The user interface 410 includes caller information 411, a call scene prompt bar 412, call scene options 413, and the like. Among them, the caller is a contact, and the caller information includes the contact avatar, contact name, contact group, contact number, and number location, etc. The call scene prompt bar 412 is used to prompt the user to select a specific call scene to make a call. The call scene options 413 include a subway scene option 413A, a work scene option 413B, a quiet scene option 413C, and a sleep scene option 413D.

[0193] In some implementations, the click operation of the dial control 303 in FIG4A may be referred to as an operation of the user making a call.

[0194] In some implementations, the user interface 410 shown in FIG4B may be referred to as a third interface. In the embodiment of the present application, the user interface 400 is merely an example, and the user interface 400 may also include more or less content.

[0195] S204: The electronic device 100 detects a user operation of selecting a target call scenario.

[0196] In some implementations, the user operation may refer to an operation in which the user selects a target call scenario from multiple call scenarios when the electronic device 100 displays the incoming call interface or the outgoing call interface in step S203. The user operation may include, but is not limited to, a click operation, a touch operation, a slide operation, a voice command, and the like.

[0197] In some implementations, the user can select a specific call scenario based on subjective factors. For example, the call scenarios displayed by the electronic device 100 in the incoming call interface or the outgoing call interface include work scenario, fatigue scenario, quiet scenario, and sleep scenario. If the current user is working or determines through the incoming call information that the content of the call may be work-related, the user can choose the work scenario to make the call; if the current user is at the end of work or the user subjectively resists the call from the caller but objectively should answer the call, the user can choose the fatigue scenario. In the embodiment of the present application, the above is only an example.

[0198] In some implementations, the call scenario selected by the user may be referred to as a first call scenario, and the call scenarios other than the first call scenario among the multiple call scenarios identified by the electronic device 100 may be referred to as second call scenarios.

[0199] For example, the user operation may be a click on subway scene option 402A in user interface 400, or a swipe from subway scene option 402A to answer call control 402E. Alternatively, the user operation may be a click with a pointer on subway scene option 413A in user interface 410. This is not a limitation.

[0200] S205 . After responding to the user operation of selecting the target call scene, the electronic device 100 plays a sound at a call volume corresponding to the target call scene.

[0201] In some implementations, if the electronic device 100 adjusts the call volume corresponding to the target call scenario from the default call volume to the first call volume, that is, the third call scenario in the above steps includes the target call scenario, then the electronic device 100 answers the call at the first call volume corresponding to the target call scenario, or makes a call at the first call volume corresponding to the target call scenario.

[0202] If the electronic device 100 does not adjust the call volume corresponding to the target call scenario from the default call volume to the first call volume, that is, the third call scenario in the above step does not include the target call scenario, the electronic device 100 answers the call at the default call volume corresponding to the target call scenario, or makes a call at the default call volume corresponding to the target call scenario.

[0203] It is worth noting that when the electronic device 100 acts as the initiator of the call, after the electronic device 100 responds to the user operation of selecting the target call scene, it also needs to receive the signal of the call request initiated by the electronic device at the other end before it can play the sound collected by the electronic device at the other end at the call volume corresponding to the target call scene.

[0204] The following describes step S205 in conjunction with related interfaces.

[0205] After electronic device 100 responds to a click on subway scene option 402A in user interface 400, user interface 500 may be displayed as shown in FIG5B . User interface 500 exemplarily illustrates a scenario in which electronic device 100 is in a call with a peer electronic device. User interface 500 includes, but is not limited to, call duration 501, call scene reminder information 502, and a hang-up control 503. Call duration 501 displays the current call duration. Call scene reminder information 502 reminds the user that the current call scene is a subway scene.

[0206] After electronic device 100 responds to a click on the subway scene option 413A in user interface 410, it may display user interface 510 as shown in FIG4C . User interface 510 illustrates a scenario in which electronic device 100 is waiting for the other electronic device 100 to answer the call. User interface 510 is also an outgoing call interface. User interface 510 may include, but is not limited to, a call prompt 511, a call scene reminder 512, and a hang-up control 513. Call prompt 511 notifies the user that the current call has not been connected and is waiting for the other electronic device 100 to answer. Call scene reminder 512 reminds the user that the current call scene is a subway scene. After the other electronic device 100 answers the current call, electronic device 100 may display user interface 500 as shown in FIG5B . It is worth noting that if electronic device 100 is the initiator of a call, electronic device 100 may initiate a call request to the other electronic device in response to a user click on the dial control 303 in user interface 300. Electronic device 100 may also initiate a call request to the other electronic device 100 while identifying the current call scene. The electronic device 100 may also initiate a call request to the other electronic device after identifying the current call scenario, i.e., when the electronic device 100 displays the user interface 410. The electronic device 100 may also send a call request to the other electronic device after the user selects the target call scenario, i.e., when the electronic device 100 displays the user interface 510. This is not limited in the embodiments of the present application.

[0207] In some implementations, the user interface 500 shown in FIG5B may be referred to as the second interface. The call scene reminder information 502 may be referred to as the first prompt information. In the embodiment of the present application, the user interface 500 is merely an example, and the user interface 500 may include more or less content.

[0208] In some implementations, the user interface 500 shown in FIG4C may be referred to as the fourth interface. The call scene reminder information 512 may be referred to as the second prompt information. In the embodiment of the present application, the user interface 500 is merely illustrative, and the user interface 500 may include more or less content.

[0209] S206: The electronic device 100 sends the background sound corresponding to the target call scenario to the opposite electronic device, and the background sound is played by the opposite electronic device.

[0210] In some implementations, the electronic device 100 can send the background sound corresponding to the target call scene to the opposite electronic device, so that the opposite electronic device also plays the background sound. For example, when the target call scene is a subway scene, the opposite electronic device can obtain the background sound effects corresponding to the subway scene sent by the electronic device 100, such as subway noise, etc. When the opposite user hears the background sound effects, he / she believes that the local user is in a subway environment with loud noise and poor call experience. The opposite user can hang up the phone and wait until the local user is in an environment with less noise before establishing a call connection. In this way, the opposite user can be informed of the call scene of the local user and can shorten the call time of the local user if it is inconvenient for the user to answer the call, thus providing a good user experience.

[0211] In some implementations, while a user is talking to a remote user, the electronic device 100 can play audio at the volume corresponding to the target call scenario, and can also play background sound corresponding to the target call scenario. In one possible implementation, each call scenario set by the electronic device 100 can also be configured with corresponding background sound. This ensures that when others besides the user may hear the user's call, they will mostly hear the background sound effects rather than the conversation content, thereby protecting the user's privacy.

[0212] In one possible implementation, electronic device 100 and a peer electronic device simultaneously play background sound effects corresponding to the target call scenario. Specifically, after determining the first call scenario, the electronic device sends the background sound data corresponding to the first call scenario to the peer electronic device, allowing the peer electronic device to simultaneously obtain the local user's voice data and background sound data, and simultaneously play the local user's speech and the background sound corresponding to the first call scenario.

[0213] In one possible implementation, the electronic device 100 can also play sound in a directional manner during a call between a user and a remote user. Thus, in handset listening mode, the electronic device 100 can play sound in a direction close to the user's ear, thereby preventing sound leakage and protecting user privacy.

[0214] In one possible implementation, when a user is talking to a remote user, the electronic device 100 can, upon receiving audio data sent by the remote electronic device, perform voice modification on the audio data and then play the modified audio. This ensures that only the user knows the identity of the remote user, and others who may overhear the user's conversation cannot determine the identity of the remote user, thereby protecting the user's privacy.

[0215] In one possible implementation, while a user is talking to a remote user, the electronic device 100 may send a prompt to the remote electronic device, prompting the remote user to lower or raise the volume. Specifically, the prompt may be played as a voice message to the remote user. For example, the voice message may read, "The current speaking volume is detected to be too high. Please lower your volume." Alternatively, the voice message may read, "The other party is detected to be in an environment that may easily leak privacy. Please lower your volume."

[0216] As can be seen from the above-described first embodiment, the electronic device 100 can select a target call scenario from multiple call scenarios identified by the electronic device 100 based on the user's personal preferences, thereby improving the interactivity between the user and the mobile phone. Furthermore, the user can directly adjust the call volume to the call volume corresponding to the target call scenario by answering or making a call, simplifying the user's call volume adjustment operations and improving the user experience. Furthermore, the electronic device 100 can play background sound to further prevent privacy leaks, and the other end's electronic device can play background sound to improve the call experience of the local user.

[0217] Example 2:

[0218] In the second embodiment, the electronic device 100 can also be pre-set with multiple call scenarios, and can also pre-set the call volume and background sound corresponding to each of the multiple call scenarios. Before calling with the other electronic device, the electronic device 100 determines whether the other user is the target user. If the other user is the target user, the electronic device 100 obtains the user information of the other user, matches the target call scenario based on the user information of the other user, and then plays the sound collected by the other electronic device at the volume corresponding to the target call scenario, and plays the background sound corresponding to the target call scenario.

[0219] The above user information may include any of the following: the relationship between the opposite user and the local user, the call scenario set for the opposite user, etc.

[0220] Refer to FIG6 , which is a flowchart of a method for adjusting call volume provided in Embodiment 2 of the present application.

[0221] The method provided in Example 2 specifically includes:

[0222] S601. The electronic device 100 sets relevant user information for a first user.

[0223] For the relevant description about the electronic device 100 presetting multiple call scenarios and the default call volumes corresponding to the multiple call scenarios, and adjusting the call volumes corresponding to the multiple call scenarios to the first call volume according to user needs, please refer to the relevant description in S201 and will not be repeated here.

[0224] In some implementations, the electronic device 100 may also set up a call scenario related to the other user. The first user may be a contact. When the other user is a contact of the local user, the electronic device 100 may set up a corresponding call scenario for the contact.

[0225] The following describes how the electronic device 100 sets relevant user information for the first user in conjunction with the relevant user interface.

[0226] Referring to Figure 7A , an exemplary user interface 700 is shown. User interface 700 may be a user interface within the system's built-in contacts application. User interface 700 may include, but is not limited to, a contact name 701, a contact group 702, a contact phone number 703, a call scenario selection box 704, and a selection control 705. The contact group can be used to indicate the relationship between the peer user and the local user. For example, contact name 701 is "Xiao Ming" and contact group 702 is "Family."

[0227] As shown in Figure 7A, the prompt information displayed in the call scene selection box 704 is "To be selected". The electronic device 100 can respond to the user's click operation on the selection control 705, set the corresponding call scene for "Xiao Ming", and display the user interface 710 as shown in Figure 7B. The user interface 710 includes a variety of call scene options. The electronic device 100 can respond to the user's click operation on the subway scene option 711, set the corresponding call scene for "Xiao Ming" as the subway scene, and display the user interface 720 as shown in Figure 7C. The prompt information in the call scene selection box 721 included in the user interface 720 is "Subway Scene", indicating that the electronic device 100 has completed setting the call scene for the contact "Xiao Ming".

[0228] In the embodiment of the present application, the user interfaces shown in FIG. 7A to FIG. 7C are merely exemplary and are not limiting.

[0229] In some implementations, the electronic device 100 can also assign multiple contacts to a specific contact group and set a specific call scenario for the contact group. That is, peer users in the same group can correspond to the same call scenario. For example, if the electronic device 100 assigns the call scenario to the "Family" group in the contact list, then all contacts in the "Family" group will correspond to the same call scenario.

[0230] S602: The electronic device 100 receives a call request sent by a peer electronic device, or the electronic device 100 receives a user operation for requesting a call with the peer electronic device.

[0231] For a detailed description of S602, please refer to the above-mentioned introduction to S201, which will not be repeated here.

[0232] S603: The electronic device 100 determines whether the opposite user is a target user.

[0233] In some implementations, the target user may include a contact stored in the electronic device 100. Specifically, the electronic device 100 may determine whether the opposite-end user is the target user based on whether the number identifier in the call request sent by the opposite-end electronic device is consistent with the number identifier of the contact stored in the electronic device 100; the electronic device 100 may also determine whether the opposite-end user is the target user based on whether the number identifier identified after receiving a user operation for requesting a call with the opposite-end electronic device is consistent with the number identifier of the contact stored in the electronic device 100.

[0234] In addition to contacts, the target user can also refer to a user on the other end with a specific identifier. Specifically, the electronic device 100 can identify the identifier of the incoming or outgoing number through the number identification service provided by the relevant application or the identification of the number by other users of other electronic devices manufactured by the same manufacturer as the local electronic device 100, and make a note of the incoming or outgoing number. For example, if the incoming or outgoing number is the customer service phone number of the express application, the electronic device 100 can note the number as "express"; if the incoming number is an advertising and promotion call, the electronic device 100 can note the number as "advertisement"; if the incoming number is a malicious harassment call, the electronic device 100 can note the number as "harassment call". Not limited to the above-mentioned number annotation methods, in the embodiment of the present application, there can also be more or fewer number annotation methods.

[0235] In the embodiment of the present application, the target persons are not limited to the two types mentioned above, and more or fewer types of target persons may be included, which is not limited to this.

[0236] S604: If the opposite user is the target user, the electronic device 100 obtains user information of the opposite user.

[0237] In some implementations, the electronic device 100 can determine whether the peer user is a target user by using the relevant method in S605. The target user may include but is not limited to: a contact stored in the electronic device 100, a peer user with a special identifier, and the like.

[0238] If the other party user is a contact stored in the electronic device 100, the electronic device 100 can determine the contact number of the current call through the number identifier, and then obtain the other party user information, i.e., contact information, based on the contact number. The above contact information includes, but is not limited to: the relationship between the contact and the local user, the call scenario set for the contact, the contact name, the contact notes, etc.

[0239] If the other party user is a user with a special identifier, the electronic device 100 can determine the number of the other party user of the current call through the number identifier, and then obtain the other party user information based on the number of the other party user. The other party user information includes but is not limited to: the call scene set for the other party user, number notes, etc.

[0240] S605: The electronic device 100 matches the target call scenario according to the user information and displays an incoming call interface or an outgoing call interface.

[0241] In some implementations, matching target call scenarios based on user information may include the following methods:

[0242] 1. Match the target call scenario based on the call scenario set for the contact.

[0243] The electronic device 100 can set a corresponding call scene for the contact in response to the user operation. That is, different contacts can correspond to different call scenes. For a detailed introduction to the call scene corresponding to the contact set by the electronic device 100, please refer to the relevant description in the above step S603, which will not be repeated here. In this case, after the electronic device 100 determines that the opposite user is a contact among the target users through the number identification, it can obtain user information, which may include the call scene set for the contact, and then match the target call scene based on the user information.

[0244] 2. Match the target call scenario based on the call scenario set for the contact group.

[0245] The electronic device 100 can set corresponding call scenarios for contact groups in response to user operations. The contact group can refer to the relationship between the opposite user and the local user. For a detailed introduction to the call scenarios corresponding to the contact groups set by the electronic device 100, please refer to the relevant description in the above step S603, which will not be repeated here. In this scenario, after the electronic device 100 determines that the opposite user is a contact of the target user through the number identification, it can obtain user information, which may include the relationship between the opposite user and the local user, and then match the target call scenario based on the user information.

[0246] 3. Match the target call scenario based on the number notes.

[0247] The electronic device 100 can set a corresponding call scenario for the number annotation. For example, if the electronic device 100 annotates the number as "express delivery," the call content may involve the user's private information. In this case, the electronic device 100 sets the call scenario corresponding to the number annotation as a privacy scenario. For another example, if the electronic device 100 annotates the number as "advertisement," the electronic device 100 sets the scenario corresponding to the number annotation as a "fatigue scenario." In this scenario, the electronic device 100 can match the target call scenario based on the number annotation.

[0248] In the embodiment of the present application, it is not limited to the above-mentioned method, and may also include more or fewer methods of determining the target call scenario based on the incoming call information, which is not limited to this.

[0249] In some implementations, after the electronic device 100 determines the target call scenario, it may display an incoming call interface or an outgoing call interface. The incoming call interface may be a user interface used by the electronic device 100 to receive call requests when the electronic device 100 is acting as a call receiver. The outgoing call interface may be a user interface used by the electronic device 100 to initiate a call request when the electronic device 100 is acting as a call initiator.

[0250] The following describes the incoming call interface and the outgoing call interface displayed in S606 in conjunction with related interfaces.

[0251] Referring to Figure 8A, Figure 8A exemplifies the incoming call interface in the system application. After the electronic device 100 receives the call request sent by the opposite electronic device 100, the electronic device 100 can determine the target call scene according to the number identifier in the call request. The method of matching the target call scene can refer to the above description and will not be repeated here. The electronic device 100 can display a user interface 800. The user interface 800 includes caller information 801, call scene prompt information 802, answering control 803, and hang up control 804. The call scene prompt information 802 can display the text message "The current call scene is the subway scene", which means that the target call scene matched by the electronic device 100 based on the user information is the subway scene.

[0252] Referring to Figure 8B , Figure 8B illustrates an exemplary outgoing call interface within a system application. In response to a user clicking on the dial control 303 in Figure 4A , the electronic device 100 may display a user interface 810 . The electronic device 100 may determine a target call scenario based on the identifier of the number entered by the user in the user interface 300 . The method for matching the target call scenario can be found in the above description and is not further elaborated here. User interface 810 includes caller information 811 and a call scenario prompt bar 812 , wherein the call scenario prompt bar 812 includes prompt information 812A, an OK control 812B, and a cancel control 812C. Prompt information 812A may display the text message "Detected that the current user is adapted for the subway scenario. Do you want to apply?" This indicates that the target call scenario matched by the electronic device 100 based on the user information is the subway scenario. In response to a user clicking on the OK control 812B, the electronic device 100 may determine that the currently used call scenario is the subway scenario and display the user interface 820 shown in Figure 8C . User interface 820 illustrates a scenario where electronic device 100 is waiting for a call from a remote electronic device 100. User interface 820 may include, but is not limited to, call prompt information 821, call scenario reminder information 822, and a hang-up control 823. Call prompt information 821 reminds the user that the current call has not been connected and that the user is waiting for the remote electronic device 100 to answer. Call scenario reminder information 822 reminds the user that the current call scenario is a subway train.

[0253] S606: The electronic device 100 plays sound at a call volume corresponding to the target call scenario.

[0254] In some implementations, after matching the target call scenario, the electronic device 100 can play the sound collected by the other electronic device at the call volume corresponding to the target call scenario.

[0255] If the electronic device 100 adjusts the call volume corresponding to the target call scenario from the default call volume to the first call volume, that is, the third call scenario in the above step S602 includes the target call scenario, then the electronic device 100 answers the call at the first call volume corresponding to the target call scenario, or makes a call at the first call volume corresponding to the target call scenario.

[0256] If the electronic device 100 does not adjust the call volume corresponding to the target call scenario from the default call volume to the first call volume, that is, the third call scenario in the above step S602 does not include the target call scenario, the electronic device 100 answers the call at the default call volume corresponding to the target call scenario, or makes a call at the default call volume corresponding to the target call scenario.

[0257] It should be noted that when the electronic device 100 serves as the initiator of a call, after the electronic device 100 responds to the user's operation to determine the call application for the target call scenario, it also needs to receive a signal from the other electronic device 100 that the call request initiated by the electronic device 100 is received before it can play the sound collected by the other electronic device at the call volume corresponding to the target call scenario.

[0258] The following describes step S606 in conjunction with related interfaces.

[0259] After electronic device 100 responds to a click on answer control 803 in user interface 800, it may display user interface 900 as shown in FIG9 . User interface 900 exemplarily illustrates a scenario in which electronic device 100 is in a call with a peer electronic device. User interface 900 includes, but is not limited to, call duration 901, call scenario reminder information 902, and a hang-up control 903. Call duration 901 displays the current call duration. Call scenario reminder information 902 reminds the user that the current call scenario is a subway call.

[0260] When the electronic device 100 displays the user interface 820 , after the opposite electronic device receives the call request sent by the electronic device 100 , the electronic device 100 receives a receiving signal sent by the opposite electronic device and can switch to displaying the user interface 900 .

[0261] It is worth noting that, when the electronic device 100 serves as the initiator of the call, the electronic device 100 can initiate a call request to the electronic device at the other end after responding to the user's click operation on the dial control 303 in the user interface 300. The electronic device 100 can also initiate a call request to the electronic device at the other end during the process of matching the target call scene. The electronic device 100 can also initiate a call request to the electronic device at the other end after matching the target call scene, that is, when the electronic device 100 displays the user interface 810. The electronic device 100 can also send a call request to the electronic device at the other end after the user determines to apply the target call scene call, that is, when the electronic device 100 displays the user interface 820. In the embodiments of the present application, this is not limited.

[0262] In one possible implementation, after step S605, when the opposite user is not the target user, that is, the opposite user has no corresponding user information, has not added a relationship with the local user, and has not set a corresponding call scene, the electronic device 100 can directly use the method of adjusting the call volume provided in Example 1 to play the sound collected by the opposite electronic device, or play the sound collected by the opposite electronic device according to the call volume corresponding to the call scene applied to the historical call of the opposite user, or play the sound collected by the opposite electronic device according to the volume provided by the current audio device of the electronic device 100.

[0263] In one possible implementation, the method for adjusting the call volume can be applied not only to one-to-one call scenarios, but also to multi-person call scenarios. When the electronic device 100 determines the call scenario based on the user information of the opposite user, it is also necessary to determine the priority of multiple opposite users and determine the call scenario based on the user information of the opposite user with the highest priority.

[0264] For example, electronic device 100 is connected to a multi-person call, in which there are two other users, namely contact A and contact B. Contact A is the top contact in the contact list of electronic device 100, and the call scene of contact A is set to the intimate scene. Contact B is a non-top contact in the contact list of electronic device 100, and the call scene of contact B is set to the work scene. When connecting to the multi-person call, electronic device 100 determines that the priority of contact A is higher than the priority of contact B. Then, electronic device 100 determines that the call scene of the multi-person call is the intimate scene based on the user information of contact A, and adjusts the call volume of electronic device 100 when connecting to the multi-person call to the call volume corresponding to the intimate scene.

[0265] The priority is set in the following ways:

[0266] 1. The priority of the contact groups set in the electronic device 100. For example, the priority of contacts in the family group is higher than that of contacts in the friends group, and the priority of contacts in the friends group is higher than that of contacts in the colleagues group.

[0267] 2. The priority of the contact notes set in the electronic device 100. For example, contacts with notes have a higher priority than contacts without notes. Notes here refer to nicknames, nicknames, etc. set by the user in addition to the contact name.

[0268] 3. The priority of the location of the number of the contact making the call. For example, the priority of the contact whose number is in the same location as the user is using is higher than the priority of the contact whose number is in a different location than the user is using.

[0269] Not limited to the above-mentioned methods, the embodiment of the present application may also have more or fewer settings for the priority of contacts.

[0270] In one possible implementation, the current location of the electronic device 100 may affect the order of priority. When the electronic device 100 obtains the current location as a home, the priority of the contacts in the friend group is higher than the priority of the contacts in the colleague group; when the electronic device 100 obtains the current location as a company, the priority of the contacts in the colleague group is higher than the priority of the contacts in the friend group. This is not limited in the embodiments of the present application.

[0271] S607: The electronic device 100 sends the background sound corresponding to the target call scenario to the opposite electronic device, and the background sound is played by the opposite electronic device.

[0272] For a detailed description of S607, please refer to the above-mentioned introduction to S206, which will not be repeated here.

[0273] The various implementation modes of this application can be combined arbitrarily to achieve different technical effects.

[0274] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described herein are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).

[0275] Those skilled in the art will appreciate that all or part of the process steps in the above-described method embodiments can be implemented by a computer program instructing the relevant hardware. The program can be stored in a computer-readable storage medium, and when executed, the program can include the process steps in the above-described method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.

[0276] In short, the above description is only an embodiment of the technical solution of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent replacements, improvements, etc. made based on the disclosure of the present invention should be included in the scope of protection of the present invention.

Claims

1. A method for adjusting call volume, characterized in that: The method is applied to an electronic device, and the method comprises: The electronic device receives a call request sent by the opposite electronic device, and displays a first interface, wherein the first interface includes a first call scenario option and a second call scenario option, wherein the first call scenario option corresponds to a first call scenario, and the second call scenario option corresponds to the second call scenario, and the first call scenario is different from the second call scenario; The electronic device establishes a call connection with the opposite electronic device in response to the operation of selecting the first call scenario option; The electronic device plays a sound at a call volume corresponding to the first call scenario; The electronic device sends the background sound corresponding to the first call scenario to the opposite electronic device, and the background sound is played by the opposite electronic device.

2. The method according to claim 1, characterized in that After the electronic device establishes a call connection with the opposite electronic device, the method further includes: The electronic device displays a second interface, where the second interface includes first prompt information, and the first prompt information is used to prompt that the current call scenario is the first call scenario.

3. A method for adjusting call volume, characterized in that: The method is applied to an electronic device, and the method comprises: The electronic device displays a third interface in response to a user's operation of making a call, wherein the third interface includes a first call scenario option and a second call scenario option, wherein the first call scenario option corresponds to a first call scenario, and the second call scenario option corresponds to a second call scenario, and the first call scenario is different from the second call scenario; The electronic device initiates a call request to the other electronic device in response to the operation of selecting the first call scenario option; After receiving the information that the opposite electronic device confirms the call request, the electronic device establishes a call connection with the opposite electronic device; The electronic device plays sound at a call volume corresponding to the first call scenario; the electronic device sends the background sound corresponding to the first call scenario to the opposite electronic device, and the background sound is played by the opposite electronic device.

4. The method according to any one of claims 1 to 3, characterized in that After the electronic device plays a sound at a call volume corresponding to the first call scenario, the method further includes: The electronic device displays a fourth interface, and the third interface includes second prompt information; the second prompt information is used to prompt that the current call scenario is the first call scenario.

5. The method according to any one of claims 1 to 4, characterized in that The method further comprises: The peer electronic devices include multiple ones, and the number of peer user information of the peer electronic devices includes multiple ones, and the second call scenario is the call scenario corresponding to the peer user information with the highest priority among the multiple peer user information.

6. The method according to claim 5, characterized in that The correspondence between the peer user information and the second call scenario is set by a local user of the electronic device, or is preset by the electronic device.

7. The method according to any one of claims 1 to 6, characterized in that The first call scenario or the second call scenario is determined by the electronic device based on one or more of the following: the environment of the local user, the status of the local user, the information of the opposite user, the relationship between the opposite user and the local user, and the current time.

8. The method according to any one of claims 1 to 7, characterized in that After the electronic device plays the sound at the call volume corresponding to the first call scenario, the method further includes: the electronic device plays the background sound.

9. The method according to any one of claims 1 to 8, characterized in that Before the electronic device plays a sound at a call volume corresponding to the first call scenario, the method further includes: The electronic device performs voice modification processing on the sound; The electronic device playing the sound at the call volume corresponding to the first call scenario specifically includes: The electronic device plays the voice-changed sound at a call volume corresponding to the first call scenario.

10. An electronic device, characterized in that: The electronic device comprises a memory, one or more processors, and one or more programs; when the one or more processors execute the one or more programs, the electronic device implements the method as claimed in any one of claims 1 to 9.

11. A computer-readable storage medium comprising instructions, characterized in that: When the instructions are executed on an electronic device, the electronic device is caused to execute the method according to any one of claims 1 to 9.

Citation Information

Patent Citations

  • Method for adding background voice during conversation and communication terminal

    CN102810316A

  • Method and terminal for controlling voice frequency during telephone communication

    CN103731541A

  • User terminal volume adjusting method, device and terminal

    CN103945062A

  • Method for adding background sound in call, terminal and system

    CN106506834A

  • Call volume adjusting method applied to terminal, terminal and storage device

    CN111064843A

Cited By

  • Call method and related equipment

    CN120434323A