CN107659906B

CN107659906B - Method and device for realizing call waiting

Info

Publication number: CN107659906B
Application number: CN201711122861.7A
Authority: CN
Inventors: 李延斌; 马瑞涛; 龚子丹; 罗佩华; 谭蓓; 石乐; 邢向晖
Original assignee: China United Network Communications Group Co Ltd; China Information Technology Designing and Consulting Institute Co Ltd
Current assignee: China United Network Communications Group Co Ltd; China Information Technology Designing and Consulting Institute Co Ltd
Priority date: 2017-11-14
Filing date: 2017-11-14
Publication date: 2021-06-18
Anticipated expiration: 2037-11-14
Also published as: CN107659906A

Abstract

The application provides a method and a device for realizing call waiting, relates to the technical field of communication, is applied to a mobile communication network, and can improve the experience of a user signing a call waiting service in a communication process. The specific scheme comprises the following steps: in the process of establishing a call between first User Equipment (UE) and second UE, the first UE receives a third party call request sent by third UE through a network side device, and the first UE signs a call waiting service; the first UE sends an idle response to the network side device according to the third party call request; the first UE generates a third party calling prompt tone and/or a third party caller identification according to the third party calling request; the network side device receives an idle response sent by the first UE and plays a call waiting prompt tone to the third UE; the first UE answers the call initiated by the third UE, or the first UE rejects the call initiated by the third UE, or the first UE ignores the call initiated by the third UE.

Description

Method and device for realizing call waiting

Technical Field

The embodiment of the invention relates to the technical field of communication, in particular to a method and a device for realizing call waiting.

Background

The Call Waiting (CW) service of the current mobile communication network refers to a service in which a User Equipment (UE) can make or receive a third party UE (e.g., a telephone Call) during a Call and can freely switch between two calls. Wherein, a UE must first turn on a call waiting service before using a multi-party call. The three parties in a call cannot hear each other's voice at the same time, i.e. the other party hears the system alert tone when the two parties are in a call.

For example, when the UE1 talks to the UE2, the UE3 attempts to establish a call with the UE1, and the UE1 waiting on call may receive a third party call alert tone indicating that another UE3 is waiting on call. At the same time, the camped UE3 may receive a camp-on alert tone indicating that an outgoing call is being camped on. The UE1 may choose to answer, reject or ignore the call waiting for the third party. The UE1 needs to sign a call waiting service at a network element such as a Home Subscriber Server (HSS) on the network side.

There is a problem in that, in the process of the UE1 establishing a call with the UE2 (the UE1 receives a call request and rings as a called party, or the UE2 receives an incoming call request and rings as a called party), when the UE3 attempts to establish a call with the UE1, the UE1 cannot respond even if the UE1 signs up for a call waiting service. At this time, the UE1 cannot know the call of the UE3, and the UE3 can only hear the indication tone that the user is busy, i.e., the call initiated by the UE3 is not call-waiting. As such, the user experience provided by UEs (e.g., UE1) subscribing to the call waiting service may be expected to be improved.

Disclosure of Invention

The application provides a method and a device for realizing call waiting, which are applied to the process of three-party communication in a mobile communication network, in particular to the process of waiting for a third-party call in a called way, so that user equipment signing a call waiting service can receive the third-party call, and the user experience of the user equipment in the communication process is improved.

In a first aspect, the present application provides a method for implementing call waiting, including: in the process of establishing a call between first UE and second UE, the first UE receives a third party call request sent by third UE through a network side device, the first UE signs a call waiting service, and the third party call request is used for indicating the third UE to request the call between the third UE and the first UE; the first UE sends an idle response to the network side device according to the third party call request, wherein the idle response is used for indicating that the first UE line is idle and the first UE is establishing a call or is in a call; the first UE generates a third party call prompt tone and/or a third party incoming call display according to the third party call request, wherein the third party call prompt tone and the third party incoming call display are both used for indicating that the third UE initiates a call to the first UE; the first UE answers the call initiated by the third UE, or the first UE rejects the call initiated by the third UE, or the first UE ignores the call initiated by the third UE.

It should be noted that, the method for implementing call waiting provided by the present application may determine, in a process of establishing a call between two UEs, that states of the two UEs are states of establishing a call or being in a call. At this time, even if one UE (abbreviated as a subscribed UE) subscribed to call waiting is establishing a call with another UE and does not have a call (call is not connected), the subscribed UE may receive a call initiated by a third party UE and trigger a call waiting service flow. Therefore, the user experience provided by the signed UE in the communication process can be improved, and important calls are prevented from being missed.

In a second aspect, the present application provides a method for implementing call waiting, the method comprising: in the process of establishing a call between first UE and second UE, a network side device receives a third party call request initiated by third UE, the first UE signs a call waiting service, and the third party call request is used for the third UE to request the call between the third UE and the first UE; the network side device sends the third party call request to the first UE; the network side device receives an idle response sent by the first UE, wherein the idle response is used for indicating that the first UE line is idle and the first UE is establishing a call or is in a call; and the network side device plays a call waiting prompt tone to the third UE according to the idle response, wherein the call waiting prompt tone is used for indicating that the call initiated from the third UE to the first UE is in a call waiting state.

In a third aspect, the present application provides a first UE, including: the device comprises a receiving module, a sending module and a processing module. The receiving module is used for receiving a third party call request sent by a third UE through a network side device in the process of establishing a call between the first UE and a second UE, the first UE signs a call waiting service, and the third party call request is used for indicating the third UE to request the call with the first UE. The sending module is configured to send an idle response to the network side device according to the third party call request received by the receiving module, where the idle response is used to indicate that the first UE line is idle and the first UE is establishing a call or is in a call. The processing module is configured to generate a third-party call alert tone according to the third-party call request received by the receiving module, where the third-party call alert tone is used to indicate that the third UE is initiating a call to the first UE. The processing module is configured to answer a call initiated by the third UE, or reject the call initiated by the third UE, or ignore the call initiated by the third UE.

In a third aspect, the present application provides a first UE, including: one or more processors, memory, a communication interface, a display, an input, and a bus. The memory is configured to store at least one instruction, and the one or more processors and the memory, the communication interface, the display and the input device are connected through the bus, and when the first UE runs, the one or more processors execute the at least one instruction stored in the memory, so that the first UE executes the method for implementing call waiting as in the first aspect and various possible implementations thereof.

In a fourth aspect, the present application provides a computer storage medium comprising: at least one instruction; the at least one instruction, when executed on a computer, causes the computer to perform a method of implementing call waiting as in the first aspect and its various possible implementations described above.

In a fifth aspect, the present application provides a computer program product comprising: at least one instruction; the at least one instruction, when executed on a computer, causes the computer to perform a method of implementing call waiting as in the first aspect and its various possible implementations described above.

It is to be understood that the first UE described in the second and third aspects, the computer storage medium described in the fourth aspect, or the computer program product described in the fifth aspect are all configured to execute the corresponding method provided above, and therefore, the beneficial effects achieved by the method may refer to the beneficial effects in the corresponding method provided above, and are not described herein again.

In a sixth aspect, the present application provides a network-side device, including: the device comprises a receiving module and a sending module. The receiving module is used for receiving a third party call request initiated by a third UE in the process of establishing a call between the first UE and a second UE, the first UE signs a call waiting service, and the third party call request is used for the third UE to request the call between the third UE and the first UE. The sending module is used for sending the third party call request received by the receiving module to the first UE. The receiving module is further configured to receive an idle response sent by the first UE, where the idle response is used to indicate that the first UE line is idle. The sending module is further configured to play a call waiting alert tone to the third UE according to the idle response, where the call waiting alert tone is used to indicate that a call initiated by the third UE to the first UE is in a call waiting state.

In a seventh aspect, a network side device in the present application includes: one or more processors, memory, communication interfaces, and buses; the memory is configured to store at least one instruction, and the one or more processors and the memory are connected to the communication interface via a bus, and when the network-side device is operated, the one or more processors execute the at least one instruction stored in the memory, so that the network-side device performs the method for implementing call waiting as in the second aspect and various possible implementations thereof.

In an eighth aspect, the present application is directed to a computer storage medium comprising: at least one instruction;

when the at least one instruction is executed on a computer, the computer is caused to perform a method of implementing call waiting as in the second aspect and its various possible implementations as described above.

In a ninth aspect, the present application provides a computer program product comprising: at least one instruction

It is to be understood that the network-side device according to the sixth aspect and the network-side device according to the seventh aspect, the computer storage medium according to the eighth aspect, or the computer program product according to the ninth aspect are all configured to execute the corresponding method provided above, and therefore, the beneficial effects achieved by the method can refer to the beneficial effects in the corresponding method provided above, and are not described herein again.

Drawings

Fig. 1 is a schematic diagram illustrating a network architecture applied in a method for implementing call waiting according to an embodiment of the present invention;

fig. 2 is a schematic structural component diagram of an S-CSCF according to an embodiment of the present invention;

FIG. 3 is a schematic structural diagram of an Mmtel AS according to an embodiment of the present invention;

fig. 4 is a schematic structural diagram of an MRF according to an embodiment of the present invention;

fig. 4a is a schematic structural diagram of a network-side device according to an embodiment of the present invention;

fig. 5 is a schematic structural diagram of a UE according to an embodiment of the present invention;

fig. 6 is a flowchart illustrating a method for implementing call waiting according to an embodiment of the present invention;

