CN115941847A

CN115941847A - Call method, electronic device and system

Info

Publication number: CN115941847A
Application number: CN202110977380.4A
Authority: CN
Inventors: 孟繁瑞; 薛睿; 刘丽标; 张世茗; 马中骐
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-08-24
Filing date: 2021-08-24
Publication date: 2023-04-07
Also published as: WO2023025150A1

Abstract

The application provides a communication method, electronic equipment and a system; the method can improve the conversation efficiency between terminals, and comprises the following steps: the method comprises the steps of carrying out VoIP conversation with a second terminal, receiving an operator conversation request from a third terminal in the VoIP conversation process with the second terminal, and sending the VoIP conversation request to the third terminal under the condition that the third terminal supports the VoIP conversation, wherein the VoIP conversation request is used for requesting the third terminal to join the VoIP conversation.

Description

Call method, electronic device and system

Technical Field

The present application relates to the field of terminal technologies, and in particular, to a call method, an electronic device, and a system.

Background

At present, more and more users use various terminals to carry out audio and video calls. Audio and video calls can be divided into voice over internet protocol (VoIP) and operator calls. The VoIP call may be for example a clear connection call,

speech sound>

Video, etc.

In some communication schemes, when a mobile phone is in a VoIP communication, if someone dials an operator communication to the mobile phone, the mobile phone can keep the VoIP communication, and thus, the operator communication cannot be answered. Or the mobile phone can hang up the VoIP call and answer the operator call. For the clear connection example, the user a is performing a VoIP call with the user B through a clear connection application of a mobile phone, and at this time, the friend C dials an operator phone to the mobile phone of the user a, so the user a can only select to answer the operator phone of the friend C, or select to continue to perform the VoIP call with the user B, which results in low call efficiency.

Disclosure of Invention

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

In order to achieve the above object, the embodiments of the present application provide the following technical solutions:

in a first aspect, a call method is provided, which is applicable to a first terminal or a component (such as a chip system) capable of implementing the function of the first terminal; the method comprises the following steps: the VoIP call with the second terminal is carried out, an operator call request from the third terminal is received in the VoIP call process with the second terminal, and the VoIP call request is sent to the third terminal under the condition that the third terminal is determined to support the VoIP call. The VoIP call request is used for requesting the third terminal to join the VoIP call.

According to the communication method provided by the embodiment of the application, when the first terminal identifies the conflict between the VoIP communication and the operator communication, for example, when the first terminal has a new operator communication call in the VoIP communication process, the first terminal can initiate the VoIP communication to the third terminal initiating the operator communication, and the third terminal is added into the current VoIP communication, so that the integration of the VoIP communication and the operator communication is realized, the VoIP communication complaint and the operator communication appeal can be met simultaneously, and the communication efficiency is improved.

In addition, the communication method of the embodiment of the application carries out communication in a VoIP communication mode, and extra communication cost of an operator is not increased.

In some possible designs, the method further comprises: and presenting a first interface, wherein the first interface is used for prompting whether to request the third terminal to join the VoIP call. By the method, whether the user requests the third terminal to join the VoIP call can be prompted, and the user can approve or reject the third terminal to join the current VoIP call according to the current call requirement.

In some possible designs, the method further comprises: and presenting a first interface, wherein the first interface is used for prompting that the third terminal is requested to join the VoIP call.

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

In some possible designs, the method further comprises: determining whether a friend relationship exists between a third user of a third terminal and a second user of a second terminal;

sending a VoIP call request to a third terminal, comprising: and responding to the determination that the second user and the third user are in friend relationship, and sending a VoIP call request to the third terminal. Through the method, only under the condition that the second user and the third user are determined to be in friend relationship, the first terminal sends the VoIP call request to the third terminal, the third user unknown by the second user of the second terminal can be prevented from being pulled into the current VoIP call, the safety line of the call is further improved, and the probability of privacy disclosure is reduced.

In one possible design, a first interface is presented that includes: and presenting the first interface in response to the friend relationship between the second user and the third user. That is, only when it is determined that the second user and the third user are in a friend relationship, the first terminal presents the first interface, so as to prompt the user whether to request the third terminal to join the current VoIP call.

In a second aspect, a call method is provided, where the method is applicable to a third terminal or a component (such as a chip system) capable of implementing or assisting in implementing a function of the third terminal; the method comprises the following steps:

in the process of carrying out internet protocol (VoIP) conversation between a first terminal and a second terminal, sending an operator conversation request to the first terminal, receiving a VoIP conversation request from the first terminal, and adding VoIP conversation according to the VoIP conversation request.

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

and presenting a second interface, wherein the second interface is used for prompting the VoIP call request. Therefore, when the third terminal dials the telephone of the operator, the VoIP call request from the first terminal can be prompted through the interface, and then whether the user of the third terminal chooses to answer the VoIP call or not is guided, so that the third terminal can join the ongoing VoIP call of the first terminal.

In one possible design, joining the VoIP call based on the VoIP call request includes:

and responding to a second instruction input by the user on the second interface, and adding the VoIP call according to the VoIP call request and the second instruction, wherein the second instruction is used for indicating the addition of the VoIP call.

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

the first terminal is used for carrying out VoIP conversation with the second terminal and receiving an operator conversation request from the third terminal in the VoIP conversation process with the second terminal;

the first terminal is also used for sending a VoIP call request to the third terminal under the condition that the third terminal is determined to support the VoIP call, and the VoIP call request is used for requesting the third terminal to join the VoIP call;

and the third terminal is used for receiving the VoIP call request from the first terminal and joining the VoIP call according to the VoIP call request.

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

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

In a possible design, the first terminal is further configured to determine whether a friend relationship exists between a third user of the third terminal and a second user of the second terminal;

the first terminal is used for sending a VoIP call request to the third terminal, and comprises: and responding to the fact that the second user and the third user have friend relation, and sending a VoIP call request to the third terminal.

In one possible design, a first terminal, configured to present a first interface, includes: and 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 configured to prompt a VoIP call request.

In a fourth aspect, a call method is provided, which is applicable to a first terminal or a component (such as a system on a chip) capable of implementing the function of the first terminal; the method comprises the following steps: and receiving an operator call request from the third terminal, and sending the VoIP call request to the third terminal under the condition that the third terminal is determined to support the VoIP call.

According to the call method provided by the embodiment of the application, for a received incoming call of an operator, if the incoming call terminal (namely, the third terminal) supports the VoIP call function, the first terminal can call back the incoming call terminal (the third terminal) in the VoIP call mode, so that the terminals communicate in the VoIP call mode.

Generally, the VoIP call function requires installation of a corresponding VoIP application. A VoIP conversation may provide some functionality that is different from an operator conversation. For instance, in some examples, a VoIP application may integrate screen sharing functionality. The first terminal can use some functions of the VoIP call by initiating the VoIP call to the third terminal, so that the interactive experience in the call process is improved.

In some possible designs, the method further comprises: and presenting a first interface, wherein the first interface is used for prompting whether to send the VoIP call request to the third terminal or prompting that the VoIP call request is sent to the third terminal.

In a fifth aspect, a call method is provided, where the method is applicable to a third terminal or a component (such as a chip system) capable of implementing or assisting in implementing a function of the third terminal; the method comprises the following steps:

and sending an operator call request to the first terminal, receiving a VoIP call request from the first terminal, and carrying out VoIP call with the first terminal according to the VoIP call request.

and presenting a second interface, wherein the second interface is used for prompting the VoIP call request.

In one possible design, conducting a VoIP call with a first terminal according to a VoIP call request includes:

responding to a second instruction input by the user on the second interface, and carrying out VoIP call with the first terminal according to the VoIP call request and the second instruction, wherein the second instruction is used for indicating to answer the VoIP call.

A sixth aspect provides a communication system, including a first terminal and a third terminal;

a first terminal for receiving an operator call request from a third terminal;

the first terminal is also used for sending a VoIP call request to the third terminal under the condition that the third terminal is determined to support the VoIP call;

and the third terminal is used for receiving the VoIP call request from the first terminal and carrying out 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, where 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 having a function of implementing the call method in any of the above aspects and any possible implementation manner. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In an eighth aspect, the present application provides a computer-readable storage medium, which includes computer instructions, when the computer instructions are executed on an electronic device, the electronic device is caused to perform the conversation method according to any one of the above aspects and any one of the possible implementations.

In a ninth aspect, the present application provides a computer program product, which, when run on an electronic device, causes the electronic device to perform a call method according to any one of the aspects and any one of the possible implementations thereof.

In a tenth aspect, there is provided circuitry comprising processing circuitry configured to perform the method of telephony in any of the aspects above and any one of the possible implementations.

In an eleventh aspect, an embodiment of the present application provides a chip system, including at least one processor and at least one interface circuit, where the at least one interface circuit is configured to perform a transceiving function and send an instruction to the at least one processor, and when the at least one processor executes the instruction, the at least one processor performs a call method according to any of the foregoing aspects and any one of the possible implementations of the foregoing aspects.

Drawings

Fig. 1 is a schematic diagram of a system architecture according to an embodiment of the present application;

fig. 2A and fig. 2B are schematic structural diagrams of an electronic device according to an embodiment of the present disclosure;

fig. 3 is a schematic diagram of a call architecture according to an embodiment of the present application;

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

FIGS. 5A-5D are schematic diagrams of four sets of UIs provided by embodiments of the present application;

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

FIGS. 7A-7B are schematic diagrams of two sets of UIs provided by embodiments of the present application;

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

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

