WO2007118379A1 - Procédé et système de fourniture de service appelé - Google Patents

Procédé et système de fourniture de service appelé Download PDF

Info

Publication number
WO2007118379A1
WO2007118379A1 PCT/CN2006/003205 CN2006003205W WO2007118379A1 WO 2007118379 A1 WO2007118379 A1 WO 2007118379A1 CN 2006003205 W CN2006003205 W CN 2006003205W WO 2007118379 A1 WO2007118379 A1 WO 2007118379A1
Authority
WO
WIPO (PCT)
Prior art keywords
unit
user
voice
mgw
mixing
Prior art date
Application number
PCT/CN2006/003205
Other languages
English (en)
French (fr)
Inventor
Hongxing Wang
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2007118379A1 publication Critical patent/WO2007118379A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways

Definitions

  • the present invention relates to a technique for playing a mix, and more particularly to a method and apparatus for implementing a mix in a separate core network. Background of the invention
  • the bearer is completed by the media gateway (MGW), and the control is completed by the media gateway controller (MGC), wherein the mobile MGC controls the MGW allocation through the H248 protocol.
  • MGW media gateway controller
  • MGC media gateway controller
  • 7 Loaded resources or pass the corresponding call bearer control signaling.
  • the interface between the MGC and the MGW is called an H248 interface or a Mc interface.
  • FIG. 1 is a schematic diagram of a process of implementing a normal call in an MGC and an MGW, the process including:
  • Step 101 The MGC sends a message (ADD T1 ) to add the calling side packet end point to the MGW.
  • Step 102 The MGC sends a message (ADD T2 ) to the MGW to add the called side packet end point.
  • the MGC may send a message to the MGW to add other called side packet endpoints.
  • the called in step 102 is called the first called, and after step 102, further includes:
  • Step 102a The MGC sends a message (ADD T3) to the MGW to add the second called side packet end point.
  • FIG. 2 is a schematic diagram of an internal structure of an MGW for implementing a normal call in the prior art, the device The calling unit 21 and the called unit 22, wherein the calling unit 21 includes: a calling endpoint T1, and the called unit 22 includes: a called endpoint T2.
  • the calling endpoint T1 in the calling unit 21 exchanges voice data with the external calling resource and interacts with the called endpoint ⁇ 2 in the called unit 22.
  • the called endpoint ⁇ 2 in the called unit 22 interacts with the external called resource and exchanges voice data with the calling endpoint T1 in the calling unit 21.
  • FIG. 3 is a schematic diagram of an internal structure of a MGW of a three-party call in the prior art, where the apparatus includes: a calling unit 31, a first called unit 32, a second called unit 33, a calling unit 31, and a first called unit 32.
  • the second called unit 33 interacts with the voice data, and interacts with the external calling resource, the first called resource, and the second called resource respectively, wherein the calling unit 31 includes: the calling endpoint T1, the calling party The codec unit TCI, the calling mix channel unit CC1, and the first called unit 32 include: a first called endpoint T2, a first called codec unit TC2, a first called mixing channel unit CC2, and a second called The calling unit 33 includes: a second called endpoint T3, a second called codec unit TC3, and a second called mixing channel unit CC3.
  • the mixing channel unit CC1, the mixing channel unit CC2, and the mixing channel unit CC3 are mixing channel resources.
  • the codec unit TC1, the codec unit TC2, and the codec unit TC3 are transcoders, and the transcoder can perform code conversion, for example: converting asynchronous transfer mode (ATM) data or IP data into pulse code modulation ( PCM, Pulse Code Modulation data, or convert PCM data into ATM data or IP data.
  • ATM asynchronous transfer mode
  • PCM pulse code modulation
  • PCM Pulse Code Modulation data
  • the calling endpoint T1 in the calling unit 31 exchanges voice data with the external calling resource and exchanges voice data with the calling codec unit TC1.
  • the calling codec unit TCI in the calling unit 31 receives the voice data sent by the calling endpoint T1, performs code conversion, and sends the voice data to the calling mixing channel unit CC1 to receive the voice data sent by the calling mixing channel unit CC1. After code conversion, it is sent to the calling endpoint T1.
  • the calling mixing channel unit CCl in the calling unit 31 receives the voice data sent by the calling codec unit TC1, and then forwards it to the first called mixing channel unit CC2 and the second called mixing channel unit CC3, and receives The voice data sent by the first called mixing channel unit CC2 and the second called mixing channel unit CC3 is forwarded to the calling codec unit TC1.
  • the first called endpoint T2 in the first called unit 32 exchanges voice data with the external first called resource and interacts with the first called codec unit TC2.
  • the first called codec unit TC2 in the first called unit 32 receives the voice data sent by the first called endpoint T2, performs code conversion, and sends the voice data to the first called mixing channel unit CC2 to receive the first received
  • the voice data sent by the mixing channel unit CC2 is code-converted and sent to the first called endpoint T2.
  • the first called mixing channel unit CC2 in the first called unit 32 receives the voice data sent by the first called codec unit TC2, and then forwards it to the calling mixing channel unit CC1 and the second called mixing channel.
  • the unit CC3 receives the voice data sent by the calling mix channel unit CC1 and the second called mix channel unit CC3, and then forwards the voice data to the first called codec unit TC2.
  • the second called endpoint T3 in the second called unit 33 interacts with the external second called resource and exchanges voice data with the second called codec unit TC3.
  • the second called codec unit TC3 in the second called unit 33 receives the voice data sent by the second called endpoint T3, performs code conversion, and sends the voice data to the second called mixing channel unit CC3 to receive the second received
  • the voice data sent by the mixing channel unit CC3 is code-converted and sent to the second called endpoint T3.
  • the second called mixing channel unit CC3 in the second called unit 33 receives the second called party After the voice data sent by the codec unit TC3 is forwarded to the calling mix channel unit CC1 and the first called mix channel unit CC2, the caller mix channel unit CC1 and the first called mix channel unit CC2 are sent. After the voice data is forwarded, it is forwarded to the second called codec unit TC3.
  • the MGW device shown in Figure 2 and Figure 3 can support normal calls, that is, ordinary calls.
  • some applications need to provide a mix, that is, some users in the call can normally talk to other users while listening to the background sound played by the MGW.
  • Commonly used mixing applications include call waiting service and mobile prepaid, which reminds the user that there is not much balance in the last minute. Both services need to play background music without affecting the user's call.
  • a primary object of the present invention is to provide an apparatus for implementing mixing that solves the problem of providing mixing in a separate core network.
  • a method of implementing a mix comprising the following steps:
  • the media gateway controller sends a message containing the signal identifier to the media gateway MGW.
  • the MGW mixes the voice and the call tone corresponding to the signal identifier according to the received message.
  • step B The message received in step B is mixed as follows:
  • MGW determines whether the received signal identifier is the source of the sound source that needs to be mixed. The signal identifier is determined, if yes, it is determined that the voice data corresponding to the voice play signal identifier is required, and step B12 is performed; otherwise, the voice corresponding to the signal identifier is not mixed, and the processing flow is ended;
  • the MGW determines whether the structure supports mixing, and if so, mixes the voice and the call tone corresponding to the signal identifier; otherwise, the voice corresponding to the signal identifier is not mixed.
  • the playback source that needs to be mixed is:
  • the MGW is pre-configured as a playback source that needs to be mixed.
  • the message in step A further includes: playing a mix indication;
  • Step B According to the received message, the mixing is specifically as follows:
  • the MGW determines whether the received playback mix indication includes information that needs to be mixed, and if yes, determines that the voice data corresponding to the mixed play signal identifier is required, and performs step B22, otherwise, the voice corresponding to the signal identifier is performed. Do not mix, and end this process;
  • the MGW determines whether the structure supports the mixing, and if so, mixes the voice and the call tone corresponding to the signal identifier; otherwise, the voice corresponding to the signal identifier is not mixed.
  • the method further includes: the MGC sending a message to the MGW to add at least two user endpoints; establishing a call between the at least two user endpoints.
  • the playback mix indication further includes: a user endpoint that receives the played voice; and in step B22, when it is determined that the mix play is required, the MGW mixes the voice corresponding to the playback target signal to the user endpoint.
  • the method further includes: sending, by the MGC, the MGW to stop playing the voice indication;
  • the MGW After receiving the stop voice indication, the MGW stops the voice corresponding to the play signal identifier. After the MGC sends the play mix indication to the MGW, the method further includes: the MGC sends a stop play voice indication to the MGW;
  • the stopping the playing of the voice indication comprises: stopping the user endpoint of playing the voice;
  • the MGW After receiving the stop voice indication, the MGW stops playing the voice corresponding to the signal identifier to the user endpoint.
  • An apparatus for implementing sound mixing comprising: a plurality of user units, wherein voice data is exchanged between a plurality of user units, and the plurality of user units respectively exchange voice data with different user resources connected to the outside of the device, and the device further
  • the method includes: a control unit, a sound emitting unit; and a control unit, receiving a message including a signal identifier outside the device, and sending the mixing control information to the sound emitting unit;
  • a sounding unit receiving the mixing control information sent by the control unit, and transmitting the voice data to the at least one user unit;
  • Each of the at least one subscriber unit receives the voice data sent by the sound emitting unit and the voice data sent by the remaining subscriber units for mixing, and then sends the mixed voice data to the outside of the device and is connected to itself.
  • User resources User resources.
  • Each user unit includes: a user endpoint, a user codec unit, and a user mixing channel unit;
  • the playback unit includes: a sound source unit, a sound source codec unit, and a sound source mixing channel unit;
  • the user mixing channel unit of each user unit receives the voice data sent by the sound source mixing channel unit of the sound emitting unit and the user mixing channel unit of the remaining user unit sends the voice data for mixing, and then mixes the sound.
  • the voice data is sent to the user codec unit of the user unit; after receiving the voice data sent by the user codec unit of the user unit, the voice data is forwarded to the user mix channel unit of the remaining user units;
  • the user codec unit of each subscriber unit receives the voice data sent by the user mixing channel unit of the user unit, performs code conversion, and sends the voice data to the user unit.
  • a user endpoint receiving voice data sent by a user endpoint of the user unit, performing code conversion, and transmitting the voice data to the user mixing channel unit of the user unit;
  • the user endpoint of each subscriber unit interacts with the user codec unit of the subscriber unit to exchange voice data with the user resource connected to the outside of the device;
  • a sound source unit of the sound emitting unit receiving sound mixing control information sent by the control unit, and transmitting voice data to the sound source codec unit;
  • the playback source codec unit of the sound reproduction unit receives the voice data sent by the sound reproduction unit, performs code conversion, and sends the voice data to the sound source mixing channel unit;
  • a sound mixing source mixing channel unit of the sound emitting unit receiving voice data sent by the sound source codec unit, and forwarding the voice data to the user mixing channel unit of the at least one subscriber unit; the user mixing channel unit of the at least one subscriber unit, After receiving the voice data sent by the sound source mixing channel unit of the sound emitting unit, the voice data is forwarded to the user codec unit of the user unit.
  • the MGC sends a message including a signal identifier (SIGNAL ID) to the MGW, and after receiving the message, the MGW determines that the received message includes an indication that a mix needs to be performed, or is SIGNAL
  • SIGNAL ID a signal identifier
  • the voice corresponding to the ID is a pre-configured specific voice that needs to be mixed, and the MGW determines that the mixing needs to be performed, otherwise the MGW determines that the mixing is not required.
  • the MGW determines that the mixing is required, if the internal structure of the MGW does not support mixing, whether the MGC indicates that the MGW needs to play the mixing, or the MGW configures the specific speech as the mixing, no mixing is performed.
  • the present invention solves the problem of providing mixing in a separate core network, and can flexibly implement mixing.
  • the play mix indication sent by the MGC to the MGW may include information that needs to be mixed or not required to be mixed, and the MGW may determine whether to mix according to the information in the received play mix indication; It is also possible to determine whether to perform the mixing according to whether the voice corresponding to the received SIGNAL ID is a pre-configured specific voice that needs to be mixed; when the MGW determines that the mixing needs to be performed, if the internal structure of the MGW does not support the mixing, then The mixing is performed; therefore, the method of realizing the mixing in the present invention can flexibly realize the mixing.
  • the present invention provides an MGW device capable of realizing mixing, in which the MGW connects the background sound in a single direction to the mixing channel resource of the user side that needs to receive the mixing, so that the user side receiving the mixing hears the background sound. It does not affect normal conversations with other users.
  • FIG. 1 is a schematic diagram of a process of implementing an ordinary call in an MGC and an MGW in the prior art
  • FIG. 2 is a schematic diagram of an internal structure of an MGW for implementing a normal call in the prior art
  • FIG. 3 is a schematic diagram of an internal structure of an MGW for implementing a three-party call in the prior art
  • FIG. 4 is a schematic diagram of implementing the hybrid in the MGC and the MG W according to the first embodiment of the present invention; Schematic diagram of the process of sound;
  • FIG. 5 is a schematic diagram of a process of implementing mixing in an MGC and an MGW according to Embodiment 2 of the present invention
  • FIG. 6 is a schematic diagram of an internal structure of an MGW that implements mixing in an embodiment of the present invention. detailed description
  • the media gateway controller MGC sends a message including the SIGNAL ID to the media gateway MGW; the MGW corresponds to the SIGNAL ID according to the received message.
  • the voice and the call tone are mixed.
  • the information sent by the MGC may include: a SIGNAL ID, or a SIGNAL ID and a play mix indication.
  • the MGW device capable of realizing the mixing in the present invention includes: a plurality of user units, which exchange voice data between the plurality of user units, and the plurality of user units respectively exchange voice data with different user resources connected to the outside of the device,
  • the device further includes: a control unit, a sound emitting unit; a control unit, receiving a message including a SIGNAL ID outside the device, and transmitting the mixing control information to the sound emitting unit; and a sounding unit receiving the sound mixing control information sent by the control unit, Transmitting voice data to at least one subscriber unit; each of the at least one subscriber unit receives the voice data sent by the sound emitting unit and the voice data sent by the remaining subscriber units, and then sends the voice data to the user connected to the outside of the device Resources.
  • the information sent by the MGC includes: a SIGNAL ID.
  • some special sounds are defined by the configuration on the MGW, and the mixing is performed by the mixing mode to achieve the mixing.
  • FIG. 4 is a schematic diagram of a process for implementing mixing in an embodiment of the present invention.
  • the process includes the following steps: Step 401: The MGC sends a message including a SIGNAL ID to the MGW.
  • step 401 the MGC sends a message containing the SIGNAL ID to the MGW.
  • step 401 the MGC sends the SIGNAL to the MGW in many cases.
  • the message of the ID is usually sent to the MGW when the MGC determines that the user needs to hear the voice corresponding to the SIGNAL ID.
  • Steps 402 to 404 The MGW determines whether the received SIGNAL ID is the SIGNAL ID corresponding to the playback source of the pre-configured playback source, and if yes, determines that the voice data corresponding to the SIGNAL ID is required to be played by the mix, otherwise determining For no need to mix
  • the method for pre-configuring a sound source that needs to be mixed may be: the MGW pre-selects some voice data, and specifies a sound source that needs to be mixed, and sets the attributes of the sound source and the user who needs to play the sound. Endpoints, etc.
  • the specific configuration method can be various, as long as the configuration can enable the MGW to identify which SINGAL IDs correspond to which playback sources, and which one or which user endpoints need to be mixed.
  • the MGW can determine whether the structure supports the mixing, and if so, mix the voice and the voice corresponding to the SIGNAL ID; otherwise, the corresponding to the SIGNAL ID The voice is not mixed.
  • the call tone generally refers to a call tone between users.
  • the information sent by the MGC includes: SIGNAL ED, and the playback mix indication.
  • FIG. 5 is a schematic diagram of a process for implementing mixing in an embodiment of the present invention.
  • the process includes: Step 501: The MGC sends a message including a SIGNAL ID and a playback mix indication to the MGW.
  • step 501 the MGC sends a message containing the SIGNAL ID and the play mix indication to the MGW.
  • step 501 the MGC sends a message including the SIGNAL ID to the MGW in many cases.
  • the MGC determines that the user needs to hear the voice corresponding to the SIGNAL ID, the MGC sends the message to the MGW.
  • the indication is performed by expanding the parameter of whether the SIGNAL ID corresponding to the playback source needs to be mixed in the H248 interface, that is, the Mc interface.
  • the parameters can be extended on the H248 interface
  • a new package carries a new attribute to implement, and correspondingly, the H248 interface for playing the mix indication is as follows:
  • Package ID ( PackagelD ) : MixTonelnd (package ID value to be determined)
  • the mix package defines the attributes, events, processes, etc. required to extend the mix service between the M GW and the MGC.
  • the properties of the mixing indicator package are: Mix Tone indication:
  • Mix Tone indication attribute which is used to indicate whether a particular SIGNAL ID is being mixed.
  • the MGC is required to carry this attribute while carrying the play SIGNAL descriptor to indicate whether the play tone requires a mix play. If the MGC does not carry the attribute when the play sound SIGNAL descriptor is sent, it indicates that the mix is not indicated, and whether the mix is controlled by the MGW.
  • MOD Tl indicates that the mix is played to the calling side endpoint.
  • Step 502 to step 504 The MGW determines whether the received playback mix indication includes information that needs to be mixed, and if yes, determines that the voice data corresponding to the SIGNAL ID is required to be played by the mix, otherwise it is determined that the mix is not required. .
  • the specific format of the playback mix indication received by the MGW is:
  • the MGW determines that the voice data corresponding to the Signalld1 needs to be played to the calling side endpoint mix.
  • the MGC is further included to indicate that the MGW adds the calling user side packet endpoint, specifically:
  • Step 501a The MGC sends a message (ADD Tl ) to the MGW to add the calling side packet endpoint.
  • Step 501a and step 501 further include the step of the MGC instructing the MGW to add the called user side packet endpoint. If there are multiple called users, the MGC instructs the MGW to add each called user side packet endpoint one by one, and the present invention exists in FIG. The process when two called users are specifically:
  • Step 501b The MGC sends a message (ADD T2) to the MGW to add the first called side packet end point.
  • Step 501 c The MGC sends a message to the MG W to add the second called side packet endpoint (ADD T3) o
  • step 501 the MGC indicates that the MGW needs to perform the mixing, then after step 501 Usually included: The MGC instructs the MGW to stop the playback of the mix indication.
  • the MGW After the MGW receives the stop playback mix indication sent by the MGC, it usually stops playing the mix.
  • the stop playing mix indication is usually implemented when the H248 interface is implemented, and the specific format of the message may be:
  • the MGW After the MGW receives the stop to play the mix indication, it usually stops playing the voice played to the calling user endpoint.
  • step 501 may also include: The MGC instructs the MGW to instruct to stop playing the voice indication.
  • the MGW After the MGW receives the stop voice indication sent by the MGC, it usually stops playing the mix.
  • the MGW can determine whether the structure supports mixing, and if so, mix the voice and the call tone corresponding to the SIGNAL ID; otherwise, the voice corresponding to the SIGNAL ID is not mixed.
  • Embodiment 1 an internal structure of an MGW device capable of realizing mixing is as shown in FIG. 6.
  • the device mainly includes: a calling unit 61, a first called unit 62, a control unit 60, and a sound emitting unit 63.
  • the MGW device may further include: a second called unit 64, where the calling unit 61 includes: a calling endpoint T1, a calling codec unit TC1, and a calling party.
  • the sound channel unit CC1 the first called unit 62 includes: a first called endpoint T2, a first called codec unit TC2, a first called mixing channel unit CC2, and a sound emitting unit 63 comprising: a sound source unit 631
  • the playback codec unit TC3, the playback mixing channel unit CC3, and the second called unit 64 include: a second called endpoint T4, a second called codec unit TC4, and a second called mixing channel unit CC4.
  • the calling endpoint T1 in the calling unit 61 exchanges voice data with the external calling resource. And interacting with the calling codec unit TCI voice data.
  • the calling codec unit TC1 in the calling unit 61 receives the voice data sent by the calling endpoint T1, performs code conversion, and sends the voice data to the calling mixing channel unit CC1 to receive the voice data sent by the calling mixing channel unit CC1. After code conversion, it is sent to the calling endpoint T1.
  • the calling mixing channel unit CC1 in the calling unit 61 receives the voice data sent by the calling codec unit TC1, and then forwards it to the first called mixing channel unit CC2 and the second called mixing channel unit CC4, and receives The first called mixing channel unit CC2 and the second called mixing channel unit CC4, and the voice data sent by the sound mixing channel unit CC3 are forwarded to the calling codec unit TC1.
  • the first called endpoint T2 in the first called unit 62 interacts with the external first called resource and exchanges voice data with the first called codec unit TC2.
  • the first called codec unit TC2 in the first called unit 62 receives the voice data sent by the first called endpoint T2, performs code conversion, and sends the voice data to the first called mixing channel unit CC2 to receive the first received
  • the voice data sent by the mixing channel unit CC2 is code-converted and sent to the first called endpoint T2.
  • the first called mixing channel unit CC2 in the first called unit 62 receives the voice data sent by the first called codec unit TC2, and then forwards it to the calling mixing channel unit CC1 and the second called mixing channel.
  • the unit CC4 receives the voice data sent by the calling mixing channel unit CC1 and the second called mixing channel unit CC4, and then forwards the voice data to the first called codec unit TC2 0
  • the control unit 60 receives a message including a SIGNAL ID outside the device, and transmits the mixing control information to the sound source unit 631 in the playback unit 63.
  • the control unit 60 can generally determine that a mix is required based on the received message.
  • the message including the SIGNAL ID received by the control unit 60 may be sent by the MGC.
  • the sound emitting source unit 631 in the sound emitting unit 63 receives the sound mixing control information transmitted from the control unit 60, and transmits the voice data to the sound reproducing codec unit TC3.
  • the sound emitting source unit 631 may be a sound source database for storing voice data to be played, or may be a sound source database interface of a sound source database connected to the MGW externally stored voice data to be played back, when the sound source unit 631 is used.
  • the voice data sent by the sound source unit 631 to the sound reproduction codec unit TC3 is acquired from an external sound source database.
  • the sound source unit 631 transmits the voice data of the desired square sound to the playback codec unit TC3.
  • the playback codec unit TC3 in the playback unit 63 receives the voice data transmitted from the playback source unit 631, and transmits the voice data to the playback mixing channel unit CC3.
  • the playback mixing channel unit CC3 in the playback unit 63 receives the voice data transmitted by the playback codec unit TC3 and forwards it to the mixing channel unit CC1 in the calling unit 61.
  • the second called endpoint T4 of the second called unit 64 interacts with the external second called user resource to exchange voice data with the second called codec unit TC4.
  • the second called codec unit TC4 in the second called unit 64 receives the voice data sent by the second called endpoint T4, performs code conversion, and sends the voice data to the second called mixing channel unit CC4 to receive the second received
  • the voice data sent by the mixing channel unit CC4 is code-converted and sent to the second called endpoint T4.
  • the second called mixing channel unit CC4 in the second called unit 64 receives the voice data sent by the second called codec unit TC4, and then forwards the voice data to the calling mixing channel unit CC1 and the first called mixing channel.
  • the unit CC2 receives the voice data sent by the calling mixing channel unit CC1 and the first called mixing channel unit CC2, and then forwards the voice data to the second called codec unit TC4.
  • the MGW determines that the mixing is required, but if the MGW is not configured with the mixing resource, for example, the MGW is not plugged into the mixing resource board, The internal structure does not support mixing, and the voice corresponding to the SIGNAL ID is played in normal voice.
  • the MGW does not configure the mixing resource. Specifically, in FIG. 6, if there is only one called in the call, that is, when the first called, the MGW has no mixing resource, which means: there is no calling codec unit TC1, the calling party One or more of the mixing channel unit CC1, the first called codec unit TC2, the first called mixing channel unit CC2, the playback codec unit TC3, the playback mixing channel unit CC3, etc.; When there are multiple called parties, for example, when the two called parties are shown in FIG. 6, the MGW does not have a mixing resource, which means that there is no one or more of the units such as the playback codec unit TC3 and the playback mixing channel unit CC3.
  • Embodiment 1 when the MGW determines that the mixing is not required, the voice corresponding to the SIGNAL ID is played only in accordance with the normal voice.
  • the specific method of the MGW according to the ordinary voice play may be various, and the specific implementation manner does not affect the scheme for realizing the mix in the present invention.
  • the device in which the MGW plays in accordance with normal voice is a device in which the MGW does not have a mix resource configured. There are a plurality of devices for playing the MGW according to ordinary voice, and the specific implementation manner does not affect the scheme for realizing the mixing in the present invention.
  • a user can play a mix, or a mix can be played for multiple users.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)

