CN121056568A - A method and terminal for transferring network calls - Google Patents

Abstract

A transfer method and terminal of network call relates to communication technology field, which can transfer network call on different terminals, promote flexibility of user to answer network call, meet user demand under different scenes, the method includes that first terminal and second terminal establish signaling channel through first server, and establish media channel through second server; the method comprises the steps that after a second terminal receives a user instruction to transfer the network call between a first terminal and a second terminal, a first message is sent to a first server through a signaling channel and used for requesting to transfer the network call between the second terminal and a third terminal, the first server sends a second message to the third terminal according to the first message and used for requesting to transfer the network call between the second terminal and the third terminal, the second message comprises an identification of a media channel, the third terminal joins the media channel through the second server according to the identification of the media channel, and video data and/or audio data are interacted with the first terminal through the media channel.

Description

A method and terminal for transferring network calls

This application is a divisional application. The original application has the application number 202110586980.8 and the original application date is May 27, 2021. The entire contents of the original application are incorporated herein by reference.

Technical Field

This application relates to the field of communication technology, and in particular to a method and terminal for transferring network calls.

Background Technology

VoIP (including audio and video calls) has become a frequently used software in people's daily lives and work, leading to an increasing number of terminals in home and work networks having VoIP software installed. Furthermore, the ability to flexibly transfer VoIP calls between different terminals has become a hot research topic for manufacturers.

Summary of the Invention

This application provides a method and terminal for transferring network calls, which can realize the transfer of network calls on different terminals, improve the flexibility of users in answering network calls, and meet the needs of users in different scenarios.

To achieve the above objectives, the embodiments of this application provide the following technical solutions:

A first aspect provides a network call transfer system, including a first terminal, a second terminal, a third terminal, a first server, and a second server; the first terminal and the second terminal establish a signaling channel through the first server; the first terminal and the second terminal establish a media channel through the second server; the second terminal is used to receive a first instruction from a user, the first instruction being used to instruct the transfer of the network call between the first terminal and the second terminal; the second terminal is also used to, in response to the first instruction, send a first message to the first server through the signaling channel, the first message being used to request the transfer of the network call of the second terminal to the third terminal; the first server is used to, according to the first message, send a second message to the third terminal, the second message being used to request the transfer of the network call of the second terminal to the third terminal, and the second message containing an identifier of the media channel; the third terminal is used to, according to the media channel identifier contained in the second message, join the media channel through the second server; the third terminal is used to interact with the first terminal through the media channel to exchange video data and/or audio data.

Therefore, since the transferred device (i.e., the third terminal) can directly join the media channel originally created for this network call (i.e., the media channel established by the first terminal and the second terminal through the second server), real-time communication between the third terminal and the first terminal can be achieved, thus transferring the network call on the second terminal to the third terminal for answering. Compared to the prior art, where both parties need to exit the current media channel and apply for a new media channel, and the transferred device joins the new media channel to achieve network call transfer, the technical solution provided in this application simplifies the signaling interaction process between the terminal (including the third terminal and the first terminal) and the server (including the first server and the second server) during the entire transfer process, improving the efficiency of network call transfer.

In one possible implementation, after the second terminal receives a call request from the first terminal but has not yet established a network call with the first terminal, the second terminal receives a first instruction; or, after the second terminal receives a call request from the first terminal but has already established a network call with the first terminal, the second terminal receives a first instruction; or, after the second terminal sends a call request to the first terminal but the first terminal has not yet established a network call with the second terminal, the second terminal receives a first instruction; or, after the second terminal sends a call request to the first terminal but the first terminal has already established a network call with the second terminal, the second terminal receives a first instruction.

In other words, users can transfer their current VoIP call immediately upon receiving an incoming call, before the call is connected. Users can also transfer the call after it has been connected. The called party can transfer the call to another device, and the calling party can also transfer the call to another device. Therefore, the technical solution provided in this application embodiment enables users to flexibly transfer VoIP calls, meeting their VoIP call needs in different scenarios.

In one possible implementation, the third terminal is further configured to, upon receiving the second message, output a first prompt, the first prompt being used to ask the user whether they agree to accept the network call transferred by the second terminal; the third terminal joins the media channel through the second server according to the media channel identifier, including: in response to the third terminal receiving the second instruction, the third terminal joins the media channel through the second server according to the media channel identifier, wherein the second instruction is used to instruct the user to agree to accept the network call transferred by the second terminal. Thus, a method for asking a user on a third terminal whether they agree to accept the transfer is provided.

In some other examples, if the second terminal forwards a VoIP call to the third terminal for the first time, the third terminal can output the first prompt, asking the user whether they agree to accept the VoIP call forwarded by the second terminal. Once the user agrees to accept the forwarded VoIP call, when the second terminal forwards the call to the third terminal again, the third terminal can assume the user has agreed and directly display the relevant VoIP call interface (call screen or VoIP call interface). In other examples, the user of the third terminal can pre-authorize receiving VoIP calls forwarded by the second terminal. For example, the user may pre-enable receiving VoIP calls forwarded by the second terminal in the VoIP application or system settings. Then, regardless of whether the third terminal receives the forwarded VoIP call for the first time or the Mth time (M greater than 1), there is no need to output the first prompt; the relevant VoIP call interface will be displayed directly.

In one possible implementation, the second server is further configured to send a third message to the first terminal and the second terminal, the third message being used to trigger the third terminal to join the media channel; the second terminal is further configured to exit the media channel through the second server after receiving the third message.

Understandably, if the second terminal exits the media channel, it will be unable to receive media data exchanged between the first and third terminals. In some other examples, the second terminal may not exit the media channel, in which case it can still receive media data exchanged between the first and third terminals.

In one possible implementation, the third terminal is further configured to receive a third instruction from the user, the third instruction being used to instruct the transfer of the network call on the third terminal to the second terminal; in response to receiving the third instruction, the third terminal sends a fourth message to the first server, the fourth message being used to request the transfer of the network call on the third terminal to the second terminal; the first server is further configured to send a fifth message to the second terminal, the fifth message being used to notify the transfer of the network call on the third terminal to the second terminal; the second terminal is further configured to join a media channel through the second server according to the fifth message; and to interact with the first terminal via the media channel to exchange video data and/or audio data.

In other words, users can operate on a third terminal to instruct the current VoIP call to be migrated back to the original second terminal, thus providing a more comprehensive and flexible VoIP call transfer solution.

In one possible implementation, the second terminal is further configured to receive a fourth instruction from the user, the fourth instruction indicating that a network call on the third terminal be transferred to the second terminal; in response to receiving the fourth instruction, the second terminal sends a sixth message to the first server, the sixth message requesting that a network call on the third terminal be transferred to the second terminal; the first server is further configured to send a seventh message to the second terminal, the seventh message notifying that a network call on the third terminal be transferred to the second terminal; the second terminal is further configured to join a media channel through the second server according to the seventh message; and to interact with the first terminal via the media channel to exchange video data and/or audio data.

In other words, the second terminal retains some control over the current VoIP call. For example, users can operate on the second terminal to instruct VoIP calls originating on the third terminal to be migrated back to the second terminal, thus providing a more comprehensive and flexible VoIP call transfer solution.

In one possible implementation, the second terminal is also used to disconnect the signaling channel from the first server after receiving the third message.

Understandably, after the second terminal disconnects the signaling channel, it completely exits the current network call and no longer controls it. In other examples, the mobile phone can still retain the signaling channel. When the user continues to perform relevant control operations on the second terminal, such as switching back to the network call or ending the network call, the second terminal can forward the relevant control signaling through the signaling channel to execute the relevant control procedures.

In one possible implementation, the second terminal and the third terminal log in to the same account; or, the second terminal and the third terminal log in to different accounts belonging to the same group; or, the second terminal and the third terminal are located in the same communication network.

In one specific embodiment, after receiving the user's instruction to transfer the network call, the second terminal can use wireless communication functions (such as Wi-Fi or Bluetooth) to search for nearby devices. This means the user can transfer the network call on the second terminal to another device near the second terminal. This allows the user to flexibly choose the most suitable nearby device to answer the current network call. For example, a user can transfer a network call from their mobile phone to a smart screen to enjoy a larger video experience and free their hands. In other scenarios, after transferring the network call to a smart screen, more family members or colleagues can be invited to participate in the call. Alternatively, the user can transfer the network call from the smart screen to their mobile phone to protect user privacy or to facilitate movement. For another example, a user can transfer a network call from their mobile phone to an in-vehicle terminal to free their hands while driving. Alternatively, the user can transfer a network call from the in-vehicle terminal to their mobile phone so they can continue answering network calls when leaving the vehicle.

In another specific embodiment, after receiving the user's instruction to transfer the VoIP call, the second terminal can also access the home server to query the associated devices of the second terminal. The associated devices of the second terminal refer to devices logged into the same account as the second terminal, or devices logged into an account belonging to the same family group as the account logged into the second terminal. It should be noted that the associated devices of the second terminal queried through the home server may not be located near the second terminal. In other words, the method provided in this application embodiment can also be applied to transferring the VoIP call function on the second terminal to other remote devices. In this way, the user can choose to transfer the current VoIP call to another more suitable user in the home or work environment. For example, when the user is away, they can transfer the VoIP call on their mobile phone to a smart screen in the home, where a family member can answer the call.

