CN101312428A - Voice packet transmitting and receiving method, media gateway and mobile switching center server - Google Patents

Abstract

The invention provides a method for sending and receiving voice package, a media network gateway and a MSC server thereof. The method comprises steps that: the sender media network gateway combines the common voice packages received at the same time and sent to different users of a receiver media network gateway into a synthesis voice package; and sends the synthesis voice package to the receiver media network gateway. The invention packages a plurality of common voice packages into a synthesis voice package for the transmission between the sender network gateway and the receiver media gateway, wherein the common voice packages share one IP package head, thereby improving the real bandwidth utilization and reducing transmission cost. Further, the invention combines the common voice packages sent to different users of a receiver media network gateway, to eliminate the prolongation of frame length and the waiting time.

Description

Voice packet sending and receiving method, media gateway and mobile switching center server

technical field

The invention relates to the technology of sending and receiving voice packets, in particular to the technology of realizing the sending and receiving of voice packets in a soft switch network with a media gateway, and belongs to the application field of communication technology.

Background technique

Softswitch technology is one of the core technologies of network evolution and next-generation packet network. It realizes the functions of control, connection and business processing of the original switch through software, and connects and communicates with each other through standard protocols. In the next generation network (Next Generation Network, referred to as NGN), various complex protocols can be realized more quickly and services can be provided more conveniently.

The Media Gateway (hereinafter referred to as: MGW) of the softswitch system is a unit that connects different types of networks, and is mainly used for media conversion and frame protocol conversion. When performing voice processing, the MGW can simultaneously support multiple voice codec formats, such as G.711 and G.729.

For example, taking the G.729 codec as an example, when performing voice processing, a digital signal processor is used for the Pulse Code Modulation (PCM) code stream on the Time Division Multiplex (TDM) side. (Digital SignalProcessor, referred to as: DSP) to realize the conversion of voice coding, according to the fixed 10ms packaging time and frame division, do G.729 codec conversion, that is, comply with the G.729 standard protocol, and can perform voice activity detection function according to configuration parameters, Silent compression function and other processing, and then multiplex according to 10ms, 20ms or 30ms multi-frame, encapsulate Real Time Transport Protocol (RTP) header and User Datagram Protocol (User Datagram Protocol: UDP) header, and then send to the IP network. The voice packet structure adopted is shown in Table 1. The rate of the G.729 algorithm is 8Kbit/s, so each voice packet has (20ms×8Kbit/s)/8=20 bytes. The RTP header is fixed at 12 bytes, the UDP header is fixed at 8 bytes, and the IP header is fixed at 20 bytes. Therefore, after each voice packet is encapsulated into an IP data packet, the total length is 60 bytes.

Table 1

20byte 8byte 12byte 20byte

IP header UDP header RTP header G.729 voice frame

Since this IP data packet needs to be sent out within 20ms, the link overhead of Layer 2 is not considered, and calculated according to the G.729 algorithm, the bandwidth of each telephone is 60byte×8/20ms=24kbit/s.

The defect of prior art is: existing voice packet structure needs to increase RTP packet header, UDP packet header, IP packet header, Multiprotocol Label Switching (Multiprotocol Label Switch, MPLS) protocol header, (Point to Point Protocol, Abbreviation: PPP) protocol header, Ethernet (Ethernet), Synchronous Digital Hierarchy (Synchronous Digital Hierarchy, referred to as SDH) optical network and other overheads, due to the small proportion of voice frames, the actual bandwidth utilization is very low, resulting in transmission resources huge waste.

Specifically, when transmitted on an Ethernet link, existing voice packets need to increase Ethernet link layer overhead. For example, the total length of a G.729 voice frame plus Ethernet data link layer overhead is 78 bytes. Plus the physical layer overhead is 98 bytes. Therefore, the physical layer utilization rate of the existing voice packet payload on the Ethernet is only: 20/98=20.4%. When transmitting on the SDH optical network link, several 77-byte data packets are filled into the SDH payload area, and the payload area of an SDH frame can actually only be filled with 30 data packets, that is, 77×30=2310 bytes Therefore, the utilization rate of the softswitch voice packet payload in the 155M link physical layer is about: 20*30/(270*9)=24.7%.

In addition, since voice communication is a real-time service, there are strict requirements on delay. According to existing standards, the time delay on the softswitch side cannot exceed 25ms, otherwise the voice quality will be affected. The frame length of the speech frame encoded and decoded in the G.729 format is 20ms, that is, the delay is already 20ms. Therefore, the bandwidth utilization cannot be improved by extending the frame length, because the longer the frame length, the longer the delay.

Contents of the invention

The problem to be solved by the invention is to improve the bandwidth utilization ratio of the softswitch network without increasing the time delay.