Description

一种实现被叫服务的方法和系统 技术领域
本发明涉及一种播放混音的技术，特别涉及一种在分离式核心网 络中实现混音的方法和装置。 发明背景
在第三代移动通信系统版本 4 ( R4 ) 的分离式核心网络中， 承载 由媒体网关 （MGW ) 完成， 控制由媒体网关控制器 （MGC ) 完成， 其中，移动 MGC通过 H248协议来控制 MGW分配 7 载的资源或传递相 应的呼叫承载控制信令。所述 MGC与 MGW之间的接口称为 H248接口 或 Mc接口。
图 1为在 MGC和 MGW中实现普通通话的过程示意图， 该过程包 含：
步骤 101 : MGC向 MGW发送添加主叫侧分组端点的消息 （ADD T1 ) 。
步骤 102: MGC向 MGW发送添加被叫侧分组端点的消息 （ADD T2 ) 。
如果通话中存在多个被叫时， 步骤 102之后， MGC可以向 MGW 发送添加其他被叫侧分組端点的消息。 比如： 存在两个被叫时， 步骤 102中的被叫为第一被叫， 且步骤 102之后， 进一步包含：
步驟 102a： MGC向 MGW发送添加第二被叫侧分组端点的消息 ( ADD T3 ) 。
通过图 1所示过程， 各个用户端点之间建立通话。
图 2为现有技术中实现普通通话的 MGW内部结构示意图，该装置 包含： 主叫单元 21、 被叫单元 22， 其中， 主叫单元 21包含： 主叫端点 T1 , '被叫单元 22包含： 被叫端点 T2。
主叫单元 21中的主叫端点 T1 , 与外部的主叫资源交互语音数据， 并与被叫单元 22中的被叫端点 Τ2交互语音数据。
被叫单元 22中的被叫端点 Τ2, 与外部的被叫资源交互语音数据， 并与主叫单元 21中的主叫端点 T1交互语音数据。
现有技术中， 存在多个被叫时， 在 MGW内部也需要相应地增加 对应的端点， 且各个端点需要通过混音通道单元与其他端点连接。
图 3为现有技术中三方通话的 MGW内部结构示意图， 该装置包 含： 主叫单元 31、 第一被叫单元 32、 第二被叫单元 33， 主叫单元 31、 第一被叫单元 32、 第二被叫单元 33相互交互语音数据， 并分别与外部 的主叫资源、 第一被叫资源、 第二被叫资源交互语音数据， 其中， 主 叫单元 31包含： 主叫端点 Tl、 主叫编解码单元 TCI、 主叫混音通道单 元 CC1， 第一被叫单元 32包含： 第一被叫端点 T2、 第一被叫编解码单 元 TC2、 第一被叫混音通道单元 CC2, 第二被叫单元 33包含： 第二被 叫端点 T3、 第二被叫编解码单元 TC3、 第二被叫混音通道单元 CC3。
所述混音通道单元 CC1、 混音通道单元 CC2、 混音通道单元 CC3 为混音通道资源。 所述编解码单元 TC1、 编解码单元 TC2、 编解码单 元 TC3为变码器， 所述变码器可以进行码转换， 比如： 将异步传输模 式 （ATM ) 数据或 IP数据转换为脉冲编码调制 （PCM， Pulse Code Modulation )数据， 或者是将 PCM数据转换为 ATM数据或 IP数据。 通 常， 主叫端点或被叫端点发送给变码器的数据为 ATM数据或 IP数据， 混音通道单元发送给变码器的数据为 PCM数据。
主叫单元 31中的主叫端点 T1 , 与外部的主叫资源交互语音数据， 并与主叫编解码单元 TC1交互语音数据。 主叫单元 31中的主叫编解码单元 TCI ,接收主叫端点 T1发送的语 音数据， 进行码转换后， 发送给主叫混音通道单元 CC1 , 接收主叫混 音通道单元 CC1发送的语音数据，进行码转换后，发送给主叫端点 Tl。
主叫单元 31中的主叫混音通道单元 CCl， 接收主叫编解码单元 TC1发送的语音数据后， 转发给第一被叫混音通道单元 CC2和第二被 叫混音通道单元 CC3 , 接收第一被叫混音通道单元 CC2和第二被叫混 音通道单元 CC3发送的语音数据后 , 转发给主叫编解码单元 TC1。
第一被叫单元 32中的第一被叫端点 T2,与外部的第一被叫资源交 互语音数据， 与第一被叫编解码单元 TC2交互语音数据后。
第一被叫单元 32中的第一被叫编解码单元 TC2, 接收第一被叫端 点 T2发送的语音数据， 进行码转换后，发送给第一被叫混音通道单元 CC2, 接收第一被叫混音通道单元 CC2发送的语音数据， 进行码转换 后， 发送给第一被叫端点 T2。
第一被叫单元 32中的第一被叫混音通道单元 CC2， 接收第一被叫 编解码单元 TC2发送的语音数据后， 转发给主叫混音通道单元 CC1和 第二被叫混音通道单元 CC3 , 接收主叫混音通道单元 CC1和第二被叫 混音通道单元 CC3发送的语音数据后， 转发给第一被叫编解码单元 TC2。
第二被叫单元 33中的第二被叫端点 T3，与外部的第二被叫资源交 互语音数据， 与第二被叫编解码单元 TC3交互语音数据。
第二被叫单元 33中的第二被叫编解码单元 TC3 , 接收第二被叫端 点 T3发送的语音数据， 进行码转换后，发送给第二被叫混音通道单元 CC3 , 接收第二被叫混音通道单元 CC3发送的语音数据， 进行码转换 后， 发送给第二被叫端点 T3。
第二被叫单元 33中的第二被叫混音通道单元 CC3 , 接收第二被叫 编解码单元 TC3发送的语音数据后， 转发给主叫混音通道单元 CC1和 第一被叫混音通道单元 CC2， 接收主叫混音通道单元 CC1和第一被叫 混音通道单元 CC2发送的语音数据后， 转发给第二被叫编解码单元 TC3。
图 2、 图 3所示 MGW装置能够支持正常通话， 即普通呼叫。
在分离式核心网络中， 有些应用需要提供混音， 即通话中的某些 用户在听见 MGW播放的背景音的同时可以与其他用户正常通话。 常 见的混音应用有呼叫等待业务和移动预付费在最后一分钟提示用户 余额不多等业务，这两种业务均需要播放背景音乐时能够不影响用户 通话。
目前分离式核心网络中， 还没有提供混音的方案。 发明内容
有鉴于此， 本发明的主要目的在于提供一种实现混音的方法， 能 够解决在分离式核心网络中提供混音的问题。
本发明的主要目的在于提供一种实现混音的装置，能够解决在分 离式核心网络中提供混音的问题。
本发明的技术方案是这样实现的：
一种实现混音的方法， 该方法包含以下步骤：
A、 媒体网关控制器 MGC向媒体网关 MGW发送包含信号标识的 消息；
B、 MGW根据收到的消息对信号标识对应的语音和通话音进行 混音。
步驟 B所述 居收到的消息进行混音具体为：
Bl l、 MGW判断收到的信号标识是否是需要混音的放音源所对 应的信号标识， 如果是， 则确定为需要混音播放信号标识对应的语音 数据， 并执行步骤 B12, 否则对信号标识对应的语音不进行混音， 并 结束本处理流程；
B12、 MGW判断自身结构是否支持混音， 如果是， 则对信号标 识对应的语音和通话音进行混音；否则对信号标识对应的语音不进行 混音。
所述需要混音的放音源为： MGW预先配置为需要混音的放音源。 步骤 A所述消息进一步包含： 播放混音指示；
步骤 B所述根据收到的消息进行混音具体为：
B21、 MGW判断收到的播放混音指示中是否包含需要进行混音 的信息， 如果是， 则确定为需要混音播放信号标识对应的语音数据， 并执行步骤 B22， 否则对信号标识对应的语音不进行混音， 并结束本 处理流程；
B22、 MGW判断自身结构是否支持混音， 如果是， 则对信号标 识对应的语音和通话音进行混音；否则对信号标识对应的语音不进行 混骨。
MGC向 MGW发送播放混音指示之前，该方法进一步包含： MGC 向 MGW发送添加至少两个用户端点的消息；所述至少两个用户端点 之间建立通话。
所述播放混音指示中进一步包含： 接收所播放语音的用户端点； 步骤 B22中， 确定为需要混音播放时， MGW向所述用户端点混 音播放信号标识对应的语音。
MGC向 MGW发送播放混音指示后， 该方法进一步包含： MGC 向 MGW发送停止播放语音指示；
MGW收到停止播放语音指示后 ,停止播放信号标识对应的语音。 MGC向 MGW发送播放混音指示后， 该方法进一步包含： MGC向 MGW发送停止播放语音指示；
所述停止播放语音指示包含： 停止播放语音的用户端点；
MGW收到停止播放语音指示后， 停止向所述用户端点播放信号 标识对应的语音。
一种实现混音的的装置， 包含： 多个用户单元， 多个用户单元之 间交互语音数据，多个用户单元分别与该装置外部与自身相连接的不 同用户资源交互语音数据，该装置进一步包含：控制单元、放音单元； 控制单元， 接收该装置外部的包含信号标识的消息， 向放音单元 发送混音控制信息；
放音单元， 接收控制单元发送的混音控制信息， 向至少一个用户 单元发送语音数据；
所述至少一个用户单元中的每个单元，接收放音单元发送的语音 数据和其余用户单元发送的语音数据进行混音后，将混音后的语音数 据发送给该装置外部与自身相连接的用户资源。
所述每个用户单元包含： 用户端点、 用户编解码单元、 用户混音 通道单元； 所述放音单元包含： 放音源单元、 放音源编解码单元、 放 音源混音通道单元；
所述每个用户单元的用户混音通道单元，接收放音单元的放音源 混音通道单元发送的语音数据和其余用户单元的用户混音通道单元 发送语音数据进行混音后，将混音后的语音数据发送给自身用户单元 的用户编解码单元；接收自身用户单元的用户编解码单元发送的语音 数据后， 转发给其余用户单元的用户混音通道单元；
所述每个用户单元的用户编解码单元，接收自身用户单元的用户 混音通道单元发送的语音数据，进行码转换后发送给自身用户单元的 用户端点； 接收自身用户单元的用户端点发送的语音数据， 进行码转 换后发送给自身用户单元的用户混音通道单元；
所述每个用户单元的用户端点， 与自身用户单元的用户编解码单 元交互语音数据；与该装置外部与自身相连接的用户资源交互语音数 据；
放音单元的放音源单元， 接收控制单元发送的混音控制信息， 向 放音源编解码单元发送语音数据；
放音单元的放音源编解码单元， 接收放音单元发送的语音数据， 进行码转换后发送给放音源混音通道单元；
放音单元的放音源混音通道单元，接收放音源编解码单元发送的 语音数据， 转发给所述至少一个用户单元的用户混音通道单元； 所述至少一个用户单元的用户混音通道单元，接收放音单元的放 音源混音通道单元发送的语音数据后，转发给自身用户单元的用户编 解码单元。
本发明有以下有益效果：
1 ) 本发明中通过在分离式核心网络中， MGC向 MGW发送包含 信号标识 （SIGNAL ID ) 的消息， MGW收到消息后判定为收到的消 息中包含需要进行混音的指示，或者是 SIGNAL ID对应的语音为自身 预先配置的需要混音的特定语音， 则 MGW确定需要进行混音， 否则 MGW确定为不需要进行混音。 当 MGW确定为需要进行混音时， 如果 MGW的内部结构不支持混音， 则无论是 MGC指示 MGW需要播放混 音， 还是 MGW配置特定语音为混音， 均不进行混音。 本发明解决了 在分离式核心网络中提供混音的问题， 且可以灵活实现混音。
2 ) 由于能够在分离式核心网络中提供混音业务， 丰富了业务应 用。 3 ) 本发明中， MGC向 MGW发送的播放混音指示可以包含需要 进行混音或不需要进行混音的信息， MGW可以根据收到的播放混音 指示中的信息确定是否进行混音； MGW也可以根据收到的 SIGNAL ID对应的语音是否为自身预先配置的需要混音的特定语音来确定是 否进行混音； MGW确定为需要进行混音时， 如果 MGW内部结构不支 持混音， 则不进行混音； 因此本发明中实现混音的方法可以灵活实现 混音。
4 ) 本发明提供了能够实现混音的 MGW装置， 该装置中， MGW 将背景音单方向接入到需要接收混音的用户侧的混音通道资源，使接 收混音的用户侧听见背景音的同时不影响与其他用户的正常通话。 附图说明
图 1为现有技术中在 MGC和 MGW中实现普通通话的过程示意 图；
图 2为现有技术中在实现普通通话的 MGW内部结构示意图； 图 3为现有技术中实现三方通话的 MGW内部结构示意图； 图 4为本发明实施例 1中在 MGC和 MG W中实现混音的过程示意 图；
图 5为本发明实施例 2中在 MGC和 MGW中实现混音的过程示意 图；
图 6为本发明实施例中实现混音的 MGW内部结构示意图。 具体实施方式
本发明的核心思想是： 媒体网关控制器 MGC向媒体网关 MGW发 送包含 SIGNAL ID的消息； MGW根据收到的消息对 SIGNAL ID对应 的语音和通话音进行混音。
所述 MGC发送的信息可以包含： SIGNAL ID,或者是 SIGNAL ID 与播放混音指示。
本发明中能够实现混音的 MGW装置包含： 包含： 多个用户单元， 多个用户单元之间交互语音数据，多个用户单元分别与该装置外部与 自身相连接的不同用户资源交互语音数据， 该装置进一步包含： 控制 单元、 放音单元； 控制单元， 接收该装置外部的包含 SIGNAL ID的消 息， 向放音单元发送混音控制信息； 放音单元， 接收控制单元发送的 混音控制信息， 向至少一个用户单元发送语音数据； 所述至少一个用 户单元中的每个单元，接收放音单元发送的语音数据和其余用户单元 发送的语音数据后， 发送给该装置外部与自身相连接的用户资源。
以下参照附图并举实施例， 对本发明进一步详细说明。
实施例 1 :
本实施例中， MGC发送的信息包含： SIGNAL ID。 本实施例是， 在 MGW上通过配置来定义一些特殊音需要通过混音方式播放来实现 混音。
图 4为本发明实施例中实现混音的过程示意图， 该过程包含： 步骤 401 : MGC向 MGW发送包含 SIGNAL ID的消息。
步骤 401中， MGC向 MGW发送包含 SIGNAL ID的消息。
步骤 401中， MGC在很多情况下都会向 MGW发送包含 SIGNAL
ID的消息， 通常是 MGC确定为需要让用户听到 SIGNAL ID对应的语 音时， 向 MGW下发所述消息。
步骤 402〜步骤 404: MGW判断收到的 SIGNAL ID是否是自身预先 配置的需要混音的放音源所对应的 SIGNAL ID, 如果是， 则确定为需 要混音播放 SIGNAL ID对应的语音数据， 否则确定为不需要进行混 所述预先配置需要混音的放音源的方法， 具体可以为： MGW预 先选择某些语音数据， 并指定为需要混音的放音源， 且设置所述放音 源的属性、需要播放混音的用户端点等。具体配置的方法可以有多种， 只要配置后能够让 MGW识别出哪些放音源对应于哪个 SINGAL ID、 且该放音源需要对哪个或哪些用户端点进行混音即可。
步骤 404中 MGW确定为需要混音播放 SIGNAL ID对应的语音数 据后， MGW可以判断自身结构是否支持混音， 如果是， 则对 SIGNAL ID对应的语音和通话音进行混音；否则对 SIGNAL ID对应的语音不进 行混音。
所述通话音通常是指用户之间的通话音。
实施例 2:
本实施例中， MGC发送的信息包含： SIGNAL ED, 播放混音指 示。
图 5为本发明实施例中实现混音的过程示意图， 该过程包含： 步骤 501 : MGC向 MGW发送包含 SIGNAL ID和播放混音指示的 消息。
步骤 501中， MGC向 MGW发送包含 SIGNAL ID和播放混音指示 的消息。
步骤 501中， MGC在很多情况下都会向 MGW发送包含 SIGNAL ID的消息， 通常是 MGC确定为需要让用户听到 SIGNAL ID对应的语 音时， 向 MGW下发所述消息。
至于播放混音指示，通常是对于一些基于用户定制的需要混音的 放音源，通过在 H248接口即 Mc接口中扩展所述放音源对应的 SIGNAL ID是否需要混音的参数来进行指示。 所述参数可以在 H248接口扩展 一个新包携带一个新属性来实现，相应的，进行播放混音指示的 H248 接口如下：
混音指示包 ( Mix Tone Indication Package ) 定义：
包标识 （ PackagelD ) ： MixTonelnd (包 ID取值待定）
版本 ( Version ) ： 1
扩展 ( Extends ) ： None
所述混音包定义了 M GW与 MGC之间扩展混音业务所需要的属 性、 事件、 过程等。 其中， 所述混音指示包的属性 （Properties ) 为： 混音指示 ( Mix Tone indication ) ：
属性标识 （Property ID ) ： Mixlndication (0x0001)
描述（ Description )： 定义 Mix Tone indication属性， 用来指示特 定的 SIGNAL ID是否进行混音。 要求 MGC在下发播放音 SIGNAL描述 符的同时携带该属性来指示是否该播放音需要混音播放。 如果 MGC 在下发播放音 SIGNAL描述符的时候没有携带该属性， 则表示为不指 示进行混音， 具体是否混音由 MGW控制。
类型 （Type ) ： 整数 ( integer )
可能值 ( Possible Values ) ：
"TRUE" (0x0001)需要进行混音。
"FALSE" (0x0002)不需要进行混音。
默认（Default ) ： " FALSE " (0x0002) 不需要进行混音。
定义在 ( Defined in ) ： Local Control descriptor
特性 ( Characteristics ) ： Read/Write
比如： MGC判断为需要混音时， 驱动向某个用户侧如主叫侧的 端点播放混音， 且所述播放音的 SIGNAL ID为SignalIdl , 则播放混音 指示的具体格式可以为： MOD Tl ( LocalControl { MixIndication=TRUE }, Signals {Signalldl } )
其中， MOD Tl表示向主叫侧端点播放混音。
步骤 502〜步骤 504: MGW判断收到的播放混音指示中是否包含需 要进行混音的信息， 如果是， 则确定为需要混音播放 SIGNAL ID对应 的语音数据， 否则确定为不需要进行混音。
比如： MGW收到的播放混音指示的具体格式为：
MOD Tl ( LocalControl { MixIndication=TRUE }, Signals {Signalldl } )
则， MGW确定为需要向主叫侧端点混音播放 Signalldl对应的语 音数据。
实际应用中， 步骤 501之前通常进一步包含 MGC指示 MGW添加 主叫用户侧分组端点的步骤， 具体为：
步骤 501a: MGC向 MGW发送添加主叫侧分组端点的消息（ADD Tl ) 。
步骤 501a和步骤 501之间， 进一步包含 MGC指示 MGW添加被叫 用户侧分组端点的步骤， 如果存在多个被叫用户， 则 MGC逐个指示 MGW添加各个被叫用户侧分组端点，图 5中包含存在两个被叫用户时 的过程， 具体为：
步骤 501b: MGC向 MGW发送添加第一被叫侧分组端点的消息 ( ADD T2 ) „
步骤 501 c： MGC向 MG W发送添加第二被叫侧分组端点的消息 ( ADD T3 ) o
通过步驟 501a〜步骤 501c所示过程，各个用户端点之间建立通话。 如果步骤 501中， MGC指示 MGW需要进行混音， 则步驟 501之后 通常包含： MGC指示 MGW指示停止播放混音指示。
MGW收到 MGC发送的停止播放混音指示后， 通常会停止播放混 音。
所述停止播放混音指示通常在 H248接口实现时， 消息的具体格 式可以为：
MOD Tl ( Signals { } )
MGW收到所述停止播放混音指示后， 通常会停止播放向主叫用 户端点播放的语音。
如果步骤 501中， MGC指示 MGW不需要进行混音， 则步骤 501之 后通常也可以包含： MGC指示 MGW指示停止播放语音指示。
MGW收到 MGC发送的停止播放语音指示后， 通常会停止播放混 音。
步骤 504之后， MGW可以判断自身结构是否支持混音， 如果是， 则对 SIGNAL ID对应的语音和通话音进行混音； 否则对 SIGNAL ID对 应的语音不进行混音。
实施例 1、 实施例 2中， 能够实现混音的 MGW装置内部结构如图 6 所示， 该装置主要包含： 主叫单元 61、 第一被叫单元 62、控制单元 60、 放音单元 63。 通话中存在多个被叫比如两个被叫时， MGW装置还可 以包含： 第二被叫单元 64， 其中， 主叫单元 61包含： 主叫端点 Tl、 主 叫编解码单元 TC1、 主叫混音通道单元 CC1 , 第一被叫单元 62包含： 第一被叫端点 T2、 第一被叫编解码单元 TC2、 第一被叫混音通道单元 CC2, 放音单元 63包含： 放音源单元 631、 放音编解码单元 TC3、 放音 混音通道单元 CC3 , 第二被叫单元 64包含： 第二被叫端点 T4、 第二被 叫编解码单元 TC4、 第二被叫混音通道单元 CC4。
主叫单元 61中的主叫端点 Tl , 与外部的主叫资源交互语音数据， 并与主叫编解码单元 TCI交互语音数据。
主叫单元 61中的主叫编解码单元 TC1 ,接收主叫端点 T1发送的语 音数据， 进行码转换后， 发送给主叫混音通道单元 CC1 , 接收主叫混 音通道单元 CC1发送的语音数据，进行码转换后，发送给主叫端点 Tl。
主叫单元 61中的主叫混音通道单元 CC1 , 接收主叫编解码单元 TC1发送的语音数据后， 转发给第一被叫混音通道单元 CC2和第二被 叫混音通道单元 CC4, 接收第一被叫混音通道单元 CC2和第二被叫混 音通道单元 CC4， 以及放音混音通道单元 CC3发送的语音数据后， 转 发给主叫编解码单元 TC1。
第一被叫单元 62中的第一被叫端点 T2，与外部的第一被叫资源交 互语音数据， 与第一被叫编解码单元 TC2交互语音数据。
第一被叫单元 62中的第一被叫编解码单元 TC2， 接收第一被叫端 点 T2发送的语音数据， 进行码转换后，发送给第一被叫混音通道单元 CC2, 接收第一被叫混音通道单元 CC2发送的语音数据， 进行码转换 后， 发送给第一被叫端点 T2。
第一被叫单元 62中的第一被叫混音通道单元 CC2， 接收第一被叫 编解码单元 TC2发送的语音数据后， 转发给主叫混音通道单元 CC1和 第二被叫混音通道单元 CC4, 接收主叫混音通道单元 CC1和第二被叫 混音通道单元 CC4发送的语音数据后， 转发给第一被叫编解码单元 TC20
控制单元 60, 接收该装置外部的包含 SIGNAL ID的消息， 向放音 单元 63中的放音源单元 631发送混音控制信息。
所述控制单元 60通常可以根据收到的消息， 确定为需要进行混 音。 所述控制单元 60接收的包含 SIGNAL ID的消息可以是由 MGC发 放音单元 63中的放音源单元 631 , 接收控制单元 60发送的混音控 制信息， 向放音编解码单元 TC3发送语音数据。
所述放音源单元 631可以为存储所需要放音的语音数据的放音源 数据库， 也可以为连接 MGW外部存储所需要放音的语音数据的放音 源数据库的放音源数据库接口， 当放音源单元 631为放音源数据库接 口时， 所述放音源单元 631向放音编解码单元 TC3发送的语音数据是 从外部的放音源数据库获取。 通常是 MGW确定为需要进行混音时， 放音源单元 631向放音编解码单元 TC3发送所需要方音的语音数据。
放音单元 63中的放音编解码单元 TC3， 接收放音源单元 631发送 的语音数据， 向放音混音通道单元 CC3发送语音数据。
放音单元 63中的放音混音通道单元 CC3， 接收放音编解码单元 TC3发送的语音数据后， 转发给主叫单元 61中的混音通道单元 CC1。
第二被叫单元 64中的第二被叫端点 T4，与外部的第二被叫用户资 源交互语音数据， 与第二被叫编解码单元 TC4交互语音数据。
第二被叫单元 64中的第二被叫编解码单元 TC4, 接收第二被叫端 点 T4发送的语音数据， 进行码转换后，发送给第二被叫混音通道单元 CC4, 接收第二被叫混音通道单元 CC4发送的语音数据， 进行码转换 后， 发送给第二被叫端点 T4。
第二被叫单元 64中的第二被叫混音通道单元 CC4, 接收第二被叫 编解码单元 TC4发送的语音数据后， 转发给主叫混音通道单元 CC1和 第一被叫混音通道单元 CC2, 接收主叫混音通道单元 CC1和第一被叫 混音通道单元 CC2发送的语音数据后， 转发给第二被叫编解码单元 TC4。
实施例 1、实施例 2中，当 MGW确定为需要进行混音，但如果 MGW 没有配置混音资源，比如： MGW没有插上混音资源单板，则由于 MGW 的内部结构不支持混音，对于 SIGNAL ID对应的语音按照普通语音播 放。
所述 MGW没有配置混音资源具体是指： 图 6中， 如果通话中只存 在一个被叫， 即第一被叫时， MGW没有混音资源是指： 没有主叫编 解码单元 TC1、 主叫混音通道单元 CC1、 第一被叫编解码单元 TC2、 第一被叫混音通道单元 CC2、 放音编解码单元 TC3、 放音混音通道单 元 CC3等单元中的一个或多个； 如果通话中存在多个被叫， 比如图 6 所示两个被叫时， MGW没有混音资源是指： 没有放音编解码单元 TC3、 放音混音通道单元 CC3等单元中的一个或多个。
实施例 1、 实施例 2中， MGW确定为不需要进行混音时， 对于 SIGNAL ID对应的语音也只按照普通语音播放。对于 SIGNAL ID对应 的语音， MGW按照普通语音播放的具体方法可以有多种， 其具体实 现方式不影响本发明中实现混音的方案。 这里， MGW按照普通语音 播放的装置即为 MGW没有配置混音资源的装置。 MGW按照普通语音 播放的装置可以有多种，其具体实现方式不影响本发明中实现混音的 方案。
利用本发明所述方案可以给一个用户播放混音，也可以给多个用 户播放混音。
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明 的使用范围。

