CN115243206B

CN115243206B - Voice call establishing method and electronic equipment

Info

Publication number: CN115243206B
Application number: CN202211150559.3A
Authority: CN
Inventors: 李海波; 赵钊; 姚东强
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2022-09-21
Filing date: 2022-09-21
Publication date: 2023-01-31
Anticipated expiration: 2042-09-21
Also published as: CN115243206A

Abstract

The application provides a voice call establishing method and electronic equipment. The method comprises the following steps: after receiving an invitation request of a voice call sent by calling equipment, called equipment sends a response of successful connection aiming at the invitation request to the calling equipment and starts timing; if the timing time reaches a first duration, the called equipment does not receive a first confirmation message returned by the calling equipment for response of successful connection, and sends a connection notification based on a first private protocol to the calling equipment, wherein the connection notification is used for indicating that the called equipment is connected; the called device receives a second confirmation message which is returned by the calling device aiming at the connection notification and is based on the first private protocol, confirms that the voice call with the calling device is established, and adjusts the local call state of the calling device to be connected after the calling device sends the second confirmation message. Therefore, the called party of the voice call informs the calling party of the connection through the private protocol, so that the calling party adjusts the call state to the connected state, and the call completing rate of the voice call ticket is reduced.

Description

Voice call establishing method and electronic equipment

Technical Field

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

Background

Voice calls are one of the main functions of electronic devices. Before voice communication, the electronic devices of both parties need to establish communication connection through the network, and the signaling interaction process before communication is completed. In a scene of network abnormality, after a called party connects a call invitation of a calling party, the called party cannot hear the sound of the calling party, the calling party displays that the call is not connected, but the calling party can hear the sound of the called party, so that the phenomenon of single call is caused, and the experience of a user is poor.

Disclosure of Invention

In order to solve the technical problem, the application provides a voice call establishing method and electronic equipment, wherein a called party notifies the calling party of being connected through a private protocol under the condition that a confirmation message of the calling party is not received within a certain time after a response of successful connection is sent, so that the calling party adjusts the call state to be connected, two parties of the call can normally call, the call rate of a voice call ticket is reduced, and the voice call experience of a user is improved.

In a first aspect, the present application provides a voice call establishment method. The method is applied to the electronic equipment. The method comprises the following steps: after receiving an invitation request of a voice call sent by calling equipment, called equipment sends a response of successful connection aiming at the invitation request to the calling equipment and starts timing; if the timing time reaches the first duration, the called equipment does not receive a first confirmation message returned by the calling equipment for successful response of connection, and sends a connection notification based on a first private protocol to the calling equipment, wherein the connection notification is used for indicating that the called equipment is connected; the called device receives a second confirmation message which is returned by the calling device aiming at the connection notification and is based on the first private protocol, confirms that the voice call with the calling device is established, and adjusts the local call state of the calling device to be connected after the calling device sends the second confirmation message. Therefore, under the condition that the called party of the voice call does not receive the confirmation message of the calling party within a certain time after sending the response of successful connection, the called party is informed of the connection through the private protocol, so that the calling party adjusts the call state to be connected, both parties of the call can normally communicate, the call rate of the voice call is reduced, and the voice call experience of the user is improved.

According to a first aspect, the first private protocol is the private real time transport control protocol RTCP protocol.

According to the first aspect, the connection notification is an RTCP packet of a source description type, and the CNAME field in the RTCP packet is used to store identification information that the called device has been connected.

According to the first aspect, the connection notification is an RTCP packet of a source description type, i.e., 202 type, and a PRIV field in the RTCP packet is used to store identification information that the called device has been connected; alternatively, the connection notification is an RTCP packet of type 204.

According to the first aspect, the first period of time is greater than 0 and less than or equal to 3 seconds.

According to a first aspect, the first duration is 0.

According to the first aspect, the first duration is a preset multiple of a second duration, and the second duration is a duration from a time when the called device sends a successful response to the time when the called device receives the first acknowledgement message when the communication network between the calling device and the called device is normal.

According to a first aspect, further comprising: if the timing time does not reach the first duration, the called device receives a first confirmation message returned by the calling device aiming at the successful response of the connection, stops timing and confirms that the voice call with the calling device is established.

In a second aspect, the present application provides a method for establishing a voice call, including: the calling equipment sends an invitation request of voice call to the called equipment; the method comprises the steps that a calling device receives a connection notification based on a first private protocol, wherein the connection notification is sent by a called device and used for indicating that the called device is connected; the calling device adjusts the local call state to be connected according to the connection notification, and sends a second confirmation message based on the first private protocol to the called device, wherein the second confirmation message is specific to the connection notification, so that the called device confirms that the voice call between the called device and the calling device is established according to the second confirmation message. Therefore, the calling party of the voice call does not receive the successful response of the called party in a certain time, so that under the condition that the calling party does not return a confirmation message aiming at the successful response of the call to the called party, the calling party receives the notification that the called party is connected through the private protocol, the calling party adjusts the call state to be connected according to the notification, the two parties of the call can normally call, the call rate of the voice call ticket is reduced, and the voice call experience of the user is improved.