In order to solve the above problems, an embodiment of the present invention provides a method for sending voice packets, including: the originating media gateway synthesizes the ordinary voice packets received at the same time and sent to different users of the same receiving media gateway into a synthesized voice package; sending the synthesized voice package to the receiving media gateway.

In order to solve the above problems, an embodiment of the present invention provides a method for receiving voice packets, including: after receiving the synthesized voice packets, the media gateway at the receiving end splits the synthesized voice packets into ordinary voice packets; Voice packets are processed or forwarded.

In order to solve the above problems, an embodiment of the present invention provides an originating media gateway, including: a first communication module, used to receive common voice packets from different users; Synthesize voice packets received from different users sent to the same receiving media gateway at any time; the second communication module is used to send the synthesized voice packets generated by the synthesizing module to the receiving media gateway.

In order to solve the above problems, an embodiment of the present invention provides a media gateway at the receiving end, including: a splitting module, which is used to split the received synthetic voice packets into ordinary voice packets; a processing module, which is used to split The ordinary voice packets after module splitting are processed or forwarded.

In order to solve the above problems, an embodiment of the present invention provides a method for generating a gateway capability table of a media gateway, including: after the mobile switching center server receives the gateway capability information from the media gateway, the gateway capability information is combined with the The IP address of this media gateway is associated and preserved, and generates the gateway capability table on this mobile switching center server; Send all entry information in the gateway capability table of the media gateway to the media gateway; the media gateway saves the received entry information to generate a gateway capability table on the media gateway.

In order to solve the above problems, an embodiment of the present invention provides a method for updating the gateway capability table of a media gateway, including: after the media gateway detects that the gateway capability table on the media gateway has been modified, it sends a report to the mobile switching center connected to it The server sends a capability table update request message carrying the modified entry information; the mobile switching center server updates the gateway capability table on the mobile switching center server according to the entry information carried in the capability table update request message, and sends a report to the mobile switching center server. Other media gateways connected to the mobile switching center server except the media gateway of the sender send a capability table update command message carrying the updated table item information; the media gateway updates the information on the media gateway according to the table item information carried in the capability table update command message. The gateway capability table of the

In order to solve the above problems, an embodiment of the present invention provides a mobile switching center server, including: a capability table generation module, used to associate the received gateway capability information from the media gateway with the IP address of the media gateway Save and generate the gateway capability table on the mobile switching center server; the first table item sending module is used to send the capability table generation module when detecting that all media gateways connected to the mobile switching center server have completed the gateway capability information sending All the entry information of the generated gateway capability table is sent to the media gateway.

In order to solve the above problems, an embodiment of the present invention provides another mobile switching center server, including: a capability table update module, configured to update the The gateway capability table on the mobile switching center server is updated; the update command sending module is used to send a capability table update command message to other media gateways other than the media gateway of the sender connected to the mobile switching center server, so that the media gateway can update the media gateway for this media gateway. The gateway capability table on the gateway is updated, wherein the capability table update command message carries the updated entry information in the capability table update module.

Through the present invention, since a plurality of ordinary voice packets are encapsulated into a synthesized voice packet for transmission between the media gateway at the originating end and the media gateway at the receiving end, a plurality of ordinary voice packets share one IP header, thus greatly improving the utilization rate of actual bandwidth , reducing the transmission cost. Moreover, by merging common voice packets sent to different users of the same media gateway at the receiving end, there is no need to extend the frame length or wait time.

The technical solutions of the present invention will be described in further detail below with reference to the accompanying drawings and embodiments.

Description of drawings

Fig. 1 is the flow chart of voice packet sending and receiving method described in embodiment 1 of the present invention;

FIG. 2 is a flowchart of a method for generating a gateway capability table according to Embodiment 2 of the present invention;

FIG. 3 is a flowchart of a method for updating a gateway capability table according to Embodiment 3 of the present invention;

Fig. 4 is the flow chart of generating and sending synthetic voice packets described in Embodiment 1 of the present invention;

Fig. 5 is the flowchart of splitting and synthesizing speech packets described in Embodiment 1 of the present invention;

FIG. 6 is a schematic structural diagram of an originating media gateway according to Embodiment 4 of the present invention;

FIG. 7 is a schematic structural diagram of the receiving media gateway according to Embodiment 5 of the present invention;

FIG. 8 is a schematic structural diagram of the MSC server described in Embodiment 6 of the present invention;

FIG. 9 is a schematic structural diagram of another MSC server according to Embodiment 7 of the present invention.

Detailed ways

Example 1

The present embodiment provides a voice packet sending and receiving method, as shown in Figure 1, including:

Step 101, after receiving the ordinary voice packet from the user, the originating media gateway judges whether the receiving end media gateway to which the ordinary voice packet will be sent supports the function of synthesizing voice packets, if yes, execute step 110, otherwise execute step 120, and receive The received ordinary voice packets are directly sent to the receiving media gateway. Wherein, the ordinary voice packet refers to an unmerged voice packet using an existing frame format. It should be pointed out here that this step can be omitted if it is known in advance that all the media gateways in the softswitch network have the ability to support synthesized voice packets.