A second aspect provides a method for transferring network calls, applied to a third terminal. In the process of transferring a network call between a second terminal and a first terminal to the third terminal, the second terminal and the first terminal establish a signaling channel through a first server, and the second terminal and the first terminal establish a media channel through the second server. The method includes: the third terminal receiving a first message sent by the first server, the first message requesting the transfer of the network call between the second terminal and the third terminal; and the first message containing an identifier of the media channel; the third terminal joining the media channel through the second server according to the media channel identifier contained in the first message; and exchanging video data and/or audio data with the first terminal through the media channel.

In one possible implementation, after the third terminal receives the first message, the method further includes: the third terminal outputting a first prompt to ask the user whether they agree to accept the network call transferred by the second terminal; the third terminal joining the media channel through the second server according to the media channel identifier contained in the first message, including: in response to the third terminal receiving a second instruction, the third terminal applying to the second server to join the media channel according to the media channel identifier, wherein the second instruction is used to instruct the user to agree to accept the network call transferred by the second terminal.

In one possible implementation, the method further includes: a third terminal receiving a third instruction from a user, the third instruction indicating that the network call on the third terminal be transferred to a second terminal; in response to receiving the third instruction, the third terminal sending a second message to a first server requesting that the network call on the third terminal be transferred to the second terminal.

In one possible implementation, the second terminal and the third terminal log in to the same account; or, the second terminal and the third terminal log in to different accounts belonging to the same group; or, the second terminal and the third terminal are located in the same communication network.

A third aspect provides a method for transferring network calls, applied to a second terminal. The second terminal and a first terminal establish a signaling channel through a first server, and the second terminal and the first terminal establish a media channel through a second server. The method includes: the second terminal receiving a first instruction from a user, the first instruction being used to instruct the transfer of network calls between the first terminal and the second terminal; in response to the first instruction, the second terminal sending a first message to the first server through the signaling channel, the first message being used to request the transfer of network calls of the second terminal to a third terminal; and after receiving a first message that the third terminal has joined the media channel, the second terminal exiting the media channel through the second server.

In one possible implementation, after the second terminal receives a call request from the first terminal but has not yet established a network call with the first terminal, the second terminal receives a first instruction; or, after the second terminal receives a call request from the first terminal but has already established a network call with the first terminal, the second terminal receives a first instruction; or, after the second terminal sends a call request to the first terminal but the first terminal has not yet established a network call with the second terminal, the second terminal receives a first instruction; or, after the second terminal sends a call request to the first terminal but the first terminal has already established a network call with the second terminal, the second terminal receives a first instruction.

In one possible implementation, after the second terminal exits the media channel through the second server, the method further includes: the second terminal receiving a second message requesting that the network call on the third terminal be transferred to the second terminal; the second terminal joining the media channel through the second server according to the second message, and interacting with the first terminal with video data and/or audio data through the media channel.

A fourth aspect provides a method for transferring network calls, applied to a first server. During the process of transferring a network call between the second terminal and the first terminal to a third terminal via a second terminal, wherein the second terminal and the first terminal establish a signaling channel through the first server, and the second terminal and the first terminal establish a media channel through the second server, the method includes: the first server receiving a first message sent by the second terminal, the first message requesting the transfer of the network call of the second terminal to the third terminal; the first server sending a second message to the third terminal, the second message being used by the third terminal to join the media channel; wherein the second message carries an identifier of the media channel.

The fifth aspect provides a terminal including: a processor, a memory, and a touch screen, wherein the memory and the touch screen are coupled to the processor, the memory is used to store computer program code, the computer program code including computer instructions, and when the processor reads the computer instructions from the memory, causes the terminal to perform a network call transfer method as described in the second or third aspect above, and in any possible implementation thereof.

A sixth aspect provides a server comprising: a processor, a memory, and a communication interface, wherein the memory and the communication interface are coupled to the processor, the memory being used to store computer program code, the computer program code including computer instructions, wherein when the processor reads the computer instructions from the memory, the server performs a network call transfer method as described in the fourth aspect above and any possible implementation thereof.

A seventh aspect provides a computer-readable storage medium including computer instructions that, when executed on a terminal, cause the terminal to perform a method for transferring network calls as described in the second or third aspect above, and in any possible implementation thereof.

The eighth aspect provides a computer-readable storage medium including computer instructions that, when executed on a server, cause the server to perform the network call transfer method as described in the fourth aspect above, and in any possible implementation thereof.

The ninth aspect provides a computer program product that, when run on a computer, causes a terminal to perform a method for transferring network calls as described in the second or third aspect above, and in any possible implementation thereof.

The tenth aspect provides a computer program product that, when run on a computer, causes a server to perform a network call transfer method as described in the fourth aspect above and any possible implementation thereof.

The technical effects achievable by the methods, terminals, servers, computer-readable storage media, and computer program products provided in the second to tenth aspects above can be referred to the descriptions of technical effects in the first aspect and the possible implementations therein, and will not be repeated here.

Attached Figure Description

Figure 1 is a schematic diagram of the structure of a network call system provided in an embodiment of this application;

Figure 2 is a structural schematic diagram of a terminal 100 provided in an embodiment of this application;

Figure 3 is a structural schematic diagram of a signaling server 300 provided in an embodiment of this application;

Figure 4 is a schematic diagram of the user interface of some terminals 100 provided in the embodiments of this application;

Figure 5 is a schematic diagram of the user interface of some other terminals 100 provided in the embodiments of this application;

Figure 6A is a schematic diagram of the user interface of some terminals 200 provided in the embodiments of this application;

Figure 6B is a schematic diagram of the user interface of some other terminals 200 provided in the embodiments of this application;

Figure 7A is a schematic diagram of the user interface of some terminals 500 provided in the embodiments of this application;

Figure 7B is a schematic diagram of the user interface of another terminal 500 provided in an embodiment of this application;

Figure 7C is a schematic diagram of the user interface of another terminal 500 provided in an embodiment of this application;

Figure 8 is a schematic diagram of the user interface of another terminal 200 provided in an embodiment of this application;

Figure 9 is a schematic diagram of the user interface of another terminal 100 provided in an embodiment of this application;

Figure 10 is a schematic diagram of the user interface of some other terminals 200 provided in the embodiments of this application;

Figure 11 is a flowchart illustrating a method for transferring network calls according to an embodiment of this application;

Figure 12 is a flowchart illustrating another method for transferring network calls provided in an embodiment of this application;

Figure 13 is a flowchart illustrating another method for transferring network calls provided in an embodiment of this application;

Figure 14 is a flowchart illustrating another method for transferring network calls provided in an embodiment of this application;

Figure 15 is a schematic diagram of the structure of a chip system provided in an embodiment of this application.

Detailed Implementation

In the description of the embodiments of this application, unless otherwise stated, "/" means "or". For example, A/B can mean A or B. "And/or" in this document is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and/or B can mean: A exists alone, A and B exist simultaneously, and B exists alone.

Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of embodiments of this application, unless otherwise stated, "a plurality of" means two or more.

In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

Figure 1 illustrates a VoIP system provided in an embodiment of this application. As shown in Figure 1, the VoIP system includes two or more terminals (e.g., terminal 100, terminal 200), a signaling server 300, and a media server 400. Each of the terminals can establish a communication connection with the signaling server 300 and with the media server 400 through one or more networks.

In this embodiment, terminal 100 can establish a call link with terminal 200 through signaling server 300 and media server 400 to realize network call service between terminal 100 and terminal 200. The network call service provided in this embodiment can be applied to scenarios such as audio calls, video calls, video conferencing, live video streaming, online classes, and internet healthcare.

The signaling server 300 is used to establish a signaling channel between terminal 100 and terminal 200. Terminal 100 and terminal 200 exchange control-related messages in the network call service through this signaling channel, such as establishing a call link, disconnecting a call link, and transferring a call.

The media server 400 is used to establish a media channel between terminal 100 and terminal 200. Terminal 100 and terminal 200 exchange media data through this media channel, which includes video data, audio data, etc.

As users own or use more and more terminals, there is often a need to transfer VoIP calls. Furthermore, the VoIP system described in Figure 1 also includes a terminal 500. Terminal 500 establishes communication connections with signaling server 300 and media server 400 through one or more networks. For example, in a VoIP call between user A on terminal 100 and user B on terminal 200, user B can transfer the VoIP call from terminal 200 to terminal 500 for answering. Optionally, terminal 500 and terminal 200 can be logged into the same user account, or different accounts belonging to the same group (e.g., a family group). Of course, user A can also migrate the VoIP call from terminal 100 to another terminal of user A; this application does not limit this.

