CN101420729A - Method, system and apparatus for implementing redirection - Google Patents
Method, system and apparatus for implementing redirection Download PDFInfo
- Publication number
- CN101420729A CN101420729A CNA2007101812872A CN200710181287A CN101420729A CN 101420729 A CN101420729 A CN 101420729A CN A2007101812872 A CNA2007101812872 A CN A2007101812872A CN 200710181287 A CN200710181287 A CN 200710181287A CN 101420729 A CN101420729 A CN 101420729A
- Authority
- CN
- China
- Prior art keywords
- release request
- redirection
- parameter
- called
- switching device
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 43
- 230000011664 signaling Effects 0.000 claims abstract description 125
- 238000006243 chemical reaction Methods 0.000 claims description 30
- 238000013507 mapping Methods 0.000 claims description 5
- 230000000977 initiatory effect Effects 0.000 claims description 2
- 230000008569 process Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 5
- 230000002441 reversible effect Effects 0.000 description 4
- 230000004044 response Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
- 238000012559 user support system Methods 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/54—Arrangements for diverting calls for one subscriber to another predetermined subscriber
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention provides a method for realizing redirection, a system and a device thereof, wherein, the method comprises the following steps: receiving a first release request sent by a called exchange device which executes a redirection service, and then converting the first release request into a second release request supported by a calling exchange device according to a signaling type supported by the calling exchange device; sending the second release request to the calling exchange device to instruct the calling exchange device to call a third-party user, thus realizing the redirection service, and releasing network resources occupied between a switching exchange device and the called exchange device and between the switching exchange device and the calling exchange device during a call period after the called exchange device sends the redirection, and further saving the network resources occupied by the redirection service.
Description
Technical Field
The present invention relates to mobile communications technologies, and in particular, to a method, a system, and a device for implementing redirection.
Background
With the continuous development of the existing mobile communication technology, the coexistence of networks using different signaling is a common phenomenon, which requires the realization of the handover of a call between networks using different signaling. For example, an IP Multimedia Subsystem (IMS) network uses SIP (Session initiation Protocol) signaling, which supports other switching devices accessing the IMS network for multimedia services through various packet-switched access networks using non-SIP signaling.
There are already in the prior art services that enable handover between networks using different signalling, such as normal call traffic and redirection traffic. In the prior art, a system for realizing switching between networks using different signaling for redirection services may be as shown in fig. 1, where switching device a is a calling switching device, switching device B is a switching device, and switching device a and switching device B are communicated with each other by using SIP signaling; the switching device C is a called switching device, and uses Integrated Services Digital Network (ISDN) User part (ISUP, ISDN User part) signaling or Bearer Independent Control Channel (BICC) signaling for interworking with the switching device B. The specific redirection process is as follows: the method comprises the steps that switching equipment A initiates a call to switching equipment C, the switching equipment A sends a call request to switching equipment B through an Invite (Invite) message, and the switching equipment B converts the Invite message into an Initial Address (IAM) message and sends the IAM message to the switching equipment C; the called user corresponding to the switching equipment C triggers the redirection service due to the reasons of number change or forwarding and the like, and the redirection number is the number of the third party user, so the switching equipment C continues the call to the third party user.
In the redirection service switched between networks adopting different signaling in the prior art, after the called party corresponding to the called switching equipment triggers the redirection service, the called switching equipment continues the call from the calling switching equipment to the third party user, so that network resources occupied during the call establishment process between the switching equipment and the called switching equipment are occupied during the call process, which inevitably causes waste of network resources.
Disclosure of Invention
The embodiment of the invention provides a method, a system and equipment for realizing redirection, so as to save network resources occupied in a calling process on the basis of realizing redirection.
A method of implementing redirection, the method comprising:
after receiving a first release request sent by a called switching device for executing redirection service, converting the first release request into a second release request supported by a calling switching device according to a signaling type supported by the calling switching device;
and sending the second release request to the calling switching equipment to indicate the calling switching equipment to initiate a call to a third party user.
A system for implementing redirection, the system comprising: calling exchange equipment, switching exchange equipment and called exchange equipment;
the calling switching equipment is used for receiving a second release request sent by the switching equipment;
the switching equipment is used for converting a first release request into a second release request supported by the calling switching equipment according to the signaling type supported by the calling switching equipment after receiving the first release request sent by the called switching equipment for executing redirection service, and sending the second release request to the calling switching equipment to indicate the calling switching equipment to initiate a call to a third party user;
the called switching equipment is used for sending a first release request to the switching equipment after redirection is executed.
A handover switching device, the handover switching device comprising: a receiving unit, a converting unit and a transmitting unit;
the receiving unit is used for receiving a first release request sent by the called switching equipment for executing the redirection service;
the conversion unit is configured to convert the first release request received by the receiving unit into a second release request supported by the calling switching device according to the signaling type supported by the calling switching device;
and the sending unit is used for sending the second release request converted by the conversion unit to the calling switching equipment to indicate the calling switching equipment to initiate a call to a third party user.
It can be seen from the above technical solutions that, in the method, system, and device provided in the embodiments of the present invention, in a redirection service that is switched between networks using different signaling, after receiving a first release request sent by a called switching device to execute the redirection service, the first release request is converted into a second release request according to a signaling type supported by the calling switching device and sent to the calling switching device, so that the calling switching device can initiate a call to a third party user, thereby implementing the redirection service, the method enables, after the called switching device sends redirection, a network resource occupied during the call between the switching device and the called switching device to be released through the first release request, and the first release request to be converted into the second release request and sent to the calling switching device, a signaling connection established between the switching device and the calling switching device to be released through the second release request, therefore, the network resource occupied by the redirection service is saved, and the called exchange equipment can continue to execute other services without being influenced after triggering the redirection service.
Drawings
Fig. 1 is a system diagram of redirection service implementing switching between networks using different signaling in the prior art;
fig. 2 is a flowchart of a method for implementing redirection according to an embodiment of the present invention;
fig. 3 is a diagram of a system structure for implementing redirection according to an embodiment of the present invention;
fig. 4 is a structural diagram of a handover switching device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in detail with reference to the accompanying drawings and specific embodiments.
The method for realizing redirection provided by the embodiment of the invention comprises the following steps: after receiving a first release request sent by a called switching device for executing redirection service, converting the first release request into a second release request supported by a calling switching device according to a signaling type supported by the calling switching device; and sending the second release request to the calling switching equipment to indicate the calling switching equipment to initiate a call to the third party user.
The calling switching device may support SIP signaling, and the called switching device may support non-SIP signaling such as ISUP signaling, BICC signaling, or SIP-I signaling, at this time, the first release request may be an REL request in the non-SIP signaling or a message encapsulating the REL request, and the second release request may be a release request of the SIP signaling. Or, the calling switching device may support non-SIP signaling such as ISUP signaling, BICC signaling, or SIP-I signaling, and the called switching device may support SIP signaling, in which case, the first release request may be a release request of SIP signaling, and the second release request may be an REL request of non-SIP signaling or a message encapsulating a REL request.
In the following, the method provided by the embodiment of the present invention is described in detail, and fig. 2 is a flowchart of the method provided by the embodiment of the present invention. The exchange equipment A and the exchange equipment B adopt SIP signaling for interaction, the exchange equipment B and the exchange equipment C adopt ISUP signaling for interaction, and the exchange equipment B completes the switching of a call between two networks adopting different signaling. As shown in fig. 2, the method may include the steps of:
step 201: switch a sends a call request to switch B via an Invite message.
The Invite message carries information of the called subscriber corresponding to the called exchange device C.
Step 202: switch B converts the received Invite message to an IAM message.
Switching device B needs to convert the received SIP signaling into ISUP signaling employed by switching device C. The IAM message may also carry the address of the called user corresponding to the switching device C.
Step 203: the switching device C performs a call offset service.
In this step, the redirection service executed by the switching device C is a call offset (CD) service, for example, the switching device C may be a Mobile Switching Center (MSC) of the called user equipment, the MSC of the called user equipment learns that the called user equipment corresponding to the MSC triggers the call offset service, and obtains subscription information of the called user equipment from a Home Location Register (HLR) of the called user equipment, so as to obtain a redirection number set by the called user equipment, that is, a number of a third party user. In addition, the redirection service executed by the switching device C may also be a call forwarding service, including: for example, the switching device C may be an MSC of the called user equipment, the MSC may send the received call request to the called user equipment through a Set up message, the called user equipment is busy at this time, the busy forwarding is triggered, and the MSC of the called user equipment knows that the called user equipment has triggered the redirection service, and may obtain subscription information of the called user from an HLR of the called user, thereby obtaining a redirection number Set by the called user, that is, a number of a third party user. In this step, the process of the switching device C performing the redirection service is not described herein again because it is a prior art.
Step 204: switching device C returns a Release (REL) request carrying redirection information to switching device B.
Step 205: switch B returns a release complete (RLC) message to switch C.
Through the above steps 204 and 205, the call connection established between the switch C and the switch B is torn down, and the network resources between the switch C and the switch B are released.
Step 206: the switching equipment B converts the REL request carrying the redirection information into a 302 message carrying the redirection information in the SIP signaling, and sends the 302 message carrying the redirection information to the switching equipment A.
In this step, the switching device B converts the received REL request into a corresponding release request of the SIP signaling according to the redirection information carried in the REL request. In the converted SIP signaling release request, the redirection information is carried by a History-Info header field in the SIP signaling release request, or by a conversion (division) header field in the release request, or by other types of header fields.
The redirection type indicator (redirection indicator) parameter contained in the existing REL request carries the type of the executed redirection service, and whether the converted release request carries redirection information or not is determined according to the redirection indicator parameter in the REL request. Since REL redirection traffic contains two types: rerouting (Call routed) and transferring (Call division), when the type information carried in the redirection parameter indicates that the redirection is Call routed, the converted release request may not need to carry redirection information, and at this time, the contact header field of the converted message may carry information of the third party user. When the type information carried in the redirection indicator parameter indicates that the redirection is Call division, the converted release request can carry redirection information. Table 1 shows a correspondence between a redirection type indication parameter in an REL request and a converted release request of an SIP signaling according to an embodiment of the present invention. It should be noted that the correspondence shown in table 1 is reversible, and can be used not only for the conversion from the REL request of non-SIP signaling to the SIP signaling release request, but also for the conversion from the SIP signaling release request to the REL request of non-SIP signaling.
The release request in the SIP signaling formed after the conversion in this step may be a 300 message, a 301 message, a 302 message, a 305 message, or other 3XX messages. In this embodiment a 302 message is used.
TABLE 1
| Redirection type indication | Type of redirection traffic | SIP Release request |
| 0 | Non-redirection | 4XX, 5XX, 6XX failure response |
| 1 | Rerouting (local use) | 302 (not carrying redirection information) |
| 2 | Restricting rerouting of all rerouting information (local use) | 302 (not carrying redirection information) |
| 3 | Transfer of | 302 |
| 4 | Restricting transfer of all forwarded information | 302 |
| 5 | Restricting rerouting of redirect numbers (local use) | 302 (not carrying redirection information) |
| 6 | Restricting the forwarding of redirect numbers (local use) | 302 |
In addition, in the conversion process, for call division type redirection service, redirection information carried in the REL request needs to be mapped to a History-Info header field or a Dviersion header field of a release request of an SIP signaling. Of course, no matter what type of redirection service, the redirection information may be carried in the History-Info header or the Dviersion header.
The REL request may also include at least one of the following redirection parameters: original called number (Original called number), Original Redirection reason (Original Redirection replay), Original address presentation (Original address presentation), Redirection number (Redirection number), Redirection replay, Redirection address presentation (Redirection address), Redirection number (Redirection number), Redirection counter, etc. The redirecting number, the redirecting reason and the redirecting address providing language are parameters used when more than one redirection occurs.
The following describes an example in which the History-Info header carries redirection information. When performing redirection once, the mapping relationship shown in table 2 may be adopted, where table 2 is a corresponding relationship between a parameter in the REL request and a parameter of the History-Info header field when performing redirection once, and table 3 is a corresponding relationship between a parameter in the REL request and a parameter of the History-Info header field when performing redirection many times, which are provided by the embodiment of the present invention. Likewise, the correspondence shown in tables 2 and 3 is reversible, and can be used not only for the conversion from the REL request for non-SIP signaling to the SIP signaling release request, but also for the conversion from the SIP signaling release request to the REL request for non-SIP signaling.
When redirection is performed once, two History-Info header fields may be set in the SIP release request, where each History-Info header field includes a Universal Resource Identifier (URI), or only one History-Info header field including two URIs may be set. When two or more redirections are performed, three or more than three History-Info header fields may be set in the SIP release request, where each History-Info header field includes one URI, or only one History-Info header field including three or more than three URIs may be set. Each URI corresponds to an Index (Index), when redirection is carried out once, the name-address (name-addr) parameter of the URI with the Index value of 1 can be used for carrying the original called number information, and the reason (cause) parameter can be used for carrying the original redirection reason information; the name-addr parameter of a URI with an Index value of 1.1 may be used to carry the redirect number information. The Index of the last URI in the SIP message may be used to indicate the number of redirections. For example, if the Index of the last URI is 1.1, the call is redirected once; if the Index of the last URI is 1.1.1, then the call is redirected twice, and so on. Of course, the Index may also represent the number of times of redirection, for example, it represents that the call is redirected once when the Index is 1.1, and represents that the call is redirected twice when the Index is 1.1.2. It should be noted that, in general, the redirecting number is the destination device number of the call when the last redirection is performed, and the redirecting number is the destination device number of the call when the last redirection is performed.
In the embodiment shown in fig. 2, the name-addr parameter of the URI with Index value 1 may be used to carry the information of the called user corresponding to the switching device C, and the cause of the redirection of the called user corresponding to the switching device C may be carried by the cause parameter of the URI with Index value 1; carrying the address provision attribute of the switching equipment C by using a private (private) parameter of the URI with the Index value of 1; and the name-addr parameter of the URI with the Index value of 1.1 carries the information of the third-party user.
TABLE 2
| Parameters in REL requests | Parameters of History-Info header field |
| Original called number | Name-addr parameter of URI with Index of 1 |
| Reason for primary reorientation | Cause parameter for URI with Index of 1 |
| Original address providing expression | Privacy parameter for URI with Index of 1 |
| Redirect number | Name-addr parameter of URI with Index of 1.1 |
| Number of redirections | Index of last URI |
TABLE 3
| Parameters in REL requests | Parameters of History-Info header field |
| Original called number | Name-addr parameter of URI with Index of 1 |
| Reason for primary reorientation | Cause parameter for URI with Index of 1 |
| Original address providing representationLanguage (1) | Privacy parameter for URI with Index of 1 |
| Number of the other party | Name-addr parameter of penultimate URI |
| Reasons for hair transformation | Cause parameter of penultimate URI |
| Redirecting address presentation | Privacy parameter of penultimate URI |
| Redirect number | Name-addr parameter of last URI |
| Number of redirections | Index of last URI |
As shown in table 2 and table 3, the REL request usually adopts the parameter of the redirection reason to carry the redirection reason information, the redirection reason values correspond to the cause parameter items in the History-Info header field, and the specific corresponding relationship may be as shown in table 4, where table 4 is the corresponding relationship between the redirection reason value in the REL request and the cause parameter in the History-Info header field provided in the embodiment of the present invention. The correspondence shown in table 4 is also reversible, and can be used not only for the conversion from the REL request of non-SIP signaling to the SIP signaling release request, but also for the conversion from the SIP signaling release request to the REL request of non-SIP signaling.
TABLE 4
| Redirect reason value | Description of the causes | Cause status code |
| 0 | Is unknown | 404 |
| 1 | User busy | 486 |
| 2 | No answer | 408 |
| 3 | Unconditionally | 302 |
| 4 | Ringing offset | 480 |
| 5 | Instantaneous offset | 480 |
| 6 | User unreachable | 503 |
The following is an example of a syntax format for carrying redirection information through History-Info based on the History-Info syntax format defined by the existing protocol:
History-Info:<sip:UserA@ims.example.comPrivacy＝history&Reason＝SIP％3Bcause％3D302>；index＝1，
History-Info:<sip:45432@vm.example.com>；index＝1.1
the above example is that when redirection occurs once, a syntax format that two History-Info header fields carry redirection information is adopted, wherein the called user is user A, the reason for redirection occurrence is unconditional forwarding, and the address providing attribute is limited number display; the third party user number is 45432.
Step 205 and step 206 may be executed simultaneously or sequentially in any order.
Step 207: switching equipment a replies a response ACK to switching equipment B.
The release of the signalling connection established between switching device a and switching device B is accomplished by the above-mentioned steps 206 and 207.
Step 208: and the switching equipment A sends a call request to the third-party user according to the redirection information carried by the received 302 message.
Step 209: and after receiving the call request, the third-party user replies a response to the switching equipment A.
The above embodiment is described by taking redirection occurring in a network using ISUP signaling as an example, and when redirection occurs in a network using other non-SIP signaling, the redirection may also be implemented by using the flow shown in fig. 2.
In addition, redirection information may be carried in a version signaling in the SIP signaling, and a process of signaling conversion of the switching device B is described below by taking a case where an SIP-I message of the encapsulated REL request is converted into a release message of the SIP signaling. Of course, the method can still be employed with other messages encapsulating the REL request converted to a release message for SIP signaling.
Firstly, in the message type selection mode of the converted SIP signaling, since the REL request carrying redirection information is encapsulated in the redirection message in the SIP-I signaling, the redirection information carried in the REL request needs to be mapped to the redirection header field of the SIP signaling during the conversion, and certainly, the redirection information can also be mapped to the History-Info header field of the SIP signaling.
When redirection is performed once, a division header field can be set, in the division header field, the name-addr parameter can be used for carrying original called number information, the replay parameter can be used for carrying original redirection reason information, and the privacy parameter can be used for carrying an original address to provide a representation language. The number of the third party subscriber may be indicated by a prior art header field such as Contact. The following is an example of the syntax format of the version header field when this form is used:
Diversion:
<sip:13607556935@128.4.0.66:5060；user＝phone；tt1＝0>；counter＝1；reason＝unconditional；privacy＝full
Supported:100rel，timer
Contact:<sip:13122222223@128.4.0.6:5061；user＝phone；tt1＝0>
Content-Length:0
in this example, the called subscriber has a number of 13607556935, the reason for redirection is unconditional forwarding, and the third party subscriber has a number of 13122222223.
In addition, a mode of setting a plurality of redirection header fields can be adopted to carry all redirection information. Table 5 shows a correspondence between parameters in the SIP-I message and parameters in the version header field when performing redirection for one time according to the embodiment of the present invention. If redirection is carried out once, two division header fields can be set, in the first division header field, the name-addr parameter can be used for carrying original called number information, the replay parameter can be used for carrying original redirection reason information, and the privacy parameter can be used for carrying an original address to provide a representation language. In the second division header field, the name-addr parameter may be used to carry redirection number information, and the replay parameter may be used to carry redirection number information. The first and second division header fields may be arranged in an order, for example, the first division header field may be placed at the bottom of the text message, the second division header field may be placed at the top of the text message, and so on. The correspondence shown in table 5 is also reversible, and can be used not only for the conversion from the REL request of non-SIP signaling to the SIP signaling release request, but also for the conversion from the SIP signaling release request to the REL request of non-SIP signaling.
TABLE 5
| Parameters in REL requests | Parameters of the Diversion header field |
| Original called number | Name-addr parameter in first division header field |
| Reason for primary reorientation | The replay parameter in the first division header field |
| Original address providing expression | Privacy parameter in first version header field |
| Redirect number | Name-addr parameter in the second division header field |
| Number of redirections | Counter parameter in the conversion header field |
If more than two redirections are performed, more than three redirection header fields may be set to carry the redirection information. The principle of the method is the same as the mode of setting a plurality of History-Info header fields, but the History-Info header fields adopt indexes to identify the redirection information when redirection occurs each time, and the division header fields arrange the plurality of division header fields according to a certain sequence to identify the redirection information when redirection occurs each time.
Besides adopting the existing parameters in the History-Info header field or the division header field to carry redirection information, the method can also adopt the setting of extension parameters in the History-Info header field or the division header field to carry redirection information.
The above processes are all described by taking the example of converting the non-SIP signaling containing the Redirection information into the SIP signaling containing the Redirection information, if the calling switching device a and the called switching device B use the non-SIP signaling, and the called switching device C that is redirected uses the SIP signaling with the switching device B in the IMS network, the method used in the embodiment of the present invention can still be used, but the switching device B needs to map the Redirection information carried in the History-Info header field or the Redirection header field of the release request of the SIP signaling into the Redirection parameters of the non-SIP signaling message, for example, into each parameter of the Redirection information cell in the REL request, when performing switching. In the specific conversion, the correspondence shown in tables 1 to 5 in the embodiment of the present invention may be still used.
Fig. 3 is a block diagram of a system according to an embodiment of the present invention, and as shown in fig. 3, the system may include: calling switching device 300, handover switching device 310, and called switching device 320.
The calling switching device 300 is configured to receive the second release request sent by the handover switching device 310.
The handover switching device 310 is configured to, after receiving a first release request sent by the called switching device 320 for executing the redirection service, convert the first release request into a second release request supported by the calling switching device 300 according to the signaling type supported by the calling switching device, and send the second release request to the calling switching device 300 to indicate that the calling switching device 300 initiates a call to the third party user.
The called switching device 320 is configured to perform redirection and send a first release request to the handover switching device 310.
After receiving the second release request, the calling switching device 300 may release the signaling connection established between itself and the handover switching device 310. The handover switching device 310 may release the signaling connection established between itself and the called switching device 320 after receiving the first release request.
Wherein the calling switching device 300 and the called switching device 320 support different signaling.
The calling switching device 300 may be a device such as a calling user equipment, a calling MSC, etc. located in a network where the calling user equipment is located; the handover switching device 310 may be a Media Gateway Controller (MGCF), an inter-network unit (IWU), or the like; the called switching device 320 may be a called user equipment, a called MSC, or other device located in the network where the called user is located.
When the third party user and the calling switching device 300 are located in a network supporting the same signaling, the calling switching device 300 may directly send a call request to the third party user; when the third party user and the calling switching device 300 are located in networks supporting different signaling, for example, the calling switching device 300 supports SIP signaling, and the third party user supports non-SIP signaling, the calling switching device 300 may send a call request to the switching device 310, and the switching device 310 converts the call request into signaling supported by the network where the third party user is located and sends the signaling to the third party user.
In the following, the handover switching device 310 is described in detail, and fig. 4 is a structural diagram of the handover switching device 310 according to an embodiment of the present invention, as shown in fig. 4, the handover switching device may include: receiving section 401, converting section 402, and transmitting section 403.
A receiving unit 401, configured to receive a first release request sent by a called switching device to execute a redirection service.
A converting unit 402, configured to convert the first release request received by the receiving unit 401 into a second release request supported by the calling switching device according to the signaling type supported by the calling switching device.
A sending unit 403, configured to send, to the calling switching device, the second release request converted by the conversion unit 402 to instruct the calling switching device to initiate a call to the third party user.
After the receiving unit 401 receives the first release request, the handover switching device may release the signaling connection established between the handover switching device where the handover switching device is located and the called switching device.
The handover switching apparatus may further include: a correspondence storing unit 404, configured to store a correspondence between the redirection parameter of the first release request and the redirection parameter of the second release request.
The converting unit 402 may be further configured to obtain the correspondence from the correspondence storing unit 404, and execute the operation of converting the first release request containing the redirection information into the second release request containing the redirection information according to the correspondence stored in the correspondence storing unit 404.
Wherein the converting unit 402 may include: a first conversion unit 4021 or a second conversion unit 4022.
The first converting unit 4021 may be configured to map the redirection parameter of the REL request or the message encapsulating the REL request to a History-Info header field or a version header field of the SIP signaling release request according to the correspondence stored in the correspondence storing unit 404.
The second converting unit 4022 may be configured to map redirection information carried in a History-Info header field or a division header field of the SIP signaling release request to a redirection parameter of the REL request or a message encapsulating the REL request, according to the corresponding relationship stored in the corresponding relationship storing unit 404.
The conversion unit 402 may map the redirection parameters of the REL request or the message encapsulating the REL request and the redirection information carried in the History-Info header field or the redirection header field of the SIP signaling release request by using the corresponding relationship in table 1, table 2, table 3, table 4, or table 5 in the method embodiments. Wherein the release request of SIP signaling may be a 300 message, a 301 message, a 302 message, a 305 message, or other 3XX message.
As can be seen from the above description, in the method, system, and device provided in the embodiments of the present invention, in a redirection service for switching between networks using different signaling, a called switching device executes the redirection service to send a first release request to a handover switching device, the handover switching device, after receiving the first release request, may release a signaling connection established between itself and the called switching device, and convert the first release request into a second release request according to a signaling type supported by the calling switching device, and send the second release request to the calling switching device, so that the calling switching device may release the signaling connection established between itself and the handover switching device, and may initiate a call to a third party again, thereby implementing the redirection service, the method enables a network resource occupied between the handover switching device and the called switching device in a call process to be released, thereby saving the network resources occupied by the redirection service.
Moreover, the embodiment of the present invention specifically provides how to convert the first release request into the second release request, that is, mapping the redirection parameter in the non-SIP signaling to the History header field or the division header field in the SIP signaling, or mapping the redirection information in the History header field or the division header field in the SIP signaling to the redirection parameter in the non-SIP signaling, thereby implementing lossless transparent transmission of the redirection information, so that an operator of the calling switching equipment network can specify a specific policy according to the specific redirection information to control the execution of the redirection service, and provide conditions for various differentiated services of the operator.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (14)
1. A method for implementing redirection, the method comprising:
after receiving a first release request sent by a called switching device for executing redirection service, converting the first release request into a second release request supported by a calling switching device according to a signaling type supported by the calling switching device;
and sending the second release request to the calling switching equipment to indicate the calling switching equipment to initiate a call to a third party user.
2. The method of claim 1, wherein the first release request is a release request of non-Session Initiation Protocol (SIP) signaling or a message encapsulating a release request of non-SIP signaling, and the second release request is a release request of SIP signaling; or,
the first release request is a release request of SIP signaling, and the second release request is an REL request of non-SIP signaling or a message encapsulating the REL request.
3. The method of claim 1, wherein converting the first release request into a second release request supported by an originating switching device according to a signaling type supported by the originating switching device comprises: and converting the first release request carrying the redirection information into a second release request carrying the redirection information according to the signaling type supported by the calling switching equipment according to the corresponding relation between the redirection parameter of the first release request and the redirection parameter of the second release request.
4. The method of claim 1, wherein converting the first release request into a second release request supported by an originating switching device according to a signaling type supported by the originating switching device comprises: and converting the first release request into a second release request supported by the calling switching equipment according to the corresponding relation between the message type of the first release request and the message type of the second release request.
5. The method of claim 1, further comprising: and the calling switching equipment initiates a call to the third party again according to the redirection information carried in the received second release request.
6. The method as claimed in claim 2, wherein the SIP signaling release request carries redirection information in a History-Info header field or a translation-division header field.
7. The method of claim 3, wherein the release request of the non-SIP signaling or the message encapsulating the release request of the non-SIP signaling carries the redirection information at least by one of the following ways:
carrying the information of the called party corresponding to the called exchange equipment through the original called number parameter or the re-sent number parameter;
carrying the reason for the redirection of the called user corresponding to the called exchange equipment by the original redirection reason parameter or redirection reason parameter;
providing a representation language through an original address or providing a representation language parameter by redirecting an address to carry an address providing attribute of the called switching equipment;
carrying the information of the third party user through the redirecting number parameter or the redirecting number parameter;
and carrying redirection time information of the call through the redirection time parameter.
8. The method of claim 6, wherein the History-Info header carries redirection information at least one of:
carrying the information of the called user corresponding to the called exchange equipment by the name-address-addr parameter of a universal resource identifier URI in the History-Info header field;
the reason cause parameter of the URI in the History-Info header field carries the reason for the redirection of the called user corresponding to the called switching equipment;
the private privacy parameter of the URI in the History-Info header field carries the address providing attribute of the called switching equipment;
carrying the information of the third party user through the name-addr parameter of another URI in the History-Info header field;
and carrying the redirection time information of the call by the Index parameter of the last URI in the History-Info header field.
9. The method of claim 6, wherein the redirection header field carries redirection information by at least one of:
carrying the information of the called user corresponding to the called exchange equipment through the name-addr parameter of a division header field;
the reason for the redirection of the called user corresponding to the called switching equipment is carried by the replay parameter of the redirection header field;
carrying the address providing attribute of the called switching equipment by the privacy parameter of the version head domain;
carrying the information of the third party user through the name-addr parameter of the other division header domain;
and carrying redirection time information of the call by the Counter parameter in the conversion header domain.
10. The method of claim 2, wherein the request for release of SIP signaling comprises: 300 message, 301 message, 302 message, or 305 message.
11. A system for implementing redirection, the system comprising: calling exchange equipment, switching exchange equipment and called exchange equipment;
the calling switching equipment is used for receiving a second release request sent by the switching equipment;
the switching equipment is used for converting a first release request into a second release request supported by the calling switching equipment according to the signaling type supported by the calling switching equipment after receiving the first release request sent by the called switching equipment for executing redirection service, and sending the second release request to the calling switching equipment to indicate the calling switching equipment to initiate a call to a third party user;
the called switching equipment is used for sending a first release request to the switching equipment after redirection is executed.
12. A handover switching device, comprising: a receiving unit, a converting unit and a transmitting unit;
the receiving unit is used for receiving a first release request sent by the called switching equipment for executing the redirection service;
the conversion unit is configured to convert the first release request received by the receiving unit into a second release request supported by the calling switching device according to the signaling type supported by the calling switching device;
and the sending unit is used for sending the second release request converted by the conversion unit to the calling switching equipment to indicate the calling switching equipment to initiate a call to a third party user.
13. The handover switching device of claim 12, further comprising: a correspondence storage unit, configured to store a correspondence between a redirection parameter of the first release request and a redirection parameter of the second release request;
the conversion unit is further configured to obtain the corresponding relationship from the corresponding relationship storage unit, and convert the first release request including the redirection information into a second release request including the redirection information according to the signaling type supported by the calling switching device according to the corresponding relationship.
14. The handover switching apparatus according to claim 12, wherein the switching unit comprises: a first conversion unit or a second conversion unit;
the first conversion unit is used for mapping the SIP signaling release request or the redirection parameter of the message encapsulating the SIP signaling release request to a History-Info header field or a division header field of the SIP signaling release request according to the corresponding relation stored in the corresponding relation storage unit;
and the second conversion unit is used for mapping the redirection information carried in the History-Info header field or the conversion header field of the SIP signaling release request to the non-SIP signaling request or the redirection parameter of the message encapsulating the non-SIP signaling release request according to the corresponding relation stored in the corresponding relation storage unit.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2007101812872A CN101420729A (en) | 2007-10-26 | 2007-10-26 | Method, system and apparatus for implementing redirection |
| PCT/CN2008/072643 WO2009065322A1 (en) | 2007-10-26 | 2008-10-10 | A method, system and device for achieving the redirection |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2007101812872A CN101420729A (en) | 2007-10-26 | 2007-10-26 | Method, system and apparatus for implementing redirection |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101420729A true CN101420729A (en) | 2009-04-29 |
Family
ID=40631262
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2007101812872A Pending CN101420729A (en) | 2007-10-26 | 2007-10-26 | Method, system and apparatus for implementing redirection |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN101420729A (en) |
| WO (1) | WO2009065322A1 (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010145394A1 (en) * | 2009-09-24 | 2010-12-23 | 中兴通讯股份有限公司 | Method and system for implementing bearer control |
| WO2016000114A1 (en) * | 2014-06-30 | 2016-01-07 | 华为技术有限公司 | Method, system and related devices for making statistics on redirection performance indicators |
| CN110661787A (en) * | 2019-09-04 | 2020-01-07 | 苏宁云计算有限公司 | Method and device for capturing Http redirection state code and computer equipment |
| CN111131506A (en) * | 2019-12-31 | 2020-05-08 | 华为技术有限公司 | Message processing method and device |
| CN111629099A (en) * | 2020-05-06 | 2020-09-04 | Oppo（重庆）智能科技有限公司 | Mobile terminal, control method and control device thereof, and storage medium |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7035248B2 (en) * | 2000-08-10 | 2006-04-25 | Alcatel | Switch with emulation client |
| DE10323403A1 (en) * | 2003-05-23 | 2004-12-09 | Siemens Ag | Method for signaling call forwarding parameters in a SIP network |
| US7995559B2 (en) * | 2006-02-27 | 2011-08-09 | Cisco Technology, Inc. | System and method for interworking communication protocols to provide supplementary services |
| CN1988726B (en) * | 2006-12-20 | 2010-04-21 | 华为技术有限公司 | Method, device and system for intelligent triggering and charging in call redirection |
-
2007
- 2007-10-26 CN CNA2007101812872A patent/CN101420729A/en active Pending
-
2008
- 2008-10-10 WO PCT/CN2008/072643 patent/WO2009065322A1/en active Application Filing
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010145394A1 (en) * | 2009-09-24 | 2010-12-23 | 中兴通讯股份有限公司 | Method and system for implementing bearer control |
| WO2016000114A1 (en) * | 2014-06-30 | 2016-01-07 | 华为技术有限公司 | Method, system and related devices for making statistics on redirection performance indicators |
| CN105393579A (en) * | 2014-06-30 | 2016-03-09 | 华为技术有限公司 | Method, system and related devices for making statistics on redirection performance indicators |
| CN110661787A (en) * | 2019-09-04 | 2020-01-07 | 苏宁云计算有限公司 | Method and device for capturing Http redirection state code and computer equipment |
| CN111131506A (en) * | 2019-12-31 | 2020-05-08 | 华为技术有限公司 | Message processing method and device |
| CN111131506B (en) * | 2019-12-31 | 2021-10-01 | 华为技术有限公司 | Message processing method and device |
| CN111629099A (en) * | 2020-05-06 | 2020-09-04 | Oppo（重庆）智能科技有限公司 | Mobile terminal, control method and control device thereof, and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2009065322A1 (en) | 2009-05-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP4856241B2 (en) | Number portability for IMS networks | |
| EP2728843B1 (en) | Telephone call processing | |
| US10469541B2 (en) | Session initiation protocol (SIP) router | |
| KR101352796B1 (en) | An Method And System For Ending-Call Anchoring of the CS Domain | |
| US9148288B2 (en) | Conditional telecommunications | |
| CN101132378B (en) | A method and communication system for intercommunication between different networks | |
| JP2005006328A (en) | Redirect of new media path between packet switched portion and circuit switched portion of mobile communication switching center using server component | |
| EP2197237B1 (en) | Late call forwarding method in ip multimedia core network subsystem centralized service | |
| CN101420729A (en) | Method, system and apparatus for implementing redirection | |
| DK2443850T3 (en) | Methods and arrangement in a telecommunications network | |
| US8374330B2 (en) | Call control | |
| CN100471182C (en) | Method and system of providing service of subsystem in IP multimedia for users in circuit switching domain | |
| CN101815270B (en) | Processing method and device for calling | |
| EP2173085B1 (en) | A method for realizing user decision user busy forwarding | |
| US20080254771A1 (en) | Apparatus and method for performing call setup for domain transfer in mobile communication system | |
| EP2040508A1 (en) | Method, apparatuses and program product for controlling IMS services when user is roaming in CS domain | |
| KR20090119983A (en) | Communication system, communication device and bypass control method when congestion occurs | |
| CN102833715B (en) | Inquisition switching implementation method, application server, business terminal and system | |
| JP5679577B2 (en) | Relay system and relay network codec selection method | |
| KR101617776B1 (en) | Mobile Communication System and Method for processing supplementary service | |
| CN101686441B (en) | Call hold service (CHS) calling method, equipment and system | |
| KR100917927B1 (en) | Incoming call switching method for outgoing call of IP network and mobile communication system performing the same | |
| KR20190120951A (en) | System and Method for processing a Incoming Call | |
| CN101247323B (en) | Method and system for transmitting history identification information | |
| KR101698134B1 (en) | Communication system and call processing method for treating a call of number portability |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Open date: 20090429 |