Call method, call system, electronic equipment, chip system and storage medium

Abstract

The invention provides a call method, a call system, electronic equipment, a chip system and a storage medium, and relates to the technical field of terminals. The method comprises: a first device triggers a first incoming call prompt in response to a first call request, a second device triggers a second incoming call prompt in response to a second call request, and both the first call request and the second call request are used for requesting a first call. The first device responds to the answering operation, ends the first incoming call reminding, and sends a hang-up signaling to the second device through short-distance wireless communication; and the second device ends the second incoming call reminding in response to the hang-up signaling. Thus, the hang-up signaling can be diffused through short-distance wireless communication, the situation that incoming call reminding is not finished due to the fact that the second device does not receive the hang-up signaling sent by the server is reduced, and then the abnormal situation that the second device conducts incoming call reminding is reduced.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to call methods, call systems, electronic devices, chip systems, and storage media. Background Technology

[0002] When mobile phones and other electronic devices receive an incoming call, they will provide call notifications, such as displaying the caller ID or ringing. To reduce missed calls, call notifications can be implemented across multiple devices using software such as Voice over Internet Protocol (VoIP). For example, if a user has VoIP software installed on both their mobile phone and car infotainment system, a call will be notified via either the mobile phone or the car infotainment system.

[0003] However, in multi-device call notification scenarios, call notification anomalies may occur, affecting user experience. For example, when a VoIP call is received and the call is notified via a mobile phone, the user answers the call on their phone, but the call notification continues on the vehicle's infotainment system. Summary of the Invention

[0004] This application provides a call method, a call system, an electronic device, a chip system, and a storage medium, applicable to the field of terminal technology. It helps reduce abnormal call notifications in electronic devices during multi-device call notification scenarios.

[0005] A first aspect provides a call method applied to a call system consisting of a first device and a second device connected via short-range wireless communication. The method includes: the first device receiving a first call request, the first call request being used to request a first call from a first account; the first device responding to the first call request triggering a first incoming call alert; the second device receiving a second call request, the second call request being used to request the first call, both the first and second call requests originating from a server; the second device responding to the second call request triggering a second incoming call alert; the first device responding to an answer operation ending the first incoming call alert; the first device responding to the answer operation sending a hang-up signal to the second device via short-range wireless communication, the hang-up signal indicating the end of the second incoming call alert; and the second device responding to the hang-up signal ending the second incoming call alert.

[0006] The first account can be the calling party's account, corresponding to account A in the following text; the first device and the second device are called devices from the same called party, corresponding to called device A and called device B in the following text; the server can correspond to the cloud server in the following text. The first call can be a call from the same calling party, corresponding to a call between account A and account B in the following text. This can be understood as follows: when multiple devices from the same called party receive calls from the same calling party, the calls received by those devices are identical.

[0007] In this way, the hang-up signal can be disseminated through short-range wireless communication, which can reduce the abnormal situation of the second device not ending the call reminder for a long time.

[0008] In one possible implementation, both the first and second call requests originate from the server. In this way, the first and second call requests are transmitted over the public network and can be call requests sent to a cloud server.

[0009] In one possible implementation, the first call request is not received via short-range wireless communication; the second call request is also not received via short-range wireless communication. In this way, both the first and second call requests are transmitted over the public network and can be call requests sent to a cloud server.

[0010] In one possible implementation, the unique identifier in the first call request is the same as the unique identifier in the second call request.

[0011] In this way, the unique identifier in the call request can be used to determine whether the first and second devices received the same call. If the first and second devices receive the same call, and the first device answers, the dissemination of the hang-up signal via short-range wireless communication can reduce the possibility of the second device's call being disconnected when the first and second devices receive different calls, thus improving the user experience.

[0012] In one possible implementation, the account on the first device is the same as the account on the second device; or, the calling application on the first device and the calling application on the second device are logged in with the same account.

[0013] In this way, it can be determined whether the first and second devices received the same call by means of the device's account (e.g., system account) or the account of the calling application. When the first and second devices receive the same call, and the first device answers, the dissemination of the hang-up signal through short-range wireless communication can reduce the possibility of the call being disconnected on the second device when the first and second devices receive different calls, thus improving the user experience.

[0014] In one possible implementation, before the first device sends a hang-up signal to the second device, the method further includes: the first device obtaining the account of the second device; or, the first device obtaining the account logged in by the calling application on the second device.

[0015] In this way, the first device obtains the account of the second device, or the account logged into the VoIP application on the second device, to identify whether there is a similar call on the second device.

[0016] In one possible implementation, the call system further includes a third device, which is connected to the second device via short-range wireless communication. The method further includes: the first device sending a third call request to the third device via short-range wireless communication, the third call request being used to request a first call; the third device does not have independent call capability; and the third device responding to the third call request triggers a third incoming call alert.

[0017] The third device can correspond to the short-range wireless communication device B mentioned below.

[0018] In this way, incoming call reminders can be made to devices such as earphones and wristbands that do not have independent call capabilities through short-range wireless communication, enabling multiple devices to receive incoming calls.

[0019] In one possible implementation, the second device has independent calling capability, and after receiving the first call request, the first device does not send a request to the second device to trigger the first call notification via short-range wireless communication.

[0020] The second device may correspond to the short-range wireless communication device A mentioned below.

[0021] This reduces the likelihood of a second device receiving multiple call requests for the same call, and also reduces abnormal situations such as repeated call reminders.

[0022] In one possible implementation, the method further includes: a first device acquiring the status information of a call application in a second device; if the status information of the call application in the second device indicates that it is not in an active state, the first device, after receiving the first call request, sends a fourth call request to the second device via short-range wireless communication, the fourth call request being used to request the first call; the second device responds to the fourth call request by triggering a fourth incoming call reminder.

[0023] In this way, when the second device is not activating the network calling application for various reasons such as network outage, the second device can provide call reminders.

[0024] Secondly, a call method is provided, applied to a first device, the method comprising: the first device receiving a first call request, the first call request being used to request a first call; the first device responding to the first call request triggering a first incoming call alert; the first device responding to an answering operation ending the first incoming call alert; and the first device responding to the answering operation sending a hang-up signaling to a second device via short-range wireless communication, the second device being a device connected to the first device via short-range wireless communication, the hang-up signaling being used to instruct the termination of a second incoming call alert triggered by the second device in response to a second call request, the second call request being used to request the first call.

[0025] In this way, the hang-up signal can be propagated through short-range wireless communication, which can reduce abnormal situations such as long-term unending call reminders from the second device.

[0026] In one possible implementation, the unique identifier in the first call request is the same as the unique identifier in the second call request.

[0027] In one possible implementation, the account on the first device is the same as the account on the second device; or, the calling application on the first device and the calling application on the second device are logged in with the same account.

[0028] In one possible implementation, before sending a hang-up signal to the second device, the method further includes: the first device obtaining the account of the second device; or, the first device obtaining the account logged in by the calling application on the second device.

[0029] In one possible implementation, after receiving a first call request, the first device does not send a request to the second device via short-range wireless communication to trigger an incoming call notification for the first call.

[0030] In one possible implementation, the method further includes: after receiving the first call request, the first device sends a third call request to the third device via short-range wireless communication. The third call request is used to request the first call and to trigger a third incoming call reminder. The third device does not have independent call capability.

[0031] In one possible implementation, the method further includes: a first device obtaining the status information of a call application in a second device; if the status information of the call application in the second device indicates that it is not in an active state, the first device, after receiving the first call request, sends a fourth call request to the second device via short-range wireless communication, the fourth call request being used to request the first call and to trigger a third incoming call reminder.

[0032] Thirdly, a call method is provided, applied to a second device, the method comprising: the second device receiving a second call request, the second call request being used to request a first call; the second device responding to the second call request triggering a second incoming call reminder; the second device receiving a hang-up signaling from a first device, the hang-up signaling being generated by the first device in response to an answering operation for the first call request, the first call request being used to request the first call; and the second device responding to the hang-up signaling ending the second incoming call reminder.

[0033] In one possible implementation, the unique identifier in the first call request is the same as the unique identifier in the second call request.

[0034] In one possible implementation, the account on the first device is the same as the account on the second device; or, the calling application on the first device and the calling application on the second device are logged in with the same account.

[0035] In one possible implementation, before the second device receives the hang-up signaling from the first device, the method further includes: the second device sending its own account to the first device; or, the second device sending the account logged into the calling application on the second device to the first device.