fig. 6a is a schematic flowchart of another method for implementing call waiting according to an embodiment of the present invention;

FIG. 7 is a diagram illustrating a display interface according to an embodiment of the present invention;

fig. 8 is a flowchart illustrating another method for implementing call waiting according to an embodiment of the present invention;

FIG. 9 is a schematic diagram of another display interface provided by an embodiment of the invention;

FIG. 10 is a schematic diagram of another display interface provided by an embodiment of the invention;

fig. 11 is a flowchart illustrating another method for implementing call waiting according to an embodiment of the present invention;

FIG. 12 is a schematic diagram of another display interface provided by an embodiment of the invention;

fig. 13 is a flowchart illustrating another method for implementing call waiting according to an embodiment of the present invention;

fig. 14 is a flowchart illustrating another method for implementing call waiting according to an embodiment of the present invention;

fig. 15 is a flowchart illustrating another method for implementing call waiting according to an embodiment of the present invention;

FIG. 16 is a schematic diagram of another display interface provided by an embodiment of the invention;

FIG. 17 is a schematic diagram of another display interface provided by an embodiment of the invention;

fig. 18 is a schematic structural diagram of a first UE according to an embodiment of the present invention;

fig. 19 is a schematic structural component diagram of another first UE according to an embodiment of the present invention;

fig. 20 is a schematic structural diagram of another network-side device according to an embodiment of the present invention;

fig. 21 is a schematic structural diagram of another network-side device according to an embodiment of the present invention;

fig. 22 is a schematic structural diagram of another network-side device according to an embodiment of the present invention.

Detailed Description

In the following, the terms "first", "second" and "third" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, features defined as "first", "second", "third" may explicitly or implicitly include one or more of the features. In the description of the present application, "a plurality" means two or more unless otherwise specified.

The embodiment of the invention provides a method and a device for realizing call waiting, which are applied to the process of mobile communication, in particular to the process of waiting for a third-party call, so that user equipment signing a call waiting service can receive the third-party call, and the experience of the user in the communication process is improved.

The basic call service in a mobile communication network is a process in which a calling party inputs a telephone number of a called party and then both parties enter a call. Wherein, the two user equipments can realize the call with each network element of the network side interactively.

It should be noted that the method for implementing call waiting provided in the embodiment of the present invention may be applied to Voice Over LTE (Voice LTE) service in a Long Term Evolution (Long Term Evolution, LTE) network. At this time, the UE provided in the embodiment of the present invention supports the VoLTE technology. The network elements supporting the two UE calls may include a Serving Call Session Control Function (S-CSCF), a Multimedia Telephony Application Server (Mmtel AS), and a Media Resource Function (MRF).

Of course, the method for implementing call waiting provided in the embodiment of the present invention may also be applied to the voice service of the third generation mobile communication technology (3rd-generation, 3G) network and the voice service of the second generation mobile communication technology (2G) network. At this time, both the UE and the network element supporting the call of the two UEs provided by the embodiment of the present invention support the 3G technology. For example, the network element supporting the call between two UEs may be a Mobile Switching Center (MSC). The MSC is used for providing call switching service and call control equipment for the UE.

The following description of the embodiment of the present invention only takes voice service (VoLTE) in an LTE network as an example to describe the method for implementing call waiting provided by the embodiment of the present invention.

The technical solutions in the embodiments of the present invention are described in detail below with reference to the accompanying drawings in the embodiments of the present invention.

Fig. 1 is a schematic diagram illustrating a network architecture applied to a method for implementing call waiting according to an embodiment of the present invention. In fig. 1, a network architecture including a network side device and UEs (UE1, UE2, and UE3) is shown. Two UEs (such as UE1 and UE2) establish a call or perform a call by interacting with a network side device. The network side device may provide a communication service for one or more UEs, that is, control one or more UEs to talk.

Specifically, the network architecture shown in fig. 1 includes S-CSCF 101, Mmtel AS 102, and MRF 103, AS well AS UE1, UE2, and UE 3. The functions of the network-side device shown in fig. 1 may be implemented by a set of S-CSCF 101, Mmtel AS 102, and MRF 103 shown in fig. 1.

The following describes each component of the S-CSCF 101 in detail with reference to fig. 2:

processor 21 is the control center of S-CSCF 101 and may be a single processor or a collection of processing elements. For example, the processor 21 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits configured to implement embodiments of the present invention, such as: one or more microprocessors (digital signal processors, DSPs), or one or more Field Programmable Gate Arrays (FPGAs).

Processor 21 may control, among other things, the operation of S-CSCF 101 by running or executing software programs stored in memory 22 and invoking data stored in memory 22. For example, the processor 21 may be configured to provide information related to a call service to two or more UEs and to control a call of the two or more UEs.

In particular implementations, processor 21 may include one or more CPUs such as CPU0 and CPU1 shown in fig. 2 as one example.

In particular implementations, the UE may include multiple processors, such as processor 21 and processor 25 shown in fig. 2, as an example. Each of these processors may be a single-Core Processor (CPU) or a multi-Core Processor (CPU). A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