There are many specific judgment methods. For example, a gateway capability table can be established in the media gateway, as shown in Table 2.

Table 2

MGW name MGW IP address Whether to support synthetic voice package MGW1 10.0.0.1 yes

MGW2 10.0.0.10 yes ... ... ...

The IP address of each media gateway in the softswitch network and the gateway capability information of whether it supports the ability to synthesize voice packets are stored in the gateway capability table. The sending media gateway can determine the gateway capability of the corresponding receiving media gateway by querying the gateway capability table. Wherein, the gateway capability table can be configured manually or automatically.

Step 110, the originating media gateway combines the ordinary voice packets sent to different users of the same receiving media gateway received at the same time, and then sends them to the receiving media gateway. Specifically, the steps shown in FIG. 4 may be used to implement.

Step 110A, pre-setting a cache queue for the MGW in each entry in the originating media gateway according to the entry information in the gateway capability table stored in the gateway.

In step 110B, the originating media gateway adds the ordinary voice packets received at the same time and destined for the same receiving media gateway into the corresponding buffer queue.

Step 110C, encapsulating an ordinary voice packet in a buffer queue into a synthesized voice packet in IP data packet format. Wherein, the IP header of the IP data packet includes the IP address of the receiving media gateway. The format of the IP data packet of the synthesized voice packet is shown in Table 3.

table 3

20 bytes 8 bytes 12 bytes 20 bytes 8 bytes 12 bytes 20 bytes

IP header UDP header RTP header Speech frame UDP header RTP header Speech frame ...

As shown in Table 3, the length of the speech frame in each common speech packet is usually 20 bytes, but in practical applications, the speech frames sent to different users of the same MGW may use different codec methods, therefore, the speech frame The length of may also be different, but this does not affect the synthesis of ordinary speech packets.

In actual Ethernet applications, the maximum allowable length of the above-mentioned synthesized voice packet is preferably not more than the length of the Maximum Transmission Unit (MTU for short) of Ethernet. This is because MTU refers to the largest data packet that is allowed to be transmitted on the Ethernet network. IP data packets that exceed the MTU length will be disassembled and transmitted, which will generate many data packet fragments, and the receiving end needs to wait for all the fragments to arrive. Afterwards, it is reassembled and restored to a complete IP data packet, which will undoubtedly increase the overhead and delay of the network. When the length of the MTU is 1500 bytes, in order to avoid the system overhead caused by fragmentation and reassembly of IP data packets, the length of the synthesized voice packet should not exceed 1500 bytes. Assuming that there are N ordinary voice packets synthesized into synthetic voice packets, UDP header + RTP header + voice frame length = 40 bytes, IP header is 20 bytes, and Ethernet Layer 2 overhead is 18 bytes, then N should satisfy Inequality: 40×N+20<=1500-18, the calculation result is: N<=36, that is, in order to avoid the problem of fragmentation and reassembly of IP packets, the number of ordinary voice packets that can be synthesized into synthetic voice packets is at most 36 indivual. The length of the IP payload of the synthesized voice packet is 1440 bytes, which can be filled with 36 synthesized voice packets encoded and decoded by G.729 with a frame length of 20 ms. If voice frames of other codecs are encapsulated, the IP payload length and the number of UDP voice packets will change, but the IP payload length cannot exceed 1482 bytes.

Step 110D, send the synthesized voice packet to the receiving media gateway, and clear the cache queue.

Since the multiple ordinary voice packets synthesized into the synthesized voice packet are sent to the originating media gateway at the same time, no waiting time is required, and the waiting delay will not be increased. In addition, a queue timer can also be set in the media gateway at the originating end. If the total length of the synthesized voice packet after encapsulation reaches the length of the maximum transmission unit of the Ethernet within a predetermined timing time, then the timing time will not wait until the timing arrives. It starts to encapsulate the ordinary voice packets in the buffer queue.

If within the predetermined timing time, the total length of the encapsulated synthetic voice packet does not reach the length of the maximum transmission unit of Ethernet, then when the timing time arrives, the ordinary voice packet in the cache queue is encapsulated A synthetic voice packet in IP packet format.

The purpose of doing this is to synthesize as many ordinary voice packets as possible under the allowable delay condition, so as to improve the utilization rate of network bandwidth as much as possible. However, in order to avoid too long delay time, the timing time of the above queue timer can be configured as required, for example, it can be set to 5ms by default. The purpose of setting the queue timer is to prevent too few ordinary voice packets sent to a certain MGW within a certain period of time, resulting in too long waiting time, thereby causing the problem of too long delay.