fig. 10-fig. 13 are schematic flow charts of a communication method according to an embodiment of the present application;

14-15 are schematic UI diagrams provided by embodiments of the application;

fig. 16-17 are schematic flow charts of a call method according to an embodiment of the present application;

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

fig. 19 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 20 is a schematic structural diagram of a chip system according to an embodiment of the present application.

Detailed Description

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

The call fusion method provided by the embodiment of the application can be applied to the call system 100. The telephony system can include one or more electronic devices. The electronic device may be, but not limited to, a mobile phone, a tablet computer, a television (also referred to as an intelligent screen, a large screen device, etc.), a notebook computer, a handheld computer, a netbook, a vehicle-mounted device (also referred to as a vehicle-mounted device), etc., which is not limited in this embodiment of the present application.

Fig. 1 is a schematic diagram of an exemplary communication system. As shown in fig. 1, the communication system 100 includes a mobile phone 101, a mobile phone 102, and a mobile phone 103. The mobile phone 101, the mobile phone 102, and the mobile phone 103 can communicate with each other via a communication network.

In some embodiments, the call between the handsets may be a carrier call implemented over a carrier network. The mobile phone can be provided with a telephone application, and a user can use the telephone application to realize the conversation of an operator. In some embodiments, the carrier call may comprise a Public Switched Telephone Network (PSTN) call. The PSTN is mainly used as an example herein, but does not constitute a limitation to the operator call.

In some embodiments, the call between the handsets may also be a VoIP call implemented over a non-carrier network. The VoIP call comprises a voice call and/or a video call. Applications (VoIP applications for short) capable of realizing VoIP calls can be installed in the mobile phone, and users can use the applications to realize VoIP calls. VoIP applications include, but are not limited to, open talk,

And so on. Wherein the clear to talk call may be as a stand-alone application or integrated into a system such as a telephony application.

The operator network may be, for example, a network conforming to the third generation partnership project (3 rd generation partnership project) specification. Exemplary, operator networks include, but are not limited to, networks in 4th generation (4 g) mobile communication systems, such as Long Term Evolution (LTE) systems, fifth generation (5 th generation,5 g) mobile communication systems, such as New Radio (NR) systems, and future communication systems, such as the sixth generation (6 th generation,6 g) mobile communication systems.

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

In some embodiments, the telephony system 100 also includes a server 104. And a server 104 for storing call related information. The call related information includes, but is not limited to, whether the handset supports a VoIP call. Taking VoIP conversation as the open connection conversation as an example, the conversation related information of the mobile phone includes whether the mobile phone supports the open connection conversation. The support of the open connection call means that the mobile phone number corresponding to the mobile phone has opened an open connection call service (a preset service), and the mobile phone is currently installed with an open connection call application (a preset application program). The clear talk application may be integrated into the telephony application or the clear talk application may be a stand-alone 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 the terminal managed by the server (or the terminal subscribed to the call related information). Or, the server may send the updated call related information to the terminal according to a preset period. Or after receiving a request for acquiring the call related information from the terminal, 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 the call related information to the terminal.

It is noted that the telephony system 100 may include one or more servers. One server may have multiple functions or different functions may be implemented by different servers. For example, the telephony system 100 may also include a server 105 (not shown in FIG. 1). The server 105 may 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 may also process call instructions during the call, such as sending and receiving call requests and call responses, so as to ensure smooth call progress. As another example, the telephony system 100 can also include a server 106 (not shown in figure 1) that can be used to create one or more media rooms. Subsequently, different handsets can join different media rooms. After the mobile phone joins the media room, the mobile phone can collect the media data of the mobile phone and issue the media data, and other devices in the same room can subscribe the media data of the mobile phone. The media data includes, but is 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, and thus, the PSTN call cannot be answered. Or, the mobile phone can hang up the VoIP call and answer the PSTN call. In the open communication example, the user a is making a VoIP call with the user B through the open communication application of the mobile phone, and at this time, the friend C makes a PSTN call to the mobile phone of the user a, so the user a can only select to answer the PSTN call of the friend C, or select to continue making a VoIP call with the user B.

In order to solve the above problem, an embodiment of the present application provides a call fusion method. When the mobile phone 101 is performing a VoIP call (e.g., a clear connection call) with the mobile phone 102, if the mobile phone 101 receives a call from the mobile phone 103, the mobile phone 101 may query the server whether the mobile phone number of the mobile phone 103 has the VoIP call service (e.g., a clear connection call service) enabled, or the mobile phone 101 may query locally stored call related information of the mobile phone 103 previously acquired from the server.

It should be noted that the mobile phone 101 may query, from the server, call related information of other mobile phones that is authorized to be obtained, and may locally store the call related information. The storage time limit may be set, that is, within the preset time limit, the mobile phone 101 may locally query the call related information of other mobile phones authorized to be obtained, and when the preset time limit is reached, the mobile phone 101 automatically deletes the call related information, so as to ensure the security of the call related information as much as possible.

In some cases, upon a query, the handset 101 may initiate a VoIP call to the handset 103 if the VoIP service has been enabled by the handset number of the handset 103. Thus, after the user of the handset 103 agrees to answer the VoIP call, the handset 103 can participate in the VoIP call between the handset 101 and the handset 102. That is to say, in the embodiment of the present application, a user initiating a PSTN call can be added to a current VoIP call, and for the user of the current VoIP call, the current VoIP call can be maintained without interruption, and a call of a new user can also be answered, so that the call efficiency can be improved.

Still taking the mobile phone 101 as an example of the electronic device in the call system 100, fig. 2A shows a schematic structural diagram of the mobile phone 101.

The handset 101 may include a processor 110, an external memory interface 120, an internal memory 121, a Universal Serial Bus (USB) interface 130, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, and the like.

It is to be understood that the illustrated structure of the embodiment of the present invention does not specifically limit the mobile phone 101. In other embodiments of the present application, the cell phone 101 may include more or fewer components than shown, or combine certain components, or split certain components, or arrange different components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Processor 110 may include one or more processing units, such as: the processor 110 may include an Application Processor (AP), a modem processor, a Graphics Processing Unit (GPU), an Image Signal Processor (ISP), a controller, a memory, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural-Network Processing Unit (NPU), etc. The different processing units may be separate devices or may be integrated into one or more processors.

A memory may also be provided in processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that have just been used or recycled by the processor 110. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Avoiding repeated accesses reduces the latency of the processor 110, thereby increasing 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, the baseband processor, and the like.

The

antennas

1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the handset 101 may be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may 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 a solution including wireless communication of 2G/3G/4G/5G and the like applied to the handset 101. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a Low Noise Amplifier (LNA), and the like. The mobile communication module 150 may receive the electromagnetic wave from the antenna 1, filter, amplify, etc. the received electromagnetic wave, and transmit the electromagnetic wave to the modem processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 1 to radiate the electromagnetic wave. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the same device as at least some of the modules of the processor 110.

The wireless communication module 160 may provide a solution for wireless communication applied to the mobile phone 101, including Wireless Local Area Networks (WLANs), such as Wi-Fi networks, bluetooth (BT), global Navigation Satellite Systems (GNSS), frequency Modulation (FM), near Field Communication (NFC), infrared (IR), and the like. 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, performs frequency modulation and filtering on electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves through the antenna 2 to radiate the electromagnetic waves.

In some embodiments, antenna 1 of the handset 101 is coupled to the mobile communication module 150 and antenna 2 is coupled to the wireless communication module 160 so that the handset 101 can communicate with networks and other devices through wireless communication techniques. The wireless communication technology may include global system for mobile communications (GSM), general Packet Radio Service (GPRS), code division multiple access (code division multiple access, CDMA), 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 technologies, among others. The GNSS may include a Global Positioning System (GPS), a global navigation satellite system (GLONASS), a beidou satellite navigation system (BDS), a quasi-zenith satellite system (QZSS), and/or a Satellite Based Augmentation System (SBAS).

The mobile phone 101 implements a 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 an application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 194 is used to display images, video, and the like. The display screen 194 includes a display panel. The display panel may be a Liquid Crystal Display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (active-matrix organic light-emitting diode, AMOLED), a flexible light-emitting diode (FLED), a miniature, a Micro-oeld, a quantum dot light-emitting diode (QLED), or the like. In some embodiments, the cell phone 101 may include 1 or N display screens 194, N being a positive integer greater than 1.

The mobile phone 101 may implement a shooting function through the ISP, the camera 193, the video codec, the GPU, the display screen 194, the application processor, and the like.

The ISP is used to process the data fed back by the camera 193. For example, when a photo is taken, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing and converting into an image visible to naked eyes. The ISP can also carry out algorithm optimization on the noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in camera 193.

The camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image to the photosensitive element. The photosensitive element may be a Charge Coupled Device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The light sensing element converts the optical signal into an electrical signal, which is then passed to the ISP where it is converted into a digital image signal. And the ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into image signal in standard RGB, YUV and other formats. In some embodiments, the handset 101 may include 1 or N cameras 193, N being a positive integer greater than 1.

The digital signal processor is used for processing digital signals, and can process digital image signals and other digital signals. For example, when the handset 101 is making frequency point selection, the digital signal processor is used to perform fourier transform and the like on the frequency point energy.

Video codecs are used to compress or decompress digital video. The handset 101 may support one or more video codecs. Thus, the mobile phone 101 can play or record video in a plurality of encoding formats, such as: moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, and the like.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to extend the storage capability 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. For example, files such as music, video, etc. are saved in an external memory card.