According to a second aspect, the first private protocol is the private real-time transport control protocol RTCP protocol.

According to a second aspect, the second acknowledgement message is an RTCP packet of the source description type, and the CNAME field in the RTCP packet is used to store information identifying the acknowledgement.

According to a second aspect, the second acknowledgement message is an RTCP packet of the source description type, and the PRIV field in the RTCP packet is used to store information identifying the acknowledgement.

In a third aspect, the present application provides a voice call establishing method, including: the calling equipment sends an invitation request of voice call to the called equipment; the called equipment receives the invitation request, sends a response of successful connection aiming at the invitation request to the calling equipment and starts timing; if the timing time reaches the first duration, the called equipment does not receive a first confirmation message returned by the calling equipment for successful response of connection, and sends a connection notification based on a first private protocol to the calling equipment, wherein the connection notification is used for indicating that the called equipment is connected; the calling equipment receives the connection notification, adjusts the local call state to be connected according to the connection notification, and sends a second confirmation message based on the first private protocol for the connection notification to the called equipment; the called device receives the second confirmation message, and confirms that the voice call with the calling device is established.

In a fourth aspect, the present application provides a method for hanging up a voice call, including: the first device hangs up the voice call with the second device; the first equipment sends a call hang-up notice to the second equipment and starts timing, wherein the call hang-up notice is used for indicating that the first equipment hangs up the call; if the timing time reaches the first time length, the first equipment does not receive a third confirmation message returned by the second equipment aiming at the telephone hang-up notification, and sends a first notification based on a first private protocol to the second equipment, wherein the first notification is used for indicating that the first equipment has hung up the call; and the first equipment receives a fourth confirmation message which is returned by the second equipment aiming at the first notification and is based on the first private protocol, and confirms that the voice call between the first equipment and the second equipment is hung up, wherein the fourth confirmation message is sent after the second equipment receives the first notification and adjusts the local call state into the hung up state according to the first notification.

In a fifth aspect, the present application provides a voice call canceling method, including: the first equipment cancels the voice call with the second equipment; the first equipment sends a telephone cancellation notice to the second equipment and starts timing, wherein the telephone cancellation notice is used for indicating that the first equipment cancels the call; if the timing time reaches the first time length, the first equipment does not receive a fifth confirmation message returned by the second equipment for the telephone cancellation notification, and sends a third notification based on the first private protocol to the second equipment, wherein the third notification is used for indicating that the first equipment cancels the call; and the first equipment receives a sixth confirmation message which is based on the first private protocol and returned by the second equipment aiming at the third notification, confirms that the voice call with the second equipment is cancelled, and the sixth confirmation message is sent after the second equipment receives the third notification and adjusts the local call state to be cancelled according to the third notification.

In a sixth aspect, the present application provides an electronic device, comprising: a memory and a processor, the memory coupled with the processor; the memory stores program instructions that, when executed by the processor, cause the electronic device to perform the voice call setup method of any of the first aspects or to perform the voice call setup method of any of the second aspects.

In a seventh aspect, the present application provides a computer-readable storage medium, which includes a computer program and when the computer program runs on an electronic device, causes the electronic device to execute the voice call establishment method in any one of the first aspect described above, or execute the voice call establishment method in any one of the second aspect.

In an eighth aspect, the present application provides an electronic device, comprising: a memory and a processor, the memory coupled to the processor; the memory stores program instructions that, when executed by the processor, cause the electronic device to perform the voice call hanging-up method of any one of the fourth aspects.

In a ninth aspect, the present application provides a computer-readable storage medium, which includes a computer program, and when the computer program runs on an electronic device, the computer program causes the electronic device to execute the voice call hang-up method of any one of the foregoing fourth aspects.

In a tenth aspect, the present application provides an electronic device comprising: a memory and a processor, the memory coupled with the processor; the memory stores program instructions that, when executed by the processor, cause the electronic device to perform the voice call cancellation method of any one of the fifth aspects.

In an eleventh aspect, the present application provides a computer-readable storage medium including a computer program, which, when run on an electronic device, causes the electronic device to execute the voice call cancellation method of any one of the foregoing fifth aspects.

Drawings

Fig. 1 is a schematic structural diagram of an exemplary electronic device 100;

fig. 2 is a block diagram illustrating a software structure of the electronic device 100 according to the embodiment of the present application;

FIG. 3 is a schematic diagram of an exemplary voice call setup process;

fig. 4 is another schematic diagram illustrating a voice call setup procedure;

FIG. 5 is a diagram illustrating an example of a data structure of a power-on notification;

fig. 6 is a schematic flowchart of an exemplary called device side in the voice call setup process;

fig. 7 is another exemplary flow chart of the called device side in the voice call setup process;

fig. 8 is a schematic flowchart of an exemplary flow diagram of the calling device side in the voice call setup process;

fig. 9 is a flow diagram illustrating a voice call hang-up process;

FIG. 10 is another flow chart diagram illustrating a voice call hang-up process;

fig. 11 is a flowchart illustrating a voice call cancellation procedure;