Step 111: After receiving the synthesized voice packet, the media gateway at the receiving end splits it into ordinary voice packets, and then processes them as ordinary voice packets. Specifically, as shown in Figure 5, the following steps may be included:

In step 111A, after receiving the voice packet from the originating media gateway, the receiving media gateway judges whether the voice packet is a synthesized voice packet, and if so, executes step 111B; otherwise, treats the voice packet as a normal voice packet.

Concrete judging method can be: the total length field value in the IP packet header of receiving voice packet is compared with the length field value in a UDP packet header in this voice packet, if the difference between the two is greater than the length of IP packet header, for example , assuming that the length of the IP header used is 20 bytes, and the difference between the above two is greater than 20 bytes, it indicates that the voice packet contains at least one UDP data packet, indicating that the voice packet is a synthetic voice packet; otherwise, if If the difference between the above two is equal to the length of the IP packet header, it indicates that the voice packet is an unsynthesized ordinary voice packet.

Step 111B, split the synthesized voice packets into common voice packets, and process them as normal voice packets.

Specifically, by adding an unpacking function layer in the media gateway at the receiving end, the function is located between the IP layer and the UDP layer. After the media gateway at the receiving end judges that the received voice packet is a synthesized voice packet, it will not The packet is forwarded to the UDP protocol module for processing but forwarded to the unpacking functional layer for processing.

Specifically, the function of the unpacking functional layer can be realized by the following algorithm:

Let L1 be the length of the IP packet header, L2 be the total length of the synthetic voice IP packet, L_ip=L2-L1, L_udp=the value in the length field in the first UDP packet header.

int i, j;

i＝L1, j＝L1+L_udp; //Set the split point in the synthesized voice package

L=L_ip-L_udp; //The difference between the length of the IP header and the total length of the synthetic voice packet

while(L＞＝0) //Set split condition

{

Send the content between i and j to the UDP protocol processing module; // split the UDP voice packet

if(L＝0)break; //Judge whether the split is complete

L_udp=the value in the length field in the next UDP packet header;

i=j;

j=i+L_udp;//update split point

L=L-L_udp;

}

By the method described in the present embodiment, because a plurality of ordinary voice packets are encapsulated into a synthetic voice packet for transmission between the media gateway of the originating end and the media gateway of the receiving end, a plurality of ordinary voice packets share an IP packet header, thus greatly improving actual bandwidth utilization. Analysis shows that when the synthesized voice packet described in this implementation is used to transmit on the Ethernet link, the required bandwidth is only 0.42 of the existing method; when transmitted on the SDH link, the required bandwidth is only 0.54 of the existing method, which saves about half of the bandwidth resources, thus greatly improving the actual bandwidth utilization and reducing the transmission cost.

Moreover, the method described in this embodiment is to combine the ordinary voice packets sent to different users of the same receiving media gateway. There are a lot of common speech packets received from different users. Combining these common speech packets requires almost no frame length extension or waiting time, except for a certain synthesis time. The synthesis time is only on the order of microseconds, which is almost negligible compared with the speech frames on the order of milliseconds.

Example 2

The specific method for generating and updating the gateway capability table described in the above step 101 can be implemented by the media gateway in cooperation with the mobile switching center (Mobile Switching Center, referred to as: MSC) server. Among them, the MSC server is a functional entity in the MSC, which implements the switching function in the softswitch core network together with the MGW, and is specifically described as follows:

The generation process of the gateway capability table is shown in Figure 2.

In step 201, the MGW sends the gateway capability information of the gateway to the connected MSC server to inform the MSC server whether the gateway has the ability to support synthesized voice packets.

Specifically, it can be realized through the non-standard data (Non Standard Data) parameter in the server service change request (ServerServiceChange.Req) command in the existing protocol. For example, the non-standard data parameter can be set as "MGW name, MGW IP address, support synthesized voice package", which means that the MGW with this IP address supports the function of synthesized voice package.

In step 202, the MSC server associates the received gateway capability information from the MGW with the IP address of the MGW and saves it in the gateway capability table on the server, that is, generates the gateway capability table shown in Table 4.

Step 203, when the MSC server detects that all the MGWs connected to it have completed sending the gateway capability information, it sends all the entry information of the gateway capability table to the MGW for storage.

Step 204, if there are multiple MSC servers in a softswitch network, after one MSC server completes the generation of the gateway capability table, it can also send the entry information of the gateway capability table to the adjacent MSC server.

Specifically, it may be implemented through an initial address management (Initial Address Management, IAM) message in a Bearer Independent Call Control Protocol (BICC for short) protocol. For example, the station number of the receiving MSC server can be filled in the called number (CalledNumber, CLD for short) field of the IAM message, and the codec list (CodecList) field can be filled with "MGW name, MGW IP address, and support for synthetic voice packets".

