WO2008011821A1

WO2008011821A1 - System, apparatus and communicaiton method with sip trunk group

Info

Publication number: WO2008011821A1
Application number: PCT/CN2007/070271
Authority: WO
Inventors: Tianyu Yang; Qing Wen; Ming Tao; Benping Shuai
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-07-21
Filing date: 2007-07-11
Publication date: 2008-01-31
Also published as: CN1901541A; CN1901541B

Abstract

A system with SIP trunk group is disclosed. The system includes a first SIP entity, which transmits the calling external SIP message in the selected SIP trunk group. There is a corresponding relation between the source IP address, teminal IP address and character field of said SIP message and the said SIP trunk group; A second SIP entity, which receives the SIP message and determines which SIP trunk group it belongs according to the source IP address, terminal IP address and character field, and then processes service-task according to the SIP trunk group.A corresponding communication method is also disclosed. As a result, any two IP addresses in two SIP entities can be with multiple SIP trunk groups, the SIP calling management is more effective and the telecommunication capacity between SIP callings is stronger.

Description

System, device and communication method with SIP relay group

This application claims priority to Chinese Patent Application No. 200610061791.4, entitled "System and Communication Method with SIP Relay Group", filed on July 21, 2006, the entire contents of which are incorporated by reference. In this application.

Technical field

The present invention relates to the field of communications, and in particular, to a system, apparatus, and communication method for a SIP (Session Initiation Protocol) relay group.

Background technique

In an NGN (Next Generation Network) network, when interworking between a softswitch device and a softswitch device, and between a softswitch device and other SIP entities that need to be connected to the softswitch device through the SIP protocol to implement call control Although there is no circuit concept, the call between two SIP entities can still be divided into different groups to distinguish different call sources and other call related attributes, and the same group gives the same call attributes. Different groups may have the same or different call attributes, and such a group is referred to herein as a SIP trunk group (SIPTG).

Referring to FIG. 1 , an existing system with a SIP trunk group includes a first SIP entity and a second SIP entity, where the first SIP entity and the second SIP entity each include multiple service modules, a first SIP entity and a second The SIP entity includes multiple IP addresses. The prior art implements SIP trunk group division by combining the source IP (Internet Protocol) address and the destination IP address. The service modules of the two SIP entities are in SIP. The SIP attribute of the group is processed according to the call attribute of the group, and only one SIP trunk group can be added between the two IP addresses. Therefore, in the existing system with SIP trunk group, the number of partitionable SIP trunk groups is limited by the IP address resources owned by the SIP entity, since SIP call management is usually performed for SIP trunk groups, and the number is limited. The SIP trunk group is not conducive to effective call management.

Summary of the invention

The embodiment of the invention provides a communication method, device and system with a SIP relay group, which can implement multiple SIP relay groups between any two IP addresses of two SIP entities, and improve SIP calls. The effectiveness of management.

The system with the SIP protocol relay group provided by the embodiment of the present invention includes: a first SIP entity, configured to send an out-of-call SIP message on a selected SIP trunk group, where the SIP trunk group and the source IP address, the destination IP address, and the feature field of the out-of-call SIP message have Correspondence relationship

a second SIP entity, configured to receive the out-of-call SIP message, determine a SIP trunk group to which it belongs according to its source IP address, destination IP address, and feature field, and perform message distribution according to the SIP trunk group .

An apparatus with a SIP trunk group according to an embodiment of the present invention includes:

At least one service module, configured to select a SIP trunk group used for sending an out-of-call SIP message, and generate the call by using a source IP address, a destination IP address, and a feature field corresponding to the SIP trunk group. External SIP message;

And a sending module, configured to send the out-of-call SIP message.

Another apparatus having a SIP relay group according to an embodiment of the present invention includes at least one service module, and:

a receiving module, configured to receive an out-of-call SIP message;

a group dividing module, configured to determine, according to a source IP address, a destination IP address, and a feature field of the SIP message, a SIP trunk group to which the SIP message belongs, and send the SIP trunk group to a service module according to the SIP trunk group to which the SIP message belongs .

The embodiment of the invention further provides a communication method with a SIP relay group, including:

Select the SIP trunk group used to send out-of-call SIP messages;

The out-of-call SIP message is sent by using a source IP address, a destination IP address, and a feature field corresponding to the selected SIP trunk group.

Another communication method with a SIP relay group according to an embodiment of the present invention includes:

Receiving an outbound SIP message;

The SIP trunk group to which the SIP message belongs is determined according to the source IP address, the destination IP address, and the feature field of the SIP message, and the message is distributed according to the SIP trunk group to which it belongs.

