Call method and terminal equipment
By awakening and maintaining the main process of VoIP application in the terminal device and performing corresponding freezing processing according to its behavior, the possible abuse of VoIP applications during the process survival is solved, and lower power consumption and memory usage is achieved, while avoiding application crashes.
Patent Information
- Application Number
- CN202510137042.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-06-19
- Publication Date
- 2025-06-13
- Estimated Expiration
- 2044-06-19
AI Technical Summary
Existing VoIP applications may perform call-independent behaviors during the process survival, resulting in the abuse of VoIP messages and increasing the power consumption and memory usage of the entire machine.
By implementing a call method in the terminal device, the main process of the VoIP application is awakened and the process is kept within the preset time period, and the process is frozen only when the VoIP application does not make incoming calls within the preset time period.
It effectively constrains the behavior of VoIP applications, reduces the probability of VoIP messages being abused, increases the power consumption and memory usage of the entire machine, and solves the problem of VoIP applications crashing.
Smart Images

Figure CN120151329A_ABST
Abstract
Description
[0001] This application is a divisional application. The application number of the original application is 202410799406.4, and the original application date is June 19, 2024. The entire content of the original application is incorporated herein by reference. Technical Field
[0002] This application relates to the field of terminal technologies, and in particular, to a call method and a terminal device. Background Art
[0003] Currently, some applications (APPs) can implement calls using Voice over Internet Protocol (VoIP) technology based on Internet Protocol (IP). Such applications can be simply referred to as VoIP applications. When a VoIP application runs in the background of a device, to reduce the overall power consumption of the device, the device will freeze or destroy the process of the VoIP application. At this time, to implement a call of the VoIP application, the server can send a call message to the Push side through a Push channel. Then, after receiving the call message, the Push side will directly wake up the main process of the VoIP application to deliver the call message. Subsequently, the VoIP application can process operations such as process keep-alive and incoming call interface display in its own main process. In this solution, the VoIP application may perform behaviors unrelated to VoIP calls during the process survival period, resulting in the abuse of VoIP messages, thereby increasing the overall power consumption and memory occupancy of the device. Summary of the Invention
[0004] This application provides a call method and a terminal device, which can constrain the behavior of a VoIP application after the Push side receives a call message and wakes up the main process of the VoIP application, and solve the problems of abuse of VoIP messages, increased overall power consumption, and memory occupancy of the device.
[0005] To achieve the above object, this application adopts the following technical solutions:
[0006] In a first aspect, a call method is provided, which is applied to a terminal device. A first application with VoIP call function is installed in the terminal device. The method includes: when the first application is not running in the foreground of the terminal device, the terminal device wakes up the main process of the first application and sends a first call message received through the Push channel to the first application. The first call message is used to implement a first VoIP call; when, in response to the first call message, the first application does not give a first incoming call notification within a preset duration, the terminal device keeps the main process of the first application alive within the preset duration, where the first incoming call notification is used to output a first incoming call notification message for reminding the user.
[0007] Based on the above technical solution, when an application with VoIP call function is not running in the foreground of the terminal device, the terminal device can wake up the main process of the application and send the call message received through the Push channel for implementing VoIP calls to the application. After receiving the call message, if the application does not perform an incoming call notification for outputting an incoming call notification message to remind the user within a preset duration, the terminal device keeps the main process of the application alive within the preset duration. In this way, when the call message arrives at the terminal side and wakes up the main process of the VoIP application, if the VoIP application does not perform an incoming call notification within the preset duration, the terminal device only keeps the main process of the VoIP application alive within the preset duration, that is, only keeps the main process of the VoIP application alive for a period of time, which can restrict the behavior of the VoIP application and solve the problems of abuse of VoIP messages, increased power consumption of the entire machine, and occupation of memory.
[0008] In a possible design, the terminal device keeping the main process of the first application alive within the preset duration includes: the terminal device keeping the main process of the first application alive within the preset duration; at the moment when the preset duration is satisfied, the terminal device freezes the main process of the first application. In this way, after the terminal device keeps the VoIP application alive for a preset duration from the moment of waking up the main process of the VoIP application, then, at the moment when the preset duration from the moment of waking up the main process of the VoIP application is satisfied, the main process of the VoIP application is frozen. In this way, if the VoIP application does not perform an incoming call notification within the preset duration, the main process of the VoIP application will be refrozen. This can not only restrict the behavior of the VoIP application and reduce the probability of abuse of VoIP messages, increased power consumption of the entire machine, and occupation of memory. Moreover, by using the method of refreezing, the main process of the application can be woken up again, and the problem of the VoIP application crashing can be solved.
[0009] In a possible design, the method further includes: when, in response to the first call message, the first application performs the first incoming call notification within the preset duration, the terminal device continues to keep the main process of the first application alive after the preset duration. In this way, if the VoIP application performs an incoming call notification within the preset duration, the terminal device can continue to keep the main process of the VoIP application alive after the preset duration, so that the VoIP application can be kept active normally during the incoming call process and the call process and will not be frozen.
[0010] In a possible design, a Push end is included in the terminal device, and the Push end is used to transmit call messages; the terminal device wakes up the main process of the first application and sends a first call message received through the Push channel to the first application, including: the Push end wakes up the main process of the first application and sends the first call message received through the Push channel to the first application. In this way, the terminal device can include a Push end. When the VoIP application is not running in the foreground, the call message sent through the Push channel can be received through this Push end. Furthermore, the Push end can wake up the VoIP application based on the call message and deliver the call message. This can enable the VoIP application to receive call messages even when it is not running in the foreground, ensuring the normal progress of the call.
[0011] In a possible design, a process resource management service is further included in the terminal device, and the process resource management service is used to keep alive and freeze the main process of the first application; the terminal device keeps alive the main process of the first application within the preset duration, including: the Push end sends a first request to the process resource management service, and the first request is used to instruct the process resource management service to keep alive the main process of the first application within the preset duration; in response to the first request, the process resource management service keeps alive the main process of the first application within the preset duration. In this way, a process resource management service is further included in the terminal device. The Push end requests the process resource management service to keep alive the VoIP application within the preset duration. That is to say, the Push end can act as an agent for the VoIP application to apply to keep alive the main process of the VoIP application within the preset duration, instead of the VoIP application itself handling the keep-alive and freezing of the main process. This can restrict the behavior of the VoIP application and reduce the probability of abuse of VoIP messages, increase in overall power consumption, and occupation of memory.
[0012] In a possible design, the Push end sending a first request to the process resource management service includes: the Push end sends a first keep-alive request to the process resource management service, and the first keep-alive request is used to instruct the process resource management service to keep alive the main process of the first application; at the moment when the preset duration is satisfied, the Push end sends a first freeze request to the process resource management service, and the first freeze request is used to instruct the process resource management service to freeze the main process of the first application; the process resource management service keeping alive the main process of the first application within the preset duration in response to the first request includes: in response to the first keep-alive request and the first freeze request, the process resource management service keeps alive the main process of the first application within the preset duration.
[0013] In this way, the Push end can first send a keep-alive request to the process resource management service so that the main process of the VoIP application can be kept alive. Then, at the moment when the time elapsed since the main process of the VoIP application was awakened meets a preset duration, the Push end sends a freezing request to the process resource management service so that the main process of the VoIP application is frozen again. This can restrict the behavior of the VoIP application after the main process of the VoIP application is awakened, and reduce the probability of VoIP messages being misused, increasing the overall power consumption and memory occupancy of the device. Moreover, by adopting the method of refreezing, the main process of the application can be awakened again, which can solve the problem of the VoIP application crashing.
[0014] In a possible design, the terminal device includes a Push end, a process resource management service, and a VoIP management service. The Push end is used to transmit call messages. The process resource management service is used to keep alive and freeze the main process of a first application. The VoIP management service is used to receive incoming call notifications. When, in response to the first call message, the first application makes the first incoming call notification within the preset duration, for the terminal device to continue to keep alive the main process of the first application after the preset duration, it includes: the Push end sends a first keep-alive request to the process resource management service, and the first keep-alive request is used to instruct the process resource management service to keep alive the main process of the first application; in response to the first keep-alive request, the process resource management service keeps alive the main process of the first application; the first application, in response to the first call message, makes the first incoming call notification to the VoIP management service within the preset duration; in response to the first incoming call notification, the VoIP management service sends a second keep-alive request to the process resource management service, and the second keep-alive request is used to instruct the process resource management service to keep alive the main process of the first application; at the moment when the preset duration is met, the Push end sends a first freezing request to the process resource management service, and the first freezing request is used to instruct the process resource management service to freeze the main process of the first application; in response to the second keep-alive request and the first freezing request, the process resource management service continues to keep alive the main process of the first application within and after the preset duration.
[0015] In this way, the Push end, as the proxy of the VoIP application, sends a keep-alive request to the process resource management service, so that the VoIP application is kept alive. If the VoIP application notifies the VoIP management service of an incoming call within a preset duration, the VoIP management service can, as the proxy of the VoIP application, send a keep-alive request to the process resource management service, so that the VoIP application continues to be kept alive. Subsequently, even if the Push end, as the proxy of the VoIP application, sends a freeze request to the process resource management service again at the moment when the preset duration from the moment of waking up the main process of the VoIP application is satisfied, the process resource management service can still keep the main process of the VoIP application alive after the preset duration according to the keep-alive request of the VoIP management service, that is, the process resource management service can not respond to the freeze request of the Push end. This can not only restrict the behavior of the VoIP application after waking up the main process of the VoIP application, but also reduce the probability of VoIP messages being misused, increasing the overall power consumption of the device and the memory occupancy. It can also ensure that the VoIP application can be normally active during incoming calls and calls, not be frozen, and thus ensure the normal progress of calls.
[0016] In a possible design, the terminal device further includes a notification display service, and the notification display service is used to display the incoming call notification message of the first application; after the first application responds to the first call message and notifies the VoIP management service of the first incoming call within the preset duration, the method further includes: in response to the first incoming call notification, the VoIP management service sends the first incoming call notification message of the first application to the notification display service; the notification display service displays the first incoming call notification message on the terminal device. In this way, when the VoIP application is not running in the foreground, the notification display service can be used to display the incoming call notification message instead of the VoIP application.
[0017] In a possible design, the method further includes: when the first application is running in the foreground of the terminal device, the first application responds to the second call message received through the long connection and notifies the VoIP management service of the second incoming call; in response to the second incoming call notification, the VoIP management service sends the second incoming call notification message of the first application to the notification display service; the notification display service displays the second incoming call notification message on the terminal device. In this way, when the VoIP application is running in the foreground, the notification display service can also be used to display the incoming call notification message, which can be consistent with the situation when the VoIP application is not running in the foreground, and achieve the unity of the display entry.
[0018] In a possible design, the styles of the first incoming call notification message and the second incoming call notification message are the same. In this way, it can be ensured that the display styles of the incoming call notification messages are the same whether the VoIP application is running in the foreground or not, achieving unified display styles.
[0019] In a possible design, the first incoming call notification message and the second incoming call notification message are not full-screen displayed, and both the first incoming call notification message and the second incoming call notification message include the caller information, an answer button, and a reject button. In this way, the incoming call notification messages are all non-full-screen notification messages, and the incoming call notification messages directly include the caller information, an answer button, and a reject button. This can not only distinguish from the incoming calls of the traditional native system and solve the problem of easily misleading users, but also improve the connection efficiency.
[0020] In a possible design, the first incoming call notification message is displayed on the lock screen interface of the terminal device with a lock screen password set, and the first incoming call notification message supports the user to answer the incoming call of the first application without unlocking the terminal device. In this way, the incoming call notification message can be directly displayed on the lock screen interface with a lock screen password set, and the user can answer the call without unlocking the terminal device through this incoming call notification message, realizing answering without unlocking and improving the connection efficiency.
[0021] In a possible design, the method further includes: the notification display service displays a reminder message in the status bar of the terminal device, and the reminder message is used to remind that the call type corresponding to the first incoming call notification message is a VoIP call. In this way, the notification display service can display a reminder message in the status bar of the terminal device to remind that the incoming call is a VoIP call, realizing strong reminder of VoIP calls. Moreover, this reminder message is located in the status bar and can be not affected by whether the VoIP application is running in the foreground or in the background.
[0022] In a second aspect, a call method is provided, which is applied to a terminal device. The terminal device is installed with a first application having a VoIP call function. The method includes: the terminal device displays a first interface, the first interface is a lock screen interface with a lock screen password set, a first incoming call notification message of the first application is displayed on the first interface, the first incoming call notification message occupies a partial area of the first interface, and the first incoming call notification message includes a first answer button; the terminal device receives a trigger operation on the first answer button; in response to the trigger operation, without unlocking the terminal device, the terminal device connects the first VoIP call corresponding to the first incoming call notification message.
[0023] Based on the above technical solution, the terminal device can display a lock screen interface with a lock screen password set, and a call notification message of a VoIP application that occupies a part of the area is displayed on this interface, that is, the call of the VoIP application is a non-full-screen call, which can be distinguished from the native call notification interface to avoid misleading users. Moreover, the call notification message includes an answer button. When the terminal device receives a trigger operation on this answer button, without unlocking, it can connect the VoIP call corresponding to the call notification message. In this way, it can achieve answering without unlocking and improve the connection efficiency.
[0024] In a possible design, the first call notification message is a voice call notification message or a video call notification message, and the first VoIP call is a voice call. In this way, the call notification message is a video call or a voice call, and what is realized after unlocking without password is a voice call. That is to say, it can achieve a voice call without unlocking and can realize the quick answering of the voice call.
[0025] In a possible design, the first call notification message is a video call notification message, and the first call notification message further includes a second answer button; the method further includes: the terminal device receives a trigger operation on the second answer button; in response to the trigger operation on the second answer button, the terminal device reminds the user to unlock the terminal device; when the terminal device is successfully unlocked, the terminal device connects the second VoIP call corresponding to the first call notification message, and the second VoIP call is a video call. In this way, when receiving a video call notification message, the user needs to unlock the terminal device before a video call can be made, which can ensure the privacy of the video call.
[0026] In a possible design, after the terminal device connects the first VoIP call corresponding to the first call notification message, the method further includes: the terminal device receives an unlocking operation on the terminal device; in response to the unlocking operation, the terminal device displays a second interface and a first reminder message. The second interface is the interface that the terminal device finally displayed before locking the screen, and the first reminder message is located in the status bar. The first reminder message is used to remind that the call type of the first VoIP call is a VoIP call, and / or the progress of the first VoIP call. In this way, after the terminal device receives the unlocking operation, it can unlock the device and display the interface that was finally displayed before locking the screen, as well as the reminder message located in the status bar, that is, the call notification message is no longer displayed, which can avoid blocking the user interface. And this reminder message can be used to remind that the call type is a VoIP call, the progress of the VoIP call, etc., so that this reminder message can be not affected by whether the VoIP application is running in the foreground or not running in the background.
[0027] In a possible design, after the terminal device displays the second interface and the first reminder message, the method further includes: the terminal device receives a trigger operation on the first reminder message; in response to the trigger operation, the terminal device displays a third interface and the first reminder message, and the third interface is a full-screen voice call interface. In this way, the user can also operate on the first reminder message to present a full-screen voice call interface. That is to say, the first reminder message supports user operations, which can improve the user experience.
[0028] In a possible design, after the terminal device answers the first VoIP call corresponding to the first incoming call notification message, the method further includes: the terminal device receives a trigger operation on the first incoming call notification message; in response to the trigger operation on the first incoming call notification message, the terminal device reminds the user to unlock the terminal device; when the terminal device is successfully unlocked, the terminal device displays a third interface and the first reminder message, the third interface is a full-screen voice call interface, the first reminder message is located in the status bar, and the first reminder message is used to remind that the incoming call type of the first VoIP call is a VoIP incoming call, and / or the progress of the first VoIP call.
[0029] In this way, the incoming call notification message after connection displayed on the lock screen interface can be supported to be converted into a full-screen displayed call interface, and when the terminal device displays the full-screen call interface, the VoIP application is running in the foreground. In this scenario, the first reminder message located in the status bar is still displayed. That is to say, when the VoIP application is running in the foreground and in the background, the way of reminding the call progress is the same, which can improve the user experience.
[0030] In a possible design, the method further includes: the terminal device displays a fourth interface, and the fourth interface is the running interface of the first application. A second incoming call notification message of the first application is displayed on the fourth interface, and the second incoming call notification message is displayed in the notification center. In this way, when the terminal device displays the running interface of the VoIP application, the terminal device is running in the foreground. At this time, the incoming call notification message received can be displayed in the notification center, that is, the incoming call notification message not displayed by the VoIP application itself, so that the way of presenting the incoming call notification message can be kept consistent when the VoIP application is running in the foreground and not in the foreground.
[0031] In a third aspect, a terminal device is provided, and the terminal device has a function of implementing the method described in the first aspect and any one of the designs therein. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.
[0032] Fourthly, a terminal device is provided, which includes a processor and a memory. The memory is coupled to the processor. The memory is used to store computer program code, and the computer program code includes computer instructions. The processor reads the computer instructions from the memory so that the terminal device executes the method described in the first aspect or the second aspect and any design thereof as above. Optionally, the memory may be coupled to the processor or may be independent of the memory.
[0033] In a possible design, the terminal device further includes a display screen, which can be used for the terminal device to perform a display operation.
[0034] In a possible design, the terminal device further includes a communication interface, which can be used for the terminal device to communicate with other devices (such as a server). Exemplarily, the communication interface may be a transceiver, an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or a related circuit, etc.
[0035] Fifthly, a computer-readable storage medium is provided. The computer-readable storage medium includes a computer program. When the computer program runs on a terminal device, the terminal device is caused to execute the method described in the first aspect or the second aspect and any design thereof as above.
[0036] Sixthly, a computer program product is provided. The computer program product includes: a computer program or instructions. When the computer program or instructions run on a computer, the computer is caused to execute the method described in the first aspect or the second aspect and any design thereof as above.
[0037] Seventhly, a chip system is provided, which includes at least one processor and at least one interface circuit. The at least one interface circuit is used to perform a transceiver function and send instructions to the at least one processor. When the at least one processor executes the instructions, the at least one processor executes the method described in any design of the first aspect or the second aspect as above.
[0038] Eighthly, a communication system is provided, which includes a terminal device and a server. The terminal device and the server cooperate to implement the method described in any design of any aspect as above. Optionally, the server may include at least one of a Push server and an application server.
[0039] It should be noted that the technical effects brought by any design in the third aspect to the eighth aspect as above can refer to the technical effects brought by the corresponding design in the first aspect or the second aspect, which will not be elaborated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0040] Figure 1 It is a schematic diagram of the process of a call method provided by an embodiment of the present application;
[0041] Figure 2 Schematic diagram of another call method provided by an embodiment of this application;
[0042] Figure 3 Interface schematic provided by an embodiment of this application Figure 1 ;
[0043] Figure 4 Schematic diagram of another call method provided by an embodiment of this application;
[0044] Figure 5 Interface schematic provided by an embodiment of this application Figure 2 ;
[0045] Figure 6 Interface schematic provided by an embodiment of this application Figure 3 ;
[0046] Figure 7 Schematic diagram of the architecture of a communication system provided by an embodiment of this application;
[0047] Figure 8 Schematic diagram of the structure of a terminal device provided by an embodiment of this application;
[0048] Figure 9 Schematic diagram of the software structure of a terminal device provided by an embodiment of this application;
[0049] Figure 10 Schematic diagram of the flow of a call method provided by an embodiment of this application;
[0050] Figure 11 Interface schematic provided by an embodiment of this application Figure 4 ;
[0051] Figure 12 Interface schematic provided by an embodiment of this application Figure 5 ;
[0052] Figure 13 Schematic diagram of an answering process provided by an embodiment of this application;
[0053] Figure 14 Interface schematic provided by an embodiment of this application Figure 6 ;
[0054] Figure 15 Interface schematic provided by an embodiment of this application Figure 7 ;
[0055] Figure 16 Schematic diagram of a rejection process provided by an embodiment of this application;
[0056] Figure 17A schematic flowchart of another call method provided by an embodiment of the present application;
[0057] Figure 18 An interface schematic provided by an embodiment of the present application Figure 8 ;
[0058] Figure 19 A schematic flowchart of another call method provided by an embodiment of the present application;
[0059] Figure 20 A schematic structural diagram of another terminal device provided by an embodiment of the present application;
[0060] Figure 21 A schematic diagram of the structure of a chip system provided by an embodiment of the present application. Detailed implementation manners
[0061] In the description of the present application, unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship. For example, A / B may represent A or B; "and / or" in the present application is merely a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. Among them, A and B can be singular or plural.
[0062] In the description of the present application, unless otherwise specified, "a plurality of" means two or more than two. "At least one (item)" or similar expressions thereof refer to any combination of these items, including any combination of single item (item) or plural items (items). For example, at least one (item) of a, b, or c may represent: a, b, c, a and b, a and c, b and c, a and b and c, where a, b, and c can be single or multiple.
[0063] In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish the same items or similar items with basically the same functions and effects. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit being different.
[0064] VoIP (also known as IP phone, Internet phone, broadband phone, etc.) is a voice call technology that enables calls over the Internet. In one scenario, when a VoIP application (hereinafter simply referred to as a VoIP application, such as but not limited to social applications, conferencing applications, video applications, etc.) that uses VoIP technology to make calls runs in the foreground of a device, to establish a call, it can create a long connection in its own process to establish a communication connection with the server, and receive call messages (or VoIP call messages, call request messages, etc.) from the server through the long connection. It can be understood that in the embodiments of this application, a call message can refer to a call request message sent by the caller. A long connection means that after the client and the server establish a connection and communicate, after the communication is completed, the connection is not actively disconnected and remains connected.
[0065] In another scenario, when a VoIP application runs in the foreground of a device, to establish a call, it needs to send the call message through the Push channel. In this scenario, Figure 1 shows a schematic process diagram of a call method provided by an embodiment of this application. As Figure 1 shown, when the application server receives a call message sent by the caller, it requests the Push server to send the call message. Then, the Push server sends the call message to the Push client installed on the terminal device acting as the callee through the Push channel. Among them, the Push client can be a client responsible for receiving and processing Push messages. Correspondingly, after receiving the call message, the Push client directly wakes up (or is also called launches) the main process of the VoIP application and delivers the call message to the VoIP application. Finally, the VoIP application establishes a call connection (or is described as establishing a call connection) with the application server in the main process, and can communicate with the caller after the user answers.
[0066] In this solution, since the Push client does not perform any control on the application after delivering the call message to the VoIP application, the VoIP application processes operations such as process keep-alive and incoming call interface display in its own main process. In this way, the behavior of the VoIP application after the main process is woken up cannot be restricted, and the VoIP application may perform behaviors unrelated to VoIP calls during the process survival period, which may lead to the abuse of VoIP messages, thereby increasing the power consumption of the entire machine and the memory occupancy.
[0067] In this scenario, by way of example, Figure 2 shows a schematic process diagram of another call method provided by an embodiment of this application. As Figure 2As shown, after the application server receives a call message sent by the calling party, it requests the Push server to send the call message. Then, the Push server distributes the call message to the Push end installed on the terminal device serving as the called party through the Push channel. After receiving the call message, the Push end can act as an agent for the VoIP application and replace the VoIP application to connect to the notification display service to display a general notification message. When the user performs an opening operation such as clicking on the general notification message, in response to this operation, the notification display service will wake up the main process landing page of the VoIP application. It can be understood that the landing page can refer to the application interface entered by opening the general notification message, such as the incoming call interface 320 shown in (3) below. Finally, the VoIP application establishes a call connection with the application server in the main process and can communicate with the calling party after the user answers the call. Figure 3 as shown in (3) below.
[0068] In the locked screen scenario, when it detects that the user performs an operation to open the general notification message, it will first trigger device unlocking. Exemplarily, taking the device as a mobile phone and the Push application as an application in the mobile phone as an example, Figure 3 shows a schematic diagram of an interface provided by an embodiment of the present application. As Figure 3 shown in (1) below, the mobile phone displays a locked screen interface 300, where a general notification message 301 is displayed in the locked screen interface 300, and this general notification message 301 is the general notification message displayed by the notification display service. No answer button, reject button, etc. are displayed in the general notification message 301, and the foregoing buttons can only be presented by opening the general notification message 301. If the mobile phone detects an opening operation such as the user clicking on the general notification message 301, in response to this operation, it will first trigger mobile phone unlocking. The unlocking method can include but is not limited to face, fingerprint, or password. Taking the password as an example, the mobile phone can present an unlocking interface 310 as shown in Figure 3 shown in (2) below. When the user enters the mobile phone unlocking password in the unlocking interface 310, the mobile phone unlocks successfully. At the same time, the mobile phone can present an incoming call interface 320 as shown in Figure 3 shown in (3) below, where the incoming call interface 320 includes incoming call person information 321 (such as an avatar, name), an answer button 322, a reject button 323, etc.
[0069] In this solution, the user needs to perform multiple operations such as opening the general notification message, unlocking the device, and clicking the answer button to complete answering, and this operation is cumbersome, resulting in low connection efficiency. Moreover, in this solution, since the main process of the VoIP application only establishes a call connection with the application server after the user performs an opening operation on the general notification message, this will cause a long answering time and poor user experience.
[0070] Exemplarily, Figure 4The process schematic diagram of another call method provided by the embodiments of the present application is shown. As Figure 4 shown, when the application server receives a call message sent by the calling party, it requests the Push server to send the call message. Then, the Push server sends the call message to the Push end installed on the terminal device of the called party through the Push channel. Correspondingly, after receiving the call message, the Push end directly wakes up the main process of the VoIP application and delivers the call message to the VoIP application. At the same time, the Push end requires the VoIP application to give an incoming call notification within a specified time; otherwise, the main process will be destroyed. Then, the VoIP application will establish a call connection with the application server in advance and give an incoming call notification to the call management service within the specified time. Then, after receiving the incoming call notification from the VoIP application, the call management service will display a full-screen incoming call to the native call management service, such as Figure 5 the incoming call interface 500 in the lock screen scenario shown in (1) of Figure 5 . Subsequently, the user can answer the call through the incoming call interface fully displayed by the native call management service. For example, the user can perform operations such as swiping on the answer button 501 included in the incoming call interface 500 shown in (1) of Figure 5 . In response to this operation, the call is connected. At the same time, Figure 5 the incoming call interface shown in (1) of
[0071] can be switched to the call interface 510 shown in (2) of Figure 2 . Subsequently, the native call service will inform the VoIP application of the answer event. Correspondingly, the VoIP application processes the answer event by itself and can communicate with the calling party after informing the application server of the answer event.
[0072] In addition, in this solution, since the VoIP application will establish a call connection with the application server in advance, this can solve Figure 5 the problem of long answer time and poor user experience existing in the solution shown in Figure 5 . However, in this solution, if the VoIP application does not give an incoming call notification within the specified time, the main process will be forcibly destroyed. However, at the same time when the main process is destroyed, if the user opens the VoIP application, for example, when the user opens the VoIP application through the icon of the VoIP application on the desktop, this will cause the problem of the VoIP application crashing. Figure 4 In addition, in this solution, the full-screen incoming call interface (such as Figure 2The solution shown (such as a normal notification message) is displayed, so for the video call scenario, there is still Figure 2 The solution shown has the problems of complicated answering operation and low connection efficiency.
[0073] In addition, for the above two scenarios based on long connection and Push channel, in the audio and video call scenario, when the VoIP application switches to the background, the VoIP application will actively access the floating window capability to remind the user of the call progress. The way of reminding the user of the call progress when the VoIP application is running in the background and the foreground is not unified. Taking the audio call scenario as an example, for example, Figure 6 In the desktop 600 shown in (1), when the VoIP application is running in the background, the user can be reminded of the call progress (such as the call duration) through the floating window 601. When the VoIP application is running in the foreground, the user can be reminded of the call progress (such as the call duration) through the floating window 601. Figure 6 The call interface 610 shown in (2) reminds the user of the call progress. The reminder methods in these two scenarios are inconsistent, which affects the user experience.
[0074] Based on the above technical problems, the embodiment of the present application provides a calling method, which can constrain the behavior of the VoIP application after the call message arrives at the end side to wake up the main process of the VoIP application, reduce the abuse of VoIP messages, increase the power consumption of the whole machine and the probability of memory usage, and solve the problem of VoIP application crashing. It can also solve the problem that the incoming call interface and the call interface displayed in full screen are too similar to the native call interface, which is easy to mislead users, while achieving fast answering and improving the connection efficiency. It can also solve the problem that the way of reminding the call progress when the VoIP application is running in the foreground and when it is running in the background is inconsistent.
[0075] For example, Figure 7 FIG. 1 is a schematic diagram showing the architecture of a communication system for applying a calling method provided in an embodiment of the present application. Figure 7 As shown, the communication system 700 includes a terminal device 701, an application server 702, and a Push server 703, etc.
[0076] Among them, the terminal device 701 can be various devices installed with VoIP applications. Exemplarily, the terminal device 701 can include, but is not limited to, mobile phones, tablet computers, desktop computers, laptop computers, handheld computers, notebook computers, ultra-mobile personal computers (UMPCs), netbooks, as well as cellular phones, personal digital assistants (PDAs), artificial intelligence (AI) devices, wearable devices, in-vehicle devices, smart home devices, and / or smart city devices. Optionally, the terminal device 701 can be a fixed device or a portable device. The specific type of the terminal device in the embodiments of the present application is not particularly limited.
[0077] In some embodiments, the terminal device 701 can receive a call message from a calling party (such as the terminal device 704 described below) as the called party.
[0078] The Application Server 702 can be a server for providing services for the VoIP application. For example, it can provide a running environment for the VoIP application and manage resources such as the execution of the VoIP application, database connection, and file system. The application server can be used to process and respond to user requests, execute business logic, manage data storage, etc., to ensure that the VoIP application can run stably and efficiently. In some embodiments of the present application, when the terminal device 701 is the called party, the application server 702 is responsible for receiving the call message from the calling party and sending the call message to the Push server 703. It is also responsible for establishing a call connection with the terminal device 701.
[0079] The Push server 703 can be a server capable of implementing the application message push function. The Push server 703 can be used to handle and send Push requests and push real-time messages or notifications to the terminal device. In some embodiments of the present application, the Push server 703 is responsible for receiving the call message from the application server 702 and sending the call message to the terminal device 701 through the Push channel.
[0080] Optionally, the application server 702 and the Push server 703 can be cloud servers or network servers and other devices or servers with computing functions. It can be a single server, a server cluster composed of multiple servers, or a cloud computing service center.
[0081] It can be understood that in the embodiments of the present application, the application server 702 and the Push server 703 are implemented as two different servers. In other embodiments, the application server 702 and the Push server 703 may also be integrated together and implemented as one server.
[0082] Optionally, the operating systems installed on the terminal device 701, the application server 702, the Push server 703, etc. include but are not limited to or other operating systems. Of course, it is also possible that no operating system is installed.
[0083] Optionally, connections can be established between any two of the terminal device 701, the application server 702, the Push server 703, etc. through wired communication technologies and / or wireless communication technologies. Among them, the wireless communication technologies include but are not limited to at least one of the following: near field communication (NFC), Bluetooth (BT) (for example, traditional Bluetooth or Bluetooth low energy (BLE)), wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Zigbee, frequency modulation (FM), infrared (IR), wide area networks relayed through relay devices, etc.
[0084] Exemplarily, when the wireless communication technology is the above-mentioned wide area network, the wireless communication technology may be a 3rd-generation wireless telephone technology (3G) network, a 4th-generation mobile communication technology (4G) network, a 5th-generation mobile communication technology (5G) network, a future evolved public land mobile network (PLMN), or the Internet, etc.
[0085] It can be understood that Figure 7 is only a simplified schematic diagram for easy understanding. In actual applications, Figure 7Other devices may also be included in the communication system shown, such as the terminal device 704, which may also be various devices installed with VoIP applications. In some embodiments, the terminal device 704 may send a call message as the calling party to the called party (such as the terminal device 701 described above). The terminal device 704 and the terminal device 701 may be of the same type of terminal device or different types of terminal devices. Other introductions about the terminal device 704 (such as communication methods, device types, etc.) may refer to the corresponding introductions of the terminal device 701.
[0086] Exemplarily, Figure 8 A schematic structural diagram of a terminal device provided by an embodiment of the present application is shown. As Figure 8 shown, the terminal device 701 may include a processor 810, a memory 820, a universal serial bus (USB) interface 830, a charging management module 840, a power management module 841, a battery 842, an antenna 1, an antenna 2, a mobile communication module 850, a wireless communication module 860, an audio module 870, a speaker 870A, a receiver 870B, a microphone 870C, a key 880, a motor 891, a camera 892, a display screen 893, etc.
[0087] The processor 810 may include one or more processing units. For example, the processor 810 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Among them, different processing units may be independent devices or integrated in one or more processors.
[0088] The controller may generate operation control signals according to the instruction operation code and timing signals to complete the control of fetching and executing instructions.
[0089] A memory can also be provided in the processor 810 for storing instructions and data. In some embodiments, the memory in the processor 810 is a cache memory. This memory can hold the instructions or data that the processor 810 has just used or recycled. If the processor 810 needs to use the instruction or data again, it can directly call it from the said memory. This avoids repeated accesses and reduces the waiting time of the processor 810, thus improving the efficiency of the system.
[0090] In some embodiments, the processor 810 may include one or more interfaces, such as the USB interface 830.
[0091] The memory 820 can be used to store computer-executable program code, and the executable program code includes instructions. The memory 820 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 810 executes various functional applications and data processing of the terminal device 701 by running the instructions stored in the memory 820 and / or the instructions stored in the memory provided in the processor.
[0092] The charging management module 840 is used to receive a charging input from a charger. While charging the battery 842, the charging management module 840 can also supply power to the electronic device through the power management module 841.
[0093] The power management module 841 is used to connect the battery 842, the charging management module 840, and the processor 810. The power management module 841 receives the inputs from the battery 842 and / or the charging management module 840 and supplies power to the processor 810, the memory 820, the display screen 893, the camera 892, the wireless communication module 860, etc.
[0094] The wireless communication function of the terminal device 701 can be implemented through antenna 1, antenna 2, the mobile communication module 850, the wireless communication module 860, the modulation and demodulation processor, and the baseband processor, etc.
[0095] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the terminal device 701 can be used to cover a single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization rate of the antennas. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.
[0096] The mobile communication module 850 can provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc. applied to the terminal device 701.
[0097] The wireless communication module 860 can provide solutions for wireless communications applied to the terminal device 701, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc.
[0098] In some embodiments, the antenna 1 of the terminal device 701 is coupled to the mobile communication module 850, and the antenna 2 is coupled to the wireless communication module 860, enabling the terminal device 701 to communicate with the network and other devices (such as the application server 702, Push server 703, etc.) through wireless communication technologies. The wireless communication technologies may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc.
[0099] The audio module 870 is used to convert digital audio information into an analog audio signal for output, and is also used to convert analog audio input into digital audio signals.
[0100] The speaker 870A, also known as the "horn", is used to convert an audio electrical signal into a sound signal. The terminal device 701 can listen to hands-free calls through the speaker 870A.
[0101] The receiver 870B, also known as the "earpiece", is used to convert an audio electrical signal into a sound signal. When the terminal device 701 answers a call or a voice message, it can listen to the voice by bringing the receiver 870B close to the human ear.
[0102] The microphone 870C, also known as the "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can speak close to the microphone 870C with their mouth to input the sound signal into the microphone 870C.
[0103] The button 880 includes a power-on button, a volume button, etc. The button 880 can be a mechanical button or a touch button. The terminal device 701 can receive button inputs and generate key signal inputs related to the user settings and function controls of the terminal device 701.
[0104] The motor 891 can generate vibration prompts. For example, the motor 891 can be used for incoming call vibration prompts.
[0105] The camera 892 is used to capture still images or videos. In some embodiments, the terminal device 701 may include one or N cameras 892, where N is a positive integer greater than 1. In some embodiments of the present application, the camera can be used to collect images in a video call scenario.
[0106] The display screen 893 is used to display images, videos, etc. In some embodiments of the present application, the display screen 893 can be used to display various interfaces and information involved in VoIP calls.
[0107] In some embodiments, the software structure of the terminal device 701 can adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservices architecture, or a cloud architecture. In the embodiments of the present invention, taking the layered architecture as an example, the software structure of the terminal device 701 is exemplarily described.
[0108] Figure 9 Shows a schematic diagram of the software structure of a terminal device 701 provided by an embodiment of the present invention.
[0109] The layered architecture divides the software into several layers, and each layer has a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the terminal device 701 can include two layers, namely the application layer and the system service layer from top to bottom.
[0110] Among them, the application layer can include a series of application program packages, such as the VoIP application. The VoIP application can be used to establish a call connection with the application server to implement VoIP calls. It can also be used to handle events such as answering and hanging up. In some embodiments, when the VoIP application runs in the background of the terminal device 701, the VoIP application can receive call messages from the application server through the Push channel. In other embodiments, when the VoIP application runs in the foreground of the terminal device 701, the VoIP application can also receive call messages from the application server through a long connection with the application server.
[0111] The system server layer may include a series of system services, such as the Push end, process resource management service, VoIP management service, notification display service, etc. The Push end can be used to receive call messages sent by the Push server through the Push channel and deliver the call messages to the VoIP application. It can also be used to manage the wake-up (or thawing), keep-alive, freezing (or de-keep-alive) of the VoIP application process. The process resource management service can be used to perform operations such as waking up, keeping alive, and freezing the VoIP application process. For example, the process resource management service can allocate the required system resources (such as but not limited to memory resources, hard disk resources, processor resources, etc.) for the VoIP application process to wake up and keep alive the VoIP application process. Or, the process resource management service can recycle the system resources occupied by the VoIP application process to freeze the VoIP application process. The VoIP management service can be used to receive and process incoming call notification messages from the VoIP application. The incoming call can come from the Push channel or a long connection. It can also be used to publish incoming call information, handle the answering or hanging up of VoIP calls, manage the keep-alive of the VoIP application process, etc. The notification display service can be used to be responsible for the display of information related to VoIP calls, such as the display of incoming call information, etc.
[0112] It can be understood that in the embodiments of the present application, keeping alive the main process of the VoIP application can enable the main process to always exist and run in the memory. Freezing the main process of the VoIP application only temporarily suspends the main process and does not terminate the execution of the main process or destroy the main process. Once the main process needs to be run again, the main process can be awakened and quickly resume running.
[0113] The above system services are divided according to functions. In actual applications, there can also be other division methods. For example, multiple system services can be integrated together, or can be divided more finely according to the multiple functions included in each system service.
[0114] It can be understood that Figure 8 、 Figure 9 The schematic structure does not constitute a specific limitation on the terminal device 701. In other embodiments of the present application, the terminal device 701 may include more or fewer components than shown in the figure, or combine certain components, or split certain components, or have different component arrangements. The components shown in the figure can be implemented in hardware, software, or a combination of software and hardware.
[0115] For the hardware structure and software structure of the terminal device 704, reference can be made to the structure introduction of the terminal device 701. For the structures of the Push server 703 and the application server 702, reference can be made to Figure 8 the introduction of the terminal device 701 shown. Optionally, the Push server 703 or the application server 702 may include more thanFigure 8 More or fewer components shown, such as Push server 703 or application server 702, may only include a processor, a memory, a communication interface (or communication module), etc.
[0116] The technical solutions involved in the following embodiments can all be implemented in a device having a structure as shown in Figure 8 , Figure 9 and a system having the architecture as shown in Figure 7 The following describes with terminal device 701 as the terminal device, Push server 703 as the Push server, and application server 702 as the application server.
[0117] Exemplarily, Figure 10 shows a schematic flowchart of a call method provided by an embodiment of the present application. As shown in Figure 10 , the method includes the following steps:
[0118] S1001. The application server sends a call message to the Push server. Correspondingly, the Push server receives the call message from the application server.
[0119] Wherein, the call message may be a call message sent by the calling party, such as a call message sent by a VoIP application installed on the calling party. Exemplarily, taking the calling party as terminal device 704 as an example, as shown in Figure 11 in (1), terminal device 704 may display the running interface 1100 of the VoIP application. One or more contacts or groups may be included in the running interface of the VoIP application. The user may select any one of the contacts or groups to make a voice call or a video call. For example, if the terminal device detects that the user has performed a click operation on contact 1, in response to this operation, as shown in Figure 11 in (2), terminal device 704 displays the chat interface 1110 with contact 1. The user may implement a video call or a voice call with the contact by invoking a video call control or a voice call control in the chat interface 1110.
[0120] For example, the chat interface 1110 may include a function button 1111. If the terminal device 704 detects that the user has performed a click operation on the function button 1111, in response to this operation, as shown in Figure 11 in (3), terminal device 704 displays a voice call control 1121, a video call control 1122, etc. In response to the user's triggering operation on the voice call control 1121 or the video call control 1122, the application server may obtain the call message from terminal device 704.
[0121] It can be understood that Figure 11This is only an example of an operation for generating a call message for a VoIP application on a terminal device 704. In other embodiments, the operation for generating a call message for a VoIP application may be various key operations, gesture operations, voice operations, etc.
[0122] It can also be understood that in the embodiments of the present application, the call message may be a call message for a voice call or a call message for a video call.
[0123] S1002. The Push server sends the call message to the Push side through the Push channel. Correspondingly, the Push side receives the call message from the Push server.
[0124] S1003. The Push side acts on behalf of the VoIP application to apply to the process resource management service to keep the main process of the VoIP application alive.
[0125] S1004. The process resource management service keeps the main process of the VoIP application alive.
[0126] In some embodiments, there may be multiple proxies for the VoIP application, such as the Push side, the VoIP management service, etc. In this embodiment, the process resource management service can keep the main process of the VoIP application alive according to the granularity of the proxy (or proxy agent), that is, the process resource management service can keep the main process of the VoIP application alive respectively according to the instructions for keeping alive applied by each proxy of the VoIP application.
[0127] In some scenarios, the process resource management service may receive different instructions from different proxies of the VoIP application at the same time. For example, taking the different proxies of the VoIP application as the Push side and the VoIP management service respectively, the Push side applies to the process resource management service to keep the main process of the VoIP application alive, while the VoIP management service applies to freeze the main process of the VoIP application. At this time, in response to the instructions of the foregoing two proxies, the process resource management service can keep the main process of the VoIP application alive. That is to say, the priority of the instruction to keep the main process of the VoIP application alive is higher than the priority of the instruction to freeze the main process of the VoIP application at the same time, so that the normal operation of the VoIP application can be ensured.
[0128] S1005. The Push side wakes up the main process of the VoIP application and delivers the call message. Correspondingly, the VoIP application receives the call message from the Push side.
[0129] In this way, after the Push end receives the call message sent by the Push server, it first wakes up the main process of the VoIP application, and applies for thawing and keep-alive to the process resource management service through the proxy VoIP application, which can ensure that the VoIP application is not frozen during an incoming call and a call. Moreover, since it takes some time to wake up the main process of the VoIP application, performing step S1005 first and then step S1006 can reserve sufficient time for the VoIP application to give an incoming call notification.
[0130] S1006. The Push end restricts the VoIP application to give an incoming call notification within a specified time.
[0131] In some embodiments, the Push end can restrict the VoIP application to give an incoming call notification within a specified time by setting a freeze timer. Specifically, after the Push end executes step S1005, it starts the freeze timer to count. When the count reaches the specified duration, it refreezes the main process of the VoIP application. Optionally, in the embodiments of the present application, the Push end can also proxy the VoIP application to apply to the process resource management service to refreeze the main process of the VoIP application in the manner shown in step S1003.
[0132] Optionally, the Push end can set the freeze timer according to the granularity of the application and the call. That is, the freeze timer is set separately for different VoIP applications, and the freeze timer is set separately for different calls of the same VoIP application. In this way, the operations of keeping the main process alive and freezing the main process can be respectively performed on the main processes of different VoIP applications, so that the operations of different VoIP applications do not affect each other. The operations of keeping the main process alive and freezing the main process are respectively performed on different call processes of the same VoIP application, so that different call processes do not affect each other.
[0133] In this way, after the Push end wakes up the main process of the VoIP application, it restricts the VoIP application to give an incoming call notification within a specified time by setting a freeze timer, etc. When the VoIP application fails to give an incoming call notification within the specified time, the main process of the VoIP application will be refrozen. Or, when the process resource management service can keep the main process of the VoIP application alive according to the proxy granularity, at this time, if there is no other proxy applying to keep the main process of the VoIP application alive, then the main process of the VoIP application will also be refrozen. This can not only restrict the behavior of the VoIP application, but also reduce the probability of abuse of VoIP messages, increase the power consumption of the whole machine, and increase the memory occupancy. Moreover, by using the refreezing method, the main process of the application can be woken up again, which can solve the problem of the VoIP application crashing.
[0134] Of course, in other embodiments, after the Push end executes step S1005, the Push end can monitor the behavior of the VoIP application within a specified duration. When it is determined that the VoIP application does not give an incoming call notice within the specified time, the main process of the VoIP application can be refrozen. Conversely, when it is determined that the VoIP application gives an incoming call notice within the specified time, the main process of the VoIP application may not be refrozen. Optionally, the Push end can determine whether the VoIP application gives an incoming call notice within the specified time from the feedback message of other services (such as the VoIP management service). Optionally, in this implementation, the Push end can also start timing through a timer. Before the timing reaches the specified duration, if it is determined that the VoIP application has given an incoming call notice, the timer can be shut down. Correspondingly, the main process of the VoIP application will continue to be kept alive. Conversely, when the timing reaches the specified duration and it is determined that the VoIP application has not given an incoming call notice yet, the main process of the VoIP application can be refrozen.
[0135] Optionally, in addition to executing the above steps S1003, S1005 to S1006, the Push end can also perform operations such as verifying the legality of the call message and deduplication, which can ensure the security of the call process. These operations will not be introduced in detail in this article.
[0136] Steps S1001 to S1006 introduce the process of an incoming call. Next, the process of the VoIP application giving an incoming call notice will be introduced. Exemplarily, as Figure 10 shown, this process includes steps S1007 to S1014.
[0137] S1007. The VoIP application establishes a call connection with the application server.
[0138] In this way, the VoIP application establishes a call connection with the application server before the user executes the answer operation, that is, establishes a connection in advance. Compared with the method of establishing a call connection with the application server after the user executes the answer operation, it can reduce the answer delay and improve the user experience.
[0139] S1008. The VoIP application generates incoming call information.
[0140] Among them, the incoming call information can include one or more of the incoming callers' information (such as avatars, names, etc.), the notification landing page address, etc. Among them, the notification landing page address can be used to index the landing page displayed by the VoIP application when the call interface is opened through the incoming call notification, as shown in interface 1510 in (2) below Figure 15 and the video screen 1520 in (3) below. Figure 15
[0141] In some embodiments, after the VoIP application successfully establishes a connection with the application server in step S1007, it can then execute step S1008. Conversely, after the connection with the application server fails, step S1008 may not be executed. In this way, the overhead of the terminal device generating incoming call information can be saved. Of course, in other embodiments, steps S1007 and S1008 can also be executed synchronously.
[0142] S1009. The VoIP application registers at least one of an answer event and a reject event with the VoIP management service.
[0143] Among them, the answer event can be used by the VoIP management service to notify the VoIP application that the answer event has occurred when it determines that the user has performed an answer operation. The reject event can be used by the VoIP management service to notify the VoIP application that the reject event has occurred when it determines that the user has performed a reject operation.
[0144] Optionally, steps S1008 and S1009 can be executed synchronously or sequentially. When executed sequentially, the embodiments of the present application do not limit the order.
[0145] S1010. The VoIP application notifies the VoIP management service of an incoming call. Correspondingly, the VoIP management service receives the incoming call notification from the VoIP application.
[0146] Optionally, the incoming call notification may include the incoming call information in step S1008. In this way, the VoIP management service has a new incoming call notification capability, and the VoIP application can notify the VoIP management service of an incoming call.
[0147] S1011. The VoIP management service acts as an agent for the VoIP application to apply to the process resource management service to keep the main process of the VoIP application alive. Correspondingly, the process resource management service keeps the main process of the VoIP application alive.
[0148] In some embodiments, before the VoIP application executes step S1011, it can also verify the legality of the incoming call information, and after the verification passes, then execute step S1011.
[0149] In this way, by executing step S1011, a new agent for the process resource management service is added, that is, the VoIP management service. The VoIP management service acts as an agent for the VoIP application to apply to continue to keep the main process of the VoIP application alive. Even when the freeze timer described in step S1006 times out, the main process of the VoIP application can still be kept alive instead of responding to the freeze timer and refreezing the main process of the VoIP application.
[0150] Of course, in combination with the solutions in other embodiments described in step S1006, since the VoIP application will not be refrozen after the incoming call is notified within the specified time, that is, there is no scenario where the main process of the VoIP application needs to be refrozen when the freeze timer expires, the VoIP management service does not need to execute step S1011 either.
[0151] S1012. The VoIP management service generates an incoming call notification.
[0152] In some embodiments, the VoIP management service may generate an incoming call notification based on the incoming call information from the VoIP application. Among them, the incoming call notification may include one or more of the incoming callers' information, answer button, reject button, etc. Among them, the answer button can be used to receive the user's answer operation, and the reject button can be used to receive the user's reject operation, etc. Optionally, in the embodiments of the present application, the answer button and the reject button can be implemented by different controls, or by performing different operations on the same control.
[0153] S1013. The VoIP management service sends the incoming call notification to the notification display service. Correspondingly, the notification display server receives the incoming call notification from the VoIP management service.
[0154] Optionally, after the VoIP management service executes step S1013, it can also light up the screen of the terminal device.
[0155] S1014. The notification display service displays the incoming call notification.
[0156] Optionally, the notification display service can display the incoming call notification on the lock screen interface, notification center, etc. It can be understood that the lock screen interface in the examples of the present application is an example of a lock screen interface with a password set. In other embodiments, the lock screen interface can also be a lock screen interface without a password set.
[0157] Exemplarily, taking the voice call scenario as an example, Figure 12 (1) in shows a schematic diagram of an incoming call notification provided in the embodiments of the present application. As Figure 12 shown in (1), the terminal device displays the lock screen interface 1200 (which can be used as an example of the first interface). Among them, an incoming call notification 1201 (which can be used as an example of the first incoming call notification message) is displayed on the lock screen interface 1200. In the incoming call notification 1201, the incoming caller's information 1201a (such as name, avatar, etc., Figure 12In (1), only the name, the answer button 1201b (which can be used as an example of the first answer button), the reject button 1201c, etc. are shown. The incoming call notification 1201 enables the user to answer the voice call (which can be used as an example of the first VoIP call) or reject the voice call without unlocking the terminal device. Optionally, an identifier for the voice call, such as "xx application voice", can also be displayed in the incoming call notification 1201.
[0158] Taking the call scenario as a video call scenario as an example, Figure 12 In (2), a schematic diagram of another incoming call notification provided by an embodiment of the present application is shown. As Figure 12 As shown in (2), the terminal device displays the lock screen interface 1210. Among them, an incoming call notification 1211 (which can also be used as an example of the first incoming call message) is displayed on the lock screen interface 1210. In the incoming call notification 1211, the incoming caller information 1211a (such as the name, avatar, etc., Figure 12 In (2), only the name, the answer button 1211b (which can be used as an example of the second answer button), the reject button 1211c, etc. are shown. The incoming call notification 1211 enables the user to answer the video call (which can be used as an example of the second VoIP call) after unlocking the terminal device. Or, enables the user to reject the video call without unlocking the terminal device. Optionally, an identifier for the video call, such as "xx application video", can also be displayed in the incoming call notification 1211. Optionally, in the video call scenario, the user can also choose to only make a voice call. For example, Figure 12 As shown in the incoming call notification 1211 in (2), an answer button 1211d (which can also be used as an example of the first answer button) can also be displayed. By pressing this answer button 1211d, the user can make a voice call without unlocking the terminal device. That is to say, the incoming call notification 1211 can also enable the user to answer the voice call without unlocking the terminal device.
[0159] It can be understood that in the non-lock screen video call scenario, the video call notification received by the terminal device (such as Figure 12 the incoming call notification shown in (4), etc.) can also include the answer button 1211d to facilitate the user to choose to make a voice call.
[0160] Optionally, while executing step S1014, the VoIP application can also ring and vibrate. Of course, this ringing and vibrating operation can also be performed by other services (such as the VoIP management service). The embodiments of the present application do not make specific limitations on this.
[0161] Steps S1007 to S1014 introduce the process of notifying the VoIP application of an incoming call. Next, the answering process will be introduced. Exemplarily, Figure 13The figure shows a schematic diagram of an answering process provided by an embodiment of the present application. As Figure 13 shown, this process includes the following steps:
[0162] S1301. The notification display service receives the answering operation performed by the user.
[0163] Exemplarily, the answering operation can be a click operation on the answering button 1201b or the answering button 1211b as shown in 12. Of course, the answering operation can also be a triggering operation on the answering button included in the incoming call notification presented in the unlocking interface, etc. Or, the answering operation can also be other voice operations or gesture operations, etc.
[0164] S1302. The notification display service informs the VoIP management service of the answering operation. Correspondingly, the VoIP management server receives the answering operation informed by the notification display service.
[0165] In some embodiments, taking the voice call scenario as an example, the terminal device can execute steps S1303 to S1307.
[0166] S1303. The VoIP management service informs the VoIP application of the audio answering event. Correspondingly, the VoIP application receives the audio answering event from the VoIP management service.
[0167] In some embodiments, the VoIP management service can execute step S1303 based on Figure 10 the answering event registered by the VoIP application with the VoIP management service as shown in step S1009.
[0168] S1304. The VoIP application sends an audio answering instruction to the application server. Correspondingly, the application server receives the audio answering instruction from the VoIP application.
[0169] Among them, the VoIP application can send an audio answering instruction to the application server through the call connection established in Figure 10 step S1007 as shown.
[0170] S1305. Audio stream transmission is performed between the VoIP application and the application server.
[0171] Among them, when the application server returns an answering success to the VoIP application, audio stream transmission can be performed between the VoIP application and the application server, and the user can then make an audio call. Through this audio answering method, after the user performs an operation such as a click on the answering button 1201b as shown in (1) in Figure 12 , the answering is successful. That is, in the locked screen scenario, voice answering can be achieved in one step through the incoming call notification 1201, which can save answering steps, simplify operations, and improve the connection efficiency.
[0172] S1306. The VoIP application reports a successful answer event to the VoIP management service. Correspondingly, the VoIP management service receives the successful answer event reported by the VoIP application.
[0173] S1307. The VoIP management service docks with the notification display service to convert the incoming call notification into an in - call notification.
[0174] Among them, the in - call notification can be used to remind the user that a voice call is in progress.
[0175] Exemplarily, in combination with Figure 12 the incoming call notification 1201 shown in (1) of Figure 14 the incoming call notification 1201 can be converted into the in - call notification 1401 included in the lock screen interface 1200 shown in (1) of Figure 14 As shown in (1) of Figure 12 the in - call notification 1401 can include a microphone button 1401a, a speaker button 1401b, a hang - up button 1401c, etc. Optionally, the hang - up button 1401c and
[0176] In some embodiments, taking the video call scenario as an example, the terminal device can execute steps S1308 to S1311.
[0177] S1308. The VoIP management service triggers user unlocking.
[0178] In some embodiments, the VoIP management service can dock with the notification display service or other services to display an unlocking interface to trigger user unlocking. Exemplarily, in combination with Figure 12 the incoming call notification 1211 shown in (2) of Figure 15 when the user performs an operation such as clicking on the answer button 1211b, in response to this operation, as
[0179] shown in (1) of
[0180] the terminal device can present an unlocking interface 1500, and the user can enter a password in the unlocking interface 1500 to unlock the device. Of course, in other embodiments, the VoIP management service can also trigger user unlocking in other ways, such as face, fingerprint and other various ways. Figure 10 shown in
[0181] In some embodiments, the video answer landing page of the VoIP application main process can be an interface that reminds the user that a call is being answered. Exemplarily, after unlocking the terminal device in the manner shown in (1) of 15, the terminal device can present an in-call interface 1510 as shown in (2) of Figure 15 , and this interface 1510 is the video answer landing page of the VoIP application main process.
[0182] Similarly, in an audio call scenario, the terminal device can also present a notification that reminds the user that a call is being answered. As shown in the incoming call notification 1201 in conjunction with Figure 12 (1), when the user performs an answer operation such as clicking on the answer button 1201b, in response to this operation, before the terminal device presents an in-call notification 1401 as shown in (1) of Figure 14 , the terminal device can also present a notification that a call is being answered. For example, the notification that a call is being answered can be a notification after converting the words such as "xx application voice" included in the incoming call notification 1201 to words such as "connecting". Similarly, the VoIP management service can display the notification that a call is being answered to the notification display service.
[0183] Of course, in other embodiments, since the connection process is relatively fast, the above-mentioned in-call interface or in-call notification may be invisible to the user. Or, in other embodiments, the terminal device may also not display the above-mentioned in-call interface or in-call notification and directly present a notification or interface after answering the call. That is to say, in this embodiment, the video answer landing page can also be a video screen 1520 as shown in (3) below Figure 15 .
[0184] S1310. The VoIP application sends a video answer instruction to the application server. Correspondingly, the application server receives the video answer instruction from the VoIP application.
[0185] Among them, the VoIP application can send the video answer instruction to the application server through the call connection established in step S1007 as shown in Figure 10 .
[0186] S1311. Video stream transmission is performed between the VoIP application and the application server.
[0187] Among them, when the application server returns an answer success to the VoIP application, video stream transmission can be performed between the VoIP application and the application server.
[0188] Meanwhile, the VoIP application can also display a video screen. Exemplarily, after the answer is successful, the interface 1510 as shown in (2) of Figure 15 can jump to as shown in Figure 15When the video screen 1520 shown in (3) appears, the user can make a normal call.
[0189] Figure 13 The answering process has been introduced. Next, the rejection process will be introduced. Exemplarily, Figure 16 FIG. shows a schematic diagram of a rejection process provided by an embodiment of the present application. As Figure 16 shown, this process includes the following steps:
[0190] S1601. The notification display service receives the rejection operation performed by the user.
[0191] Exemplarily, the rejection operation can be, for example, a click operation on the rejection button 1201c or the rejection button 1211c as shown in Figure 12 FIG.. Of course, the rejection operation can also be a trigger operation on the rejection button included in the incoming call notification presented in the unlock interface, etc. Or, the rejection operation can also be other voice operations or gesture operations, etc.
[0192] S1602. The notification display service informs the VoIP management service of the rejection operation. Correspondingly, the VoIP management server receives the rejection operation informed by the notification display service.
[0193] S1603. The VoIP management service informs the VoIP application of the rejection event. Correspondingly, the VoIP application receives the rejection event from the VoIP management service.
[0194] In some embodiments, the VoIP management service can execute step S1603 based on the rejection event registered by the VoIP application with the VoIP management service according to step S1009 shown in Figure 10 FIG..
[0195] S1604. The VoIP application sends a rejection instruction to the application server. Correspondingly, the application server receives the rejection instruction from the VoIP application.
[0196] Among them, the VoIP application can send the rejection instruction to the application server through the call connection established according to step S1007 shown in Figure 10 FIG..
[0197] When the application server returns that the rejection is successful, this call ends.
[0198] S1605. The VoIP application reports a rejection success event to the VoIP management service. Correspondingly, the VoIP management service receives the rejection success event reported by the VoIP application.
[0199] S1606. The VoIP management service instructs the notification display service to delete the incoming call notification.
[0200] Exemplarily, the incoming call notification can be, for example, the incoming call notification 1201, incoming call notification 1211, etc. as shown in Figure 12 .
[0201] S1607. The VoIP management service agent requests the process resource management service to freeze the main process of the VoIP application.
[0202] Among them, step S1606 and step S1607 can be executed synchronously or sequentially. When executed sequentially, the present application does not limit the sequence.
[0203] S1608. The process resource management service freezes the main process of the VoIP application.
[0204] The above introduced the call process of sending a call message through the Push channel. It can be understood that in the embodiments of the present application, when sending a call message through the Push channel, the VoIP application is not running in the background. Before the terminal device receives the calling party's call message, the terminal device can present a locked screen interface or a non-locked screen interface (such as a desktop, or the running interface of other applications except this VoIP application, etc.). In the above embodiments, the locked screen interface presented by the terminal device is taken as an example. When the terminal device presents a non-locked screen interface, taking the desktop as an example, as shown in Figure 12 (3) therein, the terminal device can present a desktop 1220, and a voice incoming call notification 1221 can be displayed in the desktop 1220. As shown in Figure 12 (4) therein, the terminal device can present a desktop 1230, and a video incoming call notification 1231 can be displayed in the desktop 1230. Both the voice incoming call notification 1221 and the video incoming call notification 1231 can be in the notification center.
[0205] Among them, since the video incoming call notification 1231 is presented on the non-locked screen interface, therefore, the video incoming call notification 1231 enables the user to answer without unlocking. For example, when the user performs an answer operation through the answer button in the video incoming call notification 1231, in response to this answer operation, the terminal device can directly present the interface 1510 as shown in Figure 15 (2) therein, or directly present the video screen 1520 as shown in Figure 15 (3) therein, etc.
[0206] For the introduction of each control or information in the voice incoming call notification 1221 and the video incoming call notification 1231, reference can be made to the introduction of the corresponding controls or information in Figure 12 (1), (2) therein. For the display of the voice incoming call notification 1221 and the video incoming call notification 1231, and the implementation of answering, rejecting, etc. through the voice incoming call notification 1221 and the video incoming call notification 1231, reference can be made to the implementation of the incoming call notifications shown in Figure 12 (1), (2) therein.
[0207] The call process of sending call messages through a long connection is introduced below. It can be understood that in the embodiments of the present application, when a call message is sent through the Push channel, the VoIP application runs in the foreground. Before the terminal device receives the call message from the calling party, the terminal device can present any running interface of the VoIP application.
[0208] In this long connection scenario, Figure 17 shows a schematic flowchart of another call method provided by the embodiments of the present application. As Figure 17 shown, the method includes the following steps:
[0209] S1701. The application server sends a call message to the VoIP application through the long connection channel. Correspondingly, the VoIP application receives the call message from the application server.
[0210] Among them, the long connection channel can be the long connection channel established between the VoIP application when it runs in the foreground and the application server.
[0211] S1702. The VoIP application generates incoming call information.
[0212] S1703. The VoIP application registers at least one of the answer event and the reject event with the VoIP management service.
[0213] S1704. The VoIP application notifies the VoIP management service of an incoming call. Correspondingly, the VoIP management service receives the incoming call notification from the VoIP application.
[0214] S1705. The VoIP management service acts on behalf of the VoIP application to apply to the process resource management service to keep the main process of the VoIP application alive.
[0215] Figure 17 In the solution shown, although there is no freeze timer, due to various reasons such as the VoIP application may be switched to the background, the main process of the VoIP application may be frozen. By executing step S1705, the main process of the VoIP application can be included, so that the main process of the VoIP application can be normally active during an incoming call and a call.
[0216] S1706. The process resource management service keeps the main process of the VoIP application alive.
[0217] S1707. The VoIP management service generates an incoming call notification.
[0218] S1708. The VoIP management service sends the incoming call notification to the notification display service. Correspondingly, the notification display server receives the incoming call notification from the VoIP management service.
[0219] S1709. The notification display service displays an incoming call notification.
[0220] Regarding Figure 17 For the introduction of each of the steps shown, reference can be made to Figure 10 the introduction of the corresponding steps shown.
[0221] Currently, when the VoIP application is running in the foreground, the incoming call information displayed is presented by the VoIP application itself, and this incoming call information is a notification within the application that includes the caller information, an answer button, and a reject button. When the VoIP application is running in the background, the incoming call information displayed is presented by the device system, and this incoming call information is a general notification message or a full-screen incoming call interface. The display entry and style in the two scenarios are inconsistent. However, for the solution provided in the embodiments of the present application, such as Figure 10 , Figure 17 etc., it unifies the display entry (such as the lock screen interface or the notification center) and the display style (such as both being non-full-screen incoming call notifications, and both including caller information, an answer button, and a reject button, etc.) in the two scenarios. Moreover, for the solution provided in the embodiments of the present application, when the system service proxy VoIP application makes an incoming call notification and keeps the call alive during the call process, there is no need for the VoIP application to handle the keep-alive operation.
[0222] Exemplarily, the incoming call notification in the long connection scenario can be like the voice incoming call notification 1801 (which can be used as an example of the second incoming call notification message) presented in the interface 1800 shown in (1) of Figure 18 (which can be used as an example of the fourth interface), or it can be like the video incoming call notification 1811 presented in the interface 1810 shown in (2) of Figure 18 (which can be used as an example of the fourth interface). The voice incoming call notification 1801 and the video incoming call notification 1811 can be presented in the notification center. It can be understood that both the interface 1800 and the interface 1810 are the running interfaces of the VoIP application. In the embodiments of the present application, this running interface is taken as an example of a chat interface, and this running interface can also be other interfaces, such as the main interface, the Moments interface, and various other running interfaces.
[0223] Similarly, in this scenario, the video incoming call notification 1811 can also enable the user to answer without unlocking. Regarding Figure 18 For the introduction of the incoming call notification shown, reference can be made to Figure 12 the relevant introduction shown.
[0224] Optionally, for the answer process and the reject process in the long connection scenario, reference can be made to the relevant implementation in the Push channel scenario.
[0225] Based on the incoming call notification provided in the embodiments of the present application, it not only supports answering without unlocking, simplifies the answering operation, improves the connection efficiency, but also can be distinguished from the system native call interface to avoid misleading users.
[0226] In some embodiments, in addition to presenting the above notifications, the terminal device may also present reminder information for VoIP calls. This reminder information may not be affected by whether the VoIP application is running in the foreground. That is, regardless of whether the VoIP application is running in the foreground, the terminal device can always present the reminder information for the VoIP call. Based on the reminder information provided in the embodiments of the present application, the way of reminding the call progress during the answering process of the VoIP application can be unified, improving the user experience.
[0227] As a possible implementation, the reminder information for the VoIP call includes at least one of an incoming call reminder and a reminder during the call. Optionally, the incoming call reminder, the reminder during the call, etc. can be presented in the status bar in a capsule style. Of course, they can also be presented in other forms, or presented in an area included in all running interfaces other than the status bar. Exemplarily, the incoming call reminder can be used to remind the user that the incoming call is from the VoIP application (or called a VoIP incoming call), such as Figure 12 , Figure 15 in (1), (2) in Figure 18 etc., the incoming call reminder 10 shown. The reminder during the call can be used to remind the user that the incoming call is from the VoIP application, remind the user of the progress of the VoIP call, etc. at least one of them, such as Figure 14 , Figure 15 the reminder during the call 20 shown in (3) in
[0228] Optionally, after the terminal device presents the incoming call reminder 10, if it detects that the user has performed an answering operation, in response to this answering operation, after the answering is successful, the terminal device can change the incoming call reminder 10 to the reminder during the call 20.
[0229] In some embodiments, the above reminder information supports user operations.
[0230] For example: Combining Figure 14 the lock screen interface 1200 shown in (1) in Figure 14 when the user performs an unlocking operation on the lock screen interface 1200, such as clicking on an area other than the in-call notification 1401 or swiping up from the bottom, in response to this operation, the terminal device can present Figure 14 the password interface 1410 described in (2) in
[0231] It can be understood that Figure 14 In (3), the example is that the last interface presented by the terminal device before locking the screen is the desktop. In other embodiments, if the last interface presented by the terminal device before locking the screen is other running interfaces other than the desktop, then after unlocking the lock screen interface 1200 shown in Figure 14 (1), the terminal device can also present the other running interface with the in - call reminder 20 displayed.
[0232] When the user performs an operation such as clicking on the in - call notification 1401 in the lock screen interface 1200 shown in Figure 14 (1), in response to this operation, the terminal can also present the password interface 1410 shown in Figure 14 (2). When the user unlocks the terminal device, in response to the user's unlocking operation, the terminal device can present the full - screen call interface 1430 shown in Figure 14 (4). Among them, the in - call reminder 20 is also displayed in the full - screen call interface 1430.
[0233] The user can realize the Figure 14 switching between the desktop 1420 shown in Figure 14 (3) and the full - screen call interface 1430 shown in Figure 14 (4) through the in - call reminder 20. For example, when the terminal device detects an operation such as the user clicking on the in - call reminder 20 shown in Figure 14 (3), in response to this operation, the terminal device can present the full - screen call interface 1430 (which can be used as an example of the third interface) shown in
[0234] Or, the user can also realize the Figure 14 switching between the lock screen interface 1200 shown in Figure 14 (1) and the full - screen call interface 1430 shown in Figure 14 (4) through the in - call reminder 20. For example: when the terminal device detects an operation such as the user clicking on the in - call reminder 20 shown in Figure 14 (1), in response to this operation, the terminal device can also present the password interface 1410 shown in Figure 14 (2) to remind the user to unlock the device. When the user unlocks successfully, in response to the user's unlocking, the terminal device can present the full - screen call interface 1430 shown in
[0235] Optionally, as shown in Figure 14 (4), the full - screen call interface 1430 can also include a button 1431. When the terminal device detects an operation such as the user clicking on the button 1431, in response to this operation, the terminal device can hide the full - screen call interface 1430. For example, the terminal device can return to the desktop 1420 shown in Figure 14 (3).
[0236] Taking the execution of an answer operation for an incoming call notification in the lock screen scenario as an example, similarly, when an answer operation is performed for an incoming call notification in the notification center scenario, it is also possible to implement the switching between the interface containing the incoming call notification and the full-screen call interface. For example, when the user performs an answer operation on the answer button in the incoming call notification 1221 shown in (3) of Figure 12 , in response to this operation, the terminal device can present the desktop 1420 shown in (3) of Figure 14 . Subsequently, through the in-call reminder 20, it is possible to implement the switching between the desktop 1420 shown in (3) of Figure 14 and the full-screen call interface 1430 shown in (4) of Figure 14 . The same applies to the incoming call notification 1801 shown in (1) of Figure 18 .
[0237] Taking the voice call scenario as an example above, optionally, the video call scenario is similar. In response to a user operation on the in-call reminder 20, the terminal device can also implement the switching between different interfaces, such as the video screen and the interface finally presented before the terminal device is locked, or the video screen and the interface containing the incoming call notification, etc.
[0238] The above examples take the in-call reminder 20 as an example. In other examples, the user can also use the incoming call reminder 10 to implement the display of a full-screen incoming call interface (such as a full-screen incoming call interface similar to the one containing the incoming call reminder 10 shown in (4) of Figure 14 ), a full-screen call interface (such as (4) of Figure 14 ), a full-screen answering interface (such as a full-screen in-progress answering interface similar to the one containing the incoming call reminder 10 shown in (2) of Figure 15 ), etc.
[0239] In this embodiment, when executing processes such as Figure 10 Figure 17 shown, in addition to presenting the incoming call notification to the notification display service, the VoIP management service can also present the reminder information of the above VoIP call to the notification display service. For example: In the incoming call notification stage described in Figure 10 , the VoIP management service can present the incoming call reminder 10 to the notification display service. Another example: In the answering scenario shown in Figure 13 , the VoIP application can also report an answer success event to the VoIP management service, and the VoIP management service can also present the incoming call reminder 10 updated to the in-call reminder 20 to the notification display service. Similarly, in the scenario shown in Figure 16 , the VoIP management service can also present the incoming call reminder 10 to the notification display service.
[0240] Exemplarily, Figure 19 The flowchart shows another call method provided by an embodiment of the present application. This method can be applied to a terminal device, and a first application with VoIP call function, such as the VoIP application described above, is installed on the terminal device. Exemplarily, as Figure 19 shown, the method includes the following steps:
[0241] S1901. When the first application is not running in the foreground of the terminal device, the terminal device wakes up the main process of the first application and sends a first call message received through the Push channel to the first application.
[0242] Among them, the first call message (such as Figure 10 the call message in the above process) is used to implement the first VoIP call. For the implementation of the first call message, reference can be made to Figure 10 the related implementation of the call message shown.
[0243] In some embodiments, the terminal device includes a Push end as described above. The Push end can be used to transmit call messages, and step S1901 can be executed by the Push end.
[0244] S1902. When, in response to the first call message, the first application does not execute the first incoming call notification within a preset duration, the terminal device keeps the main process of the first application alive within the preset duration.
[0245] Among them, the first incoming call notification is used to output a first incoming call notification message to remind the user. Exemplarily, the preset duration can be the specified time as described above, and the first incoming call notification can be as Figure 10 shown in Figure 10 the incoming call notification shown.
[0246] In some embodiments, the terminal device keeping the main process of the first application alive within the preset duration can be specifically implemented as the terminal device keeping the main process of the first application alive within the preset duration after the moment of waking up the main process of the first application, and freezing the main process of the first application at the moment when the preset duration is satisfied after the moment of waking up the main process of the first application.
[0247] In some embodiments, the terminal device includes a process resource management service as described above. The terminal device can keep the main process of the first application alive within the preset duration through the Push end and the process resource management service.
[0248] As a possible implementation, the Push side sends a first request to the process resource management service. The first request is used to instruct the process resource management service to keep the main process of the first application alive within a preset duration. In response to the first request, the process resource management service keeps the main process of the first application alive within the preset duration. Optionally, the first request can be implemented as one or more requests.
[0249] Taking the case where the first request is implemented as multiple requests as an example, the Push side can send a first keep-alive request to the process resource management service. The first keep-alive request is used to instruct the process resource management service to keep the main process of the first application alive, such as Figure 10 shown in step S1003. At the moment when the time from waking up the main process of the first application reaches the preset duration, the Push side sends a first freeze request to the process resource management service. The first freeze request is used to instruct the process resource management service to freeze the main process of the first application, such as Figure 10 shown in step S1006. Correspondingly, in response to the first keep-alive request and the first freeze request, the process resource management service keeps the main process of the first application alive within the preset duration, such as Figure 10 shown in step S1004 and step S1006.
[0250] In some embodiments, Figure 19 the method shown can further include step S1903.
[0251] S1903. When the first application executes the first incoming call notification within a preset duration in response to the first call message, the terminal device continues to keep the main process of the first application alive after the preset duration.
[0252] In some embodiments, the terminal device includes the Push side, the process resource management service, and the VoIP management service as described above. The VoIP management service can be used to receive the incoming call notification. For the introduction of the Push side and the process resource management service, reference can be made to the corresponding introduction described above. The terminal device can implement the operation of continuing to keep the main process of the first application alive after the preset duration through the Push side, the process resource management service, and the VoIP management service.
[0253] As a possible implementation, the Push side sends a first keep-alive request to the process resource management service. The first keep-alive request is used to instruct the process resource management service to keep the main process of the first application alive, such as Figure 10 shown in step S1003. In response to the first keep-alive request, the process resource management service keeps the main process of the first application alive, such as Figure 10 shown in step S1004. The first application executes the first incoming call notification to the VoIP management service within a preset duration in response to the first call message, such as Figure 10Step S1010 shown. In response to the first incoming call notification, the VoIP management service sends a second keep-alive request to the process resource management service, and the second keep-alive request is used to instruct the process resource management service to keep alive the main process of the first application as Figure 10 Step S1011 shown. At the moment when the time since waking up the main process of the first application meets a preset duration, the Push side sends a first freezing request to the process resource management service, and the first freezing request is used to instruct the process resource management service to freeze the main process of the first application, as Figure 10 Step S1006 shown. In response to the second keep-alive request and the first freezing request, the process resource management service continues to keep alive the main process of the first application within the preset duration and after the preset duration.
[0254] In some embodiments, the terminal device further includes the notification display service as described above, and the notification display service can be used to display the incoming call notification message of the first application. After the first application responds to the first call message and performs the first incoming call notification to the VoIP management service within a preset duration, in response to the first incoming call notification, the VoIP management service sends the first incoming call notification message of the first application to the notification display service, as Figure 10 Step S1013 shown. The notification display service displays the first incoming call notification message on the terminal device, as Figure 10 Step S1014 shown. Exemplarily, the first incoming call notification message can be like the incoming call notification message shown in Figure 12 .
[0255] In some embodiments, when the first application is running in the foreground of the terminal device, the first application responds to the second call message received through the long connection (such as the call message shown in Figure 17 ) and performs a second incoming call notification to the VoIP management service (such as the incoming call notification shown in Figure 17 ). In response to the second incoming call notification, the VoIP management service sends the second incoming call notification message of the first application to the notification display service (such as the incoming call notification shown in Figure 17 ), as Figure 17 Step S1708 shown. The notification display service displays the second incoming call notification message on the terminal device, as Figure 17 Step S1709 shown.
[0256] The above mainly introduced the solution provided by the embodiments of the present application from the perspective of methods. It can be understood that, in order to implement the above functions, the terminal device includes the corresponding hardware structures and / or software modules for executing each function. Combining the units and algorithm steps of each example described in the embodiments disclosed in the present application, the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the form of hardware or computer-driven hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the technical solution of the embodiments of the present application.
[0257] The embodiments of the present application can divide the functional modules of the terminal device according to the above method examples. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional module. It should be noted that the division of units in the embodiments of the present application is illustrative, only a logical functional division, and there can be other division methods in actual implementation.
[0258] As Figure 20 shown, it is a schematic structural diagram of a terminal device provided by an embodiment of the present application. The terminal device 2000 can be used to implement the methods executed by the terminal device recorded in each of the above method embodiments. Exemplarily, the terminal device 2000 may include a processing unit 2001, a communication unit 2002, and a display unit 2003.
[0259] Among them, the processing unit 2001 is used to support the terminal device 2000 to execute Figures 1 to 19 any one of the described processing functions, and the communication unit 2002 is used to support the terminal device 2000 to execute Figures 1 to 19 any one of the described communication functions. The display unit 2003 is used to support the terminal device 2000 to execute Figures 1 to 19 any one of the described display functions.
[0260] Optionally, Figure 20 the terminal device 2000 shown may further include a storage unit ( Figure 20 not shown in the figure), and the storage unit stores programs or instructions. When the processing unit 2001 executes the program or instructions, the Figure 20 terminal device 2000 shown can execute the methods described in the above method embodiments.
[0261] Figure 20 The technical effects of the terminal device 2000 shown can refer to the technical effects described in the above method embodiments, and will not be elaborated here.Figure 20 In the terminal device 2000 shown, the processing unit 2001 involved can be implemented by a processor or processor-related circuit components, and can be a processor or a processing module. The communication unit 2002 can be implemented by a transceiver or transceiver-related circuit components, and can be a transceiver or a transceiver module. The display unit 2003 can be implemented by components related to a display screen.
[0262] The embodiment of the present application also provides a chip system, as Figure 21 shown, the chip system includes at least one processor 2101 and at least one interface circuit 2102. The processor 2101 and the interface circuit 2102 can be interconnected by a line. For example, the interface circuit 2102 can be used to receive signals from other devices. Again, for example, the interface circuit 2102 can be used to send signals to other devices (such as the processor 2101). Exemplarily, the interface circuit 2102 can read instructions stored in a memory and send the instructions to the processor 2101. When the instructions are executed by the processor 2101, the terminal device can be made to execute each step performed by the terminal device in the above embodiment. Of course, the chip system can also include other discrete devices, and the embodiment of the present application does not make specific limitations thereto.
[0263] Optionally, the processor in the chip system can be one or more. The processor can be implemented by hardware or by software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented by software, the processor can be a general-purpose processor that implements by reading software code stored in a memory.
[0264] Optionally, the memory in the chip system can also be one or more. The memory can be integrated with the processor or can be separately provided from the processor, and the present application does not limit this. Exemplarily, the memory can be a non-transitory processor, such as a read-only memory ROM, which can be integrated with the processor on the same chip or can be separately provided on different chips. The present application does not make specific limitations on the type of the memory and the setting manner of the memory and the processor.
[0265] Exemplarily, the chip system may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a micro controller unit (MCU), a programmable logic device (PLD), or other integrated chips.
[0266] It should be understood that each step in the above method embodiments can be completed by the integrated logic circuit in the processor or the instructions in software form. The method steps disclosed in combination with the embodiments of the present application can be directly embodied as being executed and completed by the hardware processor, or executed and completed by the combination of the hardware and software modules in the processor.
[0267] The embodiments of the present application further provide a computer storage medium, in which computer instructions are stored. When the computer instructions run on the terminal device, the terminal device is enabled to execute the methods described in the above method embodiments.
[0268] The embodiments of the present application provide a computer program product, which includes: a computer program or instructions. When the computer program or instructions run on a computer, the computer is enabled to execute the methods described in the above method embodiments.
[0269] In addition, the embodiments of the present application further provide a device, which may specifically be a chip, a component or a module. The device may include a processor and a memory connected thereto; wherein, the memory is used to store computer execution instructions. When the device runs, the processor may execute the computer execution instructions stored in the memory, so that the device executes the methods in the above method embodiments.
[0270] Among them, the terminal device, the computer storage medium, the computer program product or the chip provided in this embodiment are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above, and will not be elaborated here.
[0271] Through the description of the above embodiments, those skilled in the art can understand that for the convenience and brevity of description, only the division of the above functional modules is used as an example. In actual applications, the above functions can be allocated to different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.
[0272] In several embodiments provided in the present application, it should be understood that the disclosed device and method can be implemented in other ways. The embodiments can be combined with each other or referred to each other without conflict. The device embodiments described above are only illustrative. For example, the division of modules or units is only a logical function division. In actual implementation, there can be other division methods. For example, multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection between each other can be through some interfaces. The indirect coupling or communication connection of the device or unit can be in electrical, mechanical or other forms.
[0273] The unit described as a separated component may or may not be physically separated. The component displayed as a unit may be a physical unit or multiple physical units, that is, it can be located in one place or distributed to multiple different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0274] In addition, in each embodiment of the present application, the functional units can be integrated in a processing unit, or each unit exists physically alone, or two or more units can be integrated in one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
[0275] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on such an understanding, the technical solution of the embodiments of the present application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. The software product is stored in a storage medium and includes several instructions to enable a device (which can be a single-chip microcomputer, a chip, etc.) or a processor to execute all or part of the steps of the methods of the embodiments of the present application. The foregoing storage medium includes: USB flash drive, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other various media that can store program codes.
[0276] The above content is only a specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of changes or substitutions, which should all be covered within the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims
1. A method for making a call, characterized in that: Applied to a terminal device, the method comprises: When the first application is not running in the foreground of the terminal device, the terminal device wakes up the main process of the first application and sends a first call message received through the Push channel to the first application, the first application has a VoIP call function, and the first call message is used to implement a first VoIP call; In response to the first call message, if the first application does not execute a first incoming call notification within a preset time period, the terminal device keeps the main process of the first application active within the preset time period, wherein the first incoming call notification is used to output a first incoming call notification message to remind the user.
2. The method according to claim 1, characterized in that The method further comprises: In response to the first call message, when the first application executes the first incoming call notification within the preset time period, the terminal device continues to keep the main process of the first application alive after the preset time period.
3. The method according to claim 1 or 2, characterized in that: The terminal device includes a Push terminal, and the Push terminal is used to transmit a call message; The terminal device wakes up the main process of the first application and sends the first call message received through the Push channel to the first application, including: The Push end wakes up the main process of the first application, and sends the first call message received through the Push channel to the first application.
4. The method according to claim 3, characterized in that The terminal device also includes a process resource management service, and the process resource management service is used to keep alive and freeze the main process of the first application; The terminal device keeping the main process of the first application alive within the preset time period includes: The Push end sends a first request to the process resource management service, where the first request is used to instruct the process resource management service to keep the main process of the first application alive within the preset time period; In response to the first request, the process resource management service keeps the main process of the first application alive within the preset duration.
5. The method according to claim 4, characterized in that The Push end sends a first request to the process resource management service, including: The Push end sends a first keep-alive request to the process resource management service, where the first keep-alive request is used to instruct the process resource management service to keep the main process of the first application alive; When the preset duration is met, the Push end sends a first freezing request to the process resource management service, where the first freezing request is used to instruct the process resource management service to freeze the main process of the first application; In response to the first request, the process resource management service keeps the main process of the first application alive within the preset time period, including: In response to the first keep-alive request and the first freeze request, the process resource management service keeps the main process of the first application alive within the preset time period.
6. The method according to claim 2, characterized in that The terminal device includes a Push terminal, a process resource management service and a VoIP management service. The Push terminal is used to transmit call messages. The process resource management service is used to keep alive and freeze the main process of the first application. The VoIP management service is used to receive incoming call notifications.
7. The method according to claim 6, characterized in that In response to the first call message, when the first application executes the first incoming call notification within the preset time period, the terminal device continues to keep the main process of the first application alive after the preset time period, including: The Push end sends a first keep-alive request to the process resource management service, where the first keep-alive request is used to instruct the process resource management service to keep the main process of the first application alive; In response to the first keep-alive request, the process resource management service keeps the main process of the first application alive; The first application executes the first incoming call notification to the VoIP management service within the preset time period in response to the first call message; In response to the first incoming call notification, the VoIP management service sends a second keep-alive request to the process resource management service, where the second keep-alive request is used to instruct the process resource management service to keep the main process of the first application alive; When the preset duration is met, the Push end sends a first freezing request to the process resource management service, where the first freezing request is used to instruct the process resource management service to freeze the main process of the first application; In response to the second keep-alive request and the first freeze request, the process resource management service continues to keep the main process of the first application alive within and after the preset time period.
8. The method according to claim 7, characterized in that The terminal device also includes a notification display service, and the notification display service is used to display an incoming call notification message of the first application; After the first application performs the first incoming call notification to the VoIP management service within the preset time period in response to the first call message, the method further includes: In response to the first incoming call notification, the VoIP management service sends a first incoming call notification message of the first application to the notification display service; The notification display service displays the first incoming call notification message on the terminal device.
9. The method according to claim 8, characterized in that The method further comprises: When the first application is running in the foreground of the terminal device, the first application performs a second incoming call notification to the VoIP management service in response to a second call message received through the persistent connection; In response to the second incoming call notification, the VoIP management service sends a second incoming call notification message of the first application to the notification display service; The notification display service displays the second incoming call notification message on the terminal device.
10. The method according to claim 8 or 9, characterized in that: The first incoming call notification message has the same format as the second incoming call notification message.
11. The method according to claim 10, characterized in that The first incoming call notification message and the second incoming call notification message are not displayed in full screen, and both the first incoming call notification message and the second incoming call notification message include caller information, an answer button, and a reject button.
12. The method according to claim 11, characterized in that The first incoming call notification message is displayed on a lock screen interface of the terminal device which is set with a lock screen password, and the first incoming call notification message supports a user to answer an incoming call of the first application without unlocking the terminal device.
13. The method according to any one of claims 8 to 12, characterized in that: The method further comprises: The notification display service displays a reminder message in the status bar of the terminal device, and the reminder message is used to remind that the incoming call type corresponding to the first incoming call notification message is a VoIP call.
14. A method for making a call, characterized in that: Applied to a terminal device, the method comprises: The terminal device displays a first interface, the first interface is a lock screen interface with a lock screen password, a first incoming call notification message of the first application is displayed on the first interface, the first application has a VoIP call function, the first incoming call notification message occupies a part of the first interface, and the first incoming call notification message includes a first answer button; The terminal device receives a triggering operation on the first answer button; In response to the triggering operation, without unlocking the terminal device, the terminal device connects the first VoIP call corresponding to the first incoming call notification message.
15. The method according to claim 14, characterized in that The first incoming call notification message is a voice incoming call notification message or a video incoming call notification message, and the first VoIP call is a voice call.
16. The method according to claim 14, characterized in that The first incoming call notification message is a video incoming call notification message, and the first incoming call notification message also includes a second answer button; the method further includes: The terminal device receives a triggering operation on the second answer button; In response to a triggering operation on the second answer button, the terminal device reminds the user to unlock the terminal device; When the terminal device is successfully unlocked, the terminal device connects the second VoIP call corresponding to the first incoming call notification message, and the second VoIP call is a video call.
17. The method according to any one of claims 14 to 16, characterized in that: After the terminal device connects the first VoIP call corresponding to the first incoming call notification message, the method further includes: The terminal device receives an unlocking operation on the terminal device; In response to the unlocking operation, the terminal device displays a second interface and a first reminder message, the second interface is the last interface displayed before the terminal device is locked, the first reminder message is located in the status bar, and the first reminder message is used to remind that the incoming call type of the first VoIP call is a VoIP call, and / or the progress of the first VoIP call.
18. The method according to claim 17, characterized in that After the terminal device displays the second interface and the first reminder message, the method further includes: The terminal device receives a triggering operation on the first reminder message; In response to the trigger operation, the terminal device displays a third interface and the first reminder message, and the third interface is a voice call interface displayed in full screen.
19. The method according to any one of claims 14 to 18, characterized in that After the terminal device connects the first VoIP call corresponding to the first incoming call notification message, the method further includes: The terminal device receives a triggering operation on the first incoming call notification message; In response to a triggering operation on the first incoming call notification message, the terminal device reminds the user to unlock the terminal device; When the terminal device is successfully unlocked, the terminal device displays a third interface and a first reminder message, the third interface is a full-screen voice call interface, the first reminder message is located in the status bar, and the first reminder message is used to remind that the incoming call type of the first VoIP call is a VoIP call, and / or the progress of the first VoIP call.
20. The method according to any one of claims 14 to 19, characterized in that The method further comprises: The terminal device displays a fourth interface, which is a running interface of the first application. A second incoming call notification message of the first application is displayed on the fourth interface, and the second incoming call notification message is displayed in a notification center.
21. A terminal device, characterized in that: include: A processor, a display screen and a memory, wherein the memory and the display screen are coupled to the processor, the memory is used to store program code, the program code includes instructions, and the processor reads the instructions from the memory so that the terminal device executes the method as described in any one of claims 1-13, or so that the terminal device executes the method as described in any one of claims 14-20.
22. A computer-readable storage medium, characterized in that: The computer-readable storage medium comprises a computer program, and when the computer program is executed on a terminal device, the terminal device executes the method according to any one of claims 1 to 13, or the terminal device executes the method according to any one of claims 14 to 20.
23. A computer program product, characterized in that The computer program product comprises: a computer program or instructions, which, when executed on a computer, causes the computer to execute the method according to any one of claims 1 to 13, or causes the computer to execute the method according to any one of claims 14 to 20.
Citation Information
Patent Citations
Voice of internet phone processing method and terminal
CN108809894A
Prefabricated data propagation method and device and electronic equipment
CN110661920A
Data transmission method and system
CN111615170A
Method for cooperatively waking up first electronic equipment and communication system
CN115278829A
Voice-over-internet protocol (VOIP) application platform
US20130343373A1
