WO2023025150A1

WO2023025150A1 - Call method, electronic device, and system

Info

Publication number: WO2023025150A1
Application number: PCT/CN2022/114266
Authority: WO
Inventors: 孟繁瑞; 薛睿; 刘丽标; 张世茗; 马中骐
Original assignee: 华为技术有限公司
Priority date: 2021-08-24
Filing date: 2022-08-23
Publication date: 2023-03-02
Also published as: CN115941847A

Abstract

The present application relates to the technical field of terminals, and provides a call method, an electronic device, and a system, capable of improving the call efficiency among terminals. The method comprises: performing a voice over Internet protocol (VoIP) call with a second terminal; in the process of the VoIP call with the second terminal, receiving an operator call request from a third terminal; and when it is determined that the third terminal supports the VoIP call, sending a VoIP call request to the third terminal, the VoIP call request being used for requesting the third terminal to join the VoIP call.

Description

A communication method, electronic device and system

This application claims the priority of the Chinese patent application with the application number 202110977380.4 and the title of the invention "a communication method, electronic device and system" submitted to the State Intellectual Property Office on August 24, 2021, the entire contents of which are incorporated herein by reference In this application.

technical field

The present application relates to the technical field of terminals, and in particular to a calling method, electronic equipment and a system.

Background technique

Currently, more and more users use various terminals to make audio and video calls. Audio and video calls can be divided into voice over internet protocol (voice over internet protocol, VoIP) and carrier calls. For example, VoIP calls can be Changlian calls, WeChat

Voice, WeChat

video etc.

In some call plans, when a mobile phone is in a VoIP call, if someone calls the mobile phone to the carrier, the mobile phone can keep the VoIP call, so that the carrier call cannot be answered. Alternatively, the phone can hang up the VoIP call and pick up the carrier call. For example, user A is making a VoIP call with user B through the mobile app, and at this time friend C calls user A's mobile phone to call the operator, then user A can only choose to answer friend C's operator call , or choose to continue to make a VoIP call with user B. In this way, the call efficiency is low.

Contents of the invention

The present application provides a call method, electronic equipment and system, which can improve call efficiency between terminals.

In order to achieve the above purpose, the embodiment of the present application provides the following technical solutions:

In the first aspect, a calling method is provided, which can be applied to a first terminal or a component (such as a chip system) capable of realizing the functions of the first terminal; the method includes: performing a VoIP call with the second terminal, and communicating with the second terminal During the VoIP call, the two terminals receive an operator call request from the third terminal, and send a VoIP call request to the third terminal when it is determined that the third terminal supports the VoIP call. Wherein, the VoIP call request is used to request the third terminal to join the VoIP call.

In the call method provided by the embodiment of the present application, when the first terminal recognizes the conflict between the VoIP call and the operator call, for example, when the first terminal has a new operator call in during the VoIP call, the first terminal can send a call to the originator. The third terminal of the operator call initiates a VoIP call and adds the third terminal to the current VoIP call to realize the integration of VoIP call and operator call, which can meet both VoIP call demands and operator call demands, and improve call efficiency.

In addition, the call method of the embodiment of the present application communicates through VoIP call mode, and does not increase additional call charges of the operator.

In some possible designs, the method further includes: presenting a first interface, where the first interface is used to prompt whether to request the third terminal to join the VoIP call. In this way, the user can be prompted whether to request the third terminal to join the VoIP call, and the user can agree or reject the third terminal to join the current VoIP call according to the current call requirement.

In some possible designs, the method further includes: presenting a first interface, where the first interface is used to prompt that the third terminal has been requested to join the VoIP call.

In some possible designs, sending the VoIP call request to the third terminal includes: sending the VoIP call request to the third terminal after responding to a first instruction input by the first user of the first terminal on the first interface.

In some possible designs, the method further includes: determining whether a third user of the third terminal has a friend relationship with the second user of the second terminal;

Sending the VoIP call request to the third terminal includes: sending the VoIP call request to the third terminal in response to determining that the second user and the third user are friends. In this way, only when it is determined that the second user and the third user are friends, the first terminal sends a VoIP call request to the third terminal, which can avoid sending a third user unknown to the second user of the second terminal. Pull in the current VoIP call, thereby improving the security line of the call and reducing the probability of privacy leakage.

In a possible design, presenting the first interface includes: presenting the first interface in response to the second user being in a friend relationship with the third user. That is to say, only when it is determined that the second user and the third user are friends, the first terminal presents the first interface, thereby prompting the user whether to request the third terminal to join the current VoIP call.

In the second aspect, there is provided a call method, which can be applied to a third terminal or a component (such as a chip system) capable of realizing or assisting in realizing the functions of the third terminal; the method includes:

During the VoIP call between the first terminal and the second terminal, the operator sends a call request to the first terminal, receives the VoIP call request from the first terminal, and joins the VoIP call according to the VoIP call request.

In a possible design, after receiving the VoIP call request from the first terminal, the method further includes:

A second interface is presented, and the second interface is used to prompt a VoIP call request. In this way, when the third terminal calls the operator, it can prompt the VoIP call request from the first terminal through the interface, and then instruct the user of the third terminal whether to choose to answer the VoIP call so as to join the ongoing VoIP call of the first terminal.

In one possible design, joining a VoIP call according to a VoIP call request includes:

In response to the second instruction input by the user on the second interface, join the VoIP call according to the VoIP call request and the second instruction, the second instruction is used to indicate to join the VoIP call.

In a third aspect, a call system is provided, including a first terminal, a second terminal, and a third terminal;

The first terminal is configured to conduct a VoIP call with the second terminal, and receive an operator call request from the third terminal during the VoIP call with the second terminal;

The first terminal is further configured to send a VoIP call request to the third terminal when it is determined that the third terminal supports the VoIP call, and the VoIP call request is used to request the third terminal to join the VoIP call;

The third terminal is configured to receive the VoIP call request from the first terminal, and join the VoIP call according to the VoIP call request.

In a possible design, the first terminal is further configured to present a first interface, and the first interface is used to prompt whether to request the third terminal to join the VoIP call.

In a possible design, the first terminal, configured to send the VoIP call request to the third terminal, includes: sending the VoIP call request to the third terminal in response to a first instruction input by the first user of the first terminal on the first interface. call request.

In a possible design, the first terminal is further configured to determine whether a third user of the third terminal has a friendship relationship with the second user of the second terminal;

The first terminal is configured to send the VoIP call request to the third terminal, including: sending the VoIP call request to the third terminal in response to determining that the second user has a friendship relationship with the third user.

In a possible design, the first terminal being configured to present the first interface includes: presenting the first interface in response to determining that the second user has a friend relationship with the third user.

In a possible design, the third terminal is further configured to present a second interface, and the second interface is used to prompt a VoIP call request.

In the fourth aspect, there is provided a call method, which can be applied to a first terminal or a component (such as a chip system) capable of realizing the functions of the first terminal; the method includes: receiving a call request from an operator from a third terminal, and determining the first terminal When the three terminals support the VoIP call, a VoIP call request is sent to the third terminal.

In the call method provided by the embodiment of the present application, if the caller terminal (that is, the third terminal) supports the VoIP call function for the received call from the operator, the first terminal can call back the caller terminal (third terminal) through the VoIP call mode. , enabling terminals to communicate through VoIP calls.

Usually, the VoIP call function needs to install a corresponding VoIP application. VoIP calls can offer some features that differ from carrier calls. For example, in some examples, a VoIP application may integrate screen sharing functionality. By initiating a VoIP call to the third terminal, the first terminal can use some functions of the VoIP call to improve interactive experience during the call.

In some possible designs, the method further includes: presenting a first interface, where the first interface is used to prompt whether to send a VoIP call request to the third terminal, or to prompt that the VoIP call request has been sent to the third terminal.

In the fifth aspect, there is provided a call method, which can be applied to a third terminal or a component (such as a chip system) capable of realizing or assisting in realizing the functions of the third terminal; the method includes:

Sending an operator call request to the first terminal, receiving a VoIP call request from the first terminal, and performing a VoIP call with the first terminal according to the VoIP call request.

A second interface is presented, and the second interface is used to prompt a VoIP call request.

In a possible design, performing a VoIP call with the first terminal according to the VoIP call request includes:

In response to the second instruction input by the user on the second interface, the VoIP call is made with the first terminal according to the VoIP call request and the second instruction, and the second instruction is used to instruct to answer the VoIP call.

In a sixth aspect, a call system is provided, including a first terminal and a third terminal;

The first terminal is configured to receive an operator call request from a third terminal;

The first terminal is further configured to send a VoIP call request to the third terminal when it is determined that the third terminal supports VoIP calls;

The third terminal is configured to receive a VoIP call request from the first terminal, and conduct a VoIP call with the first terminal according to the VoIP call request.

In a possible design, the first terminal is further configured to present a first interface, and the first interface is used to prompt whether to send a VoIP call request to the third terminal.

In a seventh aspect, the present application provides an electronic device, and the electronic device has a function of implementing the call method in any of the above aspects and any possible implementation manners. This function may be implemented by hardware, or may be implemented by executing corresponding software on the hardware. The hardware or software includes one or more modules corresponding to the above functions.

In an eighth aspect, the present application provides a computer-readable storage medium, including computer instructions. When the computer instructions are run on the electronic device, the electronic device executes any of the above-mentioned aspects and any of its possible implementations. call method.

In a ninth aspect, the present application provides a computer program product. When the computer program product is run on an electronic device, the electronic device is made to execute the call method according to any aspect and any possible implementation thereof.

In a tenth aspect, a circuit system is provided, and the circuit system includes a processing circuit, and the processing circuit is configured to execute the calling method in any of the foregoing aspects and in any possible implementation manner.

In the eleventh aspect, the embodiment of the present application provides a chip system, including at least one processor and at least one interface circuit, at least one interface circuit is used to perform the sending and receiving function, and send instructions to at least one processor, When the processor executes the instructions, at least one processor executes the call method in any of the above aspects and any possible implementation manners.

Description of drawings

FIG. 1 is a schematic diagram of a system architecture provided by an embodiment of the present application;

FIG. 2A and FIG. 2B are schematic structural diagrams of the electronic equipment provided by the embodiment of the present application;

FIG. 3 is a schematic diagram of a call architecture provided by an embodiment of the present application;

FIG. 4 is a schematic diagram of a set of UI provided by the embodiment of the present application;

5A-5D are schematic diagrams of four sets of UI provided by the embodiment of the present application;

6A-6B are schematic diagrams of two sets of UI provided by the embodiment of the present application;