The SIP trunk group enables multiple SIP trunk groups to be implemented between any two IP addresses of the two SIP entities, thereby improving the effectiveness of SIP call management and enhancing the telecom operation capability of the SIP call. DRAWINGS 1 is a schematic diagram of a system with a SIP trunk group in the prior art;

2 is a schematic diagram of a system with a SIP trunk group in an embodiment of the present invention;

FIG. 3 is a structural diagram of a system with a SIP trunk group in an embodiment of the present invention.

detailed description

In order to enable multiple SIP trunk groups between any two IP addresses of two SIP entities,

The SIP entity may perform the division of the SIP trunk group according to the combination of the IP address and the port, and the judgment conditions include: a combination of the source IP address, the destination IP address, and the destination port; the source IP address, the destination IP address, the source port, and Combination of destination ports; or combination of source IP address, destination IP address, and source port.

Embodiment 1 : Performing division of a SIP trunk group according to a combination of a source IP address, a destination IP address, and a destination port as a judgment condition

Referring to FIG. 2, the system with a SIP trunk group in this embodiment includes a first SIP entity 300 and a second SIP entity 400.

The first SIP entity 300 includes a plurality of service modules 311, 312, 313 to 31s. Each service module may reside on a different hardware entity, each service module has a unique local port bound, and the service modules 311, 312, The local ports bound to 313 and 3 Is are local ports 321, 322, 323, and 32s, respectively. The IP address 331 and the IP address 332 to the IP address 33p are the addresses of the first SIP entity 300 for sending or receiving SIP messages. Each IP address corresponds to multiple service ports 341, 342 to 34n (the service port may be a SIP well-known port 5060 or Is another configurable port), each service port is used to receive and send SIP messages.

The second SIP entity 400 includes a plurality of service modules 411, 412, 413 to 41t, each of which has a unique local port bound, and the local ports bound by the service modules 411, 412, 413, and 41t are local ports 421, respectively. 422, 423 and 42t. The IP address 431, the IP address 432 to the IP address 43q are the addresses of the second SIP entity 400 for sending or receiving SIP messages. Each IP address corresponds to multiple service ports 441, 442 to 44n, and each service port is used for receiving and transmitting SIP. Message.

When the first SIP entity 300 is connected to the second SIP entity 400, multiple SIP trunk groups may be added between any two IP addresses, and the call on each SIP trunk group may be in the first SIP entity 300 or the second SIP. Load sharing is implemented on the business module of the entity 400.

The following is an example of interworking between the first SIP entity 300 and the second SIP entity 400.

When any one of the first SIP entities 300 initiates a call to the second SIP entity 400 through any of the external IP addresses and the service port, the service module 311 and the IP on the first SIP entity 300 are now used. The call between the address 332 and the IP address 432 on the second SIP entity 400 is described as an example: For the SIP message outside the first call, the source IP address is the IP address 332, the source port is the local port 321, and the destination IP address. The address is the IP address 432 of the second SIP entity 400, the destination port is the service port 44n, that is, the address in the SIP header field is filled in with the IP address 332, the address in the Contact header field is filled in the IP address 332, and the port is the local port 321; RequestUri and The IP address in the TO header field is filled in as the IP address 432, and the port is the service port 44n; then the SIP message will be the SIP trunk group corresponding to the source IP address 332, the destination IP address 432, and the destination port 44n by the first SIP entity 300. Send on, as shown in the SIPTG-21 connection in Figure 2. The SIP message header field and the message body are filled in according to the SIP protocol and the specific application.

After receiving the SIP message, the second SIP entity 400 confirms that the call is a call on the SIPTG-21 according to the source IP address, the destination IP address, and the destination port of the message. The response message sent by the second SIP entity 400 to the first SIP entity 300 and the subsequent request message are implemented according to the SIP protocol standard. The second SIP entity 400 initiates a call to the first SIP entity 300 and also initiates a call to the second SIP entity 400 similar to the first SIP entity 300. In this way, the call between the IP address 332 and the IP address 432 can be divided into calls on multiple different SIP trunk groups by using the source IP address, the destination IP address, and the destination port, and different call sources are assigned according to actual operation requirements. Related call properties.