fig. 12 is another flowchart illustrating a voice call cancellation process.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone.

The terms "first" and "second," and the like, in the description and in the claims of the embodiments of the present application are used for distinguishing between different objects and not for describing a particular order of the objects. For example, the first target object and the second target object, etc. are specific sequences for distinguishing different target objects, rather than describing target objects.

In the embodiments of the present application, words such as "exemplary" or "for example" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

In the description of the embodiments of the present application, the meaning of "a plurality" means two or more unless otherwise specified. For example, a plurality of processing units refers to two or more processing units; a plurality of systems refers to two or more systems.

The embodiment of the application provides a voice call establishing method, which can reduce the call ticket passing rate and improve the call experience of a user.

The voice call establishing method in the embodiment of the application can be applied to electronic equipment, and the electronic equipment can be a mobile phone, other electronic equipment with a call function and the like

The structure of the electronic device in this embodiment may be as shown in fig. 1.

Fig. 1 is a schematic structural diagram of an exemplary electronic device 100. It should be understood that the electronic device 100 shown in fig. 1 is only one example of an electronic device, and that the electronic device 100 may have more or fewer components than shown in the figures, may combine two or more components, or may have a different configuration of components. The various components shown in fig. 1 may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.

Referring to fig. 1, an electronic device 100 may include: the mobile terminal includes a processor 110, an internal memory 121, a Universal Serial Bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, an indicator 192, a camera 193, and the like.

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

The controller may be, among other things, a neural center and a command center of the electronic device 100. The controller can generate an operation control signal according to the instruction operation code and the timing signal to complete the control of instruction fetching and instruction execution.

A memory may also be provided in processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory.

The wireless communication function of the electronic device 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 100 may be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed as a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution including 2G/3G/4G/5G wireless communication applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a Low Noise Amplifier (LNA), and the like. The mobile communication module 150 may receive the electromagnetic wave from the antenna 1, filter, amplify, etc. the received electromagnetic wave, and transmit the electromagnetic wave to the modem processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 1 to radiate the electromagnetic wave. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the same device as at least some of the modules of the processor 110.

The Modem processor may include one or more modems (modems) that may include modulators and demodulators. The modulator is used for modulating a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then passes the demodulated low frequency baseband signal to a baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional modules, independent of the processor 110.

The software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. In the embodiment of the present application, an Android (Android) system with a layered architecture is taken as an example to exemplarily illustrate a software structure of the electronic device 100.

Fig. 2 is a block diagram illustrating a software structure of the electronic device 100 according to the embodiment of the present application.

The layered architecture of the electronic device 100 divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android system may include an application layer, an application framework layer, a kernel layer, and the like.

The application layer may include a series of application packages.

As shown in fig. 2, the application packages may include camera, calendar, map, WLAN, music, short message, gallery, call, navigation, bluetooth, video, etc. applications.

Wherein the call application is used to implement a voice call function.

The application framework layer provides an Application Programming Interface (API) and a programming framework for the application program of the application layer. The application framework layer includes a number of predefined functions.

As shown in fig. 2, the application framework layer may include a resource manager, a telephony manager, and the like.

The resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files, and the like.

The phone manager is used to provide communication functions for the electronic device 100. Such as management of call status (including on, off, etc.).

As shown in FIG. 2, the kernel layer may include modules such as a display driver, a Wi-Fi driver, a Bluetooth driver, an audio driver, a sensor driver, and the like.

As shown in fig. 2, the hardware abstraction layer may include a modem, and the modem may include a first voice call setup module and a second voice call setup module therein. The first voice call establishing module is used for executing the method of the calling equipment side in the voice call establishing method embodiment of the application. The second voice call establishing module is used for executing the method of the called device side in the voice call establishing method embodiment of the application.

When the electronic device 100 is used as a calling device in a voice call, the electronic device 100 uses the first voice call establishment module to interact with the second voice call establishment module in the called device, so as to complete the establishment process of the voice call.

When the electronic device 100 is used as a called device in a voice call, the electronic device 100 uses the second voice call establishment module to interact with the first voice call establishment module in the calling device, and completes the establishment process of the voice call.

It is to be understood that the layers in the software structure shown in fig. 2 and the components included in each layer do not constitute a specific limitation of the electronic device 100. In other embodiments of the present application, electronic device 100 may include more or fewer layers than those shown, and may include more or fewer components in each layer, which is not limited in this application.

The present application will be described in detail below with reference to examples.

Fig. 3 is a schematic diagram illustrating an exemplary voice call setup procedure. Referring to fig. 3, in an embodiment of the present application, a voice call setup procedure between a calling device and a called device may include the following steps:

s301, the calling device sends an invitation request of voice call to the called device through the network.

The two parties to be talking create a Session through SIP (Session Initiation Protocol). The calling device initiating the call firstly sends an invitation request of the voice call to the called device through the network, and the invitation request is an invite message.

S302, the called device returns a call test message to the calling device through the network.

In this step, the called device sends the trial call message to the network, and the network forwards the trial call message to the calling device.

The trying call message is a 100 trying message.