7A-7B are schematic diagrams of two sets of UI provided by the embodiment of the present application;

FIG. 8 is a schematic diagram of a set of UI provided by the embodiment of the present application;

FIG. 9 is a schematic diagram of a set of UI provided by the embodiment of the present application;

10-13 are schematic flowcharts of the call method provided by the embodiment of the present application;

Figure 14-Figure 15 are UI schematic diagrams provided by the embodiment of this application;

16-17 are schematic flowcharts of the call method provided by the embodiment of the present application;

FIG. 18 is a schematic diagram of the UI provided by the embodiment of the present application;

FIG. 19 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 20 is a schematic diagram of the architecture of the chip system provided by the embodiment of the present application.

Detailed ways

The technical solution in this application will be described below with reference to the accompanying drawings.

A call fusion method provided in the embodiment of the present application may be applied to the call system 100 . The intercom system may include one or more electronic devices. Among them, the electronic device can be, but not limited to, a mobile phone, a tablet computer, a TV (also called a smart screen, a large screen device, etc.), a notebook computer, a handheld computer, a netbook, a vehicle-mounted device (also called a car machine), etc. The embodiment of the present application does not impose any limitation on this.

Exemplarily, FIG. 1 is a schematic structural diagram of a communication system. As shown in FIG. 1 , the call system 100 includes a mobile phone 101 , a mobile phone 102 and a mobile phone 103 as an example. The mobile phone 101, the mobile phone 102, and the mobile phone 103 can communicate through the communication network.

In some embodiments, the call between mobile phones may be an operator call implemented through an operator network. The phone application can be installed in the mobile phone, and the user can use the phone application to implement the operator call. In some embodiments, the carrier call may comprise a public switched telephone network (PSTN) call. This article mainly takes PSTN as an example, but it does not constitute a restriction on operator calls.

In some embodiments, the call between mobile phones may also be a VoIP call implemented through a non-operator network. Wherein, the VoIP call includes voice call and/or video call. Applications capable of implementing VoIP calls (VoIP applications for short) can be installed in the mobile phone, and users can use these applications to implement VoIP calls. VoIP applications include but not limited to smooth calls

,WeChat

、Skype

wait. Among them, the smooth call can be used as an independent application, or integrated in the system such as telephone applications.

Wherein, the operator network may be, for example, a network conforming to the specifications of the third generation partnership project (3rd generation partnership project). Exemplarily, the operator's network includes but is not limited to a 4th generation (4th generation, 4G) mobile communication system, such as a long term evolution (long term evolution, LTE) system, a 5th generation (5th generation, 5G) mobile communication system, such as New radio (new radio, NR) system, and future communication systems, such as the network in the sixth generation (6th generation, 6G) mobile communication system.

The non-operator network may include but not limited to a wireless fidelity (wireless fidelity, Wi-Fi) network. The embodiment of the present application does not limit specific types and standards of operator networks and non-operator networks.

In some embodiments, the call system 100 further includes a server 104 . The server 104 is configured to store call-related information. Call-related information includes, but is not limited to, whether the mobile phone supports VoIP calls. Taking a VoIP call as an example of a smooth call, the call-related information of the mobile phone includes whether the mobile phone supports the smooth call. Support for smooth calls means that the mobile phone number corresponding to the mobile phone has activated the smooth call service (default service), and the mobile phone is currently installed with the smooth call application (default application). The smooth calling application can be integrated in the phone application, or the smooth calling application can be an independent application.

As a possible implementation manner, when the call-related information in the server is updated, the updated call-related information may be actively sent to a terminal managed by the server (or a terminal subscribing to the call-related information). Alternatively, the server may send updated call-related information to the terminal according to a preset period. Alternatively, after receiving the request from the terminal for acquiring call-related information, the server sends the call-related information to the terminal. The embodiment of the present application does not limit the specific manner in which the server sends call-related information to the terminal.

It should be noted that the call system 100 may include one or more servers. A server may have multiple functions, or different functions may be implemented by different servers. For example, the call system 100 may further include a server 105 (not shown in FIG. 1 ). The server 105 can be used to create a signaling channel between the parties to the call prior to the call so that the parties can address each other. Optionally, the server 105 can also process call instructions during the call, for example, send and receive call requests, and call responses, so as to ensure the smooth progress of the call. For another example, the call system 100 may further include a server 106 (not shown in FIG. 1 ), which may be used to create one or more media rooms. Later, different mobile phones can join different media rooms. After the mobile phone joins the media room, it can collect its own media data and publish the media data, and other devices in the same room can subscribe to the media data of the mobile phone. Media data includes but not limited to voice data and image data during a call.

In some schemes, when a mobile phone is in a VoIP call, if someone dials a PSTN call to the mobile phone, the mobile phone can keep the VoIP call, so that the PSTN call cannot be answered. Alternatively, the phone can hang up the VoIP call and answer the PSTN call. For example, user A is making a VoIP call with user B through the mobile app, and friend C makes a PSTN call to user A's mobile phone, then user A can only choose to answer friend C's PSTN call, or Select Continue to make a VoIP call with user B.

In order to solve the above problem, an embodiment of the present application provides a call fusion method. When mobile phone 101 was carrying out VoIP call (for example, it can be a smooth call) with mobile phone 102, if mobile phone 101 received the call of mobile phone 103, so, mobile phone 101 can inquire whether the mobile phone number of mobile phone 103 has opened VoIP call service from server ( For example, the smooth call service), or, the mobile phone 101 can query the locally stored and previously obtained call-related information of the mobile phone 103 from the server.

It should be noted that the mobile phone 101 may query the server for authorized call-related information of other mobile phones, and may store the call-related information locally. Among them, the storage period can be set, that is, within the preset period, the mobile phone 101 can locally query the call-related information of other mobile phones that have been authorized to obtain. Security of call-related information.

In some cases, upon inquiry, if the mobile phone number of the mobile phone 103 has subscribed to the VoIP service, then the mobile phone 101 can initiate a VoIP call to the mobile phone 103 . In this way, after the user of the mobile phone 103 agrees to answer the VoIP call, the mobile phone 103 can participate in the VoIP call between the mobile phone 101 and the mobile phone 102 . That is to say, in the embodiment of this application, the user who initiated the PSTN call can be added to the current VoIP call. For the user of the current VoIP call, he can keep the current VoIP call uninterrupted, and can also answer the call of the new user , which can improve call efficiency.

The following still uses the mobile phone 101 as an example of the electronic device in the call system 100 , and FIG. 2A shows a schematic structural diagram of the mobile phone 101 .

The mobile phone 101 can include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, and an audio module 170 , speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, sensor module 180 and so on.

It can be understood that the structure shown in the embodiment of the present invention does not constitute a specific limitation on the mobile phone 101 . In other embodiments of the present application, the mobile phone 101 may include more or fewer components than shown in the figure, or combine certain components, or separate certain components, or arrange different components. The illustrated components can be realized in hardware, software or a combination of software and hardware.

The processor 110 may include one or more processing units, for example: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), controller, memory, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processor (neural-network processing unit, NPU) wait. Wherein, different processing units may be independent devices, or may be integrated in one or more processors.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to use the instruction or data again, it can be called directly from the memory. Repeated access is avoided, and the waiting time of the processor 110 is reduced, thus improving the efficiency of the system.

The wireless communication function of the mobile phone 101 can be realized by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in handset 101 can be used to cover single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: Antenna 1 can be multiplexed as a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 can provide wireless communication solutions including 2G/3G/4G/5G applied on the mobile phone 101 . The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA) and the like. The mobile communication module 150 can receive electromagnetic waves through the antenna 1, filter and amplify the received electromagnetic waves, and send them to the modem processor for demodulation. The mobile communication module 150 can also amplify the signals modulated by the modem processor, and convert them into electromagnetic waves through the antenna 1 for radiation. In some embodiments, at least part of the functional modules of the mobile communication module 150 may be set in the processor 110 . In some embodiments, at least part of the functional modules of the mobile communication module 150 and at least part of the modules of the processor 110 may be set in the same device.

The wireless communication module 160 can provide applications on the mobile phone 101 including wireless local area networks (wireless local area networks, WLAN), such as Wi-Fi networks, bluetooth (bluetooth, BT), global navigation satellite system (global navigation satellite system, GNSS), FM (frequency modulation, FM), near field communication (near field communication, NFC), infrared technology (infrared, IR) and other wireless communication solutions. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2 , frequency-modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 . The wireless communication module 160 can also receive the signal to be sent from the processor 110 , frequency-modulate it, amplify it, and convert it into electromagnetic waves through the antenna 2 for radiation.

In some embodiments, the antenna 1 of the mobile phone 101 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the mobile phone 101 can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (general packet radio service, GPRS), code division multiple access (code division multiple access, CDMA), broadband Code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access