The Memory 22 may be a Read-Only Memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical Disc storage, optical Disc storage (including Compact Disc, laser Disc, optical Disc, digital versatile Disc, blu-ray Disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to these. The memory 22 may be self-contained and coupled to the processor 21 via a bus 24. The memory 22 may also be integrated with the processor 21.

The memory 22 may be configured to store service-related information for a call between two or more UEs and instructions for controlling the call between two or more UEs.

The communication interface 23 may include two communication interfaces, a sending interface for sending data to an external device and a receiving interface for receiving data from the external device, that is, the data receiving and the data sending can be respectively realized through two different communication interfaces. For example, in conjunction with FIG. 1, one communication interface of S-CSCF 101 may be used to send messages, such AS Invite messages, to Mmtel AS 102, UE1, UE2, and UE3, AS described above; another communication interface of S-CSCF 101 may be used to receive messages, such AS 200 messages, sent by network elements such AS Mmtel AS 102 and UE 1. Of course, the communication interface 23 may integrate the data receiving function and the data transmitting function into one communication interface, and the communication interface has the data receiving function and the data transmitting function.

The bus 24, the bus 24 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus 24 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 2, but it is not intended that there be only one bus or one type of bus.

The structure of S-CSCF 101 shown in fig. 2 does not constitute a limitation of the S-CSCF and may include more or fewer components than shown, or some components may be combined, or a different arrangement of components.

Specifically, the following describes each component of Mmtel AS 102 in detail with reference to fig. 3:

mmtel AS 102 may include a processor 31, a memory 32, a communication interface 33, a bus 34, and a processor 35. The memory 32 may be self-contained and coupled to the processor 31 via a bus 34. The memory 32 may also be integrated with the processor 31.

The processor 31 may be used to provide basic voice and video services to the UE, among other things.

The memory 32 may be used to store information related to basic speech of the UE.

With reference to FIG. 1, one communication interface of Mmtel AS 102 may be used to send messages, such AS INFO messages (playback messages), to the S-CSCF 101, MRF 103, UE1, UE2, and UE3 described above; one communication interface of Mmtel AS 102 may be used to receive messages, such AS 200 messages, sent by S-CSCF 101 or MRF 103 AS described above.

It should be noted that, for specific description of each component in the Mmtel AS shown in fig. 3, reference may be made to the description of the constituent structure of the S-CSCF shown in fig. 2 in the foregoing embodiment, and details of this embodiment of the present invention are not described here again.

Specifically, the following specifically describes each component of the MRF 103 with reference to fig. 4:

processor 41, memory 42, communication interface 43, bus 44, and processor 45 may be included in MRF 103. The memory 42 may be self-contained and coupled to the processor 41 via a bus 44. The memory 42 may also be integrated with the processor 41.

Wherein, the processor 41 can be used to provide a playback service to the UE, and send a call waiting prompt tone to the UE, where the call waiting prompt tone can be "no start, user who you dial is in a call, please dial again later, thank you! ".

The memory 42 may be used to store the information related to the playback service of the UE.

Referring to FIG. 1, one communication interface of the MRF 103 may be used to send messages, such as ACK messages, to the S-CSCF 101, MRF 103, UE1, UE2, and UE3 described above; another communication interface of MRF 103 may be used to receive messages, such as 200 messages, sent by S-CSCF 101 or MRF 103 as described above.

It should be noted that, for specific description of each component in the MRF shown in fig. 4, reference may be made to the description of the constituent structure of the S-CSCF shown in fig. 2 in the foregoing embodiment, and details of this embodiment of the present invention are not described here again.

In a possible implementation manner, the network side device according to the embodiment of the present invention may be composed of an S-CSCF, an Mmtel AS, and an MRF. Exemplarily, as shown in fig. 4a, a schematic structural composition diagram of a network-side device according to an embodiment of the present invention is provided. The network-side device 40a shown in FIG. 4a may be composed of S-CSCF 101 shown in FIG. 2, Mmtel AS 102 shown in FIG. 3, and MRF 103 shown in FIG. 4.

Specifically, the network-side device 40a shown in fig. 4a may include a processor 41a, a memory 42a, a communication interface 43a, a bus 44a, and a processor 45 a.

It is contemplated that

processors

41a and 45a described above may be comprised of

processors

21 and 25 included in S-CSCF 101 described above,

processors

31 and 35 included in Mmtel AS 102, and

processors

41 and 45 included in MRF 103. That is, the functions of the processor 41a may be a set of functions of each processor in the S-CSCF 101, the Mmtel AS 102 and the MRF 103, which are not described herein again.

Similarly, the functions of the memory 42a may be a set of functions of each memory in the S-CSCF 101, the Mmtel AS 102 and the MRF 103, which are not described herein again. The functions of the communication interface 43a may be a set of functions of each communication interface in S-CSCF 101, Mmtel AS 102, and MRF 103, which are not described herein again. The function of the bus 44a may be a set of functions of each bus in the S-CSCF 101, the Mmtel AS 102 and the MRF 103, which are not described herein again.

It should be noted that the UE may be a user equipment such as a cellular phone, a netbook, a Personal Digital Assistant (PDA), and the like, and the user equipment may be provided with a mobile communication network service by an operator. Of course, the above-described UE supports VoLTE technology.

It is conceivable that, since the constituent structures of the UE1, the UE2 and the UE3 provided by the embodiments of the present invention may be the same, only one UE is described in detail below in the embodiments of the present invention.

Exemplarily, fig. 5 is a schematic diagram illustrating a UE according to an embodiment of the present invention. As shown in fig. 5, the UE may include a memory 52, a communication interface 53 and one or more processors 51.

The following specifically describes each constituent component of the UE with reference to fig. 5:

the processor 51 is a control center of the UE, and may be a single processor or a collective term for multiple processing elements. For example, the processor 51 may be a CPU, an ASIC, or one or more integrated circuits configured to implement embodiments of the present invention, such as: one or more DSPs, or one or more FPGAs.

The processor 51 may perform various functions of the UE by running or executing software programs stored in the memory 52, and calling data stored in the memory 52, among other things. For example, the processor 51 may be used to identify the telephone number or the like of a received incoming call request.

In particular implementations, processor 51 may include one or more CPUs such as CPU0 and CPU1 shown in fig. 5 as one example.

In particular implementations, the UE may include multiple processors, such as processor 51 and processor 55 shown in fig. 5, as an example. Each of these processors may be a single core processor or a multi-core processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

The memory 52 may be, but is not limited to, a ROM or other type of static storage device that can store static information and instructions, a RAM or other type of dynamic storage device that can store information and instructions, an EEPROM, a CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory 52 may be separate and coupled to the processor 51 by a bus 54. The memory 52 may also be integrated with the processor 51.

The memory 22 is used for storing relevant information during the conversation between the UE and another UE, such as telephone numbers of the two UEs. For example, a memory included in the UE1 may store therein a phone number of the UE1, a phone number of the UE2 described above, and the like.

The communication interface 53 may include two communication interfaces. For example, in conjunction with FIG. 1, a communication interface of UE1 may be used to receive messages, such AS 180 messages, sent by S-CSCF 101 or Mmtel AS 102 AS described above; another communication interface of UE1 may be used to receive messages, such AS 200 messages, sent by S-CSCF 101 or Mmtel AS 102, AS described above. Of course, the communication interface 53 may integrate a data receiving function and a data transmitting function into one communication interface, and the communication interface has a data receiving function and a data transmitting function.

The bus 54 may be a PCI bus or an EISA bus, etc. The bus 54 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 5, but this is not intended to represent only one bus or type of bus.

A display 56 may be used to display to the user the telephone number of the UE originating the call, etc.

The input device 57 may be configured to receive an operation instruction of the user for the call displayed on the display 56, so that the user selects to answer, reject or ignore the call.

In a specific embodiment, when the UE is a UE having a touch screen, the display 56 and the input device 57 may be implemented by the touch screen. At this time, the touch screen is used to implement input and output functions of the UE, collect operation instructions of the user on or near the touch screen (for example, operation instructions of the user on or near the touch screen using any suitable object or accessory such as a finger, a stylus pen, etc.), and drive the corresponding connection device according to a preset program. But also for displaying information entered by the user or provided to the user (the telephone number of the received call). The touch screen provided in the embodiment of the present invention may be of various types, such as a resistive type, a capacitive type, an infrared light sensing type, an ultrasonic wave type, and the like, which is not limited in the embodiment of the present invention. In the following, the UE provided in the embodiment of the present invention is described only by using a mobile phone with a touch screen.

The audio circuitry 58, speaker 59, microphone 60 may provide an audio interface between the user and the UE 1. The audio circuit 58 can transmit the electrical signal converted from the received audio data to the speaker 59, and the electrical signal is converted into a sound signal by the speaker 59 and output; on the other hand, the microphone 60 converts the collected sound signals into electrical signals, which are received by the audio circuit 58 and converted into audio data, which are then transmitted to, for example, another UE, or output to the processor 51 for further processing. For example, the audio circuitry 58, speaker 59, and microphone 60 described above may be used to enable a call between two UEs. The speaker 59 may also play a system alert tone such as a call waiting alert tone.

The structure of the UE shown in fig. 5 does not constitute a limitation of the positioning server and may comprise more or less components than those shown, or some components may be combined, or a different arrangement of components.

It should be noted that, in the method for implementing call waiting provided in the embodiment of the present invention, in order to improve user experience provided by a UE (subscriber UE) subscribing to a call waiting service in a communication process, the subscriber UE may receive a third party call while the subscriber UE is in a call, and the subscriber UE may receive the third party call while the subscriber UE establishes a call.

The method for implementing call waiting provided by the embodiment of the present invention is described in detail below with reference to a schematic diagram of a network architecture applied to the method for implementing call waiting shown in fig. 1, the S-CSCF shown in fig. 2, the Mmtel AS shown in fig. 3, the MRF shown in fig. 4, and the UE shown in fig. 5. Referring to fig. 6, a method for implementing call waiting provided by the embodiment of the present application includes steps 601 to 608:

s601, in the process of establishing a call between the first UE and the second UE, the network side device receives a third party call request initiated by a third UE.

Illustratively, in conjunction with fig. 1-4 and fig. 4a, step 601 may be implemented by each communication interface among S-CSCF 101, Mmtel AS 102 and MRF 103.

The first UE signs a call waiting service, and the third party call request is used for the third UE to request the conversation with the first UE.

S602, the network side device sends the third party call request to the first UE.

Illustratively, in conjunction with fig. 1-4 and fig. 4a, step 602 may be implemented by each communication interface in S-CSCF 101, Mmtel AS 102 and MRF 103.

The first UE signs a call waiting service, and the third party call request is used for indicating the third UE to request the conversation with the first UE. Generally, the UE1 may interact with the S-CSCF and HSS described above to implement the signed call waiting service.

S603, in the process of establishing a call between the first UE and the second UE, the first UE receives a third party call request sent by a third UE through a network side device.

Illustratively, in conjunction with fig. 1 and 5, the first UE may be the UE1, and the step 603 may be performed by the communication interface 53 included in the UE 1.

S604, the first UE sends an idle response to the network side device according to the third party call request.

Illustratively, in conjunction with fig. 1 and 5, the above-described step 604 may be performed by the communication interface 23 of the UE 1.

The idle response is used for indicating that the first UE line is idle and the first UE is establishing a call or is calling. It is obvious that the idle response sent by the first UE in the embodiment of the present invention indicates that the first UE is establishing a call.

The third party call request is received when the first UE is establishing a call, and may trigger the first UE to generate an idle response, so as to perform a call waiting service with the network side device interactively.

It should be noted that, in the process of establishing a call, the first UE sends an idle response instead of a busy response (e.g., 486 message) to the network side apparatus, which may indicate that the line of the first UE is idle, that is, the first UE is currently in a state where it can answer a new call. Specifically, the idle response may carry indication information indicating that the first UE is currently speaking or is currently establishing a conversation.

S605, the network side device receives the idle response sent by the first UE.

Illustratively, in conjunction with fig. 1-4 and fig. 4a, step 605 may be interactively implemented by each communication interface in S-CSCF 101, Mmtel AS 102 and MRF 103.

It should be noted that, after receiving the idle response sent by the first UE, the network side apparatus may determine that the first UE is establishing a call or is in a call, and at the same time, determine that the first UE may receive a new call in the call waiting service.

And S606, the first UE generates a third party calling prompt tone and/or a third party caller identification according to the third calling request.

Illustratively, in conjunction with FIGS. 1-4, step 606 can be implemented by S-CSCF 101, Mmtel AS 102, and MRF 103, AS described above.

Wherein, the third party call prompt tone is used to indicate that the third UE is initiating a call to the first UE. The third party call alert tone may be an alert tone that plays a "beep" in the first UE, and may be accompanied by a vibration of the body of the first UE. In addition, a third party caller identification can be displayed on the display interface of the first UE. The third-party caller id display may include information such as a user name, a phone number, and an operator corresponding to the third UE, and is used to indicate to the first UE that the third UE is initiating a call to the first UE.

Optionally, the first UE may generate a third-party call alert tone, or generate a third-party caller id display, or generate a third-party call alert tone and a third-party caller id display. In this way, the first UE may prompt the user in multiple ways to "a call initiated from the third UE to the first UE", which may improve user experience provided during the first UE (subscribed UE) call.

The execution sequence of the above steps 605 and 606 is not limited in the embodiment of the present invention, and the step 606 is executed after the step 605 in fig. 6 as an example, which illustrates the method for implementing call waiting provided in the embodiment of the present invention.

S607, the network side device plays the call waiting prompt tone to the third UE according to the idle response.

Illustratively, in conjunction with FIGS. 1-4, step 607 may be performed interactively by S-CSCF 101, Mmtel AS 102, and MRF 103, AS described above.

The call waiting tone is used for indicating that a call initiated from the third UE to the first UE is in a call waiting state.

For example, the wait alert tone may be "hello, please don't hang up, you are calling! ". In this way, the call waiting alert tone prompts the user corresponding to the third UE that the call initiated by the third UE is being requested to be answered by the first UE.

S608, the first UE answers the call initiated by the third UE, or the first UE rejects the call initiated by the third UE, or the first UE ignores the call initiated by the third UE.

Illustratively, the above step 608 may be implemented by the processor 51 included in the UE1 shown in fig. 1 and 5.

It is conceivable that the first UE may select whether to answer the third UE-originated call after receiving the third UE-originated call. Therefore, the user corresponding to the first UE can select to establish a call with the second UE or a call with the third UE according to the requirement of the user.

It should be noted that, the method for implementing call waiting provided in the embodiment of the present invention may determine, in a process of establishing a call between two UEs, that states of the two UEs are states of executing a call service. At this time, even if one UE (abbreviated as a subscribed UE) subscribed to call waiting is establishing a call with another UE and does not have a call (call is not connected), the subscribed UE may receive a call initiated by a third party UE and trigger a call waiting service flow. Therefore, the user experience of the signed UE in the communication process can be improved, and important calls are prevented from being missed.

It is contemplated that the network-side device may receive the third-party call request initiated by the third UE before receiving the third-party call request initiated by the third UE. For example, as shown in fig. 6a, before the step 601, the method for implementing call waiting according to the embodiment of the present invention may further include the step 601 a:

s601a, the third UE sends a third call request to the network side device.

For example, assuming that the third UE is the UE3, the step 601a may be performed by a processor of the UE3, wherein the processor of the UE3 may refer to the processor 51 of the UE1 shown in fig. 5.

Wherein, when the UE3 initiates a call to the UE1, the processor of the UE3 may generate an outgoing alert tone that is a "beep". Also, the display interface provided by the UE3 may display the user name and phone number of the user corresponding to the UE 1.

In a specific embodiment, the process of establishing a call between the first UE and the second UE may include: the method comprises the steps that a calling UE in the first UE and the second UE has initiated a call, and a called UE is not ringing, or the steps that the calling UE in the first UE and the second UE has initiated a call, and the called UE is ringing.

It should be noted that, in the method for implementing call waiting provided in the embodiment of the present invention, in the process of establishing a call between two UEs (e.g., a first UE and a second UE), even if the called party of the two UEs does not ring yet, as long as the two UEs start to establish a call through a network side device, a subscribed UE of the two UEs may execute a call waiting service when receiving a call initiated by a third UE. Therefore, the user experience provided by the signed UE in the communication process can be further improved, and important calls are prevented from being missed.

The embodiment of the invention also provides a Graphical User Interface (GUI); and the GUI comprises graphic options in a text form and an icon form, and both the graphic options in the text form and the graphic options in the icon form of the GUI can be operated by a user through a touch screen. The GUI includes windows, drop-down menus, dialog boxes and their corresponding control mechanisms (e.g., the CPU of the UE). Meanwhile, GUIs are standardized in various new applications or software, i.e., the same operations are always done in the same way; for example, operating any graphic option (hereinafter referred to as an option) in a text form or an icon form in the GUI may be that the user clicks or slides the option on the touch screen with a finger. After the user operates an option, the processor can generate a corresponding operation instruction and respond to the operation.

The display interface displayed by the UE provided by the embodiment of the invention can be changed along with different application scenes of the method for realizing call waiting.

It should be noted that the method for implementing call waiting provided by the embodiment of the present invention may be applied to various application scenarios. Illustratively, the first application scenario provided in the embodiment of the present invention is that a first UE and a second UE are establishing a call, and the first UE is a calling UE. The second application scenario provided by the embodiment of the present invention is that a first UE and a second UE are establishing a call, and the first UE is a called UE. Of course, in the first application scenario or the second application scenario, the called UE may be ringing or not ringing.

Specifically, in the first application scenario provided in the embodiment of the present invention, the touch screen of the first UE may display an "outgoing call prompt" interface to the user. The calling prompt interface comprises information such as a user name and a telephone number of a user corresponding to the second UE.

When the first UE is UE1 and the second UE is UE2, it is assumed that the user name corresponding to UE1 provided in the embodiment of the present invention is "wang yi", and the phone number of UE1 is "137 × 9059"; the user name corresponding to the UE2 is "tension three", and the phone number of the UE2 is "138 × 4215".

Exemplarily, as shown in fig. 7, a schematic diagram of a display interface provided in an embodiment of the present invention is shown. The display interface 71 in fig. 7 is an "outgoing call prompt" interface of the UE1, where the display interface 71 includes a user name "zhang san" corresponding to the UE2 (called UE), and a phone number "138 × 4215" of the UE 2. Also included in the display interface 71 are a "mute" option, a "pause call" option, a "note" option, a "address book" option, an "add call" option, a "record" option, a "hands free" option, a "keyboard" option, and an option 711. The functions of the various options shown in the provided display interface 71 are not described in detail in the embodiments of the present invention, and can be easily known by those skilled in the art.

In addition, the "human hand icon" in fig. 7 is used to schematically represent a human hand. In the embodiment of the invention, the position of the finger of the user is only represented by the 'human hand icon', but the 'human hand icon' is not displayed on the touch screen of the UE in practice. In fig. 7, the position of the "human hand icon" indicates the operation of the option by the user. The operation instruction related to the embodiment of the invention can be a touch screen operation instruction. The touch screen operation instruction corresponds to operations such as a pressing operation, a long pressing operation, a sliding operation, a clicking operation, a floating operation (an operation of the user near the touch screen) and the like of the touch screen of the UE by the user. In the embodiment of the present invention, only "click operation" is taken as an example to describe the method for implementing call waiting provided in the embodiment of the present invention. For example, the user clicks on an option 711 included in the display interface 71 shown in fig. 7, so that the UE1 receives an operation instruction (also referred to as an instruction) indicating that a call currently directed to the UE2 is to be dropped.

In the first application scenario (e.g. the first UE has called the second UE and the second UE starts ringing), the method for implementing call waiting according to the embodiment of the present invention further includes step 801 before step 608. The step 608 of "the first UE answering the call initiated by the third UE" may be replaced with the steps 802 and 803; the step 608 of "the first UE rejecting the call initiated by the third UE" may be replaced with the step 804; the step of "the first UE ignoring the call originated by the third UE" in the step 608 may be replaced by the step 805. Wherein, the relationship among the steps 802, 803, 804 and 805 is "OR". For example, as the method for implementing call waiting shown in fig. 8, step 608 shown in fig. 6a may further include step 801 before step 608, and step 608 may be replaced with steps 802 and 803, step 804, and step 805:

s801, in the process of establishing a call between the first UE and the second UE, the first UE determines that the first UE is a calling UE.

Illustratively, the above step 801 may be performed by the processor 51 included in the UE1 shown in fig. 1 and 5.

At this time, the UE1 provided by the embodiment of the present invention may display the display interface 71 as shown in fig. 7, and show the user name and the phone number of the UE2 to the user.

In the first application scenario provided in the embodiment of the present invention, when the UE1 receives a call initiated by the UE3, the display interface of the UE1 may display not only the user name and the phone number of the UE2, but also the user name and the phone number of the UE 3. It is assumed that the user name corresponding to the UE3 is "lie four", and the phone number of the UE3 is "182 × 8510". That is, the third party caller id provided in the embodiment of the present invention may further include the user name and the phone number of the UE 2.

Exemplarily, as shown in fig. 9, a schematic diagram of another display interface provided in the embodiment of the present invention is shown. In the first application scenario described above, a display interface ("incoming call alert" interface) is shown in fig. 9, where a UE1 receives a call originated by a UE3 when the UE2 is originating the call. An option 911, an option 912, an option 913, and an option 914 are included in the "incoming call alert" interface 91 shown in fig. 9. Wherein, the option 911 may be used to hang up the current call; option 912 may be used to implement hanging up the third party call; option 913 may be used to implement answering a third party call; option 914 may be used to implement a short message reply to a third party UE initiating a third party call. At this time, the third party caller id display provided in the embodiment of the present invention may be the display interface shown in fig. 9.

S802, the first UE cancels the call to the second UE through the network side device.

Illustratively, in conjunction with fig. 1 and 5, the above step 802 may be performed by the processor 51 of the UE 1.

The user corresponding to the UE1 clicks an option 911 in the display interface shown in fig. 9, so that the current call can be hung up (i.e., the call initiated by the UE1 to the UE 2). Specifically, after receiving the click operation instruction of the user on the option 911, the UE1 interacts with the network-side device to hang up the current call.

Optionally, the UE1 may also autonomously interact with the network side device to hang up the call initiated by the UE1 to the UE 2.

It is conceivable that, in this embodiment of the present invention, the network side apparatus may perform step 802a to support the first UE to perform step 802.

S802a, the network side device controls the first UE to cancel the call to the second UE.

It is conceivable that, in the first application scenario provided in the embodiment of the present invention, if the second UE starts ringing, after the network-side device performs step 802a, a prompt of "missed call" may be further displayed on the display interface of the second UE. The "missed call" prompt may include information such as a user name and a phone number of the first UE. For example, the "missed call" prompt displayed on the display interface of the UE2 includes the user name "wanyi" corresponding to the UE1, and the phone number "137 × 9059" of the UE 1. Of course, in the first application scenario, if the second UE does not ring, after the network-side device performs step 802a, the "missed call" prompt is not displayed on the display interface of the second UE.

And S803, the first UE answers the call initiated by the third UE through the network side device.

Illustratively, a user of the UE1 clicking on the option 913 of the display interface shown in fig. 9 may implement answering a third party call (i.e., a call initiated by the UE3 to the UE 1).

It should be noted that, in the method provided in this embodiment of the present invention, the step 608 may include "the first UE answers the call initiated by the third UE" instead of the step 803. At this time, while the UE1 receives the user-initiated operation instruction to answer the call initiated by the UE3, the UE1 may also autonomously hang up the call initiated to the UE 2.

It is conceivable that, in this embodiment of the present invention, the network side apparatus may perform step 803a to support the first UE to perform step 803.

S803a, the network side device controls the first UE to answer the call initiated by the third UE.

In the first application scenario provided in the embodiment of the present invention, after the network-side device performs step 803a, a "call-out prompt" interface including the user name and the phone number corresponding to the first UE may also be displayed on the display interface of the third UE. For example, the UE3 may display an "outgoing call prompt" including the user name "wang yi" corresponding to the UE1, and the phone number "137 × 9059" of the UE 1.

S804, the first UE rejects the call initiated by the third UE through the network side device, so that the network side device plays the call failure prompt tone to the third UE.

Wherein, the call failure prompt tone is used for indicating that the call initiated by the third UE is not connected. For example, the call failure alert tone provided by embodiments of the present invention may be "hello, the user you are calling, please dial again later! ".

On the other hand, for example, the user corresponding to the UE1 clicks an option 912 in the display interface shown in fig. 9, so that the UE1 receives a corresponding operation instruction, and can hang up (reject) the third party call (i.e., the call initiated by the UE3 to the UE 1).

Likewise, in this embodiment of the present invention, the network side apparatus may further perform step 804a-1 and step 804a-2 to support the first UE to perform step 804.

S804a-1, the network side device controls the first UE to reject the call initiated by the third UE.

S804a-2, the network device plays a call failure prompt tone to the third UE.

It is conceivable that the third UE may suspend the call initiated to the first UE after receiving the call failure notification tone played by the network-side device.

S805, the first UE ignores the call initiated by the third UE through the network side device, so that the network side device plays a call failure prompt tone to the third UE after a preset time.

For example, the UE1 may not click any of the options in the display interface shown in fig. 9 and described above, and may be enabled to ignore calls initiated by the UE 3. The preset time is a preset time in a communication protocol between the first UE and the network side device, such as 15 seconds.

Likewise, in this embodiment of the present invention, the network side apparatus may further perform step 805a-1 and step 805a-2 to support the first UE to perform step 805.

S805a-1, the network side device controls the first UE to ignore the call initiated by the third UE.

S805a-2, the network side device plays a call failure prompt tone to the third UE after a preset time.

Illustratively, after the network-side device and the UE1 interactively implement ignoring the call initiated by the UE3, a call failure prompt tone may be played to the UE3 at a preset time interval of 15 seconds to prompt the user corresponding to the UE3 to initiate a call to the UE1 later.

It should be noted that, in the method for implementing call waiting provided in the embodiment of the present invention, when the subscribed UE initiates a call to another UE as a calling UE, the subscribed UE is supported to execute a call waiting service, so that the subscribed UE can select to continue the current call or answer a third party call. Therefore, the user experience of the signed UE in the communication process is improved.

In another specific embodiment, in the second application scenario provided in the embodiment of the present invention, the touch screen of the first UE may present an "incoming call prompt" interface to the user. The call-in prompt interface comprises information such as a user name and a telephone number of a user corresponding to the second UE.

Exemplarily, as shown in fig. 10, a schematic diagram of another display interface provided in the embodiment of the present invention is shown. FIG. 10 illustrates a display interface 101 ("outgoing display" interface) of a UE1 in a second application scenario according to an embodiment of the present invention. The display interface 101 includes an option 1011, an option 1012, and an option 1013. Similarly, the detailed description of option 1011, option 1012 and option 1013 may refer to the related description of option 912, option 913 and option 914, which is not repeated here.

In the second application scenario (e.g., the second UE has called the second UE and the first UE starts ringing), the method for implementing call waiting according to the embodiment of the present invention may further include step 1101 before step 608. The step 608 of "the first UE answering the call initiated by the third UE" may be replaced with the step 1102; the step 608 of "the first UE rejects the call initiated by the third UE" may be replaced with the step 1103; the step of "the first UE ignoring the call originated by the third UE" in the step 608 may be replaced by the step 1104. The above-mentioned step 1102, step 1103 and step 1104 have an or relationship. For example, as shown in fig. 11, the method for implementing call waiting may further include step 1101 before step 608 shown in fig. 6a, and step 608 may be replaced with step 1102, step 1103, and step 1104:

s1101, in the process of establishing a call between the first UE and the second UE, the first UE determines that the first UE is called UE.

Illustratively, the above step 1101 may be performed by the processor 51 included in the UE1 shown in fig. 1 and 5.

At this time, the UE1 provided by the embodiment of the present invention may display the display interface 71 as shown in fig. 10, and show the user name and the phone number of the UE2 to the user.

It is conceivable that, in the second application scenario, when the UE1 receives a call originated from the UE3, the display interface of the UE1 may display not only the user name and the phone number of the UE2 but also the user name and the phone number of the UE 3.

Exemplarily, as shown in fig. 12, a schematic diagram of another display interface provided in the embodiment of the present invention is shown. In the second application scenario described above, a display interface ("incoming call alert" interface) is shown in fig. 12 where the UE1 has received a call originated by the UE2 and is ringing and receives a call originated by the UE 3. The "incoming call alert" interface 121 shown in fig. 12 includes an option 1211, an option 1212, an option 1213, an option 1214, an option 1215, and an option 1216. Similarly, the detailed descriptions of option 1211, option 1212, option 1213, option 1214, option 1215 and option 1216 may refer to the above description of

options

912, 913 and 914, and are not repeated here. At this time, the third party call display provided in the embodiment of the present invention may also be the display interface shown in fig. 12.

S1102, the first UE answers a call initiated by the third UE through the network side device, and the network side device plays a call failure prompt tone aiming at the second UE to the second UE.

Illustratively, the above step 1102 may be performed by the processor 51 of fig. 1 in conjunction with the UE1 shown in fig. 5.

The call failure prompt tone for the second UE is used to indicate that the call initiated by the second UE to the first UE is not connected. For example, the failure alert tone for the second UE described above may also be "hello, the user you are calling, please dial again later! ".

Illustratively, a user clicking operation corresponding to UE1 on option 1215 of the display interface shown in fig. 12 may enable answering a third party call (i.e., a call originated by UE1 to UE 2). At this point, the UE1 may autonomously hang up the call originated by the UE2 to the UE 1.

It is contemplated that, in this embodiment of the present invention, the network side apparatus may perform step 1102a-1 and step 1102a-2 to support the first UE to perform step 1102. As shown in fig. 11, the method for implementing call waiting according to the embodiment of the present invention may further include step 1102a-1 and step 1102 a-2:

s1102a-1, the network side device controls the first UE to answer the call initiated by the third UE.

S1102a-2, the network device plays a call failure prompt tone for the second UE to the second UE.

Illustratively, the network-side device interacts with the UE1 to perform step 1202a-1 above, and the network-side device interacts with the UE2 to perform step 1202a-2 above.

S1103, the first UE rejects the call initiated by the third UE through the network side device, so that the network side device plays a call failure prompt tone to the third UE.

Illustratively, the user corresponding to the UE1 clicks an option 1214 in the display interface shown in fig. 12, so that the UE1 receives the corresponding operation instruction, and can hang up (reject) the third party call (i.e., the call initiated by the UE3 to the UE 1).

Likewise, in this embodiment of the present invention, the network side device may further perform step 1103a-1 and step 1103a-2 to support the first UE to perform step 1103.

S1103a-1, the network side device controls the first UE to ignore the call initiated by the third UE.

S1103a-2, the network side device plays a call failure alert tone to the third UE.

Similarly, at this time, after receiving the call failure notification tone played by the network-side device, the third UE may control the network-side device to hang up the call initiated to the first UE.

S1104, the first UE ignores the call initiated by the third UE through the network side device, and the network side device plays a call failure prompt tone to the third UE after a preset time.

For example, the UE1 may not click any of

options

1214, 1215, and 1216 in the display interface shown in fig. 12, described above, to enable ignoring calls initiated by the UE 3.

Likewise, in this embodiment of the present invention, the network-side device may further perform step 1104a-1 and step 1104a-2 to support the first UE to perform step 1104. Exemplarily, as shown in fig. 11, the method for implementing call waiting according to the embodiment of the present invention may further include step S1104a-1 and step S1104 a-2:

s1104a-1, the network side device controls the first UE to ignore the call initiated by the third UE.

S1104a-2, the network side device plays a call failure prompt tone to the third UE after a preset time.

Illustratively, after the network-side device interacts with the UE1 to ignore the call initiated by the UE3, a call failure alert tone may be played to the UE3 at a preset time interval of 15 seconds to prompt the user corresponding to the UE3 to initiate a call to the UE1 later.

It is contemplated that the UE1 may choose whether to answer a call originated by the UE2 while ignoring the UE 3. Specifically, the UE1 may choose to answer, reject or ignore the call initiated by the UE2 through operation instructions received via

options

1211, 1212 and 1213 as shown in fig. 12.

It should be noted that, in the method for implementing call waiting provided in the embodiment of the present invention, when the subscribed UE receives a call initiated by another UE as a called UE, the subscribed UE is supported to execute a call waiting service, so that the subscribed UE can select to continue the current call or answer a third party call. Therefore, the user experience of the signed UE in the communication process is improved.

In a specific embodiment, before performing a call service, a UE generally needs to register on the network side to connect to the wireless communication network to enable a call with another UE. The registered UE is a UE capable of performing a basic call service. At this time, the method for implementing call waiting according to the embodiment of the present invention may further include step 1301 before step 602. For example, as shown in fig. 13, the method for implementing call waiting according to the embodiment of the present invention may further include, before step 602 shown in fig. 6, step 1301:

s1301, the network side device determines that the first UE is the registered UE.

Illustratively, in conjunction with fig. 1-4, step 1301 above may be implemented by respective processors in S-CSCF 101, Mmtel AS 102, and MRF 103, AS described above.

Wherein, the first UE indicates that the first UE can perform a basic call service for the registered UE. I.e., the first UE has the capability to talk to other UEs, such as a third UE.

It should be noted that, in the method for implementing call waiting according to the embodiment of the present invention, no matter whether the subscribed UE is establishing a call or is in a call, as long as the network side apparatus determines that the subscribed UE is the registered UE, the network side apparatus may interact with the subscribed UE to control the call of the subscribed UE. Therefore, the method is beneficial to executing the call waiting service by the signed UE and avoiding missing important calls.

In a specific embodiment, in a case that the method for implementing call waiting provided by the embodiment of the present invention is applied to a voice service of a 3G network, the execution main bodies of the step 801 and the step 1101 may be the network-side device. At this time, step 801 and step 1101 in the method provided by the embodiment of the present invention may be replaced by step 1401 and step 1402, respectively. Exemplarily, as shown in fig. 14, a flowchart of another method for implementing call waiting according to an embodiment of the present invention is shown. In fig. 14, step 801 included in the method shown in fig. 8 described above may be replaced with step 1401:

s1401, in the process of establishing a call between the first UE and the second UE, the network side apparatus determines that the first UE is a calling UE.

S1402, in the process of establishing a call between the first UE and the second UE, the network side device determines that the first UE is called UE.

Illustratively, the above steps 1401 and 1402 may be implemented by the above MSC. At this time, the network side device provided by the embodiment of the present invention is an MSC.

Generally, in the process of performing a call service, a UE supporting the VoLTE technology may autonomously determine whether it is a calling UE or a called UE, while a UE supporting only the 3G technology (which may also be downward compatible with the 2G technology) may not autonomously determine whether it is a calling UE or a called UE.

It should be noted that the method for implementing call waiting provided in the embodiment of the present invention is applied to a voice service of a 3G network (that is, a subscribed UE is a UE that only supports a 3G technology). At this time, even if the subscribed UE supporting the 3G technology cannot determine whether it is the calling UE or the called UE, the network-side device may determine whether the subscribed UE is the calling UE or the called UE. Therefore, the UE only supporting the 3G technology can execute the method for realizing call waiting provided by the embodiment of the invention, and important calls are prevented from being missed.

In another specific embodiment, a third application scenario provided in the embodiment of the present invention is that the first UE and the second UE are in a call, and whether the first UE is a calling UE or a called UE. Referring to step 601a and steps 601 to 607 included in the method for implementing call waiting shown in the above embodiment, in a third application scenario, the method for implementing call waiting provided in the embodiment of the present invention may further include step 1501a and steps 1501 to 1507. Exemplarily, as shown in fig. 15, a flowchart of another method for implementing call waiting according to an embodiment of the present invention is shown. Steps 1501 to 1507 may be included in the method illustrated in fig. 15:

s1501a, in the process of the first UE talking with the second UE, the third UE sends a third party call request to the network side apparatus.

S1501, in the process of the first UE and the second UE communicating, the network side device receives a third party call request initiated by a third UE.

S1502, the network side device sends the third party call request to the first UE.

S1503, during the process of establishing a call between the first UE and the second UE, the first UE receives a third party call request sent by a third UE through the network side device.

S1504, the first UE sends an idle response to the network side device according to the third party call request.

S1505, the network side device receives the idle response sent by the first UE.

S1506, the first UE generates a third party call prompt tone and/or a third party caller identification according to the third party call request.

S1507, the network device plays the call waiting tone to the third UE according to the idle response.

It should be noted that, for the detailed description of 1501a and steps 1501 to 1507, reference may be made to the detailed description of step 601a and steps 601 to 607 in the foregoing embodiments, and no further description is given here in the embodiments of the present invention.

In another possible implementation manner of the third application scenario provided in the embodiment of the present invention, the method for implementing call waiting shown in fig. 15 may further include steps 1508 to 1510:

s1508, in the process of the first UE talking with the second UE, the first UE answers the call initiated by the third UE through the network side device, so that the network side device plays the call hold prompt tone to the second UE.

The call hold prompt tone is used for indicating that the call between the first UE and the second UE is in a call hold state. Illustratively, the call hold alert tone provided by embodiments of the present invention herein may be a "beep" sound.

It should be noted that, in this embodiment of the present invention, only the first UE (subscribed UE) in the third application scenario is taken as an example, and the method for implementing call waiting provided in the embodiment of the present invention is described. For example, referring to the display interface shown in fig. 7, the UE1 provided by the embodiment of the present invention may display the display interface 161 shown in fig. 16, and show the user name and phone number of the UE2 and the call duration of the UE1 and the UE2 to the user. The description of each option shown in fig. 16 may refer to the description related to each option in fig. 7 in the foregoing embodiment, and is not repeated here.

Likewise, in the third application scenario, when the UE1 receives a call initiated by the UE3, the display interface of the UE1 may display not only the user name and the phone number of the UE2, but also the user name and the phone number of the UE 3.

Exemplarily, as shown in fig. 17, a schematic diagram of another display interface provided for the embodiment of the present invention is shown. In the third application scenario described above, a display interface ("incoming call alert" interface) is shown in fig. 17, where a call originated by UE3 is received while UE1 is talking to UE 2. An option 1711, an option 1712, an option 1713, and an option 1714 are included in the "incoming call prompt" interface 171 shown in fig. 17. Here, the detailed description of the option 1711, the option 1712, the option 1713, and the option 1714 in the above embodiment may refer to the detailed description of the option 911, the option 912, the option 913, and the option 914 in the above embodiment.

S1509, the network side device controls the first UE to answer the call initiated by the third UE.

S1510, the network device plays a call hold alert tone to the second UE.

In another possible implementation manner of the third application scenario provided in the embodiment of the present invention, the method for implementing call waiting shown in fig. 15 may further include steps 1507 to 1509:

s1511, the first UE rejects the call initiated by the third UE through the network side device, and the network side device plays the call failure prompt tone to the third UE.

At this time, the first UE and the second UE continue normal conversation. For example, the UE1 continues to have a normal call with the UE 2.

S1512, the network side device controls the first UE to reject the call initiated by the third UE.

S1513, the network side device plays the call failure prompt tone to the third UE.

In another possible implementation manner, the method for implementing call waiting shown in fig. 15 may further include steps 1510 to 1512:

s1514, the first UE ignores the call initiated by the third UE through the network side device, and makes the network side device play a call failure prompt tone to the third UE after a preset time.

S1515, the network side apparatus controls the first UE to ignore the call initiated by the third UE.

S1516, the network side device plays the call failure prompt tone to the third UE after the preset time.

Similarly, for the detailed description of the steps 1508 to 1516, reference may be made to the description related to the steps 802, 802a, 803a, 804a-1, 804a-2, 805a-1, and 805a-2 in the foregoing embodiment, and no further description is given here in the embodiment of the present invention.

It should be noted that, the method for implementing call waiting provided in the embodiment of the present invention may not only enable the subscribed UE that is establishing a call to execute a call waiting service, but also enable the subscribed UE that is establishing a call to execute a call waiting service. Therefore, the signed UE can execute the call waiting service in different scenes, and further avoid missing important calls.

The above-mentioned scheme provided by the embodiment of the present application is introduced mainly from the perspective of interaction between the first UE and the network-side device and other devices. It is understood that, in order to implement the above functions, the first UE and the network side device include corresponding functional modules for performing the respective functions. Those skilled in the art will readily appreciate that the exemplary first UE, network cabinet apparatus, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or a combination of hardware and computer software. 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, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The present embodiment provides the first UE to implement the foregoing method embodiments, and specifically, the first device may be divided according to the foregoing method example, for example, each module or unit may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module may be implemented in the form of hardware, or may be implemented in the form of a software module or unit. The division of the modules or units in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation.

Fig. 18 shows a schematic diagram of a possible structure of the first UE involved in the above embodiments. As shown in fig. 18, the first UE 1800 may include: a receiving module 1801, a sending module 1802, and a processing module 1803.

The receiving module 1801 is configured to support the first UE 1800 to perform step 603, step 1503 in the above method embodiment, and/or other processes for the techniques described herein. The above-described transmitting module 1802 is used to support the first UE 1800 to perform step 604 in the above-described method embodiments, and/or other procedures for the techniques described herein. The processing module 1803 is configured to enable the first UE 1800 to perform step 606, step 608, step 802-step 805, step 1102-step 1104, step 1506, step 1508, step 1511, and step 1514 in the above-described method embodiments, and/or other processes for the techniques described herein.

In a specific embodiment, fig. 18 shows another possible structural diagram of the first UE involved in the foregoing embodiments. As shown in fig. 19, the first UE 1800 may further include: a module 1804 is determined.

Wherein the determining module 1804 is configured to enable the first UE 1800 to perform steps 801 and 1101 of the above-described method embodiments, and/or other processes for the techniques described herein.

Of course, the first UE 1800 includes, but is not limited to, the above listed unit modules. In addition, the functions that can be specifically realized by the modules also include, but are not limited to, the functions corresponding to the method steps described in the above examples.

Illustratively, the first UE 1800 may further include a storage module, a display module, and an input module. The storage module may be configured to store an instruction for the first UE to execute the call service. The display module may be configured to display, to the user, information related to a call service performed with the first UE, such as a user name and a phone number corresponding to the UE that has a call with the first UE. The input module may be configured to enable a user to input a phone number of another UE that establishes a call with the first UE. For the detailed description of other units of the first UE 1800 and each unit of the first UE 1800, reference may be made to the detailed description of the corresponding method steps, which is not described herein again in the embodiments of the present application.

In the case of an integrated Unit, the Processing module 1803, the determining module 1804, and the like may be integrated into a Processing Unit, which may be a processor or a controller, such as a CPU, a Graphics Processing Unit (GPU), a general purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or execute the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processing unit may also be a combination of computing functions, e.g., comprising one or more microprocessors, a combination of a DSP and a microprocessor, or the like. The storage module may be a memory.

When the processing unit is a processor and the storage module is a memory, the first UE according to the embodiment of the present application may be the first UE shown in fig. 5 in the above embodiment. At this time, the receiving module 1801 and the transmitting module 1802 may be integrated in the communication interface 53 shown in fig. 5. The processing module 1803 and the determining module 1804 may be integrated into the processor 21 shown in fig. 5. The storage module of the first UE may be implemented by the memory 52 shown in fig. 5, the display module may be implemented by the display 56 shown in fig. 5, and the input module may be implemented by the input device 57 shown in fig. 5.

The memory 52 is configured to store at least one instruction, and when the UE shown in fig. 5 runs, the one or more processors 51 execute the at least one instruction stored in the memory 52, so as to enable the UE to perform the method for implementing call waiting as in the above embodiments.

An embodiment of the present invention further provides a computer storage medium, where a computer program code is stored in the computer storage medium, and when the one or more processors 51 of the UE shown in fig. 5 execute the computer program code, the UE executes the relevant method steps in any of the above-mentioned embodiments to implement the method for implementing call waiting in the above-mentioned embodiments.

Embodiments of the present invention further provide a computer program product, which when run on a computer, causes the computer to execute the relevant method steps in any of the above embodiments to implement the method for implementing call waiting in the above embodiments.

In addition, the UE, the first UE 1800, the computer storage medium, or the computer program product shown in fig. 5 provided in the embodiment of the present invention are all configured to execute the corresponding method provided above, and therefore, the beneficial effects achieved by the method can refer to the beneficial effects in the corresponding method provided above, which are not described herein again.

Fig. 20 shows a schematic diagram of a possible structure of the network-side device involved in the above embodiment. As shown in fig. 20, the network-side device 2000 may include: a receiving module 2001 and a transmitting module 2002.

The receiving module 2001 is used to support the network-side device 2000 to perform the steps 601, 605, 1501 and 1505 in the above method embodiments, and/or other processes for the techniques described herein. The sending module 2002 is configured to support the network-side device 2000 to perform step 602, step 607, step 804a-2, step 805a-2, step 1102a-2, step 1103a-2, step 1104a-2, step 1502, step 1510, step 1513, and step 1516 in the foregoing method embodiments, and/or other processes for the techniques described herein.

Further, fig. 21 shows another possible structural diagram of the network-side device involved in the above embodiment. As shown in fig. 21, the network-side device 2000 may further include: a processing module 2003.

The processing module 2003 is configured to support the network-side device 2000 to perform steps 802a, 803a, 804a-1, 805a-1, 1102a-1, 1103a-1, 1104a-1, 1509, 1512, and 1515 in the foregoing method embodiments, and/or other processes for the technologies described herein.

Further, fig. 22 shows another possible structural diagram of the network-side device involved in the above embodiment. As shown in fig. 21, the network-side device 2000 may further include: a determination module 2004.

Wherein the determining module 2004 is used for supporting the network-side device 2000 to perform the steps 1301, 1401, and 1402 in the above method embodiments, and/or other processes for the techniques described herein.

Illustratively, the network-side device 2000 may further include a storage module. The storage module may be configured to store an instruction for controlling the first UE to talk with the second UE or the third UE. For the detailed description of other units of the network-side device 2000 and each unit of the network-side device 2000, reference may be made to the detailed description of the corresponding method steps, which is not described herein again in this embodiment of the present application.

In case of an integrated unit, the processing module 2003, the determining module 2004, etc. may be implemented in one integrated processing unit, which may be a processor or a controller, for example, a CPU, a general processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or execute the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processing unit may also be a combination of computing functions, e.g., comprising one or more microprocessors, a combination of a DSP and a microprocessor, or the like. The storage module may be a memory.

When the processing unit is a processor and the storage module is a memory, the network-side device according to the embodiment of the present application may be the network-side device shown in fig. 4a in the above embodiment. At this time, the above-described receiving module 2001 and transmitting module 2002 may be integrated in the communication interface 43a shown in fig. 4 a. The processing module 2003 and the determination module 2004 may be integrated into the processor 41a shown in fig. 4 a. The storage module of the network-side device may be implemented by the memory 424 shown in fig. 4 a.

When the network-side device 40a shown in fig. 4a operates, the one or more processors 41a execute the at least one instruction stored in the memory 42a, so that the network-side device 40a executes the method for implementing call waiting as in the above embodiment.

An embodiment of the present invention further provides a computer storage medium, in which computer program codes are stored, and when one or more processors 41a of a network-side device 40a execute the computer program codes, the network-side device 40a executes relevant method steps in any of the above-mentioned embodiments to implement the method for implementing call waiting in the above-mentioned embodiments.

The network-side device 40a, the network-side device 2000, the computer storage medium, or the computer program product provided in the embodiments of the present invention are all configured to execute the corresponding methods provided above, and therefore, the beneficial effects achieved by the present invention can refer to the beneficial effects in the corresponding methods provided above, which are not described herein again.

Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, 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. For the specific working processes of the system, the apparatus and the unit described above, reference may be made to the corresponding processes in the foregoing method embodiments, and details are not described here again.

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

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

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

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) or a processor to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: flash memory, removable hard drive, read only memory, random access memory, magnetic or optical disk, and the like.

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