Claims

权利要求书
1、 一种实现混音的方法， 其特征在于， 该方法包含以下步骤：
A、 媒体网关控制器 MGC向媒体网关 MGW发送包含信号标识的 消息；
B、 MGW根据收到的消息对信号标识对应的语音和通话音进行 混音。
2、 根据权利要求 1所述的方法， 其特征在于， 步骤 B所述根据收 到的消息进行混音具体为：
' Bl l、 MGW判断收到的信号标识是否是需要混音的放音源所对 应的信号标识， 如果是， 则确定为需要混音播放信号标识对应的语音 数据， 并执行步骤 B12, 否则对信号标识对应的语音不进行混音， 并 结束本处理流程；
B12、 MGW判断自身结构是否支持混音， 如果是， 则对信号标 识对应的语音和通话音进行混音；否则对信号标识对应的语音不进行 混音。
3、 根据权利要求 2所述的方法， 其特征在于， 所述需要混音的放 音源为： MGW预先配置为需要混音的放音源。
4、 根据权利要求 1所述的方法， 其特征在于， 步骤 A所述消息进 一步包含： 播放混音指示；
步骤 B所述根据收到的消息进行混音具体为：
B21、 MGW判断收到的播放混音指示中是否包含需要进行混音 的信息， 如果是， 则确定为需要混音播放信号标识对应的语音数据， 并执行步骤 B22, 否则对信号标识对应的语音不进行混音， 并结束本 处理流程； B22、 MGW判断自身结构是否支持混音， 如果是， 则对信号标 识对应的语音和通话音进行混音；否则对信号标识对应的语音不进行 混音。
5、 居权利要求 4所述的方法， 其特征在于， MGC向 MGW发 送播放混音指示之前， 该方法进一步包含： MGC向 MGW发送添加 至少两个用户端点的消息； 所述至少两个用户端点之间建立通话。
6、 根据权利要求 5所述的方法， 其特征在于， 所述播放混音指示 中进一步包含： 接收所播放语音的用户端点；
步骤 B22中， 确定为需要混音播放时， MGW向所述用户端点混 音播放信号标识对应的语音。
7、 根据权利要求 4至 6任一项所述的方法， 其特征在于， MGC向 MGW发送播放混音指示后， 该方法进一步包含： MGC向 MGW发送 停止播放语音指示；
MGW收到停止播放语音指示后，停止播放信号标识对应的语音。
8、 根据权利要求 6所述的方法， 其特征在于， MGC向 MGW发送 播放混音指示后， 该方法进一步包含： MGC向 MGW发送停止播放语 音指示；
所述停止播放语音指示包含： 停止播放语音的用户端点；
MGW收到停止播放语音指示后， 停止向所述用户端点播放信号 标识对应的语音。
9、 一种实现混音的的装置， 包含： 多个用户单元， 多个用户单 元之间交互语音数据，多个用户单元分别与该装置外部与自身相连接 的不同用户资源交互语音数据， 其特征在于， 该装置进一步包含： 控 制单元、 放音单元；
控制单元， 接收该装置外部的包含信号标识的消息， 向放音单元 发送混音控制信息；
放音单元， 接收控制单元发送的混音控制信息， 向至少一个用户 单元发送语音数据；
所述至少一个用户单元中的每个单元，接收放音单元发送的语音 数据和其余用户单元发送的语音数据进行混音后 ,将混音后的语音数 据发送给该装置外部与自身相连接的用户资源。
10、 根据权利要求 9所述的装置， 其特征在于， 所述每个用户单 元包含： 用户端点、 用户编解码单元、 用户混音通道单元； 所述放音 单元包含： 放音源单元、 放音源编解码单元、 放音源混音通道单元； 所述每个用户单元的用户混音通道单元，接收放音单元的放音源 混音通道单元发送的语音数据和其余用户单元的用户混音通道单元 发送语音数据进行混音后，将混音后的语音数据发送给自身用户单元 的用户编解码单元；接收自身用户单元的用户编解码单元发送的语音 数据后， 转发给其余用户单元的用户混音通道单元；
所述每个用户单元的用户编解码单元，接收自身用户单元的用户 混音通道单元发送的语音数据，进行码转换后发送给自身用户单元的 用户端点； 接收自身用户单元的用户端点发送的语音数据， 进行码转 换后发送给自身用户单元的用户混音通道单元；
所述每个用户单元的用户端点， 与自身用户单元的用户编解码单 元交互语音数据；与该装置外部与自身相连接的用户资源交互语音数 据；
放音单元的放音源单元， 接收控制单元发送的混音控制信息， 向 放音源编解码单元发送语音数据；
放音单元的放音源编解码单元， 接收放音单元发送的语音数据， 进行码转换后发送给放音源混音通道单元； 放音单元的放音源混音通道单元，接收放音源编解码单元发送的 语音数据， 转发给所述至少一个用户单元的用户混音通道单元； 所述至少一个用户单元的用户混音通道单元，接收放音单元的放 音源混音通道单元发送的语音数据后，转发给自身用户单元的用户编 解码单元。
PCT/CN2006/003205 2006-04-19 2006-11-28 Procédé et système de fourniture de service appelé WO2007118379A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200610066673.2 2006-04-19
CN2006100666732A CN1984353B (zh) 2006-04-19 2006-04-19 一种实现混音的方法和装置