In one technical solution, user B can operate terminal 200 to instruct it to transfer the network call on terminal 200 to terminal 500. Firstly, terminal 200 informs terminal 100 via signaling server 300 that it will transfer the network call to terminal 500. Then, terminal 100 exits its current media channel (referred to as media channel 1) via media server 400. Furthermore, terminal 100 creates a new media channel (referred to as media channel 2) via media server 400 and joins it. Terminal 100 then informs terminal 500 of the newly created media channel 2 via signaling server 300. Secondly, terminal 200 exits its current media channel 1 and joins media channel 2 via media server 400. Thus, terminal 100 and terminal 500 establish a new media channel for transmitting media data, meaning user B can continue the network call with user A through terminal 500.

It can be noted that during the process of user B migrating the network call on terminal 200 to terminal 500, the signaling interaction between the terminals (including terminal 100, terminal 200 and terminal 500) and the servers (including signaling server 300 and media server 400) is cumbersome, and the transfer process of the network call takes a long time.

In other scenarios, terminal 100 can also establish communication links with two or more other terminals (e.g., terminal 200, terminal 600) through signaling server 300 and media server 400 to enable network calls between two or more people (including many-to-one, one-to-many, and many-to-many network calls). In this scenario, terminals 100, 200, and 600 all join media channel 1, which terminal 100 requests from media server 400 for this network call. It is understandable that if the above technical solution is still used to migrate a network call from one terminal (e.g., terminal 200) to another terminal (e.g., terminal 500), terminal 200 needs to notify more terminals (terminal 100 and terminal 600) to leave the current media channel 1. Furthermore, after terminal 100 creates a new media channel 2, it also needs to notify more terminals (terminal 200 and terminal 600) to join the current media channel 2. It is evident that the signaling interaction between terminals (including terminals 100, 200, 500, and 600) and servers (including signaling server 300 and media server 400) is more cumbersome, and the transfer process of network calls takes longer.

To address this, this application provides another technical solution: the transferred terminal (i.e., terminal 500) reuses the previous media channel 1, thereby simplifying the signaling interaction between the terminal and the server during the network call migration process, reducing the time consumed in the migration process, and enabling users to flexibly transfer network calls between different terminals. Furthermore, in this application embodiment, the user can also migrate the network call back to the original terminal (i.e., terminal 200), in which case media channel 1 is also directly reused. It is evident that this simplifies the signaling interaction between the terminal and the server during the network call migration process, reduces the time consumed in the migration process, and enables users to flexibly migrate network calls between different terminals.

Figure 2 shows a schematic diagram of the terminal 100. In this embodiment, the terminal 100 may be, for example, a mobile phone, tablet computer, personal computer (PC), personal digital assistant (PDA), smartwatch, netbook, wearable electronic device, augmented reality (AR) device, virtual reality (VR) device, in-vehicle device, smart screen, smart speaker, etc. This application does not impose any special restrictions on the specific form of the terminal.

As shown in Figure 2, the terminal 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.

It is understood that the interface connection relationships between the modules illustrated in the embodiments of the present invention are merely illustrative and do not constitute a structural limitation on the terminal 100. In other embodiments of this application, the terminal 100 may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments. Furthermore, the structure illustrated in the embodiments of the present invention does not constitute a specific limitation on the terminal 100. In other embodiments of this application, the terminal 100 may include more or fewer components than illustrated, or combine certain components, or split certain components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units, such as an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and/or a neural network processing unit (NPU). These different processing units may be independent devices or integrated into one or more processors.

The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

Internal memory 121 can be used to store computer executable program code, which includes instructions. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of terminal 100 (such as audio data, phonebook, etc.). Furthermore, internal memory 121 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. Processor 110 executes various functional applications and data processing of terminal 100 by running instructions stored in internal memory 121 and/or instructions stored in memory located in the processor.

The external storage interface 120 can be used to connect an external storage card, such as a Micro SD card, to expand the storage capacity of the terminal 100. The external storage card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, music, video, and other files can be saved on the external storage card.

The wireless communication function of terminal 100 can be implemented through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc.

Antennas 1 and 2 are used to transmit and receive electromagnetic wave signals. Each antenna in terminal 100 can be used to cover one or more communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with tuning switches.

The mobile communication module 150 can provide solutions for wireless communication applications including 2G/3G/4G/5G/6G on the terminal 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

In some embodiments of this application, terminal 100 can connect to the Internet via cellular network (e.g., 2G/3G/4G/5G/6G network) through mobile communication module 150, and establish communication connections with signaling server 300 and media server 400 respectively.

The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through an audio device (not limited to speaker 170A, receiver 170B, etc.) or displays images or videos through the display screen 194. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 110 and may be housed in the same device as the mobile communication module 150 or other functional modules.

The wireless communication module 160 can provide solutions for wireless communication applications on the terminal 100, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

In some other embodiments of this application, the terminal 100 can connect to a wireless network (e.g., a Wi-Fi network) via the wireless communication module 160, and then connect to the Internet via the Wi-Fi network, establishing communication connections with the signaling server 300 and the media server 400 respectively.

In some embodiments, antenna 1 of terminal 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling terminal 100 to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), 5G and subsequent evolution standards, BT, GNSS, WLAN, NFC, FM, and/or IR technologies, etc. The GNSS may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and/or satellite-based augmentation systems (SBAS).

Terminal 100 implements display functions through a GPU, display screen 194, and application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

Terminal 100 can perform shooting functions through ISP, camera 193, video codec, GPU, display 194 and application processor.

The ISP (Image Signal Processor) is used to process data fed back from the camera 193. For example, when taking a picture, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, and the camera's photosensitive element transmits the electrical signal to the ISP for processing, transforming it into an image visible to the naked eye. The ISP can also perform algorithmic optimization of image noise, brightness, and skin tone. The ISP can also optimize parameters such as exposure and color temperature of the shooting scene. In some embodiments, the ISP can be set in the camera 193.

Camera 193 is used to capture still images or videos. An object is projected onto a photosensitive element by generating an optical image through the lens. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then passed to an ISP for conversion into a digital image signal. The ISP outputs the digital image signal to a DSP for processing. The DSP converts the digital image signal into image signals in standard RGB, YUV, or other formats. In some embodiments, terminal 100 may include one or N cameras 193, where N is a positive integer greater than 1.

A digital signal processor (DSP) is used to process digital signals. Besides digital image signals, it can also process other digital signals. For example, when terminal 100 selects a frequency point, the DSP can perform Fourier transforms on the frequency energy.

Video codecs are used to compress or decompress digital video. Terminal 100 may support one or more video codecs. Thus, terminal 100 can play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG 2, MPEG 3, MPEG 4, etc.

Terminal 100 can implement audio functions, such as music playback and recording, through audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.

Additionally, the charging management module 140 receives charging input from the charger. The charger can be a wireless charger or a wired charger. The power management module 141 connects the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and/or the charging management module 140 to power the processor 110, internal memory 121, display screen 194, camera 193, and wireless communication module 160, etc. In some other embodiments, the power management module 141 may also be located within the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be located in the same device. The buttons 190 include a power button, volume buttons, etc. The buttons 190 can be mechanical buttons or touch buttons. The terminal 100 can receive button input and generate key signal inputs related to user settings and function control of the terminal 100. The motor 191 can generate vibration alerts. The motor 191 can be used for incoming call vibration alerts or for touch vibration feedback. Indicator 192 can be an indicator light, used to indicate charging status, power changes, or to indicate messages, missed calls, notifications, etc.

It should be noted that the structures of other terminals in Figure 1, such as terminals 200, 500, and 600, can all refer to the structure of terminal 100. It is understood that the structures of terminals 200, 500, and 600 may have more or fewer components than terminal 100 in Figure 2, or they may combine some components, split some components, or have different component arrangements. This application does not impose any special restrictions on the structures of terminals 200, 500, and 600. Furthermore, the specific forms of terminals 200, 500, and 600 may be the same as or different from terminal 100. For example, terminal 200 may be a mobile phone, and terminal 500 may also be a mobile phone. In other words, the network call transfer scheme provided in this application embodiment is applicable to scenarios where a network call on one mobile phone is transferred to another mobile phone. For another example, terminal 200 may be a mobile phone, and terminal 500 may be a PC, smart screen, tablet computer, or in-vehicle terminal, etc. In other words, the network call forwarding scheme provided in this application is applicable to scenarios where network calls on a mobile phone are forwarded to other types of devices (such as large-screen devices, in-vehicle terminals, etc.). In summary, this application does not impose any special restrictions on the specific form of each terminal.

Figure 3 shows a schematic diagram of a signaling server 300 provided in an embodiment of this application. The signaling server 300 includes at least one processor 210, at least one memory 220, and at least one communication interface 230. Optionally, the signaling server 300 may also include output devices and input devices, which are not shown in the figure.

Processor 210, memory 220, and communication interface 230 are connected via a bus. Processor 210 can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program according to this application. Processor 210 may also include multiple CPUs, and processor 210 can be a single-core processor or a multi-core processor. Here, processor can refer to one or more devices, circuits, or processing cores used to process data (e.g., computer program instructions).