The internal memory 121 may be used to store computer-executable program code, which includes instructions. The processor 110 executes various functional applications and data processing of the cellular phone 101 by executing instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. The storage program area may store an operating system, an application program (such as a sound playing function, an image playing function, etc.) required by at least one function, and the like. The data storage 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 further include a nonvolatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (UFS), and the like.

The mobile phone 101 can implement an 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 playing, recording, etc.

The audio module 170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a 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 disposed in the processor 110, or some functional modules of the audio module 170 may be disposed in the processor 110.

The speaker 170A, also called a "horn", is used to convert the audio electrical signal into an acoustic signal. The cellular phone 101 can listen to music through the speaker 170A or listen to a hands-free call.

The receiver 170B, also called "earpiece", is used to convert the electrical audio signal into an acoustic signal. When the mobile phone 101 receives a call or voice information, it is possible to receive voice by placing the receiver 170B close to the ear.

The microphone 170C, also called "microphone" or "microphone", converts a sound signal into an electrical signal. When making a call or transmitting voice information, the user can input a voice signal to the microphone 170C by speaking near the microphone 170C through the mouth. The handset 101 may be provided with at least one microphone 170C. In other embodiments, the mobile phone 101 may be provided with two microphones 170C to achieve a noise reduction function in addition to collecting sound signals. In other embodiments, the mobile phone 101 may further include three, four, or more microphones 170C to collect sound signals, reduce noise, identify sound sources, and implement directional recording functions.

The earphone interface 170D is used to connect a wired earphone. The headset interface 170D may be the USB interface 130, or may be a 3.5mm open mobile electronic device platform (OMTP) standard interface, a cellular telecommunications industry association (cellular telecommunications industry association) standard interface of the USA.

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.

Of course, the mobile phone 101 may further include a charging management module, a power management module, a battery, a key, an indicator, and 1 or more SIM card interfaces, which is 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 in fig. 2A, and the server 104 can have more or less components than the structure shown in fig. 2A, or combine some components, or split some components, or arrange different components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

For example, as shown in fig. 2B, server 104 may include a processor 401 (optionally including a processor 408), a memory 403, a transceiver 404, and so forth.

Wherein, a channel can be included between the components for transmitting information between the components.

A transceiver 404 for communicating with other devices or communication networks using protocols such as ethernet, WLAN, etc.

For details of the processor and the memory, please refer to the description of the related structure in the terminal of fig. 2A, which is not repeated here.

Taking a mobile phone as an example, fig. 3 shows a call architecture diagram of the mobile phone. The call architecture of the mobile phone comprises a call application, a telephony module, a telecom module and a Meetime. The modules are matched with each other to complete the communication function.

In some embodiments, the telephony application may be an incalui. In other embodiments of the present application, the telephony application may be a VoIP application such as an open call. The following embodiments mainly use the call application as a smooth connection call as an example to describe the technical solution, which is stated herein in a unified manner and will not be described in detail below.

The fluent session application may include modules such as an incall activity, an incall serviceimp, and a Call.

The incalActivity may be used to implement a call interface, such as a display dialing interface, an incoming call interface, an outgoing call interface, and the like. Taking the user initiating the calling as an example, the user makes a call through the call interface realized by the incall activity, and the smooth call connection application transmits the call making event to the telecom module.

The incall serviceimp is a call management service extension implementation class. In the embodiment of the present application, the callback function oncalladd may be implemented in the incalserviceimp class, and when the oncalladd is called, the clear connection session application may determine that there is a PSTN call. Calls are Call implementation classes that can be used to record the status of each Call.

And the telecom module can be used for being responsible for controlling the call logic. As a possible implementation manner, the telecom module may include incall service, call, connectionService, connection and the like. Wherein, the incall service is a call management service class. The InCallService class may be used to process call information. Call is a Call implementation class. The Connection service is a call Connection management service, and the Connection is a call Connection implementation class.

In the embodiment of the present application, in a case that the user is a calling party, the user initiates a call through an interface implemented by the incalactivity (such as the interface shown in (2) of fig. 4), and the clear call session application transfers a call event to the collect module. the select module may determine whether the call is a PSTN call or a clear call. If the call dialed by the user is smooth connection, the telecom module transmits the call event to the Meetime.HwVoipservice module, and the Meetime.HwVoipservice module establishes a related media channel and a signaling channel. Thus, the smooth connection conversation between the calling party and the called party can be realized. If the user dials a PSTN telephone, the telecom module transmits the calling event to the telephony module, and the telephony module realizes the PSTN conversation between the calling party and the called party.

When the user is a called party and a PSTN phone calls in, the telecom module can receive an incoming call event from the telecom module and inform an upper layer of the PSTN incoming call event by using a smooth connection call.

As a possible implementation manner, the reporting of the PSTN call event to the fluent call application by the telecom module may be implemented by calling oncalladd. Alternatively, a broadcast transmitter may be provided in the telecom module, and a broadcast receiver may be provided in the open talk application. When the telecom incoming call event is detected by the telecom module, the broadcast is sent, and the smooth call can monitor the broadcast of the PSTN incoming call event through the broadcast receiver so as to determine that a PSTN phone is incoming.

When the user is a called party and a smooth connected call incoming call exists, the telecom module can receive an incoming call event from the meetime.hwVoipservice module and report the smooth connected call to an upper layer smooth connected call application.

In some embodiments, the technical solution of the embodiment of the present application implements detection of a VoIP call and an operator call by extending a telecom module function.

And a telephony module which can be used for being responsible for PSTN call service. Such as being responsible for dialing, hanging up, and changing the state of the phone, such as dialing, ringing, making, etc. The Telephony module may include TelephonyConnectionservice, telephonyConnection. Wherein, telephonyConnectionservice is a connection management service, and TelephonyConnection is a connection implementation class.

In the embodiment of the application, when a PSTN telephone calls in, the telephony module reports a PSTN call event to the telecom module.

The device comprises a Meetime HwVoipService module, which can be used for providing VoIP conversation service. As a possible implementation, the module may include CassVoipConnectionService (VoIP connection management service of a smooth talk application) and CassVoipConnection (VoIP connection implementation class of a smooth talk application).

In the embodiment of the application, when a smooth call incoming call is connected, the meetime.

As one possible implementation, the media cloud shown in fig. 3 may be a server that provides a media service for a smooth connection. The signaling cloud may be a server that provides signaling services for the clear connection session. Media services include, but are not limited to, establishing, maintaining, and updating media channels for parties to a call. Signaling services include, but are not limited to, establishing, maintaining, updating signaling channels between parties to a call, signaling addressing, and the like.

In the following, the call integration method is described specifically by taking a call terminal as a mobile phone as an example.

The application for implementing the VoIP call in the embodiment of the present application may be various applications. Such as a system level application or a user level application. The following description mainly takes the case where a VoIP call is realized by a clear connection session, and the clear connection session can be used as an independent application.

As shown in (1) of fig. 4, the cell phone a may present an interface 501, the interface 501 including icons of a plurality of applications. Such as icon 502 including a clear talk application. When a user's operation, such as clicking, on the icon 502 is detected, the cell 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: input box 504, native information 505, contact information to open a open connection function. The user may search for contacts by entering keywords or enter a cell phone number to dial a clear to connect call in input box 504. The user may also search the contact information 506 for a desired contact to call, and initiate a voice call or a video call through the control 507 corresponding to the contact.

Illustratively, handset a detects that the user has clicked control 507 corresponding to contact Jane (user B), then handset a may send a call request to the server, and the server may send the call request to handset B of contact Jane. Also, handset a may present a call interface 508 such as that shown in (3) of fig. 4.

After Jane answers the connected call, for example, operating an "answer button", jane's mobile phone B may send a call response to the server, which in turn forwards the call response to mobile phone a initiating the call to inform mobile phone a that the call is connected. Alternatively, after the call is connected, the handset a may present a call interface 509 (of the first interface) such as that shown in fig. 4 (4).

In some scenarios, while cell phone a is in a clear connection with cell phone B of Jane (the second user), cell phone C (e.g., the cell phone of Bob (the third user)) may call user Jack of cell phone a (the first user). Specifically, upon detecting an operation of the user indicating initiation of a PSTN call to the cell phone a, such as an operation of the user dialing a PSTN phone through a phone application, the cell phone C may transmit a call request to the cell phone a, and the cell phone C may display a call interface 601 such as shown in (1) of fig. 6A. When handset a receives the call request, handset 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 phone from Bob. The mobile phone a may query the call related information of the mobile phone C of Bob, which may query the call related information from this time, or query the call related information from the server. In some cases, upon inquiry, if the mobile phone number of mobile phone C has opened the open connection call service, then mobile phone a may display a control 511 shown in (1) of fig. 5A to ask the user whether to request to initiate the open connection call to mobile phone C of Bob.

In some examples, if an operation that the user instructs to initiate a open connection call to the cell phone C of Bob is detected, such as detecting that the user clicks a "yes" button (first instruction) shown in (1) of fig. 5A, the cell phone a may initiate a open connection call to the cell phone C through the open connection call application. As a possible implementation, handset a sends a clear connect session request to handset C of Bob. During initiation of the open call, handset a may display a call interface such as that shown in (2) of fig. 5A. Accordingly, after receiving the open connection call request from the mobile phone a, the mobile phone C may pop up an interface 605 (second interface) such as shown in (2) of fig. 6A, for prompting the open connection call from the mobile phone a. Interface 605 includes a control 602 for prompting a clear connection to answer. Optionally, the control 602 shown in (2) of fig. 6A further includes a "listen" control 603, and the listen control 603 is used for listening to the open connection call from Jack. In response to an instruction (second instruction) input by the user, such as clicking a control 603, the mobile phone C joins the open connection call between the mobile phone a and the mobile phone B according to the second instruction, wherein the second instruction is used for instructing to join the open connection call.