S303, the called device sends 183 a message to the calling device through the network, wherein the message does not contain PEM (P-Early-Media).

At this point the network is normal and so the 183 message is successful in reaching the calling device.

S304, the called device sends 180 messages to the calling device through the network, and at the moment, the network is abnormal, so that the 180 messages are not forwarded to the calling device by the network.

S305, the called device sends a completion success response 200 OK message aiming at the invitation request to the calling device through the network, and the network is abnormal, so that the network does not forward the completion success response 200 OK message to the calling device.

The information in steps S301 to S305 is transmitted through an IMS (IP Multimedia system) message dedicated channel QCI5 of Voice over Long-Term Evolution (VOLTE) bearer.

And S306, the called device starts timing.

In this step, the called device may start a timer, and the timing time of the timer is T.

S307, the called device sends an RTP (Real-time Transport Protocol) voice packet to the calling device through the network.

In this step, the called device sends the RTP voice packet to the network, and the network forwards the RTP voice packet to the calling device.

Wherein, the RTP voice packet is transmitted through a voice channel QCI 1.

S308, the calling device sends an RTCP (RTP Control Protocol, real-time transport Control Protocol) reception report to the called device through the network.

Here, the RTCP reception report is transmitted through the voice channel QCI 1.

S309, the called device sends an RTCP sending report to the calling device through the network.

Here, the RTCP transmission report is transmitted through the voice channel QCI 1.

S310, the called device determines whether the timing time reaches T and whether an Acknowledgement (ACK) message returned by the calling device for the successful response of connection is received, and if the timing time reaches T and the acknowledgement message returned by the calling device for the successful response of connection is not received, executes step S311. And if the timing time does not reach T and a confirmation message returned by the calling equipment for successful response of connection is received, stopping timing and confirming that the voice call with the calling equipment is established.

Where T may be set to a value less than or equal to 3 seconds.

In practical applications, the value of T may be set to be about n times (e.g., n = 3) the time consumed by normal SIP messages for interaction. Of course, the value of T may also be dynamically adjusted under different core networks. At this time, the communication device, for example, a mobile phone may obtain the value of T by multiplying the time consumed for normal transmission of 200 ok in the specific network learned by itself (i.e., the time consumed from sending the 200 ok message to receiving the ACK message corresponding to the 200 ok message) by the corresponding multiple n. The value of T may also be adjusted according to the congestion level of the uplink and downlink transmitted data.

S311, the called device sends a connection notification based on the RTCP protocol to the calling device through the network, the connection notification indicating that the called device is connected.

The on notification in this step is transmitted through the voice channel QCI 1.

In one example, the on notification may be an SDES (Source Description) type RTCP packet.

In one example, in case of an RTCP packet in which the turn-on notification is of SDES type, the CNAME field in the RTCP packet may be used to store identification information that the called device has been turned on.

Fig. 5 is a diagram illustrating an example of a data structure of the switch-on notification. Referring to fig. 5 (a), when the CNAME field in the RTCP packet has a value of 1, it indicates that the called device is turned on.

It should be noted that, in other embodiments, it may be defined that the called device is already connected when the value of the CNAME field is other values, for example, it may be defined that the called device is already connected when the value of the CNAME field is 0.

In another example, in case of an RTCP packet in which the connection notification is of SDES type, the PRIV field in the RTCP packet may be used to store identification information that the called device has been connected. Referring to fig. 5 (b), when the value of the PRIV field in the RTCP packet is 8, it indicates that the called device is turned on.

It should be noted that, in other embodiments, it may be defined that the called device is turned on when the value of the PRIV field is another value.

In one example, the on notification may also be a 204 (APP) type RTCP packet. In this case, a custom field in a 204 (APP) type RTCP packet may be used to identify that the called device is on.

S312, the calling device sends an acknowledgement message based on RTCP protocol for the connection notification to the called device through the network.

The acknowledgement message in this step is transmitted through the voice channel QCI 1.

Through steps S311 and S312, even if the IMS message dedicated channel QCI5 of the network is abnormal, the calling device can still know that the called device is connected, so that the local call state can be adjusted to be connected based on this, and the voice of the local terminal of the calling device is allowed to be sent to the network, so that both the calling party and the called party can connect the call, and the occurrence of the single-pass condition that only one party is connected is avoided.

And S313, the calling equipment adjusts the local call state of the calling equipment to be connected and allows the voice of the local terminal to be sent to the network.

Therefore, the calling device and the called device can normally transmit the voice RTP packet, and the voice communication between the two parties is realized.

In the above embodiment, the operation performed by the calling device is performed by the first voice call setup module in the calling device, and the operation performed by the called device is performed by the second voice call setup module in the called device.

Fig. 4 is another schematic diagram illustrating a voice call setup procedure. Referring to fig. 4, in an embodiment of the present application, a voice call setup procedure between a calling device and a called device may include the following steps:

s401, the calling device sends an invitation request of voice call to the called device through the network.

The two devices create a session through SIP. The calling device initiating the call firstly sends an invitation request of the voice call to the called device through the network, and the invitation request is an invite message.

S402, the called device returns the call trying information to the calling device through the network.