Publications (1)

Publication Number Publication Date
WO2007118379A1 true WO2007118379A1 (fr) 2007-10-25

Family

ID=38166497

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/003205 WO2007118379A1 (fr) 2006-04-19 2006-11-28 Procédé et système de fourniture de service appelé

Country Status (2)

Country Link
CN (1) CN1984353B (zh)
WO (1) WO2007118379A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101378430B (zh) * 2007-08-27 2011-01-05 华为技术有限公司 会议中混合指定媒体流的方法、装置和系统
CN103794216B (zh) * 2014-02-12 2016-08-24 能力天空科技（北京）有限公司 一种语音混音处理方法及装置
CN105721469B (zh) * 2016-02-18 2019-09-20 腾讯科技（深圳）有限公司 音频数据处理方法、服务器、客户端以及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003030143A1 (en) * 2001-09-28 2003-04-10 Telefonaktiebolaget Lm Ericsson (Publ) An electronic communications device with a karaoke function
WO2005074240A2 (en) * 2004-01-29 2005-08-11 Volt Information Sciences, Inc. Voice interface board for providing operator services
CN1745564A (zh) * 2003-01-27 2006-03-08 冲电气工业株式会社 电话通信装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2300087B (en) * 1995-04-18 1999-04-28 Ibm Voice processing system and method
JP3719057B2 (ja) * 1999-08-24 2005-11-24 ヤマハ株式会社 電話端末装置および通信方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003030143A1 (en) * 2001-09-28 2003-04-10 Telefonaktiebolaget Lm Ericsson (Publ) An electronic communications device with a karaoke function
CN1745564A (zh) * 2003-01-27 2006-03-08 冲电气工业株式会社 电话通信装置
WO2005074240A2 (en) * 2004-01-29 2005-08-11 Volt Information Sciences, Inc. Voice interface board for providing operator services