[0036] In one possible implementation, when the calling application in the second device is not active, the second device receives a fourth call request sent by the first device via short-range wireless communication. The fourth call request is sent by the first device after receiving the first call request, and the fourth call request is used to request the first call.

[0037] Fourthly, embodiments of this application provide a call system, including: a first device and a second device; the first device is used to perform the method described in the second aspect or any possible implementation of the second aspect; the second device is used to perform the method described in the third aspect or any possible implementation of the third aspect.

[0038] Fifthly, embodiments of this application provide a communication device, which may be an electronic device or a chip or chip system within an electronic device. The communication device may include a communication unit and a processing unit. When the communication device is an electronic device, the communication unit may be a wireless communication module. The communication unit is used to perform data transmission steps, such as sending (sending hang-up signaling, etc.) or receiving (receiving call requests, receiving hang-up signaling, etc.), to enable the electronic device to implement the methods described in the second aspect or any possible implementation of the second aspect, or to enable the electronic device to implement the methods described in the third aspect or any possible implementation of the third aspect. When the communication device is an electronic device, the processing unit may be a processor. The communication device may also include a storage unit, which may be a memory. The storage unit is used to store instructions, and the processing unit executes the instructions stored in the storage unit to enable the electronic device to implement the methods described in the second aspect or any possible implementation of the second aspect, or to enable the electronic device to implement the methods described in the third aspect or any possible implementation of the third aspect. When the communication device is a chip or chip system within an electronic device, the processing unit may be a processor. The processing unit executes the instructions stored in the storage unit to cause the electronic device to implement the method described in the second aspect or any possible implementation of the second aspect, or to cause the electronic device to implement the method described in the third aspect or any possible implementation of the third aspect. The storage unit may be a storage unit within the chip (e.g., a register, cache, etc.) or a storage unit located outside the chip within the electronic device (e.g., a read-only memory, random access memory, etc.).

[0039] In a sixth aspect, embodiments of this application provide an electronic device, including a processor and a memory, wherein the memory is used to store code instructions, and the processor is used to execute the code instructions to perform the method described in the first aspect or any possible implementation thereof, or to perform the method described in the second aspect or any possible implementation thereof.

[0040] In a seventh aspect, embodiments of this application provide a computer-readable storage medium storing a computer program or instructions that, when executed on a computer, cause the computer to perform the methods described in the second aspect or any possible implementation thereof, or cause the computer to perform the methods described in the third aspect or any possible implementation thereof.

[0041] Eighthly, embodiments of this application provide a computer program product including a computer program, which, when run on a computer, causes the computer to perform the method described in the second aspect or any possible implementation thereof, or causes the computer to perform the method described in the third aspect or any possible implementation thereof.

[0042] Ninthly, this application provides a chip or chip system including at least one processor and a communication interface, the communication interface and the at least one processor being interconnected via a circuit, the at least one processor being configured to run a computer program or instructions to perform the methods described in the second aspect or any possible implementation thereof, or to perform the methods described in the third aspect or any possible implementation thereof. The communication interface in the chip may be an input / output interface, pins, or circuits, etc.

[0043] In one possible implementation, the chip or chip system described above in this application further includes at least one memory storing instructions. The memory can be an internal storage unit of the chip, such as a register or cache, or it can be a storage unit of the chip itself (e.g., read-only memory, random access memory, etc.).

[0044] It should be understood that the second to ninth aspects of this application correspond to the technical solutions of the first aspect of this application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation are similar, and will not be repeated here. Attached Figure Description

[0045] Figure 1 A schematic diagram illustrating a scenario where call notifications are implemented across multiple devices using VoIP software, as provided in this application embodiment;

[0046] Figure 2 A schematic diagram illustrating a scenario for implementing call notifications across multiple devices using Bluetooth communication, provided as an embodiment of this application.

[0047] Figure 3 This is a schematic diagram illustrating a scenario where multiple devices receive call notifications via VoIP software and Bluetooth communication, as provided in an embodiment of this application.

[0048] Figure 4 A flowchart illustrating a possible communication method in an embodiment of this application;

[0049] Figure 5 A flowchart corresponding to one of the possible scenarios provided in the embodiments of this application;

[0050] Figure 6 A schematic diagram of the vehicle system interface corresponding to one of the possible scenarios provided in the embodiments of this application;

[0051] Figure 7 A flowchart corresponding to one of the possible scenarios provided in the embodiments of this application;

[0052] Figure 8 A schematic diagram of the vehicle's interface corresponding to a possible second scenario provided in the embodiments of this application;

[0053] Figure 9A A flowchart illustrating a communication method provided in an embodiment of this application;

[0054] Figure 9B A flowchart illustrating another communication method provided in an embodiment of this application;

[0055] Figure 10 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0056] Figure 11 A flowchart illustrating a communication method provided in an embodiment of this application;

[0057] Figure 12 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0058] Figure 13 This is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0059] To facilitate a clear description of the technical solutions in the embodiments of this application, some terms and technologies involved in the embodiments of this application will be briefly introduced below:

[0060] 1. Public network communication

[0061] Public network communication can be understood as communication conducted through a public network. A public network is a network that allows any device globally to communicate with each other via Internet protocols (such as TCP / IP), for example, the Internet. Public network communication allows data transmission and communication between any devices connected to the Internet.

[0062] 2. Short-range wireless communication

[0063] Short-range wireless communication refers to communication technologies that use radio waves to transmit data over a relatively short distance (e.g., within a range of tens of meters). Short-range wireless communication can include Bluetooth, Near Field Communication (NFC), Zigbee, Ultra-Wideband (UWB), Infrared Data Transmission (IrDA), or Wireless Local Area Networks (e.g., Wi-Fi).

[0064] 3. Electronic equipment

[0065] The electronic devices in this application embodiment may include handheld devices with call functionality, vehicle-mounted devices, etc. For example, some electronic devices include: mobile phones, tablets, PDAs, laptops, mobile internet devices (MIDs), wearable devices (e.g., smartwatches, smart glasses, smart bracelets, or smart jewelry), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, and the Internet of Things (IoT). Terminal devices in IoT systems, terminal devices in 5G networks, or terminal devices in future public land mobile networks (PLMNs) are not limited to this category in the embodiments of this application.

[0066] The electronic devices in the embodiments of this application may also be referred to as: terminal equipment, user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device, etc.

[0067] In this embodiment, the electronic device or various network devices include a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, such as Linux, Unix, Android, iOS, or Windows. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software.

[0068] 4. Other terms

[0069] In the embodiments of this application, terms such as "first" and "second" are used to distinguish identical or similar items with essentially the same function and effect. For example, the first value and the second value are only used to distinguish different values ​​and do not limit their order. Those skilled in the art will understand that terms such as "first" and "second" do not limit the quantity or execution order, and that terms such as "first" and "second" do not necessarily imply that they are different.

[0070] It should be noted that, in the embodiments of this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplarily" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0071] In the embodiments of the present application, "at least one" means one or more, and "multiple" means two or more. "And / or" describes the association relationship of associated objects and indicates that there can be three relationships. For example, A and / or B can represent the situations of: A exists alone, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. "At least one (item)" or similar expressions refer to any combination of these items, including any combination of single item or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, a - b, a - c, b - c, or a - b - c, where a, b, and c can be single or multiple.

[0072] When an electronic device such as a mobile phone receives an incoming call, an incoming call reminder will be given. Currently, multi-device incoming call reminders can be implemented through at least one of the following methods to reduce the situation of missed incoming calls. For example, incoming call reminders for multiple devices under the same account can be implemented through software such as Voice over Internet Protocol (VoIP); the incoming call reminder of an electronic device can be spread to other electronic devices through short-range wireless communication such as Bluetooth, and the other electronic devices are devices connected to the electronic device through short-range wireless communication.

[0073] Exemplarily, taking the VoIP application as an example Figure 1 FIG. is a schematic diagram of a scenario for implementing multi-device incoming call reminders through a VoIP application provided by an embodiment of the present application. As Figure 1 shown, the scenario includes: a calling device 101, a cloud server 102, and a called end 103. The called end 103 may include at least one called device: a watch 103-1, a car machine 103-2, a mobile phone 103-3, etc. The calling device 101 is installed with VoIP software and logged in with account A; the called devices included in the called end 103 are all installed with VoIP applications and logged in with account B. The cloud server 102 is a server for providing VoIP services.