The called device sends the trial call message to the network, and the network forwards the trial call message to the calling device.

The trying call message is a 100 trying message.

S403, the called device sends 183 a message to the calling device through the network, wherein the message does not contain PEM.

S404, the called device sends 180 information to the calling device through the network, and the network is abnormal, so that the network does not forward the notification information 180 information for playing the ring back tone to the calling device.

S405, the called device sends a connection success response 200 OK message aiming at the invitation request to the calling device through the network, and the network is abnormal, so that the network does not forward the connection success response 200 OK message to the calling device.

The information in steps S401 to S405 is transmitted through the IMS message dedicated channel QCI5 of VOLTE.

S406, the called device sends a connection notice based on the RTCP protocol to the calling device through the network, wherein the connection notice is used for indicating that the called device is connected.

In this embodiment, after the called device sends a successful connection response 200 OK message to the calling device, it immediately sends a connection notification based on the RTCP protocol to the calling device. Thus, if the network is normal, the calling device can successfully receive the connection success response 200 OK message, adjust the local call state to be connected based on the connection success response 200 OK message, and allow the voice to be sent to the network. If the network is abnormal, the calling device cannot successfully receive the connection success response 200 OK message, the calling device can also receive a connection notification indicating that the called device is connected through a private protocol RTCP, adjust the local call state to be connected based on the connection notification, and allow the voice to be sent to the network.

In addition, because the connection notification based on the RTCP protocol is sent immediately after the 200 OK message of the successful connection response is sent, under the abnormal condition of the network, the calling equipment and the called equipment can quickly enter a normal conversation state, the waiting time of the calling equipment and the called equipment is shortened, and the user experience is improved.

S407, the calling device sends a confirmation message based on the RTCP protocol for the connection notification to the called device through the network.

Through steps S406 and S407, even if the IMS message dedicated channel QCI5 of the network is abnormal, the calling device can still know that the called device is connected, so that the local call state can be adjusted to be connected based on this, and the voice of the calling device itself is allowed to be sent to the network, so that both the calling party and the called party can connect the call, and the single-pass situation in which only one party is connected is avoided.

S408, the calling device adjusts the local call state of the calling device to be connected and allows the voice of the local terminal to be sent to the network.

In the above embodiment, the operation performed by the calling device is performed by a first voice call establishment module in the calling device, and the operation performed by the called device is performed by a second voice call establishment module in the called device.

The voice call establishment procedure in the embodiment of the present application is described below with respect to a single side of a calling device and a single side of a called device.

Fig. 6 is a schematic flowchart of an exemplary procedure of the called device side in the voice call setup process. Referring to fig. 6, in the embodiment of the present application, a process of a called device side in a voice call setup process may include the following steps:

s601, after receiving the invitation request of the voice call sent by the calling equipment, the called equipment sends a response of successful connection aiming at the invitation request to the calling equipment and starts timing.

S602, if the timing time reaches a first duration, the called device does not receive a first confirmation message returned by the calling device for the successful response of the connection, and a connection notification based on a first private protocol is sent to the calling device and used for indicating that the called device is connected.

S603, the called device receives a second confirmation message which is returned by the calling device aiming at the connection notification and is based on the first private protocol, confirms that the voice call with the calling device is established, and adjusts the local call state of the calling device to be connected after the calling device sends the second confirmation message.

Wherein the first private protocol may be the RTCP protocol described previously.

Wherein the first time period may be greater than 0 and less than or equal to 3 seconds.

Fig. 7 is another exemplary flowchart of the called device side in the voice call setup process. Referring to fig. 7, in the embodiment of the present application, a flow of a called device side in a voice call setup process may include the following steps:

and S701, after receiving the invitation request of the voice call sent by the calling equipment, the called equipment sends a response of successful connection aiming at the invitation request to the calling equipment.

S702, the called device sends a connection notification based on a first private protocol to the calling device, and the connection notification is used for indicating that the called device is connected.

S703, the called device receives a second confirmation message based on the first private protocol and returned by the calling device for the connection notification, confirms that the voice call with the calling device is established, and adjusts the local call state of the calling device to be connected after the calling device sends the second confirmation message.

Fig. 8 is a schematic flowchart of an exemplary procedure of the calling device during the voice call setup procedure. Referring to fig. 8, in the embodiment of the present application, a flow of a calling device side in a voice call setup process may include the following steps:

s801, the calling device sends an invitation request of voice communication to the called device.

S802, the calling device receives a connection notification based on a first private protocol, which is sent by the called device and used for indicating that the called device is connected.

And S803, the calling device adjusts the local call state to be connected according to the connection notification, and sends a second confirmation message based on the first private protocol to the called device, so that the called device confirms that the voice call with the calling device is established according to the second confirmation message.

The embodiment of the application also provides a voice call hang-up method.

Fig. 9 is a flow chart illustrating an exemplary voice call hang-up procedure. Referring to fig. 9, in the embodiment of the present application, the voice call hang-up process may include the following steps:

and S901, the first equipment hangs up the voice call with the second equipment.

In one example, the first device may be a calling device and the first device may be a called device.

