Call method, and electronic device and computer-readable storage medium

Abstract

A call method, and an electronic device and a computer-readable storage medium. In the call method, when an electronic device establishes a target communication connection with a second electronic device, a first system can receive, by means of the target communication connection, an incoming call request which is sent by the second electronic device and is used for calling the second electronic device, and can perform call data transmission with the second electronic device in response to an incoming call answering operation on a first incoming call request. In this way, a second system with a relatively high power consumption can be in a sleep state during a call, and a call function of the electronic device is ensured by means of running the first system with a relatively low power consumption. Therefore, not only can the call function of the electronic device be maintained, but the power consumption of the second system during the call can also be further reduced, thereby achieving the effect of reducing the power consumption of the electronic device while keeping the function of the electronic device unchanged.

Description

Communication methods, electronic devices, and computer-readable storage media

[0001] This application claims priority to Chinese Patent Application No. 202510181842X, filed on February 18, 2025, entitled "Method of Conversation, Electronic Device and Computer-Readable Storage Medium", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of electronic device technology, and includes, but is not limited to, a communication method, an electronic device, and a computer-readable storage medium. Background Technology

[0003] Dual-core systems, because they can provide more computing resources to electronic devices through two processor cores and improve the computing performance of electronic devices, have gradually become the mainstream architecture for electronic devices.

[0004] Electronic devices with dual-core systems can support a variety of functions. However, this diversification may increase the power consumption of electronic devices. Therefore, how to reduce the power consumption of electronic devices with dual-core systems is an urgent problem to be solved. Summary of the Invention

[0005] The communication method, electronic device, and computer-readable storage medium provided in the embodiments of this application are implemented as follows:

[0006] In one aspect of this application, a call method is provided, applied to a first electronic device, the first electronic device supporting a first system and a second system, wherein the power consumption of the first system is less than the power consumption of the second system, the method comprising:

[0007] When the first electronic device and the second electronic device establish a target communication connection, the first system receives a first incoming call request sent by the second electronic device through the target communication connection. The first incoming call request is used to call the second electronic device.

[0008] The first system responds to the incoming call answering operation in response to the first incoming call request by transmitting call data with the second electronic device.

[0009] In another aspect of this application, an electronic device is also provided, which supports a first system and a second system, wherein the power consumption of the first system is less than the power consumption of the second system, and the electronic device includes:

[0010] The receiving module is configured to, when the electronic device establishes a target communication connection with the second electronic device, receive a first incoming call request sent by the second electronic device through the target communication connection, wherein the first incoming call request is used to call the second electronic device;

[0011] An execution module is used by the first system to perform call data transmission with the second electronic device in response to an incoming call answering operation for the first incoming call request.

[0012] In another aspect of the embodiments of this application, an electronic device is also provided, the electronic device including a memory and a processor, the memory storing a computer program that can run on the processor, and the processor executing the program to implement the method of the embodiments of this application.

[0013] In another aspect of the embodiments of this application, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the method provided in the embodiments of this application. Attached Figure Description

[0014] Figure 1 is a structural block diagram of an example electronic device provided in an embodiment of this application;

[0015] Figure 2 is a flowchart of an example of a call method provided in an embodiment of this application;

[0016] Figure 3 is a structural block diagram of an exemplary software architecture of the Android system provided in an embodiment of this application;

[0017] Figure 4 is a structural block diagram of an exemplary software architecture of the RTOS system provided in an embodiment of this application;

[0018] Figure 5 is a flowchart of another example of the call method provided in the embodiments of this application;

[0019] Figure 6 is a schematic diagram of an example of the first incoming call notification interface provided in an embodiment of this application;

[0020] Figure 7 is a flowchart of another example of the call method provided in the embodiments of this application;

[0021] Figure 8 is a flowchart of another example of the call method provided in the embodiments of this application;

[0022] Figure 9 is a flowchart of another example of the call method provided in the embodiments of this application;

[0023] Figure 10 is a flowchart of another example of the call method provided in the embodiments of this application;

[0024] Figure 11 is a schematic diagram of an example of a power-off interface provided in an embodiment of this application;

[0025] Figure 12 is a structural block diagram of an example electronic device provided in an embodiment of this application;

[0026] Figure 13 is a schematic diagram of an example of an electronic device provided in an embodiment of this application. Detailed Implementation

[0027] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the specific technical solutions of this application will be further described in detail below with reference to the accompanying drawings of the embodiments of this application. The following embodiments are used to illustrate this application, but are not intended to limit the scope of this application.

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

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

[0030] It should be noted that the terms "first, second, third" used in the embodiments of this application are used to distinguish similar or different objects and do not represent a specific order of objects. It can be understood that "first, second, third" can be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0031] The diversification of functions in electronic devices is one of the main research directions in the field of electronic device technology. Taking smartwatches as an example, to achieve functional diversification, smartwatches can not only provide functions such as displaying information like time and date, but also, after being paired with a mobile phone, provide call functionality, that is, answer and handle incoming call requests through the smartwatch, enabling communication with the caller. However, functional diversification inevitably increases the power consumption of electronic devices. Therefore, in order to reduce power consumption while maintaining functional diversification, electronic devices with dual-core systems have been proposed.

[0032] Please refer to Figure 1, which is a structural block diagram of an example of an electronic device 100 with a dual-core system provided in an embodiment of this application.

[0033] A dual-core system can be understood as having multiple processor cores with different computing performance in an electronic device 100. For example, in Figure 1, the electronic device 100 may include a first processor core 101 and a second processor core 102. Different processor cores can run different systems. For example, as shown in Figure 1, the first processor core 101 runs a first system 201, and the second processor core 102 runs a second system 202. The power consumption of different processor cores running different systems is different, and the first system 201 and the second system 202 can communicate with each other.

[0034] The processor core here can be understood as a logical processor core, which virtualizes a physical processor core into multiple logical processor cores. Different logical processor cores can independently run their own operating systems and applications, and different logical processor cores correspond to the same processor chip. Alternatively, the processor core can also be understood as a physical processor core, that is, different processor cores correspond to different processor chips. For example, the first processor core 101 can be a microcontroller unit (MCU), and the second processor core 102 can be a central processing unit (CPU). Of course, the first processor core 101 and the second processor core 102 can also be other processors, which are not limited here.

[0035] The system here can be understood as an operating system. For example, the first system 201 can be a real-time operating system (RTOS), and the second system 202 can be an Android operating system. Of course, the first system and the second system can also be other systems, which will not be listed here.