Step 205, the adjacent MSC server saves the received entry information on the server, and then notifies the MGW connected to it in a similar manner to step 203, and the MGW copies the gateway capability table from the adjacent MSC server to the Save this gateway.

What needs to be pointed out here is that the MSC server that has received the IAM message will not send IAM messages to other adjacent MSC servers. This is to avoid loops or infinite loops in the system. If the receiving MSC server needs to send the MGW gateway capability information set in the local domain to the sending MSC server, it can be realized through the Application Transport Mechanism (Application Transport Mechanism, APM for short) message in the existing protocol.

What needs to be pointed out here is that the gateway capability table is configured on the MGW through steps 201-205, but it is also possible to configure the gateway capability table on each MGW manually instead of the above method, and through this embodiment The method can automatically realize the configuration of the gateway capability table, which is beneficial to improve configuration efficiency.

Through the method described in this embodiment, the gateway capability table is automatically generated, which is faster, more efficient, and more accurate than manual configuration, and saves labor costs.

Example 3

This embodiment provides a method for updating the gateway capability table on the media gateway, as shown in Figure 3, including the following steps:

In step 301, after the MGW detects that the gateway capability table saved in the local gateway has been modified, it sends a capability table update request message to the MSC server, which carries the modified entry information. Specifically, the MGW may report to the MSC server through a notification request message (Notify.reqeust) in the existing protocol, requesting to update relevant information of the gateway capability table.

Wherein, the user can modify the gateway capability table saved on the MGW through the user interface configured on the MGW. Specifically, the user can enable or disable the synthesized voice packet function of the gateway through the user interface.

In step 302, after receiving the capability table update request message from the MGW, the MSC server updates the corresponding entry in the gateway capability table stored on the server according to the entry information carried therein.

Step 303, after the MSC server finishes updating the gateway capability table, it sends a capability table update command message carrying updated entry information to other MGWs connected to the MSC server. Specifically, the capability table update command message may adopt a modification request message (Modify.request) in the existing protocol.

In addition, the MSC server may also reply a capability table update acknowledgment message to the MGW requesting to update the entry as needed, so as to notify the MGW that the gateway capability table has been updated. Specifically, the capability table update confirmation message may adopt a notification response message (Notify.reply) in the existing protocol.

Step 304, after receiving the capability table update command message, the MGW updates the gateway capability table stored on the local gateway according to the entry information carried therein.

Step 305, if there are multiple MSC servers in a softswitch network, after an MSC server completes the update of the gateway capability table, it can also send the updated entry information to the adjacent MSC server, and the adjacent MSC server will update this server. and the gateway capability table on the MGW connected to it are updated. Specifically, according to a method similar to that described in step 205, the entry information transmission can be implemented through an IAM message.

It should be pointed out here that if the user modifies the gateway capability table saved on the MSC server instead of the gateway capability table saved on the MGW, the MSC server can directly send the updated table entries to all other MGWs connected to it. information of a capability table update command message; after receiving the capability table update command message, the MGW updates the gateway capability table stored on the gateway according to the entry information carried therein. Specifically, the capability table update command message may adopt a modification request message (Modify.request) in the existing protocol.

Through the method described in this embodiment, the automatic update of the gateway capability table is realized. Compared with the manual configuration, the speed is faster, the efficiency is higher, and the accuracy is higher. When the network structure changes, the update can be automatically implemented. More timely and save labor costs.

Example 4

This embodiment provides an originating media gateway. As shown in FIG. 6 , the originating media gateway 4 includes: a first communication module 41 , a combining module 42 and a second communication module 43 .

Wherein, the first communication module 41 is used to receive the ordinary voice packets from different users; the synthesis module 42 is used to send the ordinary voices of different users received by the first communication module 41 at the same time to the same receiving media gateway The packets are synthesized into synthesized voice packets; the second communication module 43 is configured to send the synthesized voice packets generated by the synthesis module 42 to the receiving media gateway. Specifically, in order to avoid the system overhead caused by fragment reassembly when IP data packets are transmitted over Ethernet, when the total length of the synthesized voice packets encapsulated in the first communication module 41 reaches the maximum transmission unit of Ethernet When the length is , the second communication module 43 can send it.

Specifically, the synthesis module 42 may specifically include: a caching module 42A and a packaging module 42B. Wherein, the cache module 42A is used to set the buffer queue for the receiving media gateway, and add the ordinary voice packets sent to different users of the same receiving media gateway received by the first communication module 41 at the same time to the corresponding buffer queue The encapsulation module 42B is used to encapsulate the common voice packet in a cache queue in the cache module 42A into a synthetic voice packet in the IP data packet format, wherein the IP header of the IP data packet contains the receiving end IP address of the media gateway.