The load sharing of the call on each service module is implemented according to a certain load sharing strategy. Taking the second SIP entity 400 as an example, after the uplink SIP message arrives at the service port, it can be distributed to the local port of the service module according to a certain sharing policy; the downlink can be selected by the upper layer application or protocol, and the service module is based on the service module. A certain strategy selects a SIPTG to send SIP messages. For example, the second SIP entity 400 receives the SIP message on the SIPTG-21 with the IP address 432 and the service port 44n, and the message is according to a certain load sharing policy (for example, according to the average allocation of the call or the proportion of the call according to each service module). The processing is distributed to the service module 411, and the message may be distributed from the service port 44n to other service modules, and the service module performs service processing according to the common call attribute of the relay group SIPTG-21; The subsequent message processing path remains the same as the processing path of the call.

Embodiment 2: According to a combination of a source IP address, a destination IP address, a source port, and a destination port as a judgment condition, a SIP trunk group is divided.

This embodiment is similar to the foregoing Embodiment 1 solution, except that: the sender selects the SIP trunk group used for sending the out-of-call SIP message according to the load sharing policy, and the sender corresponds to the SIP trunk group. Source IP address, source port, destination IP address, and destination port to generate the message; When receiving the SIP message outside the call, the receiving SIP entity determines the SIP trunk group according to the source IP address, the source port, the destination IP address, and the destination port, and then according to the load sharing policy. The message is distributed to the corresponding service module, and the service module performs service processing according to the call attribute of the SIP trunk group.

Embodiment 3: According to a combination of a source IP address, a destination IP address, and a source port as a judgment condition

Division of SIP trunk groups

This embodiment is similar to the foregoing Embodiment 1, except that: the sender selects the SIP trunk group used for sending the out-of-call SIP message according to the load sharing policy, and the sender corresponds to the SIP trunk group. The source IP address, the source port, and the destination IP address are used to generate the message. When the receiving SIP entity receives the SIP message outside the call, the source IP address, the source port, and the destination IP address are used as the judgment conditions to determine which message the message comes from. The SIP trunk group, and then distributes the message to the corresponding service module according to the load sharing policy, and the service module performs service processing according to the call attribute of the SIP trunk group.

It should be noted that, in the first SIP entity of the foregoing embodiment, the same n service ports, service modules, and local port bindings are described as an example for each IP address. Those skilled in the art can understand that the service ports corresponding to each IP address can be the same or different, and the number of service ports can be the same or different. Similarly, the service module may not be bound to the local port, and the number may be different from the number of the local port. In this case, when the received message is distributed according to the SIP trunk group to which it belongs, secondary distribution may be adopted, that is, It is first distributed by the service port to the local port, and then distributed to the service module by the local port.

A person skilled in the art may understand that all or part of the steps of implementing the foregoing SIP entity and/or the second SIP entity having a SIP relay group may be performed by a program to instruct related hardware. The program can be stored in a readable storage medium, such as a read only memory, a random access memory, a magnetic disk, an optical disk, or the like.

FIG. 3 is a schematic structural diagram of a system with a SIP trunk group according to the present invention. The system includes a first SIP entity 300 and a second SIP entity 400. The first SIP entity 300 includes service modules 311, 312, 313 to 31 s, and a sending module 350. The second SIP entity 400 includes service modules 411, 412. 413 to 41t, and a receiving module 350 and a group dividing module 460. Those skilled in the art can understand that the first Both the SIP entity 300 and the second SIP entity 400 may have more than one service module.

The first SIP entity 300 is used as a sender of the out-of-call SIP message in the system, and the service module selects a SIP trunk group used for sending the out-of-call SIP message, and adopts a correspondence relationship with the SIP trunk group. The source IP address, the destination IP address, and the feature field generate the out-of-call SIP message. The service module outputs the generated out-of-call SIP message to the sending module 450, which is sent by the sending module 450 to the second SIP entity 400.

Each service module may include a transmission load sub-module. After receiving the SIP message to be sent from the upper application, the transmission load sub-module may complete the selection of the SIP relay group according to the load sharing policy. The load sharing policy may be determined by the administrator of the first SIP entity 300 according to specific needs, for example, may be equally distributed by call or allocated to each SIP trunk group according to the call proportion of each service module.

The receiving module 450 of the second SIP entity 400 receives the out-of-call SIP message sent by the first SIP entity 300 and outputs it to the group dividing module 460. The group dividing module 460 determines the SIP trunk group to which the SIP trunk group belongs according to the source IP address, the destination IP address, and the feature field of the out-of-call SIP message, and sends the SIP trunk group to the service module, according to the service module. The SIP trunk group performs business processing on it.

The group dividing module 460 may include a receiving load sub-module. When determining a service module for processing the out-of-call SIP message, the receiving load sub-module selects a service module according to the load sharing policy, and sends the out-of-call SIP message to the selected one. On the business module. The specific load sharing strategy can be determined by the administrator of the second SIP entity 400 according to actual needs.