In another example, the first device may be a called device and the first device may be a calling device.

S902, the first device sends a call hang-up notification to the second device, and starts timing, wherein the call hang-up notification is used for indicating that the first device has hung up the call.

And S903, if the timing time reaches the first time length, the first device does not receive a third confirmation message returned by the second device aiming at the telephone hang-up notification, and sends a first notification based on the first private protocol to the second device, wherein the first notification is used for indicating that the first device has hung up the call.

The data structure of the first notification may be the same as the data structure of the connection notification based on the RTCP protocol, for example, a value in a CNAME field or a PRIV field in an RTCP packet of SDES type may be used to identify that the first device has hung up the call, and is not described herein again. The first notification may also be an RTCP packet of the 204 (APP) type. In this case, a custom field in a 204 (APP) type RTCP packet may be used to identify that the first device has hung up.

Wherein the first proprietary protocol may be RTCP protocol.

The first notification in this step is transmitted over the voice channel QCI 1.

And S904, the first device receives a fourth confirmation message which is returned by the second device aiming at the first notification and is based on the first private protocol, and confirms that the voice call between the first device and the second device is hung up, wherein the fourth confirmation message is sent after the second device receives the first notification and adjusts the local call state to be hung up according to the first notification.

Through the embodiment, when the network is abnormal, under the condition that the special channel QCI5 for the IMS message can not transmit the call hang-up notice, the information of the call hang-up can be transmitted to the opposite voice call terminal through the voice channel QCI1 through the private protocol, so that the opposite voice call terminal can timely know the information of the call hang-up of the other end of the call, the call state of the terminal is timely modified to be the call hang-up, the single-pass condition that one party is hung up and the other party is still in a connected state is avoided, and the user experience is improved.

Fig. 10 is another flow chart illustrating a voice call hang-up procedure. Referring to fig. 10, in the embodiment of the present application, the voice call hang-up process may include the following steps:

and S1001, hanging up the voice call with the second equipment by the first equipment.

S1002, the first device sends a call hang-up notification to the second device, wherein the call hang-up notification is used for indicating that the first device hangs up the call.

S1003, the first device sends a first notification based on the first private protocol to the second device, wherein the first notification is used for indicating that the first device hangs up the call.

The data structure of the first notification may be the same as the data structure of the connection notification based on the RTCP protocol, for example, the value in the CNAME field or the PRIV field in the RTCP packet of the SDES type may be used to identify that the first device has hung up the call, which is not described herein again.

Wherein the first private protocol may be RTCP protocol.

In this embodiment, the first device sends the first notification based on the first private protocol to the second device immediately after sending the call hangup notification, so that the opposite device hanging up the call device can quickly hang up the call under the abnormal network condition, and the waiting time of the opposite device is shortened, thereby improving the user experience.

And S1004, the first device receives a fourth confirmation message which is returned by the second device aiming at the first notification and is based on the first private protocol, and confirms that the voice call between the first device and the second device is hung up, wherein the fourth confirmation message is sent after the second device receives the first notification and adjusts the local call state to be hung up according to the first notification.

The embodiment of the application also provides a voice call cancelling method.

Fig. 11 is a flowchart illustrating a voice call cancellation procedure. Referring to fig. 11, in the embodiment of the present application, the voice call hang-up process may include the following steps:

s1101, the first device cancels the voice call with the second device.

And actively canceling the voice communication with the second equipment in the process of calling the second equipment by the first equipment.

And S1102, the first equipment sends a telephone cancellation notice to the second equipment, and starts timing, wherein the telephone cancellation notice is used for indicating that the first equipment cancels the call.

S1103, if the time reaches the first duration, the first device does not receive a fifth acknowledgement message returned by the second device for the phone cancel notification, and sends a third notification based on the first private protocol to the second device, where the third notification is used to indicate that the first device has cancelled the call.

The data structure of the third notification may be the same as the data structure of the connection notification based on the RTCP protocol, for example, a value in a CNAME field or a PRIV field in an SDES type RTCP packet may be used to identify that the first device has cancelled the call, and details thereof are not repeated herein. The third notification may also be a 204 (APP) type RTCP packet. In this case, a custom field in a 204 (APP) type RTCP packet may be used to identify that the first device has cancelled the call.

Wherein the first private protocol may be RTCP protocol.

The third notification in this step is transmitted through the voice channel QCI 1.

And S1104, the first device receives a sixth acknowledgement message based on the first private protocol and returned by the second device for the third notification, and acknowledges that the voice call with the second device is cancelled, wherein the sixth acknowledgement message is sent after the second device receives the third notification and adjusts the local call state to be cancelled according to the third notification.

Through the embodiment, when the network is abnormal and the IMS message special channel QCI5 can not transmit the telephone cancellation notice, the information of telephone cancellation can be transmitted to the voice call opposite terminal through the voice channel QCI1 through the private protocol, so that the voice call opposite terminal can timely know the information of canceling the call with the other terminal of the call, the call state of the terminal is timely modified to be cancelled, the situation that a calling party cancels the voice call and a called party rings is avoided, and the user experience is improved.