[0036] This approach enhances the computing performance of electronic devices by using two processor cores, enabling them to perform a variety of functions. However, this functional diversification can increase power consumption, reducing battery life and impacting user experience. Therefore, reducing the power consumption of dual-core electronic devices is a pressing issue that needs to be addressed.

[0037] To address this issue, the applicant analyzed the power consumption of electronic devices with dual-core systems. Since the power consumption of the system with higher operating power consumption is the main source of power consumption in dual-core electronic devices, the power consumption analysis primarily focuses on the power consumption of the system with higher operating power consumption. For example, the power consumption of the second system 202 in the electronic device shown in Figure 1 is analyzed. The analysis reveals that the system with higher operating power consumption, such as the second system 202, consumes more power during calls. Therefore, reducing the power consumption of the dual-core electronic device during calls will effectively reduce the overall power consumption of the electronic device.

[0038] Therefore, this application provides a call method applied to an electronic device with a dual-core system, such as a first electronic device. This first electronic device supports two systems with different power consumptions: a first system with lower power consumption and a second system with higher power consumption. Since the first system has lower power consumption, it can perform some functions of the electronic device, such as the call function. Thus, when a target communication connection is established with the second electronic device, the first system can receive a call request from the second electronic device and, in response to the call answering operation for the first call request, transmit call data with the second electronic device. In this way, the higher-power second system can be in a sleep state during a call, while the lower-power first system ensures the call function of the electronic device. This maintains the call function of the electronic device while further reducing the power consumption of the second system during a call, achieving the effect of reducing the power consumption of the electronic device without changing its functionality. Furthermore, when the second system is off, the call can be conducted solely through the first system, ensuring call functionality in various situations.

[0039] The call method provided in the embodiments of this application will now be described in detail with reference to Figure 1.

[0040] Please refer to Figure 2, which is a flowchart illustrating an example of a call method provided in an embodiment of this application. This call method is applied to a first electronic device, which supports a first system and a second system, wherein the power consumption of the first system is less than that of the second system. It is understood that the first electronic device can be the electronic device 100 shown in Figure 1, the first system can be the first system 201 shown in Figure 1, and the second system can be the second system 202 shown in Figure 1. The flowchart includes the following steps:

[0041] S201. When the first electronic device and the second electronic device establish a target communication connection, the first system receives the first incoming call request sent by the second electronic device.

[0042] In this embodiment, an example is taken where the processor cores running the first system and the second system have different processing performance, and the processing performance of the processor core running the first system is lower than that of the processor core running the second system. The first electronic device may include multiple operating modes, and the first system and the second system are in different states under different operating modes.

[0043] As an example, the multiple operating modes may include a fully intelligent mode and a low-power mode. When the first electronic device is in fully intelligent mode, the first system and the second system can be simultaneously awake. The second system is used to support most of the functions of the first electronic device, while the first system is used to provide auxiliary functions. In this way, the processing performance of the electronic device is improved through the joint action of the first system and the second system. When the first electronic device is in low-power mode, the first system is awake, while the second system is in hibernation. By putting the second system into hibernation, the power consumption of the first electronic device can be reduced, thereby improving the battery life of the first electronic device.

[0044] Users can set the operating mode of the first electronic device according to their actual usage needs. For example, in scenarios with strong interaction, such as playing games, users can set the first electronic device to full smart mode; while in scenarios with weak interaction, such as when the first electronic device only needs to display the time or notification messages, it can be set to low power mode.

[0045] It should be noted that the functions supported by the first system and the second system can overlap to some extent. For example, both the first system and the second system can support functions such as notification message display and time display. However, the second system can support some functions with high processing performance requirements, such as game functions, which are not supported by the first system. The specific functions to be set in the first system and the second system are not restricted here.

[0046] Since the method in this application embodiment is aimed at the call function of a first electronic device, the call function of the first electronic device will be described below. In this application embodiment, the call function supported by the first electronic device may include, but is not limited to, the following two types:

[0047] The first type of call is short-range communication:

[0048] Near-field communication can be understood as using a short-range communication connection channel established with other electronic devices to process incoming calls from other electronic devices through a first electronic device.

[0049] This short-range communication can be Bluetooth, Zigbee, etc., and is not limited here. Taking Bluetooth as an example, this short-range call can also be called a Bluetooth call. After the first electronic device establishes a Bluetooth connection with other electronic devices, when the other electronic device receives an incoming call request, it can forward the received call request to the first electronic device through the Bluetooth connection channel. The user can then operate on the first electronic device to handle incoming calls from other electronic devices, such as answering or rejecting the call.

[0050] The second type of call is a Subscriber Identity Module (SIM) call:

[0051] A SIM call can be understood as a first electronic device equipped with a SIM card, allowing other electronic devices to call that first electronic device via the SIM card. In this case, the incoming call request received by the first electronic device is for the purpose of calling the first electronic device. Because SIM calls are based on cellular networks, they can also be called cellular calls.

[0052] In the embodiments of this application, the SIM card can be a physical SIM card, such as a micro SIM card or a nano SIM card; it can also be a virtual SIM card, that is, an embedded SIM (eSIM) card implemented in software, which is not limited here. The following description uses eSIM as an example.

[0053] As an example, both types of calling functions can be set in one of the first and second systems. For example, both types of calling functions can be set in the second system. Alternatively, the two types of calling functions can be set in different systems. For example, near-field communication can be set in the first system, while eSIM communication can be set in the second system.

[0054] However, the functions set in the system will affect the power consumption of the corresponding system. For example, if both of the above-mentioned call functions are set in the second system, the second system may not be able to sleep for a long time in order for the first electronic device to receive incoming call requests or implement any of the call functions, thus increasing the power consumption of the first electronic device. If only one of the above-mentioned call functions is set in the first system, the second system can sleep while implementing one of the call functions through the first system, thereby reducing the power consumption of the first electronic device.

[0055] Therefore, in this embodiment of the application, the two call functions are set in different systems. For example, the near-field call function is set in the first system, and the eSIM call function is set in the second system.

[0056] Thus, once the first electronic device establishes a target communication connection with the second electronic device, it receives the first incoming call request sent by the second electronic device through the target communication connection. In this embodiment, the first incoming call request is a call request to the second electronic device.

[0057] As described above regarding proximity communication, the first call request in step S201 is a call request corresponding to proximity communication. That is, the first call request received by the first electronic device is used to call other electronic devices that have established a proximity communication connection with the first electronic device. For example, if the first electronic device establishes a proximity communication connection with a second electronic device, then the first call request is a call request to the second electronic device. Correspondingly, the target communication connection in step S201 can also be understood as a communication connection established using a target proximity communication method. It can be understood that the first call request can be sent by the second electronic device through this target communication connection.