In addition, a timing module 42C can also be set in the synthesis module 42: for setting a queue timer, when the timing time of the queue timer arrives, a timing signal is sent to the encapsulation module 42B; after the encapsulation module 42B receives the timing signal, although At this time, the total length of the synthesized voice packets after encapsulating the normal voice packets in the cache queue in the buffer module 42A does not reach the length of the maximum transmission unit of Ethernet, but the step of encapsulating the synthesized voice packets is still started. The purpose of doing this is to synthesize as many ordinary voice packets as possible under the allowable delay condition, so as to improve the utilization rate of network bandwidth as much as possible. However, in order to avoid too long delay time, the timing time of the above queue timer can be configured as required, for example, it can be set to 5ms by default. The purpose of setting the queue timer is to prevent too few ordinary voice packets sent to a certain MGW within a certain period of time, resulting in too long waiting time, thereby causing the problem of too long delay.

In addition, the originating media gateway 4 may further include a capability judging module 44 for judging whether the receiving media gateway to which the ordinary voice packets received by the first communication module 41 from the user are to be sent supports the function of synthesizing voice packets, If yes, send the judgment result to the synthesizing module 42, so that the synthesizing module 42 starts to execute the step of encapsulating and synthesizing voice packets; otherwise, the ordinary voice packets received by the first communication module 41 are directly sent to the receiving media gateway.

Through the originating media gateway described in this embodiment, it is realized that ordinary voice packets are encapsulated into synthesized voice packets, which greatly improves the utilization rate of the actual bandwidth and does not cause delay.

Example 5

This embodiment provides a receiving media gateway. As shown in FIG. 7 , the receiving media gateway 5 includes: a splitting module 51 and a processing module 52 .

Wherein, the splitting module 51 is used for splitting the received synthesized speech packets into ordinary speech packets; the processing module 52 is used for processing or forwarding the ordinary speech packets split by the splitting module 51 .

In addition, the media gateway 5 at the receiving end may further include a voice packet judging module 53 for judging whether the received voice packet from the media gateway at the sending end is a synthetic voice packet, and if so, the synthetic voice packet is sent to the splitting module 51.

Through the media gateway at the receiving end described in this embodiment, it is realized that the synthesized voice packets are divided into ordinary voice packets, and the receiving and processing of the ordinary voice packets is completed.

Example 6

This embodiment provides a mobile switching center server, that is, an MSC server. As shown in FIG. 8 , the MSC server 6 includes: a capability table generating module 61 and a first entry sending module 62 .

Among them, the capability table generation module 61 is used to associate and store the received gateway capability information from the MGW with the IP address of the MGW, and generate a gateway capability table on the server; the first entry sending module 62 is used to detect After all the MGWs connected to the server have finished sending the gateway capability information, all the item information of the gateway capability table generated by the capability table generation module 61 is sent to each MGW.

In addition, if there are multiple MSC servers in a network, after one MSC server completes the generation of the gateway capability table, it can also send the entry information of the gateway capability table to the adjacent MSC server. Therefore, the MSC server 6 described in this embodiment may further include a second entry sending module 63, which is used to generate the capability table generating module 61 after detecting that all MGWs connected to the server have completed sending gateway capability information. All entry information in the gateway capability table of the gateway is sent to the adjacent MSC server. Correspondingly, a third entry sending module 64 can also be set in the MSC server 6, which is used to send the entry information from the adjacent MSC server to all MGWs connected to this server, so that these MGWs can generate gateways on this gateway. Ability table.

Through the MSC server described in this embodiment, automatic generation of the gateway capability table is realized. Suitable for networks with one or more MSC servers.

Example 7

This embodiment provides another MSC server 7 , as shown in FIG. 9 , including: a capability table update module 71 and an update command sending module 72 .

Among them, the capability table update module 71 is used to update the gateway capability table on the server according to the entry information carried in the capability table update request message from the MGW; the update command sending module 72 is used to send the MGWs other than the sender MGW send a capability table update command message to enable the MGW to update the gateway capability table on the gateway, wherein the capability table update command message carries the updated entry information in the capability table update module 71 .

In addition, the MSC server 7 can also include: an update information sending module 73, which is used to send the updated table item information in the capability table update module 71 to the adjacent MSC server, so that the adjacent MSC server can compare and match with the corresponding table item information according to the table item information. The gateway capability table on the MGW connected to the adjacent MSC server is updated.

Through the MSC server described in this embodiment, automatic updating of the gateway capability table is realized. Suitable for networks with one or more MSC servers.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention without limitation. Although the present invention has been described in detail with reference to the preferred embodiments, those of ordinary skill in the art should understand that the technical solutions of the present invention can be The scheme shall be modified or equivalently replaced without departing from the spirit and scope of the technical scheme of the present invention.

Claims (31)