[0074] In the embodiments of the present application, the calling device 101 is used to call the called devices of the called end 103. The calling device 101 can also be referred to as the calling end. The called end 103 is used to receive the call from the calling device 101.

[0075] Both the calling device 101 and the called device of the called terminal 103 are electronic devices with communication functions. The electronic devices can be referred to in the corresponding descriptions above, and will not be elaborated further here. The type of the calling device 101 and the type of the called device of the called terminal 103 can be the same or different; the called terminal 103 can include one or more called devices, and the number of called terminals 103 is not specifically limited here. When the called terminal 103 includes multiple called devices, the types of these multiple called devices can be the same or different, and this is not specifically limited here.

[0076] The cloud server 102 is used to send a call request from the calling device 101 to the called device of the called end 103, so that multiple called devices of the called end 103 can receive call notifications. The cloud server 102 is also used to send a hang-up signal to other called devices of the called end 103 other than the called device after the called device of any called end 103 answers the call, so as to stop the call notifications of other called devices of the called end 103 other than the called device.

[0077] In some embodiments, the media and signaling cloud for VoIP calls can be built on a private or leased server, which enables media negotiation and data transmission between the calling and called devices. During a VoIP call, the cloud server can propagate the call request to at least one called device via the signaling cloud during media negotiation, enabling multi-device call notification. Furthermore, after any called device answers, it can send a hang-up signal to other called devices (excluding the one answering the call) via the cloud server, automatically hanging up for the other called devices.

[0078] However, due to the unreliability of public network communication (e.g., network latency, network interruption, etc.), other called devices (devices other than the receiving device) may not receive the hang-up signal sent by the cloud server for a long time, which may result in other called devices being unable to end the call reminder for a long time.

[0079] The above Figure 1 The scenario shown illustrates how to implement call notifications across multiple devices using a VoIP application. The following section will combine... Figure 2 This paper describes a scenario where short-range wireless communication enables call notifications for multiple devices.

[0080] For example, taking short-range wireless communication such as Bluetooth as an example, Figure 2 This is a schematic diagram illustrating a scenario where Bluetooth communication enables call notifications for multiple devices, as provided in an embodiment of this application. Figure 2 As shown, the scenario includes: calling device 201, cloud server 202, called device 203, and Bluetooth device 204.

[0081] The calling device 201 is used to call the called device 203. The calling device 201 can also be referred to as the calling end. The called device 203 is used to receive the call from the calling device 201. The called device 203 can also be referred to as the called end.

[0082] Both the calling device 201 and the called device 203 are electronic devices with communication functions. The specific electronic devices described above are not detailed here. The types of the calling device 201 and the called device 203 can be the same or different; no specific restrictions are imposed here.

[0083] The cloud server 202 is used to send a call request from the calling device 201 to the called device 203, enabling the called device 203 to provide call notification. The called device 203 is also used to send a call request via Bluetooth communication to the Bluetooth device 204 after receiving a call from the calling device 201, enabling the Bluetooth device 204 to provide call notification. The call request received by the Bluetooth device 204 and the call request received by the called device 203 from the calling device 201 request have the same requested call content.

[0084] After Bluetooth device 204 receives the answer operation, Bluetooth device 204 connects with calling device 201 via called device 203 and cloud server 202. Alternatively, after called device 203 receives the answer operation, called device 203 connects with calling device 201 via cloud server 202.

[0085] However, even when electronic devices support the two methods mentioned above for multi-device call notifications, abnormal situations may occur, such as duplicate call notifications on the called device, or the call being answered on one called device but the call notification not ending on other called devices. The following section will discuss these issues in conjunction with... Figures 3 to 8 The scenario architecture for multi-device call alerts using the two methods described above is explained, along with the normal and abnormal situations in which the called device receives call alerts.

[0086] For example, Figure 3 This illustration shows a scenario where multiple devices receive call notifications via VoIP software and Bluetooth communication, as provided in this application embodiment. Figure 3 As shown, the scenario includes: calling device 301, cloud server 302, and called device 303.

[0087] The calling device 301, cloud server 302, and called terminal 303 can be referred to the corresponding descriptions of the calling device 101, cloud server 102, and called terminal 103 mentioned above, and will not be repeated here.

[0088] Taking the called device 303 as an example, the called device includes: watch 303-1, car infotainment system 303-2 and mobile phone 303-3, and the mobile phone 303-3 and car infotainment system 303-2 are connected via Bluetooth. The mobile phone 303-3 can be the called device 203 mentioned above; the car infotainment system 303-2 can be either the Bluetooth device 204 mentioned above or the called device 203 mentioned above.

[0089] Understandable Figure 3 In the scenario shown, the vehicle infotainment system 303-2, watch 303-1, and mobile phone 303-3 log in using the same account (e.g., account B). When the calling device 301 makes a call for account B, the calling device 301 can send call request 1A, call request 1B, and call request 1C to the mobile phone 303-3, vehicle infotainment system 303-2, and watch 303-1 respectively via cloud server 302. Call request 1A, call request 1B, and call request 1C are all used to request a call between account A and account B. After receiving their respective call requests, the vehicle infotainment system, watch, and mobile phone will all provide call notifications.

[0090] Furthermore, since mobile phone 303-3 and vehicle infotainment system 303-2 are connected via Bluetooth, after receiving call request 1A, mobile phone 303-3 will send call request 2a to vehicle infotainment system 303-2 via Bluetooth communication. Vehicle infotainment system 303-2 may receive two call requests (e.g., call request 1B and call request 2a), and may thus display two incoming call alerts.

[0091] In some embodiments, the call request carries an identifier for the corresponding service. The vehicle-mounted system 303-2 can determine whether to provide a call reminder based on the service identifier. Specifically, call request 1B carries an identifier for a VoIP service, and call request 2a carries an identifier for a short-range wireless communication service. Upon receiving call request 1B, the vehicle-mounted system 303-2 can disable call reminders for call request 2a corresponding to the short-range wireless communication service identifier. Upon receiving both call request 1B and call request 2a, the vehicle-mounted system 303-2 may disable call reminders for call request 2a. This reduces repeated reminders for the same incoming call.

[0092] In this embodiment of the application, if multiple called devices on the same called end receive calls from the same calling end, then the calls corresponding to these multiple called devices are considered to be the same. For example, Figure 3 In the scenario shown, call requests 1A, 1B, 1C, and 2a all request the same call.

[0093] For example, Figure 4This application provides a schematic diagram of a call flow, taking the device of account A as the calling device and the called device of account B as an example, including mobile phones and in-vehicle systems. Figure 4 As shown, the mobile phone and the vehicle's infotainment system are connected via short-range wireless communication. Taking the vehicle's infotainment system connecting a caller's device as an example, the specific process includes:

[0094] S401. In response to a call operation for account B, the calling device sends a call request (e.g., an invite request) to the cloud server. The call request carries account B.

[0095] Adaptively, the cloud server can confirm that the device corresponding to account B is the called device based on the correspondence between the account and the device.

[0096] S402, The cloud server sends call requests (e.g., ringing requests) to the mobile phone and the vehicle system.

[0097] Specifically, S402 can include: S402-1 and S402-2. S402-1: The cloud server sends a call request 1A to the mobile phone; S402-2: The cloud server sends a call request 1B to the vehicle's infotainment system.

[0098] Call Request 1A and Call Request 1B are used to request the same call. Call Request 1A and Call Request 1B may include: an identifier for the VoIP service and an identifier for the calling device. The VoIP service identifier indicates that the call type is a VoIP call.

[0099] S403. After receiving call request 1B, the vehicle's infotainment system will issue an incoming call reminder.

[0100] S404. After receiving call request 1A, the mobile phone will issue a call reminder.

[0101] S405. After receiving call request 1A, the mobile phone sends call request 2a to the vehicle's infotainment system.

[0102] Call request 2a includes: an identifier for the mobile phone and an identifier for a short-range wireless communication service. The identifier for the short-range wireless communication service indicates that the call type is a short-range wireless communication call (e.g., a Bluetooth call). The call requested by call request 2a is the same as the call requested by call request 1A.

[0103] S406. After receiving call request 2a following S403, the vehicle's infotainment system does not provide call notification for call request 2a.

[0104] Understandably, since the vehicle system does not issue a call notification corresponding to call request 2a because call request 1B carrying the identifier of VoIP service was received before call request 2a.