[0058] As an example, in the case of a near-field call using Bluetooth, the target communication connection can also be understood as a Bluetooth communication connection, and the first incoming call request is a call request sent through the Bluetooth communication connection. For ease of explanation, the following text uses a Bluetooth call as an example.

[0059] It should be noted that the first electronic device is equipped with a communication component, such as a Bluetooth communication component. The first electronic device can establish a Bluetooth communication connection with the second electronic device through the Bluetooth communication component and receive incoming call requests sent by the second electronic device through the Bluetooth communication connection.

[0060] As an example, the first call request may include information about the caller, such as at least one of the caller's number, name, or location.

[0061] S202, the first system responds to the incoming call answering operation in response to the first incoming call request and transmits call data with the second electronic device.

[0062] After receiving a first incoming call request, the first system can output an incoming call alert, which may include information about the caller corresponding to the first incoming call request. The first electronic device may output the incoming call alert in at least one of the following ways: sound alert, vibration alert, and interface alert.

[0063] After the first electronic device displays an incoming call notification, the user can decide whether to answer or hang up the call. For example, the user can use voice, touch, or gesture controls to determine whether to answer or hang up the call.

[0064] When an incoming call to the first call request is detected, the first system can send an answer notification to the second electronic device through the target communication connection and transmit call data with the second electronic device.

[0065] In the above technical solution, when a target communication connection is established with the second electronic device, the first system of the first electronic device can receive a call request from the second electronic device via the target communication connection, and can respond to the call answering operation in response to the first call request by transmitting call data with the second electronic device. In this way, the power-intensive second system can be in a sleep state during a call, while the lower-power first system ensures the call function of the electronic device. This maintains the call function of the electronic device and further reduces the power consumption of the second system during a call, achieving the effect of reducing the power consumption of the electronic device without changing its functionality.

[0066] To further illustrate the call method in the embodiments of this application, the software architecture of the first electronic device in the embodiments of this application will first be described. The first electronic device is a dual-system electronic device including a first system and a second system. In the following example, the first system is an RTOS system and the second system is an Android system.

[0067] Please refer to Figure 3, which is a structural block diagram of the software architecture of an Android system illustrated in an exemplary embodiment of this application. As shown in Figure 3, the software architecture of the Android system may include an application layer 301, an application framework layer 302, a system layer 303, a hardware abstraction layer (HAL) 304, and a kernel layer 305, with the layers communicating with each other through software interfaces.

[0068] Application layer 301 may include a series of application packages. As shown in Figure 3, the application packages may include applications such as gallery, map, and calling. In this embodiment, assuming that eSIM calling is enabled in the Android system, the calling application in this application package can be understood as an eSIM calling application.

[0069] Application framework layer 302 provides application programming interfaces (APIs) and programming frameworks for applications in application layer 301. To ensure eSIM calls in the Android system, application framework layer 302 may include a telecom service. The telecom service is used to manage eSIM call functionality, including initiating, managing, and terminating eSIM calls.

[0070] System layer 303 includes the Android runtime and native libraries. The Android runtime module includes core libraries and a virtual machine, responsible for system scheduling and management. The core libraries may include modules for eSIM call adaptation. Application layer 301 and application framework layer 302 run in a virtual machine. The virtual machine executes the programming files of application layer 301 and application framework layer 302 into binary files and performs object lifecycle management functions.

[0071] The native library can include multiple functional modules or services. For example, it can include a virtual Bluetooth hands-free profile (HFP) service, which provides an interface for all upper-layer applications that rely on Bluetooth call status (such as eSIM calls) to obtain the Bluetooth call status of electronic devices.

[0072] Hardware Abstraction Layer (HAL) 304. The Hardware Abstraction Layer includes the Audio HAL, etc. The Audio HAL is used to manage the audio capabilities of the primary electronic device. Of course, it can also include HALs corresponding to the capabilities of other devices, which will not be listed here.

[0073] Kernel layer 305 is the layer between hardware and software. The kernel layer includes at least display drivers, audio drivers, network drivers, storage drivers, and CPU drivers.

[0074] Please refer to Figure 4, which is a structural block diagram of the software architecture of an RTOS system illustrated in an exemplary embodiment of this application. As shown in Figure 4, the software architecture of the RTOS system may include an application layer 401, a service layer 402, a framework layer 403, a hardware abstraction layer 404, and a hardware layer 405.

[0075] Application layer 401 includes multiple applications, such as watch face applications, message center applications, and health applications. Since the RTOS system supports Bluetooth calling, application layer 401 also includes a Bluetooth calling application.

[0076] Service layer 402 supports the development of application layer 401 by providing a series of system-level services. For example, to support Bluetooth calling applications, service layer 402 can provide Bluetooth calling services to support voice calls.

[0077] The framework layer 403 is the core of the RTOS system, providing a collection of software components that offer system-level functions and services. For example, it may include a task scheduler responsible for scheduling tasks based on priority and status; it may also include a function library providing system calls and APIs. This function library may include an HFP service for Bluetooth calling, with specific functions similar to the HFP service in Figure 3, which will not be elaborated further here. Additionally, to support Bluetooth calling functionality, the framework layer 403 may also include a Bluetooth protocol stack, which handles all protocol details of Bluetooth communication, including data transmission, device discovery, connection management, and audio transmission.

[0078] Hardware abstraction layer 404 is similar to hardware abstraction layer 304 shown in Figure 3, and will not be described in detail here.

[0079] Hardware layer 405 is the lowest layer of the RTOS architecture, which includes the actual hardware devices such as processors, memory, audio acquisition modules (e.g., microphones), audio playback modules (e.g., speakers), and Bluetooth chips for supporting Bluetooth calls.

[0080] It should be noted that the above-described communication software framework is for illustrative purposes only. Those skilled in the art can add, delete, or modify the framework according to actual needs. The embodiments of this application do not limit the specific structure of the communication software framework.

[0081] As shown in Figure 4, the software architecture of the RTOS system can deploy all components related to the Bluetooth calling function. In this way, the first electronic device can directly support the Bluetooth calling function through the RTOS system. Furthermore, during the Bluetooth calling process of the first electronic device through the RTOS system, the Android system can be in a sleep state, which can reduce the power consumption of the first electronic device during the Bluetooth calling process.