In other embodiments, as shown in fig. 6B (1), if cell phone C detects that cell phone a is open-connected during a call to cell phone a, cell phone C may pop up a control 604, such as fig. 6B (2), to prompt whether to join the open-connected call of cell phone a. In one example, if it is detected that the user clicks the "yes" button, cell phone C joins the open connection call of cell phone a. After cell phone C joins the open connection call of cell phone a, cell phone a may display a call interface such as that shown in (3) of fig. 6B.

In this embodiment, the callback process may refer to a process of calling the other party after receiving an incoming PSTN call from the other party. The call-back party can be a call-back through VoIP application such as open connection conversation. Thus, after the callback is successful, the opposite party can join the ongoing VoIP call.

It will be appreciated that handset C can detect whether Bob agrees to answer the open connection call from handset a (Jack). For example, if Bob double-clicking on control 602 is detected, cell phone C determines that Bob agrees to answer the open-link call from cell phone a. For another example, if Bob is detected to click the control 602, the mobile phone C may present a call interface of the open connection call, where the call interface includes an "answer button". Upon detecting Bob's operation, such as clicking on the "answer button," cell phone C determines that Bob agrees to answer the open connection call from cell phone a (Jack). The embodiment of the application does not limit the mode of detecting whether the user agrees to answer the current incoming call or not by the mobile phone C.

Taking the example that the control 602 is double-clicked by Bob, and the mobile phone C determines that Bob agrees to answer the open connection call from the mobile phone a, after determining that Bob agrees to answer the open connection call from the mobile phone a, the mobile phone C may send an open connection call response to the mobile phone a through the server, so as to instruct the mobile phone C to join the open connection call. After receiving the open connection response from the mobile phone C, the mobile phone a connects, and the mobile phone a may display a call interface 512, such as shown in (3) of fig. 5A. Interface 512 may present image information of the parties to the call. For example, interface 512 may include a window 513 for each party to the call, the window being used to present the avatar or real-time video of the party to the call. As can be seen from (3) of fig. 5A, the parties of the open call are increased from the initial Jack, jane to Jack, jane and Bob. Accordingly, after the open communication is connected, the mobile phone C may present an open communication interface such as shown in (3) of fig. 6A.

Therefore, for the mobile phone in the open connection conversation, if the mobile phone receives the PSTN conversation of other mobile phones which open the open connection conversation service, the mobile phone can initiate the open connection conversation to the mobile phone which initiates the PSTN conversation, and thus, the mobile phone which initiates the PSTN conversation can be added into the ongoing open connection conversation. Furthermore, the method can not only not interrupt the smooth conversation of the current user, but also answer a new important incoming call.

In other cases, if the mobile phone number of the mobile phone C is not registered to open the open connection call service, the mobile phone a may perform the operation according to the prior art. For example, handset a may answer the PSTN call of handset C of Bob and hang up the open call with handset B of Jane under the operation of the user. Alternatively, the handset may continue to maintain the current open talk without answering the PSTN call from handset C.

The control used for triggering the mobile phone a to initiate the smooth connection call to the mobile phone C in the embodiment of the present application is not limited to the control 511 shown in fig. 5A. In other embodiments, after the mobile phone a receives a PSTN call from the mobile phone C (mobile phone of Bob), the mobile phone a may display a control 510 such as shown in (1) of fig. 5B, where the control 510 may include a control 516, and the control 516 is configured to trigger the mobile phone to send a corresponding VoIP call request, for example, a user may trigger the mobile phone a to initiate a open connection call request (VoIP call request) to the mobile phone C by operating the control 516.

In other embodiments, the handset a may determine whether the counterpart of the PSTN phone to be answered (e.g., user B of handset B) has a friend relationship with the counterpart of the VoIP phone being answered (e.g., user C of handset C). In some cases, in response to determining that user B is in a friend relationship with user C, cell phone a sends a clear connection request to cell phone C.

Alternatively, in response to determining that user B is in a friend relationship with user C, cell phone a may prompt the user with a first interface for prompting to request cell phone C to join the ongoing connected call, such as displaying a control 511, such as shown in (1) of fig. 5A, so as to prompt the user to invite cell phone C to join the current connected call.

In other cases, if it is determined that user B and user C are not in a friend relationship, based on privacy protection and other considerations, cell phone a does not ask the user whether to request cell phone C to join the ongoing connected call. The user of handset a can process the PSTN phone of handset C according to the current requirements.

For example, the user of cell phone a selects to answer the PSTN call of cell phone C, such as the user sliding the "answer" control 514 of the control 510 shown in (1) of fig. 7A to the right to answer the PSTN call from cell phone C. Optionally, after receiving the PSTN call of the mobile phone C, the mobile phone a automatically hangs up the connection with the mobile phone B.

Alternatively, the user of cell phone a clicks on the hang-up control 515 shown in (1) of fig. 5A to hang up the PSTN phone of cell phone C, so that the user of cell phone a can continue to keep the current open connection with cell phone B.

As a possible implementation manner, different users may backup their respective mobile phone address lists to the server, and accordingly, the server stores the address lists of the respective mobile phones. Subsequently, the mobile phone can inquire the friend relationship among other users from the server. Of course, the mobile phone may also determine the friend relationship between other users in other manners. The embodiment of the present application does not limit this.

It should be noted that, the user B and the user C are in a friend relationship, and the contact information of the user B may be in the address book of the mobile phone C of the user C, or the contact information of the user C may be in the address book of the mobile phone B of the user B.

Or, the user B and the user C are in a friend relationship, and the address book of the mobile phone B may include the contact information of the user C, and the address book of the mobile phone C includes the contact information of the user B.

Or, the user B and the user C are in a friend relationship, the user C may be included in a group of friends in an address list of the mobile phone B, the user B may also be included in a group of friends in an address list of the mobile phone C, and the user C is included in a group of friends in an address list of the mobile phone B. The embodiment of the application does not limit the specific meaning of the friend relationship.

Optionally, in order to reduce the disclosure of the private information, the server may set a certain query condition for the mobile phone that wants to query the friend relationship between other users, and when the query condition is satisfied, the mobile phone has the right to query the friend relationship between other users. Optionally, the query condition may be that the mobile phone queries the friend relationship between friends of the mobile phone. For example, among the user a of the mobile phone a, the user B of the mobile phone B, the user C of the mobile phone C, the user D of the mobile phone D, and the user E of the mobile phone E, the user a and the user B are friends, and the user a and the user C are friends. Then, the mobile phone a can query whether the user B and the user C are in a friend relationship (because both the users B and C are friends of the user a), the mobile phone a cannot query whether the user D and the user E are in a friend relationship, and the mobile phone a cannot query whether the user B and the user E are in a friend relationship. The embodiments of the present application do not limit the query condition.

For example, also taking the above mobile phones a, B, and C as examples, jane may back up the address book of the mobile phone B to the server, and Bob may back up the address book of the mobile phone C to the server. As shown in (1) of fig. 7A, during the process of a smooth connection session between Jack handset a and Jane handset B, handset a hears the PSTN call from Bob handset C and displays an interface 701, where interface 701 includes a control 510 for prompting the PSTN call. The mobile phone a may send a query request to the server for querying whether the user B (Jane) and the user C (Bob) are in a friend relationship. And the server sends an inquiry response to the mobile phone A, wherein the inquiry response comprises information indicating whether the mobile phone A is in a friend relationship. Assuming that the query response indicates that users B and C are in a friend relationship, and if cell phone a determines that cell phones B and C can participate in the smooth connection call together, cell phone a may present a control 702, such as shown in (1) of fig. 7A, in interface 701 to ask whether the user invites Bob to join the ongoing smooth connection call. When it is detected that the user indicates to invite Bob to the ongoing open-connected call, for example, by clicking the "yes" button shown in (1) of fig. 7A, the handset a may call Bob via the open-connected call, and may display a call interface such as shown in (2) of fig. 7A. After the call is connected, the mobile phones A, B and C can carry out smooth connection conversation of three parties. The interface of the mobile phone a during the three-party smooth call connection process can be as shown in (3) of fig. 7A.

In other embodiments, during the process of the mobile phone a calling back to the mobile phone C (i.e. the mobile phone a calls the mobile phone C through the VoIP application such as the open connected call), the mobile phone a may notify the mobile phone C of the information of the participant of the current open connected call. As a possible implementation, the mobile phone a sends the participant information to the 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. For example, the user of the mobile phone C dials the carrier, and during the dialing process, the mobile phone C may display an interface such as that shown in (1) of fig. 8. When the mobile phone C answers the call back from the mobile phone a through the open connected call application, the mobile phone C may display an interface 802 as shown in (2) of fig. 8, where the interface 802 includes a control 801, and the control 801 may include information of a participant of the open connected call. Thus, the user C (Bob) of the mobile phone C can know the participants of the ongoing smooth connection call, and accordingly, judge whether to join the smooth connection call. After the mobile phone C joins the smooth connection, a call interface such as that shown in (3) of fig. 8 may be displayed.