The memory 220 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory 220 may exist independently and be connected to the processor 210 via a bus. The memory 220 may also be integrated with the processor 210. The memory 220 is used to store application code that executes the scheme of this application, and its execution is controlled by the processor 210.

In this embodiment of the application, the memory 220 of the signaling server 300 can be used to store the device correspondence before and after the network call transfer. For example, if the device before the transfer is terminal 200 and the device after the transfer is terminal 500, then the memory 220 can record the correspondence between terminal 200 and terminal 500.

The communication interface 230 can be used to communicate with other devices or communication networks, such as Ethernet, wireless local area networks (WLAN), etc.

In this embodiment of the application, the signaling server 300 can receive a request from the terminal 100 to call the terminal 200 through the communication interface 230, establish a signaling channel with the terminal 100 and the terminal 200, and use it to interact with and control related information, such as instructions to transfer network calls.

Output devices communicate with the processor to display information in various ways. For example, output devices can be liquid crystal displays (LCDs), light-emitting diode (LED) displays, cathode ray tube (CRT) displays, or projectors. Input devices communicate with the processor to receive user input in various ways. For example, input devices can be mice, keyboards, touchscreen devices, or sensors.

It should also be noted that the structure of the media server 400 described above can refer to the structure of the signaling server 300 shown in Figure 3. It is understood that the structure of the media server 400 may have more or fewer components than the signaling server 300 in Figure 3, or may combine some components, split some components, or have different component arrangements. This application does not impose any special restrictions on the structure of the media server 400.

The following will take terminal 100 as mobile phone 1, terminal 200 as mobile phone 2, and terminal 500 as smart screen as examples, and describe in detail the technical solution provided by the embodiments of this application with reference to the accompanying drawings.

First, mobile phone 1 calls mobile phone 2 through a VoIP application (such as MeeTime). The VoIP application is any application that includes VoIP functionality. For example, the VoIP application can be a calling application or a contacts application. That is, the calling application or contacts application integrates VoIP functionality.

For example, take the "Connect Call" feature in the calling application as an example. As shown in Figure 4 (1), this is the desktop 501 displayed on the mobile phone 1. In response to detecting that user A operates the "Phone" application icon 502, the mobile phone displays the main interface 503 of the "Phone" application as shown in Figure 4 (2). In response to detecting that user A operates the "Connect Call" icon 504 in the main interface 503 of the "Phone" application, the mobile phone displays the interface 505 of "Connect Call" (i.e., the main interface of the network calling function) as shown in Figure 5 (1). The interface 505 includes an input box 506, local information 507, and contact information 508 for those who have enabled the network calling function. User A can enter keywords in the input box 506 to search for contacts or enter a number to make a network call directly. User A can also find the contact they want to call in the contact information 508 and call that contact through the corresponding "voice" or "video" control. For example, user A operates the "video" control 509 corresponding to Jane, and mobile phone 1 sends a video call request to the signaling server via the network to request a video call with Jane. The call request includes Jane's mobile phone number. Simultaneously, mobile phone 1 displays the video call interface 510 shown in Figure 5(2). For example, the video call interface 510 may include information such as the called party's avatar, mobile phone number (not shown in the figure), and name (not shown in the figure). The video call interface 510 also includes a hang-up control to end the currently ongoing video call. Optionally, the video call interface 510 may also include controls to switch the video call to an audio call, controls to turn on the speakerphone, etc. (all not shown in the figure).

After receiving a call request from the signaling server, mobile phone 2 displays a video call interface 601 as shown in Figure 6A (1). This video call interface 601 can display the caller's avatar, mobile phone number (not shown in the figure), and name (not shown in the figure), as well as a "Reject" control, an "Answer" control, and a "Discover" control 602. The "Discover" control 602 can be used to search for devices around mobile phone 2. Of course, the name of the "Discover" control 602 can also be expressed as "Scan," "Search," or other terms; this embodiment does not limit this.

It should be noted that during the process of mobile phone 1 calling mobile phone 2, mobile phone 1 and mobile phone 2 respectively establish a signaling channel with the signaling server and a media channel with the media server. It should also be noted that, in this embodiment, even if mobile phone 2 transfers the network call to another device, or mobile phone 1 transfers the network call to another device, the transferred device and the peer device still reuse the media channel to exchange media data.

In some embodiments, in response to detecting that user B operates the "discover" control 602 in the video call interface 601 shown in FIG6A (1), mobile phone 2 can use wireless communication functions (such as Wi-Fi or Bluetooth) to search for surrounding devices and display the interface 603 shown in FIG6A (2). The interface 603 may include a search list 604, which displays a list of information about surrounding devices searched by mobile phone 2, such as a smart screen (e.g., named Vision), a smart speaker (e.g., named SoundX), and a laptop (e.g., named MateBook X). That is, user B can transfer the network call on mobile phone 2 to other devices near mobile phone 2. In this way, the user can flexibly choose the most suitable device nearby to answer the current network call. For example, the user can transfer the network call on the mobile phone to the smart screen to enjoy a larger video experience on the smart screen and free up the user's hands. In some other scenarios, after the network call is transferred to the smart screen, more family members or colleagues can be invited to participate in the network call. For another example, the user can transfer the network call on the mobile phone to the in-vehicle terminal to free up the user's hands and facilitate the user's driving.

Optionally, as a specific example, the devices displayed in search list 604 are devices near mobile phone 2. Furthermore, these devices are logged into the same account as mobile phone 2, or the account logged into by the device belongs to the same group (e.g., a family group) as the account logged into by mobile phone 2, or the device belongs to the same communication network (e.g., the same Wi-Fi network) as mobile phone 2. Optionally, as another specific example, the devices displayed in search list 604 are also devices capable of transferring VoIP calls. That is, mobile phone 2 filters out devices that support the ability to transfer VoIP calls from the search results. Among these, devices capable of transferring VoIP calls are, for example, devices with a VoIP application installed, and that VoIP application supports the function of transferring VoIP calls.

In some other embodiments, in response to detecting that user B operates the "Discover" control 602 in the video call interface 601 shown in FIG6A (1), mobile phone 2 can also access the home server to query the associated devices of mobile phone 2. The associated devices of mobile phone 2 refer to devices logged into the same account as mobile phone 2, or devices logged into an account belonging to the same family group as the account logged into mobile phone 2. Then, mobile phone 2 displays the interface 603 shown in FIG6A (2). The interface 603 may include a search list 604, which displays a list of information about the associated devices queried by mobile phone 2, such as a smart screen (e.g., named Vision), a smart speaker (e.g., named SoundX), and a laptop computer (e.g., named MateBookX). It should be noted that the associated devices of mobile phone 2 queried through the home server may not be located near mobile phone 2. In other words, the method provided in this application embodiment can also be applied to transferring the network call function on mobile phone 2 to other remote devices. In this way, the user can choose to transfer the current network call to another more suitable user in the home or work environment to answer the call. For example, when users are away from home, they can transfer internet calls from their mobile phones to a smart screen at home, where family members can answer the calls.

Optionally, as a specific example, the devices displayed in search list 604 are currently online devices. Optionally, as another specific example, the devices displayed in search list 604 are also devices capable of transferring VoIP calls. That is, mobile phone 2 filters out devices that support the ability to transfer VoIP calls from the searched related devices.

In the search list 604 of the aforementioned interface 603, each device has a corresponding "Call Transfer" control. This "Call Transfer" control can be used to switch the current network call on mobile phone 2 to the corresponding device for answering. Of course, "Call Transfer" in this document can also be expressed as "Call Migration," "Call Switching," or other terms, and this embodiment of the application does not limit this to such terms.

For example, if user B is detected operating the "transfer call" control 605 corresponding to the smart screen (i.e., Vision), mobile phone 2 sends a transfer instruction from user B to the signaling server, instructing that the network call on mobile phone 2 be transferred to the smart screen. Based on the received transfer instruction, the signaling server records the correspondence between mobile phone 2 and the smart screen in this network call. That is, mobile phone 2 and the smart screen are marked as the same participant in this network call. It should be noted that, in fact, the user of mobile phone 2 and the user of the smart screen can be the same user, or they can be different users. In other words, after the network call is transferred, user B of mobile phone 2 can continue to answer, or another user can continue to answer. Then, the signaling server broadcasts a transfer request, which carries information about the media channel where mobile phone 1 and mobile phone 2 are located. In this way, all devices joined to the media channel can receive the transfer request and know that mobile phone 2 and the smart screen correspond to the same participant. In addition, the signaling server sends a transfer request to the smart screen, and the smart screen obtains the information about the media channel where mobile phone 1 and mobile phone 2 are located.

It should be noted that the control used to trigger call transfer on mobile phone 2 can also be set on other interfaces. For example, a "call transfer" control 607 can also be set in the video call interface 606 shown in Figure 6B (1). In response to detecting that user B operates the "call transfer" control 607, mobile phone 2 displays the interface 608 shown in Figure 6B (2). The interface 608 displays a list 609 of surrounding devices searched by mobile phone 2. User B can select the target device for call transfer in the device list 609. Of course, user B can also trigger the function of mobile phone 2 to transfer network calls in other ways. For example, user B can also trigger mobile phone 2 to transfer the current network call by performing a preset operation (e.g., drawing a preset pattern) or inputting a voice command on the screen of mobile phone 2.