[0082] The call method provided in the embodiments of this application will be described in detail below.

[0083] Please refer to Figure 5, which is a flowchart of another example of the call method provided in the embodiments of this application. The flowchart includes the following steps:

[0084] S501. When the first electronic device and the second electronic device establish a target communication connection, the first system receives the first incoming call request sent by the second electronic device.

[0085] Step S501 is similar to step S201, and will not be described again here.

[0086] Referring to the RTOS described in Figure 4, the first electronic device can establish a Bluetooth connection with the second electronic device through the Bluetooth chip and Bluetooth protocol stack in the first system (e.g., the RTOS system). As an example, the first electronic device can be a wearable device, such as a smartwatch; the second electronic device can be a mobile phone, tablet computer, or other electronic device, without limitation.

[0087] When the second electronic device receives an incoming call request, it can forward the request via the Bluetooth connection established with the first electronic device.

[0088] S502, The first system responds to the first incoming call request and outputs the first incoming call notification interface.

[0089] In this embodiment of the application, the example is the first system outputting an incoming call notification interface through an interface reminder.

[0090] Specifically, the first system launches the target calling application and controls the target calling application to display the first incoming call notification interface. It is understood that the target calling application is an application that uses the target communication connection for call data transmission.

[0091] In this embodiment, taking Bluetooth calling as an example, when the first system receives the first incoming call request, it invokes the Bluetooth calling application and displays the first incoming call notification interface. If the Bluetooth calling application is not running, the first system starts the Bluetooth calling application and controls it to display the first incoming call notification interface. Of course, if the Bluetooth calling application is already running after the first system receives the first incoming call request, for example, if the Bluetooth calling application is a background application of the first system, the first system activates the Bluetooth calling application as a foreground application and controls it to display the first incoming call notification interface.

[0092] As an example, the first incoming call notification interface includes an answer control, which the user can use to answer the call. As another example, the first incoming call notification interface may also include a reject control, which the user can use to reject the call. Of course, in addition to the aforementioned controls, the first incoming call notification interface may also include other information, such as the caller's information. As shown in Figure 6, where the first electronic device is a smartwatch, the first incoming call notification interface includes not only the answer control but also the caller's information, including name, number, and location. This allows the user to determine whether to answer or reject the call based on the caller's information.

[0093] S503, the first system responds to a touch operation on the answering control and transmits call data with the second electronic device.

[0094] Specifically, after detecting a touch operation on the answering control, the first system, in response to the touch operation, sends an answer notification to the second electronic device via Bluetooth connection, and acquires first call data collected by an audio acquisition module, such as a microphone, and sends the first call data to the second electronic device via Bluetooth connection for playback by the audio playback module of the second electronic device; and after receiving the answer notification, the second electronic device sends the second call data it has acquired to the first electronic device via the Bluetooth connection. After receiving the second call data, the first system controls the audio playback module of the first electronic device, such as a speaker, to play the second call data, thereby realizing the transmission of call data with the second electronic device.

[0095] S504. In response to a touch operation on the rejection control, the first system sends a hang-up notification to the second electronic device.

[0096] Specifically, when the first system detects a touch operation on the rejection control, in response to the touch operation on the rejection control, it sends a hang-up notification to the second electronic device through the Bluetooth connection between the two devices. Upon receiving the rejection notification, the second electronic device hangs up the incoming call.

[0097] It should be noted that only one of steps S503 and S504 is executed. In the flowchart shown in Figure 5, taking the execution of step S503 without executing step S504 as an example, step S504 is represented by a dashed line in Figure 5.

[0098] The process described in Figure 5 will now be explained in conjunction with the software architecture of the first system shown in Figure 4.

[0099] Figure 7 shows a flowchart of an example of a call method provided in an embodiment of this application. The flowchart includes the following steps:

[0100] 701. The first electronic device establishes a Bluetooth connection with the second electronic device according to the Bluetooth protocol stack.

[0101] 702. The third electronic device sends the first incoming call request to the second electronic device.

[0102] 703. The second electronic device forwards the first incoming call request to the first electronic device via Bluetooth connection.

[0103] 704. The first incoming call request is reported to the Bluetooth phone service via the Bluetooth protocol stack and HFP service.

[0104] 705. The Bluetooth phone service calls the Bluetooth calling application and outputs an incoming call reminder.

[0105] For example, a Bluetooth calling application can be invoked to display an incoming call notification interface, which includes controls for answering and rejecting calls.

[0106] 706. The Bluetooth calling application will send the detected operation to the Bluetooth phone service.

[0107] When a user interacts with the incoming call notification screen, such as by touching the answer or reject control, the Bluetooth calling application will send the detected interaction to the Bluetooth phone service.

[0108] 707. The Bluetooth telephony service generates corresponding control commands based on this operation, and sends the generated commands to the second electronic device through the HFP service and Bluetooth connection.

[0109] For example, if the operation is a touch-to-answer control, the Bluetooth phone service generates an answer command; if the operation is a touch-to-reject control, the Bluetooth phone service generates a reject command.

[0110] 708. When the instruction is an answer instruction, the Bluetooth phone service can also transmit call data with a second electronic device through the HFP service and the Bluetooth protocol stack.

[0111] For example, a Bluetooth phone service can access the microphone of a first electronic device to capture the user's voice and send the voice message via Bluetooth. It can also receive the voice message sent by a second electronic device via Bluetooth and play it through the speaker of the first electronic device, thereby enabling a Bluetooth call with the second electronic device.

[0112] Additionally, it should be noted that the call method provided in this application embodiment does not restrict the state of the second system. The second system can be in a sleep state, which can reduce the power consumption of the electronic device; the second system can also be in a wake-up state. In this case, the second system has control over the display screen of the first electronic device. When the first system receives the first incoming call request, the first system can obtain control over the display screen from the second system to display the incoming call notification interface. When a rejection operation is detected or the Bluetooth call ends, the control over the display screen is released.

[0113] As described above regarding the call functions supported by the first electronic device, it supports two call functions. To prevent malfunctions caused by simultaneous operation of both call functions, the first system can also synchronize the Bluetooth call status to the second system. This situation will be explained below.

[0114] Please refer to Figure 8, which is a flowchart of another example of the call method provided in the embodiments of this application. The flowchart includes the following steps:

[0115] S801. When the first electronic device and the second electronic device establish a target communication connection, the first system receives the first incoming call request sent by the second electronic device.

[0116] S802, the first system responds to the incoming call answering operation in response to the first incoming call request and transmits call data with the second electronic device.