[0105] S407, the vehicle's infotainment system responds to the call answering operation and ends the call reminder.

[0106] S408, in response to an answering operation, the vehicle's infotainment system sends a message (e.g., answer signaling) to the cloud server to indicate that the call should be answered.

[0107] In this embodiment of the application, the answering operation in S407 and the answering operation in S408 are the same operation.

[0108] S409. After receiving a message indicating that the call should be answered, the cloud server sends a message indicating that the call should be answered (e.g., answer signaling) to the calling device.

[0109] S410. In response to the message indicating that the call has been answered, the calling device sends a response message (OK signaling) to the cloud server to notify the cloud server that the call has been received.

[0110] S411. After receiving the response message from the calling device, the cloud server sends a message to the vehicle's infotainment system to indicate that the connection has been established (e.g., a connect signaling message).

[0111] S412. After receiving a message indicating that the call has been connected, the vehicle-mounted unit begins a conversation with the calling device.

[0112] S413. After receiving a response message from the calling device, the cloud server sends a message to the mobile phone indicating that the call should be disconnected (e.g., disconnect signaling).

[0113] In this embodiment of the application, the response message in S413 and the response message in S411 are the same message.

[0114] S414. The mobile phone responds to a message indicating disconnection (e.g., disconnect signaling) and ends the call reminder.

[0115] S415, the vehicle's infotainment system responds to the hang-up operation and ends the call.

[0116] S416. In response to a hang-up operation, the vehicle's infotainment system sends a message (e.g., a disconnect signaling) to the cloud server to indicate that the device has been hung up.

[0117] S417. The cloud server sends a message to the calling device indicating that the connection has been terminated (e.g., disconnect signaling).

[0118] S418. The calling device terminates the call after receiving a message indicating that the call should be hung up.

[0119] from Figure 4As shown in the flowchart, when the vehicle's system receives call request 1B, it does not issue a call notification for call request 2a. This reduces repeated notifications for the same incoming call.

[0120] However, due to the unreliability of public network communication, the time when the mobile phone receives call request 1A and the time when the vehicle's system receives call request 1B may differ, which may lead to abnormal call notifications on the vehicle's system. The following section combines... Figure 5 and Figure 6 Explain the possible anomaly, and combine it with Figure 7 and Figure 8 The second possible anomaly will be explained.

[0121] In one possible abnormal scenario, the vehicle's infotainment system first receives call request 1B. After the user answers the call through the vehicle's infotainment system, the cloud server 302 sends a hang-up signal to the mobile phone to end the call notification. If the vehicle's infotainment system receives call request 2a during the period between the call being answered and the mobile phone receiving the hang-up signal, a situation may occur where the call is answered but a call notification is still in effect.

[0122] For example, Figure 5 This is a flowchart illustrating the call process for a possible abnormal situation, taking device A as the calling device and device B as the called end, including mobile phones and in-vehicle systems as examples. Figure 5 As shown, the mobile phone and the vehicle's infotainment system are connected via short-range wireless communication. Taking the vehicle's infotainment system connecting a caller's device as an example, the specific process includes:

[0123] S501. In response to a call operation for account B, the calling device sends a call request (e.g., an invite request) to the cloud server. The call request carries account B.

[0124] Adaptively, the cloud server can confirm that the device corresponding to account B is the called device based on the correspondence between the account and the device.

[0125] S502, the cloud server sends call requests (e.g., ringing requests) to mobile phones and vehicle systems.

[0126] Specifically, S502 can include: S502-1 and S502-2. S502-1, the cloud server sends a call request 1A to the mobile phone; S502-2, the cloud server sends a call request 1B to the vehicle's infotainment system.

[0127] Call Request 1A and Call Request 1B can be referred to the above. Figure 4 The corresponding explanations in the document will not be repeated here.

[0128] S503. After receiving call request 1B, the vehicle's infotainment system will issue a call reminder for call request 1B.

[0129] S504, the vehicle's infotainment system responds to the call answering operation and ends the call reminder.

[0130] S505, in response to an answering operation, the vehicle's infotainment system sends a message (e.g., answer signaling) to the cloud server to indicate that the call should be answered.

[0131] In this embodiment of the application, the answering operation in S505 and the answering operation in S504 are the same operation.

[0132] S506. After receiving a message indicating that the call should be answered, the cloud server sends a message indicating that the call should be answered (e.g., answer signaling) to the calling device.

[0133] S507. In response to the message indicating that the call has been answered, the calling device sends a response message (OK signaling) to the cloud server to notify the cloud server that the call has been received.

[0134] After receiving a response message from the calling device, the S508 cloud server sends a message (e.g., connect signaling) to the vehicle's infotainment system to indicate that the connection has been established.

[0135] S509. After receiving a message indicating that the call has been connected, the vehicle-mounted unit begins a conversation with the calling device.

[0136] After receiving a response message from the calling device, the S510 cloud server sends a message to the mobile phone indicating that the call should be disconnected (e.g., disconnect signaling).

[0137] In this embodiment of the application, the response message in S510 and the response message in S509 are the same message.

[0138] S511: After S504 and before S510, the mobile phone receives call request 1A and then provides call reminder.

[0139] S512. After receiving call request 1A, the mobile phone sends call request 2a to the vehicle's infotainment system.

[0140] Call request 2a includes: an identifier for the mobile phone and an identifier for a short-range wireless communication service. The identifier for the short-range wireless communication service indicates that the call type is a short-range wireless communication call (e.g., a Bluetooth call).

[0141] S513. After receiving call request 2a after S504, the vehicle's infotainment system will provide call reminder based on call request 2a.

[0142] S514, the vehicle's infotainment system responds to the call reminder hang-up operation in S513, and ends the call reminder.

[0143] In some embodiments, the vehicle's infotainment system sends a message to the mobile phone indicating that the call should be disconnected, and the mobile phone ends the call notification.

[0144] In some embodiments, the mobile phone and vehicle system can also end the incoming call reminder via S515 and S516.

[0145] S515: The mobile phone responds to the message in S508 indicating that the call has been hung up, and ends the call reminder.

[0146] In response to the message indicating call termination in S508, the mobile phone sends a message to the vehicle's infotainment system indicating call end. Adaptively, the vehicle's infotainment system terminates call notification upon receiving this message.

[0147] from Figure 5 As shown in the flowchart, after the vehicle's infotainment system answers an incoming call based on call request 1B, if it receives call request 2a, it will issue a call notification based on call request 2a. For the same call (same incoming call), the vehicle's infotainment system may show a call notification even though the call has been answered.

[0148] For example, call notifications include displaying a caller ID on the interface. Figure 6 This is a schematic diagram of the in-vehicle infotainment system interface corresponding to a possible abnormal situation. Taking the scenario of in-vehicle navigation before receiving an incoming call as an example, such as... Figure 6 As shown, the car's infotainment system can display the following information before receiving an incoming call: Figure 6 The interface shown in Figure 'a' includes windows 601 and 602. Window 601 can display icons for navigation applications (11), messaging applications (12), phone applications (13), and other functions (14) for accessing more features. Window 602 can display maps, navigation routes, and information indicating the location of the electronic device.

[0149] After the vehicle's infotainment system receives call request 1B, it can display... Figure 6 The interface shown in b is shown in the image. This interface includes windows 601 and 602. (The last two lines appear to be incomplete and possibly contain errors.) Figure 6 Compared to the interface shown in 'a', Figure 6 The interface shown in b, window 602, also includes: call notification 21. Call notification 21 includes: the caller's device identifier, answer control 22, and hang-up control.

[0150] In response to a trigger operation on the answer control 22, the vehicle's infotainment system displays... Figure 6 The interface shown in 'c' is as follows. This interface includes: a hang-up notification 23. The hang-up notification includes: the caller's device identifier and hang-up controls, but does not include: answer controls.

[0151] When the vehicle's infotainment system receives call request 2a, it displays... Figure 6The interface shown in 'd' is as follows. This interface includes: hang-up notification 23 and incoming call notification 24. Incoming call notification 24 includes: the caller's device identifier, answer control, and hang-up control.

[0152] When the vehicle's infotainment system receives a trigger operation on the hang-up control in call notification 24, the system displays... Figure 6 The interface shown in 'c' is included. This interface includes a hang-up notification (23), but does not include an incoming call notification (24).

[0153] Thus, for the same incoming call, the vehicle's infotainment system may show a call notification even though the call has been answered.