After receiving a transfer request from the signaling server, the smart screen outputs a prompt message to ask the user (who could be user B or another user) whether to accept the transferred network call on their device. In some examples, after receiving the transfer request from the signaling server, the smart screen can display interface 701 as shown in Figure 7A (1), for example, a prompt box 702 is displayed on the interface (e.g., video playback interface) when the smart screen receives the transfer request, prompting the user to "agree to accept the network call transfer request from Phone P40". Optionally, the smart screen can further prompt the user to click the "OK" button on the remote control if they agree, and click the "Cancel" button on the remote control if they disagree. In other examples, after receiving the transfer request from the signaling server, the smart screen can also display interface 704 as shown in Figure 7C, that is, a prompt box 705 is displayed at the bottom (or top or side) of the screen, prompting the user to "agree to accept the network call transfer request from Phone P40". Alternatively, the smart screen can play voice prompts, etc. In summary, the embodiments of this application do not limit the prompting method of the smart screen.

When the user clicks the "OK" button on the remote control or enters a voice command such as "Yes" (or "Agree"), the smart screen displays the video call interface 703 shown in Figure 7A (2). Furthermore, the user can answer or end network calls on this interface 703. It should be noted that when the user clicks the "OK" button on the remote control or enters a voice command such as "Yes" (or "Agree"), the smart screen also requests to join the media channel through the media server, thereby establishing a media channel for communication between the smart screen and mobile phone 1. At this time, the smart screen displays the video call interface 706 shown in Figure 7B. This video call interface 706 displays the video footage received from mobile phone 1 through the aforementioned media channel, as well as the video footage collected by the smart screen itself. The smart screen can also output the audio data collected by mobile phone 1 through the aforementioned media channel. The video footage and audio data collected by the smart screen will also be sent to mobile phone 1 through the media channel, thereby achieving real-time communication between the smart screen and mobile phone 1. As shown in Figure 7B, the video call interface 706 can also include controls for managing the network call, such as a "hang up" control and a "mute" control. Optionally, the video call interface 706 can also include a "return to original device" control 707, used to return the current network call to mobile phone 2. Optionally, the video call interface 706 can also include a "discover" control (not shown in the figure), used to transfer the current network call to another device. The process of returning to the original device and transferring to another device is similar to the process of migrating to the smart screen, and will not be described in detail here.

After user B confirms the transfer of the current VoIP call on the smart screen, the smart screen can notify mobile phone 2 through a signaling server, a wireless connection between the smart screen and mobile phone 2, or a home server. In some embodiments, when mobile phone 2 learns that user B has agreed to transfer the VoIP call, mobile phone 2 can turn off its screen, display the desktop, display the interface before the VoIP function was initiated, or output a prompt message to inform user B that the current VoIP call has been transferred to the smart screen. For example, mobile phone 2 displays interface 801 as shown in Figure 8. Interface 801 includes a prompt box 802 to inform user B that the current VoIP call has been transferred to the smart screen.

Optionally, after transferring a VoIP call to another device, mobile phone 2 can retain some control over the current VoIP call. For example, interface 801 also includes a "Return Call" control 803, used to transfer a VoIP call transferred from the device back to the device. Interface 801 may also include a "End Call" control 804, used to hang up the current VoIP call. Interface 801 includes a close control 805, used to close the notification box 802. In other words, after mobile phone 2 transfers a VoIP call to another device, user B can continue to use other functions of mobile phone 2.

It should be noted that after mobile phone 2 transfers the current network call to the smart screen, mobile phone 2 can request to exit the media channel through the media server. That is, mobile phone 2 will no longer receive media data (audio data and video data) collected by mobile phone 1 and the smart screen. Of course, mobile phone 2 can also choose not to exit the media channel, meaning mobile phone 2 can continue to receive media data collected by mobile phone 1 and the smart screen. In some examples, mobile phone 2 can also disconnect the signaling channel with the signaling server, meaning mobile phone 2 completely exits the current network call and no longer controls it. In other examples, the mobile phone can retain the signaling channel with the signaling server. When user B continues to perform relevant control operations on mobile phone 2, such as transferring back to the network call or ending the network call, mobile phone 2 can execute the relevant control procedures through the signaling channel with the signaling server.

The above embodiments illustrate the process by which the called party (i.e., mobile phone 2) transfers a VoIP call to another device when it receives an incoming call. In other embodiments, the calling party (i.e., mobile phone 1) can also transfer the VoIP call to another device while calling the called party (i.e., mobile phone 2). For example, as shown in Figure 9, the video call interface 901 displayed on mobile phone 1, which calls mobile phone 2, also includes a "discover" control 902, which can be used to search for devices around mobile phone 1, making it convenient for user A to transfer the VoIP call on mobile phone 1 to another device. The specific transfer process can be referred to as the process by which user B transfers the VoIP call on mobile phone 2 to a smart screen, which will not be repeated here.

The above details the process of transferring a VoIP call to another device when the called party receives an incoming call but does not answer it (i.e., the VoIP call is not yet connected). In some other embodiments, the called party or the caller can also transfer the VoIP call to another device after the called party answers the call (i.e., after the VoIP call is connected). Here, we will still use the example of the called party transferring the VoIP call to a smart screen for illustration.

For example, as shown in Figure 10(1), the video call interface 1001 displayed by mobile phone 2 after a video call is connected displays the video screen captured by mobile phone 2 and the video screen captured by mobile phone 1 through the media channel. At the same time, mobile phone 2 also plays the audio data captured by mobile phone 1 through the media channel. The video screen and audio data captured by mobile phone 2 are also sent to mobile phone 1 through the media channel, thereby realizing real-time communication between mobile phone 1 and mobile phone 2. The video call interface 1001 also includes some network call control controls, such as hang-up control and "discover" control 1002. Similar to the process of user B transferring network calls when receiving an incoming call, user B can use the "discover" control 1002 to trigger mobile phone 2 to search for surrounding devices and transfer the current network call to the device selected by the user. For example, in response to user B's operation of the "discover" control 1002, mobile phone 2 displays the interface 1003 shown in Figure 10(2), which displays a list 1004 of surrounding devices searched by mobile phone 2. Furthermore, in response to the user's operation of the "Transfer Call" control 1005 corresponding to the smart screen, mobile phone 2 sends a transfer instruction to the signaling server, instructing to transfer the network call on mobile phone 2 to the smart screen. The signaling server records the correspondence between mobile phone 2 and the smart screen in this network call based on the received transfer instruction. Then, the signaling server broadcasts a transfer request, which carries media channel information. In this way, all devices joined to the media channel can receive the transfer request and know that mobile phone 2 and the smart screen correspond to the same participant. In addition, the signaling server sends a transfer request to the smart screen, and the smart screen obtains the media channel information of mobile phone 1 and mobile phone 2. It is understandable that the control triggering mobile phone 2 to transfer the network call could also be set on other interfaces, or user B could also trigger mobile phone 2 to transfer the network call in other ways.

Additionally, after receiving an instruction from mobile phone 2 to transfer the video call, the smart screen can display interface 701 as shown in Figure 7A (1), or interface 704 as shown in Figure 7C. After receiving the user's consent to transfer the video call, the smart screen displays the video call interface 706 as shown in Figure 7B. Other details can be found in the relevant content above and will not be repeated here.

Furthermore, the process by which the caller triggers a transfer of the VoIP call is similar to that by the called party, and will not be described in detail here.

The above example illustrates the overall process of a one-to-one VoIP call between mobile phone 1 and mobile phone 2. In fact, the method provided in this application is also applicable to one-to-many VoIP calls, many-to-one VoIP calls, and scenarios where either party in a many-to-many VoIP call transfers the VoIP call from their mobile device to another device.

The following details the message exchange process between various devices during network call transfer in different scenarios.

Figure 11 shows a flowchart of a method for transferring a network call according to an embodiment of this application. This method can be applied to one-to-one network calls and includes:

S1100, Mobile phone 1 receives an instruction to call mobile phone 2.

Mobile phone 1 can call mobile phone 2 through a network calling application (such as Changlian Call). For example, when mobile phone 1 receives an instruction to call mobile phone 2, it may be because mobile phone 1 detects that a user (for example, user A) operates the "video" control 509 corresponding to Jane in the interface 505 shown in Figure 5 (1).

S1101a, Mobile phone 1 establishes a signaling channel with mobile phone 2 through the signaling server.

S1101b, Mobile phone 1 establishes a media channel with mobile phone 2 through a media server.