[0117] Steps S801 to S802 are similar to steps S201 to S202, and will not be described again here.

[0118] S803, The first system sends target status information to the second system.

[0119] In this embodiment, the target state information is used to indicate the current state of the first system, which includes a call state or a non-call state. For example, when the first system answers a first incoming call request and conducts a data call with a second electronic device, the current state of the first system is the call state; when the first system rejects the first incoming call request, the current state of the first system is the non-call state.

[0120] As an example, step S803 can be implemented in, but is not limited to, the following two ways:

[0121] First implementation method:

[0122] When the second system is in a wake-up state, the first system sends target status information to the second system.

[0123] In this implementation, the first system proactively sends the target status information to the second system. For example, the first system can detect whether the second system is awake; if so, the first system sends the target status information. Alternatively, if the second system is in a sleep state, the first system can proactively wake it up and then send the target status information; or, the first system can periodically send the target status information to the second system according to a preset period. This allows for timely synchronization of the first system's status with the second system.

[0124] The second implementation method:

[0125] When the second system is in a wake-up state, the second system sends a status acquisition request to the first system to obtain target status information, and the first system responds to the status acquisition request by sending the target status information to the second system.

[0126] In this implementation, the first system sends the target status information to the second system based on the second system's request. This way, the first system only sends the target status information when the second system requires it, reducing interaction between the two systems and saving power.

[0127] As an example, the second system can send a status acquisition request to the first system each time it switches to the wake-up state; or, the second system can periodically send the status acquisition request to the first system.

[0128] As another example, after receiving a second incoming call request from a third electronic device for calling the first electronic device, the second system can, in response to the second incoming call request, send the status acquisition request to the first system. It is understood that the second incoming call request is an eSIM call request. In this embodiment, to prevent the first electronic device from simultaneously making Bluetooth and eSIM calls, when the second system receives an eSIM call request, it can proactively send a status acquisition request to the first system to determine whether it can output an incoming call alert based on the second incoming call request.

[0129] If the target status information indicates that the current state of the first system is a non-call state, the second system outputs a second incoming call notification interface, which is the incoming call notification interface corresponding to the eSIM call. Specifically, the second system can control the eSIM call application to be running and control the eSIM call application to display the second incoming call notification interface. The content included in the second incoming call notification interface is similar to that included in the first incoming call notification interface, and will not be described again here. Of course, the second system can also use other methods to output incoming call reminders, such as sound reminders or vibration reminders, etc., which will not be listed here.

[0130] If the target status information indicates that the current status of the first system is the call status, the second system sends a hang-up notification or a busy signal notification to the third electronic device. It is understood that for the caller, both hang-up and busy signal notifications result in the same outcome: the second call request was not answered. Those skilled in the art can configure the system to select which notification to send in this situation based on actual circumstances; no restrictions are imposed here.

[0131] If the target status information indicates that the current state of the first system is the call state, the second system can also send an incoming call notification to the first system. In this way, the first system can also notify the user of a new call without affecting the Bluetooth call. For example, upon receiving an incoming call notification from the second system, the first system can alert the user of a new call through at least one method, such as vibration, screen display, or audio. Taking screen display as an example, the first system can pop up a notification message on the Bluetooth call application interface to indicate a new call. In this embodiment, the notification methods of the first system will not be described one by one.

[0132] In some embodiments, after receiving a new incoming call notification, a user can choose to hang up the current Bluetooth call on the first system and choose to answer the incoming call on the second system.

[0133] In some embodiments, after receiving a new incoming call notification, a user can choose to suspend the current Bluetooth call on the first system and choose to answer the call on the second system first.

[0134] The process described in Figure 8 will now be explained in conjunction with the software architecture of the first system shown in Figures 3 and 4.

[0135] Figure 9 shows a flowchart of an example of a call method provided in an embodiment of this application. The flowchart includes the following steps:

[0136] 901. The eSIM calling application of the second system receives the second incoming call request.

[0137] The second incoming call request is a request sent by a third electronic device to call the first electronic device.

[0138] 902. The second system's telecom service sends a status retrieval request to the virtual HFP service.

[0139] 903. The virtual HFP service sends the status retrieval request to the HFP service of the first system.

[0140] 904. The HFP service of the first system feeds back the target status information to the virtual HFP service.

[0141] 905. The virtual HFP service sends the acquired target status information to the telecom service.

[0142] 906. When the Telecom service indicates that the target status information of the first system is in a non-call state, it calls the eSIM calling application and displays the second incoming call notification interface.

[0143] The above description illustrates the call method provided in this application embodiment, using the example of answering or rejecting a call during a conversation. In other examples, the above call method may also include a step of sending a call.

[0144] Please refer to Figure 10, which is a flowchart of another example of the call method provided in the embodiments of this application. The flowchart includes the following steps:

[0145] S1001. When the first electronic device and the second electronic device establish a target communication connection, the first system receives the first incoming call request sent by the second electronic device.

[0146] S1002, the first system responds to the incoming call answering operation in response to the first incoming call request and transmits call data with the second electronic device.

[0147] Steps S1001 to S1002 are similar to steps S201 to S202, and will not be described again here.

[0148] S1003, The first system responds to the power-off operation and outputs the first power-off interface.

[0149] In this embodiment, the first call-out interface includes at least one called party information stored in the second electronic device. Since the first system supports Bluetooth calling, which is used to enable communication between the second electronic device and the calling party, when the first system detects a call-out operation and outputs the first call-out interface, the first call-out interface can be understood as being used to enable communication between the second electronic device and the called party. Therefore, the called party information displayed in the first call-out interface is stored in the second electronic device.

[0150] In some embodiments, S1003 may also be: when the second system is in the hibernation state or the off state, the first system responds to the power-off operation by outputting a first power-off interface.

[0151] Understandably, in this situation, the power-off operation can be performed directly through the first system to save power consumption.

[0152] For example, the first system can launch a target calling application and control the target calling application to display the first outgoing call interface. In this embodiment, the target calling application can be a Bluetooth calling application. The Bluetooth calling application of the first system can obtain at least one called party information stored in the second electronic device through a Bluetooth connection. Thus, when the first system detects an outgoing call operation, it can output an outgoing call interface including at least one called party information through the Bluetooth calling application.

[0153] S1004. The first system, in response to a touch operation on the target called party, sends a call request to the second electronic device.

[0154] In this embodiment of the application, the call request is used to call the electronic device corresponding to the target called party, and the target called party is one of the at least one called party.