Fig. 12 is another flowchart illustrating a voice call cancellation process. Referring to fig. 12, in the embodiment of the present application, the voice call hang-up process may include the following steps:

and S1201, the first equipment cancels the voice call with the second equipment.

And S1202, the first equipment sends a telephone cancellation notice to the second equipment, wherein the telephone cancellation notice is used for indicating that the first equipment cancels the call.

S1203, the first device sends a third notification based on the first private protocol to the second device, where the third notification is used to indicate that the first device has cancelled the call.

The data structure of the third notification may be the same as the data structure of the connection notification based on the RTCP protocol, for example, the value in the CNAME field or the PRIV field in the RTCP packet of the SDES type may be used to identify that the first device has cancelled the call, which is not described herein again.

Wherein the first private protocol may be RTCP protocol.

In this embodiment, the first device sends the third notification based on the first private protocol to the second device immediately after sending the phone cancellation notification, so that the opposite device that cancels the call device can cancel the call quickly under the abnormal network condition, and the waiting time of the opposite device is shortened, thereby improving the user experience.

And S1204, the first device receives a sixth acknowledgement message based on the first private protocol returned by the second device for the third notification, and acknowledges that the voice call with the second device is cancelled, wherein the sixth acknowledgement message is sent after the second device receives the third notification and adjusts the local call state to be cancelled according to the third notification.

An embodiment of the present application further provides an electronic device, where the electronic device includes a memory and a processor, the memory is coupled to the processor, and the memory stores program instructions, and when the program instructions are executed by the processor, the electronic device is enabled to implement the voice call establishment method executed by the electronic device.

It will be appreciated that the electronic device, in order to implement the above-described functions, comprises corresponding hardware and/or software modules for performing the respective functions. The present application is capable of being implemented in hardware or a combination of hardware and computer software in conjunction with the exemplary algorithm steps described in connection with the embodiments disclosed herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, with the embodiment described in connection with the particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The present embodiment further provides a computer storage medium, where computer instructions are stored in the computer storage medium, and when the computer instructions are run on an electronic device, the electronic device is caused to execute the relevant method steps to implement the voice call establishment method in the foregoing embodiment.

The embodiment also provides a computer program product, which when running on a computer, causes the computer to execute the relevant steps to implement the voice call establishment method in the embodiment.

In addition, the embodiment of the present application further provides an apparatus, which may specifically be a chip, a component or a module, and the apparatus may include a processor and a memory connected to each other; the memory is used for storing computer execution instructions, and when the device runs, the processor can execute the computer execution instructions stored in the memory, so that the chip can execute the voice call establishment method in the above method embodiments.

The electronic device, the computer storage medium, the computer program product, or the chip provided in this embodiment are all configured to execute the corresponding method provided above, so that the beneficial effects achieved by the electronic device, the computer storage medium, the computer program product, or the chip may refer to the beneficial effects in the corresponding method provided above, and are not described herein again.

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

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

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

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

Any of the various embodiments of the present application, as well as any of the same embodiments, can be freely combined. Any combination of the above is within the scope of the present application.

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

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the present embodiments are not limited to those precise embodiments, which are intended to be illustrative rather than restrictive, and that various changes and modifications may be effected therein by one skilled in the art without departing from the scope of the appended claims.