Certainly, the mobile phone a may also send other related information of the current smooth connected call to the mobile phone C, so that the user C of the mobile phone C can determine whether to access the ongoing smooth connected call according to the information.

Optionally, in order to enhance the security level of the 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, the mobile phone a may send a notification message to the mobile phone B to notify the mobile phone C that the smooth connection may be joined. After receiving the notification message from the mobile phone a, the mobile phone B may present a window 901, such as shown in fig. 9, for inquiring whether the mobile phone C is authorized to obtain the call information of the mobile phone B. If the user clicks the option "yes" is detected, it means that the mobile phone C can obtain call information of the mobile phone B (for example, identity information of the user of the mobile phone B) in a subsequent process. For example, if the user of the mobile phone B clicks the option "yes" in the window 901 shown in fig. 9, when the subsequent mobile phone a calls back the mobile phone C through the smooth connection session, the mobile phone C may display the control 801 shown in (2) in fig. 8, which is used to prompt the user of the mobile phone C with the identity information of the current participant of the smooth connection session.

Alternatively, an interface for authorizing call information may be displayed on the mobile phone a. For example, a message indicating "whether Bob is allowed to obtain the identity information of each currently calling party" is displayed on the mobile phone a. Or, there may be other prompting manners on the mobile phone a, and the implementation of the present application does not limit the specific interface presentation manner.

Taking an ongoing VoIP call as an example of a smooth connection call, it should be noted that the ongoing smooth connection call may be a three-party or more smooth connection call. Some of the parties may agree to authorize their information to the third terminal and others may not agree to authorize their information to the third terminal. Accordingly, the third terminal can view the information of the authorized party through the interface, and the third terminal cannot view the information of the unauthorized party.

Alternatively, the user may also set the call information visible to the contact. Then, under the condition that the user of the mobile phone B and the user of the mobile phone C are confirmed to be in a friend relationship, the mobile phone C can also acquire the identity information of the currently smooth connected call participant.

Fig. 10 shows a flow of a call method according to an embodiment of the present application. Referring to fig. 10, the method includes:

s101, the first terminal and the second terminal carry out VoIP communication.

For example, taking the first terminal as the mobile phone a, the second terminal as the mobile phone B, and the VoIP call as the open connection call, as shown in (1) - (2) of fig. 4, the mobile phone a may initiate the open connection call to the mobile phone B through the open connection call application. Wherein, after the mobile connection session is dialed and before the mobile connection session is established, the call interface of the mobile phone a is as shown in (3) of fig. 4, and after the mobile connection session is established, the call interface of the mobile phone a is as shown in (4) of fig. 4.

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

Correspondingly, the first terminal receives the operator call request of the third terminal.

Here, taking the first terminal as the mobile phone a, the second terminal as the mobile phone B, the third terminal as the mobile phone C, the VoIP call is a smooth connection call, and the carrier call is a PSTN call, for example, as shown in (1) of fig. 5A, the mobile phone C sends a PSTN call request to the mobile phone a while the mobile phone a and the mobile phone B are in a smooth connection call. Alternatively, the handset C may display the call interface 601 shown in (1) of fig. 6A before the PSTN call is connected. After receiving the PSTN call of the mobile phone C of Bob, the mobile phone a may display an interface 509 for prompting the PSTN call from the mobile phone C.

For another example, as shown in (1) of fig. 5B, when the mobile phone a and the mobile phone B are in a smooth connection session, the mobile phone a receives the PSTN call of the mobile phone C of Bob, and displays a control 517 for prompting the PSTN call from the mobile phone C.

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 it is determined that the mobile phone C supports the open connection call, the mobile phone a may automatically send the open connection call request to the mobile phone C, and the mobile phone a is triggered to send the open connection call request without inputting an instruction by the user. Taking fig. 5B as an example, after the mobile phone C connects a smooth call, the mobile phone a may display the interface shown in (3) of fig. 5B.

S103, the first terminal determines whether the third terminal supports the VoIP conversation.

As a possible implementation manner, the first terminal (such as the mobile phone a) has previously inquired the call related information of the third terminal (such as the mobile phone C) from the server (including whether the third terminal supports the VoIP call (such as the open connection)), and stores the information locally, so that the first terminal can inquire whether the third terminal supports the VoIP call from the local. Or the first terminal does not store the call related information of the third terminal, then the first terminal may acquire, from the server, whether the third terminal supports the VoIP call.

In this embodiment, if the third terminal supports the VoIP call, the first terminal may call back the third terminal through a VoIP call application (e.g., a clear connection call application), so that the third terminal can access the ongoing VoIP call. The process of the first terminal calling back the third terminal includes the following steps S104 to S105. On the contrary, if the first terminal does not support the VoIP call, as a possible implementation manner, the first terminal continues to use the prior art to handle the operator call (such as the PSTN call) of the third terminal.

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

Accordingly, the third terminal receives a VoIP call request from the first terminal.

Alternatively, the open communication request may be invite multi-party (invite mp) signaling.

Optionally, the first terminal sends a VoIP call request to the third terminal through the server, where the VoIP call request is used to request the third terminal to join the VoIP call between the first terminal and the second terminal.

For example, the first terminal is the mobile phone a, the second terminal is the mobile phone B, the third terminal is the mobile phone C, the VoIP call is a smooth connection call, and the operator call is a PSTN call, and the mobile phone a sends a smooth connection call request to the mobile phone C. Before the open connection call is connected, the mobile phone a may display a call interface as shown in (2) of fig. 5A, and the mobile phone C may display a call interface 605 as shown in (2) of fig. 6A or a call interface 606 as shown in (2) of fig. 6B. Details of the interface 605 and the interface 606 can be found in the above embodiments.

And S105, the third terminal joins the VoIP call according to the VoIP call request.

For example, still taking the first terminal as the mobile phone a, the second terminal as the mobile phone B, the third terminal as the mobile phone C, the VoIP call is a smooth connection call, and the operator call is a PSTN call, in an example, after the mobile phone C receives a smooth connection call request from the mobile phone a, the mobile phone C may join the smooth connection call between the mobile phone a and the mobile phone B. Optionally, the mobile phone C may join the open connection call between the mobile phone a and the mobile phone B based on an instruction input by the user. For example, the mobile phone C joins the open call between the mobile phone a and the mobile phone B in response to an instruction from the user to click the control 603 shown in (2) of fig. 6A. For another example, the mobile phone C joins the open connection call between the mobile phone a and the mobile phone B in response to the user clicking the "yes" button of the control 604 shown in (2) of fig. 6B.

By the aid of the communication method, when the conflict between the VoIP communication and the operator communication is identified, for example, when a new operator communication call is incoming in the VoIP communication process, the VoIP communication can be initiated to the third terminal of the new operator communication, the third terminal is added into the current VoIP communication, the VoIP communication and the operator communication are integrated, the VoIP communication complaint and the operator communication appeal can be met simultaneously, and the communication efficiency is improved.

Optionally, the 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 conversation 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.

The specific way in which the terminal joins the media room can be found in the prior art, and for example, the terminal can call an interface of the system to join the first media room.

As one possible implementation manner, on the basis of S201, step S101 in fig. 10 may be implemented as the following step S101a:

s101a, the first terminal and the second terminal carry out VoIP conversation through the first media room.

As a possible implementation manner, after the first terminal joins the first media room, the first terminal may collect local media data and may 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 may only collect audio data, and if the VoIP call between the first terminal and the second terminal is a video call, the mobile phone may collect audio data and image data.

The second terminal may subscribe to media data of one or more devices in the same media room, such as audio and/or video data of the first terminal. Taking the first terminal as the mobile phone a and the second terminal as the mobile phone B as an example, as shown in fig. 4, in a scenario where Jack and Jane have two parties in a smooth video call, the mobile phone a and the mobile phone B subscribe to audio and video data of each other by default. After the mobile phone a subscribes to the audio data and the video data of the mobile phone B, the mobile phone a can acquire the audio data and the video data acquired by the mobile phone B from the mobile phone B, and display a call interface shown in (4) of fig. 4 to play the audio data acquired by the mobile phone B. Similarly, after subscribing the audio data and the video data of the mobile phone a, the mobile phone B can acquire the audio data and the video data acquired by the mobile phone a from the mobile phone a, display a corresponding call interface including the video data, and play the audio data acquired by the mobile phone a.

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

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

Taking the first terminal as the mobile phone a, the second terminal as the mobile phone B, the third terminal as the mobile phone C, the operator call is a PSTN call, and the VoIP call is a smooth connection call, as shown in (1) of fig. 5A, when the mobile phone a and the mobile phone B are in a smooth connection call, the mobile phone a receives the PSTN call of the mobile phone C of Bob.

As a possible implementation manner, a broadcast listener may be disposed in the mobile phone a, and configured to listen to the first broadcast from the telecom module, where the first broadcast is a broadcast of a PSTN incoming call event.

As another possible implementation manner, the mobile phone a may implement the callback function oncalladd in an incalservice module of the open connected call application, and when the oncalladd is called, the mobile phone a may determine that there is a PSTN call.

Other implementation details of step S102 may refer to the corresponding description in fig. 10, and are not described herein again.

S103, the first terminal determines whether the third terminal supports the VoIP call.

Taking the first terminal as the mobile phone a, the second terminal as the mobile phone B, the third terminal as the mobile phone C, the operator call is a PSTN call, and the VoIP call is a smooth connection call, for example, optionally, if the mobile phone C supports the smooth connection call, the mobile phone a may apply a callback mobile phone C through the smooth connection call, so that the mobile phone C can access the ongoing smooth connection call. The process of handset a calling back to handset C includes the following steps S105-S115. On the contrary, if the mobile phone C does not support the smooth connection call, the mobile phone a continues to use the prior art to process the PSTN call of the mobile phone C as a possible implementation manner.