Claims

1. A method for implementing call waiting, comprising:

in the process of establishing a call between first User Equipment (UE) and second UE, the first UE receives a third party call request sent by third UE through a network side device, the first UE signs a call waiting service, and the third party call request is used for indicating the third UE to request the call with the first UE;

the first UE sends an idle response to the network side device according to the third party call request, wherein the idle response is used for indicating that the first UE line is idle and the first UE is establishing a call or the first UE is calling;

the first UE generates a third party call prompt tone and/or a third party incoming call display according to the third party call request, wherein the third party call prompt tone and the third party incoming call display are both used for indicating that the third UE initiates a call to the first UE;

in the process of establishing a call between the first UE and the second UE, if the first UE is a called UE:

the first UE answering the call initiated by the third UE comprises the following steps:

the first UE answers the call initiated by the third UE through a network side device, so that the network side device plays a call failure prompt tone aiming at the second UE to the second UE, wherein the call failure prompt tone aiming at the second UE is used for indicating that the call initiated by the second UE is not connected;

the first UE rejects the call initiated by the third UE, including:

the first UE rejects the call initiated by the third UE through a network side device, so that the network side device plays a call failure prompt tone to the third UE, wherein the call failure prompt tone is used for indicating that the call initiated by the third UE is not connected;

the first UE ignores the call initiated by the third UE, including:

and the first UE ignores the call initiated by the third UE through a network side device, so that the network side device plays a call failure prompt tone to the third UE after a preset time.

2. The method of claim 1, wherein the process of the first UE establishing a call with the second UE comprises:

the method comprises the steps that a calling UE in the first UE and the second UE initiates a call and a called UE does not ring, or the steps that the calling UE in the first UE and the second UE initiates a call and the called UE rings.

3. The method of claim 2, wherein the first UE determines that the first UE is a calling UE during the process of establishing a call with the second UE;

the first UE cancels the call to the second UE through a network side device;

the first UE answers the call initiated by the third UE through a network side device;

the first UE rejects the call initiated by the third UE, including:

the first UE ignores the call initiated by the third UE, including:

and the first UE ignores the call initiated by the third UE through a network side device, so that the network side device plays the call failure prompt tone to the third UE after a preset time.

4. The method of claim 1, further comprising:

in the process of establishing a call between the first UE and the second UE, the first UE receives a third party call request sent by a third UE through a network side device;

the first UE sends the idle response to the network side device according to the third party call request;

the first UE generates the third party calling prompt tone and/or the third party caller identification according to the third party calling request;

the first UE answers a call initiated by the third UE through a network side device, so that the network side device plays a call hold prompt tone to the second UE, wherein the call hold prompt tone is used for indicating that the call between the first UE and the second UE is in a call hold state;