In steps S1101a and S1101b, mobile phone 1, according to the instructions of calling mobile phone 2, establishes a signaling channel with mobile phone 2 through a signaling server and a media channel with mobile phone 2 through a media server, based on the real-time communication protocol. It should be noted that steps S1101a and S1101b shown in Figure 11 are only used to illustrate that the process of establishing a call connection between mobile phone 1 and mobile phone 2 includes two steps: establishing a signaling channel and establishing a media channel. It does not limit steps S1101a and S1101b to two independent steps. In some examples, the execution of step S1101a includes the execution of step S1101b. That is, part of the process in step S1101a is executed first, then step S1101b is executed, and then the remaining processes of step S1101a are continued. It should be noted that during the process of establishing a signaling channel between mobile phone 1 and mobile phone 2 through the signaling server, the signaling server obtains information about the media channel, such as the media channel identifier.

S1102, Mobile Phone 2 displays the first call interface.

After receiving the call request sent by mobile phone 1 through the signaling server, mobile phone 2 displays the first call interface.

For example, mobile phone 2 can display a video call interface 601 as shown in Figure 6A (1). This video call interface 601 can display the caller's avatar, mobile phone number, and other information, as well as a "reject" control, an "answer" control, and a "discover" control 602. The "discover" control 602 can be used to search for devices around mobile phone 2.

S1103, Mobile Phone 2 receives a transfer instruction, which instructs the network call on Mobile Phone 2 to be transferred to the smart screen for answering.

In some embodiments, the user of mobile phone 2 (e.g., user B) can instruct the caller to switch the call on mobile phone 2 to the smart screen when receiving an incoming call but not yet connected to the network call. In other words, when user B receives an incoming call on mobile phone 2, he can forward the call to another device and connect to the network call with user A on that other device.

For example, in response to detecting that user B operates the "discover" control 602 in the video call interface 601 shown in Figure 6A (1), mobile phone 2 can use wireless communication functions (such as Wi-Fi or Bluetooth) to search for surrounding devices, or access a home server to query the associated devices of mobile phone 2, displaying interface 603 as shown in Figure 6A (2). This interface 603 may include a search list 604, which displays a list of information about transferable devices, such as a smart screen (named, for example, Vision), a smart speaker (named, for example, SoundX), and a laptop (named, for example, MateBook X). If user B operates the "transfer call" control 605 corresponding to the smart screen (i.e., Vision), it is considered that mobile phone 2 has received a transfer instruction from user B and instructs to transfer the network call on mobile phone 2 to the smart screen. In some examples of this embodiment, the smart screen may be located near mobile phone 2, for example, both mobile phone 2 and smart screen are located at home or in the office. That is, mobile phone 2 transfers the network call to another nearby device to be answered. In other examples of this embodiment, in the method where mobile phone 2 queries its associated devices by accessing a home server, the smart screen may not be located near mobile phone 2. That is, mobile phone 2 transfers the network call to another remote device for another user to answer the current network call.

In other embodiments, user B can also instruct the call to be switched from mobile phone 2 to the smart screen after the call is connected. That is, user B can connect to a network call on mobile phone 2 and, while in a network call with user A, transfer the call to another device to continue the network call with user A on that other device.

For example, when user B connects to a network call, mobile phone 2 displays a video call interface 1001 as shown in Figure 10(1). This video call interface 1001 displays the screen of user A on mobile phone 1 and the screen of user B on mobile phone 2. The video call interface 1001 also displays a "switch camera" control, a "hang up" control, and a "discover" control 1002. When user B operates the "discover" control 1002, mobile phone 2 uses wireless communication functions (such as Wi-Fi or Bluetooth) to search for surrounding devices, displaying an interface 1003 as shown in Figure 10(2). This interface 1003 may include a search list 1004, which displays a list of information about surrounding devices found by mobile phone 2, such as a smart screen (named, for example, Vision), a smart speaker (named, for example, SoundX), and a laptop (named, for example, MateBook X). Each found device has a corresponding "transfer call" control. If user B operates the "transfer call" control 1005 corresponding to the smart screen (i.e., Vision), it is considered that mobile phone 2 has received a transfer instruction from user B and instructs to transfer the network call on mobile phone 2 to the smart screen. In some examples of this embodiment, the smart screen may be located near mobile phone 2, for example, both mobile phone 2 and the smart screen may be located at home or in the office. That is, mobile phone 2 transfers the network call to another nearby device for answering. In other examples of this embodiment, in the method where mobile phone 2 queries the associated devices of mobile phone 2 by accessing the home server, the smart screen may not be located near mobile phone 2. That is, mobile phone 2 transfers the network call to another remote device for another user to answer the current network call.

It should be noted that the following description uses the example of the called party (i.e., mobile phone 2) transferring a VoIP call to another device (smart screen) to illustrate the transfer process. In some other embodiments, after user B answers the VoIP call, user A can also operate on mobile phone 1 to instruct mobile phone 1 to transfer the current VoIP call to another device of user A. The transfer process is similar to the process of user B transferring the VoIP call on mobile phone 2 to the smart screen, and will not be described separately.

S1104, Mobile Phone 2 sends a transfer notification to the signaling server, and the transfer notification carries the identifier of the smart screen.

After receiving the transfer instruction from user B, mobile phone 2 sends a transfer notification to the signaling server, notifying that the network call on mobile phone 2 will be transferred to the smart screen. The smart screen's identifier can be, for example, the smart screen's MAC address, or the smart screen's ID (also known as the International Mobile Equipment Identity (IMEI) or serial number, etc.).

S1105, the signaling server records the correspondence between mobile phone 2 and smart screen in network calls.

Specifically, the signaling server establishes a correspondence between the identifier of the smart screen and the identifier of mobile phone 2. In other words, in this network call, the smart screen and mobile phone 2 correspond to the same participant. It should be noted that, in fact, the user of mobile phone 2 and the user of the smart screen can be the same user, or they can be different users. In other words, after the network call is transferred, it can be answered by user B of mobile phone 2, or it can be answered by another user. The identifier of mobile phone 2 includes the phone number, MAC address, ID, and logged-in account, etc.

S1106. The signaling server broadcasts a transfer request to notify other devices in the media channel that mobile phone 2 will transfer the network call to the smart screen. Furthermore, the signaling server sends a transfer request to the smart screen.

S1107, Smart Screen Display Transfer Interface.

For example, the smart screen displays interface 701 as shown in Figure 7A (1), interface 701 includes prompt information 702, which asks whether the current user of the smart screen agrees to accept the transfer request of the network call from mobile phone 2. Alternatively, the smart screen displays interface 704 as shown in Figure 7C, interface 704 includes prompt information 705. Alternatively, the smart screen can also ask the current user whether they agree to accept the transfer request of the network call from mobile phone 2 by playing voice prompt information.