[0154] In the second possible abnormal scenario, the vehicle's infotainment system first receives call request 2a and displays the call notification for call request 2a. When the system receives call request 1B, it will disable the call notification for call request 2a and switch to the call notification for call request 1B. Because the call notification changes, the user may perceive that the system has received two incoming calls.

[0155] For example, Figure 7 This is a flowchart illustrating the call process for a possible exception (Scenario 2), taking account A as the calling device and account B as an example where the devices include mobile phones and in-vehicle systems. Figure 7 As shown, the mobile phone and the vehicle's infotainment system are connected via short-range wireless communication. Taking the vehicle's infotainment system connecting a caller's device as an example, the specific process includes:

[0156] S701. In response to a call operation for account B, the calling device sends a call request (e.g., an invite request) to the cloud server. The call request carries account B.

[0157] Adaptively, the cloud server can confirm that the device corresponding to account B is the called device based on the correspondence between the account and the device.

[0158] S702, The cloud server sends call requests (e.g., ringing requests) to the mobile phone and the vehicle system.

[0159] Specifically, S702 can include: S702-1 and S702-2. S702-1: The cloud server sends a call request 1A to the mobile phone; S702-2: The cloud server sends a call request 1B to the vehicle's infotainment system.

[0160] Call requests can be made in accordance with the above. Figure 4 The corresponding explanations in the document will not be repeated here.

[0161] S703: After receiving call request 1A, the mobile phone will provide call reminder.

[0162] S704. After receiving call request 1A, the mobile phone sends call request 2a to the vehicle's infotainment system.

[0163] Call request 2a includes: an identifier for the mobile phone and an identifier for a short-range wireless communication service. The identifier for the short-range wireless communication service indicates that the call type is a short-range wireless communication call (e.g., a Bluetooth call).

[0164] S705: After receiving call request 2a, the vehicle's infotainment system will provide a call reminder for call request 2a.

[0165] S706: After receiving call request 1B after S705, the vehicle-mounted unit terminates call request 2a and provides call reminder based on call request 1B.

[0166] S707: The vehicle's infotainment system responds to the call answering operation and ends the call reminder.

[0167] S708, in response to an answering operation, the vehicle's infotainment system sends a message (e.g., answer signaling) to the cloud server to indicate that the call should be answered.

[0168] In this embodiment of the application, the answering operation in S708 and the answering operation in S707 are the same operation.

[0169] S709. After receiving a message indicating that the call should be answered, the cloud server sends a message indicating that the call should be answered (e.g., answer signaling) to the calling device.

[0170] S710: In response to the message indicating that the call has been answered, the calling device sends a response message (OK signaling) to the cloud server to notify the cloud server that the call has been received.

[0171] After receiving a response message from the calling device, the cloud server sends a message (e.g., connect signaling) to the vehicle's infotainment system.

[0172] S712. After receiving a message indicating that the call has been connected, the vehicle's infotainment system begins a conversation with the calling device.

[0173] S713: After receiving a response message from the calling device, the cloud server sends a message to the mobile phone indicating that the call should be disconnected (e.g., disconnect signaling).

[0174] In this embodiment of the application, the response message in S712 and the response message in S711 are the same message.

[0175] S714, the mobile phone responds to a message indicating disconnection (e.g., disconnect signaling) and ends the call reminder.

[0176] S715, the vehicle's infotainment system responds to the hang-up operation and ends the call.

[0177] S716, in response to a hang-up operation, the vehicle's infotainment system sends a message (e.g., a disconnect signal) to the cloud server to indicate the hang-up.

[0178] S717, The cloud server sends a message to the calling device A to indicate that the call should be disconnected.

[0179] S718. After receiving a message indicating that the caller has hung up, the calling device ends the call.

[0180] from Figure 7 As can be seen from the process shown, if the vehicle's infotainment system receives call request 2a first and then call request 1B, it may switch to call reminder.

[0181] For example, Figure 8 This is a schematic diagram of the vehicle's infotainment system interface corresponding to a possible abnormal situation (Scenario 2). Taking the scenario of the vehicle's navigation system before receiving an incoming call as an example, such as... Figure 8 As shown, the car's infotainment system can display the following information before receiving an incoming call: Figure 8 The interface shown in Figure 'a' includes windows 601 and 602. Window 601 can display icons for navigation applications (11), messaging applications (12), phone applications (13), and other functions (14) for accessing more features. Window 602 can display maps, navigation routes, and information indicating the location of the electronic device.

[0182] After the vehicle's infotainment system receives a call request 2a from the mobile phone, the system can display... Figure 8 The interface shown in b is shown in the image. This interface includes windows 601 and 602. (The last two lines appear to be incomplete and possibly contain errors.) Figure 8 Compared to the interface shown in 'a', Figure 8 The interface shown in b, window 602, also includes: caller ID 24. Caller ID 24 includes: the caller's device identifier, answer control, and hang-up control.

[0183] After the vehicle's infotainment system receives call request 1B from the cloud server, it can display the following information in sequence. Figure 8 The interface shown in c and Figure 8 The interface shown in d is used to switch the call notification corresponding to call request 2a to the call notification corresponding to call request 1B.

[0184] in, Figure 8 The interface shown in 'c' does not include: Caller ID 24 and Caller ID 21. Figure 8 The interface shown in d includes: caller ID 21, but does not include: caller ID 24.

[0185] This means that the car's infotainment system might display two call notifications for the same incoming call, which could lead users to mistakenly believe that there are two calls coming in.

[0186] In view of this, embodiments of this application provide a call method, a call system, an electronic device, a chip system, and a storage medium. The called device can respond to an answer operation by sending a hang-up signal to a target device via short-range wireless communication. The target device is a device connected to the called device via short-range wireless communication. This can terminate the call reminder for the target device, reducing the likelihood of the target device failing to terminate the call reminder for an extended period due to not receiving the hang-up signal from the server, thereby reducing abnormal situations where the target device fails to provide call reminders.

[0187] For example, Figure 9A This is a flowchart illustrating a communication method provided in an embodiment of this application. Taking a call system including: a calling device, a cloud server, called device A, and called device B as an example, ... Figure 9A As shown, the method includes: called device A and called device B are connected via short-range wireless communication. Both called device A and called device B have a VoIP application (also known as VoIP software or VoIP application) installed and are logged into account B. Called device A and called device B can be any type of electronic device, and no specific limitation is made here.

[0188] S801. In response to a call operation for the device corresponding to account B, the calling device sends a call request to the cloud server.

[0189] The call request included account B.

[0190] Call operations are used to instruct someone to make a phone call. For the device corresponding to account B, a call operation can be a click on the identifier of account B displayed in the VoIP application interface (e.g., account B, the name corresponding to account B, etc.), a voice operation instructing someone to make a call to account B in the VoIP application, or any other type of operation; no specific limitations are made here.

[0191] S802. After receiving a call request from the calling device, the cloud server sends call requests to both called device A and called device B.

[0192] Specifically, S802 can include S802-1 and S802-2. S802-1: The cloud server sends call request 1A to the called device A; S802-2: The cloud server sends call request 1B to the called device B. The call requested by call request 1A is the same as the call requested by call request 1B.

[0193] In this embodiment, the cloud server can manage the devices corresponding to account B. For example, the cloud server stores the correspondence between accounts and devices. Any account can correspond to at least one device. Through this correspondence and call requests, the cloud server can determine each called device and then send call requests to each called device.

[0194] The call request may include at least one of the following: a VoIP service identifier, an identifier for the calling device A, and a unique identifier. The unique identifier is used to uniquely identify the call request corresponding to the calling device, and can also be understood as: a call between a device logged into account A and a device logged into account B.

[0195] In some embodiments, the cloud server generates a read-only memory identifier (ROMID) corresponding to a call request in response to a call request from the calling device. The call requests sent by the cloud server to each called device corresponding to the same called party include a unique identifier. Subsequent called devices can use the unique identifier in the call request to confirm whether it is the same call.

[0196] S803. After receiving call request 1A, the called device A will issue a call reminder.

[0197] The embodiments of this application do not impose specific restrictions on the order of S803 and S804.

[0198] S804. The called device B responds to call request 1B and provides a call reminder.

[0199] Incoming call alerts are used to notify the user that the called device A has an incoming call. Incoming call alerts may include at least one of the following: interface display, ringing, etc., without specific limitations here.