Also Published As

Publication number Publication date
CN1984353B (zh) 2010-12-08
CN1984353A (zh) 2007-06-20

Similar Documents

Publication Publication Date Title
EP1848189B1 (en) A method for implementing a multi-media ringback and a system thereof
ES2392858T3 (es) Método y sistema para la reproducción de archivos multimedia
EP2012516B1 (en) Customised playback telephony services
JP5044380B2 (ja) 配信装置及びコーデック変換装置、通信システム
CN110012366B (zh) 一种用于公专网ip互联下的宽窄带融合通信系统及方法
CN101159906B (zh) 呼叫提示信息播放方法及系统
JP2008544638A (ja) 呼セットアップ（ｓｅｔｕｐ：設定）を行う方法及び装置
US20160088043A1 (en) Instant Communications System Having Established Communication Channels Between Communication Devices
JP2017521936A (ja) ビデオメディア再生方法、装置及びシステム、コンピュータ記憶メディア
WO2004093422A1 (ja) マルチメディアｒｂｔ／ｂｔ送出システムおよび方法
WO2008095385A1 (fr) Procédé, système et dispositif d'appel personnalisé
US9531883B2 (en) Providing an announcement for a multiparty communication session
US20090299735A1 (en) Method for Transferring an Audio Stream Between a Plurality of Terminals
CN100563283C (zh) 一种控制回铃音的方法及系统
WO2012113209A1 (zh) 一种在窄带业务中实现宽带放音的方法及系统
WO2007118379A1 (fr) Procédé et système de fourniture de service appelé
US6937704B1 (en) Connection controller for setting-up a media path between a terminal and an audio source
CN100461878C (zh) 实现媒体网关控制协议放音的方法
CN104301551B (zh) 一种音乐播放的方法和设备
US8036209B2 (en) Method and apparatus for announcement for session
WO2013091310A1 (zh) 终端实现呼叫等待的方法、装置和系统
WO2013082927A1 (zh) 一号通业务中实现彩铃业务的方法和一号通业务服务器
WO2016183774A1 (zh) 一种通话录音的方法、装置及系统
JP2008518523A5 (zh)
JP3762709B2 (ja) 音声ｉｐ伝送システム

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: 06828194

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: 06828194

Country of ref document: EP

Kind code of ref document: A1