WO2008104113A1 - Procédé de resélection de route de défaillance du nœud de médiation d'appel et échangeur et système de celui-ci - Google Patents
Procédé de resélection de route de défaillance du nœud de médiation d'appel et échangeur et système de celui-ci Download PDFInfo
- Publication number
- WO2008104113A1 WO2008104113A1 PCT/CN2007/070884 CN2007070884W WO2008104113A1 WO 2008104113 A1 WO2008104113 A1 WO 2008104113A1 CN 2007070884 W CN2007070884 W CN 2007070884W WO 2008104113 A1 WO2008104113 A1 WO 2008104113A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- bicc
- route
- cmn
- office
- bearer
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/06—Arrangements for interconnection between switching centres using auxiliary connections for control or supervision, e.g. where the auxiliary connection is a signalling system number 7 link
- H04M7/063—Arrangements for interconnection between switching centres using auxiliary connections for control or supervision, e.g. where the auxiliary connection is a signalling system number 7 link where the telephone network is a network other than PSTN/ISDN
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/64—Distributing or queueing
- H04Q3/66—Traffic distributors
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13141—Hunting for free outlet, circuit or channel
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13145—Rerouting upon failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13176—Common channel signaling, CCS7
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13196—Connection circuit/link/trunk/junction, bridge, router, gateway
Definitions
- the present invention relates to the field of bearer independent call control protocol (BICC) technology, and more particularly, to a BICC call arbitration node (CMN) failed route reselection method, switch and system.
- BICC bearer independent call control protocol
- CMS BICC call arbitration node
- the Bearer Independent Call Control Protocol is a bearer-independent call control protocol developed by the ITU-TSG11 team.
- the main purpose of the BICC protocol is to solve the problem of separation of call control and bearer control, so that call control signaling can be given in such as Message Transfer Part (MTP), SS7 network, Asynchronous Transfer Mode (ATM) network. 7 on various networks such as the Internet Protocol (IP) network.
- MTP Message Transfer Part
- SS7 SS7 network
- ATM Asynchronous Transfer Mode
- IP Internet Protocol
- the BICC protocol evolved from the ISDN User Part (ISUP) and is an important supporting tool for the evolution of traditional telecommunication networks to integrated multi-service networks.
- the BICC protocol divides nodes supporting BICC signaling into a Service Node (SN) and a Call Media Node (CMN).
- the SN has a Bearing Control Function (BCF), and the CMN does not have a load control function.
- BCF Bearing Control Function
- the call function and the load control function can be physically separated or not separated. If separated, the call function and bearer control function entity need to use Call Bearing Control (CBC) signaling to send the message.
- CBC Call Bearing Control
- ATM has good Quality of Service (QoS) guarantee and call processing capability, and BICC can better support ATM network bearer. This is one of the reasons why the industry is optimistic about BICC.
- the bearer is controlled by the local switch, and the BICC signaling is used between the interoffices. If the outgoing route fails, the outgoing route is reselected.
- the failure routing reselection mechanism in the prior art may result in the outbound control bearer, and the incoming bear does not control the bearer, which is related to the BICC itself.
- the described call setup model conflicts and the call cannot be established.
- the embodiment of the present invention provides a method for re-routing a BICC CMN. After the local exchange fails as the outgoing route of the CMN, the switch can re-select the outgoing route, so as to establish a call smoothly.
- the embodiment of the present invention further provides a failing route reselection system of the BICC CMN, which can re-select an outgoing route after the local switch fails as the outgoing route of the CMN, thereby establishing a call smoothly.
- the embodiment of the present invention further provides a switch that acts as a BICC CMN in the current call. After the local switch fails to make an outgoing route as a CMN, the switch can re-select the outgoing route, so as to establish a call smoothly.
- a self-contained call control protocol (BICC) call arbitration node (CMN) failure route reselection method which pre-configures an outbound route failure cause value, a designated route, and the outgoing route failure cause value in an exchange that is a BICC CMN.
- BICC call control protocol
- CPN call arbitration node
- a failed route reselection system comprising: a back-office point, configured to provide a disconnection message including an outbound route failure cause value to an MSC server that is a BICC CMN when the outgoing route fails to be selected;
- the MSC server as a BICC CMN, is configured to obtain an outbound route failure reason value from the disconnection message, and control the media gateway to make a call out according to a preset correspondence between the outgoing route failure cause value and the designated route. Connect to the specified route;
- the media gateway is configured to accept control of the MSC server and connect the call outgoing path to the designated route.
- a switch comprising:
- a call processing unit configured to receive and forward the bearer related information in the call, and obtain a route routing failure cause value
- a bearer establishing unit configured to perform bearer information interaction with the media gateway
- the routing unit is configured to connect the call outgoing path to the designated route according to a preset correspondence between the outgoing route failure cause value and the designated route.
- a BICC CMN failure route reselection method in which an outbound route failure cause value, a designated route, and the outgoing call are configured in advance as an exchange of the BICC CMN.
- the correspondence between the route failure cause value and the specified route the method further includes: when the outgoing route fails, the BICC CMN obtains the outbound route failure reason value, and according to the correspondence between the outgoing route failure cause value and the designated route, The call outgoing connection is connected to the specified route. It can be seen that after applying the present invention, the local office acts as a BICC CMN.
- the back-office re-opening message carries a special disconnection cause value or the local office chooses to go out of the CIC.
- the local office supports the failure to process the data configuration.
- the outgoing route rate is improved by reselecting the outgoing route for the specified failure cause value.
- FIG. 1 is a schematic flowchart diagram of a BICC CMN failure route reselection method according to an embodiment of the present invention
- FIG. 2 is an exemplary structural diagram of a BICC CMN failed route reselection system according to an embodiment of the present invention
- FIG. 3 is a schematic diagram of a BICC CMN failure route reselection according to a first embodiment of the present invention
- FIG. 4 is a schematic diagram of a BICC CMN failure route reselection method according to a first embodiment of the present invention
- FIG. 5 is a schematic diagram of a BICC CMN failure route reselection according to a second embodiment of the present invention
- FIG. 6 is a schematic diagram of a BICC CMN failure route reselection method according to a second embodiment of the present invention
- FIG. 7 is a schematic diagram of a BICC CMN failure route reselection according to a third embodiment of the present invention
- FIG. 8 is a flow chart of a BICC CMN failure route reselection method according to a third embodiment of the present invention
- FIG. 9 is a schematic diagram of a BICC CMN failure route reselection according to a fourth embodiment of the present invention
- FIG. 10 is a flow chart of a BICC CMN failure route reselection method according to a fourth embodiment of the present invention
- FIG. 11 is a schematic diagram of a BICC CMN failure route reselection according to a fifth embodiment of the present invention
- FIG. 12 is a flow chart of a BICC CMN failure route reselection method according to a fifth embodiment of the present invention
- FIG. 13 is a schematic diagram of a BICC CMN failure route reselection according to a sixth embodiment of the present invention
- FIG. 14 is a flow chart of a BICC CMN failure route reselection method according to a sixth embodiment of the present invention
- FIG. 15 is a schematic structural diagram of a switch according to an embodiment of the present invention. Mode for carrying out the invention
- FIG. 1 is a schematic flowchart diagram of a BICC CMN failure route reselection method according to an embodiment of the present invention.
- the exchange referred to as the local office
- the method includes:
- Step 101 Pre-configure the correspondence between the cause of the outbound route failure, the specified route, and the failure route value of the outgoing route and the designated route on the exchange that is the BICC CMN.
- Step 102 When the outgoing route fails, the exchange that is the BICC CMN obtains the outbound route failure cause value, and connects the call outgoing path to the designated route according to the corresponding relationship between the outgoing route failure cause value and the designated route.
- the reason for the outbound route failure reason is provided by the local office itself when the outgoing route of the BICC CMN fails.
- the disconnection message including the reason for the failure of the outgoing route is sent to the local office by the backward office. Then, the local office obtains the reason for the failure of the outgoing route from the disconnection message.
- the local office may act as a BICC CMN or not as a BICC CMN, and may trigger a BICC CMN failed route reselection before the call bearer is established, or may be The BICC CMN failed routing reselection is triggered after the call bearer is established.
- the method may further include: the local office interacts with the forward office to carry the information to support the TrFO process of the local office and the forward office.
- the local office is no longer a BICC CMN, and the outgoing route fails before the BICC interoffice is established, and the designated route is BICC-BICC interworking.
- the method needs to further include: the local office and the forward office and the backward direction The site performs the interaction of the information, respectively, to support the TrFO process of the Office and the forward and backward offices.
- the method should further include: The local office forwards the original inter-office bearer information in the outgoing message.
- the The method should further include: the local office uses the bearer redirection process to notify the forward inter-office to re-establish the bearer, and the local office interacts with the forward office to carry the bearer information to support the TrFO process of the local office and the forward office.
- the local office uses the bearer redirection process to notify the forward inter-office to re-establish the bearer, and the local office interacts with the forward office and the backward office to carry out the information exchange to support the local office and the forward office.
- Backward TrFO process
- the local office acts as a BICC CMN;
- the method further includes: the local office uses the bearer redirection process to notify the forward inter-office to re-establish the bearer, and the local office forwards the original inter-office bearer information in the outgoing message.
- FIG. 2 is an exemplary structural diagram of a BICC CMN failed route reselection system in accordance with an embodiment of the present invention.
- the system includes:
- the backward office point 201 is configured to provide a disconnection line including the cause value of the outbound route failure to the MSC SERVER 202 (called the MSS) as the BICC CMN when the outgoing route fails to be selected.
- MSS MSC SERVER 202
- the MSC SERVER 202 of the BICC CMN is configured to obtain an outbound route failure cause value from the disconnection message, and control the media gateway 203 according to a preset correspondence between the outgoing route failure cause value and the designated route.
- the call outgoing connection is connected to the designated route;
- the media gateway 203 is configured to accept the control of the MSC SERVER 202 as a BICC CMN, and connect the call outgoing path to the designated route.
- the back office point 201 may be a Redirecting-from node node, and the MSC SERVER 202 as a BICC CMN may be a CC-Anchor node.
- the system may further include a BC-Anchor node as a forward site.
- the backward office 201 and the MSC SERVER 202 as the BICC CMN can be integrated into one node, and the backward office 201 and the designated routing switch can also be integrated into one node.
- the BICC CMN node can perform the re-selection of the outgoing route for the specified failure cause value through the failure processing data configuration, thereby improving Call completion rate.
- the Office can still be a CMN or it may not be a CMN.
- the local office can trigger a failed route reselection before the original call bearer is established, or trigger a failed route reselection after the original call bearer is established.
- the local office is a BICC CMN
- the failed route re-selection is triggered before the original call bearer is established.
- the local office pre-configures the data for failing to re-route according to the specified cause value.
- the local office receives the disconnection message of the subsequent office and carries the specified cause value.
- the local office performs the failed route reselection process of the BICC CMN.
- 3 is a schematic diagram of a BICC CMN failure route reselection according to a first embodiment of the present invention.
- 4 is a schematic flow chart of a BICC CMN failure route reselection method according to a first embodiment of the present invention.
- the local office triggers a failed route reselection before the original call bearer is established.
- the local station is not a BICC CMN, and the failed route reselection is BICC-TDM interworking.
- the local office configures the failure processing data as the BICC CMN node.
- the local office chooses the outgoing route to fail, or the back office returns the disconnection message carrying the special disconnection cause value before the forward direction and the backward direction bearer are established.
- the local office performs failure processing and reselects the outgoing route based on the failed processing data.
- the local office is not a BICC CMN, so the BICC bearer establishment procedure needs to be performed.
- the Office needs to interact with the forward office for bearer information, which uses the BICC bearer establishment process to support the TrFO process of this office and the forward office.
- the process includes the MSC server receiving the Initial Address and forwarding the Initial Address information, and the subsequent process is similar to the conventional BICC inter-office call flow in the prior art.
- FIG. 5 is a schematic diagram of a BICC CMN failure route reselection according to a second embodiment of the present invention.
- 6 is a schematic flow chart of a BICC CMN failure route reselection method according to a second embodiment of the present invention.
- the local office triggers a failed route reselection before the original call setup is established, and the local router is not a BICC CMN after the failed route reselection, and the BICC-BICC is interworked after the failed route reselection.
- the local office configures the failure processing data as the BICC CMN node.
- the local office chooses the outgoing route to fail, or the back office returns the disconnection message carrying the special disconnection cause value before the forward direction and the backward direction bearer are established.
- the local office performs failure processing and reselects the outgoing route based on the failed processing data.
- the local non-BICC CMN After re-selecting the outgoing route, the local non-BICC CMN, This requires a BICC bearer setup process. If BICC-BICC is interoperable after re-routing, the Office needs to interact with the forward-office and subsequent offices to carry information.
- the BICC bearer establishment process is used to support the TrFO process of the Office and the forward-office and subsequent offices.
- the ISUP is used as an example to describe the bearer information interaction process between the local office and the forward office and the subsequent office.
- the MSC server selects the outgoing route and forwards the IAM message.
- the MSC server processes the data according to the received failure reason and the pre-configured failure.
- the MSC server performs the bearer information exchange with the forward office and the bearer information interaction with the media gateway (MGW), and carries the bearer information interaction with the subsequent office.
- MGW media gateway
- FIG. 7 is a schematic diagram of a BICC CMN failure route reselection according to a third embodiment of the present invention.
- FIG. 8 is a schematic flow chart of a BICC CMN failure route reselection method according to a third embodiment of the present invention.
- the local office acts as a BICC CMN, triggering a failed route reselection before the original call setup is established, and the local office is still a BICC CMN after re-routing.
- the local office configured the failure processing data as the BICC CMN node.
- the local office chooses the outgoing route to fail, or the back office returns the disconnection message carrying the special disconnection cause value before the forward direction and the backward direction bearer are established. Failure processing, re-selecting the outgoing route based on the failed processing data, and the local office is still the BICC CMN after re-routing.
- the local office as the BICC CMN is configured with data for failing rerouting based on the specified cause value.
- the local office fails to select the outgoing route.
- the local office receives the disconnection message of the subsequent office and the disconnected message carries the specified cause value.
- the local office performs the failed route reselection process of the BICC CMN.
- the local office After re-selecting the outgoing route, the local office is the BICC CMN, and the outgoing route is the BICC relay.
- the local office needs to forward the original bearer letter in the outgoing IAM (Initial Address) message.
- the subsequent call flow is the same as the normal BICC CMN call flow.
- An embodiment of triggering a BICC CMN failed route reselection after the original call is established.
- the following embodiment describes the mechanism by which the local office, as a BICC CMN, triggers a failed route reselection after the original call bearer is established.
- the local office is configured as a BICC CMN node, and the failure processing data is pre-configured. If the forward direction and the backward direction call are established after the call bearer is established, and the back-office disconnection message carries a special disconnection cause value, the local office fails the processing. Re-select the outgoing route.
- the current call is used as a BICC CMN node, and the failure processing data is pre-configured. If the forward office and the backward office bearer are established, and the backward office line disconnection message carries a special disconnection reason value, the local office is Re-select the outgoing route when the failure is processed.
- the local office can still be a BICC CMN, or non-BICC. If the forward-office and post-office are established, the BICC CMN fails routing re-election is triggered, and the BICC bearer redirection function is required (ITU-T). Q.1902.6), the forward office needs to support the BC-Anchor node as a redirect.
- BICC bearer redirection can implement the following functions: After the bearer connection is established during the call, if the service layer needs to reconnect the originating call from the original called to another destination (such as call no answer forwarding), the bearer weight is used. With the orientation function, the established bearer connection can be removed and a direct bearer between the caller and the new destination can be re-established.
- Call Control Anchor Node is a service node (SN) or CMN node that triggers the BICC bearer redirection function. This node acts as an anchor node for call control during the BICC bearer redirection process. All call control related signaling is processed through this node.
- the BC-Anchor node (Bear Control Anchor node), the jth node acts as the anchor node for bearer control in the BICC bearer redirection process, and the new and old bearers are terminated at this node.
- the Redirecting-from node is used as the initial termination node of the call in the BICC load-direction process. After the bearer redirection ends, the BC-Anchor node deletes the bearer connection with this node.
- Redirecting-to node which is the terminating node of the call after the BICC-loaded redirection process ends, and the BC-Anchor node establishes a bearer connection with this node.
- FIG. 9 is a schematic diagram of a BICC CMN failure route reselection according to a fourth embodiment of the present invention.
- FIG. 10 is a flow chart showing a BICC CMN failure route reselection method according to a fourth embodiment of the present invention.
- the local office as a BICC CMN, triggers a failed route reselection after the original call setup is established, and the local non-BICC CMN is re-routed, and the BICC-TDM is interworked after the reselection of the route.
- the local office will receive the disconnection message of the subsequent office.
- the disconnected message carries the specified cause value, and the local pre-configuration There is data for failure rerouting based on the specified cause value.
- the local office sends a release complete message RLC (Release Complete Message), and at the same time, the BICC CMN fails the route reselection process.
- RLC Release Complete Message
- the local office is not a BICC CMN.
- the local office needs to actively notify the forward office to perform the bearer redirection process.
- the bearer redirection process is described below through specific messages. Those skilled in the art will appreciate that the following specific messages are merely exemplary and are not intended to limit the invention. Range of protection. In essence, the bearer redirection process used by BICC CMN failed route reselection is not limited to the following messages.
- the local office sends a Redirect Forwards Request message to actively notify the preceding office to perform the redirect process.
- the forwarder sends a Bearer Redirection Connect Forwards message to notify the local office that the bearer redirection process can be carried.
- the message carries the new call bearer related information.
- the local office acts as the CC-Anchor node in the BICC 7-loaded redirection and the Redirecting-from node and the Redirecting-to node, and the forward office acts as the BC-Anchor node.
- the local office needs to interact with the forward office for bearer information (specifically, the process can be established using BICC 7).
- the forward office informs the local office through the message Redirect Bearer Connected that the local office is established.
- the local office sends a Redirect Bearer Release Request message to notify the forward office.
- the related bearer is called, and then the forward office sends a Redirect Bearer Release Proceed message to notify the local office to release the bearer related to the call before the route reselection.
- the local office Since the local office does not control the bearer as the BICC CMN, the local office directly sends a Redirect Bearer Release Complete message to notify the release of the forward load. After the forward bearer is released, the bearer redirection process ends.
- the IAM (ISUP) message is sent out by the local office.
- the subsequent process is the same as the normal BICC-TDM interworking process.
- the MSC server is previously interoperable for BICC-BICC. After the above detailed description, it is BICC-TDM interworking after the failed route reselection.
- FIG. 11 is a schematic diagram of a BICC CMN failure route reselection according to a fifth embodiment of the present invention.
- FIG. 12 is a flow chart showing a BICC CMN failure route reselection method according to a fifth embodiment of the present invention.
- the local office as a BICC CMN, triggers a failed route reselection after the original call bearer is established, and after the rerouting, the local non-BICC CMN is re-selected after the rerouting. Interoperate for BICC-BICC.
- the local office receives the disconnection message of the subsequent office, and the disconnection message carries the specified cause value, and the local pre-configured Data for failed rerouting based on the specified cause value.
- the local office sends an RLC message and simultaneously performs the failing route reselection process of the BICC CMN.
- the local office is not a BICC CMN.
- the local office needs to actively notify the forward office to perform the bearer redirection process.
- the local office sends a Redirect Forwards Request message to notify the preceding office to perform the redirect process.
- the forwarder sends a Bearer Redirection Connect Forwards message to notify the local office that the bearer redirection process can be performed.
- the message carries the new call bearer related information.
- the local office acts as the CC-Anchor node and the Redirecting-from node in the BICC 7 redirection, the forward office acts as the BC-Anchor node, and the subsequent office acts as the Redirecting-to node.
- the local office needs to perform bearer information interaction with the forward office and the subsequent office (specifically, the BICC bearer establishment process can be used), and the forward office informs the local office that the bearer establishment is completed through the message Redirect Bearer Connected, and the local office sends a Redirect Bearer Release Request message to notify the forward direction.
- the office starts to release the relevant bearer before the route reselection, and then forwards the Redirect Bearer Release Proceed message to the local office to notify the local office to release the relevant bearer before the route reselection.
- this office Since this office is a BICC CMN and does not control bearers, the local office directly sends a Redirect Bearer Release Complete message to notify the release of the forward load. After the forward bearer is released, the bearer redirection process ends. The subsequent process is compared with the normal BICC-TDM.
- the interworking process is the same. As can be seen from Figure 11, the MSC server is previously interoperable for BICC-BICC. After the above detailed description, it is still BICC-TDM interworking after the failed route reselection.
- FIG. 13 is a schematic diagram of a BICC CMN failure route reselection according to a sixth embodiment of the present invention
- FIG. 14 is a flow chart showing a BICC CMN failure route reselection method according to a sixth embodiment of the present invention.
- the local office as a BICC CMN, triggers a failed route reselection after the original call setup is established, and the local office is still a BICC CMN after re-routing.
- the local office receives the disconnection message of the subsequent office.
- the disconnection message carries the specified cause value, and the local pre-configuration has a basis. Specify the reason value to fail the data for rerouting.
- the local office sends an RLC message and simultaneously performs the BICC CMN failure route reselection process.
- the local office acts as the BICC CMN.
- the local office sends a Redirect Forwards Request message to actively notify the forward office to carry out the redirect process.
- the forwarder sends a Bearer Redirection Connect Forwards message to inform the local office that the bearer redirection process can be carried.
- the message carries the new call bearer related information.
- the local office acts as the CC-Anchor node and the Redirecting-from node in the BICC 7 redirection
- the forward office acts as the BC-Anchor node
- the subsequent office acts as the Redirecting-to node.
- the forward direction and the subsequent office carry out the information exchange (specifically, the BICC bearer establishment process can be used).
- the forward office informs the local office that the bearer setup is completed through the message Redirect Bearer Connected.
- the local office sends a Redirect Bearer Release Request message to notify the forward office to start releasing the route. Select the bearer associated with the previous call, and then forward the Redirect Bearer Release Proceed message to the local office to notify the local office to release the relevant bearer before the route reselection.
- this office is a BICC CMN
- the bearer is not controlled. Therefore, the local office directly sends a Redirect Bearer Release Complete message to notify the release of the forward load. After the forward bearer is released, the bearer redirection process ends. The subsequent process is compared with the normal BICC CMN. The call flow is the same.
- the MSC server was previously a BICC CMN. After the above detailed description, it is still a BICC CMN after the failed route reselection.
- the post-return disconnection message carries a special disconnection cause value.
- the local office supports the failure to process the data configuration to achieve the specified failure reason.
- the value reselects the outgoing route.
- the local office may still be a BICC CMN, and the original inter-office bearer information needs to be forwarded.
- the Bureau needs to re-establish the bearer to support the TrFO process of this Office and the Forward Office and subsequent offices. If BICC-TDM is interoperable, the Office needs to re-establish the bearer to support the TrFO process of this office and the forward office.
- this office can also be used as a BICC CMN.
- the post-office return disconnection message carries a special disconnection cause value.
- the local office supports the re-selection of the specified failure cause value through the configuration of the failed processing data. Outgoing route.
- the BICC CMN initiates the BICC bearer redirection process, triggering the forward office to re-establish the bearer.
- the local call may still be a BICC CMN.
- the local office needs to forward the forward-office to the bearer redirection process.
- Information about the application's bearer In the case of BICC-BICC interoperability, the Office needs to re-establish the bearer to support the TrFO process of this Office and the forward office and subsequent offices. In the case of BICC-TDM interoperability, the Office needs to re-establish the bearer to support the TrFO process of this Office and the Forward Office.
- FIG. 15 is a block diagram showing an exemplary structure of a switch in accordance with the present invention.
- the switch acts as a BICC CMN in this call, as shown in Figure 15, the switch includes:
- the call processing unit 1501 is configured to receive and forward the related information in the call, and obtain an outbound route failure cause value before the current call bearer is established;
- the bearer establishing unit 1502 is configured to perform bearer information interaction with the gateway and the forward office respectively.
- the routing unit 1503 is configured to connect the call outgoing path to the designated route according to a preset correspondence between the outgoing route failure cause value and the designated route.
- the routing unit 1503 may connect the call outgoing path to the narrowband trunk circuit according to a preset correspondence between the outgoing route failure cause value and the designated route, or connect the call outgoing path to the BICC trunk circuit.
- the bearer establishing unit 1502 needs to perform bearer information interaction with the forward site (for example, by using the Continuity Signal (COT)).
- the establishing unit 1502 should also interact with the media gateway to establish a bearer (such as an IAM message via ISUP).
- a bearer such as an IAM message via ISUP.
- the load establishing unit 1502 needs to perform bearer information interaction with the forward office.
- the bearer establishing unit 1502 should also Interact with the media gateway to establish a bearer (such as an IAM message through ISUP). After the failed route reselection, this office is interoperable for BICC-ISUP, and this office is not a BICC CMN.
- the outgoing call is re-routed to the BICC trunk circuit, and the outgoing call is configured as a BICC CMN, then after the failed route reselection, the local office as the BICC CMN needs to forward the original inter-office bearer related information.
- the call processing unit 1501 can be from the back to the office before the current call 7 is established.
- the disconnection message is received, and the reason for the outbound route failure is obtained from the disconnection message.
- the call processing unit 1501 may also obtain an outgoing route failure cause value from the local office before the current call 7 is established.
- the call processing unit 1501 obtains the outgoing route failure cause value before the current call bearer is established. Actually, the call processing unit 1501 can also obtain the outgoing route failure cause value after the current call is established.
- the routing unit 1503 may connect the call outgoing path to the narrowband trunk circuit according to a preset correspondence between the outgoing route failure cause value and the designated route, or connect the call outgoing path to the BICC trunk circuit.
- the bearer establishing unit 1502 needs to perform bearer redirection with the forward site, and the bearer establishing unit 1502 should also interact with the media gateway to establish 7 Load (such as IAM messages via ISUP).
- the local office communicates with the BICC-ISUP.
- the local office is not the BICC.
- the interaction between the local office and the forward office and the media gateway includes: First, send a Redirect Forwards Request request to the office to notify the forward office.
- the forward office Carrying a redirect to release the original call for 7 years; the forward office returns a Bearer Redirection Connect Forwards message, informing the local office that the bearer redirection can be performed, and returning the new call bearer related information in the message;
- the notified new call bearer related information carries the bearer interaction with the gateway, and uses the BICC signaling to interact with the forward office to carry the bearer information.
- the forward office sends the Redirect Bearer Connected message to notify the local office to complete the establishment.
- the local office also passes the Redirect Bearer.
- the Release Request message informs the forward office to start the release of the route reselection before the call is related to 7 years; the forward office point passes the Redirect Bearer Release Proceed The message informs the local office to release the call-related bearer before the route re-selection;
- the Redirect Bearer Release Complete message informs the former station that the original bearer has been released.
- the outgoing interface is a narrowband trunk circuit (such as an ISUP circuit), and the ISAM IAM message needs to be sent out to establish a call.
- the load establishing unit 1502 needs to perform bearer information interaction with the forward office.
- the bearer establishing unit 1502 should also Interact with the media gateway to establish a bearer (such as an IAM message through ISUP). After the failed route reselection, this office is interoperable for BICC-ISUP, and this office is not a BICC CMN.
- the interaction between the local office and the media office and the media gateway includes: first sending a Redirect Forwards Request request to the office, and notifying the forward office to perform the BICC redirection, releasing the original call for 7 years; Returning the Bearer Redirection Connect Forwards message, informing the local office that the bearer redirection can be performed, and returning the new call bearer related information in the message; the local office uses the new call bearer related information notified by the forward office to perform bearer interaction with the gateway, and uses the BICC at the same time.
- the signaling and the forward office perform the interaction of the bearer information.
- the local office selects the outgoing station as the BICC relay, and uses the BICC signaling to interact with the forward office and the backward office for 7-load information, and then the forward office passes the Redirect.
- the Bearer Connected message informs the local office that the bearer is established.
- the local office also informs the forward office to release the relevant bearer before the route reselection through the Redirect Bearer Release Request message.
- the forward office then informs the local office to release the route reselection through the Redirect Bearer Release Proceed message.
- the previous call was related; then Board adopted Bearer Release Complete message before the Redirect notification original bearer has been released to the game point is completed.
- the outgoing call is a BICC trunk circuit, and the IAM message of the ISUP needs to be sent out to establish a call.
- the local office needs to notify the forward office to perform the bearer redirection flow. Cheng, and after the failed route reselection, the local office as the BICC CMN needs to forward the original inter-office bearer related information.
- the device sends a Redirect Forwards Request request to the office in the forward direction, and performs a BICC bearer redirection to the office to release the bearer of the original call.
- the forward station returns a Bearer Redirection Connect Forwards message to notify the local office that the bearer can perform the bearer.
- Redirect and return the new call bearer related information in the message;
- the local office selects the outgoing call as the BICC relay, and the new outgoing call is still the BICC CMN, and the local office directly forwards the forward call to inform the local call forwarding information of the local call
- the forward-point office informs the local office that the bearer establishment is completed through the Redirect Bearer Connected message.
- the local office also informs the forward-office to release the route-reselected 7-bearings before the re-election by the Redirect Bearer Release Request message.
- the Redirect Bearer Release Proceed message is used to notify the local office to release the call-related bearer before the route re-selection.
- the local office then announces that the original bearer of the forward-point office has been released by the Redirect Bearer Release Complete message.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Telephonic Communication Services (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Description
Claims
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2007800003313A CN101507196B (zh) | 2007-02-28 | 2007-10-12 | 呼叫仲裁节点失败路由重选方法、交换机和系统 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CNA2007100842917A CN101257437A (zh) | 2007-02-28 | 2007-02-28 | 呼叫仲裁节点失败路由重选方法、交换机和系统 |
CN200710084291.7 | 2007-02-28 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2008104113A1 true WO2008104113A1 (fr) | 2008-09-04 |
Family
ID=39283912
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2007/070884 WO2008104113A1 (fr) | 2007-02-28 | 2007-10-12 | Procédé de resélection de route de défaillance du nœud de médiation d'appel et échangeur et système de celui-ci |
Country Status (4)
Country | Link |
---|---|
EP (1) | EP1965579B1 (zh) |
CN (2) | CN101257437A (zh) |
ES (1) | ES2469615T3 (zh) |
WO (1) | WO2008104113A1 (zh) |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
MY155379A (en) * | 2008-09-26 | 2015-10-15 | Ericsson Telefon Ab L M | Congestion control method and devices |
WO2014065899A1 (en) | 2012-10-26 | 2014-05-01 | Intel Corporation | Physical uplink control channel (pucch) resource allocation (ra) for a hybrid automatic retransmission re-quest-acknowledge (harq-ack) transmission |
CN103079242B (zh) * | 2012-12-18 | 2015-09-30 | 华为技术有限公司 | 呼叫切换方法、装置和系统 |
CN105144768B (zh) | 2013-04-26 | 2019-05-21 | 英特尔Ip公司 | 频谱共享情境中的共享频谱重新分配 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1402451A (zh) * | 2001-08-13 | 2003-03-12 | 华为技术有限公司 | 支持多个媒体网关的综合业务数字网用户部分路由的方法 |
US6862263B1 (en) * | 1998-12-28 | 2005-03-01 | At&T Corp. | Hierarchical telecommunications network with fault recovery |
CN1798423A (zh) * | 2004-12-21 | 2006-07-05 | 中兴通讯股份有限公司 | 承载与控制分离的移动通讯网络中的路由选择方法 |
CN1885991A (zh) * | 2005-06-20 | 2006-12-27 | 华为技术有限公司 | 一种呼叫处理方法 |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5642396A (en) * | 1995-05-10 | 1997-06-24 | Mci Corporation | Release cause table for failed calls in SS7/ISDN Networks |
DE50115850D1 (de) * | 2001-11-09 | 2011-05-26 | Nokia Siemens Networks Gmbh | Bereitstellung von IVR Ressourcen in BICC Netzen |
US20030204593A1 (en) * | 2002-04-25 | 2003-10-30 | International Business Machines Corporation | System and method for dynamically altering connections in a data processing network |
-
2007
- 2007-02-28 CN CNA2007100842917A patent/CN101257437A/zh active Pending
- 2007-10-12 WO PCT/CN2007/070884 patent/WO2008104113A1/zh active Application Filing
- 2007-10-12 CN CN2007800003313A patent/CN101507196B/zh active Active
- 2007-12-11 ES ES07122934.8T patent/ES2469615T3/es active Active
- 2007-12-11 EP EP20070122934 patent/EP1965579B1/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6862263B1 (en) * | 1998-12-28 | 2005-03-01 | At&T Corp. | Hierarchical telecommunications network with fault recovery |
CN1402451A (zh) * | 2001-08-13 | 2003-03-12 | 华为技术有限公司 | 支持多个媒体网关的综合业务数字网用户部分路由的方法 |
CN1798423A (zh) * | 2004-12-21 | 2006-07-05 | 中兴通讯股份有限公司 | 承载与控制分离的移动通讯网络中的路由选择方法 |
CN1885991A (zh) * | 2005-06-20 | 2006-12-27 | 华为技术有限公司 | 一种呼叫处理方法 |
Also Published As
Publication number | Publication date |
---|---|
EP1965579B1 (en) | 2014-03-19 |
ES2469615T3 (es) | 2014-06-18 |
CN101507196A (zh) | 2009-08-12 |
EP1965579A1 (en) | 2008-09-03 |
CN101507196B (zh) | 2012-05-23 |
CN101257437A (zh) | 2008-09-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7206582B2 (en) | Method, system and apparatus for call path reconfiguration | |
EP1920572B1 (en) | Multimedia subsystem service control for circuit-switched subsystem calls | |
JP4532048B2 (ja) | セルラ・ネットワークにおいて、呼制御とベアラ制御とを分離して、レイヤ・アドレスと論理ポイントとを逆方向に転送する、基本的呼の設定の実施方法 | |
WO2006105732A1 (fr) | Procede de transfert de connexion d’appel par commutation de circuit | |
WO2006131070A1 (fr) | Procede de realisation d'un service vocal d'apres le declenchement du service, procede de commande de route et systeme associe | |
WO2009018744A1 (fr) | Procédé d'implémentation, système, passerelle multimédia et contrôleur de passerelle multimédia pour contrôle de routage | |
WO2009012665A1 (fr) | Procédé pour assurer une continuité d'appel multimédia, équipement et système associés | |
US20040028032A1 (en) | Call looping prevention | |
JP4597449B2 (ja) | セルラ・ネットワークにおいて、呼制御とベアラ制御とを分離して、レイヤ・アドレスと論理ポイントとを順方向に転送する、基本的呼の設定の実施方法 | |
JP4472905B2 (ja) | 呼制御とベアラ制御とが分離された通信ネットワークの柔軟性を増加させる方法 | |
WO2005086453A1 (en) | Method for establishing a call in a telecommunications network; telecommunications network; and controlling device for packet networks | |
US20050180396A1 (en) | Managing routing path of voice over internet protocol (VoIP) system | |
WO2008104113A1 (fr) | Procédé de resélection de route de défaillance du nœud de médiation d'appel et échangeur et système de celui-ci | |
US20090052438A1 (en) | Method, system and device for processing supplementary services | |
WO2008122235A1 (fr) | Procédé de commande d'appel, adaptateur de domaine à commutation de circuits et dispositif terminal | |
JP2005500723A (ja) | パケット・ベースのネットワークにおけるマルチメディア・コールの処理 | |
JP3887569B2 (ja) | Atmベアラパスを管理するための方法およびコンピュータプログラムプロダクトおよびatmパケットアクセスゲートウェイシステムおよびatmパケットアクセスゲートウェイ | |
CN101951346A (zh) | Sip中继路由方法及其系统 | |
JP2001060974A (ja) | パケットネットワークと回路ネットワークを含む通信ネットワークにおいて呼を設定する方法 | |
WO2009015536A1 (fr) | Procédé permettant de faire suivre un état occupé décidé par l'utilisateur | |
WO2008086720A1 (fr) | Procédé, matériel et système de sélection de trajet et de commande de flux | |
CN104244219B (zh) | 用于一隧道解决方案的ggsn代理 | |
JP2001136275A (ja) | Tdmスイッチおよびデータ伝送ネットワーク | |
WO2012103792A1 (zh) | 切换方法及系统 | |
KR100288755B1 (ko) | 프라이비트 네트워크 네트워크 인터페이스에서 연결 설정이 진행중인 호들을 고려한 라우팅 방법 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 200780000331.3 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 07817075 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1225/DELNP/2009 Country of ref document: IN |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 07817075 Country of ref document: EP Kind code of ref document: A1 |