It should be noted that if mobile phone 2 forwards a network call to the smart screen for the first time, the smart screen can display the aforementioned forwarding interface to ask the user whether they agree to accept the network call forwarded by mobile phone 2. After the user agrees to accept the network call forwarded by mobile phone 2 this time, when mobile phone 2 forwards a network call to the smart screen again, the smart screen can assume that the user has agreed to the forwarding, and the smart screen can directly display the relevant network call interface (the network call's call interface or the network call interface). That is, the smart screen directly executes step S1112. In some other embodiments, the user of the smart screen can also pre-authorize receiving network calls forwarded by mobile phone 2. For example, the user can pre-enable receiving network calls forwarded by mobile phone 2 in the network calling application or system settings. In this way, when the smart screen receives a network call forwarded by mobile phone 2, it directly executes step S1112.

It should also be noted that if mobile phone 2 transfers a VoIP call after receiving an incoming call but before the call is connected, the smart screen can ring to notify the user of the incoming call. Furthermore, the smart screen also sends a ringing notification to the signaling server, mobile phone 1, and mobile phone 2, i.e., executes step S1108. If mobile phone 2 transfers a VoIP call after the user has connected it, the smart screen does not need to ring, i.e., step S1108 is not required.

S1108, the smart screen sends a ringing notification to mobile phone 1 and mobile phone 2 via the signaling server. Correspondingly, mobile phone 1 and mobile phone 2 receive the ringing notification from the smart screen.

This step is optional. If mobile phone 2 transfers the network call after the user has connected to the network call, the smart screen does not need to ring, and step S1108 does not need to be executed.

S1109, The smart screen receives the instruction to agree to the transfer.

For example, a user of the smart screen, such as user B or another user, can operate the smart screen's remote control, for instance, by clicking the "OK" button to instruct the smart screen to accept the call transfer request from mobile phone 2. Alternatively, the user can also enter a voice command such as "Agree" (or "Yes," "Agree to transfer," etc.) to instruct the smart screen to accept the call transfer request from mobile phone 2. Of course, the user can also refuse the call transfer request from mobile phone 2. If the user refuses, the call transfer process ends. Mobile phone 2 continues to display the call interface or conversation interface, meaning that mobile phone 2 continues to answer the call.

S1110, the smart screen sends a message to the signaling server agreeing to the transfer.

S1111: The signaling server broadcasts a message indicating that the smart screen agrees to the transfer. Correspondingly, mobile phones 1 and 2 receive this message.

S1112. The smart screen requests to join the media channel from the media server based on the media channel identifier.

As shown in step S1104, the smart screen has obtained the identifiers of the media channels where mobile phones 1 and 2 are located. Based on these identifiers, the smart screen can request to join the media channel from the media server. In this way, the smart screen and mobile phone 1 can transmit media data through the media channel. This media data includes video and audio data captured by mobile phone 1 and video and audio data captured by the smart screen. In other words, it enables video calls between the smart screen and mobile phone 1.

S1113: The media server broadcasts a notification that the smart screen has been added to the media channel. Correspondingly, mobile phones 1 and 2 receive the notification that the smart screen has been added to the media channel.

S1114, Mobile Phone 2 requests to exit the media channel from the media server.

For example, after receiving permission from the smart screen to transfer the network call, i.e., after executing step S1111, mobile phone 2 can request to exit the media channel. Alternatively, mobile phone 2 can also request to exit the media channel after receiving notification that the smart screen has joined the media channel, i.e., after executing step S1113. It is understood that if mobile phone 2 exits the media channel, it will be unable to receive media data exchanged between mobile phone 1 and the smart screen. In some other examples, mobile phone 2 may not exit the media channel, i.e., it may not execute step S1114. In this case, mobile phone 2 can still receive media data exchanged between mobile phone 1 and the smart screen.

In some embodiments, mobile phone 2 can also disconnect the signaling channel with the signaling server, meaning mobile phone 2 completely exits the current network call and no longer controls it. In other examples, the mobile phone can retain the signaling channel with the signaling server. When user B continues to perform relevant control operations on mobile phone 2, such as switching back to the network call or ending the network call, mobile phone 2 can forward relevant control signaling through the signaling channel with the signaling server to execute the relevant control procedures.

S1115, The media server sends a notification to mobile phone 1 that mobile phone 2 has exited the media channel. Correspondingly, mobile phone 1 receives the notification that mobile phone 2 has exited the media channel.

If mobile phone 2 does not execute step S1114, then the media server does not need to execute step S1115 either.

S1116, The smart screen displays a second call interface and receives call answering instructions.

For example, after the smart screen receives the user's instruction to answer the call, the smart screen can automatically launch the network call application and display the relevant network call interface.

For example, if mobile phone 2 receives a video call but does not answer the video call, and instructs the user to transfer the video call, the smart screen can display the video call interface 703 shown in Figure 7A (2). The video call interface 703 can be used to instruct the user (specifically user B or other users) to answer the video call on the smart screen or refuse to answer the video call.

For example, if mobile phone 2 instructs to transfer the video call when it is connected, the smart screen can display the video call interface 706 as shown in Figure 7B.

S1117, the smart screen and mobile phone 1 make network calls through the media channel of the media server.

The smart screen and mobile phone 1 interact with each other through a media server to collect media data (such as video footage, audio data, etc.), thereby enabling real-time communication between the smart screen and mobile phone 1.

As can be seen from the above, in the technical solution provided in this application, since the transferred device (i.e., the smart screen) can directly join the media channel created by mobile phone 1 for this network call with the media server, real-time communication between the smart screen and mobile phone 1 can be achieved. Compared to mobile phone 1 needing to exit the current media channel and apply for a new media channel, the smart screen joining the new media channel to achieve the transfer process of real-time communication between the smart screen and mobile phone 1 simplifies the signaling interaction process between the device and the server during the entire transfer process, and improves the transfer efficiency of network calls.

Furthermore, in the technical solution provided in this application embodiment, a user can transfer the current network call when they first receive an incoming call but before the network call is connected. The user can also transfer the current network call after it has been connected. The called party can transfer the network call to another device, and the calling party can also transfer the network call to another device. Therefore, the technical solution provided in this application embodiment can enable users to flexibly transfer network calls, meeting their network call needs in different scenarios.

Furthermore, in the technical solutions provided in this application, users can choose to transfer network calls to other nearby devices. This allows users to flexibly choose the most suitable device to answer the current network call. For example, users can transfer network calls from their mobile phones to a smart screen to enjoy a larger video experience and free their hands. In other scenarios, after transferring a network call to a smart screen, more family members or colleagues can be invited to participate in the call. For another example, users can also transfer network calls from the smart screen to their mobile phones to avoid privacy leaks. Users can also choose to transfer the current network call to a remote device. This allows users to choose another more suitable user in their home or work environment to answer the call. For example, when a user is out, they can transfer network calls from their mobile phone to a smart screen at home, where a family member can answer the call.

In some other embodiments of this application, after mobile phone 2 transfers a network call to the smart screen, mobile phone 2 or the smart screen can also transfer the network call back to mobile phone 2 or to other devices according to the user's instructions. The process of transferring a network call from the smart screen to other devices can be referred to the method flow shown in Figure 11 above, and will not be described again in this application.

Figure 12 shows a flowchart of a method for migrating back a network call according to an embodiment of this application. The method includes the above-mentioned steps S1100 to S1117, and steps S1201 to S1207, as detailed below:

S1201, Mobile Phone 2, or Smart Screen receives the instruction to migrate back to the network call and sends the migration instruction to the signaling server.

In some embodiments, the user can operate on the smart screen to instruct the current network call to be migrated back to the original device. For example, the smart screen displays a video call interface 706 as shown in Figure 7B, which includes a "migrate back to original device" control 707. When the smart screen detects that the user operates the "migrate back to original device" control 707, the smart screen sends a migration instruction to the signaling server. Alternatively, after receiving a voice command from the user to migrate the network call back to the original device, the smart screen sends a migration instruction to the signaling server.

In other embodiments, while mobile phone 2 retains control over the current network call, the user can also instruct on mobile phone 2 to transfer the current network call back to the original device. For example, mobile phone 2 displays interface 801 as shown in Figure 8. When mobile phone 2 detects that the user operates the "transfer call back" control 803, mobile phone 2 sends a transfer instruction to the signaling server. Alternatively, after receiving a voice command from the user to transfer the network call back, mobile phone 2 sends a transfer instruction to the signaling server.

Understandably, "call transfer" can also be considered a special case of "call forwarding," where a VoIP call is transferred to the original device.

S1202, The signaling server deletes the correspondence between mobile phone 2 and smart screen in this network call.

S1203, The signaling server sends a migration notification to notify that the current network call will be migrated back to mobile phone 2.

After receiving the migration notification, S1204 and mobile phone 2 apply to the media server to join the media channel.

S1205, The media server broadcasts a notification that mobile phone 2 has joined the media channel.

S1206, Smart Screen exits media channel.

For example, the smart screen can exit the media channel upon receiving a migration notification, i.e., after step S1203. Alternatively, the smart screen can also exit the media channel after receiving a notification that mobile phone 2 has joined the media channel, i.e., after step A1205.

S1207, Mobile Phone 2 and Mobile Phone 1 conduct network calls through the media channel of the media server.

Therefore, in the solution provided in this application embodiment, when the smart screen migrates the network call back to mobile phone 2, mobile phone 2 still reuses the original media channel, thereby restoring the real-time communication between mobile phone 2 and mobile phone 1, simplifying the signaling interaction process between the device and the server during the migration process, and improving the migration efficiency of network calls.

The transfer or migration process described in Figures 11 and 12 above is illustrated using a one-to-one network call as an example. The technical solution provided in this application embodiment can be applied to multi-party network calls, including one-to-many network calls, many-to-one network calls, and many-to-many network calls.

For example, the following example uses terminal 100 as mobile phone 1, terminal 200 as mobile phone 2, terminal 500 as a smart screen, and terminal 600 as mobile phone 3, and mobile phone 1, mobile phone 2, and mobile phone 3 to make a multi-party network call, to illustrate the process of transfer or migration.

Figure 13 shows a flowchart of another method for transferring network calls provided in this application embodiment. The method includes steps S1300 to S1317. Steps S1300 to S1317 correspond to steps S1100 to S1117 in Figure 11. It should be noted that the difference from the flowchart in Figure 11 is that in the steps of Figure 13, when mobile phone 1 establishes a signaling channel with the signaling server, mobile phone 3 also establishes a signaling channel with the signaling server. When mobile phone 1 establishes a media channel with the media server, mobile phone 3 also establishes a media channel with the media server. Furthermore, mobile phone 3 also joins the media channel. Additionally, when the signaling server or media server notifies mobile phone 1 of relevant information, it also notifies mobile phone 3. These differences are indicated by filled black triangles in Figure 13. For other details of steps S1300 to S1317, please refer to the description of steps S1100 to S1117 in Figure 11; they will not be repeated here.

Figure 14 shows a flowchart of another method for migrating back a network call according to an embodiment of this application. This method includes steps S1401 to S1407. Steps S1401 to S1407 correspond to steps S1201 to S1207 in Figure 12. It should be noted that, unlike the flowchart in Figure 12, in the steps of Figure 14, when the signaling server or media server notifies mobile phone 1 of relevant information, it also notifies mobile phone 3. This difference is indicated by filled black triangles in Figure 14. For other details of steps S1401 to S1407, please refer to the description of steps S1201 to S1207 in Figure 12; they will not be repeated here.

As can be seen from the above, in the technical solution provided by the embodiments of this application, the transferred device directly reuses the original media channel. The original device does not need to exit the current media channel or join a new media channel, which greatly simplifies the signaling interaction process between the device and the server during the entire transfer process and improves the transfer efficiency of network calls. It is easy to understand that when there are more participants in a network call, the simplification effect of the technical solution provided by the embodiments of this application is more obvious and the degree of improvement in transfer efficiency is higher compared to the solution where each participant in the network call needs to exit the current media channel and join a new media channel.

This application also provides a chip system, as shown in FIG15, which includes at least one processor 1501 and at least one interface circuit 1502. The processor 1501 and the interface circuit 1502 are interconnected via lines. For example, the interface circuit 1502 can be used to receive signals from other devices (e.g., memory). As another example, the interface circuit 1502 can be used to send signals to other devices (e.g., processor). Exemplarily, the interface circuit 1502 can read instructions stored in memory and send those instructions to the processor 1501. When the instructions are executed by the processor 1501, a terminal or server can perform the steps executed by terminal 100, terminal 200, terminal 500, signaling server 300, or media server 400 in the above embodiments. Of course, the chip system may also include other discrete devices, which are not specifically limited in this application.

This application also provides an apparatus included in a terminal or server, which has the function of implementing the terminal or server behavior in any of the methods described above. This function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes at least one module or unit corresponding to the above function. For example, a receiving module or unit, a transmitting module or unit, and a processing module or unit. Optionally, the apparatus may further include a display unit or audio unit, an input unit, etc.

This application also provides a computer storage medium including computer instructions that, when executed on a terminal or server, cause the terminal or server to perform any of the methods described in the above embodiments.

This application also provides a computer program product that, when run on a computer, causes the computer to perform any of the methods described in the above embodiments.

It is understood that the aforementioned terminals and servers, in order to achieve the above functions, include corresponding hardware structures and/or software modules for executing each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the embodiments of this invention.

This application embodiment can divide the terminal and server into functional modules according to the above method example. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

Through the above description of the embodiments, those skilled in the art will clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, device, and unit described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

In the embodiments of this application, the functional units can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as flash memory, portable hard disk, read-only memory, random access memory, magnetic disk, or optical disk.

The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims (15)

1. A network call transfer system, characterized in that it includes a first terminal, a second terminal, a third terminal, a first server, and a second server; the first terminal and the second terminal establish a signaling channel through the first server; the first terminal and the second terminal establish a media channel through the second server; The second terminal is used to detect user operations on controls corresponding to the third terminal displayed on the second terminal; The second terminal is also configured to, in response to the operation, send a first message to the first server through the signaling channel, the first message being used to request that the network call of the second terminal be transferred to the third terminal; The first server is configured to send a second message to the third terminal based on the first message, the second message being used to request the transfer of the network call of the second terminal to the third terminal, and the second message containing the identifier of the media channel; The third terminal is configured to join the media channel through the second server according to the identifier of the media channel contained in the second message; the second terminal maintains the media channel with the second server; The third terminal is used to interact with the first terminal via the media channel to exchange video data and/or audio data. 2. The system according to claim 1, characterized in that, When the second terminal receives a call request from the first terminal, and has not yet established a network call with the first terminal, the second terminal detects the operation; or, When the second terminal receives a call request from the first terminal and has already established a network call with the first terminal, the second terminal detects the operation; or, After the second terminal sends a call request to the first terminal, and the first terminal does not answer the network call with the second terminal, the second terminal detects the operation; or, After the second terminal sends a call request to the first terminal, and the first terminal has already connected to the network call with the second terminal, the second terminal detects the operation. 3. The system according to claim 1 or 2, characterized in that, The third terminal is also configured to output a first prompt after receiving the second message, for asking the user whether they agree to accept the network call transferred by the second terminal; The third terminal joins the media channel through the second server according to the identifier of the media channel contained in the second message, including: In response to the third terminal receiving a second instruction, the third terminal joins the media channel through the second server according to the identifier of the media channel, wherein the second instruction is used to indicate that the user agrees to accept the network call transferred by the second terminal. 4. The system according to any one of claims 1-3, characterized in that, The third terminal is further configured to receive a third instruction from the user, the third instruction being configured to instruct the network call on the third terminal to be transferred to the second terminal, and in response to receiving the third instruction, to send a fourth message to the first server, the fourth message being configured to request the network call on the third terminal to be transferred to the second terminal; The first server is further configured to send a fifth message to the second terminal, the fifth message being used to request that the network call on the third terminal be transferred to the second terminal; The second terminal is further configured to join the media channel via the second server according to the fifth message; and to interact with the first terminal via the media channel to exchange video data and/or audio data. 5. The system according to any one of claims 1-3, characterized in that, The second terminal is also configured to receive a fourth instruction from the user, the fourth instruction being configured to transfer the network call on the third terminal to the second terminal; In response to receiving the fourth instruction, the second terminal sends a sixth message to the first server, the sixth message being used to request that the network call on the third terminal be transferred to the second terminal; The first server is further configured to send a seventh message to the second terminal, the seventh message being used to instruct the transfer of the network call on the third terminal to the second terminal; The second terminal is further configured to join the media channel via the second server according to the seventh message; and to interact with the first terminal via the media channel to exchange video data and/or audio data. 6. The system according to any one of claims 1-5, wherein the second terminal and the third terminal log in to the same account; or, the second terminal and the third terminal log in to different accounts belonging to the same group; or, the second terminal and the three terminals are located in the same communication network. 7. A method for transferring a network call, characterized in that it is applied to a third terminal, wherein during the process of transferring a network call between the second terminal and the first terminal to the third terminal from the second terminal, the second terminal and the first terminal establish a signaling channel through a first server, and the second terminal and the first terminal establish a media channel through a second server, the method comprising: The third terminal receives a first message sent by the first server, the first message being used to request that the network call of the second terminal be transferred to the third terminal; and the first message contains the identifier of the media channel; The third terminal joins the media channel through the second server according to the media channel identifier contained in the first message; the second terminal retains the media channel with the second server; The third terminal interacts with the first terminal via the media channel to exchange video and/or audio data. 8. The method according to claim 7, characterized in that, after the third terminal receives the first message, the method further includes: The third terminal outputs a first prompt, which asks the user whether they agree to accept the network call transferred by the second terminal. The third terminal joins the media channel through the second server according to the identifier of the media channel contained in the first message, including: In response to receiving a second instruction, the third terminal joins the media channel via the second server according to the identifier of the media channel contained in the first message, wherein the second instruction is used to indicate that the user agrees to accept the network call transferred by the second terminal. 9. The method according to claim 7 or 8, characterized in that the method further comprises: The third terminal receives a third instruction from the user, the third instruction being used to instruct the network call on the third terminal to be transferred to the second terminal; In response to receiving the third instruction, the third terminal sends a second message to the first server, the second message being used to request that the network call on the third terminal be transferred to the second terminal. 10. The method according to any one of claims 7-9, wherein the second terminal and the third terminal log in to the same account; or, the second terminal and the third terminal log in to different accounts belonging to the same group; or, the second terminal and the three terminals are located in the same communication network. 11. A method for transferring network calls, characterized in that it is applied to a second terminal, wherein the second terminal and a first terminal establish a signaling channel through a first server, and the second terminal and the first terminal establish a media channel through a second server, the method comprising: The second terminal detects the user's operation on the control corresponding to the third terminal displayed on the second terminal; In response to the operation, the second terminal sends a first message to the first server through the signaling channel. The first message is used to request that the network call of the second terminal be transferred to the third terminal. After receiving the first message that the third terminal has joined the media channel, the second terminal retains the media channel with the second server. 12. The method according to claim 11, characterized in that, When the second terminal receives a call request from the first terminal, and has not yet established a network call with the first terminal, the second terminal detects the operation; or, When the second terminal receives a call request from the first terminal and has already established a network call with the first terminal, the second terminal detects the operation; or, After the second terminal sends a call request to the first terminal, and the first terminal does not answer the network call with the second terminal, the second terminal detects the operation; or, After the second terminal sends a call request to the first terminal, and the first terminal has already connected to the network call with the second terminal, the second terminal detects the operation. 13. The method according to claim 11 or 12, characterized in that the method further comprises: The second terminal exits the media channel through the second server; The second terminal receives a second message, which requests the network call on the third terminal to be transferred to the second terminal; The second terminal joins the media channel through the second server according to the second message, and the second terminal interacts with the first terminal through the media channel to exchange video data and/or audio data. 14. A terminal, characterized in that it comprises: a processor, a memory, and a touch screen, wherein the memory and the touch screen are coupled to the processor, the memory is used to store computer program code, the computer program code including computer instructions, wherein when the processor reads the computer instructions from the memory, the terminal causes the terminal to execute the network call transfer method as described in any one of claims 7-10, or the network call transfer method as described in any one of claims 11-13. 15. A computer-readable storage medium, characterized in that it includes computer instructions, which, when executed on a terminal, cause the terminal to perform the network call transfer method as described in any one of claims 7-10, or the network call transfer method as described in any one of claims 11-13.