WO2013091310A1 - Procédé, dispositif et système permettant à un terminal d'exécuter une mise en attente d'appel - Google Patents
Procédé, dispositif et système permettant à un terminal d'exécuter une mise en attente d'appel Download PDFInfo
- Publication number
- WO2013091310A1 WO2013091310A1 PCT/CN2012/072385 CN2012072385W WO2013091310A1 WO 2013091310 A1 WO2013091310 A1 WO 2013091310A1 CN 2012072385 W CN2012072385 W CN 2012072385W WO 2013091310 A1 WO2013091310 A1 WO 2013091310A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- terminal
- call
- mrs
- tone
- module
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/428—Arrangements for placing incoming calls on hold
- H04M3/4288—Notifying a called subscriber of an incoming call during an ongoing call, e.g. Call Waiting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1096—Supplementary features, e.g. call forwarding or call holding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
- H04L65/1104—Session initiation protocol [SIP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/16—Communication-related supplementary services, e.g. call-transfer or call-hold
Definitions
- the present invention relates to the field of communications, and in particular, to a method, apparatus, and system for implementing a call waiting for a terminal that does not support a second incoming call. Background technique
- the so-called call waiting means that when the user receives a new call request in an already existing call, the user will hear a call waiting tone, indicating that another user is waiting to talk to. At the same time, the new calling party is notified to wait for the call, and a call waiting prompt is played to the calling party.
- the user can choose to answer the new call, or can choose to reject the new call, or can answer the new call without answering.
- a user terminal (User Equipment, UE) B, which can be simply referred to as a terminal, is an NGN (Next Generation Network) or IMS (IP Multimedia Subsystem) user, and subscribes to call waiting.
- Service, UE A and UE C may be NGN or IMS users, or other networks such as GSM (Global System for Mobile communication), CDMA (Code Division Multiple Access), PSTN (Public Switched Telephone Network, public switched telephone network) and other users.
- GSM Global System for Mobile communication
- CDMA Code Division Multiple Access
- PSTN Public Switched Telephone Network, public switched telephone network
- Step 01 UE A sends an Invite request to the application server (AS), and the request number is UE B.
- the UE B When the UE B is in a call with the UE C, the UE A sends the Invite request to the UE B.
- the Invite request carries the Session Description Protocol (SDP) information of the UE A, including the IP address, port number, audio and video attributes, Encoding format, etc.
- SDP Session Description Protocol
- Step 02 The AS sends an Invite request to UE B, and the request number is UE B.
- the UE returns 180Ring (XML (Extensible Markup Language)) or 182 (Queued) to the AS to queue the temporary response.
- UE B supports the second incoming call and has the ability to answer the second incoming call, so it returns 180 Ring (XML) or 182Queued, indicating that UE B has received a new call request and is in a ringing state or queued state.
- 180Ring XML (Extensible Markup Language)
- 182 Queued
- Step 04 The AS sends an Invite request to the Media Resource Server (MRS), where the SDP information of the UE A is carried.
- the AS receives 180Ring (XML) or 182Queued, performs call waiting service logic, and wants to play a call waiting tone for UE A, thus establishing a playback channel of UE A to MRS.
- MRS Media Resource Server
- Step 05 The MRS returns a 200 OK final response to the AS, which carries its own SDP message.
- Step 06 the AS sends an ACK acknowledgement message to the MRS.
- Step 07 The AS returns a 180Ring temporary response to the UE A, where the SDP information of the MRS is carried.
- step 08 the AS sends an INFO (Notification) request to the MRS, instructing the MRS to play the UE A.
- INFO Notification
- step 09 the MRS returns a 200 OK response to the AS.
- UE A listens to the call waiting tone, such as: Please do not hang up, the call you are making is in a call.
- Step 10 UE B sends a 200 OK (INVITE) final response to the AS, which carries its own SDP information.
- UE B keeps UE C, UE C listens to the call hold tone, and UE B picks up the phone.
- Step 11 The AS sends a BYE (end) request to the MRS.
- the AS stops playing the call waiting tone for UE A.
- step 12 the MRS returns a 200 OK (BYE) successful response to the AS.
- Step 13 The AS sends an UPDATE (Update) request to the UE A, where the SDP information of the UE B is carried.
- UPDATE Update
- Step 14 UE A returns a 200 OK (UPDATE) successful response to the AS, where SDP information of UE A.
- Step 15 the AS returns a 200 OK (INVITE) final response to the UEA.
- Step 16 UE A sends an ACK acknowledgement message to the AS.
- Step 17 The AS sends an ACK acknowledgement message to UE B. So far, UE A and UE B have completed SDP negotiation and entered the call state.
- the call waiting service is required for the terminal, that is, the second incoming call needs to be supported, and the call holding function can be supported.
- the call waiting service is required for the terminal, that is, the second incoming call needs to be supported, and the call holding function can be supported.
- most terminals cannot meet the requirements of the call waiting service for the terminal, but return the Busy (busy) state directly to the second incoming call, so that the terminal that does not support the second incoming call is perceived when talking with the opposite end.
- the main object of the present invention is to provide a method, apparatus and system for implementing call waiting for a terminal that does not support the second incoming call, so that the terminal that does not support the second incoming call can also implement call waiting.
- a method for implementing call waiting by a terminal that does not support the second incoming call includes:
- the third terminal dials the first terminal that does not support the second incoming call
- the application server AS supporting terminal communication controls communication between the first terminal and the third terminal.
- the AS receives the busy response of the first terminal, and then plays a call waiting tone to the third terminal, and also plays the second incoming call to the first terminal. Prompt tone and receive number.
- the AS also adds the first terminal and the second terminal to the conference when the communication between the first terminal and the third terminal is controlled.
- the method for the AS to join the first terminal and the second terminal to the conference is:
- the AS applies for the conference resource to the media resource server MRS, and adds the call of the first terminal and the second terminal to the conference based on the resource.
- the AS plays a call hold tone to the second terminal, and bridges the third terminal with the first terminal;
- the AS plays a failure prompt tone to the third terminal
- the AS releases the call of the third terminal.
- the method further includes: after the AS plays the failure prompt tone to the third terminal, releasing the call of the third terminal; and,
- the AS stops playing the call hold tone for the second terminal, and bridges the second terminal with the first terminal;
- the AS releases the call of the third terminal and the second terminal.
- the method further includes: the first terminal subscribes to the call waiting service on the AS in advance.
- a system for implementing a call waiting for a terminal that does not support the second incoming call includes a terminal, an AS; the terminal includes a first terminal, a second terminal, and a third terminal;
- the third terminal is configured to dial the first terminal that does not support the second incoming call
- the AS supporting terminal communication is used to control communication between the first terminal and the third terminal.
- the AS is configured to receive a busy response of the first terminal, and then play a call waiting tone to the third terminal, and play a second call to the first terminal, when the communication between the first terminal and the third terminal is controlled. Enter the tone and receive the number.
- the AS is further configured to join the first terminal and the second terminal to the conference when the communication between the first terminal and the third terminal is controlled.
- the system further includes an MRS, where the AS applies the conference resource to the MRS when the first terminal and the second terminal are added to the conference, and adds the call of the first terminal and the second terminal to the conference based on the resource. in.
- the AS is configured to play a call hold tone to the second terminal, and bridge the third terminal with the first terminal;
- the AS is used to play a failure prompt tone to the third terminal;
- the AS is used to release the call of the third terminal.
- the AS After the AS plays the failure prompt tone to the third terminal, the AS also releases the call of the third terminal; and,
- the AS is further configured to stop playing the call hold tone for the second terminal, and bridge the second terminal with the first terminal;
- the AS is also used to release the call of the third terminal and the second terminal.
- the first terminal is further configured to sign a call waiting service on the AS in advance.
- a device for implementing a call waiting for a terminal that does not support the second incoming call includes: a receiving determining module and a call bridging module; wherein
- the receiving determining module is configured to: when the first terminal talks with the second terminal, learn that the third terminal dials the first terminal that does not support the second incoming call; and accordingly, obtains that the first terminal and the third terminal are to be controlled The result of the communication between the two;
- the call bridging module is configured to control according to the judgment result of the receiving judging module The communication between the first terminal and the third terminal is made.
- the receiving determining module is configured to receive a call event including an incoming call request, a user ringing, and a user off-hook.
- the device further includes a sound mixing module, configured to receive a busy response of the first terminal when communicating between the first terminal and the third terminal, and then play a call waiting tone to the third terminal, The terminal plays the second incoming call tone and receives the number.
- a sound mixing module configured to receive a busy response of the first terminal when communicating between the first terminal and the third terminal, and then play a call waiting tone to the third terminal, The terminal plays the second incoming call tone and receives the number.
- the receiving the determining module is further configured to add the first terminal and the second terminal to the conference based on the connected MRS, when the communication between the first terminal and the third terminal is controlled.
- the receiving determining module when adding the first terminal and the second terminal to the conference, is used to:
- the device further includes a call release module; when controlling communication between the first terminal and the third terminal,
- the play mixing module is configured to play a call hold tone to the second terminal, where the call bridge module is configured to bridge the third terminal with the first terminal;
- the playback mix module is configured to play a failure prompt tone to the third terminal
- the call release module is configured to release the call of the third terminal.
- the call release module is further configured to: release the call of the third terminal after the playback mix module plays the failure prompt tone to the third terminal;
- the playback mixing module is further configured to stop playing the call hold tone for the second terminal, where the call bridge module is further configured to use the second terminal Bridging a call with the first terminal;
- the call release module is further configured to release the call of the third terminal and the second terminal.
- the first terminal is further configured to sign a call waiting service on the AS in advance.
- the device is disposed in the AS.
- the present invention does not support the method, device and system for implementing call waiting for the second incoming call terminal.
- the third terminal can dial the first terminal that does not support the second incoming call.
- the AS supporting terminal communication controls communication between the first terminal and the third terminal. Therefore, the present invention can ensure that a terminal that does not support the second incoming call can also implement call waiting.
- 1 is a logic flow diagram of a prior art call waiting service
- FIG. 2 is a schematic structural diagram of a system of the present invention
- 3a and 3b are schematic diagrams of logic flow according to an embodiment of the present invention.
- FIG. 4 is a schematic block diagram of a call waiting application server according to an embodiment of the present invention.
- FIG. 5 is a schematic flowchart of a user having no call waiting authority according to an embodiment of the present invention.
- FIG. 6 is a schematic flowchart of joining an original call party to a conference according to an embodiment of the present invention.
- FIG. 7 is a schematic flowchart of a process for a user to answer a new call according to an embodiment of the present invention.
- FIG. 8 is a schematic flowchart of a user rejecting a new call according to an embodiment of the present invention.
- FIG. 9 is a schematic flowchart of a user not responding to a new call according to an embodiment of the present invention.
- FIG. 10 is a schematic diagram of a process for implementing call waiting for a terminal that does not support the second incoming call according to an embodiment of the present invention. detailed description
- FIG. 2 is a schematic structural diagram of a system according to the present invention. The following describes the function of the network element in FIG. 2 as follows: 1.
- UE A device used by a user to initiate a call, answer a call, and perform other call operations, such as
- C network or G network mobile phone PSTN terminal, IMS terminal, etc.
- AS Provides the underlying service capabilities, such as: call control, status 4, and bill generation.
- MRS provide voice media capabilities, generally for media servers (Media Server, MS), such as providing playback, receiving, mixing and other functions.
- Media Server Media Server
- the AS can negotiate with the MRS or the UE based on the call.
- the AS and the UE use the SIP protocol to communicate with each other.
- the AS and the MRS usually use the SIP protocol or MGCP.
- the media negotiation is performed between the UE and the MRS according to the codec format, the transceiver port, and the bandwidth transmission rate of the media packet at the time of the call, and the media stream is transmitted.
- Figure 2 is only a schematic diagram, hiding other unrelated IMS or NGN network topologies.
- the AS, the MRS, and the UE are connected to the IMS network or the NGN network.
- FIG. 3 The logic flow chart of the present invention is shown in FIG. 3, where UE B is an NGN or an IMS user, AS is a call waiting service application server, UE A and UE C may be NGN or IMS users, or may be other networks (such as GSM, CDMA, PSTN, etc.) Users.
- the process shown in Figure 3 includes the following steps:
- Steps 01, 1 ⁇ 8 and 11£ When calling, 1 ⁇ 8 dials 11£8.
- Step 02 UE B does not support the second incoming call, returns the busy final response, and the response arrives.
- Step 03 If the UE B signs the call waiting service on the AS, step 05 is performed; otherwise, step 04 is performed.
- the AS releases the UE A to the UE A to play a failure tone (eg, the call you are making is in a call, please dial later). The process ends.
- Step 05 the AS plays a call waiting tone to UE A, such as: Please do not hang up, the call you are making is in a call.
- Step 06 The AS applies for the conference resource to the MRS, and adds the call of the UE B and the UE C to the conference based on the resource.
- step 07 the AS plays the second incoming call prompt tone to the UE B (for example, if you have a new incoming call, press 1 for the call, 2 for the rejection, and press the 2) to receive the number, and the operation of the prompt tone and the receive number can be cycled. Time (such as 1 minute). At this time, the UE B can talk to the UE C or simultaneously perform the sound collection and reception operations.
- Step 08 If the AS receives the content of the UE B as 1, then step 12 is performed; otherwise, step 09 is performed.
- Step 09 If the AS receives the content of the UE B as 2, step 11 is performed; otherwise, step 10 is performed.
- Step 10 After the playback time is over, the AS releases UE A. Release the mix and play resources, and bridge the call between UE B and UE C. The process ends.
- Step 11 The AS plays a failure prompt tone to UE A, such as: The call you are making is in a call, please dial later. Then, the AS releases UE A, and releases the mixing resource and the playback resource, and bridges the call between UE B and UE C. The process ends.
- Step 12 The AS keeps a call alert tone for the UE C.
- Step 13 The AS stops playing the call waiting tone for the UEA.
- Step 14 The AS bridges UE A and UE B, and UE A and UE B enter a call state. Step 15 If UE A hangs up when UE C is not on-hook, go to step 19; otherwise, go to step 16.
- Step 16 If UE B hangs up while UE C is not on-hook, go to step 18; otherwise, execute Step 17.
- Step 18 The AS releases UE A, UE C, and then releases the original call. The process ends.
- Step 19 The AS stops playing the call hold tone for the UE C.
- Step 20 The AS bridges UE C and UE B, and UE C and UE B re-enter the call state. The process ends.
- the receiving judging module receives various call events arriving at the AS, such as an incoming call request, a user ringing, and a user picking up the phone. For example, when the UE B returns to the busy state, it is used to determine whether the user has the call waiting for the service right, and performs subsequent processing.
- the sound mixing module is used to instruct the MRS to perform operations such as playing, collecting and collecting, and mixing the meeting, such as playing the UE A failure prompt or call waiting tone, playing the UE B and collecting the number, The UE C plays the call hold tone, and the UE B and the UE C mix the conference.
- the call bridge module is used to associate the calls of two users, so that two users enter the call state. In the present invention, it is used to bridge UE A and UE B, and bridge between UE B and UE C.
- the call release module is used for call release after the end of the process, such as a failure prompt tone, a call release after the user hangs up, and the like.
- the system including the above AS includes:
- the UE can access an existing related network (such as GSM, CDMA, PSTN, NGN or IMS). It can be a terminal under existing networks, such as GSM or CDMA handsets, PSTN fixed line, NGN or IMS terminals.
- the UE B is an NGN or an IMS user, and the UE A and the UE C may be NGN or IMS users, or may be other network users.
- the softswitch placed in the NGN or IMS core network, and SS (Softswitch, under the NGN network)
- the softswitch) or the S-CSCF (Serving Call Session Controller) under the IMS network is connected and connected to the MRS. It can realize user authentication, play collection, call bridging, call release, bill generation, etc. of call waiting service. It mainly includes a receiving judgment module, a sound mixing module, a call bridge module, a call release module, and the like.
- the MRS connected to the AS, through the AS's instructions for playback, playback, and mixing.
- the MRS is used to play related prompt sounds (such as call waiting prompts, call hold prompts) to the user terminal, or to play related prompt sounds to the user terminal and receive secondary dialing input of the user terminal, or to the user terminal. Join the meeting and mix.
- FIG. 5 is a schematic flowchart of a user's no call waiting right according to an embodiment of the present invention.
- UE B is an NGN or IMS user, but there is no subscription call waiting.
- the process shown in Figure 5 includes the following steps:
- Step 01 UE A sends an INVITE request to the AS, and the request number is UE B, and the INVITE request carries the SDP information of UE A. At this time, UE B and UE C are in a call.
- Step 02 The AS sends an INVITE request to the UE B, where the request number is the UE B, and the INVITE request carries the SDP information of the UE A.
- Step 03 UE B returns a final response of 486 Busy to the AS.
- UE B and UE C are in a call, and UE B does not support the second incoming call, so UE B returns to the busy state.
- Step 04 The AS sends an ACK acknowledgement message to UE B.
- Step 05 The AS sends an INVITE request to the MRS, where the SDP information of the UE A is carried.
- the AS judges that UE B does not have a call waiting service, and wants to cancel the UE A busy state.
- Step 06 The MRS returns a 200 OK (INVITE) final response to the AS, which carries its own SDP information.
- Step 07 The AS sends an ACK acknowledgement message to the MRS.
- step 08 the AS sends a 183 Session Process temporary response to the UE A, carrying the SDP information of the MRS.
- step 09 the AS sends an INFO notification request to the MRS, requesting the MRS to play a prompt tone to the UE A, for example: The call you are making is in a call, please dial again later.
- Step 10 the MRS returns a 200 OK ( INFO ) final response to the AS.
- Step 11 The MRS sends a BYE end request to the AS.
- the MRS playback ends, requesting to release the playback resource.
- step 12 the AS returns a 200 OK (BYE) final response to the MRS.
- step 13 the AS returns a 487 Terminated final response to UE A. The end of the playback,
- the AS releases UE A.
- Step 14 UE A sends an ACK acknowledgement message to the AS. The process ends.
- FIG. 6 is a schematic flowchart of a process in which an original call party joins a conference according to an embodiment of the present invention.
- UE B is an NGN or IMS user and subscribes to call waiting services.
- the process shown in Figure 6 includes the following steps:
- Step 01 UE A sends an INVITE request to the AS, and the request number is UE B, and the INVITE request carries the SDP information of UE A. At this time, UE B and UE C are in a call.
- Step 02 The AS sends an INVITE request to the UE B, where the request number is the UE B, and the INVITE carries the SDP information of the UE A.
- Step 03 UE B returns a final response of 486 Busy to the AS.
- UE B and UE C are in a call, and UE B does not support the second incoming call, so UE B returns to the busy state.
- Step 04 The AS sends an ACK acknowledgement message to UE B.
- Step 05 The AS sends an INVITE request to the MRS, and carries the SDP information of the UE A.
- the AS judges that the UE B has a call waiting service, and wants to put a call waiting tone for UE A.
- Step 06 The MRS returns a 200 OK (INVITE) final response to the AS, which carries its own SDP information.
- Step 07 The AS sends an ACK acknowledgement message to the MRS.
- Step 08 The AS sends a 180Ring temporary response to the UE A, where the SDP carrying the MRS information.
- Step 09 The AS sends an INFO notification request to the MRS, requesting the MRS to play the prompt tone to the UE A (for example, please do not hang up, the call you are making is in a call), and the cycle time is about 1 minute.
- Step 10 the MRS returns a 200 OK ( INFO ) final response to the AS.
- Step 11 The AS sends a REINVITE request to UE B.
- AS wants to join UE B to the conference.
- Step 12 UE B returns a 200 OK (REINVITE) final response to the AS, which carries its own SDP information.
- Step 13 The AS sends an INVITE request to the MRS, where the SDP information of the UE B is carried. Step 14.
- the MRS returns a 200 OK (INVITE) final response to the AS, which carries its own SDP information.
- Step 15 The AS sends an ACK acknowledgement message to the MRS.
- Step 16 The AS sends an ACK acknowledgement message to the UE B, where the SDP message carrying the MRS.
- the node AS sends an INFO notification request to the MRS, requesting the MRS to mix the UE B.
- the MRS returns a 200 OK ( INFO ) final response to the AS.
- Step 19 The AS sends an INFO notification request to the MRS, requesting the MRS to cyclically receive the number of the UE B (for example: if you have a new incoming call, press 1 for the call, 2 for the rejection), and the cycle time is about 1 minute.
- step 20 the MRS returns a 200 OK ( INFO ) final response to the AS.
- Step 21 The AS sends a REINVITE request to the UE C.
- AS wants to add UE C to the conference.
- step 11 UE C returns a 200 OK (REINVITE) final response to the AS, which carries its own SDP information.
- step 23 The AS sends an INVITE request to the MRS, where the SDP information of the UE C is carried.
- the MRS returns a 200 OK (INVITE) final response to the AS, which carries its own SDP information.
- Step 25 The AS sends an ACK acknowledgement message to the MRS.
- Step 26 The AS sends an ACK acknowledgement message to the UE C, where the SDP message carrying the MRS is used.
- Step 27 the AS sends an INFO notification request to the MRS, requesting the MRS to mix the UE C.
- the MRS returns a 200 OK ( INFO ) final response to the AS.
- UE B is in a call state, and UE B is in a playback state.
- Step 29 The MRS sends an INFO notification request to the AS to notify the AS of the input content of the UE B.
- step 30 the AS returns a 200 OK ( INFO ) final response to the MRS.
- the content of the AS to UE B If it is 1, it will be connected to Figure 7; if it is 2, it will be connected to Figure 8; if it is empty or other, it will be connected to Figure 9.
- FIG. 7 is a schematic flowchart of a user receiving a new call according to an embodiment of the present invention.
- UE B chooses to answer the new call.
- the process shown in Figure 7 includes the following steps:
- Step 01 The AS sends an INFO notification request to the MRS to request the MRS to periodically play the call hold tone to the UE C (such as: please wait, the call is held), or may be a piece of music.
- the input content of the UE B is 1, that is, the new call is selected, and the AS keeps a prompt tone for playing the call to the UE C.
- step 02 the MRS returns a 200 OK ( INFO ) final response to the AS.
- Step 03 The AS sends a BYE end request to the MRS to request the MRS to release the playback and mixing links of the UE B and the MRS.
- the AS stops playing and mixing the UE B.
- step 04 the MRS returns a 200 OK (BYE) final response to the AS.
- Step 05 The AS sends a BYE end request to the MRS to request the MRS to release the playback link between the UE A and the MRS.
- the AS stops playing a call waiting tone for UE A.
- step 06 the MRS returns a 200 OK (BYE) final response to the AS.
- step 07 the AS sends a REINVITE request to UE B. The AS wants to bridge the call to UE A and UE B.
- Step 08 The UE returns a 200 OK (REINVITE) final response to the AS, which carries its own SDP information.
- Step 09 The AS sends an UPDATE update request to the UE, where the SDP information of the UE B is carried.
- Step 10 UE A returns a 200 OK (UPDATE) final response to the AS, which carries its own SDP information.
- Step 11 The AS returns a 200 OK (INVITE) final response to UE A.
- Step 12 UE A sends an ACK acknowledgement message to the AS.
- Step 13 The AS sends an ACK acknowledgement message to the UE B, where the SDP information of the UE A is carried.
- the UE A negotiates with the UE B media to enter the call state.
- Step 14 UE A sends a BYE end request to the AS. UE A ends the call with UE B, and UE A hangs up.
- Step 15 The AS returns a 200 OK (BYE) final response to UE A.
- Step 16 The AS sends a BYTE end request to the MRS to request the MRS to release the playback link between the UE C and the MRS.
- UE A hangs up, so the AS wants to stop keeping the tone for the UE C play call, and bridges the call between UE B and UE C.
- Step 17 the MRS returns a 200 OK (BYE) final response to the AS.
- Step 18 The AS sends a REINVITE request to UE B.
- Step 19 UE B returns a 200 OK (REINVITE) final response to the AS, which carries its own SDP information.
- Step 20 The AS sends a REINVITE request to the UE C, where the SDP of the UE B is carried in step 21, and the UE C returns a 200 OK (REINVITE) final response to the AS, where the UE carries Its own SDP information.
- REINVITE 200 OK
- Step 11 the AS sends an ACK confirmation request to the UE C.
- Step 23 The AS sends an ACK acknowledgement request to the UE B, where the SDP information of the UE C is carried.
- the negotiation between the UE B and the UE C media is completed, and the call state is re-entered. The process ends.
- FIG. 8 is a schematic flowchart of a user rejecting a new call according to an embodiment of the present invention.
- UE B chooses to reject the new call.
- the process shown in Figure 8 includes the following steps:
- Step 01 The AS sends an INFO notification request to the MRS to request the MRS to play a failure prompt tone to the UE A, such as: The call you are making is in a call, please dial later.
- the input content of UE B is 2, that is, the new call is rejected, and the AS plays a failure tone to UE A.
- step 02 the MRS returns a 200 OK ( INFO ) final response to the AS.
- Step 03 The AS sends a BYE end request to the MRS to request the MRS to release the playback link between the UE A and the MRS.
- the AS releases the UE A and releases the playback resources.
- step 04 the MRS returns a 200 OK (BYE) final response to the AS.
- Step 05 the AS returns a 487 Terminated final response to UE A.
- the AS releases UE A after the UE A plays.
- Step 06 UE A sends an ACK acknowledgement message to the AS.
- Step 07 The AS sends a BYE end request to the MRS to request the MRS to release the playback and mixing links of the UE B and the MRS. After the AS receives the number from UE B, it releases the playback and mixing resources.
- step 08 the MRS returns a 200 OK (BYE) final response to the AS.
- Step 09 The AS sends a BYE end request to the MRS to request the MRS to release the mixing link of the UE C and the MRS.
- the AS releases the mixing resources.
- step 10 the MRS returns a 200 OK (BYE) final response to the AS.
- Step 11 The AS sends a REINVITE request to UE B.
- the AS wants to bridge UE B and UE C.
- Step 12 UE B returns a 200 OK (REINVITE) final response to the AS, where Its own SDP information.
- Step 13 The AS sends a REINVITE request to the UE C, where the SDP message of the UE B is carried.
- Step 14 The UE C returns a 200 OK (REINVITE) final response to the AS, which carries its own SDP information.
- Step 15 the AS sends an ACK acknowledgement message to the UE C.
- Step 16 The AS sends an ACK acknowledgement message to the UE B, where the SDP information of the UE C is carried.
- the negotiation between the UE B and the UE C media is completed, and the call state is re-entered. The process ends.
- FIG. 9 is a schematic flowchart of a process in which a user does not respond to a new call according to an embodiment of the present invention.
- UE B does not process the new call, that is, there is no response to the new call.
- the process shown in Figure 9 includes the following steps:
- Step 01 The AS sends a BYE end request to the MRS to request the MRS to release the playback link between the UE A and the MRS.
- the AS loops to the UE B for a time (for example, about 1 minute), and the UE B input content is empty, or a value other than 1 and 2, and the AS releases the playback resource to the UE A.
- step 02 the MRS returns a 200 OK (BYE) final response to the AS.
- Step 03 The AS returns a 408Time Out final response to UE A.
- the AS releases UE A after the UE A plays.
- Step 04 UE A sends an ACK acknowledgement message to the AS.
- Step 05 The AS sends a BYE end request to the MRS to request the MRS to release the playback and mixing links of the UE B and the MRS.
- the AS loops to the UE B to receive the sound collection time, releasing the playback and mixing resources.
- step 06 the MRS returns a 200 OK (BYE) final response to the AS.
- Step 07 The AS sends a BYE end request to the MRS to request the MRS to release the mixing link of the UE C and the MRS.
- the AS releases the mixing resources.
- step 08 the MRS returns a 200 OK (BYE) final response to the AS.
- step 09 the AS sends a REINVITE request to UE B.
- the AS wants to bridge UE B and UE C.
- Step 10 UE B returns a 200 OK (REINVITE) final response to the AS, which carries its own SDP information.
- Step 11 The AS sends a REINVITE request to the UE C, where the SDP message of the UE B is carried.
- Step 12 The UE C returns a 200 OK (REINVITE) final response to the AS, which carries its own SDP information.
- Step 13 The AS sends an ACK acknowledgement message to the UE C.
- Step 14 The AS sends an ACK acknowledgement message to the UE B, where the SDP information of the UE C is carried.
- the negotiation between the UE B and the UE C media is completed, and the call state is re-entered. The process ends.
- the operation of the present invention for implementing call waiting for a terminal that does not support the second incoming call may be represented by the process shown in FIG. 10, and the process includes the following steps:
- Step 1001 When the first terminal talks with the second terminal, the third terminal dials the first terminal that does not support the second incoming call.
- Step 1002 The AS supporting terminal communication controls communication between the first terminal and the third terminal. It can be seen from the above process that the first terminal and the second terminal are terminals that are in a call, and the third terminal is a terminal that initiates a new call.
- the present invention is directed to a method for implementing call waiting for a terminal that does not support the second incoming call, regardless of the method, the device, or the system, and has the following advantages and innovations: (1) The terminal is not required to support the second incoming call. The function of the second incoming call can be implemented by the AS. When there is a new call, the AS prompts the user to choose to answer or reject the call, overcoming the problem that the user cannot perceive the new call. (2) The terminal is not required to support the call hold function, which is implemented by the AS. The traditional call waiting feature requires a call hold button on the terminal to hold the original caller. In the present invention, if the user chooses When a new call is answered, the AS automatically performs call hold on the original caller.
- the user who realizes the new call in the conference talks with the original calling user, and simultaneously performs the sound collection and collection, and takes less time for the conference resources (up to about 1 minute).
- the call between the user who can implement the new call and the original calling user can be seamlessly switched between the conference call and the ordinary call, and the original call user does not perceive the handover process.
- the terminal can be applied to both NGN and IMS terminals, such as SIP hard terminal (SIP high-end phone with video capability and SIP low-end phone without video capability), SIP soft terminal (PC client), POTS (Plain Old Telephone Service, ordinary old-fashioned telephone service) Users, etc.
- SIP hard terminal SIP high-end phone with video capability and SIP low-end phone without video capability
- SIP soft terminal PC client
- POTS Pein Old Telephone Service, ordinary old-fashioned telephone service
- terminals under GSM, CDMA, and PSTN can also access the NGN and IMS by anchoring to apply the present invention to implement call waiting.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Multimedia (AREA)
- Telephonic Communication Services (AREA)
Abstract
La présente invention concerne un procédé, un dispositif et un système permettant à un terminal ne prenant pas en charge un second appel entrant d'effectuer une mise en attente d'appel. Selon l'invention, lorsqu'un premier terminal est en communication avec un deuxième terminal, un troisième terminal appelle le premier terminal qui ne prend pas en charge un second appel entrant (1101); un serveur d'application (AS) prenant en charge une communication entre terminaux commande la communication entre le premier terminal et le troisième terminal (1102). La présente invention permet à un terminal ne prenant pas en charge un second appel entrant d'effectuer une mise en attente d'appel.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201110429317.3 | 2011-12-20 | ||
CN201110429317.3A CN102664863B (zh) | 2011-12-20 | 2011-12-20 | 终端实现呼叫等待的方法、装置和系统 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2013091310A1 true WO2013091310A1 (fr) | 2013-06-27 |
Family
ID=46774277
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2012/072385 WO2013091310A1 (fr) | 2011-12-20 | 2012-03-15 | Procédé, dispositif et système permettant à un terminal d'exécuter une mise en attente d'appel |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN102664863B (fr) |
WO (1) | WO2013091310A1 (fr) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106331386B (zh) * | 2015-07-02 | 2019-10-15 | 华为技术有限公司 | 终端状态同步方法、相关装置及系统 |
US10999716B2 (en) * | 2015-12-31 | 2021-05-04 | Huawei Technologies Co., Ltd. | Call prompt method |
CN108063908A (zh) * | 2017-12-20 | 2018-05-22 | 维沃移动通信有限公司 | 一种视频通话方法、装置及移动终端 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101197877A (zh) * | 2006-12-08 | 2008-06-11 | 华为技术有限公司 | 业务处理方法以及应用服务器 |
CN101815270A (zh) * | 2010-03-05 | 2010-08-25 | 中兴通讯股份有限公司 | 呼叫的处理方法和装置 |
CN101860542A (zh) * | 2010-06-08 | 2010-10-13 | 中兴通讯股份有限公司 | 一种在点击拨号业务中实现呼叫等待的方法及系统 |
CN101997999A (zh) * | 2010-11-16 | 2011-03-30 | 华为终端有限公司 | 一种网络设备、被叫终端及处理第三方呼叫的方法 |
CN102026108A (zh) * | 2009-09-15 | 2011-04-20 | 中兴通讯股份有限公司 | 呼叫等待业务中区别振铃的实现方法及系统 |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6498841B2 (en) * | 1998-03-19 | 2002-12-24 | Ameritech Corporation | Method and system for providing enhanced call waiting and caller identification |
CN101815097A (zh) * | 2010-04-07 | 2010-08-25 | 中兴通讯股份有限公司 | 一种ctd呼叫业务中实现呼叫保持的方法和装置 |
-
2011
- 2011-12-20 CN CN201110429317.3A patent/CN102664863B/zh active Active
-
2012
- 2012-03-15 WO PCT/CN2012/072385 patent/WO2013091310A1/fr active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101197877A (zh) * | 2006-12-08 | 2008-06-11 | 华为技术有限公司 | 业务处理方法以及应用服务器 |
CN102026108A (zh) * | 2009-09-15 | 2011-04-20 | 中兴通讯股份有限公司 | 呼叫等待业务中区别振铃的实现方法及系统 |
CN101815270A (zh) * | 2010-03-05 | 2010-08-25 | 中兴通讯股份有限公司 | 呼叫的处理方法和装置 |
CN101860542A (zh) * | 2010-06-08 | 2010-10-13 | 中兴通讯股份有限公司 | 一种在点击拨号业务中实现呼叫等待的方法及系统 |
CN101997999A (zh) * | 2010-11-16 | 2011-03-30 | 华为终端有限公司 | 一种网络设备、被叫终端及处理第三方呼叫的方法 |
Also Published As
Publication number | Publication date |
---|---|
CN102664863A (zh) | 2012-09-12 |
CN102664863B (zh) | 2015-05-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP4819947B2 (ja) | セッション設定プロトコル基盤のアーリーメディアサービス提供方法 | |
CA2701960C (fr) | Procede d'implementation pour service multimedia mrbt | |
JP2005526466A5 (fr) | ||
WO2006111100A1 (fr) | Procede pour realiser un signal de rappel dans un systeme de communication | |
US20080273671A1 (en) | Method, system and application server for preventing crosstalk of color ring back tone | |
WO2012113193A1 (fr) | Procédé et système de mise en œuvre de service d'appel multipartie | |
US8311201B2 (en) | Method and system for controlling a conference | |
WO2012113237A1 (fr) | Procédé, système et dispositif pour réaliser un service de sonnerie de retour d'appel personnalisée en couleurs (crbt) multimédia | |
WO2011113240A1 (fr) | Procédé permettant d'emboîter un fichier multimédia dans une procédure click to dial et système de service click to dial | |
WO2008095385A1 (fr) | Procédé, système et dispositif d'appel personnalisé | |
WO2011050744A1 (fr) | Procédé de lecture de sonnerie multimédia durant une période de conversation, serveur et dispositif terminal correspondants | |
WO2011124042A1 (fr) | Procédé et appareil pour la mise en œuvre d'une mise en garde d'appel dans un service d'appel click to dial (ctd) | |
WO2009086758A1 (fr) | Procédé de prestation de service en ligne de tonalité de retour d'appel et de tonalité de retour d'appel multimédia | |
WO2007093116A1 (fr) | Procédé et système de fourniture de service de simulation et entité adaptative de signalisation d'accès | |
CN102664863B (zh) | 终端实现呼叫等待的方法、装置和系统 | |
WO2011153752A1 (fr) | Procédé, système et serveur d'applications pour la mise en œuvre d'un transfert d'appel dans un service « click to dial » | |
WO2013082894A1 (fr) | Procédé de transfert d'appel d'opérateur et serveur d'application de service de standard téléphonique | |
WO2012151799A1 (fr) | Procédé et système pour mettre en œuvre un appel de groupe sonnant simultané en un clic pour appeler un service | |
WO2013040832A1 (fr) | Procédé, dispositif et système permettant à l'opérateur d'insérer un appel dans un service de standard téléphonique | |
WO2012113194A1 (fr) | Procédé et système destinés à une commutation aléatoire de conversation entre les deux côtés lors d'un service d'appel | |
WO2010060314A1 (fr) | Terminal et procédé permettant de protéger un service individualisé de tonalité de rappel | |
WO2008138187A1 (fr) | Procédé de réalisation pour un appel de nouvelle réponse | |
WO2008067722A1 (fr) | Procédé, système de téléphone et terminal de téléphone pour une session d'appel | |
WO2012034423A1 (fr) | Procédé et système de reproduction de contenu multimédia précoce dans une session | |
WO2013082927A1 (fr) | Procédé de mise en œuvre d'un service de tonalité de retour d'appel dans un service de liaison à numéro unique et un serveur de service de liaison à numéro unique |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 12859269 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 12859269 Country of ref document: EP Kind code of ref document: A1 |