The above feature field may be a source port or a destination port of an out-of-call SIP message, or a combination of a source port and a destination port of a call-out SIP message.

Those skilled in the art can understand that when a SIP entity acts as both a sender and a receiver of a call-out SIP message, it can include more than one service module, a sending module, a group dividing module, and a receiving module.

Since the SIP entity in the embodiment of the present invention divides the SIP relay group by a combination of an IP address and a source port and/or a destination port, multiple SIP relays can be implemented between any two IP addresses of the two SIP entities. The group, thereby improving the effectiveness of SIP call management, and enhancing the telecom operation capability of the SIP call; in addition, the communication method of the system with the SIP relay group in the embodiment of the present invention is based on a predetermined load sharing strategy. The message distribution from the service port to the service module is performed, so that the load sharing is well realized while ensuring the reliability of the system. The above is only the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modifications, equivalents, improvements, etc., which are made within the spirit and principles of the present invention, should be included. It is within the scope of the invention.

Claims

OP070185 WO 2008/011821 PCT/CN2007/070271 -8-claims

1. A system with a session initiation protocol SIP trunk group, comprising:

a first SIP entity, configured to send an out-of-call SIP message on a selected SIP trunk group, where the SIP trunk group and the source IP address, the destination IP address, and the feature field of the out-of-call SIP message have Correspondence relationship

a second SIP entity, configured to receive the out-of-call SIP message, determine a SIP trunk group to which the SIP trunk group belongs according to the source IP address, the destination IP address, and the feature field, and perform service processing according to the SIP trunk group. .

2. The system of claim 1, wherein: the feature field is a source port, a destination port, or a combination of a source port and a destination port of an off-call SIP message.

3. A device with a SIP trunk group, comprising:

At least one service module, configured to perform service processing on the out-of-call SIP message, including selecting a SIP trunk group used for sending the out-of-call SIP message, and adopting a source IP address corresponding to the SIP trunk group, Generating the out-of-call SIP message by the destination IP address and the feature field;

And a sending module, configured to send the out-of-call SIP message.

4. The apparatus according to claim 3, wherein: the feature field is a source port, a destination port, or a combination of a source port and a destination port of a call out SIP message.

5. The apparatus according to claim 3, wherein: the service module comprises a transmission load sub-module, configured to select a SIP relay group according to a predetermined load sharing policy.

The apparatus according to any one of claims 3 to 5, wherein the apparatus further comprises:

a receiving module, configured to receive an out-of-call SIP message;

The group dividing module is configured to determine, according to the source IP address, the destination IP address, and the feature field of the SIP message, the SIP trunk group to which the SIP message belongs, and send the SIP message to a service module.

A device with a SIP trunk group, comprising at least one service module, wherein the device further comprises:

a receiving module, configured to receive an out-of-call SIP message; OP070185

WO 2008/011821 PCT/CN2007/070271

a group dividing module, configured to determine a SIP trunk group to which the SIP message belongs according to a source IP address, a destination IP address, and a feature field of the SIP message, and send the SIP trunk group to the SIP trunk group to which it belongs A business module.

8. The apparatus according to claim 7, wherein the feature field is a source port of a call-out SIP message, a destination port, or a combination of a source port and a destination port.

9. The apparatus according to claim 7, wherein the group dividing module comprises a receiving load sub-module for transmitting the out-of-call SIP message to a service module according to a load sharing policy.

10. A communication method with a SIP relay group, comprising:

Select the SIP trunk group used to send out-of-call SIP messages;

The method according to claim 10, wherein: the feature field is a source port, a destination port, or a combination of a source port and a destination port of the off-call SIP message.

12. The method according to claim 10 or 11, wherein said selecting to send a call outside

The relay group used by the SIP message is performed according to a load sharing policy; the load sharing policy includes an average allocation by call or a proportion of calls according to each service module.

13. A communication method with a SIP relay group, comprising:

Receiving an outbound SIP message;

The SIP trunk group to which the SIP message belongs is determined according to the source IP address, the destination IP address, and the feature field of the SIP message, and the service is processed according to the SIP trunk group to which the SIP message belongs.

The method according to claim 13, wherein the feature field is a source port of a call-out SIP message, a destination port, or a combination of a source port and a destination port.

The method according to claim 13 or 14, wherein the message distribution comprises: sending the SIP message to a service module for performing service processing according to a load sharing policy; and the load sharing policy comprises pressing a call Average allocation or allocation according to the proportion of calls of each business module.