1. A voice packet sending method, characterized in that, comprising: The originating media gateway synthesizes the ordinary voice packets received at the same time and sent to different users of the same receiving media gateway into synthesized voice packets; Send the synthesized voice packet to the receiving media gateway. 2. The voice packet processing method according to claim 1, wherein said originating media gateway synthesizing said ordinary voice packet into a synthesized voice packet specifically comprises: Pre-setting a cache queue for the receiving media gateway; Add the ordinary voice packets received at the same time and sent to different users of the same receiving media gateway to the corresponding buffer queue; Encapsulating a common voice packet in a cache queue into a synthesized voice packet in the format of an IP data packet, wherein the IP header of the IP data packet contains the IP address of the receiving media gateway. 3. The voice packet processing method according to claim 2, characterized in that, the execution conditions for the media gateway at the originating end to encapsulate a common voice packet in a cache queue into a synthesized voice packet in an IP packet format are: Within a predetermined timing time, the total length of the encapsulated synthetic voice packet reaches the maximum transmission unit length of Ethernet. 4. The voice packet processing method according to claim 3, characterized in that, said originating media gateway encapsulates a common voice packet in a cache queue into a synthesized voice packet in IP packet format specifically comprising: If within the predetermined timing time, the total length of the encapsulated synthetic voice packet does not reach the length of the maximum transmission unit of Ethernet, then when the timing time arrives, the ordinary voice packet in the cache queue is encapsulated A synthetic voice packet in IP packet format. 5. The voice packet processing method according to claim 2, 3 or 4, characterized in that, after the originating media gateway sends the synthesized voice packet to the receiving media gateway, it further comprises: clearing the cache queue. 6. The voice packet processing method according to claim 1, characterized in that, before the originating media gateway synthesizes the ordinary voice packet into a synthesized voice packet, it further includes: After receiving the ordinary voice packet from the user, it is judged whether the receiving media gateway to which the ordinary voice packet is to be sent supports the function of synthesizing voice packets, and if so, the ordinary voice packet is synthesized into a synthetic voice packet. 7. The voice packet processing method according to claim 6, wherein the determining whether the receiving media gateway supports the function of synthesizing voice packets by the originating media gateway further comprises: If not supported, the received ordinary voice packet is directly sent to the receiving media gateway. 8. The voice packet processing method according to claim 6, wherein the determining by the originating media gateway whether the receiving media gateway supports the function of synthesizing voice packets specifically includes: The judgment is made according to the gateway capability table pre-established in the originating media gateway, wherein the gateway capability table stores the IP address of the media gateway and the gateway capability information of whether it supports the ability to synthesize voice packets. 9. A voice packet receiving method, characterized in that, comprising: After receiving the synthetic voice packet, the media gateway at the receiving end splits the synthetic voice packet into common voice packets; Process or forward the split ordinary voice packets. 10. The voice packet receiving method according to claim 9, characterized in that, before the media gateway at the receiving end splits the synthesized voice packet into common voice packets, it further includes: After receiving the voice packet from the originating media gateway, the receiving media gateway judges whether the voice packet is a synthesized voice packet, and if so, splits the synthesized voice packet into ordinary voice packets. 11. The voice packet receiving method according to claim 10, wherein the receiving media gateway judging whether the voice packet is a synthesized voice packet further comprises: If it is not a synthesized voice packet, the voice packet is processed or forwarded as a normal voice packet. 12. The voice packet receiving method according to claim 10, wherein the receiving media gateway judging whether the voice packet is a synthesized voice packet specifically includes: Comparing the total length field value in the IP header in the voice packet with the length field value in a UDP header in the voice packet, if the difference between the two is greater than the length of the IP header, then it is judged that the voice The package is a synthetic voice package. 13. The voice packet receiving method according to claim 9, wherein said processing or forwarding the split ordinary voice packets specifically comprises: Send the ordinary voice packet in UDP packet format after splitting to the UDP protocol module. 14. An originating media gateway, comprising: The first communication module is used to receive common voice packets from different users; Synthesizing module, used for synthesizing the normal voice packets sent to different users of the same receiving media gateway received by the first communication module at the same time into synthetic voice packets; The second communication module is configured to send the synthesized voice packet generated by the synthesizer module to the receiving media gateway. 15. The originating media gateway according to claim 14, wherein the synthesis module comprises: A cache module, configured to set a cache queue for the receiving media gateway, and add ordinary voice packets sent to different users of the same receiving media gateway received by the first communication module at the same time to the corresponding buffer queue middle; An encapsulation module, configured to encapsulate an ordinary voice packet in a cache queue in the cache module into a synthesized voice packet in an IP data packet format, wherein the IP header of the IP data packet includes the receiving media gateway IP address. 16. The originating media gateway according to claim 14, wherein the synthesis module comprises: Timing module, for setting queue timer, when the timing time of this queue timer arrives, send timing signal to described encapsulation module, after instruction encapsulation module receives this timing signal, begin to carry out the step of encapsulating described synthetic voice packet . 17. The originating media gateway according to claim 14, further comprising: Capability judging module, for judging whether the receiving end media gateway that the first communication module receives from the user's ordinary voice packet to be sent to supports the function of synthesizing voice packets, if so, send the judgment result to the synthesizing module, so that the The synthesizing module starts to execute the step of encapsulating the synthesized voice packet; otherwise, the ordinary voice packet received by the first communication module is directly sent to the receiving media gateway. 18. A receiving media gateway, characterized by comprising: A splitting module is used to split the received synthetic speech packets into common speech packets; The processing module is used for processing or forwarding the ordinary voice packets split by the splitting module. 19. The receiving media gateway according to claim 18, further comprising: The voice packet judging module is used to judge whether the received voice packet from the originating media gateway is a synthesized voice packet, and if so, send the synthesized voice packet to the splitting module. 20. A method for generating a gateway capability table of a media gateway, comprising: After the mobile switching center server receives the gateway capability information from the media gateway, associate and save the gateway capability information with the IP address of the media gateway, and generate the gateway capability table on the mobile switching center server; After the mobile switching center server detects that all the media gateways connected to it have completed sending the gateway capability information, all the entry information of the gateway capability table on the mobile switching center server is sent to the media gateway; The media gateway saves the received entry information, and generates a gateway capability table on the media gateway. 21. The method for generating the gateway capability table of the media gateway according to claim 20, characterized in that, after the mobile switching center server generates the gateway capability table on the mobile switching center server, it further includes: The mobile switching center server sends all entry information of the gateway capability table on the mobile switching center server to the adjacent mobile switching center server. 22. The method for generating the gateway capability table of the media gateway according to claim 21, characterized in that after receiving the entry information, the method further includes: saving the received entry information, and generating a gateway capability table on the adjacent mobile switching center server; Send all the entry information of the generated gateway capability table to all media gateways connected to the adjacent mobile switching center server for storage, and generate a gateway capability table on the media gateway. 23. The method for generating the gateway capability table of the media gateway according to claim 21, wherein the mobile switching center server sends the entry information to the adjacent mobile switching center server specifically as follows: The mobile switching center server sends the entry information to the adjacent mobile switching center server in an initial address management message in a bearer-independent call control protocol. 24. The method for generating the gateway capability table of the media gateway according to claim 23, characterized in that, after receiving the initial address management message, the adjacent mobile switching center server further includes: Carrying all entry information of the gateway capability table on the adjacent MSC server in an application delivery mechanism message and replying to the MSC server of the sender. 25. A method for updating a gateway capability table of a media gateway, comprising: After the media gateway detects that the gateway capability table on the media gateway has been modified, it sends a capability table update request message carrying the modified table item information to the mobile switching center server connected to it; The mobile switching center server updates the gateway capability table on the mobile switching center server according to the entry information carried in the capability table update request message, and sends a message to other media gateways connected to the mobile switching center server except the sending media gateway A capability table update command message carrying updated entry information; The media gateway updates the gateway capability table on the media gateway according to the entry information carried in the capability table update command message. 26. The method for updating the gateway capability table of the media gateway according to claim 25, wherein after the mobile switching center server updates the gateway capability table, it further includes: Send the updated entry information to the adjacent mobile switching center server; The device updates the gateway capability table on the media gateway connected to the adjacent mobile switching center service according to the entry information. 27. A mobile switching center server, comprising: A capability table generation module, used for correlating and saving the received gateway capability information from the media gateway with the IP address of the media gateway, and generating the gateway capability table on the mobile switching center server; The first entry sending module is used to send all the entry information of the gateway capability table generated by the capability table generating module to the media gateway. 28. The mobile switching center server according to claim 27, further comprising: The second entry sending module is used to send all the entry information of the gateway capability table generated by the capability table generation module to Adjacent mobile switching center server. 29. The mobile switching center server according to claim 28, further comprising: The third entry sending module is used to send the entry information from the adjacent mobile switching center server to all media gateways connected to the adjacent mobile switching center server, so that the media gateways generate the gateway on the media gateway Ability table. 30. A mobile switching center server, further comprising: A capability table update module, configured to update the gateway capability table on the mobile switching center server according to the entry information carried in the capability table update request message from the media gateway; The update command sending module is used to send a capability table update command message to other media gateways connected to the mobile switching center server except the media gateway of the sender, so that the media gateway updates the gateway capability table on the mobile switching center gateway, Wherein, the capability table update command message carries the updated entry information in the capability table update module. 31. The mobile switching center server according to claim 30, further comprising: The update information sending module is used to send the updated entry information in the capability table update module to the adjacent mobile switching center server, so that the adjacent mobile switching center server can update the gateway capability table on the corresponding media gateway according to the entry information. to update.

Images