[0155] When the first system detects a touch operation on the outgoing call interface targeting the called party, it sends a call request to the second electronic device via Bluetooth connection, so that the second electronic device calls the electronic device corresponding to the called party based on the call request.

[0156] S1005. If the first power-off interface includes a switching control, the first system responds to a touch operation on the switching control, wakes up the second system, and sends a power-off notification to the second system.

[0157] In this embodiment, the switching control is used to trigger the second system to output a second outgoing call interface. This can be understood as the first electronic device being able to switch between the outgoing call interface for Bluetooth calling and the outgoing call interface for eSIM calling. For example, when the first system is in a wake-up state, the outgoing call operation prioritizes outputting the outgoing call interface corresponding to the Bluetooth calling function; when the second system is in a wake-up state, the outgoing call operation prioritizes outputting the outgoing call interface corresponding to the eSIM calling function. Either outgoing call interface can include a switching control for switching to the outgoing call interface of the other calling function. As shown in Figure 11, in sub-figure A of Figure 11, taking the first outgoing call interface corresponding to the Bluetooth calling function displayed by the first electronic device as an example, this outgoing call interface includes the called party information stored by the second electronic device and a switching control. When the user performs a touch operation on the switching control, the first system sends an outgoing call notification to the second system. Alternatively, if the second system is in a sleep state, the first system first wakes up the second system and then sends the outgoing call notification to the second system.

[0158] S1006. The second system responds to the power outage notification and outputs a second power outage interface.

[0159] In this embodiment, the second outgoing call interface includes at least one called party information stored in the first electronic device. As shown in sub-figure B of Figure 11, when the second system receives the outgoing call notification, it can display the second outgoing call interface corresponding to the eSIM call function, which includes the called party information stored in the first electronic device. It is understood that the second outgoing call interface may also include a switching control, so that when the user touches the switching control, the first electronic device can switch from the second outgoing call interface to the first outgoing call interface.

[0160] S1007. The second system responds to touch on the at least one called information and calls the called electronic device via cellular communication on the first electronic device.

[0161] When the second system detects that the user has touched the called party's information on the second outgoing call interface, it can call the called electronic device. In this embodiment, the second system is equipped with an eSIM calling application, which is a cellular communication-based calling application. Therefore, the second system can display the outgoing call interface for calling the called electronic device through the eSIM calling application and send a call request to the called electronic device via cellular communication.

[0162] The above example illustrates the call-out operation in this application embodiment, using the user selecting the target caller as an example. In actual use, the call-out operation can be further simplified.

[0163] As an example, the first system and / or the second system runs a calling application with a first call-out control and a second call-out control. The first call-out control is used to trigger the first system to send a call-out instruction through the target communication connection (e.g., Bluetooth connection) so that the second electronic device calls a fourth electronic device according to the call-out instruction. The second call-out control is used to trigger the second system to call a fifth electronic device through cellular communication on the first electronic device according to the call-out instruction.

[0164] In some embodiments, the fourth and fifth electronic devices may be electronic devices selected by the user from their address book for communication.

[0165] In some embodiments, the first and second call-out controls can also be understood as quick call controls, which are used to call specific electronic devices. For example, when the first system is running a Bluetooth calling application, the display interface of the Bluetooth calling application includes a first and second call-out control. The first call-out control is used to call a fourth electronic device. When the user touches the first call-out control, the first system sends a call-out command to the second electronic device through the Bluetooth connection established with the second electronic device, so that the second electronic device calls the fourth electronic device. When the user touches the second call-out control, the first system sends a call-out command to the second system, triggering the second system to call a fifth electronic device through the cellular communication on the first electronic device according to the call-out command. When the second system is running an eSIM calling application, the display interface of the eSIM calling application includes a first and second call-out control. When the user touches the second call-out control, the second system calls the fifth electronic device through the cellular communication module in the first electronic device. When the user touches the first call-out control, the second system sends a call-out command to the first system, triggering the first system to send a call-out command to the second electronic device through the Bluetooth connection, so that the second electronic device calls the fourth electronic device.

[0166] Alternatively, the interface of a Bluetooth calling application may include only the first call cancellation control, and the interface of an eSIM calling application may include only the second call cancellation control; there are no restrictions here.

[0167] The above technical solutions enable one-click calling, improving the convenience of electronic devices.

[0168] Additionally, it should be noted that in the flowchart shown in Figure 10, taking the execution of steps S1001 to S1002 first, followed by steps S1003 to S1006 as an example, in this embodiment of the application, the execution order between steps S1001 to S1002 and steps S1003 to S1006 is not restricted. For example, steps S1003 to S1006 can be executed first, followed by steps S1001 to S1002, or steps S1001 to S1002 and steps S1003 to S1006 can be executed simultaneously, which will not be elaborated further here.

[0169] In the above technical solution, the first electronic device can also perform a power-off operation during a call through the first system, which can ensure the integrity of the functions of the first electronic device.

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

[0171] Based on the foregoing embodiments, this application provides an electronic device. Please refer to Figure 12, which is a schematic diagram of an example of the electronic device provided in this application. The electronic device supports a first system and a second system, where the power consumption of the first system is less than the power consumption of the second system. As shown in Figure 12, the electronic device includes:

[0172] The first system module 1201 is used to receive a first incoming call request sent by the second electronic device through the target communication connection when the electronic device establishes a target communication connection with the second electronic device. The first incoming call request is used to call the second electronic device.

[0173] And, in response to an incoming call answering operation for the first incoming call request, to transmit call data with the second electronic device.

[0174] In one embodiment, the first system module 1201 is further configured to:

[0175] Before the first system responds to the call answering operation for the first call request, in response to the first call request, a first call notification interface is output, the first call notification interface including answering controls;

[0176] The first system module 1201 is specifically used for:

[0177] In response to a touch operation on the answering control, data transmission for the call is performed with the second electronic device.

[0178] In one embodiment, the first system module 1201 is specifically used for:

[0179] Launch the target calling application and control the target calling application to display the first incoming call notification interface. The target calling application is an application that uses the target communication connection to transmit call data.

[0180] In one embodiment, the first system module 1201 is specifically used for:

[0181] In response to a touch operation on the answering control, the system acquires first call data collected by the audio acquisition module of the first electronic device and sends the first call data to the second electronic device.

[0182] The device receives second call data from the second electronic device and controls the audio playback module of the first electronic device to play the second call data.

[0183] In one embodiment, the first incoming call notification interface further includes a reject control, and the first system module 1201 is specifically used for:

[0184] In response to a touch operation on the rejection control, a hang-up notification is sent to the second electronic device.

[0185] In one embodiment, the electronic device further includes a second system module 1202, wherein the first system module 1201 is specifically used for:

[0186] When the second system module 1202 is in a wake-up state, the first system module 1201 sends target status information to the second system module 1202. The target status information is used to indicate the current status of the first system module 1201, which includes a call state or a non-call state.

[0187] In one embodiment, the second system module 1202 is further configured to:

[0188] When in a wake-up state, a status acquisition request is sent to the first system module 1201, the status acquisition request being used to acquire target status information;

[0189] The first system module 1201 is specifically used for:

[0190] In response to the status acquisition request, the target status information is sent to the second system.

[0191] In some embodiments, the second system module 1202 is specifically used for:

[0192] Receive a second incoming call request sent by a third electronic device, the second incoming call request being used to call the first electronic device;

[0193] In response to the second incoming call request, the status acquisition request is sent to the first system module 1201.

[0194] In some embodiments, the second system module 1202 is further configured to:

[0195] If the target status information indicates that the current status of the first system is the no-call state, a second incoming call notification interface is output; and / or,

[0196] If the target status information indicates that the current status of the first system is the call status, send a hang-up notification or a busy notification to the third electronic device: and / or,

[0197] When the target status information indicates that the current status of the first system is the call status, the second system sends a call notification to the first system, and the first system notifies the user that there is a new call.

[0198] In some embodiments, the first system module 1201 is further configured to:

[0199] In response to a call termination operation, a first call termination interface is output, the first call termination interface including at least one called information stored in the second electronic device;

[0200] In response to a touch operation on a target called party, a call request is sent to the second electronic device, so that the second electronic device calls the electronic device corresponding to the target called party, wherein the target called party is one of the at least one called party.

[0201] In some embodiments, the first system module 1201 is further configured to:

[0202] When the second system module 1202 is in the sleep state or in the off state, in response to the power-off operation, a first power-off interface is output, the first power-off interface including at least one called information stored in the second electronic device;

[0203] In response to a touch operation on a target called party, a call request is sent to the second electronic device, so that the second electronic device calls the electronic device corresponding to the target called party, wherein the target called party is one of the at least one called party.

[0204] In some embodiments, the first system module 1201 is specifically used for:

[0205] Launch the target call application and control the target call application to display the first outgoing call interface.

[0206] In some embodiments, the first call-out interface includes a switching control, the switching control being used to trigger the second system to output the second call-out interface, and the first system module 1201 is specifically used for:

[0207] In response to a touch operation on the switching control, the second system module 1202 is woken up, and a power outage notification is sent to the second system module 1202;

[0208] The second system module 1202 is further configured to: in response to the outgoing call notification, output a second outgoing call interface, the second outgoing call interface including at least one called information stored in the first electronic device;

[0209] In addition, in response to a touch of the at least one called information, the called electronic device is called via cellular communication on the first electronic device.

[0210] In some embodiments, the first system module 1201 is further configured to:

[0211] The first system module 1201 runs a call application, which has a first call-out control and a second call-out control. The first call-out control is used to trigger the first system to send a call-out instruction through the target communication connection, so that the second electronic device calls the fourth electronic device according to the call-out instruction. The second call-out control is used to trigger the second system to call the fifth electronic device according to the call-out instruction through cellular communication on the first electronic device.

[0212] In some embodiments, the first system module 1201 is further configured to:

[0213] The second system module 1202 runs a call application, which has a first call-out control and a second call-out control. The first call-out control is used to trigger the first system to send a call-out instruction through the target communication connection, so that the second electronic device calls a fourth electronic device according to the call-out instruction. The second call-out control is used to trigger the second system to call a fifth electronic device through cellular communication on the first electronic device according to the call-out instruction.

[0214] The descriptions of the above device embodiments are similar to those of the above method embodiments, and have similar beneficial effects. For technical details not disclosed in the device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0215] It should be noted that the module division of the electronic device shown in Figure 12 of this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, exist as separate physical units, or have two or more units integrated into one unit. The integrated units can be implemented in hardware, as software functional units, or a combination of software and hardware.

[0216] It should be noted that, in the embodiments of this application, if the above-described methods are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause an electronic device to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware and software combination.

[0217] Figure 13 is a schematic diagram of the structure of the electronic device provided in the embodiment of this application. Referring to Figure 13, the embodiment of this application provides an electronic device, which can be the electronic device with the first system and the second system described above. Its internal structure diagram is shown in Figure 13. The electronic device includes a processor 1320, a memory, and a network interface 1340 connected via a system bus 1310. The processor 1320 of the electronic device provides computing and control capabilities. The memory of the electronic device includes a non-volatile storage medium 1331 and internal memory 1332. The non-volatile storage medium 1331 stores an operating system, computer programs, and a database. The internal memory 1332 provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium 1331. The database of the electronic device is used to store data. The network interface 1340 of the electronic device is used to communicate with external electronic devices via a network connection. When the computer program is executed by the processor 1320, it implements the above-described method.

[0218] This application provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the method provided in the above embodiments.

[0219] This application provides a computer program product containing instructions that, when run on a computer, cause the computer to perform the steps in the method provided in the above-described method embodiments.

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

[0221] In one embodiment, the electronic device provided in this application can be implemented as a computer program, which can run on the electronic device shown in FIG13. The memory of the electronic device can store various program modules constituting the above-described apparatus. The computer program, composed of the various program modules, causes the processor to execute the steps of the methods in the various embodiments of this application described in this specification.

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

[0223] It should be understood that the phrases "one embodiment," "an embodiment," or "some embodiments" mentioned throughout the specification mean that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment," "in one embodiment," or "in some embodiments" appearing throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence numbers of the above-described processes do not imply a sequential order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The sequence numbers of the above-described embodiments are merely for descriptive purposes and do not represent the superiority or inferiority of the embodiments. The descriptions of the various embodiments above tend to emphasize the differences between the various embodiments; their similarities or commonalities can be referred to mutually, and for the sake of brevity, they will not be repeated here.

[0224] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three kinds of relationships. For example, object A and / or object B can represent three situations: object A exists alone, object A and object B exist simultaneously, and object B exists alone.

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

[0226] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The embodiments described above are merely illustrative. For example, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple modules or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or modules can be electrical, mechanical, or other forms.

[0227] The modules described above as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules. They may be located in one place or distributed across multiple network units. Some or all of the modules may be selected to achieve the purpose of this embodiment according to actual needs.

