Network call method and device, computer equipment and computer readable storage medium
By establishing a second call link through a bypass device during audio and video calls, the problem of interrupting the existing call when the user answers a new call is solved, enabling information reception in multiple calls and avoiding missing important calls.
Patent Information
- Application Number
- CN202411004816.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-24
- Publication Date
- 2026-01-27
AI Technical Summary
Existing audio and video calling methods require interrupting the current call to answer a new incoming call, which may cause users to miss important information.
By receiving a call request from a third device during a network call between the first and second devices, determining that the bypass device has logged into the same account, generating a call transfer instruction, and establishing a second call link, the user can answer new calls without interrupting the current call.
Users can receive and participate in multiple calls through a bypass device while maintaining their existing call, thus avoiding missing important calls.
Smart Images

Figure CN121418397A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communication technology, and in particular to a network calling method, apparatus, computer equipment, storage medium, and computer program product. Background Technology
[0002] With the development of the internet, audio and video calls have become common communication methods in people's lives. By making audio and video calls, users can communicate efficiently, greatly improving communication efficiency. However, because audio and video calls are so common, users often encounter situations where they are on one audio or video call when another one comes in. The traditional approach is usually to hang up the current call before answering the new call request, or to reject the newly received audio or video call.
[0003] However, with the current calling system, if a new call is received, the current call must be interrupted in order to answer it, which may prevent users from receiving important information in a timely manner. Summary of the Invention
[0004] Therefore, it is necessary to provide a network calling method, apparatus, computer equipment, computer-readable storage medium, and computer program product capable of connecting multiple calls, in order to address the aforementioned technical problems.
[0005] On one hand, this application provides a method for making internet calls. The method includes:
[0006] During a network call between the first device and the second device based on the first call link, a call request is received from the third device. The first device is logged into the first account, the second device is logged into the second account, and the third device is logged into the third account.
[0007] In response to a call transfer operation triggered by the call request, a bypass device is identified to establish a call with the third device, and the bypass device is logged into the first account;
[0008] A call transfer instruction for the bypass device is generated based on the call request.
[0009] The call transfer instruction is sent to the bypass device, and the call transfer instruction instructs the establishment of a second call link. The second call link is used for the bypass device that has logged into the first account and the third device that has logged into the third account to conduct network calls.
[0010] On the other hand, this application also provides a VoIP device. The device includes:
[0011] The request receiving module is used to receive a call request initiated by a third device during a network call between a first device and a second device based on a first call link, wherein the first device has logged into a first account, the second device has logged into a second account, and the third device has logged into a third account.
[0012] The device determination module is used to determine, in response to a call transfer operation triggered by the call request, a bypass device to establish a call with the third device, wherein the bypass device has logged into the first account;
[0013] The generation module is used to generate a call transfer instruction for the bypass device based on the call request;
[0014] The instruction sending module is used to send the call transfer instruction to the bypass device. The call transfer instruction instructs the establishment of a second call link. The second call link is used for the bypass device that has logged into the first account and the third device that has logged into the third account to conduct network calls.
[0015] On the other hand, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:
[0016] During a network call between the first device and the second device based on the first call link, a call request is received from the third device. The first device is logged into the first account, the second device is logged into the second account, and the third device is logged into the third account.
[0017] In response to a call transfer operation triggered by the call request, a bypass device is identified to establish a call with the third device, and the bypass device is logged into the first account;
[0018] A call transfer instruction for the bypass device is generated based on the call request.
[0019] The call transfer instruction is sent to the bypass device, and the call transfer instruction instructs the establishment of a second call link. The second call link is used for the bypass device that has logged into the first account and the third device that has logged into the third account to conduct network calls.
[0020] On the other hand, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps:
[0021] During a network call between the first device and the second device based on the first call link, a call request is received from the third device. The first device is logged into the first account, the second device is logged into the second account, and the third device is logged into the third account.
[0022] In response to a call transfer operation triggered by the call request, a bypass device is identified to establish a call with the third device, and the bypass device is logged into the first account;
[0023] A call transfer instruction for the bypass device is generated based on the call request.
[0024] The call transfer instruction is sent to the bypass device, and the call transfer instruction instructs the establishment of a second call link. The second call link is used for the bypass device that has logged into the first account and the third device that has logged into the third account to conduct network calls.
[0025] On the other hand, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, performs the following steps:
[0026] During a network call between the first device and the second device based on the first call link, a call request is received from the third device. The first device is logged into the first account, the second device is logged into the second account, and the third device is logged into the third account.
[0027] In response to a call transfer operation triggered by the call request, a bypass device is identified to establish a call with the third device, and the bypass device is logged into the first account;
[0028] A call transfer instruction for the bypass device is generated based on the call request.
[0029] The call transfer instruction is sent to the bypass device, and the call transfer instruction instructs the establishment of a second call link. The second call link is used for the bypass device that has logged into the first account and the third device that has logged into the third account to conduct network calls.
[0030] The aforementioned network calling method, apparatus, computer equipment, storage medium, and computer program product, during a network call between a first device and a second device based on a first call link, receives a call request initiated by a third device. The first device is logged into a first account, the second device is logged into a second account, and the third device is logged into a third account. In response to a call transfer operation triggered by the call request, a bypass device is identified to establish a call with the third device. This bypass device is logged into the first account. This allows a user, upon receiving a new incoming call request during a network call, to choose to transfer the new call request to a device logged into the same account as the first device. A call transfer instruction is generated for the bypass device based on the call request and sent to the bypass device, instructing it to accept the call request from the third device. The call transfer instruction instructs the establishment of a second call link. The second call link is used for network calls between a bypass device logged into the first account and a third device logged into the third account. This allows users to receive call transfer requests from the first device while making network calls using the first device based on the first call link, and to make new network calls based on the second call link using a bypass device logged into the same account. This allows users to participate in multiple calls simultaneously and avoid missing important calls.
[0031] On the other hand, this application provides a method for making network calls. The method includes:
[0032] During a network call between the first device and the second device based on the first call link, a call request initiated by the third device is forwarded to the first device. The first device is logged into a first account, the second device is logged into a second account, and the third device is logged into a third account.
[0033] The system receives a device identifier and a call transfer instruction from the first device in response to the call request. The device identifier is used to indicate a bypass device that is to establish a call with the third device. The bypass device is logged into the first account.
[0034] A second call link is established based on the call transfer instruction;
[0035] The link identifier of the second call link is sent to the third device and the bypass device respectively, so that the third device and the bypass device can access the second call link and conduct network calls based on the second call link.
[0036] On the other hand, this application also provides a VoIP device. The device includes:
[0037] The request forwarding module is used to forward a call request initiated by a third device to the first device during a network call between the first device and the second device based on a first call link. The first device has logged into a first account, the second device has logged into a second account, and the third device has logged into a third account.
[0038] The instruction receiving module is used to receive the device identifier and call transfer instruction fed back by the first device in response to the call request. The device identifier is used to indicate the bypass device to establish a call with the third device. The bypass device has been logged into the first account.
[0039] Establishment module, used to establish a second call link based on the call transfer instruction;
[0040] The identifier sending module is used to send the link identifier of the second call link to the third device and the bypass device respectively, so that the third device and the bypass device can access the second call link and conduct network calls based on the second call link.
[0041] On the other hand, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:
[0042] During a network call between the first device and the second device based on the first call link, a call request initiated by the third device is forwarded to the first device. The first device is logged into a first account, the second device is logged into a second account, and the third device is logged into a third account.
[0043] The system receives a device identifier and a call transfer instruction from the first device in response to the call request. The device identifier is used to indicate a bypass device that is to establish a call with the third device. The bypass device is logged into the first account.
[0044] A second call link is established based on the call transfer instruction;
[0045] The link identifier of the second call link is sent to the third device and the bypass device respectively, so that the third device and the bypass device can access the second call link and conduct network calls based on the second call link.
[0046] On the other hand, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps:
[0047] During a network call between the first device and the second device based on the first call link, a call request initiated by the third device is forwarded to the first device. The first device is logged into a first account, the second device is logged into a second account, and the third device is logged into a third account.
[0048] The system receives a device identifier and a call transfer instruction from the first device in response to the call request. The device identifier is used to indicate a bypass device that is to establish a call with the third device. The bypass device is logged into the first account.
[0049] A second call link is established based on the call transfer instruction;
[0050] The link identifier of the second call link is sent to the third device and the bypass device respectively, so that the third device and the bypass device can access the second call link and conduct network calls based on the second call link.
[0051] On the other hand, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, performs the following steps:
[0052] During a network call between the first device and the second device based on the first call link, a call request initiated by the third device is forwarded to the first device. The first device is logged into a first account, the second device is logged into a second account, and the third device is logged into a third account.
[0053] The system receives a device identifier and a call transfer instruction from the first device in response to the call request. The device identifier is used to indicate a bypass device that is to establish a call with the third device. The bypass device is logged into the first account.
[0054] A second call link is established based on the call transfer instruction;
[0055] The link identifier of the second call link is sent to the third device and the bypass device respectively, so that the third device and the bypass device can access the second call link and conduct network calls based on the second call link.
[0056] The aforementioned network calling method, apparatus, computer equipment, storage medium, and computer program product, during a network call between a first device and a second device based on a first call link, allows the server to forward a call request initiated by a third device to the first device. The first device is logged into a first account, the second device is logged into a second account, and the third device is logged into a third account. This enables the first device to receive call requests from the third device during a network call with the second device based on the first call link. The system also receives a device identifier and call transfer instruction from the first device in response to the call request. The device identifier indicates the bypass device to which the call is to be established with the third device, and the bypass device is logged into the first account. This allows the user, upon receiving a new call request during a network call, to choose to transfer the new call request to a device that is logged into the same account as the first device. A second call link is established based on the call transfer command. The link identifier of the second call link is sent to the third device and the bypass device respectively, so that the third device and the bypass device can access the second call link and conduct network calls based on the second call link. This allows users to receive incoming call requests transferred by the first device while using the first device to conduct network calls based on the first call link, and to conduct new network calls based on the second call link using the bypass device that is logged into the same account. This allows users to participate in multiple calls at the same time and avoid missing important calls. Attached Figure Description
[0057] Figure 1 This is a diagram illustrating the application environment of a network call method in one embodiment;
[0058] Figure 2 This is a flowchart illustrating a network call method in one embodiment;
[0059] Figure 3 This is a schematic diagram of the interface of a candidate device in one embodiment;
[0060] Figure 4 This is a diagram illustrating the application environment of the network call method in another embodiment;
[0061] Figure 5 This is a flowchart illustrating a network call method in another embodiment;
[0062] Figure 6 This is a schematic diagram of the architecture of a traditional VoIP call.
[0063] Figure 7 This is a schematic diagram of the architecture of an improved network calling method in one embodiment;
[0064] Figure 8 This is a schematic diagram of the bypass service structure in one embodiment;
[0065] Figure 9This is an interactive schematic diagram of incoming call bypass service in one embodiment;
[0066] Figure 10 This is an interactive diagram of a bypass call service in one embodiment;
[0067] Figure 11 This is a schematic diagram of the structure of a server-side device management service in one embodiment.
[0068] Figure 12 This is a schematic diagram illustrating the recording of a user's online device call status in one embodiment;
[0069] Figure 13 This is a structural block diagram of a VoIP device in one embodiment;
[0070] Figure 14 This is a structural block diagram of a VoIP device in another embodiment;
[0071] Figure 15 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation
[0072] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.
[0073] The network call method provided in this application embodiment can be applied to, for example... Figure 1 In the application environment shown, a first device 102, logged into a first account, communicates with a second device 104, logged into a second account, via a network. During a network call between the first device 102 and the second device 104 based on a first call link, the first device 102 receives a call request from a third device 106, which is logged into a third account. In response to a call transfer operation triggered by the call request, the first device 102 identifies a bypass device 108 to establish a call with the third device 106, which is logged into the first account. The first device 102 generates a call transfer instruction for the bypass device 108 based on the call request. The first device 102 sends the call transfer instruction to the bypass device 108, instructing the establishment of a second call link for network communication between the bypass device 108 (logged into the first account) and the third device 106 (logged into the third account). The terminal 102 can be, but is not limited to, various desktop computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, etc. Portable wearable devices can include smartwatches, smart bracelets, head-mounted devices, etc.
[0074] In one embodiment, such as Figure 2 As shown, a network call method is provided, which can be applied to... Figure 1 Taking the first device as an example, the explanation includes the following steps:
[0075] In step S202, during the network call between the first device and the second device based on the first call link, a call request initiated by the third device is received. The first device has logged into the first account, the second device has logged into the second account, and the third device has logged into the third account.
[0076] The first communication link is the link through which the first device and the second device communicate. A link is a medium used to transmit signals. In other words, the first communication link is the medium used for signal transmission between the first device and the second device.
[0077] A network call can be at least one of audio or video calls. A call request initiated by a third device refers to a call request initiated by a third device to the first device.
[0078] Specifically, the first device logs in to the first account, and the second device logs in to the second account. The first device, which has logged in to the first account, and the second device, which has logged in to the second account, establish a first call link. The first device and the second device conduct network calls based on the first call link.
[0079] The third device logs into the third account, and the third device that has logged into the third account initiates a call request to invite the first device to make a network call.
[0080] During a network call between the first device and the second device, the first device may receive a call request from the third device to initiate a network call.
[0081] In one embodiment, the first communication link can be a communication link between a first application on a first device and a second application on a second device. The first account belongs to the first application, the second account belongs to the second application, and both applications are of the same type. The third account belongs to a third application, which can be an application of the same type as the first application or an application of a different type.
[0082] The first, second, and third applications can be any application with VoIP functionality. These applications can refer to clients installed on the terminal or to portable applications, i.e., applications that can be used without downloading and installing. Portable applications are also called applets, which typically run as subroutines within the client; the client is called the parent application, and the subroutine running within it is called the child application. Applications can also refer to web applications opened through a browser, but are not limited to these.
[0083] In this embodiment, the first device has logged into the first account of the first application, the second device has logged into the second account of the second application, and the third device has logged into the third account of the third application.
[0084] During a network call between a first application on the first device and a second application on the second device based on a first call link, the first device may receive a call request initiated by a third application on the third device.
[0085] Step S204: In response to the call transfer operation triggered by the call request, determine the bypass device to establish a call with the third device, and the bypass device has logged into the first account.
[0086] The bypass device is bound to the first device, and the bypass device and the first device are bound through the same first account. That is, the bypass device and the first device are logged into the same first account.
[0087] A bypass device is a device that has been logged into the first account and is different from the first device.
[0088] Specifically, when a user using the first device receives a call request from a third device, they can transfer the call request to a bypass device that is logged into the first account. The user can transfer the call request by triggering a call transfer operation. In response to the user's call transfer operation, the first device identifies the bypass device that is logged into the first account, which is the bypass device to establish a call with the third device.
[0089] In this embodiment, in response to a call transfer operation triggered by a call request, the first device queries at least one candidate device that is logged into the first account, and selects one of the candidate devices from the queried candidate devices as a bypass device to establish a call with the third device.
[0090] Furthermore, the user can select one of the candidate devices as a bypass device. The first device can also select a candidate device that meets preset conditions from the queried candidate devices as a bypass device. The preset conditions may include at least one of network type, distance, or device type. For example, selecting a candidate device that uses the same network as the first device as a bypass device, or selecting a candidate device whose distance from the first device is within a preset distance range, or selecting the candidate device with the shortest distance from the first device as a bypass device, or selecting a candidate device with the same device type as the first device as a bypass device. Device types include, for example, mobile phones, tablets, computers, etc.
[0091] In this embodiment, in response to a call transfer operation triggered by a call request, the first device generates a device query request for the call request and sends the device query request to the server, requesting the server to query at least one candidate device that is logged into the first account. The first device selects a bypass device from the candidate devices returned by the server.
[0092] In this embodiment, the bypass device has logged into the first account of the first application, that is, both the bypass device and the first device are logged into the first account of the first application.
[0093] Step S206: Generate a call transfer instruction for the bypass device based on the call request.
[0094] The call transfer instruction refers to the instruction to transfer the call request of a third device to a bypass device. The call transfer instruction instructs the establishment of a second call link, which is used for network calls between a bypass device logged into the first account and a third device logged into the third account.
[0095] Specifically, after the first device determines the bypass device to establish a call with the third device, it can generate a call transfer instruction for the bypass device based on the call request.
[0096] Furthermore, the first device can generate a call transfer instruction for the bypass device based on the device identifier and call request of the bypass device.
[0097] Step S208: Send a call transfer instruction to the bypass device. The call transfer instruction is used to establish a second call link. The second call link is used for network calls between the bypass device that has logged into the first account and the third device that has logged into the third account.
[0098] Specifically, the first device initiates a call transfer instruction to the bypass device. Upon receiving the call transfer instruction, the bypass device establishes a second call link based on the instruction and conducts a network call with the third device based on the second call link.
[0099] In this embodiment, the first device can send a call transfer instruction to the server. The call transfer instruction is used to instruct the server to establish a second call link for the third device and the bypass device, and to instruct the server to send the link identifier of the second call link to the third device and the bypass device respectively. The link identifier of the second call link is used to instruct the third device and the bypass device to access the second call link.
[0100] In this embodiment, the call transfer instruction is used to instruct the bypass device to access the second call link. The first device can establish the second call link and send the link identifier of the second call link to the bypass device and the third device respectively, so that the bypass device and the third device can access the second call link based on the link identifier and conduct network calls based on the second call link.
[0101] In this embodiment, the first device and the bypass device belong to the first user, the second device belongs to the second user, and the third device belongs to the third user. When the first user is making a network call using the first device and the second user is using the second device, the third user sends a call request to the first device using the third device. The first user can select an available bypass device within the first device and transfer the call request sent by the first device to the bypass device. This allows the first user's first device to maintain its network call with the second device while simultaneously making a call with the third device through the bypass device. Furthermore, the first device and the bypass device are logged into the same first account, enabling the user to conduct multiple calls simultaneously using the same account.
[0102] In the aforementioned VoIP method, during a VoIP call between the first and second devices via a first call link, a call request initiated by a third device is received. The first device is logged into a first account, the second device into a second account, and the third device into a third account. In response to a call transfer operation triggered by the call request, a bypass device is identified to establish a call with the third device. This bypass device is logged into the first account. This allows the user, upon receiving a new incoming call during a VoIP call, to choose to transfer the new call request to a device logged into the same account as the first device. A call transfer instruction is generated for the bypass device based on the call request and sent to it, instructing the bypass device to accept the call request from the third device. The call transfer instruction instructs the establishment of a second call link. This second call link is used for VoIP calls between the bypass device logged into the first account and the third device logged into the third account. This allows the user to receive incoming call requests transferred by the first device via a bypass device logged into the same account while using the first device for a VoIP call via the first call link, and to initiate new VoIP calls via the second call link. This enables the user to participate in multiple calls simultaneously, avoiding missing important calls.
[0103] In one embodiment, in response to a call transfer operation triggered by a call request, determining a bypass device to establish a call with a third device includes:
[0104] In response to a call transfer operation triggered by a call request, at least one device identifier is displayed, indicating that the candidate device is logged into the first account; in response to a selection operation for at least one device identifier, the candidate device indicated by the selected device identifier is used as a bypass device to establish a call with the third device.
[0105] Specifically, in response to a call transfer operation triggered by a user's call request, the first device queries candidate devices logged into the first account and displays device identifiers for at least one candidate device. The user can select one of the device identifiers as a bypass device. In response to the user's selection operation, the first device determines the candidate device indicated by the selected device identifier and uses that candidate device as the bypass device to establish a call with the third device.
[0106] In this embodiment, the first device displays a request interface for a call request, which includes a call transfer control. In response to the user's triggering of the call transfer control, the first device displays the device identifier of at least one candidate device, such as... Figure 3 As shown, tablet A, tablet B, mobile phone C, and computer D are displayed, and the user can select one of them as a bypass device.
[0107] In this embodiment, in response to a call transfer operation triggered by a call request, at least one device identifier is displayed. The candidate device indicated by the device identifier is logged into the first account, thereby allowing devices logged into the first account to transfer call requests for the first device. In response to a selection operation performed on at least one device identifier, the candidate device indicated by the selected device identifier is designated as a bypass device to establish a call with the third device. This allows the first device to transfer new incoming call requests to devices logged into the same account while maintaining its current call, enabling users to participate in multiple calls simultaneously using multiple different devices logged into the same account.
[0108] In one embodiment, in response to a call transfer operation triggered by a call request, at least one device identifier is displayed, including:
[0109] The request interface for the call request is displayed, and the request interface displays a call transfer control.
[0110] In response to the triggering operation of the call transfer control, a device query request for the call request is generated and sent to the server; at least one device identifier is received from the server based on the device query request, and the received at least one device identifier is displayed on the request interface.
[0111] Specifically, when the first device receives a call request from the third device, the first device displays a request interface for the call request, which includes a call transfer control. In response to the user's triggering of the call transfer control, the first device generates a device query request for the call request and sends the request to the server.
[0112] The server receives the device query request, searches for candidate devices logged into the first account, and returns the device identifiers of at least one candidate device to the first device. The first device receives the device identifiers from the server and displays them on the request interface.
[0113] In this embodiment, a request interface for a call request is displayed. The request interface displays a call transfer control. By triggering the call transfer control, the user can send a device query request to the server. The server will then query other candidate devices that are logged into the same first account as the first device, allowing the user to select any device from the candidate devices to transfer the call request of the third device.
[0114] In one embodiment, sending a call transfer instruction to a bypass device includes:
[0115] A call transfer instruction is sent to the server. The call transfer instruction is used to instruct the server to establish a second call link for the third device and the bypass device, and to send the link identifier of the second call link to the third device and the bypass device respectively. The link identifier of the second call link is used to instruct the third device and the bypass device to access the second call link.
[0116] Specifically, the first device generates a call transfer instruction for the bypass device based on the device identifier and call request of the bypass device.
[0117] The first device sends a call transfer instruction to the server. Upon receiving the instruction, the server establishes a second call link and sends its link identifier to both the third device and the bypass device. The third device and the bypass device can then access the second call link based on the link identifier, thereby enabling network calls.
[0118] In this embodiment, the call transfer instruction includes the device identifier of the bypass device and the device identifier of the third device. The server obtains the device identifier of the bypass device and the device identifier of the third device from the call transfer instruction, and establishes a second communication link based on the device identifier and the device identifier.
[0119] In this embodiment, a call transfer instruction is sent to the server. The call transfer instruction is used to instruct the server to establish a second call link for the third device and the bypass device, and to send the link identifier of the second call link to the third device and the bypass device respectively. The link identifier of the second call link is used to instruct the third device and the bypass device to access the second call link, so that a first call link and a second call link can be established for the first account respectively, so that the user can use the first account to participate in multi-calls on two devices based on two call links.
[0120] In one embodiment, the first account belongs to the first application, the second account belongs to the second application, the first application and the second application belong to the same application type, the third account belongs to the third application, and the call request is initiated by the third application of the third device;
[0121] In response to a call transfer operation triggered by a call request, a bypass device is identified to establish a call with a third device, including:
[0122] In response to a call transfer operation triggered by a call request, the application type of the third application that initiated the call request is determined; if the application type of the third application is the same as that of the first application, the bypass device that logs into the first application through the first account is determined, and the bypass device waits to establish a call with the third device.
[0123] Specifically, the first device has logged into the first account of the first application, the second device has logged into the second account of the second application, and the third device has logged into the third account of the third application. The first application and the second application belong to the same application type.
[0124] During a network call between a first application on a first device and a second application on a second device based on a first call link, the first application on the first device may receive a call request initiated by a third application on a third device.
[0125] When a user receives a call request initiated by a third device, the user can trigger a call transfer operation for that request. The first application of the first device responds to the call transfer operation triggered by the user in response to the call request by determining the application type of the third application that initiated the call request. The first device determines whether the application type of the third application is the same as the application type of the first application. If they are the same, it determines the bypass device that is logged into the first application through the first account and uses the determined bypass device as the device to establish a call with the third device.
[0126] In this embodiment, the first device and the bypass device belong to the first user, and the first account is the application account used by the first user in the first application. The second device belongs to the second user, and the second account is the application account used by the second user in the second application. The third device belongs to the third user, and the third account is the application account used by the third user in the third application. When the first user, through the first application logged in with the first account on the first device, and the second user, through the second application logged in with the second account on the second device, are conducting a network call, the third user, through the third application logged in with the third account on the third device, sends a call request to the first application on the first device. The first user can select an available bypass device on the first device. The first user, through the first application on the first device, transfers the call request to the first application logged in with the first account on the bypass device. This allows the first user to maintain a network call with the second application through the first application while simultaneously conducting a call with the third application through the first application on the bypass device. This enables the user to simultaneously conduct multiple calls using the same account on different devices using the same application.
[0127] In this embodiment, the method further includes: when the application type of the third application is different from that of the first application, determining a bypass device that logs into the fourth application through the first account, the fourth application and the third application belong to the same application type, the bypass device is ready to establish a call with the third device, and the second call link is used for the fourth application that has logged into the first account and the third device that has logged into the third account to conduct network calls.
[0128] In this embodiment, the first account belongs to the first application, the second account belongs to the second application, the first application and the second application are of the same application type, and the third account belongs to the third application. The call request is initiated by the third application of the third device, enabling the user to make network calls through the application on the device. In response to the call transfer operation triggered by the call request, the application type of the third application that initiated the call request is determined. When the application type of the third application is the same as the application type of the first application, it means that the user is in the process of making a call using the first account of the first application on the first device, and a new call request is received for the first account of the first application. Then the user can transfer the call request to another bypass device of their own that uses the first account to log in to the first application. This allows the user to make multi-way calls with multiple users on different devices using the same application with the same account.
[0129] In one embodiment, generating a call transfer instruction for a bypass device based on a call request includes:
[0130] Determine the link type of the first call link; based on the call request and the link type of the first call link, generate a call transfer instruction for the bypass device, which instructs the establishment of a second call link with a different link type than the first call link.
[0131] Specifically, the first device determines the link type of the first call link, and based on the call request and the link type of the first call link, generates a call transfer instruction for the bypass device. The call transfer instruction instructs the establishment of a second call link with a different link type than the first call link.
[0132] In this embodiment, the first device sends a call transfer instruction to the server. After receiving the call transfer instruction, the server determines the link type of the first call link and establishes a second call link. The established second call link is of a different type than the first call link.
[0133] In this embodiment, the link type of the first call link is determined. Based on the call request and the link type of the first call link, a call transfer instruction for the bypass device is generated. The call transfer instruction instructs the establishment of a second call link with a different link type than the first call link. By establishing a first communication link and a second communication link of different types, users can use the same account of the same application on different devices to make calls with different users on different communication links, so that the same account of the same application can participate in multiple calls simultaneously on different devices.
[0134] In one embodiment, the method further includes:
[0135] The system receives a call invitation from a second device forwarded by the server, sends a feedback signal to the server accepting the call invitation, receives the link identifier of the first call link returned by the server based on the feedback signal, accesses the first call link based on the link identifier, and conducts a network call with the second device that has accessed the first call link.
[0136] Specifically, the second device generates a call invitation for the first device, which requests a network call with the first device. The second device sends the call invitation to the server, and the server forwards the call invitation to the first device.
[0137] Upon receiving the call invitation, the first device, in response to the user's call connection operation triggered by the invitation, sends a feedback signal to the server accepting the call invitation. Upon receiving this feedback signal, the server establishes a first call link and sends the link identifier of the first call link to both the first and second devices. The first and second devices then connect to the first communication link based on this link identifier. After connection, both devices can use the first call link to conduct network calls.
[0138] In this embodiment, if the second device sends a call invitation to the first application of the first device through the second application, then according to the above processing, the first application of the first device and the second application of the second device can access the first communication link and conduct a network call.
[0139] In this embodiment, the device receives a call invitation initiated by the second device forwarded by the server, sends a feedback signal to the server to accept the call invitation, and receives the link identifier of the first call link returned by the server based on the feedback signal. The device then accesses the first call link based on the link identifier, thereby conducting a network call with the second device that has already accessed the first call link.
[0140] In one embodiment, the network calling method provided in this application can be applied to, for example... Figure 4 In the application environment shown, a second device 104, already logged into a second account, sends a call invitation to a first device 102 to a server 110. The first device 102, also logged into a first account, receives the call invitation forwarded by the server 110 via the network and sends a feedback signal to the server 110 accepting the call invitation. The server 110 receives this feedback signal, establishes a first call link, and enables the first and second devices to conduct a network call based on this link. During the network call between the first device 102 and the second device 104 based on the first call link, the server 110 receives a call request from a third device 106, which is already logged into a third account. The server 110 forwards this call request to the first device 102. The first device 102, in response to the call request, triggers a call transfer operation and identifies a bypass device 108 to establish a call with the third device 106, which is already logged into the first account. The first device 102 generates a call transfer instruction for the bypass device 108 based on the call request. The first device 102 sends the device identifier and call transfer instruction of the bypass device 108 to the server 110.
[0141] Server 110 establishes a second call link based on the call transfer instruction, and sends the link identifier of the second call link to the third device 106 and the bypass device 108 respectively, so that the third device 106 and the bypass device 108 can access the second call link and conduct network calls based on the second call link.
[0142] In one embodiment, such as Figure 5 As shown, a network call method is provided, which can be applied to... Figure 1 Taking the server in the example, the following steps are included:
[0143] In step S502, during the network call between the first device and the second device based on the first call link, a call request initiated by the third device is forwarded to the first device. The first device has logged into the first account, the second device has logged into the second account, and the third device has logged into the third account.
[0144] Specifically, during a network call between the first device and the second device based on the first call link, when a call request initiated by the third device is received for the first device, the call request is forwarded to the first device.
[0145] In this embodiment, when a call invitation for the first device is received from the second device, the call invitation is forwarded to the first device; a feedback signal from the first device accepting the call invitation is received, and a first call link is established; a link identifier of the first call link is sent to the first device and the second device respectively, the link identifier being used to instruct the first device and the second device to join the first call link and conduct network calls based on the first call link.
[0146] Step S504: Receive the device identifier and call transfer instruction from the first device in response to the call request. The device identifier is used to indicate the bypass device to establish a call with the third device. The bypass device has been logged into the first account.
[0147] Specifically, the first device receives a call request initiated by the third device, forwarded by the server. In response to the call request, the first device initiates a call transfer operation, identifies the bypass device to which it intends to establish a call with the third device, and confirms that the bypass device is logged into the first device's account. Based on the call request, the first device generates a call transfer instruction for the bypass device and sends the device identifier of the bypass device along with the call transfer instruction to the server.
[0148] The server receives the device identifier and call transfer instruction from the first device, and uses the bypass device indicated by the device identifier as the bypass device to receive the call request from the third device.
[0149] Step S506: Establish a second call link based on the call transfer instruction.
[0150] Specifically, the server establishes a second call link based on the call transfer instruction, which is used for bypass devices and third devices to conduct network calls.
[0151] In step S508, the link identifier of the second call link is sent to the third device and the bypass device respectively, so that the third device and the bypass device can access the second call link and conduct network calls based on the second call link.
[0152] Specifically, the server sends the link identifier of the second call link to the third device and the bypass device, respectively. After receiving the link identifier, the third device and the bypass device access the second call link based on the link identifier and conduct network calls based on the second call link.
[0153] In this embodiment, during a network call between the first device and the second device based on the first call link, the server forwards a call request initiated by the third device to the first device. The first device is logged into a first account, the second device is logged into a second account, and the third device is logged into a third account. This allows the first device to receive call requests from the third device during a network call with the second device based on the first call link. The server also receives a device identifier and a call transfer instruction from the first device in response to the call request. The device identifier indicates the bypass device to which the call is to be established with the third device. The bypass device is logged into the first account, allowing the user to choose to transfer a new call request to a device with the same account as the first device when receiving a new call request during a network call. A second call link is established based on the call transfer command. The link identifier of the second call link is sent to the third device and the bypass device respectively, so that the third device and the bypass device can access the second call link and conduct network calls based on the second call link. This allows users to receive incoming call requests transferred by the first device while using the first device to conduct network calls based on the first call link, and to conduct new network calls based on the second call link using the bypass device that is logged into the same account. This allows users to participate in multiple calls at the same time and avoid missing important calls.
[0154] In one embodiment, receiving the device identifier and call transfer instruction from the first device in response to the call request includes:
[0155] Receive a device query request generated by the first device in response to a call request; query at least one candidate device that is logged into the first account, and return the device identifier of at least one candidate device to the first device; receive the device identifier selected by the first device from the returned device identifiers, and receive a call transfer instruction generated by the first device based on the selected device identifier and the call request.
[0156] Specifically, when the first device receives a call request from the third device, the first device generates a device query request in response to the call request and sends the device query request to the server.
[0157] When the server receives the device query request, it queries for candidate devices that are logged into the first account and returns the device identifier of at least one candidate device to the first device.
[0158] The first device displays device identifiers of at least one candidate device received. A first user using the first device can select one of the device identifiers as a bypass device. In response to the user's selection, the first device determines the selected device identifier. Based on the selected device identifier and the call request, the first device generates a call transfer instruction and sends the selected device identifier and the call transfer instruction back to the server. The server uses the candidate device indicated by the returned device identifier as a bypass device to establish a call with the third device.
[0159] In this embodiment, when the first device receives a call request from the third device, the first device displays a request interface for the call request, which includes a call transfer control. In response to the user's triggering of the call transfer control, the first device generates a device query request for the call request and sends the request to the server.
[0160] In this embodiment, the server receives a device query request generated by the first device in response to a call request, queries other candidate devices logged into the same first account as the first device, and provides the device identifiers of at least one candidate device back to the first device for the user to select. The server receives the device identifier selected by the first device from the feedback device identifiers and receives a call transfer instruction generated by the first device based on the selected device identifier and the call request. The server then uses the candidate device indicated by the selected device identifier as a bypass device to establish a call with the third device. This allows the first device to transfer new incoming call requests to devices logged into the same account while maintaining its current call, enabling the user to participate in multiple calls simultaneously using multiple different devices logged into the same account.
[0161] In one embodiment, establishing a second call link based on a call transfer instruction includes:
[0162] Based on the call transfer instruction, the call request initiated by the third device for the first device is transferred to the bypass device; in response to the bypass device's connection event for the forwarded call request, a second call link is established between the bypass device and the third device.
[0163] Specifically, the first device generates a call transfer instruction for the bypass device based on the device identifier and call request of the bypass device.
[0164] The first device sends a call transfer instruction to the server. Upon receiving the instruction, the server establishes a second call link and sends its link identifier to both the third device and the bypass device. The third device and the bypass device can then access the second call link based on the link identifier, thereby enabling network calls.
[0165] In this embodiment, the call transfer instruction includes the device identifier of the bypass device and the device identifier of the third device. The server obtains the device identifier of the bypass device and the device identifier of the third device from the call transfer instruction, establishes a second communication link, and connects the device identifier of the bypass device and the device identifier of the third device to the second communication link, so that the bypass device and the third device can conduct network calls based on the second call link.
[0166] In this embodiment, based on a call transfer instruction, a call request initiated by a third device for a first device is transferred to a bypass device. In response to the bypass device's connection event for the forwarded call request, a second call link is established between the bypass device and the third device. This allows the third device and the bypass device to access the second call link for network calls, thereby enabling the establishment of a first call link and a second call link for the first account. This allows the user to use the first account to participate in multi-calls on two devices based on two call links.
[0167] In one embodiment, a network calling method is provided for interaction between a first device, a second device, a third device, a bypass device, and a server, specifically including:
[0168] The first user logged into the first account in the first application on the first device, and the first user logged into the first account in the first application on each of the candidate devices. The second user logged into the second account in the second application on the second device, and the third user logged into the third account in the third application on the third device. Among them, the first application, the second application, and the third application are applications of the same type.
[0169] The second user triggers a call invitation for the first application on the first device through the second application on the second device, and the second application sends the call invitation to the server.
[0170] After receiving the call invitation, the server verifies the status of the second application, changes the status of the second application to "in call", and sends the call invitation to the first application on the first device.
[0171] After the first user receives a call invitation from the second user through the first application, the first application triggers a response signal to accept the call invitation, and then sends the response signal back to the server.
[0172] Upon receiving the response signal, the server can establish a first call link and send the link identifier of the first call link to the first application of the first device and the second application of the second device, respectively.
[0173] Based on the received link identifier, the first application of the first device and the second application of the second device access the first call link, enabling the first user and the second user to conduct network calls based on the first call link.
[0174] During a network call between the first application on the first device and the second application on the second device, a third user can trigger a call request to the first application on the first device through the third application on the third device, and the third application will send the call request to the server.
[0175] After receiving the call invitation, the server sends the call request to the first application on the first device.
[0176] After the first user receives the call request through the first application on the first device, the call transfer operation can be triggered to send a device query request to the server.
[0177] After receiving a device query request, the server will query each of the first user's candidate devices that are not in call mode, and then return the device identifiers of the candidate devices to the first application of the first device.
[0178] The first application on the first device displays the device identifiers of each candidate device received, and the first user can select one of the device identifiers. The first application generates a call transfer instruction based on the call request and sends the selected device identifier and the call transfer instruction back to the server.
[0179] The server receives the device identifier and call transfer instruction, and sends a call request to the first application of the bypass device indicated by the device identifier.
[0180] After the first user receives the call request through the first application of the bypass device, it can trigger an answer signal to accept the call.
[0181] Upon receiving the response signal from the bypass device, the server establishes a second call link and sends the link identifier of the second call link to the first application of the bypass device and the third application of the third device, respectively.
[0182] The first user receives the link identifier of the second call link through the first application of the bypass device, and can access the second call link based on the link identifier.
[0183] The third user receives the link identifier of the second call link through the third application of the third device, and can access the second call link based on the link identifier.
[0184] After access, the first application of the bypass device and the third application of the third device conduct network calls based on the second call link. At this time, the first user conducts network calls with the second user based on the first call link, and the first user conducts network calls with the third user based on the second call link.
[0185] In this embodiment, while the second user is making a network call with the first application on the first device using the second application, the third user sends a call request to the first application on the first device through the third application on the third device, which is logged into with the third account. The first user can select an available bypass device on the first device. The first user, through the first application on the first device, transfers the call request to the first application on the bypass device, which is logged into with the first account. This allows the first user to maintain a network call with the second application through the first application while simultaneously making a call with the third application through the first application on the bypass device. This enables the user to simultaneously make multiple calls using the same application on different devices with the same account.
[0186] Traditional VoIP architecture, such as Figure 6 As shown, the application is installed on the device as a client. Network calls are achieved through the interaction between the client installed on the device and the server. The server is the physical server. When a user clicks to make a call, the client sends call signaling to the server, containing information about both the initiator and the recipient. Call signaling is either a call request or a call invitation. Upon receiving the signaling, the server forwards it to the session management service. The session management service verifies the initiator's status and changes it to "in call," while simultaneously instructing the signaling service to send a call request to the recipient.
[0187] After receiving the call request signaling, the receiving party sends an acknowledgment signal to the signaling service through the answering service. The signaling service forwards this information to the session management service. Upon confirming the call request is accepted, the session management service obtains an available room number from the room management service and sends that room number to the client through the signaling service. A room is a communication link, and a room is a link identifier.
[0188] After receiving the room number, the client of both the initiator and the receiver sends a request to enter the room to the signaling service. The signaling service forwards the information to the room management service, which responds to the request. At this point, both the initiator and the receiver have entered the room and can then conduct audio and video calls normally.
[0189] When the call ends, the client's hang-up service sends a hang-up request to the signaling service, which then hands it over to the session management service. The session management service resets the states of the initiator and receiver. Simultaneously, the client's hang-up service sends a check-out request to the signaling service, which then hands it over to the room management service. The room management service reclaims the room resources, at which point the audio / video call ends.
[0190] As can be seen from the above process, when a user is on a call, both users are in the same call room. If a new call request is received at this time, if the user needs to answer the call, they can only leave the current call room, that is, end the call, and then establish a connection with the new caller and enter the new call room. When the call ends, if the interrupted call needs to be resumed, the call connection can only be re-established by calling again.
[0191] In this embodiment, a network call method is provided, with the following architecture: Figure 7 As shown, device management and bypass services have been added to the traditional architecture. When a new call is received during a call, the user can choose to bypass the call. At this time, the user can choose to log in to another device with the same account to answer the call. In this way, the user can answer the call without affecting the existing call line.
[0192] The bypass service is responsible for call forwarding and request processing. The structure of the bypass service is as follows: Figure 8 As shown, this includes incoming call bypass service and bypass answering service.
[0193] like Figure 9 As shown, when a user receives an incoming call, the call bypass service determines whether the user has any online devices that are not currently in a call. If so, a bypass signaling message is sent during the incoming call, activating the call bypass option. When the user selects call bypass, they send a bypass request signaling message to the server. Upon receiving this message, the server's signaling service forwards it to the device management service. The device management service queries a list of all online devices (excluding the user's own device) that are not in call mode and returns this list to the call bypass service. At this point, the call bypass service displays a list of devices available for bypassing. This list includes the device identifiers of candidate devices. When the user selects a candidate device's identifier, that device becomes the bypass device. The call bypass service then packages the device identifier and the incoming call identifier into a start bypass signaling message and sends it to the signaling service. The signaling service receives and forwards this message to the device management service, which then sends a bypass answer signaling message to the selected bypass device. After receiving the bypass answer signaling, the bypass device sends a bypass answering response signaling to the signaling service. The signaling service then forwards this to the device management service. The device management service requests a room identifier and sends it to both the bypass device and the incoming call device, while also updating the session status recorded by the session management service. At this point, the bypass device and the incoming call device have established a communication link and can begin normal audio and video calls. Finally, the device management service sends a response signal to the device that sent the start bypass signaling, and the device updates its call page display upon receiving it.
[0194] like Figure 10As shown, the bypass answering service is responsible for responding to bypass answering signaling initiated by other devices. When another device selects the bypass device for bypass answering when receiving a call, it sends a start bypass signaling to the server. The server's signaling service receives this and hands it over to the device management service, which then sends a bypass answering signaling to the bypass device. Upon receiving the bypass answering signaling, the bypass answering service replies with a bypass answering response signaling. The server's signaling service receives this and forwards it to the device management service. The device management service then assigns a room identifier to the room management service and sends this room identifier to both the bypass device and the incoming call device via a call establishment signaling. Upon receiving the call establishment signaling, both the bypass device and the incoming call device reply with a call establishment complete signaling and begin entering the corresponding room. Simultaneously, they activate local device capture and playback. Upon receiving this signaling, the signaling service hands it over to the device management service, which updates the corresponding device status and the user's session status in the session management. At this point, the user can communicate with the incoming call device from the bypass device.
[0195] The server-side device management service structure is as follows: Figure 11 As shown, this includes device status management service and bypass signaling processing service. The device status management service is responsible for recording the call status of the user's online devices to provide information for bypass calls, such as... Figure 12 As shown, this allows users to select an available candidate device when they need to make a bypass call.
[0196] The bypass signaling processing service is responsible for processing bypass-related signaling, the main signaling of which is as follows:
[0197] Bypass Request Signaling: The bypass signaling processing service needs to return a list of available online devices to the user.
[0198] Start Bypass Signaling: Send a bypass answer signaling message to the bypass device. After receiving a reply, request a room identifier from the room management service and return it to the bypass device and the incoming call device.
[0199] Bypass answering signaling: responsible for updating user equipment status and session status.
[0200] This embodiment provides an application scenario for a network call method, specifically applied to a network call scenario between a first device, a second device, a third device, and a bypass device, including:
[0201] When a user clicks to make a call, the client sends a call signaling message to the server, which includes information about the initiator and the recipient.
[0202] After receiving the signaling information, the server-side signaling service forwards it to the session management service. The session management service verifies the initiator's status and changes the initiator's status to "in call," while simultaneously instructing the signaling service to send a call request to the recipient.
[0203] After receiving the call request signaling, the receiving party sends an acknowledgment signal to the signaling service through the answering service. The signaling service forwards this information to the session management service. Upon confirming the call request is accepted, the session management service obtains an available room number from the room management service and sends this room number to the client through the signaling service. A room is a call link, and the room number is the link identifier for that call link.
[0204] After receiving the room number, the client of both the initiator and the receiver sends a request to enter the room to the signaling service. The signaling service forwards the information to the room management service, which responds to the request. At this point, both the initiator and the receiver have entered the room and can then conduct audio and video calls normally.
[0205] During an audio / video call, when a user receives a new incoming call request and can trigger the incoming call bypass service, the incoming call bypass service sends a bypass request signaling to the server. Upon receiving this signaling, the server forwards it to the device management service. The device status management service within the device management service queries a list of all online devices (excluding the user's own device) that are currently in non-call mode. The bypass signaling processing service within the device management service returns this list to the incoming call bypass service, at which point the incoming call bypass service displays a list of devices that can be bypassed.
[0206] When a user selects a candidate device from the list of bypassable devices, the selected candidate device is designated as the bypass device. The incoming call bypass service then packages the device identifier and the incoming call identifier into a start bypass signaling message and sends it to the signaling service. Upon receiving the message, the signaling service forwards it to the bypass signaling processing service in the device management service. The bypass signaling processing service in the device management service then sends a bypass answering signaling message to the selected bypass device.
[0207] After receiving the bypass answering signaling, the bypass device's bypass answering service sends a bypass answering response signaling to the signaling service. The signaling service then forwards this to the bypass signaling processing service within the device management service. The bypass signaling processing service in the device management service requests a room identifier and sends it to both the bypass device and the incoming call device, while also updating the session status recorded by the session management service. At this point, the bypass device and the incoming call device establish a communication link and can begin normal audio and video calls. Finally, the device management service sends a response signal to the device that sent the start bypass signaling, and the device updates its call page display upon receiving the signal.
[0208] When the call ends, the client's hang-up service sends a hang-up request to the signaling service, which then hands it over to the session management service. The session management service resets the states of the initiator and receiver. Simultaneously, the client's hang-up service sends a check-out request to the signaling service, which then hands it over to the room management service. The room management service reclaims the room resources, at which point the audio / video call ends.
[0209] With the network calling method of this embodiment, users can receive multiple calls simultaneously. After receiving a call, users can randomly decide whether to transfer the call. When the call is transferred, since different calls do not interfere with each other, the device can continue the call. This eliminates the need for cumbersome interruption and recovery operations and can directly support simultaneous multi-line calls.
[0210] Furthermore, since the target device for call forwarding is an online device with the same account dynamically selected by the user, the user only needs to agree to the forwarding on the calling device. The target device can then establish a call directly without confirmation, allowing the user to receive important calls in a timely manner and answer multiple calls simultaneously, responding according to priority, thus improving the timeliness and efficiency of the user's calls.
[0211] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.
[0212] Based on the same inventive concept, this application also provides a network calling device for implementing the network calling method described above. The solution provided by this device is similar to the solution described in the above method; therefore, the specific limitations in one or more network calling device embodiments provided below can be found in the limitations of the network calling method described above, and will not be repeated here.
[0213] In one embodiment, such as Figure 13 As shown, a network communication device 1300 is provided, including: a request receiving module 1302, a device determining module 1304, a generation module 1306, and an instruction sending module 1308, wherein:
[0214] The request receiving module 1302 is used to receive a call request initiated by a third device during a network call between the first device and the second device based on the first call link, wherein the first device has logged into a first account, the second device has logged into a second account, and the third device has logged into a third account.
[0215] The device determination module 1304 is used to determine the bypass device to establish a call with the third device in response to a call transfer operation triggered by a call request. The bypass device has been logged into the first account.
[0216] The generation module 1306 is used to generate a call transfer instruction for the bypass device based on the call request.
[0217] The instruction sending module 1308 is used to send a call transfer instruction to the bypass device. The call transfer instruction instructs the establishment of a second call link. The second call link is used for network calls between the bypass device that has logged into the first account and the third device that has logged into the third account.
[0218] In this embodiment, during a network call between the first device and the second device based on the first call link, a call request initiated by a third device is received. The first device is logged into a first account, the second device is logged into a second account, and the third device is logged into a third account. In response to a call transfer operation triggered by the call request, a bypass device is identified to establish a call with the third device. This bypass device is logged into the first account. This allows the user to choose to transfer a new call request to a device logged into the same account as the first device when receiving a new call request during a network call. A call transfer instruction is generated for the bypass device based on the call request and sent to the bypass device to instruct it to accept the call request from the third device. The call transfer instruction instructs the establishment of a second call link. This second call link is used for network calls between the bypass device logged into the first account and the third device logged into the third account. This allows the user to receive call requests transferred by the first device while using the first device for a network call based on the first call link, and to initiate new network calls using a bypass device logged into the same account. This enables the user to participate in multiple calls simultaneously and avoid missing important calls.
[0219] In one embodiment, the device determination module 1304 is further configured to, in response to a call transfer operation triggered in response to a call request, display at least one device identifier, wherein the candidate device indicated by the device identifier has logged into a first account; and, in response to a selection operation performed on at least one device identifier, use the candidate device indicated by the device identifier selected by the selection operation as a bypass device to establish a call with a third device.
[0220] In this embodiment, in response to a call transfer operation triggered by a call request, at least one device identifier is displayed. The candidate device indicated by the device identifier is logged into the first account, thereby allowing devices logged into the first account to transfer call requests for the first device. In response to a selection operation performed on at least one device identifier, the candidate device indicated by the selected device identifier is designated as a bypass device to establish a call with the third device. This allows the first device to transfer new incoming call requests to devices logged into the same account while maintaining its current call, enabling users to participate in multiple calls simultaneously using multiple different devices logged into the same account.
[0221] In one embodiment, the device determination module 1304 is further configured to display a request interface for a call request, the request interface displaying a call transfer control; in response to a trigger operation on the call transfer control, generate a device query request for the call request and send the device query request to the server; receive at least one device identifier from the server based on the device query request, and display the received at least one device identifier on the request interface.
[0222] In this embodiment, a request interface for a call request is displayed. The request interface displays a call transfer control. By triggering the call transfer control, the user can send a device query request to the server. The server will then query other candidate devices that are logged into the same first account as the first device, allowing the user to select any device from the candidate devices to transfer the call request of the third device.
[0223] In one embodiment, the instruction sending module 1308 is further configured to send a call transfer instruction to the server. The call transfer instruction is configured to instruct the server to establish a second call link for the third device and the bypass device, and to send the link identifier of the second call link to the third device and the bypass device respectively. The link identifier of the second call link is configured to instruct the third device and the bypass device to access the second call link.
[0224] In this embodiment, a call transfer instruction is sent to the server. The call transfer instruction is used to instruct the server to establish a second call link for the third device and the bypass device, and to send the link identifier of the second call link to the third device and the bypass device respectively. The link identifier of the second call link is used to instruct the third device and the bypass device to access the second call link, so that a first call link and a second call link can be established for the first account respectively, so that the user can use the first account to participate in multi-calls on two devices based on two call links.
[0225] In one embodiment, the first account belongs to the first application, the second account belongs to the second application, the first application and the second application belong to the same application type, the third account belongs to the third application, and the call request is initiated by the third application of the third device;
[0226] The device determination module 1304 is also used to determine the application type of the third application that initiated the call request in response to the call transfer operation triggered by the call request; when the application type of the third application is the same as the application type of the first application, it is determined that the bypass device is logged into the first application through the first account, and the bypass device is ready to establish a call with the third device.
[0227] In this embodiment, the first account belongs to the first application, the second account belongs to the second application, the first application and the second application are of the same application type, and the third account belongs to the third application. The call request is initiated by the third application of the third device, enabling the user to make network calls through the application on the device. In response to the call transfer operation triggered by the call request, the application type of the third application that initiated the call request is determined. When the application type of the third application is the same as the application type of the first application, it means that the user is in the process of making a call using the first account of the first application on the first device, and a new call request is received for the first account of the first application. Then the user can transfer the call request to another bypass device of their own that uses the first account to log in to the first application. This allows the user to make multi-way calls with multiple users on different devices using the same application with the same account.
[0228] In one embodiment, the generation module 1306 is further configured to determine the link type of the first call link; and based on the call request and the link type of the first call link, generate a call transfer instruction for the bypass device, wherein the call transfer instruction instructs the establishment of a second call link with a link type different from that of the first call link.
[0229] In this embodiment, the link type of the first call link is determined. Based on the call request and the link type of the first call link, a call transfer instruction for the bypass device is generated. The call transfer instruction instructs the establishment of a second call link with a different link type than the first call link. By establishing a first communication link and a second communication link of different types, users can use the same account of the same application on different devices to make calls with different users on different communication links, so that the same account of the same application can participate in multiple calls simultaneously on different devices.
[0230] In one embodiment, the request receiving module 1302 is used to receive a call invitation initiated by a second device forwarded by the server, and send a feedback signal to the server to accept the call invitation;
[0231] The device also includes an access module; the access module is used to receive the link identifier of the first call link returned by the server based on the feedback signal; access the first call link based on the link identifier, and conduct network calls with the second device that has been accessed by the first call link.
[0232] In this embodiment, the device receives a call invitation initiated by the second device forwarded by the server, sends a feedback signal to the server to accept the call invitation, and receives the link identifier of the first call link returned by the server based on the feedback signal. The device then accesses the first call link based on the link identifier, thereby conducting a network call with the second device that has already accessed the first call link.
[0233] In one embodiment, such as Figure 14 As shown, a network communication device 1400 is provided, including: a request forwarding module 1402, an instruction receiving module 1404, an establishment module 1406, and an identifier sending module 1408, wherein:
[0234] The request forwarding module 1402 is used to forward a call request initiated by a third device to the first device during a network call between the first device and the second device based on the first call link. The first device has logged into a first account, the second device has logged into a second account, and the third device has logged into a third account.
[0235] The instruction receiving module 1404 is used to receive the device identifier and call transfer instruction fed back by the first device in response to the call request. The device identifier is used to indicate the bypass device to establish a call with the third device. The bypass device has been logged into the first account.
[0236] Establishment module 1406 is used to establish a second call link based on call transfer instructions.
[0237] The identifier sending module 1408 is used to send the link identifier of the second call link to the third device and the bypass device respectively, so that the third device and the bypass device can access the second call link and conduct network calls based on the second call link.
[0238] In this embodiment, during a network call between the first device and the second device based on the first call link, the server forwards a call request initiated by the third device to the first device. The first device is logged into a first account, the second device is logged into a second account, and the third device is logged into a third account. This allows the first device to receive call requests from the third device during a network call with the second device based on the first call link. The server also receives a device identifier and a call transfer instruction from the first device in response to the call request. The device identifier indicates the bypass device to which the call is to be established with the third device. The bypass device is logged into the first account, allowing the user to choose to transfer a new call request to a device with the same account as the first device when receiving a new call request during a network call. A second call link is established based on the call transfer command. The link identifier of the second call link is sent to the third device and the bypass device respectively, so that the third device and the bypass device can access the second call link and conduct network calls based on the second call link. This allows users to receive incoming call requests transferred by the first device while using the first device to conduct network calls based on the first call link, and to conduct new network calls based on the second call link using the bypass device that is logged into the same account. This allows users to participate in multiple calls at the same time and avoid missing important calls.
[0239] In one embodiment, the instruction receiving module 1404 is further configured to receive a device query request generated by the first device in response to the call request; query at least one candidate device that has logged into the first account, and feed back the device identifier of the at least one candidate device to the first device; receive the device identifier selected by the first device from the fed-back device identifier, and receive a call transfer instruction generated by the first device based on the selected device identifier and the call request.
[0240] In this embodiment, the server receives a device query request generated by the first device in response to a call request, queries other candidate devices logged into the same first account as the first device, and provides the device identifiers of at least one candidate device back to the first device for the user to select. The server receives the device identifier selected by the first device from the feedback device identifiers and receives a call transfer instruction generated by the first device based on the selected device identifier and the call request. The server then uses the candidate device indicated by the selected device identifier as a bypass device to establish a call with the third device. This allows the first device to transfer new incoming call requests to devices logged into the same account while maintaining its current call, enabling the user to participate in multiple calls simultaneously using multiple different devices logged into the same account.
[0241] In one embodiment, the establishment module 1406 is further configured to transfer a call request initiated by a third device to a first device to a bypass device based on a call transfer instruction; and to establish a second call link between the bypass device and the third device in response to an event where the bypass device answers the forwarded call request.
[0242] In this embodiment, based on a call transfer instruction, a call request initiated by a third device for a first device is transferred to a bypass device. In response to the bypass device's connection event for the forwarded call request, a second call link is established between the bypass device and the third device. This allows the third device and the bypass device to access the second call link for network calls, thereby enabling the establishment of a first call link and a second call link for the first account. This allows the user to use the first account to participate in multi-calls on two devices based on two call links.
[0243] The modules in the aforementioned VoIP device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the corresponding operations of each module.
[0244] In one embodiment, a computer device is provided, which may be a terminal or a server. Taking a terminal as an example, its internal structure diagram can be as follows: Figure 15As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a network calling method. The display unit of the computer device is used to form a visually visible image. It can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.
[0245] Those skilled in the art will understand that Figure 15 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.
[0246] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.
[0247] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.
[0248] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.
[0249] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.
[0250] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.
[0251] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0252] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.
Claims
1. A method for making internet calls, characterized in that, The method includes: During a network call between the first device and the second device based on the first call link, a call request is received from the third device. The first device is logged into the first account, the second device is logged into the second account, and the third device is logged into the third account. In response to a call transfer operation triggered by the call request, a bypass device is identified to establish a call with the third device, and the bypass device is logged into the first account; A call transfer instruction for the bypass device is generated based on the call request. The call transfer instruction is sent to the bypass device. The call transfer instruction is used to establish a second call link. The second call link is used for the bypass device that has logged into the first account and the third device that has logged into the third account to conduct network calls.
2. The method according to claim 1, characterized in that, The step of determining the bypass device to establish a call with the third device in response to a call transfer operation triggered by the call request includes: In response to a call transfer operation triggered by the call request, at least one device identifier is displayed, indicating a candidate device that has logged into the first account; In response to a selection operation performed on the at least one device identifier, the candidate device indicated by the selected device identifier is designated as a bypass device to establish a call with the third device.
3. The method according to claim 2, characterized in that, The call transfer operation triggered in response to the call request, displaying at least one device identifier, includes: A request interface is displayed for the call request, and the request interface displays a call transfer control. In response to the triggering operation of the call transfer control, a device query request for the call request is generated and sent to the server; Receive at least one device identifier from the server based on the device query request, and display the received at least one device identifier on the request interface.
4. The method according to claim 3, characterized in that, Sending the call transfer instruction to the bypass device includes: The server sends a call transfer instruction to the server, which instructs the server to establish a second call link for the third device and the bypass device, and sends a link identifier of the second call link to the third device and the bypass device respectively. The link identifier of the second call link is used to instruct the third device and the bypass device to access the second call link.
5. The method according to claim 1, characterized in that, The first account belongs to the first application, the second account belongs to the second application, the first application and the second application belong to the same application type, the third account belongs to the third application, and the call request is initiated by the third application of the third device; The step of determining the bypass device to establish a call with the third device in response to a call transfer operation triggered by the call request includes: In response to a call transfer operation triggered in response to the call request, the application type of the third application that initiated the call request is determined; When the application type of the third application is the same as that of the first application, it is determined that the bypass device of the first application is logged in through the first account, and the bypass device is ready to establish a call with the third device.
6. The method according to claim 5, characterized in that, The step of generating a call transfer instruction for the bypass device based on the call request includes: Determine the link type of the first call link; Based on the call request and the link type of the first call link, a call transfer instruction is generated for the bypass device, which instructs the establishment of a second call link with a different link type than the first call link.
7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: The system receives a call invitation initiated by a second device and forwards it from the server, and sends a feedback signal to the server accepting the call invitation. Receive the link identifier of the first call link returned by the server based on the feedback signal; Access the first call link based on the link identifier, and conduct network calls with the second device that has already accessed the first call link.
8. A method for making internet calls, characterized in that, The method includes: During a network call between the first device and the second device based on the first call link, a call request initiated by the third device is forwarded to the first device. The first device is logged into a first account, the second device is logged into a second account, and the third device is logged into a third account. The system receives a device identifier and a call transfer instruction from the first device in response to the call request. The device identifier is used to indicate a bypass device that is to establish a call with the third device. The bypass device is logged into the first account. A second call link is established based on the call transfer instruction; The link identifier of the second call link is sent to the third device and the bypass device respectively, so that the third device and the bypass device can access the second call link and conduct network calls based on the second call link.
9. The method according to claim 8, characterized in that, Receiving the device identifier and call transfer instruction from the first device in response to the call request includes: Receive a device query request generated by the first device in response to the call request; Query at least one candidate device that is logged into the first account, and return the device identifier of the at least one candidate device to the first device; The device receives a device identifier selected by the first device from the feedback device identifier, and receives a call transfer instruction generated by the first device based on the selected device identifier and the call request.
10. The method according to claim 9, characterized in that, The establishment of a second call link based on the call transfer instruction includes: Based on the call transfer instruction, the call request initiated by the third device for the first device is transferred to the bypass device; In response to the bypass device's connection event for the forwarded call request, a second call link is established between the bypass device and the third device.
11. A network communication device, characterized in that, The device includes: The request receiving module is used to receive a call request initiated by a third device during a network call between a first device and a second device based on a first call link, wherein the first device has logged into a first account, the second device has logged into a second account, and the third device has logged into a third account. The device determination module is used to determine, in response to a call transfer operation triggered by the call request, a bypass device to establish a call with the third device, wherein the bypass device has logged into the first account; The generation module is used to generate a call transfer instruction for the bypass device based on the call request; The instruction sending module is used to send the call transfer instruction to the bypass device. The call transfer instruction is used to establish a second call link. The second call link is used for the bypass device that has logged into the first account and the third device that has logged into the third account to conduct network calls.
12. A network communication device, characterized in that, The device includes: The request forwarding module is used to forward a call request initiated by a third device to the first device during a network call between the first device and the second device based on a first call link. The first device has logged into a first account, the second device has logged into a second account, and the third device has logged into a third account. The instruction receiving module is used to receive the device identifier and call transfer instruction fed back by the first device in response to the call request. The device identifier is used to indicate the bypass device to establish a call with the third device. The bypass device has been logged into the first account. Establishment module, used to establish a second call link based on the call transfer instruction; The identifier sending module is used to send the link identifier of the second call link to the third device and the bypass device respectively, so that the third device and the bypass device can access the second call link and conduct network calls based on the second call link.
13. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 11.
14. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 11.
15. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 11.