The steps of a method or algorithm described in connection with the disclosure of the embodiments of the application may be embodied in hardware or in software instructions executed by a processor. The software instructions may be comprised of corresponding software modules that may be stored in Random Access Memory (RAM), flash Memory, read Only Memory (ROM), erasable Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), registers, a hard disk, a removable disk, a compact disc Read Only Memory (CD-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC.

Those skilled in the art will recognize that, in one or more of the examples described above, the functions described in the embodiments of the present application may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A voice call establishing method is characterized by comprising the following steps:

after receiving an invitation request of a voice call sent by calling equipment, called equipment sends a response of successful connection aiming at the invitation request to the calling equipment and starts timing;

if the timing time reaches a first time length, the called device does not receive a first confirmation message returned by the calling device aiming at the successful response of the connection, and sends a connection notice based on a first private protocol to the calling device, wherein the connection notice is used for indicating that the called device is connected, and the first private protocol is a private real-time transport control protocol (RTCP);

and the called equipment receives a second confirmation message which is returned by the calling equipment aiming at the connection notification and is based on the first private protocol, confirms that the voice call between the called equipment and the calling equipment is established, and adjusts the local call state of the calling equipment to be connected after the calling equipment sends the second confirmation message.

2. The method of claim 1, wherein the connection notification is an RTCP packet of a source description type, and a CNAME field in the RTCP packet is used for storing identification information that the called device is connected.

3. The method according to claim 1, wherein the connection notification is an RTCP packet of type 202, the source description type, and the PRIV field in the RTCP packet is used for storing identification information that the called device is connected; alternatively, the connection notification is an RTCP packet of type 204.

4. The method of claim 1, wherein the first time period is greater than 0 and less than or equal to 3 seconds.

5. The method of claim 1, wherein the first duration is 0.

6. The method according to claim 1, wherein the first duration is a preset multiple of a second duration, and the second duration is a duration from a time when the communication network between the calling device and the called device normally sends the successful response to the called device to a time when the called device receives the first acknowledgement message.

7. The method of claim 1, further comprising:

and if the timing time does not reach the first duration, the called equipment receives a first confirmation message returned by the calling equipment aiming at the successful response of the connection, stops timing and confirms that the voice call with the calling equipment is established.

8. A voice call establishing method is characterized by comprising the following steps:

the calling equipment sends an invitation request of voice call to the called equipment;

the calling equipment receives a connection notification which is sent by the called equipment and based on a first private protocol, wherein the connection notification is used for indicating that the called equipment is connected, and the first private protocol is a private real-time transport control protocol (RTCP);

the calling device adjusts the local call state to be connected according to the connection notification, and sends a second confirmation message based on the first private protocol to the called device, aiming at the connection notification, so that the called device confirms that the voice call between the calling device and the called device is established according to the second confirmation message;

the method for receiving the connection notification based on the first private protocol sent by the called device by the calling device comprises the following steps:

after receiving an invitation request of a voice call sent by the calling equipment, the called equipment sends a response of successful connection aiming at the invitation request to the calling equipment and starts timing;

and if the timing time reaches a first time length, the called equipment does not receive a first confirmation message returned by the calling equipment for the successful connection response, and sends a connection notification based on a first private protocol to the calling equipment.

9. The method of claim 8, wherein the second acknowledgement message is a source description type RTCP packet, and wherein a CNAME field in the RTCP packet is used to store information identifying the acknowledgement.

10. The method of claim 8, wherein the second acknowledgement message is an RTCP packet of a source description type, and wherein a PRIV field in the RTCP packet is used for storing information identifying an acknowledgement.

11. A voice call establishing method is characterized by comprising the following steps:

the called equipment receives the invitation request, sends a connection success response aiming at the invitation request to the calling equipment and starts timing;

the calling device receives the connection notification, adjusts the local call state to be connected according to the connection notification, and sends a second confirmation message based on the first private protocol to the called device, wherein the second confirmation message is specific to the connection notification;

and the called equipment receives the second confirmation message and confirms that the voice call with the calling equipment is established.

12. A method for hanging up a voice call, comprising:

the first device hangs up the voice call with the second device;

the first equipment sends a call hang-up notice to the second equipment and starts timing, wherein the call hang-up notice is used for indicating that the first equipment hangs up the call;

if the timing time reaches a first time length, the first equipment does not receive a third confirmation message returned by the second equipment aiming at the telephone hang-up notification, and sends a first notification based on a first private protocol to the second equipment, wherein the first notification is used for indicating that the first equipment hangs up the call, and the first private protocol is a private real-time transport control protocol (RTCP);

and the first equipment receives a fourth confirmation message which is returned by the second equipment aiming at the first notification and is based on the first private protocol, and confirms that the voice call between the first equipment and the second equipment is hung up, wherein the fourth confirmation message is sent after the second equipment receives the first notification and adjusts the local call state to be hung up according to the first notification.

13. A method for canceling a voice call, comprising:

the first equipment cancels the voice call with the second equipment;

the first equipment sends a telephone cancellation notice to the second equipment and starts timing, wherein the telephone cancellation notice is used for indicating that the first equipment cancels the call;

if the timing time reaches a first time length, the first equipment does not receive a fifth confirmation message returned by the second equipment for the telephone cancellation notification, and sends a third notification based on a first private protocol to the second equipment, wherein the third notification is used for indicating that the first equipment cancels the call, and the first private protocol is a private real-time transport control protocol (RTCP);

and the first equipment receives a sixth confirmation message which is returned by the second equipment aiming at the third notification and is based on the first private protocol, and confirms that the voice call between the first equipment and the second equipment is cancelled, wherein the sixth confirmation message is sent after the second equipment receives the third notification and adjusts the local call state to be cancelled according to the third notification.

14. An electronic device, comprising:

a memory and a processor, the memory coupled with the processor;

the memory stores program instructions that, when executed by the processor, cause the electronic device to perform the voice call setup method of any one of claims 1-7 or to perform the voice call setup method of any one of claims 8-10.

15. A computer-readable storage medium comprising a computer program, which, when run on an electronic device, causes the electronic device to perform a voice call setup method as claimed in any one of claims 1 to 7 or to perform a voice call setup method as claimed in any one of claims 8 to 10.

16. An electronic device, comprising:

a memory and a processor, the memory coupled with the processor;

the memory stores program instructions that, when executed by the processor, cause the electronic device to perform the voice call hanging up method of claim 12.

17. A computer-readable storage medium comprising a computer program which, when run on an electronic device, causes the electronic device to perform the voice call hanging-up method of claim 12.

18. An electronic device, comprising:

a memory and a processor, the memory coupled with the processor;

the memory stores program instructions that, when executed by the processor, cause the electronic device to perform the voice call cancellation method of claim 13.

19. A computer-readable storage medium comprising a computer program, which, when run on an electronic device, causes the electronic device to perform the voice call cancellation method of claim 13.