or, the first UE rejects the call initiated by the third UE through the network side device, and makes the network side device play the call failure prompt tone to the third UE;

or, the first UE ignores, through the network-side device, the call initiated by the third UE, and makes the network-side device play the call failure alert tone to the third UE after a preset time.

5. A method for implementing call waiting, comprising:

in the process of establishing a call between first UE and second UE, a network side device receives a third party call request initiated by third UE, the first UE signs a call waiting service, and the third party call request is used for the third UE to request the call between the third UE and the first UE;

the network side device sends the third party call request to the first UE;

the network side device receives an idle response sent by the first UE, wherein the idle response is used for indicating that the first UE line is idle and the first UE is establishing a call or the first UE is calling;

the network side device plays a call waiting prompt tone to the third UE according to the idle response, wherein the call waiting prompt tone is used for indicating that a call initiated from the third UE to the first UE is in a call waiting state;

the network side device controls the first UE to answer the call initiated by the third UE;

the network side device plays a call failure prompt tone aiming at the second UE to the second UE, wherein the call failure prompt tone aiming at the second UE is used for indicating that a call initiated by the second UE is not connected;

alternatively, the first and second electrodes may be,

the network side device controls the first UE to reject the call initiated by the third UE;

the network side device plays a call failure prompt tone to the third UE, wherein the call failure prompt tone is used for indicating that a call initiated by the third UE is not connected;