[0200] S805, The called device B responds to the answering operation and ends the call reminder.

[0201] The answer action is used to indicate that an incoming call should be answered. The answer action can be a click operation on the answer control, a voice operation to indicate that the call should be answered, or any other type of operation; there are no specific limitations here.

[0202] S806. In response to the answering operation, the called device B sends a hang-up signal to the called device A via short-range wireless communication.

[0203] In this embodiment of the application, the answering operation in S806 and the answering operation in S805 are the same operation.

[0204] S807. After receiving the hang-up signal, the called device A ends the call reminder.

[0205] In this way, called device A can receive the hang-up signal from called device B, thereby ending the call reminder for the same call and reducing the situation where the call reminder for called device A is not ended for a long time.

[0206] In the above Figure 9A Based on the illustrated embodiment, after receiving the answer operation, the called device B can also verify whether the call information of the called device A is the same as the call information of the called device B, in order to confirm whether the called device A and the called device B will receive the same call request, and thus determine whether to send a hang-up signaling. The following is in conjunction with... Figure 9B The specific implementation process in the call scenario is explained.

[0207] For example, Figure 9B This is a flowchart illustrating another communication method provided in an embodiment of this application. Taking a call system including: a calling device, a cloud server, called device A, and called device B as an example, ... Figure 9B As shown, the interaction process includes: called device A and called device B connect via short-range wireless communication. Both called device A and called device B have VoIP applications (also known as VoIP software or VoIP applications) installed, and both are logged into account B.

[0208] S901. In response to a call operation targeting the device corresponding to account B, the calling device sends a call request to the cloud server.

[0209] The call request includes account B. The call operation can be referred to the corresponding explanation in S801 above, and will not be repeated here. S902: After receiving the call request from the calling device, the cloud server sends call requests to both called device A and called device B.

[0210] Specifically, S902 can include S902-1 and S902-2. S902-1: The cloud server sends call request 1A to the called device A; S902-2: The cloud server sends call request 1B to the called device B. The call requested by call request 1A is the same as the call requested by call request 1B.

[0211] S903. After receiving call request 1A, the called device A will issue a call reminder.

[0212] The embodiments of this application do not impose specific restrictions on the order of S903 and S904.

[0213] S904. The called device B responds to call request 1B and provides a call reminder.

[0214] For call reminders, please refer to the above instructions; they will not be repeated here.

[0215] S905, The called device B responds to the answering operation and ends the call reminder.

[0216] The instructions for answering calls are as described above and will not be repeated here.

[0217] S906. In response to the call answering operation, the called device B sends a message to the cloud server to indicate that the call should be answered.

[0218] In this embodiment of the application, the answering operation in S905 and the answering operation in S906 are the same operation.

[0219] S907. After receiving a message indicating that the call should be answered, the cloud server sends a message indicating that the call should be answered (e.g., answer signaling) to the calling device.

[0220] S908: In response to the message indicating that the call should be answered, the calling device sends a response message (OK signaling) to the cloud server to notify the cloud server of the message indicating that the call should be answered.

[0221] S909: After receiving a response message from the calling device, the cloud server sends a message (e.g., connect signaling) to the called device B to indicate that the connection has been established.

[0222] S910. After receiving the message indicating that the call has been connected, the called device B begins a conversation with the calling device.

[0223] S911. After receiving a message indicating that the call has been connected, the called device B determines whether the call information of the device connected to the short-range wireless communication connection is the same as its own call information.

[0224] Call information may include: the account logged into the VoIP application on the device, or it may include: a unique identifier in the call request received by the device.

[0225] In this embodiment, the called device B may acquire the call information of the called device A when establishing a short-range wireless communication connection; or it may acquire the call information of the called device A after receiving an answer operation; or it may acquire the call information of the called device A after receiving a message indicating that the call has been connected. This embodiment does not specify the exact time at which the called device B acquires the call information of the called device A.

[0226] In some embodiments, the called device B can send a request to the called device A via short-range wireless communication to instruct it to obtain call information. Upon receiving the request, the called device A sends its call information to the called device B.

[0227] In other embodiments, after establishing a short-range wireless communication connection with called device B, called device A can proactively send its call information to called device B. This application does not specifically limit the time or method by which called device B obtains the call information of called device A.

[0228] In some embodiments, the called device B can obtain the call information of the called device A through a cloud server or other means. This application does not specifically limit the method by which the called device B obtains the call information of the called device A.

[0229] S912. When the call information of the called device B is the same as that of the called device A, the called device B sends a hang-up signal to the called device A through short-range wireless communication.

[0230] In some embodiments, the account logged into the VoIP application in called device A is the same as the account logged into the VoIP application in called device B, or the unique identifier in the call request received by called device B is the same as the unique identifier in the call request received by called device B, and called device B sends a hang-up signaling to called device A through short-range wireless communication.

[0231] In this way, the VoIP call can be ended via short-range wireless communication, thus terminating the call notification for the VoIP call in the called device B.

[0232] Understandably, if the account logged into the VoIP application on called device A is different from the account logged into the VoIP application on called device B, or if the unique identifier in the call request received by called device B is different from the unique identifier in the call request received by called device B, then called device B will not send a hang-up signal to called device A via short-range wireless communication.

[0233] This can reduce the chances of VoIP calls being abnormally disconnected in the called device B.

[0234] S913. After receiving the response message from the calling device, the cloud server sends a message to the called device A to indicate that the connection has been terminated (e.g., disconnect signaling).

[0235] In this embodiment, S913 and S909 respond to the same response message. The called device B can execute S913 first and then S909; or execute S913 and S909 simultaneously. The specific order of S913 and S909 is not limited here.

[0236] S914. After receiving the hang-up signal, the called device A ends the call reminder.

[0237] The called device A can end the call reminder after receiving the hang-up signal in S912 or S913.

[0238] It's understandable that the communication between called device A and called device B is short-range wireless communication, while the communication between the cloud server and called device A is public network communication. The latency of short-range wireless communication is typically lower than that of public network communication, meaning called device A may receive the hang-up signal in the S912 first, thus shortening the delay in ending the call notification for called device A. Furthermore, verifying the consistency of call information reduces the likelihood of VoIP calls being disconnected on called device A in scenarios with differing call information, improving the user experience.

[0239] In conclusion, Figure 9B In the illustrated embodiment, after the called device B answers the call, the hang-up signal can be propagated through short-range wireless communication, which can reduce the abnormal situation of other called devices not receiving call reminders for a long time.

[0240] Understandable Figure 9A and Figure 9B The illustrated embodiment uses the example of called device B answering the call. If called device A answers, called device A can also determine whether the call information of the device connected to it via short-range wireless communication is the same as its own call information. If the call information of called device B is the same as that of called device A, a hang-up signal is sent to called device B to end the call reminder for called device B. The specific process is the same as described above. Figure 9A and Figure 9B The process for the called device B to answer the call is similar and will not be described in detail here.

[0241] The above Figure 9A and Figure 9B The illustrated embodiment is based on the example of the called device answering an incoming call (answering a call). Even when the called device provides a call reminder, it may also hang up the call (hang up the phone). In this hang-up scenario, a hang-up signal can also be sent via short-range wireless communication. For example, using the above... Figure 9B Taking called device A and called device B as an example, after receiving call request 1B, called device B can respond to the hang-up operation by sending a hang-up signal to called device A via short-range wireless communication, causing called device A to end the call reminder for call request 1A. This shortens the delay in ending the call reminder for called device A.

[0242] The above Figure 9BThe illustrated embodiment uses the account of a VoIP application as an example to determine if a call is the same. However, this determination can be achieved through any other method, such as the device's account. No specific limitation is made here. If two called devices have the same account, and one device answers the call, that device can send a hang-up signal to the other device via short-range wireless communication to end the other device's call notification. The specific process is the same as described above. Figure 9B The process shown is similar and will not be described in detail here.

[0243] It is understandable that the above Figure 9A and Figure 9B The VoIP application mentioned here is one type of calling application. However, it can be replaced with other calling applications, such as the electronic device's own calling application, or the calling application corresponding to the electronic device's account (also known as the application corresponding to the system account). No specific limitations are made here.

[0244] The following is combined with Figure 10 and Figure 11 Another communication method provided in the embodiments of this application will be described. This communication method can solve the problem of repeated incoming call reminders in another abnormal situation provided in the embodiments of this application.