For other implementation details of step S103, reference may be made to the description of the embodiment corresponding to fig. 10, which is not described herein again.

S202, the first terminal determines whether a friend relationship exists between a third user of the third terminal and a second user of the second terminal.

This step S202 is an optional step.

Taking the first terminal as the mobile phone a, the second terminal as the mobile phone B, the third terminal as the mobile phone C, the operator call is a PSTN call, and the VoIP call is a smooth connection call as an example, optionally, after receiving the PSTN call from the mobile phone C, the mobile phone a may query whether the user of the mobile phone B has a friend relationship with the user of the mobile phone C. In some examples, if the mobile phone a determines that the user of the mobile phone B has a friend relationship with the user of the mobile phone C, the mobile phone a may perform step S203 to present a first interface to prompt whether to request the mobile phone C to join the open connection call. In this manner, in response to a first instruction (an instruction for requesting the mobile phone C to join the open connection call) input by the user, the mobile phone a sends a open connection call request to the mobile phone C. If the mobile phone A determines that the user of the mobile phone B does not have a friend relationship with the user of the mobile phone C, the call mechanism in the prior art can be used. For example, as shown in (1) of fig. 7A, after receiving the PSTN call from the cell phone C, the cell phone a may query whether the user of the cell phone B has a friend relationship with the user of the cell phone C. In response to determining that the user of the mobile phone B has a friend relationship with the user of the mobile phone C, the mobile phone a may present an interface 701 to prompt whether to request the mobile phone C to join the smooth connection call.