(time-division code division multiple access, TD-SCDMA), LTE, BT, GNSS, WLAN, NFC, FM, and/or IR technology, etc. The GNSS may include a global positioning system (global positioning system, GPS), a global navigation satellite system (global navigation satellite system, GLONASS), a Beidou navigation satellite system (beidou navigation satellite system, BDS), a quasi-zenith satellite system (quasi -zenith satellite system (QZSS) and/or satellite based augmentation systems (SBAS).

The mobile phone 101 realizes the display function through the GPU, the display screen 194, and the application processor. The GPU is a microprocessor for image processing, and is connected to the display screen 194 and the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

The display screen 194 is used to display images, videos and the like. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active matrix organic light emitting diode or an active matrix organic light emitting diode (active-matrix organic light emitting diode, AMOLED), flexible light-emitting diode (flex light-emitting diode, FLED), Miniled, MicroLed, Micro-oLed, quantum dot light emitting diodes (quantum dot light emitting diodes, QLED), etc. In some embodiments, the mobile phone 101 may include 1 or N display screens 194, where N is a positive integer greater than 1.

The mobile phone 101 can realize the shooting function through ISP, camera 193, video codec, GPU, display screen 194 and application processor.

The ISP is used for processing the data fed back by the camera 193 . For example, when taking a picture, open the shutter, the light is transmitted to the photosensitive element of the camera through the lens, and the light signal is converted into an electrical signal, and the photosensitive element of the camera transmits the electrical signal to the ISP for processing, and converts it into an image visible to the naked eye. ISP can also perform algorithm optimization on image noise, brightness, and skin color. ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, the ISP may be located in the camera 193 .

Camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects it to the photosensitive element. The photosensitive element may be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, and then transmits the electrical signal to the ISP to convert it into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. DSP converts digital image signals into standard RGB, YUV and other image signals. In some embodiments, the mobile phone 101 may include 1 or N cameras 193, where N is a positive integer greater than 1.

Digital signal processors are used to process digital signals. In addition to digital image signals, they can also process other digital signals. For example, when the mobile phone 101 is selecting a frequency point, the digital signal processor is used to perform Fourier transform on the energy of the frequency point.

Video codecs are used to compress or decompress digital video. The handset 101 may support one or more video codecs. In this way, the mobile phone 101 can play or record videos in various encoding formats, such as: moving picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the mobile phone 101. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function. Such as saving music, video and other files in the external memory card.

The internal memory 121 may be used to store computer-executable program codes including instructions. The processor 110 executes various functional applications and data processing of the mobile phone 101 by executing instructions stored in the internal memory 121 . The internal memory 121 may include an area for storing programs and an area for storing data. Wherein, the stored program area can store an operating system, at least one application program required by a function (such as a sound playing function, an image playing function, etc.) and the like. The storage data area can store data (such as audio data, phone book, etc.) created during the use of the mobile phone 101 . In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, flash memory device, universal flash storage (universal flash storage, UFS) and the like.

The mobile phone 101 can realize the audio function through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor. Such as music playback, recording, etc.

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

Speaker 170A, also referred to as a "horn", is used to convert audio electrical signals into sound signals. Cell phone 101 can listen to music through speaker 170A, or listen to hands-free calls.

Receiver 170B, also called "earpiece", is used to convert audio electrical signals into sound signals. When the mobile phone 101 receives a call or a voice message, the receiver 170B can be placed close to the human ear to listen to the voice.

Microphone 170C, also called "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can put his mouth close to the microphone 170C to make a sound, and input the sound signal to the microphone 170C. The mobile phone 101 can be provided with at least one microphone 170C. In some other embodiments, the mobile phone 101 can be provided with two microphones 170C, which can also implement a noise reduction function in addition to collecting sound signals. In some other embodiments, the mobile phone 101 can also be equipped with three, four or more microphones 170C to realize the collection of sound signals, noise reduction, identification of sound sources, and realization of directional recording functions, etc.

The earphone interface 170D is used for connecting wired earphones. The earphone interface 170D can be a USB interface 130, or a 3.5mm open mobile terminal platform (OMTP) standard interface, or a cellular telecommunications industry association of the USA (CTIA) standard interface.

The sensor module 180 may include a pressure sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like.

Certainly, the mobile phone 101 may also include a charging management module, a power management module, a battery, buttons, an indicator, and one or more SIM card interfaces, etc., which are not limited in this embodiment of the present application.

It should be noted that, the structure of the server 104 can also refer to the structure of the terminal shown in FIG. 2A, and the server 104 can have more or fewer components than the structure shown in FIG. 2A, or combine some components, or split some components , or different component arrangements. The illustrated components can be realized in hardware, software or a combination of software and hardware.

For example, as shown in FIG. 2B, the server 104 may include a processor 401 (optionally, a processor 408), a memory 403, a transceiver 404, and the like.

Wherein, a path may be included between the above components, for transmitting information between the above components.

The transceiver 404 is used for communicating with other devices or communication networks through protocols such as Ethernet and WLAN.

For the details of the processor and the memory, please refer to the description of the relevant structure in the terminal in FIG. 2A , which will not be repeated here.

Taking a mobile phone as an example, FIG. 3 shows a schematic diagram of a call architecture of a mobile phone. The call architecture of the mobile phone includes a call application, a telephony module, a telecom module, and a Meettime.HwVoipService module. Each module cooperates with each other to complete the call function.

In some embodiments, the calling application may be InCallUI. In some other embodiments of the present application, the calling application may be a VoIP application such as Unlink calling. The following embodiments mainly illustrate the technical solution by taking the call application as an example of a smooth call, which is uniformly stated here and will not be described in detail below.

Among them, the smooth call application may include modules such as InCallActivity, InCallServiceImp, and Call.

InCallActivity can be used to implement the call interface, such as displaying the dial interface, incoming call interface, and outgoing call interface. Take the user initiating a call as an example, the user makes a call through the call interface implemented by InCallActivity, and the Changlian call application passes the call event to the telecom module.

InCallServiceImp is an extension implementation class for the call management service. In the embodiment of the present application, the callback function onCallAdded can be implemented in the InCallServiceImp class, and when onCallAdded is called, the smooth call application can determine that there is an incoming PSTN call. Call is a call implementation class that can be used to record the status of each call.

Telecom module can be used to be responsible for call logic control. As a possible implementation manner, the telecom module may include modules such as InCallService, Call, ConnectionService, and Connection. Among them, InCallService is a call management service class. The InCallService class can be used to process call information. Call is the implementation class for calls. ConnectionService is a call connection management service, and Connection is a call connection implementation class.

In the embodiment of this application, when the user is the calling party, the user initiates a call through the interface implemented by InCallActivity (such as the interface shown in (2) in Figure 4), and the smooth call application passes the call event to the telecom module . The telecom module can determine whether the call is a PSTN call or a smooth call. If the call dialed by the user is a smooth call, the telecom module will pass the call event to the Meetime.HwVoipService module, and the Meetime.HwVoipService module will establish relevant media channels and signaling channels. In this way, smooth communication between the calling party and the called party can be realized. If the user dials a PSTN call, the telecom module transmits the call event to the telephony module, and the telephony module realizes the PSTN call between the calling party and the called party.

When the user is the called party and there is an incoming PSTN call, the telecom module can receive the incoming call event from the telephony module, and notify the upper layer of the smooth call application of the PSTN incoming call event.

As a possible implementation, the telecom module reports the PSTN incoming call event to the smooth call application, which can be implemented by calling onCallAdded. Or, you can set the broadcast sender in the telecom module, and set the broadcast receiver in the smooth call application. When the telecom module detects a PSTN incoming call event, it sends a broadcast, and the smooth call can monitor the broadcast of the PSTN incoming call event through the broadcast receiver, so as to determine that there is an incoming PSTN call.

When the user is the called party and there is an incoming call, the telecom module can receive the incoming call event from the Meettime.HwVoipService module, and report the incoming call to the upper-layer smooth call application.

In some embodiments, the technical solutions of the embodiments of the present application realize the detection of VoIP calls and operator calls by extending the functions of the telecom module.

The telephony module can be used to be responsible for PSTN call service. For example, it is responsible for dialing, hanging up, and changing the status of the phone such as dialing, ringing, and connecting. The Telephony module may include TelephonyConnectionService and TelephonyConnection. Among them, TelephonyConnectionService is a connection management service, and TelephonyConnection is a connection implementation class.

In the embodiment of the present application, when a PSTN call comes in, the telephony module will report the PSTN call event to the telecom module.

The Meettime.HwVoipService module can be used to provide VoIP call services. As a possible implementation, the module may include CassVoipConnectionService (VoIP connection management service of the smooth call application) and CassVoipConnection (VoIP connection implementation class of the smooth call application).

In the embodiment of the present application, when a smooth call is incoming, the Meettime.HwVoipService module will report the smooth incoming call event to the telecom module.

As a possible implementation, the media cloud shown in FIG. 3 may be a server that provides media services for smooth calls. The signaling cloud can be a server that provides signaling services for the smooth call. Media services include, but are not limited to, establishing, maintaining, and updating media channels of all parties involved in a call. Signaling services include, but are not limited to, establishing, maintaining, and updating signaling channels between call parties, signaling addressing, etc.

Still taking the mobile phone as an example as the terminal of the call, the above-mentioned call fusion method will be described in detail below.

The applications used to realize the VoIP call in the embodiment of the present application may be various applications. For example, it may be a system-level application or a user-level application. The following mainly takes the implementation of VoIP calls through Connected Calls, and Connected Calls can be used as an independent application as an example for illustration.

As shown in (1) of FIG. 4 , mobile phone A may present an interface 501, and the interface 501 includes icons of multiple applications. For example, it includes the icon 502 of the smooth call application. When an operation such as clicking on the icon 502 by the user is detected, the mobile phone A may present an interface 503 such as that shown in (2) of FIG. 4 . Optionally, the interface 503 includes any one or more of the following information: an input box 504, local machine information 505, and contact information for enabling the smooth call function. The user can search for a contact by inputting a keyword in the input box 504 or enter a mobile phone number to make a smooth call. The user can also find the desired contact in the contact information 506, and initiate a voice call or video call through the control 507 corresponding to the contact.

Exemplarily, mobile phone A detects that the user clicks the control 507 corresponding to the contact Jane (user B), then mobile phone A can send a call request to the server, and the server can send the call request to mobile phone B of the contact Jane. Moreover, mobile phone A may present a call interface 508 such as that shown in (3) of FIG. 4 .

After Jane answers the call, such as pressing the "answer button", Jane's mobile phone B can send a call response to the server, and the server then forwards the call response to the calling mobile phone A to inform mobile phone A that the call has been connected . Optionally, after the call is connected, mobile phone A may present a call interface 509 (of the first interface) such as that shown in (4) of FIG. 4 .

In some scenarios, when mobile phone A and Jane (the second user)'s mobile phone B are in the process of making a smooth call, mobile phone C (such as the mobile phone of Bob (the third user)) may call the user Jack (the first user) of mobile phone A user). Specifically, after detecting the user's instruction to initiate a PSTN call to mobile phone A, such as detecting the user's operation of dialing a PSTN call through a phone application, mobile phone C can send a call request to mobile phone A, and mobile phone C can display a message such as that shown in Figure 6A. The call interface 601 shown in (1). After mobile phone A receives the call request, mobile phone A may pop up a control 510 such as shown in (1) of FIG. 5A to prompt the user that there is currently a PSTN call from Bob. Mobile phone A can query the call-related information of Bob's mobile phone C, and it can query the call-related information from this current time, or query the call-related information from the server. In some cases, after inquiry, if the mobile phone number of mobile phone C has opened the unblocked call service, then mobile phone A can display the control 511 shown in (1) in Figure 5A to ask the user whether to request to initiate a call to Bob's mobile phone C. Smooth calls.

In some examples, if it is detected that the user instructs Bob's mobile phone C to initiate a smooth call operation, such as detecting that the user clicks the "Yes" button (the first instruction) shown in (1) in Figure 5A, then mobile phone A can pass The Changlian calling application initiates a Changlian calling to mobile phone C. As a possible implementation, mobile phone A sends a request for a smooth connection to Bob's mobile phone C. During the process of initiating a smooth call, mobile phone A may display a call interface such as that shown in (2) in FIG. 5A. Correspondingly, after mobile phone C receives the request for uninterrupted communication from mobile phone A, an interface 605 (second interface) such as that shown in (2) of FIG. 6A may pop up to prompt the uninterrupted communication from mobile phone A. The interface 605 includes a control 602, which is used for prompting a pending call to be answered. Optionally, the control 602 shown in (2) of FIG. 6A further includes a "answer" control 603, and the answer control 603 is used to answer the connected call from Jack. In response to an instruction (second instruction) input by the user such as clicking on the control 603, mobile phone C joins the smooth call between mobile phone A and mobile phone B according to the second instruction, wherein the second instruction is used to indicate Join said Connect call.

In some other embodiments, as shown in (1) of Figure 6B, if mobile phone C detects that mobile phone A is making a smooth call during the process of calling mobile phone A, mobile phone C can pop up a control such as (2) in Figure 6B 604, used to prompt whether to join the smooth call of mobile phone A. In an example, if it is detected that the user clicks the "Yes" button, mobile phone C joins the smooth call of mobile phone A. After mobile phone C joins the smooth call of mobile phone A, mobile phone A may display a call interface such as that shown in (3) in FIG. 6B.

In this embodiment of the present application, the call back process may refer to a process of calling the other party after receiving a PSTN incoming call from the other party. To call back the other party, you can call back through VoIP applications such as Changlian Call. In this way, after the call back is successful, the other party can join the ongoing VoIP call.

It can be understood that mobile phone C can detect whether Bob agrees to answer the smooth call from mobile phone A (Jack). For example, if it is detected that Bob double-clicks the control 602, then the mobile phone C determines that Bob agrees to answer the smooth call from the mobile phone A. For another example, if it is detected that Bob clicks on the control 602, the mobile phone C may present a call interface for a smooth call, and the call interface includes an "answer button". When detecting Bob's operation such as clicking the "answer button", mobile phone C determines that Bob agrees to answer the smooth call from mobile phone A (Jack). The embodiment of the present application does not limit the manner in which the mobile phone C detects whether the user agrees to answer the current incoming call.

Taking Bob’s double-click on the control 602 as an example, mobile phone C confirms that Bob agrees to answer the smooth call from mobile phone A. After confirming that Bob agrees to answer the smooth call from mobile phone A, mobile phone C can send the smooth call to mobile phone A through the server Response, used to instruct mobile phone C to join the Changlian call. After mobile phone A receives the unconnected call response from mobile phone C, the unconnected call is connected, and mobile phone A may display a call interface 512 such as shown in (3) of FIG. 5A . The interface 512 can present image information of the parties to the call. For example, the interface 512 may include a window 513 for each party in the call, and the window is used to present the avatar or real-time video of the party in the call. It can be seen from (3) in FIG. 5A that the callers of the unblocked call have been increased from Jack and Jane to Jack, Jane and Bob. Correspondingly, after the unblocked call is connected, the mobile phone C may present an unconnected call interface such as that shown in (3) in FIG. 6A.

It can be seen that, for a mobile phone that is making a smooth call, if the mobile phone receives a PSTN call from another mobile phone that has opened the smooth call service, then the mobile phone can initiate a smooth call to the mobile phone that initiated the PSTN call. In this way, the PSTN call can be initiated. The calling mobile phone joins the ongoing call. Furthermore, it is possible to answer new important incoming calls without interrupting the smooth connection of the current user.

In other cases, if the mobile phone number of the mobile phone C is not registered for the unblocked call service, then the mobile phone A can perform operations according to the existing technology. For example, mobile phone A can answer the PSTN call of Bob's mobile phone C under the operation of the user, and hang up the smooth call with Jane's mobile phone B. Or, the mobile phone can continue to maintain the current smooth connection call, and does not answer the PSTN call from the mobile phone C.

In the embodiment of the present application, the controls used to trigger mobile phone A to initiate a smooth call to mobile phone C are not limited to the control 511 shown in FIG. 5A . In other embodiments, after mobile phone A receives a PSTN incoming call from mobile phone C (Bob's mobile phone), mobile phone A may display a control 510 such as shown in (1) of FIG. It is used to trigger the mobile phone to send a corresponding VoIP call request. For example, the user can trigger the mobile phone A to initiate a smooth connection call request (VoIP call request) to the mobile phone C through the operation control 516 .

In some other embodiments, mobile phone A can determine whether there is a friend relationship between the counterparty of the PSTN call to be answered (such as user B of mobile phone B) and the counterparty of the VoIP call being answered (such as user C of mobile phone C). In some cases, in response to determining that user B and user C are friends, mobile phone A sends a call request to mobile phone C.

Alternatively, in response to determining that user B and user C are friends, mobile phone A may prompt the user with a first interface for prompting and requesting mobile phone C to join the ongoing smooth call, such as the display shown in (1) in Figure 5A Control 511, so as to prompt the user to invite mobile phone C to join the current smooth connection call.

In other cases, if it is determined that user B and user C are not friends, mobile phone A does not ask the user whether to request mobile phone C to join the ongoing smooth connection call based on factors such as privacy protection. The user of mobile phone A can handle the PSTN calls of mobile phone C according to the current demand.

For example, the user of mobile phone A chooses to answer the PSTN call of mobile phone C, such as the user slides the "answer" control 514 in the control 510 shown in (1) of Figure 7A to the right, so as to answer the PSTN call from mobile phone C. Optionally, after answering the PSTN call of mobile phone C, mobile phone A automatically hangs up the call with mobile phone B.

Alternatively, the user of mobile phone A clicks the hangup control 515 shown in (1) in FIG. 5A to hang up the PSTN call of mobile phone C. In this way, the user of mobile phone A can continue to maintain the smooth connection between the current mobile phone B and mobile phone B.

As a possible implementation, different users can back up their mobile phone address books to the server, and correspondingly, the server stores the address books of each mobile phone. Subsequently, the mobile phone can query the friendship relationship between other users from the server. Of course, the mobile phone can also judge the friend relationship between other users in other ways. This embodiment of the present application does not limit this.

It should be noted that the above-mentioned user B and user C are friends, and the contact information of user B may be in the address book of user C's mobile phone C, or the contact information of user C may be in the address book of user B's mobile phone B. in the address book.

Alternatively, the user B and the user C are friends, and the address book of the mobile phone B includes the contact information of the user C, and the address book of the mobile phone C includes the contact information of the user B.

Alternatively, user B and user C are friends, which may be that the group of friends in the address book of mobile phone B includes user C, or that the group of friends in the address book of mobile phone C includes user B, or that the group of friends in the address book of mobile phone C includes user B. The friend group in C's address book includes user B, and the friend group in mobile phone B's address book includes user C. The embodiment of the present application does not limit the specific meaning of the friend relationship.

Optionally, in order to reduce the leakage of private information, the server can set certain query conditions for a mobile phone that wants to query the friendship relationship between other users. When the query condition is met, the mobile phone has the right to query the friendship relationship between other users. Optionally, the query condition may be that the mobile phone queries the friend relationship among its own friends. For example, among user A of mobile phone A, user B of mobile phone B, user C of mobile phone C, user D of mobile phone D, and user E of mobile phone E, user A and user B are friends, and user A and user C are friends. Then, mobile phone A can query whether user B and user C are friends (because users B and C are both friends of user A), mobile phone A cannot query whether user D and user E are friends, and mobile phone A cannot query user B and user C. Whether user E is a friend relationship. The embodiment of the present application does not limit the query conditions.

Exemplarily, still taking the mobile phones A, B, and C as an example, Jane can back up the address book of mobile phone B to the server, and Bob can back up the address book of mobile phone C to the server. As shown in (1) of FIG. 7A , during the smooth call between Jack's mobile phone A and Jane's mobile phone B, mobile phone A receives a PSTN call from Bob's mobile phone C, and displays an interface 701, which includes controls 510, used to prompt the PSTN incoming call. Mobile phone A may send a query request to the server to query whether user B (Jane) and user C (Bob) are friends. The server sends a query response to the mobile phone A, and the query response includes information indicating whether it is a friend relationship. Assuming that the query response indicates that users B and C are friends, then mobile phone A determines that mobile phone B and C can participate in this smooth call together, then mobile phone A can present a control 702 such as that shown in (1) of Figure 7A in interface 701 , which is used to ask the user whether to invite Bob to join the ongoing Connect call. When it is detected that the user indicates to invite Bob to join the ongoing Connected call, such as clicking the "Yes" button shown in (1) in Figure 7A, mobile phone A can call Bob through the Connected call, and can display such as (2) in Figure 7A ) shows the calling interface. After the call is connected, mobile phones A, B, and C can carry out three-way connected calls. The interface of the mobile phone A during the three-party smooth connection call may be as shown in (3) of FIG. 7A .

In some other embodiments, during the process of mobile phone A calling back to mobile phone C (that is, mobile phone A calls mobile phone C through a VoIP application such as a smooth call), mobile phone A can notify mobile phone C of the participant information of the current smooth call . As a possible implementation, mobile phone A sends participant information to mobile phone C through the server. Optionally, the participant information is carried in the call request, or the participant information is carried in other messages of the server. Exemplarily, the user of the mobile phone C makes a call with the operator, and during the dialing process, the mobile phone C may display an interface such as that shown in (1) of FIG. 8 . When mobile phone C receives a call back from mobile phone A through the Connected Call application, mobile phone C can display an interface 802 as shown in (2) in Figure 8, and the interface 802 includes a control 801, which can include the current Connected call participant information. In this way, the user C (Bob) of the mobile phone C can know the participants of the ongoing Connect call, and judge whether to join the Connect call accordingly. After the mobile phone C joins the smooth connection call, it can display a call interface such as that shown in (3) of FIG. 8 .

Of course, mobile phone A can also send other relevant information about the smooth connection call to mobile phone C, so that user C of mobile phone C can judge whether to join the ongoing smooth connection call based on the information.

Optionally, in order to enhance the security of user privacy, authorization verification may be performed before sending the relevant information of the calling party to the mobile phone C. As a possible implementation, mobile phone A can send a notification message to mobile phone B to notify mobile phone C that it may join the smooth connection call. After mobile phone B receives the notification message from mobile phone A, it may present a window 901 such as that shown in FIG. 9 for asking whether to authorize mobile phone C to obtain the call information of mobile phone B. If it is detected that the user clicks the option "Yes", it means that the mobile phone C can obtain the call information of the mobile phone B (such as the identity information of the user of the mobile phone B) in the subsequent process. For example, if the user of mobile phone B clicks the option "Yes" in the window 901 shown in FIG. It is used to remind the user of mobile phone C of the identity information of the participant of the current smooth call.

Alternatively, an interface for authorizing call information may also be displayed on mobile phone A. For example, "Whether to allow Bob to obtain the identity information of the parties in the current call" is displayed on the mobile phone A. Alternatively, there may be other prompting methods on the mobile phone A, and the implementation of this application does not limit the specific interface presentation methods.

Taking the ongoing VoIP call as an example of an unconnected call, it should be noted that the ongoing unconnected call may be an unconnected call between three or more parties. Some of the participating parties may agree to authorize their own information to the third terminal, and some other participating parties may not agree to authorize their own information to the third terminal. Correspondingly, the third terminal can view the information of authorized participants through the interface, but the third terminal cannot view the information of unauthorized participants.

Alternatively, the user can also set the call information to be visible to contacts. Then, when it is confirmed that the user of mobile phone B and the user of mobile phone C are friends, mobile phone C can also obtain the identity information of the participant of the current smooth call.

FIG. 10 shows the flow of the call method in the embodiment of the present application. Referring to Figure 10, the method includes:

S101. The first terminal performs a VoIP call with the second terminal.

Exemplarily, taking the first terminal as mobile phone A, the second terminal as mobile phone B, and the VoIP call as an example, as shown in (1)-(2) in Figure 4, mobile phone A can use the smooth call application Initiate a smooth call to mobile phone B. Among them, after dialing the smooth connection call and before connecting the smooth connection call, the call interface of mobile phone A is shown in (3) of Figure 4, and after the smooth connection call is connected, the call interface of mobile phone A is shown in Figure 4 (4) shown.

S102. The third terminal sends an operator call request to the first terminal.

Correspondingly, the first terminal receives an operator call request from the third terminal.

Here, the first terminal is the above-mentioned mobile phone A, the second terminal is the above-mentioned mobile phone B, the third terminal is the above-mentioned mobile phone C, the VoIP call is a smooth call, and the operator call is a PSTN call as an example, for example, as shown in Figure 5A ( As shown in 1), mobile phone A and mobile phone B are in a smooth call, and mobile phone C sends a PSTN call request to mobile phone A. Optionally, before the PSTN call is connected, the mobile phone C may display the call interface 601 shown in (1) of FIG. 6A . After mobile phone A receives the PSTN call from Bob's mobile phone C, it may display an interface 509 for prompting the incoming PSTN call from mobile phone C.

For another example, as shown in (1) of Figure 5B, mobile phone A and mobile phone B are in the smooth connection call, mobile phone A receives the PSTN call of Bob's mobile phone C, and displays a control 517, which is used to prompt the PSTN call from mobile phone C call.

It should be noted that the control 511 shown in (1) of FIG. 5A and the control 516 shown in (2) of FIG. 5B are optional, that is, after the mobile phone A receives the PSTN call request from the mobile phone C, if If it is judged that mobile phone C supports uninterrupted calls, mobile phone A can automatically send an uninterrupted call request to mobile phone C, without the need for the user to input an instruction to trigger mobile phone A to send an uninterrupted call request. Taking Fig. 5B as an example, after mobile phone C connects to the smooth call, mobile phone A can display the interface shown in (3) in Fig. 5B.

S103. The first terminal determines whether the third terminal supports VoIP calls.

As a possible implementation, the first terminal (such as mobile phone A) has previously inquired about the call-related information of the third terminal (such as mobile phone C) from the server (including whether the third terminal supports VoIP calls (such as smooth calls)) , and store the information locally, then the first terminal can inquire locally whether the third terminal supports VoIP calls. Alternatively, if the first terminal does not store the call-related information of the third terminal, then the first terminal may obtain from the server whether the third terminal supports VoIP calls.

In this embodiment of the present application, if the third terminal supports VoIP calls, the first terminal can call back the third terminal through a VoIP call application (such as a smooth call application), so that the third terminal can access the ongoing VoIP call. The process for the first terminal to call back the third terminal includes the following steps S104-S105. Conversely, if the first terminal does not support the VoIP call, as a possible implementation, the first terminal uses the existing technology to process the third terminal's operator call (such as a PSTN call).

S104. The first terminal sends a VoIP call request to the third terminal.

Correspondingly, the third terminal receives the VoIP call request from the first terminal.

Optionally, the smooth call request may be invite multiparty (invite multiparty, inviteMP) signaling.

Optionally, the first terminal sends a VoIP call request to the third terminal through the server, for requesting the third terminal to join the VoIP call between the first terminal and the second terminal.

Exemplarily, assuming that the first terminal is the above-mentioned mobile phone A, the second terminal is the above-mentioned mobile phone B, and the third terminal is the above-mentioned mobile phone C, the VoIP call is a smooth call, and the operator call is a PSTN call. Send an uninterrupted call request. Before connecting to the smooth call, mobile phone A can display the call interface as shown in (2) in Figure 5A, and mobile phone C can display the call interface 605 shown in Figure 6A (2) or the call interface shown in Figure 6B (2) 606. For detailed introduction of the interface 605 and the interface 606, reference may be made to the foregoing embodiments.

S105. The third terminal joins the VoIP call according to the VoIP call request.

Exemplarily, the first terminal is the above-mentioned mobile phone A, the second terminal is the above-mentioned mobile phone B, the third terminal is the above-mentioned mobile phone C, the VoIP call is a smooth call, and the operator call is a PSTN call as an example. In an example , after mobile phone C receives the uninterrupted call request from mobile phone A, it can join the uninterrupted call between mobile phone A and mobile phone B. Optionally, mobile phone C may join the smooth call between mobile phone A and mobile phone B based on an instruction input by the user. For example, mobile phone C responds to the user's instruction to click on the control 603 shown in (2) in FIG. 6A , and joins the smooth call between mobile phone A and mobile phone B. For another example, mobile phone C responds to the user clicking the "Yes" button of control 604 shown in (2) in FIG. 6B , and joins the smooth call between mobile phone A and mobile phone B.

Through the above call method, when the conflict between the VoIP call and the operator call is recognized, for example, when a new operator call is incoming during the VoIP call, a VoIP call can be initiated to the third terminal of the new operator call, and the third terminal The terminal joins the current VoIP call to realize the integration of VoIP call and operator call, which can meet the demands of VoIP call and operator call at the same time, and improve call efficiency.

Optionally, the above embodiment corresponding to FIG. 10 may further include other steps, or some steps in the embodiment shown in FIG. 10 may be replaced with other steps or further refined. Correspondingly, the present application also provides another calling method, as shown in FIG. 11 , the method includes the following steps:

S201. The first terminal and the second terminal join the first media room.

For a specific way for a terminal to join a media room, reference may be made to the prior art. For example, a terminal may invoke a system interface to join a first media room.

As a possible implementation, on the basis of S201, step S101 in FIG. 10 can be implemented as the following step S101a:

S101a, the first terminal and the second terminal conduct a VoIP call through the first media room.

As a possible implementation manner, after the first terminal joins the first media room, it can collect local media data and publish the collected media data to the server. Optionally, if the VoIP call between the first terminal and the second terminal is a voice call, the first terminal can only collect audio data; if the VoIP call between the first terminal and the second terminal is a video call, the mobile phone Audio data as well as image data can be collected.

The second terminal may subscribe to media data of one or more devices in the same media room, for example, may subscribe to audio and/or video data of the first terminal. Taking the first terminal as the above-mentioned mobile phone A and the second terminal as the above-mentioned mobile phone B as an example, as shown in Figure 4, in the scene where Jack and Jane are making a two-party video call, mobile phone A and mobile phone B subscribe by default each other's audio and video data. After mobile phone A subscribes to the audio data and video data of mobile phone B, mobile phone A can obtain the audio data and video data collected by mobile phone B from mobile phone B, and display the call interface shown in (4) in Figure 4, and play the audio data collected by mobile phone B . Similarly, after mobile phone B subscribes to the audio data and video data of mobile phone A, it can obtain the audio data and video data collected by mobile phone A from mobile phone A, display the corresponding call interface including video data, and play the audio data collected by mobile phone A.

S102. The third terminal sends an operator call request to the first terminal.

Taking the first terminal as the above-mentioned mobile phone A, the second terminal as the above-mentioned mobile phone B, and the third terminal as the above-mentioned mobile phone C, the carrier call is a PSTN call, and the VoIP call is a smooth call as an example, as shown in (1) of Figure 5A , mobile phone A and mobile phone B are in a smooth call, and mobile phone A receives a PSTN call from Bob's mobile phone C.

As a possible implementation, a broadcast listener may be set in the mobile phone A to monitor the first broadcast from the telecom module, where the first broadcast is a broadcast for a PSTN incoming call event.

As another possible implementation, mobile phone A can implement the callback function onCallAdded in the InCallService module of the smooth call application. When onCallAdded is called, mobile phone A can determine that there is an incoming PSTN call.

For other implementation details of step S102, refer to the corresponding description in FIG. 10 , which will not be repeated here.

Taking the first terminal as the above-mentioned mobile phone A, the second terminal as the above-mentioned mobile phone B, and the third terminal as the above-mentioned mobile phone C, the carrier call is a PSTN call, and the VoIP call is a smooth call. Optionally, if the mobile phone C supports smooth If you are connected to a call, mobile phone A can call back mobile phone C through the Connected Call application, so that mobile phone C can join the ongoing Connected call. The process of mobile phone A calling back mobile phone C includes the following steps S105-step S115. Conversely, if the mobile phone C does not support smooth calls, then as a possible implementation, the mobile phone A continues to use the existing technology to process the PSTN incoming calls of the mobile phone C.

For other implementation details of step S103, refer to the description of the embodiment corresponding to FIG. 10 , which will not be repeated here.

S202. The first terminal determines whether there is a friend relationship between the third user of the third terminal and the second user of the second terminal.

This step S202 is an optional step.

Taking the first terminal as the above-mentioned mobile phone A, the second terminal as the above-mentioned mobile phone B, and the third terminal as the above-mentioned mobile phone C, the carrier call is a PSTN call, and the VoIP call is a smooth call as an example. Optionally, the mobile phone A receives the call from After the PSTN call of mobile phone C, it can be checked whether the user of mobile phone B and the user of mobile phone C have a friend relationship. In some examples, if mobile phone A determines that the user of mobile phone B and the user of mobile phone C have a friendship relationship, mobile phone A may perform the following step S203 to present a first interface to prompt whether to request mobile phone C to join the smooth call. In this manner, in response to the first instruction input by the user (an instruction for requesting mobile phone C to join the unconnected call), mobile phone A sends a request for unconnected call to mobile phone C. If the mobile phone A determines that the user of the mobile phone B and the user of the mobile phone C do not have a friend relationship, the call mechanism of the prior art may be continued. Exemplarily, as shown in (1) of FIG. 7A , after mobile phone A receives a PSTN call from mobile phone C, it may inquire whether the user of mobile phone B and the user of mobile phone C have a friendship relationship. In response to mobile phone A determining that the user of mobile phone B and the user of mobile phone C have a friendship relationship, mobile phone A may present an interface 701 to prompt whether to request mobile phone C to join the smooth call.

In some other examples, if the mobile phone A determines that the user of the mobile phone B and the user of the mobile phone C are friends, the mobile phone A no longer presents the first interface for prompting whether to request the mobile phone C to join the smooth call. Optionally, as shown in (1) of Figure 7B, when mobile phone A detects that user Bob of mobile phone B and user Jane of mobile phone A are friends, it directly sends a call request to mobile phone C (no longer by the user's For example, the first instruction triggers sending a call request), and displays the call interface 705 shown in (2) of FIG. If it is detected that the user clicks on the option of "reject joining", mobile phone A stops sending a request for a smooth connection to mobile phone C, and mobile phone A continues to make a smooth connection with mobile phone B. If it is not detected that the user clicks on the "refusal to join" option, the mobile phone A continues to wait for the mobile phone C to join the smooth connection call. After mobile phone C joins the smooth call, the call interface of mobile phone A may be as shown in (3) in FIG. 7B . In other examples, control 704 is optional.

As a possible implementation, step S105 is an optional step, that is, mobile phone A can directly send a call request to mobile phone C without displaying the callback control after finding that mobile phone C supports smooth calling . Alternatively, mobile phone A may directly send a call request to mobile phone C without displaying the callback control when it is found that mobile phone C supports uninterrupted calls, and the user of mobile phone C and the user of mobile phone B are friends.

S203. The first terminal displays a first interface.

Optionally, step S203 may be performed after S103, that is, S202 is not performed. Step S203 may also be performed after S202. Or, step S203 is not executed.

Wherein, the first interface may be used to prompt whether to request the third terminal to join the VoIP call. Taking the first terminal as the above-mentioned mobile phone A, the second terminal as the above-mentioned mobile phone B, and the third terminal as the above-mentioned mobile phone C, the carrier call is a PSTN call, and the VoIP call is a smooth call. For example, mobile phone A is communicating with the mobile phone B receives a PSTN call from mobile phone C during the smooth call. And the mobile phone A can confirm that the mobile phone C supports the smooth connection call after the inquiry, then, the mobile phone A can display an interface 509 such as shown in (1) of FIG. The control 511 in initiates a call back to the mobile phone C for a smooth call.

In another example, mobile phone A receives a PSTN call from mobile phone C during a smooth call with mobile phone B. And the mobile phone A can confirm that the mobile phone C supports the smooth connection call after querying, then, the mobile phone A can display an interface 517 such as shown in (1) of Figure 5B (for prompting whether to request the mobile phone C to join the smooth connection call), and the user can pass the interface 517 The control 516 in initiates a call back to the mobile phone C for a smooth call.

S204. In response to a first instruction input by the first user on the first interface, the first terminal sends a first message to the second terminal.

Wherein, the first message is used to prompt and request the third terminal to join the VoIP call. Optionally, the first message may carry the identifier of the third terminal. Optionally, the first message may be inviteMP signaling.

Taking the first terminal as the above-mentioned mobile phone A, the second terminal as the above-mentioned mobile phone B, and the third terminal as the above-mentioned mobile phone C, the carrier call is a PSTN call, and the VoIP call is a smooth call as an example. As an example, as shown in Figure 5A ( As shown in 1), in response to the first instruction input by the user on the interface 509, that is, the instruction for the user to click the "Yes" button in the control 511, the mobile phone A determines that the user wants to initiate a call back for a smooth call to the mobile phone C, then the mobile phone A Send the first message to mobile phone B, so as to remind mobile phone B that mobile phone C has been requested to join the smooth connection call.

S205. The second terminal presents a third interface according to the first message.

Wherein, the third interface is used to prompt that the third terminal has been requested to join the VoIP call.

Exemplarily, assuming that the first terminal is the above-mentioned mobile phone A, the second terminal is the above-mentioned mobile phone B, and the third terminal is the above-mentioned mobile phone C, the carrier call is a PSTN call, and the VoIP call is a smooth call. After receiving the PSTN call request, C can send a first message to mobile phone B, and mobile phone B can present a third interface 511 as shown in FIG. Smooth calls.

Optionally, the user of mobile phone B can also choose whether to accept mobile phone C to join the smooth connection call through the third interface. Exemplarily, as shown in FIG. 5D , the third interface 512 includes an option of "accept to join" and a "reject to join". If it is detected that the user of mobile phone B clicks the "accept to join" option, mobile phone B can feed back to mobile phone A the response of accepting mobile phone C to join the smooth connection call, and mobile phone A can continue to execute the subsequent smooth connection callback process. Conversely, if it is detected that the user of mobile phone B clicks the "Refuse to join" option, mobile phone B can feed back to mobile phone A the response of rejecting mobile phone C to join the Changlian call, and mobile phone A will no longer initiate a smooth connection call back to mobile phone C, for example Execute step S104.

S206. The second terminal acquires the identifier (room id) of the second media room according to the first message.

It can be understood that, after receiving the first message from the first terminal, the second terminal learns that the first terminal has requested the third terminal to join the VoIP call. Optionally, the second terminal may obtain the identifier of the second media room, so as to conduct a subsequent multi-party VoIP call in the second media room.

S207. The second terminal sends the identifier of the second media room to the first terminal.

Wherein, the identifier of the second media room is used for the first terminal to join the second media room.

S208. The second terminal sends the identifier of the second media room to the third terminal.

S104. The first terminal sends an uninterrupted call request to the third terminal.

Correspondingly, the third terminal receives the request for an uninterrupted call from the first terminal. Based on this, the third terminal can learn that other terminals invite itself to enter the smooth connection call.

S209. The third terminal presents the second interface.

Wherein, the second interface is used to prompt a VoIP call request from the first terminal. Still taking the first terminal as the above-mentioned mobile phone A, the second terminal as the mobile phone B, and the second terminal as the mobile phone C, the VoIP call request is a smooth connection call request, and the carrier call is a PSTN call as an example. For example, mobile phone C can receive The call request from mobile phone A may display an interface 605 shown in (2) in FIG. 6A , which is used to prompt that the call from Jack is received. As another example, mobile phone C may receive the request for uninterrupted call from mobile phone A, and may display an interface 606 shown in (2) of FIG. 6B , which is used to prompt that the uninterrupted call from Jack is received.

Optionally, if the VoIP call participant has been authorized, the second interface displayed on the third terminal may further include the information of the VoIP call participant. Exemplarily, as shown in (2) of FIG. 8 , after mobile phone C receives the request for an uninterrupted call from mobile phone A, it can display the information of the participants of the uninterrupted call on the interface 802, and can judge according to the information Do you want to join this Connected call.

S210, a key negotiation process.

This step S209 is an optional step. It can be understood that in order to improve data security, all parties to the call can be authenticated before the call is established, including but not limited to negotiating a secret key, and verifying the identities of all parties based on the secret key.

The key agreement process may include a series of signaling interactions. These signalings include but not limited to Update MP signaling.

In the embodiment corresponding to FIG. 11 , the above S105 can be implemented as: S105a. The third terminal responds to the second instruction input by the user on the second interface, and according to the VoIP call request, the second instruction, and the identifier of the second media room, join the second media room, and conduct VoIP calls with the first terminal and the second terminal through the second media room.

Still taking the above mobile phone A as the first terminal, mobile phone B as the second terminal, and mobile phone C as the third terminal, the VoIP call request is a smooth call request, and the operator call is a PSTN call as an example. It can be understood that mobile phone C receives a call from After the mobile phone A requests for a smooth call, in response to the second instruction input by the user to join the smooth call (such as clicking the answering control 603 shown in (2) in Figure 6A), the mobile phone C determines that it needs to connect to the mobile phone A and the mobile phone. For B's smooth call, mobile phone C can join the second media room according to the identification of the second media room, so as to carry out smooth call with mobile phones A and B in the second media room. Wherein, mobile phone C can publish corresponding media data in the second media room, and subscribe to the media data of mobile phone A and mobile phone B through the second media room.

S211. The first terminal joins the second media room according to the identifier of the second media room, and conducts a VoIP call with the third terminal and the second terminal through the second media room.

S212. The second terminal joins the second media room according to the first message and the identifier of the second media room, and conducts a VoIP call with the first terminal and the third terminal through the second media room.

It can be understood that after mobile phone A, mobile phone B and mobile phone C all join the second media room, all three can publish their own media data through the second media room, and subscribe to the media data of other participants in the second media room, so , mobile phone A, mobile phone B, and mobile phone C can exchange media data with each other to realize smooth three-way communication.

Through this embodiment, if the caller terminal of the PSTN call (that is, the third terminal) has the ability to connect the call, the caller terminal of the new PSTN call can be invited to the media room of the VoIP multi-party call, so that the current two-party call is upgraded For multi-party calls.

In addition, this embodiment can also provide more user experience options, that is, the user can freely choose to merge the call (that is, switch the current two-party VoIP call to a three-party VoIP call), maintain the existing VoIP call (not answer the operator's call), choose The user experience is better by answering new operator calls and other methods.

In some other embodiments, the call method provided in the embodiment of the present application may also be applied in a call system including a server. The server can be used to transfer data and signaling between terminals. In this case, the calling method of the embodiment of the present application may be as shown in FIG. 12 .

It should be noted that in FIG. 12, a server including room management function, signaling management function, etc. is used as an example for illustration. In other embodiments, the server in FIG. 12 may also be a server group, that is, include multiple servers.

As a possible implementation, in FIG. 12, step S204 shown in FIG. 11 may be implemented as: S204a. In response to the first instruction input by the first user on the first interface, the first terminal sends a first message to the server; S204b. The server sends the first message to the second terminal. That is to say, the server forwards the first message of the first terminal to the second terminal.

In the embodiment corresponding to FIG. 12, as an optional step, after receiving the first message from the first terminal, the server may execute S301, send a ringing signal to the first terminal; S302, send a ringing signal to the second terminal. bell signal. In this way, the users of the first terminal and the second terminal can learn that they are calling the third terminal to join the VoIP call according to the ringing sound.

As a possible implementation, in FIG. 12, step S104 shown in FIG. 11 may be implemented as: S104a, the first terminal sends a VoIP call request to the server; S104b, the server sends a VoIP call request to the third terminal. That is to say, the server forwards the first message of the first terminal to the third terminal.

In the embodiment corresponding to FIG. 12 , after receiving the VoIP call request from the first terminal, the server may execute step S303 to send a ringing signal to the third terminal. In this way, the user of the third terminal can know the VoIP call to be answered according to the ringing sound.

For implementation details of other steps in FIG. 12 , refer to corresponding descriptions in FIG. 10 and FIG. 11 , and details are not repeated here.

It should be noted that some operations in the processes of the foregoing method embodiments are optionally combined, and/or the order of some operations is optionally changed. Exemplarily, the above S202 can be combined with S203 and S204, that is, when the first terminal determines that the user of the second terminal and the user of the third terminal are friends, the first terminal can present the first interface to prompt the first terminal Whether the user requests the third terminal to join the VoIP call. After responding to the first instruction input by the first user of the first terminal on the first interface, the first terminal sends the first message to the second terminal. Alternatively, the above S202 can also be combined with the sending of the first message in S204, that is, when the first terminal determines that the user of the second terminal and the user of the third terminal are friends, the first terminal directly sends the first message to the second terminal. message, instead of prompting the first user whether to request the third terminal to join the VoIP call.

Moreover, the execution order of the steps of each process is only exemplary, and does not constitute a limitation on the execution order of the steps, and there may be other execution orders among the steps. It is not intended that the order of performance described is the only order in which operations may be performed. There are many ways to reorder the operations described herein will occur to those of ordinary skill in the art. In addition, it should be noted that the details of other processes described herein in conjunction with other methods described herein (for example, the method corresponding to FIG. 11 , the method corresponding to FIG. 12 ) are similarly applicable to the above in conjunction with FIG. 10 described method.

Exemplarily, the sequence between steps S204 and S104 shown in FIG. 11 may be: execute S204 first, or execute S104 first, or execute S104 and S204 simultaneously. As another example, the key agreement process may be performed after S208, or before S208, or at other possible timings. For another example, for S210, S211, and S105a in FIG. 11 , the execution order of these three steps may not be limited.

Alternatively, some steps in the method embodiments may be equivalently replaced with other possible steps. Or, some steps in the method embodiments may be optional, and may be deleted in some usage scenarios. Alternatively, other possible steps may be added to the method embodiments.

Exemplarily, the embodiment corresponding to FIG. 11 takes the second terminal determining the identifier of the switched second media room as an example. In other embodiments, the first terminal may also determine the identifier of the second media room, or, The first terminal and the second terminal determine which media room to switch the smooth connection between the two parties from the first media room to through a negotiation process. Alternatively, the server may also determine the identifier of the second media room. The embodiment of the present application does not limit the specific implementation of determining the identifier of the second media room.

The above embodiments are mainly described by taking the original unconnected call as an example of a two-party uninterrupted call. The technical solutions of the embodiments of the present application are still applicable to the scenario where the original uninterrupted call is a multi-party uninterrupted call.

In addition, the above-mentioned embodiments mainly take receiving a PSTN call during a VoIP call as an example. In other embodiments, the technical solutions of the embodiments of the present application can also be applied to the scenario where another VoIP call is received during a VoIP call, and The scenario of receiving another PSTN call during a PSTN call, and the scenario of receiving a VoIP call during a PSTN call.

In this embodiment of the application, the ongoing call is called the first call, and the newly received call is called the second call. If the first terminal receives the When the third terminal requests a second call (for example, a PSTN call), the first terminal may call back the third terminal in the first call mode (for example, call back the third terminal through a smooth call application). In this way, the first terminal can communicate with the second terminal and the third terminal at the same time, which can effectively improve the communication efficiency.

The embodiment of the present application also provides a call method. For a received call from an operator, if the caller terminal supports the VoIP call function, the caller terminal can be called back through the VoIP call method, so that the terminals communicate through the VoIP call method. As shown in Figure 13, the method includes:

S401. The third terminal sends an operator call request to the first terminal.

For a specific implementation manner of this step, reference may be made to the above step S102.

Exemplarily, taking mobile phone C as the third terminal and mobile phone A as the first terminal as an example, mobile phone C sends an operator call request to Jack's mobile phone A, and mobile phone C can present a call interface as shown in (1) in Figure 15 601. After mobile phone A receives the operator's call request from mobile phone C, it may present a control 1401 as shown in (1) in FIG. 14 to prompt the operator's call to be answered.

S402. The first terminal determines whether the third terminal supports VoIP calls.

For a specific implementation manner of this step, reference may be made to the above step S103.

S403. The first terminal sends a VoIP call request to the third terminal.

For a specific implementation manner of this step, reference may be made to the above step S104.

Exemplarily, when the third terminal supports the VoIP call request, the first terminal sends the VoIP call request to the third terminal.

Optionally, the first terminal may also display a UI to prompt the user to send a VoIP call request to the third terminal, or ask the user whether to send a VoIP call request to the third terminal, and the user agrees to send the VoIP call request (for example, the user enters " In the case of sending a VoIP call request" instruction), the first terminal sends a VoIP call request to the third terminal. Alternatively, the first terminal may display other UIs.

Exemplarily, the first terminal sends a VoIP call request to the third terminal, and may display a window 1402 as shown in (1) in FIG. The user can click the "Cancel" button to control the mobile phone A to stop the smooth connection callback process. After mobile phone A stops calling back smoothly, the missed call of mobile phone C can be processed according to the prior art. For example, after detecting the operation of the user clicking on the answering control 1403 or swiping up on the answering control 1403 , the call of the operator of the mobile phone C is answered. After detecting the user's operation of clicking the hangup control 1404 or swiping the hangup control 1404 up, the operator of the mobile phone C is hung up.

As another example, the first terminal may also display a control 511 such as that shown in (1) of FIG. 5A to ask the user whether to send a call request to the mobile phone C. The terminal sends a request for an uninterrupted call to the third terminal.

Exemplarily, after the first terminal sends a call request to the third terminal, the first terminal may display a call interface such as that shown in (2) of FIG. 14 . The third terminal may display a call interface such as that shown in (2) of FIG. 15 .

S404. The third terminal performs a VoIP call with the first terminal according to the VoIP call request.

For a specific implementation manner of this step, reference may be made to the above step S105.

Exemplarily, taking a VoIP call as an example of a smooth call, the call interfaces of the first terminal and the third terminal during the smooth call process may be shown in (3) of FIG. 14 and (3) of FIG. 15 respectively.

The embodiment of the present application also provides a call method, as shown in Figure 16, the method includes:

S401. The third terminal sends an operator call request to the first terminal.

S501. The first terminal presents a first interface.

Wherein, the first interface may be used to inquire whether to send a VoIP call request to the third terminal, or to prompt that a VoIP call request has been sent to the third terminal. Exemplarily, the first interface may be a prompt interface such as shown in (1) of FIG. 14 , or the first interface includes an inquiry control 511 such as shown in (1) of FIG. 5A .

For the specific implementation of this step S501, reference may be made to the above step S203.

S403. The first terminal sends a VoIP call request to the third terminal.

In some examples, if the first terminal does not perform S501, if it is determined that the third terminal supports the VoIP call request, the first terminal may directly send the VoIP call request to the third terminal.

In some examples, if the first terminal executes S501, the first terminal may send a VoIP call request to the third terminal after detecting an operation instruction input by a user indicating sending a VoIP call request.

S502. The first terminal obtains the identifier of the second media room.

For the first terminal to obtain the identifier of the second media room, refer to the implementation process of the second terminal obtaining the second media room, which will not be repeated here.

S503. The first terminal sends the identifier of the second media room to the third terminal.

S504. The second terminal presents a second interface.

Wherein, the second interface is used to prompt a VoIP call request.

For the specific implementation manner of step S504, reference may be made to the above step S208.

Exemplarily, the second interface may be the interface shown in (2) of FIG. 15 .

S505. A key negotiation process.

S506. The first terminal joins the second media room according to the identifier of the second media room, and conducts a VoIP call with the third terminal through the second media room.

S404a. In response to the second instruction input by the user on the second interface, according to the VoIP call request, the second instruction, and the identifier of the second media room, join the second media room, and conduct a VoIP call with the first terminal through the second media room .

Exemplarily, as shown in (2) of FIG. 15 , in the second interface 605, if the second instruction of the user clicking the answer button 603 is detected, the third terminal joins the second media room according to the identifier of the second media room. room, and make a VoIP call with the first terminal through the second media room.

The embodiment of the present application also provides a call method, which can be applied to a call system including a server. Figure 17 shows a flowchart of this method. In this method, the server can be used to forward signaling and/or data between the first terminal and the third terminal.

Wherein, the specific implementation of steps S403a, S403b, S602, S601, S503a, and S503b in FIG. 17 may refer to the above steps S104a, S104b, S302, S303, S206, and S208. For other steps in FIG. 17 , reference may also be made to the corresponding steps in the foregoing embodiments, which will not be repeated here.

It should be noted that some operations in the processes of the foregoing method embodiments are optionally combined, and/or the order of some operations is optionally changed. Moreover, the execution order of the steps of each process is only exemplary, and does not constitute a limitation on the execution order of the steps, and there may be other execution orders among the steps. It is not intended that the order of performance described is the only order in which operations may be performed. There are many ways to reorder the operations described herein will occur to those of ordinary skill in the art. In addition, it should be noted that the details of other processes described herein in conjunction with other methods described herein (for example, FIG. 10 , the method corresponding to FIG. 11 , and the method corresponding to FIG. 12 ) are similarly applicable to the above in combination The method described in Fig. 13, Fig. 16, Fig. 17.

Alternatively, some steps in the method embodiments may be equivalently replaced by other possible steps. Or, some steps in the method embodiments may be optional, and may be deleted in some usage scenarios. Alternatively, other possible steps may be added in the method embodiments. Exemplarily, step S502 shown in FIG. 17 can also be determined by the server or the third terminal. This embodiment of the present application does not limit the method of determining the second media room identifier, nor does it limit the way the second media room is forwarded between devices. Way.

In some other embodiments, the terminal may provide an entry for setting the call back function of the smooth connection. Exemplarily, as shown in (1)-(3) of FIG. 18 , when the user turns on the switch 1001 , it may further allow the PSTN caller to be answered to call back when the call is in progress. After the user allows the smart callback function to be enabled, as shown in Figure 18, the conditions for the smart callback function can be set. Subsequently, when the terminal detects that the terminal meets the condition, it can intelligently call back the PSTN caller during the smooth connection process, so as to improve the communication efficiency between the terminals.

It should be noted that the interfaces in each embodiment of the present application can be used alone or in combination. The embodiment of the present application does not limit the specific implementation of the interface.

Some other embodiments of the present application provide an apparatus, and the apparatus may be the above-mentioned electronic device (such as a folding screen mobile phone). The apparatus may include: a display screen, memory and one or more processors. The display screen, memory and processor are coupled. The memory is used to store computer program code comprising computer instructions. When the processor executes the computer instructions, the electronic device can execute various functions or steps performed by the mobile phone in the foregoing method embodiments. For the structure of the electronic device, reference may be made to the electronic device shown in FIG. 2A or FIG. 2B .

Wherein, the core structure of the electronic device may be represented as the structure shown in FIG. 19 , and the core structure may include: a processing module 1301 , an input module 1302 , a storage module 1303 , and a display module 1304 .

The processing module 1301 may include at least one of a central processing unit (CPU), an application processor (Application Processor, AP) or a communication processor (Communication Processor, CP). The processing module 1301 may perform operations or data processing related to control and/or communication of at least one of other elements of the user electronic device.

Taking the structure shown in FIG. 19 as the structure in the first terminal as an example, the processing module 1301 is used to conduct a VoIP call with the second terminal; wherein, during the call, the processing module 1301 can call modules such as the communication module 1305 Perform corresponding functions.

Optionally, the processing module 1301 is further configured to determine whether the third user of the third terminal has a friend relationship with the second user of the second terminal.

Taking the structure shown in FIG. 19 as the structure in the third terminal as an example, the processing module 1301 is configured to join the VoIP call according to the VoIP call request received from the first terminal.

Joining the VoIP call according to the VoIP call request includes:

In response to a second instruction input by the user on the second interface, join the VoIP call according to the VoIP call request and the second instruction, where the second instruction is used to indicate to join the VoIP call.

The input module 1302 is configured to obtain instructions or data input by the user, and transmit the obtained instructions or data to other modules of the electronic device. Specifically, the input mode of the input module 1302 may include touch, gesture, approaching the screen, etc., and may also be voice input. For example, the input module may be a screen of an electronic device, acquires user input operations, generates input signals according to the acquired input operations, and transmits the input signals to the processing module 1301 .

The storage module 1303 may include a volatile memory and/or a nonvolatile memory. The storage module is used to store at least one related instruction or data in other modules of the user terminal device. Specifically, the storage module can record the position of the interface where the terminal interface element UI is located.

The display module 1304 may include, for example, a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display, an Organic Light Emitting Diode (OLED) display, a Micro Electro Mechanical System (MEMS) display or an electronic paper display. Used to display user-viewable content (eg, text, images, videos, icons, symbols, etc.).

Taking the structure shown in FIG. 19 as an example in the first terminal, the display module 1304 is configured to present a first interface, and the first interface is used to prompt whether to request the third terminal to join the VoIP call.

The presenting the first interface includes: presenting the first interface in response to the second user being in a friend relationship with the third user.

Taking the structure shown in FIG. 19 as an example in the third terminal, the display module 1304 is configured to present a second interface, and the second interface is used to prompt the VoIP call request.

Optionally, the structure shown in FIG. 19 can also have a communication module 1305, which is used to support the electronic device to communicate with other electronic devices. For example, the communication module can be connected to a network via wireless communication or wired communication to communicate with other personal terminals or a network server. The wireless communication may employ at least one of cellular communication protocols, such as Long Term Evolution (LTE), Long Term Evolution-Advanced (LTE-A), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Universal Mobile Communications System (UMTS), Wireless Broadband (WiBro), or Global System for Mobile Communications (GSM). Wireless communications may include, for example, short-range communications. Short-range communication may include, but is not limited to, at least one of Wireless Fidelity (Wi-Fi), Bluetooth, Near Field Communication (NFC), Magnetic Stripe Transmission (MST), or GNSS.

Taking the structure shown in FIG. 19 as the structure in the first terminal as an example, the communication module 1305 is configured to receive an operator call request from a third terminal during a VoIP call with the second terminal; When the third terminal supports the VoIP call, send the VoIP call request to the third terminal.

The sending the VoIP call request to the third terminal includes: sending the VoIP call request to the third terminal in response to the first instruction input by the first user of the first terminal on the first interface ask.

The sending the VoIP call request to the third terminal includes: sending the VoIP call request to the third terminal in response to determining that the second user and the third user are friends.

Taking the structure shown in FIG. 19 as the structure in the third terminal as an example, the communication module 1305 is configured to send the operator call to the first terminal during the VoIP call between the first terminal and the second terminal. request, receiving a VoIP call request from the first terminal.

The embodiment of the present application also provides a chip system, as shown in FIG. 20 , the chip system includes at least one processor 1401 and at least one interface circuit 1402 . The processor 1401 and the interface circuit 1402 may be interconnected through wires. For example, interface circuit 1402 may be used to receive signals from other devices, such as memory of an electronic device. As another example, the interface circuit 1402 may be used to send signals to other devices (such as the processor 1401). Exemplarily, the interface circuit 1402 can read instructions stored in the memory, and send the instructions to the processor 1401 . When the instructions are executed by the processor 1401, the electronic device may be made to execute various steps in the foregoing embodiments. Of course, the chip system may also include other discrete devices, which is not specifically limited in this embodiment of the present application.

The embodiment of the present application also provides a computer storage medium, the computer storage medium includes computer instructions, and when the computer instructions are run on the above-mentioned electronic device, the electronic device is made to perform the various functions or steps performed by the mobile phone in the above-mentioned method embodiment .

The embodiment of the present application also provides a computer program product, which, when the computer program product is run on a computer, causes the computer to execute each function or step performed by the mobile phone in the method embodiment above.

Through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and brevity of the description, only the division of the above functional modules is used as an example for illustration. In practical applications, the above functions can be assigned by Completion of different functional modules means that the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

In the several embodiments provided in this application, it should be understood that the disclosed devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be Incorporation or may be integrated into another device, or some features may be omitted, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The unit described as a separate component may or may not be physically separated, and the component displayed as a unit may be one physical unit or multiple physical units, that is, it may be located in one place, or may be distributed to multiple different places . Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

If the integrated unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the software product is stored in a storage medium Among them, several instructions are included to make a device (which may be a single-chip microcomputer, a chip, etc.) or a processor (processor) execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: various media that can store program codes such as U disk, mobile hard disk, read only memory (ROM), random access memory (random access memory, RAM), magnetic disk or optical disk.

The above content is only the specific implementation of the application, but the protection scope of the application is not limited thereto, and any changes or replacements within the technical scope disclosed in the application shall be covered within the protection scope of the application. Therefore, the protection scope of the present application should be determined by the protection scope of the claims.

Claims

A communication system, characterized by comprising a first terminal, a second terminal and a third terminal;

The first terminal is configured to conduct a VoIP call with the second terminal, and receive an operator call request from the third terminal during the VoIP call with the second terminal;

The first terminal is further configured to send a VoIP call request to the third terminal when it is determined that the third terminal supports VoIP calls, and the VoIP call request is used to request the third terminal to join the VoIP calls;

The third terminal is configured to receive the VoIP call request from the first terminal, and join the VoIP call according to the VoIP call request.
The system according to claim 1, wherein the first terminal is further configured to present a first interface, and the first interface is used to prompt whether to request the third terminal to join the VoIP call.
The system according to claim 2, wherein the first terminal is configured to send a VoIP call request to the third terminal, comprising: responding to the first user of the first terminal at the first The first instruction input on the interface is to send the VoIP call request to the third terminal.
The system according to any one of claims 1-3, wherein the first terminal is further configured to determine whether the third user of the third terminal and the second user of the second terminal exist friendship;

The first terminal is configured to send a VoIP call request to the third terminal, including: sending the VoIP call request to the third terminal in response to determining that the second user has a friend relationship with the third user ask.
The system according to any one of claims 1-3, wherein the first terminal is configured to present the first interface, comprising: in response to determining that the second user has a friendship relationship with the third user, presenting the Describe the first interface.
A system according to any one of claims 1-5, characterized in that,

The third terminal is further configured to present a second interface, and the second interface is used to prompt the VoIP call request.
A calling method, characterized in that it is applied to a first terminal; the method includes:

performing a VoIP call with the second terminal;

receiving an operator call request from a third terminal during a VoIP call with the second terminal;

When it is determined that the third terminal supports the VoIP call, sending a VoIP call request to the third terminal, where the VoIP call request is used to request the third terminal to join the VoIP call.
The method according to claim 7, further comprising: presenting a first interface, where the first interface is used to prompt whether to request the third terminal to join the VoIP call.
The method according to claim 8, wherein the sending the VoIP call request to the third terminal comprises: responding to a first instruction input by the first user of the first terminal on the first interface Afterwards, sending the VoIP call request to the third terminal.
The method according to any one of claims 7-9, further comprising: determining whether the third user of the third terminal has a friendship relationship with the second user of the second terminal;

The sending the VoIP call request to the third terminal includes: sending the VoIP call request to the third terminal in response to determining that the second user and the third user are friends.
The method according to any one of claims 7-9, wherein the presenting the first interface comprises: presenting the first interface in response to the second user being in a friend relationship with the third user.
A calling method, characterized in that it is applied to a third terminal; the method includes:

During the VoIP call between the first terminal and the second terminal, sending an operator call request to the first terminal;

receiving a VoIP call request from the first terminal, and joining the VoIP call according to the VoIP call request.
The method according to claim 12, wherein after receiving the VoIP call request from the first terminal, the method further comprises:

A second interface is presented, and the second interface is used to prompt the VoIP call request.
The method according to claim 13, wherein joining the VoIP call according to the VoIP call request comprises:

In response to a second instruction input by the user on the second interface, join the VoIP call according to the VoIP call request and the second instruction, where the second instruction is used to indicate to join the VoIP call.
An electronic device, characterized in that it includes: a processor, a memory, the memory is coupled to the processor, the memory is used to store computer program codes, the computer program codes include computer instructions, when the processor Reading the computer instructions from the memory causes the electronic device to execute the method according to any one of claims 7-14.
A computer-readable storage medium, wherein instructions are stored in the computer-readable storage medium, and it is characterized in that, when the instructions are run on the electronic device, the electronic device is made to execute any one of claims 7-14. method described in the item.
A computer program product containing instructions, characterized in that, when the computer program product is run on an electronic device, the electronic device is made to execute the method according to any one of claims 7-14.