[0228] In addition, each functional module in the various embodiments of this application can be integrated into one processing unit, or each module can be a separate unit, or two or more modules can be integrated into one unit; the integrated modules can be implemented in hardware or in the form of hardware plus software functional units.

[0229] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, read-only memory (ROM), magnetic disks, or optical disks.

[0230] Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause an electronic device to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROMs, magnetic disks, or optical disks.

[0231] The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.

[0232] The features disclosed in the several product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.

[0233] The features disclosed in the several method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method or device embodiments.

[0234] The above description is merely an embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for making a call, characterized in that, Applied to a first electronic device, the first electronic device supporting a first system and a second system, wherein the power consumption of the first system is less than the power consumption of the second system, the method includes: When the first electronic device and the second electronic device establish a target communication connection, the first system receives a first incoming call request sent by the second electronic device through the target communication connection. The first incoming call request is used to call the second electronic device. The first system responds to the incoming call answering operation in response to the first incoming call request by transmitting call data with the second electronic device.

2. The method according to claim 1, characterized in that, Before the first system responds to an incoming call answering operation in response to the first incoming call request, the method further includes: The first system responds to the first incoming call request and outputs a first incoming call notification interface, which includes an answer control. The first system, in response to an incoming call answering operation for the first incoming call request, performs call data transmission with the second electronic device, including: The first system responds to a touch operation on the answering control to transmit call data with the second electronic device.

3. The method according to claim 2, characterized in that, In response to the first incoming call request, the first system outputs a first incoming call notification interface, including: The first system launches the target calling application and controls the target calling application to display the first incoming call notification interface. The target calling application is an application that uses the target communication connection to transmit call data.

4. The method according to claim 2, characterized in that, In response to the first incoming call request, the first system outputs a first incoming call notification interface, including: When the second system is in a wake-up state, control of the display screen of the first electronic device is obtained from the second system, and the first incoming call notification interface is displayed.

5. The method according to any one of claims 2-4, characterized in that, The first system, in response to a touch operation on the answering control, performs call data transmission with the second electronic device, including: In response to a touch operation on the answering control, the first system acquires first call data collected by the audio acquisition module of the first electronic device, and sends the first call data to the second electronic device. The first system receives the second call data from the second electronic device and controls the audio playback module of the first electronic device to play the second call data.

6. The method according to claim 2, characterized in that, The first incoming call notification interface also includes a reject control, and the method further includes: In response to a touch operation on the rejection control, the first system sends a hang-up notification to the second electronic device.

7. The method according to claim 2, characterized in that, The method further includes: When the second system is in a wake-up state, the first system, in response to a touch operation on the rejection control, releases control of the display screen of the first electronic device.

8. The method according to claim 1, characterized in that, The method further includes: When the second system is in a wake-up state, the first system sends target status information to the second system. The target status information is used to indicate the current status of the first system, which includes a call state or a non-call state.

9. The method according to claim 8, characterized in that, Before sending the target status information to the second system, the method further includes: When the second system is in a wake-up state, the second system sends a status acquisition request to the first system, the status acquisition request being used to acquire target status information; Sending target status information to the second system includes: In response to the status acquisition request, the first system sends the target status information to the second system.

10. The method according to claim 9, characterized in that, The second system sends a status acquisition request to the first system, including: The second system receives a second incoming call request sent by a third electronic device, the second incoming call request being used to call the first electronic device; In response to the second incoming call request, the second system sends the status acquisition request to the first system.

11. The method according to any one of claims 8-10, characterized in that, The method further includes: When the target status information indicates that the current status of the first system is the no-call state, the second system outputs a second incoming call notification interface; and / or, When the target status information indicates that the current status of the first system is the call status, the second system sends a hang-up notification or a busy notification to the third electronic device: and / or, When the target status information indicates that the current status of the first system is the call status, the second system sends a call notification to the first system, and the first system notifies the user that there is a new call.

12. The method according to claim 1, characterized in that, The method further includes: In response to a power outage operation, the first system outputs a first power outage interface, which includes at least one called party information stored in the second electronic device. The first system responds to a touch operation on a target called party by sending a call request to the second electronic device, so that the second electronic device calls the electronic device corresponding to the target called party according to the call request, wherein the target called party is one of the at least one called party.

13. The method according to claim 12, characterized in that, The first system outputs a first power-off interface, including: The first system launches the target call application and controls the target call application to display the first outgoing call interface.

14. The method according to claim 12, characterized in that, The first system responds to a power-off operation by outputting a first power-off interface, including: When the second system is in a dormant or off state, the first system responds to the power-off operation by outputting the first power-off interface.

15. The method according to claim 13, characterized in that, The target calling application is a Bluetooth calling application. Before the first system launches the target calling application and controls the target calling application to display the first outgoing call interface, the method further includes: The Bluetooth calling application of the first system obtains at least one called information stored in the second electronic device through a Bluetooth connection with the second electronic device.

16. The method according to claim 12, characterized in that, The first power-out interface includes a switching control, which is used to trigger the second system to output a second power-out interface. The method further includes: The first system responds to a touch operation on the switching control by waking up the second system and sending a power outage notification to the second system; In response to the outgoing call notification, the second system outputs a second outgoing call interface, which includes at least one called party information stored in the first electronic device. In response to a touch of the at least one called information, the called electronic device is called via cellular communication on the first electronic device.

17. The method according to claim 1, characterized in that, The method further includes: The first system and / or the second system run a calling application, which has a first call-out control and a second call-out control. The first call-out control is used to trigger the first system to send a call-out instruction through the target communication connection, so that the second electronic device calls a fourth electronic device according to the call-out instruction. The second call-out control is used to trigger the second system to call a fifth electronic device according to the call-out instruction through cellular communication on the first electronic device.

18. An electronic device, characterized in that, The electronic device supports a first system and a second system, wherein the power consumption of the first system is less than the power consumption of the second system, and the electronic device includes: A first system module is configured to, when the electronic device and the second electronic device establish a target communication connection, receive a first incoming call request sent by the second electronic device through the target communication connection, wherein the first incoming call request is for calling the second electronic device; and... The first system is used to conduct call data transmission with the second electronic device in response to an incoming call request for the first incoming call.

19. An electronic device comprising a memory and a processor, the memory storing a computer program executable on the processor, characterized in that, When the processor executes the program, it implements the steps of the method according to any one of claims 1 to 17.

20. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1 to 17.

Images