In other examples, if the mobile phone a determines that the user of the mobile phone B is in a friend relationship with the user of the mobile phone C, the mobile phone a does not present the first interface for prompting whether to request the mobile phone C to join the smooth connection call. Optionally, as shown in (1) of fig. 7B, when detecting that the user Bob of the mobile phone B is in a friend relationship with the user Jane of the mobile phone a, the mobile phone a directly sends a connection and disconnection request to the mobile phone C (the connection and disconnection request is no longer triggered by the user's instruction, such as the first instruction), and displays a call interface 705 shown in (2) of fig. 7B, where the call interface 705 includes a control 704 for prompting that a connection and disconnection call has been initiated to the mobile phone C of Bob. If the user clicks the option of 'refusing to join', the mobile phone A stops sending the smooth connection conversation request to the mobile phone C, and the mobile phone A continues to carry out smooth connection conversation with the mobile phone B. If the user does not click on the option of 'refusing to join', the mobile phone A continues to wait for the mobile phone C to join the smooth connection conversation. After the mobile phone C joins the open connection call, the call interface of the mobile phone a can be as shown in (3) of fig. 7B. In other examples, control 704 is optional.

As a possible implementation manner, step S105 is an optional step, that is, after querying that the mobile phone C supports the smooth connection call, the mobile phone a may directly send the smooth connection call request to the mobile phone C without displaying the callback control. Or, the mobile phone a may directly send the smooth connection request to the mobile phone C without displaying the callback control when it is found that the mobile phone C supports the smooth connection call and the user of the mobile phone C and the user of the mobile phone B are in a friend relationship.

S203, the first terminal displays a first interface.

Alternatively, the step S203 may be performed after S103, that is, not performing S202. Step S203 may be performed after S202. Alternatively, step S203 is not performed.

The first interface can be used for prompting whether to request the third terminal to join the VoIP call. Taking the first terminal as the mobile phone a, the second terminal as the mobile phone B, the third terminal as the mobile phone C, the operator call is a PSTN call, and the VoIP call is a smooth connection call, for example, the mobile phone a receives a PSTN call from the mobile phone C in the process of the smooth connection call with the mobile phone B. And cell phone a can determine that cell phone C supports a open connected session upon query, cell phone a can display an interface 509 such as that shown in (1) of fig. 5A (for prompting whether to request cell phone C to join the open connected session), and the user can initiate a callback of the open connected session to cell phone C through a control 511 in interface 509.

As another example, cell phone a answers the PSTN call from cell phone C during the open communication session with cell phone B. And cell phone a can determine that cell phone C supports a open connected session upon a query, cell phone a can display an interface 517 such as shown in (1) of fig. 5B (for prompting whether to request cell phone C to join the open connected session), and the user can initiate a callback of the open connected session to cell phone C through a control 516 in interface 517.

S204, responding to a first instruction input by the first user on the first interface, and sending a first message to the second terminal by the first terminal.

The first message is used for prompting to request the third terminal to join the VoIP call. Optionally, the first message may carry an identity of the third terminal. Optionally, the first message may be invite signaling.

Taking the first terminal as the mobile phone a, the second terminal as the mobile phone B, the third terminal as the mobile phone C, the operator call is a PSTN call, and the VoIP call is a smooth connection call as an example, as shown in (1) of fig. 5A, in response to a first instruction input by the user at the interface 509, that is, an instruction of the user clicking a "yes" button in the control 511, the mobile phone a determines that the user wants to initiate a callback of the smooth connection call to the mobile phone C, and then the mobile phone a sends a first message to the mobile phone B to prompt the mobile phone B that the mobile phone C is requested to join the smooth connection call.

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

And the third interface is used for prompting that the third terminal is requested to join the VoIP call.

For example, taking the first terminal as the mobile phone a, the second terminal as the mobile phone B, the third terminal as the mobile phone C, the operator call is a PSTN call, and the VoIP call is a smooth connection call, the mobile phone a may send a first message to the mobile phone B after receiving a PSTN call request from the mobile phone C, and the mobile phone B may present a third interface 511 shown in fig. 5C according to the first message, where the third interface 511 is used to prompt the requested mobile phone C to join the ongoing smooth connection call.

Optionally, the user of the mobile phone B may further select whether to accept the mobile phone C to join the open connection call through the third interface. Illustratively, as shown in FIG. 5D, the third interface 512 includes an "accept join" option and a "decline join" option. If the user of the mobile phone B clicks the option of 'accepting the joining', the mobile phone B can feed back a response of accepting the joining of the mobile phone C to the mobile phone A, and the mobile phone A can continue to execute the subsequent smooth continuous callback process. On the contrary, if it is detected that the user of the mobile phone B clicks the "join rejection" option, the mobile phone B may feed back a response to reject the mobile phone C to join the smooth connection call to the mobile phone a, and the mobile phone a does not initiate a smooth connection callback to the mobile phone C any more, for example, does not execute step S104 any more.

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 the second terminal receives the first message from the first terminal, it knows that the first terminal has requested the third terminal to join the VoIP call. Optionally, the second terminal may obtain an identifier of the second media room, so as to perform a subsequent multiparty VoIP call in the second media room.

S207, the second terminal sends the identification of the second media room to the first terminal.

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

S208, the second terminal sends the identification of the second media room to the third terminal.

S104, the first terminal sends a smooth connection session request to the third terminal.

Accordingly, the third terminal receives a clear connection session request from the first terminal. The third terminal can know that other terminals invite itself to enter the smooth connection conversation.

S209, the third terminal presents a second interface.

The second interface is used for prompting a VoIP call request from the first terminal. Still taking the first terminal as the mobile phone a, the second terminal as the mobile phone B, the second terminal as the mobile phone C, the VoIP call request is the open connection call request, and the operator call is the PSTN call as an example, the mobile phone C may receive the open connection call request from the mobile phone a, and may display an interface 605 shown in (2) of fig. 6A, for prompting that the to-be-answered open connection call from Jack is received. As another example, the mobile phone C may receive a connection request from the mobile phone a, and may display an interface 606 shown in (2) of fig. 6B, for prompting that a connection to be answered is received from Jack.

Optionally, in the case that the authorization of the VoIP call participant has been obtained, the second interface displayed on the third terminal may further include information of the participant of the VoIP call. For example, as shown in (2) of fig. 8, after receiving the open connection call request from the mobile phone a, the mobile phone C may display information of participants of the open connection call in the interface 802, and may determine whether to join the open connection call according to the information.

S210, negotiating a key process.

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

The key negotiation flow may include some sequence of signaling interactions. These signaling include, but are not limited to, update MP signaling.

In the embodiment corresponding to fig. 11, the above S105 may be implemented as: s105a, the third terminal responds to a second instruction input by the user on the second interface, joins the second media room according to the VoIP call request, the second instruction and the identifier of the second media room, and carries out VoIP call with the first terminal and the second terminal through the second media room.

Still taking the first terminal as the mobile phone a, the second terminal as the mobile phone B, the third terminal as the mobile phone C, the VoIP call request is a smooth call connection request, and the operator call is a PSTN call, it can be understood that, after receiving the smooth call connection request from the mobile phone a, the mobile phone C responds to a second instruction (for example, clicking the answer control 603 shown in (2) of fig. 6A) input by the user to instruct to join the smooth call connection, and the mobile phone C determines that the smooth call connection between the mobile phone a and the mobile phone B needs to be accessed, and then the mobile phone C can join the second media room according to the identifier of the second media room, so as to perform the smooth call connection between the mobile phone a and the mobile phone B in the second media room. The mobile phone C may publish corresponding media data in the second media room, and subscribe to the media data of the mobile phone a and the mobile phone B through the second media room.

And S211, the first terminal joins the second media room according to the identifier of the second media room, and performs VoIP communication with the third terminal and the second terminal through the second media room.

And S212, the second terminal joins the second media room according to the first message and the identifier of the second media room, and carries out VoIP conversation with the first terminal and the third terminal through the second media room.

It can be understood that after the mobile phone a, the mobile phone B and the mobile phone C are all added into the second media room, the three can publish their own media data through the second media room and subscribe the media data of other participants in the second media room, so that the mobile phone a, the mobile phone B and the mobile phone C can interact with each other to realize smooth communication among three parties.

By the embodiment, if the incoming call terminal (namely, the third terminal) of the PSTN call has the smooth call connection capability, the incoming call terminal of the new PSTN call can be invited to a media room of the VoIP multi-party call, so that the current two-party call is upgraded to the multi-party call.

In addition, the embodiment can also provide more user experience choices, namely, the user can freely select modes of combining calls (namely switching the current two-party VoIP call to a three-party VoIP call), keeping the existing VoIP call (not answering the operator call), selecting answering a new operator call and the like, and the user experience is better.

In other embodiments, the call method provided by the embodiments of the present application may also be applied to a call system including a server. The server may be used to relay data, signaling, etc. between terminals. In this case, the call method according to the embodiment of the present application may be as shown in fig. 12.

It should be noted that, in fig. 12, it is described by way of example that one server includes a room management function, a signaling management function, and the like, and in other embodiments, the server in fig. 12 may also be a server group, that is, include a plurality of servers.

As one possible implementation manner, in fig. 12, the step S204 shown in fig. 11 can be implemented as: s204a, responding to a first instruction input by a first user on a first interface, and sending a first message to a server by a first terminal; s204b, the server sends the first message to the second terminal. That is, the first message of the first terminal is forwarded by the server 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 perform S301, sending a ringing signal to the first terminal; s302, sending a ringing signal to the second terminal. Therefore, the users of the first terminal and the second terminal can know that the third terminal is called to join the VoIP conversation according to the ringing tone.

As one possible implementation manner, in fig. 12, the step S104 shown in fig. 11 can be implemented as: s104a, the first terminal sends a VoIP call request to the server; s104b, the server sends a VoIP conversation request to the third terminal. That is, the first message of the first terminal is forwarded by the server to the third terminal.

In the embodiment corresponding to fig. 12, after receiving the VoIP call request from the first terminal, the server may perform step S303 to send a ringing signal to the third terminal. Therefore, the user of the third terminal can know the VoIP call to be answered according to the ringing tone.

Details of implementation of other steps in fig. 12 can be referred to corresponding descriptions in fig. 10 and fig. 11, and are not described again here.

It should be noted that some operations in the flow of the above-described method embodiments are optionally combined, and/or the order of some operations is optionally changed. For example, S202 may be combined with S203 and S204, that is, when the first terminal determines that the user of the second terminal is in a friend relationship with the user of the third terminal, the first terminal may present a first interface to prompt the user of the first terminal whether to request the third terminal to join the VoIP call. And after responding to a first instruction input by a first user of the first terminal on the first interface, the first terminal sends a first message to the second terminal. Alternatively, the above S202 may 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 is in a friend relationship with the user of the third terminal, the first terminal directly sends the first message to the second terminal, and does not prompt the first user whether to request the third terminal to join the VoIP call.

The execution sequence between the steps of each flow is only exemplary, and does not limit the execution sequence between the steps, and other execution sequences may be used between the steps. It is not intended that the order of execution be the only order in which the operations may be performed. One of ordinary skill in the art will recognize a variety of ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein in connection with other methods described herein (e.g., the method corresponding to fig. 11, the method corresponding to fig. 12) also apply in a similar manner to the method described above in connection with fig. 10.

For example, the sequence between steps S204 and S104 shown in fig. 11 may be: s204 is executed first, or S104 and S204 are executed simultaneously. As another example, the key negotiation process may be performed after S208, or before S208, or at other possible occasions. For another example, in S210, S211, and S105a of fig. 11, the execution sequence between these three steps may not be limited.

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

For example, the embodiment corresponding to fig. 11 takes the second terminal to determine 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, through a negotiation process, which media room the two parties are switched to from the first media room in a clear connection. Alternatively, the identity of the second media room may also be determined by the server. The embodiment of the present application does not limit the specific implementation of determining the identifier of the second media room.

The foregoing embodiment mainly takes the original smooth continuous call as an example of two-party smooth continuous calls, and the technical solution of the embodiment of the present application is still applicable to a scenario where the original smooth continuous call is a multi-party smooth continuous call.

In addition, the above embodiment mainly takes the case that a PSTN call is received in the VoIP conversation process as an example, and in other embodiments, the technical scheme of the embodiment of the present application may also be applicable to a scenario in which another VoIP call is received in the VoIP conversation process, a scenario in which another PSTN call is received in the PSTN conversation process, and a scenario in which a VoIP call is received in the PSTN conversation process.

In the embodiment of the present application, an ongoing call is referred to as a first call, a newly received call is referred to as a second call, and if the first terminal receives a second call (e.g., a PSTN call) request of the third terminal during a first call (e.g., a smooth connection call) with the second terminal, the first terminal may call back the third terminal in the first call manner (e.g., call back the third terminal through a smooth connection call application). Therefore, the first terminal can communicate with the second terminal and the third terminal at the same time, and the communication efficiency can be effectively improved.

The embodiment of the application also provides a call method, wherein for a received incoming call of an operator, if the incoming call terminal supports the VoIP call function, the incoming call terminal can be called back in the VoIP call mode, so that the terminals communicate in the VoIP call mode. As shown in fig. 13, the method includes:

s401, the third terminal sends an operator call request to the first terminal.

The specific implementation manner of this step can be seen in step S102 described above.

Exemplarily, taking the mobile phone C as the third terminal and the mobile phone a as the first terminal, the mobile phone C sends the operator call request to the mobile phone a of Jack, and the mobile phone C may present a call interface 601 as shown in (1) of fig. 15. After receiving the operator call request from the cell phone C, the cell phone a may present a control 1401 as shown in (1) of fig. 14 to prompt the operator call to be answered.

S402, the first terminal determines whether the third terminal supports the VoIP call.

The specific implementation manner of this step can be referred to step S103 described above.

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

The specific implementation manner of this step can be seen in step S104 described above.

Illustratively, in the case where the third terminal supports the VoIP talk request, the first terminal transmits the VoIP talk request to the third terminal.

Optionally, the first terminal may further display a UI to prompt the user that the VoIP call request has been sent to the third terminal, or, in a case that the user is asked whether the VoIP call request is sent to the third terminal and the user agrees to send the VoIP call request (for example, the user inputs a "send VoIP call request" instruction), the first terminal sends the VoIP call request to the third terminal. Alternatively, the first terminal may display other UIs.

Illustratively, the first terminal sends a VoIP call request to the third terminal, and may display a window 1402 as shown in (1) of fig. 14 for prompting that a clear connection call has been initiated to the handset C. The user can click a cancel button to control the mobile phone A to stop the smooth callback flow. After the mobile phone A stops the smooth callback, the missed call of the mobile phone C can be processed according to the prior art. For example, after detecting that the user clicks the answering control 1403 or strokes the answering control 1403, the operator call of the mobile phone C is answered. After detecting that the user clicks the hang-up control 1404 or strokes the hang-up control 1404, the operator call of the mobile phone C is hung up.

As another example, the first terminal may further display a control 511, such as that shown in (1) of fig. 5A, for inquiring whether the user sends a open connection request to the cell phone C, and after detecting that the user clicks the "yes" button, the first terminal sends the open connection request to the third terminal.

Illustratively, after the first terminal transmits the open communication 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.

And S404, the third terminal carries out VoIP conversation with the first terminal according to the VoIP conversation request.

The specific implementation manner of this step can be seen in step S105 described above.

For example, taking a VoIP call as a smooth connection call, call interfaces of the first terminal and the third terminal during the smooth connection call may be as shown in fig. 14 (3) and fig. 15 (3), respectively.

An embodiment of the present application further provides a call method, as shown in fig. 16, where the method includes:

s401, the third terminal sends an operator call request to the first terminal.

S501, the first terminal presents a first interface.

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

The specific implementation of step S501 can be referred to step S203 described above.

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

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

In some examples, if the first terminal performs S501, the first terminal may transmit the VoIP call request to the third terminal after detecting an operation instruction input by the user to instruct transmission of the VoIP call request.

S502, the first terminal obtains the identification of the second media room.

The first terminal obtains the identifier of the second media room, which can refer to the implementation process of obtaining the second media room by the second terminal, and details are not repeated here.

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

And S504, the second terminal presents a second interface.

The second interface is used for prompting the VoIP call request.

The specific implementation of step S504 can be seen in step S208 described above.

Illustratively, the second interface may be an interface such as that shown in (2) of fig. 15.

S505, negotiating a key process.

S506, the first terminal joins the second media room according to the identification of the second media room, and carries out VoIP communication with the third terminal through the second media room.

S404a, responding to a second instruction input by the user on a second interface, adding a second media room according to the VoIP call request, the second instruction and the identifier of the second media room, and carrying out VoIP call with the first terminal through the second media room.

For example, as shown in (2) of fig. 15, in the second interface 605, if a second instruction that the user clicks the listen button 603 is detected, the third terminal joins the second media room according to the identifier of the second media room, and performs a VoIP call with the first terminal through the second media room.

The embodiment of the application also provides a call method, which can be applied to a call system comprising a server. A flow chart of the method is shown in fig. 17. In the method, the server may be configured to forward signaling and/or data between the first terminal and the third terminal.

The specific implementation of steps S403a, S403b, S602, S601, S503a, and S503b in fig. 17 can be referred to steps S104a, S104b, S302, S303, S206, and S208. Other steps in fig. 17 may also refer to corresponding steps in the above embodiments, and are not described again here.

It should be noted that some operations in the flow of the above-described method embodiments are optionally combined, and/or the order of some operations is optionally changed. The execution order between the steps of each flow is only exemplary, and does not limit the execution order between the steps, and other execution orders between the steps may be possible. And is not intended to suggest that the order of execution is the only order in which the operations may be performed. One of ordinary skill in the art will recognize a variety of ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein in connection with other methods described herein (e.g., the methods corresponding to fig. 10, 11, 12) also apply in a similar manner to the methods described above in connection with fig. 13, 16, 17.

Alternatively, certain steps in method embodiments may be equivalently replaced with other possible steps. Alternatively, certain steps in method embodiments may be optional and may be deleted in certain usage scenarios. Alternatively, other possible steps may be added in method embodiments. For example, step S502 shown in fig. 17 may also be determined by the server or the third terminal, and this embodiment of the application does not limit the manner of determining the identifier of the second media room, nor the manner of forwarding the second media room between the devices.

In other embodiments, the terminal may provide an entry for setting the clear callback function. Illustratively, when the user turns on the switch 1001, as shown in (1) to (3) of fig. 18, it is further allowed to call back the party to be answered to the PSTN while the open connection call is being made. After the user allows the smart callback function to be turned on, the conditions for the smart callback function may be set as shown in fig. 18. Subsequently, when the terminal detects that the terminal meets the condition, the PSTN caller can be intelligently called back in the open connection process, so that the communication efficiency between the terminals is improved.

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

Other embodiments of the present application provide an apparatus, which may be the electronic device (e.g., a folding screen handset) described above. The apparatus may include: a display screen, a memory, and one or more processors. The display screen, memory and processor are coupled. The memory is for storing computer program code comprising computer instructions. When the processor executes the computer instructions, the electronic device may perform various functions or steps performed by the mobile phone in the above-described method embodiments. The structure of the electronic device may refer to the electronic device shown in fig. 2A or fig. 2B.

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 (AP), or a Communication Processor (CP). The processing module 1301 may perform operations or data processing related to control and/or communication of at least one of the other elements of the consumer electronic device.

Taking the structure shown in fig. 19 as an example of the structure in the first terminal, the processing module 1301 is configured to perform a VoIP call with the second terminal; during the call, the processing module 1301 may call a module such as the communication module 1305 to perform a corresponding function.

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

Taking the structure shown in fig. 19 as the structure of 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, comprising:

responding to a second instruction input by the user on the second interface, and joining the VoIP call according to the VoIP call request and the second instruction, wherein the second instruction is used for indicating joining the VoIP call.

The input module 1302 is configured to obtain an instruction or data input by a user, and transmit the obtained instruction or data to another module of the electronic device. Specifically, the input mode of the input module 1302 may include touch, gesture, proximity to a screen, and the like, and may also be voice input. For example, the input module may be a screen of the electronic device, acquire an input operation of a user, generate an input signal according to the acquired input operation, and transmit the input signal to the processing module 1301.

The storage module 1303 may include volatile memory and/or nonvolatile memory. The storage module is used for storing instructions or data related to at least one of other modules of the user terminal equipment, and particularly, the storage module can record the position of an interface where a 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 systems (MEMS) display, or an electronic paper display. For displaying content (e.g., text, images, video, icons, symbols, etc.) viewable by a user.

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

The presenting a first interface includes: and responding to the friend relationship between the second user and the third user, and presenting the first interface.

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

Optionally, the structure shown in fig. 19 may further include a communication module 1305 for supporting the electronic device to communicate with other electronic devices. For example, the communication module may 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 Telecommunications System (UMTS), wireless broadband (WiBro), or global system for mobile communications (GSM). The wireless communication may include, for example, short-range communication. The 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 an example of the structure in the first terminal, the communication module 1305 is configured to receive an operator call request from a third terminal in a VoIP call with the second terminal; and under the condition that the third terminal is determined to support the VoIP conversation, sending a VoIP conversation request to the third terminal.

The sending of the VoIP call request to the third terminal includes: and after responding to a first instruction input by a first user of the first terminal on the first interface, sending the VoIP call request to the third terminal.

The sending of the VoIP call request to the third terminal includes: and responding to the fact that the second user and the third user are in friend relationship, and sending the VoIP call request to the third terminal.

Taking the structure shown in fig. 19 as an example of the structure in the third terminal, the communication module 1305 is configured to send an operator call request to the first terminal and receive a VoIP call request from the first terminal in a process that the first terminal and the second terminal perform a VoIP call over internet protocol.

Embodiments of the present application further provide a chip system, as shown in fig. 20, where 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 by lines. For example, the interface circuit 1402 may be used to receive signals from other devices (e.g., a memory of an electronic device). Also for example, the interface circuit 1402 may be used to send signals to other devices, such as the processor 1401. Illustratively, the interface circuit 1402 may read instructions stored in memory and send the instructions to the processor 1401. The instructions, when executed by the processor 1401, may cause the electronic device to perform the various steps in the embodiments described above. Of course, the chip system may further include other discrete devices, which is not specifically limited in this embodiment of the present application.

The embodiment of the present application further provides a computer storage medium, where the computer storage medium includes computer instructions, and when the computer instructions are run on the electronic device, the electronic device is enabled to execute each function or step executed by the mobile phone in the foregoing method embodiment.

The embodiment of the present application further provides a computer program product, which when running on a computer, causes the computer to execute each function or step executed by the mobile phone in the above method embodiments.

Through the description of the foregoing embodiments, it will be clear to those skilled in the art that, for convenience and simplicity of description, only the division of the functional modules is used for illustration, and in practical applications, the above function distribution may be completed by different functional modules as required, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical functional division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another device, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

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

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially or partially contributed to by the prior art, or all or part of the technical solutions may be embodied in the form of a software product, where the software product is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A communication system is characterized by comprising a first terminal, a second terminal and 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 a VoIP call, where the VoIP call request is used to request the third terminal to join the VoIP call;

2. The system of claim 1, wherein the first terminal is further configured to present a first interface, and wherein the first interface is configured to prompt whether to request the third terminal to join the VoIP call.

3. The system of claim 2, wherein the first terminal is configured to send a VoIP call request to the third terminal, comprising: and responding to a first instruction input by a first user of the first terminal on the first interface, and sending the VoIP call request to the third terminal.

4. The system according to any of claims 1-3, wherein the first terminal is further configured to determine whether a third user of the third terminal has a friend relationship with the second user of the second terminal;

the first terminal is configured to send a VoIP call request to the third terminal, and includes: and responding to the determination that the second user has a friend relationship with the third user, and sending the VoIP call request to the third terminal.

5. The system according to any one of claims 1-3, wherein the first terminal, configured to present a first interface, comprises: and presenting the first interface in response to determining that the second user has a friend relationship with the third user.

6. The system of any one of claims 1-5,

the third terminal is further configured to present a second interface, where the second interface is used to prompt the VoIP call request.

7. A conversation method is characterized in that the conversation method is applied to a first terminal; the method comprises the following steps:

carrying out VoIP communication with a second terminal;

receiving an operator call request from a third terminal in the process of carrying out VoIP call with the second terminal;

and under the condition that the third terminal is determined to support the VoIP call, sending a VoIP call request to the third terminal, wherein the VoIP call request is used for requesting the third terminal to join the VoIP call.

8. The method of claim 7, further comprising: and presenting a first interface, wherein the first interface is used for prompting whether to request the third terminal to join the VoIP call.

9. The method of claim 8, wherein sending a VoIP call request to the third terminal comprises: and after responding to a first instruction input by a first user of the first terminal on the first interface, sending the VoIP call request to the third terminal.

10. The method according to any one of claims 7-9, further comprising: determining whether a friend relationship exists between a third user of the third terminal and a second user of the second terminal;

the sending of the VoIP call request to the third terminal includes: and responding to the determination that the second user and the third user are in a friend relationship, and sending the VoIP call request to the third terminal.

11. The method of any of claims 7-9, wherein presenting the first interface comprises: and responding to the friend relationship between the second user and the third user, and presenting the first interface.

12. A conversation method is characterized in that the conversation method is applied to a third terminal; the method comprises the following steps:

the method comprises the steps that in the process of carrying out VoIP (voice over Internet protocol) conversation between a first terminal and a second terminal, an operator conversation request is sent to the first terminal;

and receiving a VoIP call request from the first terminal, and joining the VoIP call according to the VoIP call request.

13. The method of claim 12, wherein after receiving the VoIP call request from the first terminal, the method further comprises:

14. The method of claim 13, wherein joining the VoIP call according to the VoIP call request comprises:

15. An electronic device, comprising: a processor, a memory coupled with the processor, the memory for storing computer program code, the computer program code comprising computer instructions that, when read from the memory by the processor, cause the electronic device to perform the method of any of claims 7-14.

16. A computer-readable storage medium having instructions stored therein, which when run on an electronic device, cause the electronic device to perform the method of any of claims 7-14.

17. A computer program product comprising instructions for causing an electronic device to perform the method according to any of claims 7-14 when the computer program product is run on the electronic device.