[0245] For example, Figure 10 This is a flowchart illustrating a communication method provided in an embodiment of this application. Taking a call system including: a calling device, a cloud server, a called device A, and a short-range wireless communication device A (also referred to as short-range communication device A) as an example, ... Figure 10 As shown, the method includes: the called device A and the short-range wireless communication device A are connected via short-range wireless communication. Both the called device A and the short-range wireless communication device A have VoIP applications installed and are logged into account B.

[0246] S1001, In response to a call operation targeting the device corresponding to account B, the calling device sends a call request to the cloud server.

[0247] S1002. After receiving a call request from the calling device, the cloud server sends call requests to both the called device A and the short-range wireless communication device A.

[0248] Specifically, S1002 may include: S1002-1 and S1002-2. S1002-1: The cloud server sends a call request 1A to the called device A; S1002-2: The cloud server sends a call request 1B to the short-range wireless communication device A.

[0249] S1003. After receiving call request 1A, the called device A will issue a call reminder.

[0250] S1001 to S1003 can be referred to the above. Figure 9A The corresponding explanations will not be repeated here.

[0251] S1004. After receiving call request 1B, short-range wireless communication device A provides a call reminder.

[0252] The embodiments of this application do not impose specific restrictions on the order of S1003 and S1004.

[0253] S1005. The called device A determines whether the call information of the device connected to the short-range wireless communication connection is the same as its own call information.

[0254] Call details can be found above. Figure 9B The corresponding descriptions in the illustrated embodiments will not be repeated here.

[0255] If the call information of the called device A is different from that of the short-range wireless communication device A, the called device executes S1006; if the call information of the called device A is the same as that of the short-range wireless communication device A, the called device does not execute S1006.

[0256] Thus, when the short-range wireless communication device A and the called device A are the same called party, the short-range wireless communication device A will not receive call request 2a and will not issue the call notification corresponding to call request 2a, thereby reducing the likelihood of the short-range wireless communication device A repeatedly issuing call notifications. When the short-range wireless communication device A and the called device A are different called parties, call notifications can be issued through the short-range wireless communication device A.

[0257] S1006. The called device A sends a call request 2a to another short-range wireless communication device A via short-range wireless communication. The call requested by call request 2a is the same as the call requested by call request 1A.

[0258] In some embodiments, the called device A can also determine whether to send S1006 based on the activation status of the VoIP service in the short-range wireless communication device A (also known as the activation status of the VoIP application). Specifically, if the call information of the called device A is the same as the call information of the short-range wireless communication device A, and the VoIP service in the short-range wireless communication device A is active, the called device A does not execute S1006; if the call information of the called device A is the same as the call information of the short-range wireless communication device A, and the VoIP service in the short-range wireless communication device A is not active, the called device A executes S1006.

[0259] In this way, when short-range wireless communication device A fails to activate VoIP service due to network outages or other reasons, short-range wireless communication device A can still provide call reminders.

[0260] In this embodiment, the called device A can obtain the activation status of the VoIP service in the short-range wireless communication device A from the short-range wireless communication device A itself. Alternatively, it can obtain the activation status from a cloud server. No specific limitations are imposed here.

[0261] For example, called device A can send a request to short-range wireless communication device A to indicate the availability of VoIP service status information. Upon receiving the request, called device A sends the VoIP service status information to short-range wireless communication device A. This status information indicates the activation status of the VoIP service. This application embodiment does not specifically limit the method, timing, or specific implementation of the called device A obtaining the status information from short-range wireless communication device A.

[0262] In some embodiments, the called device may not determine the VoIP application's account and activation status. Specifically, if a VoIP application is installed on a short-range communication device, the called device will not send a call request 2a to that short-range communication device via short-range wireless communication. For example, the call system may not execute S1005 to S1007 as described above. If the called device A has a VoIP application installed, the called device A will not send a call request 2a to the short-range wireless communication device A via short-range wireless communication. In this way, the short-range wireless communication device A will not receive call request 2a, thereby reducing the likelihood of the short-range wireless communication device A repeatedly reminding users of incoming calls and reducing the occurrence of call reminders after the call is connected.

[0263] The above Figure 10 The illustrated embodiment uses a short-range communication device with independent call capability as an example to illustrate the call method provided in this application. The following description, in conjunction with... Figure 11 The communication method provided in the embodiments of this application is described for situations where short-range communication devices do not have independent communication capabilities.

[0264] For example, Figure 11 This is a flowchart illustrating a communication method provided in an embodiment of this application. Taking a call system including: a calling device, a cloud server, a called device A, and a short-range wireless communication device B (also referred to as short-range wireless communication device B) as an example, ... Figure 11 As shown, the method includes: the called device A and the short-range wireless communication device B are connected via short-range wireless communication. The called device A has a VoIP application installed and is logged into account B.

[0265] S1101. In response to a call operation targeting the device corresponding to account B, the calling device sends a call request to the cloud server.

[0266] S1102. After receiving a call request from the calling device, the cloud server sends a call request 1A to the called device A.

[0267] S1103. After receiving call request 1A, the called device A will issue a call reminder.

[0268] S1101 to S1103 can be referred to the above. Figure 9A The corresponding explanations will not be repeated here.

[0269] S1104. The called device A determines whether the device with the short-range wireless communication connection has independent call capability.

[0270] In some embodiments, the called device A can determine whether it has independent calling capability by the type and model of the short-range communication device.

[0271] For example, taking the determination of whether a device has independent calling capability by its category as an example, when the short-range communication device is a vehicle-mounted device, a watch, or similar device, the called device A confirms that the device has independent calling capability; when the short-range communication device is a wristband, a headset, or similar device, the called device A confirms that the device does not have independent calling capability.

[0272] The called device A can perform the above actions on devices with independent calling capabilities. Figure 10 S1005. The called device A can perform the following S1105 on a device that does not have independent calling capability.

[0273] S1105. When the short-range wireless communication device B does not have independent call capability, the called device A sends a call request 2b to the short-range wireless communication device B via short-range wireless communication. The call requested by call request 2b is the same as the call requested by call request 1A.

[0274] S1106. After receiving call request 2b, the short-range wireless communication device B provides a call reminder.

[0275] In this way, incoming call notifications can be made for devices that do not have independent call capabilities through short-range wireless communication.

[0276] It is understandable that the called device in a communication system can achieve the above. Figure 9A or Figure 9B The call method shown can also achieve the above. Figure 10 or Figure 11 The method shown above. For example, the above... Figures 9A to 11The called device A in the above can be the same device. Figure 9A or Figure 9B The called device B in the above, and the above Figure 10 The short-range wireless communication device A in the text can be the same device or different devices; no specific limitation is made here.

[0277] It should be understood that the above Figures 9A to 11 This explanation uses the example of two devices providing call alerts for the same incoming call in a communication system as an example. A communication system can also include more devices. For instance, the communication system may include the calling device, called device A, short-range wireless communication device A, and short-range wireless communication device B as described in the above embodiments. This application does not specifically limit the number of devices providing call alerts in the communication system.

[0278] It should be understood that the above embodiments are illustrated using a VoIP application for multi-device call alerts. In some embodiments, multi-device call alerts can also be achieved through other telephony applications on the device; this is not specifically limited here. The account of the VoIP application can also be replaced with the system account logged into the device, or other identifiers indicating the same called party device; this is not specifically limited here.

[0279] The call method according to the embodiments of this application has been described above. The apparatus for performing the above method provided in the embodiments of this application is described below. Those skilled in the art will understand that the methods and apparatus can be combined with and referenced by each other, and the related apparatus provided in the embodiments of this application can perform the steps in the above method.

[0280] like Figure 12 As shown, Figure 12 This is a schematic diagram of a communication device provided in an embodiment of this application. The communication device may be an electronic device in the embodiment of this application, or it may be a chip or chip system within an electronic device.

[0281] like Figure 12 As shown, the communication device can be used in communication equipment, circuits, hardware components, or chips. The communication device includes a display unit 1201, a processing unit 1202, and a communication unit 1203. The display unit 1201 supports the display steps of the communication method; the processing unit 1202 supports the information processing steps of the communication device; and the communication unit 1203 supports interaction between the communication device and other devices.

[0282] For example, when the communication device is an electronic device, the communication unit 1203 can be a communication interface or interface circuit. When the communication device is a chip or chip system within an electronic device, the communication unit 1203 can be a communication interface. For example, the communication interface can be an input / output interface, pins, or circuits, etc.