alternatively, the first and second electrodes may be,

the network side device controls the first UE to ignore the call initiated by the third UE;

and the network side device plays the call failure prompt tone to the third UE after preset time.

6. The method of claim 5, further comprising:

in the process of establishing a call between the first UE and the second UE, if the first UE is a calling UE:

the network side device controls the first UE to cancel the call to the second UE;

alternatively, the first and second electrodes may be,

7. The method of claim 5 or 6, further comprising:

in the process of establishing a call between the first UE and the second UE, the network side apparatus determines that the first UE is a calling UE, or determines that the first UE is a called UE.

8. The method of claim 5, further comprising:

in the process of the first UE and the second UE communicating, the network side device receives the third party call request initiated by the third UE;

the network side device sends the third party call request to the first UE;

the network side device receives the idle response sent by the first UE;

the network side device plays a call hold prompt tone to the second UE, wherein the call hold prompt tone is used for indicating that the conversation between the first UE and the second UE is in a conversation hold state;

alternatively, the first and second electrodes may be,

9. The method according to any of claims 5-6, wherein before the network-side device sends the third party call request to the first UE, further comprising:

the network side device determines that the first UE is a registered UE, where the first UE indicates that the first UE can perform a basic call service for the registered UE.

10. A first User Equipment (UE), comprising:

the system comprises a receiving module, a sending module and a receiving module, wherein the receiving module is used for receiving a third party call request sent by a third UE through a network side device in the process of establishing a call between the first UE and a second UE, the first UE signs a call waiting service, and the third party call request is used for indicating the third UE to request the call with the first UE;

a sending module, configured to send an idle response to the network-side device according to the third-party call request received by the receiving module, where the idle response is used to indicate that the first UE line is idle and the first UE is executing a call service;

a processing module, configured to generate a third-party call alert tone and/or a third-party incoming call display according to the third-party call request received by the receiving module, where the third-party call alert tone and the third-party incoming call display are both used to indicate that the third UE is initiating a call to the first UE; receiving the call initiated by the third UE, or rejecting the call initiated by the third UE, or ignoring the call initiated by the third UE;

the determining module is further configured to determine that the first UE is a called UE in a process of establishing a call between the first UE and the second UE;

the processing module is further specifically configured to answer the call initiated by the third UE through a network side device, so that the network side device plays a call failure notification tone for the second UE to the second UE, where the call failure notification tone for the second UE is used to indicate that the call initiated by the second UE is not connected; or, rejecting, by a network side apparatus, a call initiated by the third UE, so that the network side apparatus plays a call failure alert tone to the third UE, where the call failure alert tone is used to indicate that the call initiated by the third UE is not connected; or, ignoring the call initiated by the third UE through a network side device, so that the network side device plays a call failure prompt tone to the third UE after a preset time.

11. The first UE of claim 10, wherein the process of the first UE establishing a call with the second UE comprises:

12. The first UE of claim 11, further comprising:

the determining module is configured to determine that the first UE is a calling UE in a process of establishing a call between the first UE and the second UE;

the processing module is specifically configured to cancel, by a network side device, a call to the second UE; answering the call initiated by the third UE through a network side device; or, rejecting, by a network side apparatus, a call initiated by the third UE, so that the network side apparatus plays a call failure alert tone to the third UE, where the call failure alert tone is used to indicate that the call initiated by the third UE is not connected; or, ignoring the call initiated by the third UE through the network side device, so that the network side device plays the call failure prompt tone to the third UE after a preset time.

13. The first UE of claim 10, wherein the receiving module is further configured to, in a process that the first UE establishes a call with the second UE, receive a third party call request sent by a third UE through a network side device; the processing module is further configured to, in a process of a call between the first UE and the second UE, answer a call initiated by the third UE through a network side device, so that the network side device plays a call hold prompt tone to the second UE, where the call hold prompt tone is used to indicate that the call between the first UE and the second UE is in a call hold state; or, the network side apparatus rejects the call initiated by the third UE, and causes the network side apparatus to play a call failure prompt tone to the third UE, where the call failure prompt tone is used to indicate that the call initiated by the third UE is not connected; or, ignoring the call initiated by the third UE through the network side device, and enabling the network side device to play the call failure prompt tone to the third UE after a preset time.

14. A first UE, comprising:

one or more processors, memory, communication interfaces, displays, inputs, and buses;

the memory is configured to store at least one instruction, the one or more processors and the memory, the communication interface, the display, and the input are connected via the bus, and when the first UE is running, the one or more processors execute the at least one instruction stored in the memory to cause the first UE to perform the method of implementing call waiting of any of claims 1-4.

15. A computer storage medium, comprising: at least one instruction;

when the at least one instruction is executed on a computer, the computer is caused to perform the method of implementing call waiting of any of claims 1-4.

16. A network-side apparatus, comprising:

a receiving module, configured to receive a third party call request initiated by a third UE in a process of establishing a call between a first UE and a second UE, where the first UE signs a call waiting service, and the third party call request is used for the third UE to request the call with the first UE;

a sending module, configured to send the third party call request received by the receiving module to the first UE;

the receiving module is further configured to receive an idle response sent by the first UE, where the idle response is used to indicate that the first UE line is idle;

the sending module is further configured to play a call waiting alert tone to the third UE according to the idle response received by the receiving module, where the call waiting alert tone is used to indicate that a call initiated by the third UE to the first UE is in a call waiting state;

a processing module, configured to, in a process of establishing a call between the first UE and the second UE, if the first UE is a called UE: controlling the first UE to answer the call initiated by the third UE; controlling the first UE to reject the call initiated by the third UE; controlling the first UE to ignore the call initiated by the third UE;

the sending module is further configured to play a call failure notification tone for the second UE to the second UE, where the call failure notification tone for the second UE is used to indicate that a call initiated by the second UE is not connected; and playing the call failure prompt tone to the third UE after a preset time, wherein the call failure prompt tone is used for indicating that the call initiated by the third UE is not connected.

17. The network-side apparatus according to claim 16, further comprising:

the processing module is configured to, in a process of establishing a call between the first UE and the second UE, and when the first UE is a calling UE: controlling the first UE to cancel the call to the second UE; controlling the first UE to answer the call initiated by the third UE; or, controlling the first UE to reject the call initiated by the third UE; or, controlling the first UE to ignore the call initiated by the third UE;

the sending module is further configured to play a call failure prompt tone to the third UE, where the call failure prompt tone is used to indicate that a call initiated by the third UE is not connected; and playing the call failure prompt tone to the third UE after a preset time.

18. The network-side apparatus according to claim 16 or 17, further comprising:

a determining module, configured to determine that the first UE is a calling UE or a called UE in a process of establishing a call between the first UE and the second UE.

19. The network-side apparatus according to claim 16, further comprising:

the receiving module is further configured to receive the third party call request initiated by the third UE in a process of a call between the first UE and the second UE;

the sending module is further configured to send the third party call request to the first UE; and playing a call hold prompt tone to the second UE, wherein the call hold prompt tone is used for indicating that the conversation between the first UE and the second UE is in a call hold state.

20. The network-side apparatus of any one of claims 16-17, wherein the determining module is further configured to determine that the first UE is a registered UE, where the first UE being a registered UE indicates that the first UE can perform a basic call service.

21. A network-side apparatus, comprising:

one or more processors, memory, communication interfaces, and buses;

the memory is configured to store at least one instruction, and the one or more processors and the memory and the communication interface are connected via the bus, and when the network-side device is running, the one or more processors execute the at least one instruction stored in the memory to cause the network-side device to execute the method for implementing call waiting according to any one of claims 5 to 9.

22. A computer storage medium, comprising: at least one instruction;

when the at least one instruction is executed on a computer, the computer is caused to perform the method of implementing call waiting of any of claims 5-9.