[0283] The communication devices described in the embodiments of this application may include the units described in the above embodiments.

[0284] Specifically, the processing unit 1202 can be integrated with the display unit 1201, and the processing unit 1202 and the display unit 1201 may communicate with each other.

[0285] In one possible implementation, the communication device may further include a storage unit 1204. The storage unit 1204 may include one or more memories, which may be devices in one or more devices or circuits used for storing programs or data.

[0286] The storage unit 1204 can exist independently and be connected to the processing unit 1202 via a communication bus. Alternatively, the storage unit 1204 can be integrated with the processing unit 1202.

[0287] Taking the communication device as an example, which can be a chip or chip system of the electronic device in the embodiments of this application, the storage unit 1204 can store computer-executable instructions for the methods of the electronic device, so that the processing unit 1202 can execute the methods of the electronic device in the above embodiments. The storage unit 1204 can be a register, cache, or random access memory (RAM), etc., and the storage unit 1204 can be integrated with the processing unit 1202. The storage unit 1204 can be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, and the storage unit 1204 can be independent of the processing unit 1202.

[0288] The communication device in this embodiment can be used to perform the steps executed in the above method embodiment. Its implementation principle and technical effect are similar, and will not be repeated here.

[0289] The call method provided in this application can be applied to electronic devices with call functionality. Electronic devices include terminal devices; the specific device form of the terminal device can be referred to the above-described related features, and will not be repeated here.

[0290] For example, Figure 13 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 13As shown, the electronic device includes: 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, a headphone jack 170D, a sensor module 180, buttons 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, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity 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.

[0291] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device. In other embodiments of this application, the electronic device may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0292] The processor 110 may include one or more processing units. These processing units may be independent devices or integrated within one or more processors. The processor 110 may also include a memory for storing instructions and data. For example, the processor 110 may store instructions and data related to a call method provided in an embodiment of this application.

[0293] Electronic devices utilize GPUs, displays (194), and application processors to achieve display functions. The GPU is a microprocessor for image processing, connecting the displays (194) and the application processor.

[0294] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. For example, the display screen 194 can display incoming call reminders (e.g., displaying the incoming call notification as in the above embodiments), etc., but this application embodiment does not limit this.

[0295] The mobile communication module 150 can provide solutions for wireless communication applications including 2G / 3G / 4G / 5G in electronic devices. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device. The mobile communication module 150 can realize data transmission between the electronic device and a cloud server, such as call request 1A, answering signaling, and hanging up signaling.

[0296] The wireless communication module 160 can provide wireless communication solutions for electronic devices, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks) and short-range wireless communication. Short-range wireless communication can include Bluetooth (BT), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies.

[0297] The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signal, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0298] The wireless communication module 160 can realize data transmission between electronic devices and short-range communication devices, such as call information, VoIP service status information, call request 2a, hang-up signaling, etc., as described in the embodiments of this application. In some embodiments, the wireless communication module 160 can also transmit data with a cloud server via a wireless local area network, such as call request 1A, answer signaling, hang-up signaling, etc.

[0299] This application provides an electronic device, which includes one or more processors and a memory; the memory is coupled to one or more processors and is used to store computer program code, which includes computer instructions, and one or more processors call the computer instructions to cause the electronic device to perform the above-described method.

[0300] This application also provides a computer-readable storage medium for storing a computer program for implementing the methods shown in the above-described method embodiments.

[0301] This application also provides a computer program product, which includes a computer program (also referred to as code or instructions) that, when run on a computer, allows the computer to perform the methods shown in the above-described method embodiments.

[0302] This application provides a chip system including a processor and potentially a memory, for implementing the functions of the electronic device described in the method embodiments. The chip system may be composed of chips or may include chips and other discrete devices.

[0303] Those skilled in the art will recognize that the modules and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0304] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and modules described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

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

[0306] The modules described as separate components may or may not be physically separate. Similarly, the components shown as modules may or may not be physical modules; they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment, depending on actual needs.

[0307] In addition, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module.

[0308] If a function is implemented as a software module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, 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 a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of 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), random access memory (RAM), magnetic disks, or optical disks.

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

Claims

1. A communication method, applied to a communication system consisting of a first device and a second device, wherein the first device and the second device are connected via short-range wireless communication, characterized in that, The method includes: The first device receives a first call request, which is used to request a first call from a first account; The first device responds to the first call request and triggers the first incoming call notification; The second device receives a second call request, which is used to request the first call; both the first call request and the second call request originate from the server. The second device responds to the second call request and triggers a second incoming call alert; The first device responds to the answering operation and ends the first incoming call reminder; In response to the answering operation, the first device sends a hang-up signal to the second device via the short-range wireless communication, the hang-up signal being used to indicate the end of the second incoming call reminder; The second device responds to the hang-up signal and terminates the second incoming call notification.

2. The method according to claim 1, characterized in that, The account on the first device is the same as the account on the second device; Alternatively, the calling application in the first device and the calling application in the second device may be logged into the same account.

3. The method according to claim 2, characterized in that, Before the first device sends the hang-up signaling to the second device, the method further includes: The first device obtains the account of the second device; Alternatively, the first device may obtain the account logged into the call application in the second device.

4. The method according to any one of claims 1-3, characterized in that, The communication system further includes: a third device, the third device and the first device being connected via short-range wireless communication; the method further includes: After receiving the first call request, the first device sends a third call request to the third device via the short-range wireless communication. The third call request is used to request the first call. The third device does not have independent call capability. The third device responds to the third call request and triggers a third incoming call alert.

5. The method according to any one of claims 1-4, characterized in that, The second device has independent call capability; After receiving the first call request, the first device does not send a request to the second device via the short-range wireless communication to trigger an incoming call notification for the first call.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: The first device obtains the status information of the call application in the second device; If the status information of the call application in the second device indicates that it is not in an active state, after receiving the first call request, the first device sends a fourth call request to the second device through the short-range wireless communication, the fourth call request being used to request the first call; The second device responds to the fourth call request and triggers the fourth incoming call alert.

7. A method for making a call, characterized in that, The method includes: The first device receives a first call request, the first call request being used to request a first call; The first device responds to the first call request and triggers the first incoming call notification; The first device responds to the answering operation and ends the first incoming call reminder; In response to the answering operation, the first device sends a hang-up signal to the second device via the short-range wireless communication. The second device is a device connected to the first device via the short-range wireless communication. The hang-up signal is used to indicate the termination of the second incoming call reminder triggered by the second device in response to the second call request. The second call request is used to request the first call.

8. A method for making a call, characterized in that, The method includes: The second device receives a second call request, which is used to request the first call; The second device responds to the second call request and triggers a second incoming call alert; The second device receives a hang-up signaling from the first device, the hang-up signaling being generated by the first device in response to an answering operation for a first call request, the first call request being used to request the first call; The second device responds to the hang-up signal and terminates the second incoming call notification.

9. A communication system, characterized in that, The communication system includes: a first device and a second device; The first device is configured to perform the steps executed by the first device in the method as described in any one of claims 1 to 6; The second device is used to perform the steps performed by the second device in the method as described in any one of claims 1 to 6.

10. An electronic device, characterized in that, The electronic device includes: one or more processors and memory; The memory is coupled to the one or more processors, the memory being used to store computer program code, the computer program code including computer instructions, the one or more processors invoking the computer instructions to cause the electronic device to perform the steps performed by the first device in the method as described in any one of claims 1 to 6, or to cause the electronic device to perform the steps performed by the second device in the method as described in any one of claims 1 to 6.

11. A chip system, characterized in that, The chip system is applied to an electronic device, the chip system including one or more processors, the one or more processors being configured to invoke computer instructions to cause the electronic device to perform the steps performed by a first device in the method as described in any one of claims 1 to 6, or to cause the electronic device to perform the steps performed by a second device in the method as described in any one of claims 1 to 6.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes computer instructions that, when executed on an electronic device, cause the electronic device to perform the steps performed by a first device in the method of any one of claims 1 to 6, or cause the electronic device to perform the steps performed by a second device in the method of any one of claims 1 to 6.

13. A computer program product, characterized in that, The computer program product includes computer program code that, when run on an electronic device, causes the electronic device to perform the steps performed by a first device in the method as described in any one of claims 1 to 6, or causes the electronic device to perform the steps performed by a second device in the method as described in any one of claims 1 to 6.

Images