WO2006024225A1 - Procede de realisation d'une double inscription - Google Patents

Procede de realisation d'une double inscription Download PDF

Info

Publication number
WO2006024225A1
WO2006024225A1 PCT/CN2005/001345 CN2005001345W WO2006024225A1 WO 2006024225 A1 WO2006024225 A1 WO 2006024225A1 CN 2005001345 W CN2005001345 W CN 2005001345W WO 2006024225 A1 WO2006024225 A1 WO 2006024225A1
Authority
WO
WIPO (PCT)
Prior art keywords
media gateway
control device
core control
signaling
link
Prior art date
Application number
PCT/CN2005/001345
Other languages
English (en)
Chinese (zh)
Inventor
Jiongjiong Gu
Chunhui Zhao
Yunxia Cai
Zhenhua Liu
Hanbing Chen
Changcheng Guo
Yong Zhong
Yong Lin
Weiqiang Zhou
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CNB2005100647281A external-priority patent/CN1327727C/zh
Priority claimed from CN2005100776102A external-priority patent/CN1882107B/zh
Priority claimed from CNB2005100354806A external-priority patent/CN100459738C/zh
Priority claimed from CN 200510087133 external-priority patent/CN1905474A/zh
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to EP05781860A priority Critical patent/EP1777893A4/fr
Priority to AU2005279575A priority patent/AU2005279575B2/en
Priority to BRPI0514699-2A priority patent/BRPI0514699B1/pt
Publication of WO2006024225A1 publication Critical patent/WO2006024225A1/fr
Priority to US11/709,263 priority patent/US8116760B2/en
Priority to US13/350,261 priority patent/US8571546B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/14—Backbone network devices

Definitions

  • the invention relates to a dual-homing technology in a communication network, in particular to a dual-homing implementation method. Background of the invention
  • the dual-homing described here actually refers to a special network connection mode.
  • Each network entity that needs to provide services by the switching control center is simultaneously connected to two switching control centers, and the two switching control centers are mutually backup relationships.
  • a network entity may be served by any one of two exchange control centers connected thereto; generally, each network entity has its own exchange control center, and normally, each exchange control center manages one or one belonging to itself.
  • Each switching control center provides services for its own network entity.
  • a switching control center fails, another switching control center that is backed up with each other will take over the management of the two switching control centers.
  • the exchange control center refers to a network device at a core position in a network, such as: a soft switch, a mobile switching center server (MSC Server), etc., dual-homing
  • MSC Server mobile switching center server
  • the communication network can be divided into two categories: wired communication network and wireless communication network.
  • the typical representative of the latest wired communication network is Next Generation Network (NGN), and the next generation network is set voice, data, and fax.
  • NGN Next Generation Network
  • a new network integrated with video services realizes the separation of call control and service bearer;
  • the typical representative of the latest wireless communication network is the third generation (3G) mobile communication network.
  • the NGN network and the 3G network have large user capacity, and the requirements for communication reliability and network processing capability are also high. Therefore, the dual-homing networking mode can be introduced in the NGN network and the 3G network.
  • the softswitch in an extremely important position, and the softswitch does not have an active/standby relationship by default at the networking level.
  • dual-homing means that two softswitches back up each other at the networking level, as shown in Figure 1, so that in the case that a softswitch is down or otherwise faulty, another softswitch is in a dual-homing state. Can handle the business processing of downtime or faulty softswitch.
  • each softswitch serves the MGW belonging to itself. If a softswitch device is down or otherwise faulty, the MGW of the downtime or faulty softswitch connection needs to be re-registered to each other. Another soft exchange to ensure continuity of business.
  • the signaling point is a node in the signaling network that processes the control message.
  • the MSC Server is in an extremely important position, and the MSC Server does not have an active/standby relationship by default at the networking level.
  • the MSC Server needs to be dual-homed to realize that when a certain MSC Server is down due to abnormal disaster or hardware upgrade, the service that the failed MSC Server handles can be automatically
  • the standby MSC Server takes over and ensures that service interruption is minimized.
  • dual-homing means that two MSC Servers back up each other at the networking level, as shown in Figure 2. In this way, in the case that an MSC Server is down or otherwise faulty, another MSC Server in dual-homing status. Can handle the business processing of downtime or faulty MSC Server.
  • each MSC Server is provided with OPC, and the base station controller (BSC, Base Station Controller) is connected to the MSC Server access network through the MGW, MGW and MSC Server. Data is connected and transmitted through a relay link.
  • BSC Base Station Controller
  • MGW Mobility Management Entity
  • the core control devices that are generally dual-homed such as the softswitch or the MSC Server, respectively adopt different independent signaling points.
  • the time division on the MGW under the failed signaling point is more TDM (Time Division Multiplexing)
  • the relay link is automatically switched to the TDM trunk group under the effective signaling point.
  • the signaling point of the core control device of the downtime or other fault is invalid, the opposite end The signaling point of the network entity changes, the relay link resources under the effective signaling point are utilized, and the TDM relay link resources under the failure signaling point are no longer utilized, which causes the relay resources to be more serious. waste.
  • the present invention provides a dual-homing implementation method, which can improve the utilization of the core control device while ensuring network reliability; and can realize smooth handover between devices having dual-homing relationships. .
  • the present invention also provides a dual-homing implementation method, which can implement switching between dual-homed devices in time and improve network reliability.
  • a dual-homing implementation method setting any two core control devices to each other as a backup, and setting a network entity belonging to a core control device to be connected to two core control devices through a primary link and a standby link respectively; Includes the following steps:
  • b l Determine whether the core control device corresponding to the primary link is faulty. If yes, activate the standby link; otherwise, return to step b l.
  • Step b l further includes:
  • Step b l further includes: blocking the primary link while activating the standby link.
  • the method further includes: setting a primary signaling point and a standby signaling point in each of the core control devices that are mutually backed up, and a primary signaling point in one core control device and a standby signal in another core control device The corresponding point is corresponding; in step bl, while the standby link is activated, the standby signaling point is activated, and the primary signaling point is closed.
  • the method further includes: setting a primary signaling point and a standby signaling point in each of the core control devices that are mutually backed up, and a primary signaling point in one core control device and a standby signal in another core control device Corresponding to the point; in step cl, while the standby link is blocked, the standby signaling point is turned off, and the primary signaling point is activated.
  • the core control device is a mobile switching center server
  • the network entity is any one of a base station controller, a home location register, a public switched telephone network, a service control point, and a mobile service switching center.
  • the core control device is a mobile switching center server
  • the network entity is a base station controller
  • the method further comprising: connecting the base station controller to the two mobile switching center servers respectively through a media gateway .
  • the media gateway is provided with a signaling gateway;
  • the mobile services switching center server serves as an application service point to the third layer link user adaptation through a message transmission part, and is associated with the signaling by proxy or transit mode. At the signaling point of the gateway.
  • the core control device is a soft switch
  • the network entity is any one of a media resource server, an application server, a public switched telephone network, a comprehensive home location register, a service control point, and a soft switch.
  • the core control device is a softswitch
  • the network entity is a public switched telephone network.
  • the method further comprises: connecting the public switched telephone network to the two softswitches respectively through a media gateway.
  • the media gateway is provided with a signaling gateway; the softswitch is used as an application service point to be associated with the signaling gateway by proxy or transit mode through a message transmission part of the third layer link user adaptation. Let the point.
  • the signaling gateway After receiving the signaling message of the first source signaling point, the signaling gateway determines whether the first connection with a higher priority is available, and if available, passes the first connection and the first The first source signaling point on the core control device performs signaling interaction; otherwise, the second connection is used to perform signaling interaction with the first source signaling point on the second core control device.
  • the first connection is a link between a signaling point on the signaling gateway and a first source signaling point on the first core control device;
  • the second connection is a link between a signaling point on the signaling gateway and a first source signaling point on the second core control device.
  • the method further includes: setting a second source signaling point on the first and second core control devices that are mutually backed up, and setting a first source signaling point and a second source signaling point on each core control device Have a mutual aid relationship;
  • the first connection is a direct route between the signaling point on the signaling gateway and the first source signaling point on the first core control device;
  • the second connection is between the signaling point on the signaling gateway and the first source signaling point on the second core control device, and is forwarded by the second source signaling point on the second core control device.
  • the loop is made up of.
  • the signaling interaction with the first source signaling point on the second core control device by using the second connection includes:
  • the signaling gateway sends an uplink signaling message to a second source signaling point on the second core control device by using a lower priority loop; the second source signaling point uses the uplink signaling Transmitting the message to the first source signaling point on the second core control device;
  • the method further includes: after receiving the signaling message from the first source signaling point of the first and second core control devices, the signaling gateway selects and receives the higher priority according to the priority of the connection.
  • the signaling message of the first connection discards the signaling message from the second connection with lower priority.
  • the method further includes:
  • the first core control device obtains data of the second core control device and a state of the second core control device
  • the first core control device processes the service of the second core control device by using data of the second core control device according to the state of the second core control device.
  • the first core control device in step A1 obtains the state of the second core control device. Obtained through the handshake mechanism.
  • the state of the second core control device includes a normal state and a failure state.
  • the step B1 further includes: when the second core control device is in a normal state, the first core control device obtains data of the second core control device; When the second core control device is in a failed state, perform the following steps:
  • the first core control device takes over the service of the second core control device according to the data of the second core control device.
  • step B11 further includes:
  • the first core control device establishes a service related thereto according to the data of the second core control device;
  • the step B1 further includes: when the second core control device is changed from a failed state to a normal state, performing the following steps:
  • the first core control device returns the service of the second core control device to the second core control device.
  • Step B12 further includes:
  • the first core control device tears down related services according to data of the second core control device
  • the first core control device obtains data of the second core control device.
  • the method further includes: when the first core control device is started, the data having the identifier of the counterpart device is not processed.
  • the present invention also provides a dual-homing implementation method, which sets any two media gateway control function entities MGCF to each other as a backup, and each MGCF manages at least one media gateway, the method includes: a2. determining whether the media gateway needs to be re-registered to the standby MGCF, if yes, proceed to step b2; otherwise, return to step a2;
  • the standby MGCF activates or establishes all signaling links related to the MGW, and then the standby MGCF refreshes the called routing information.
  • the method further includes: the primary MGCF is used to close or block the signaling link associated with the MGW that needs to be re-registered; and, in step b2, the standby MGCF refreshes the called route, and further includes: Called routing information.
  • the primary MGCF closes or blocks the signaling link associated with the MGW that needs to be re-registered as: a signaling link connection involving the media gateway; or a signaling link associated only with the media gateway.
  • step b2 after the media gateway control interface of the media gateway is successfully registered, the backup media gateway control function actively activates or establishes the media gateway related to the link forwarded to the backup media gateway control function from the other device. Signaling link connection.
  • the standby media gateway control function actively opens the message related to the media gateway after the media gateway control interface of the media gateway is successfully registered. Let the link.
  • the signaling link is a link forwarded from the other device to the backup media gateway control function; the signaling link is a message transmission part 2 user adaptation link, a message transmission part 3 user adaptation link Any one of a link access protocol version 5 user adaptation link, or an integrated services digital network Q.921 user adaptation link, a radio access network application part link, and a base station application part link.
  • the other device is a media gateway, or a signaling gateway.
  • the signaling link is an inter-office signaling that is directly used by the media gateway control function on the external interface; the inter-office signaling is any one of bearer-independent call control signaling, or session initiation protocol signaling, or seventh signaling.
  • the signaling link is an inter-office signaling that is directly used by the media gateway control function on the external interface; the inter-office signaling is any one of bearer-independent call control signaling, or session initiation protocol signaling, or seventh signaling.
  • bearer-independent call control signaling or session initiation protocol signaling, or seventh signal
  • the refreshing the called routing information includes the following steps:
  • the active media gateway control function changes an intra-office call related to the re-registered media gateway in the called routing information to an inter-office call;
  • the backup media gateway control function changes an inter-office call between the media gateway other than the re-registered media gateway and the re-registered media gateway in the called routing information to an intra-office call.
  • Each MGCF corresponds to a media gateway controller, and the method includes the following steps:
  • A3. Set a media gateway managed by each media gateway controller, set a media gateway controller of the management media gateway as a home media gateway controller of the media gateway, and set two management different media.
  • the media gateway controllers of the gateway are mutually mutual media gateway controllers;
  • the media gateway periodically sends a heartbeat signal to the current home media gateway controller during normal working, and detects a heartbeat signal sent back by the home media gateway controller, if the home media gateway controller sends back a normal
  • the heartbeat signal returns to this step; otherwise, the dual-homed switchover is initiated to the mutual media gateway controller of the home media gateway controller, and the mutual media gateway controller is controlled as the current home media gateway after the dual-homed switchover. , then return to this step.
  • the method further includes: each media gateway controller establishing a media gateway list for initializing all media gateways to be controlled by the media gateway controller;
  • the initiating the dual-homing switching in the step b3 includes: the media gateway to perform the dual-homing switching reports the registration request to the destination media gateway controller of the dual-homing switching; the destination media gateway controller receives the registration reported by the media gateway After the request, determining whether the media gateway is in the media gateway list established by itself, if yes, accepting the registration request and establishing a connection with the media gateway; otherwise, rejecting the registration request.
  • the method further includes: the media gateway controller periodically transmitting a heartbeat signal to its mutual media gateway controller, and monitoring a heartbeat signal sent by the mutual media gateway controller;
  • the media gateway controller includes two normal working states: a mutual assisted inactive state and a mutual assisted active state;
  • the mediation inactive state After the media gateway controller in the mutual help inactive state detects that the heartbeat signal sent by the mutual media gateway controller is interrupted, the mediation inactive state is transferred to the mutual assisted state;
  • the media gateway controller in the mutual-assisted active state monitors that the mutual-media gateway controller normally transmits the heartbeat signal, and then transfers from the mutual-assisted active state to the mutual-assisted inactive state.
  • the media gateway controller After the media gateway controller recovers from the fault state, if it detects that the mutual mutual media gateway controller sends a normal heartbeat signal, it directly enters the mutual help inactive state; otherwise, directly enters the mutual assistance
  • the normal working state of the media gateway controller further includes: a mutual assist idle state; the media gateway controller enters a mutual assisted air-to-air state after recovering from a fault state; and a media gateway in a mutual assisted air-to-air state
  • the controller transfers to the mutual assisted state or the mutual assisted inactive state according to a state transition control command issued by the system network management center.
  • the method further includes: corresponding to each media gateway controller, setting a media gateway managed by itself as a primary media gateway, setting a media gateway managed by the mutual media gateway controller as a backup media gateway; and storing the setting result in The database of the system network management center to which the media gateway controller belongs;
  • each media gateway setting the media gateway controller that manages the media gateway as the primary media gateway controller of the media gateway, and setting the mutual media gateway controller of the primary media gateway controller as the backup of the media gateway.
  • the media gateway controller ; and stores the result of the setting in the database of the media gateway itself.
  • the media gateway controller in the mutual assisted inactive state further performs the following operations in parallel: maintaining an active link established with its own primary media gateway, and completing control of its primary media gateway through the primary link; A list of media gateways of its own, and processing the registration request reported by the media gateway according to the media gateway list maintained by itself.
  • the media gateway controller in the mutual assisted activation state further performs the following operations in parallel:
  • the media gateway information is further read from the system network management center database, and its own backup media gateway is added to its own control. List of media gateways.
  • Al l traversing the media gateway list maintained by itself, and querying the system network management center database to obtain the backup media gateway information in the media gateway list;
  • A12. Send an exit service message to the backup media gateway, notify the backup media gateway that the media gateway controller no longer performs service, and cause the backup media gateway to immediately remove the backup link; A13 > close the backup media gateway The communication port, the spare link is removed; A14. All the alternate media gateway information is deleted from the list of media gateways maintained by itself.
  • the media gateway controller further reads the media gateway information from the system network management center database and adds its own primary media gateway to the media gateway list maintained by itself before moving from the fault state or the mutual assist idle state to the mutual assist inactive state;
  • the media gateway controller further reads the media gateway information from the system network management center database and adds its own primary media gateway and backup media gateway to the list of media gateways maintained by itself before moving from the fault state or the mutual assisted idle state to the mutual assisted activation state. .
  • the media gateway After the media gateway is switched to the backup media gateway controller, the media gateway periodically sends a heartbeat signal to its own primary media gateway controller, and listens to the heartbeat signal sent back by the primary media gateway controller.
  • the media gateway controller sends a normal heartbeat signal, and then sets the primary media gateway controller to be the current home media gateway controller of the media gateway, and initiates a switchover from the backup media gateway controller to the primary media gateway controller. .
  • the method further includes: setting a heartbeat interruption threshold:
  • the home media gateway controller sends back a normal heartbeat signal to: the number of interruptions of the home media gateway controller continuously sending back a heartbeat signal or returning a heartbeat signal is less than a set heartbeat interruption threshold.
  • the dual-homing implementation method of the present invention can ensure that the MGW belonging to the faulty core control device can detect a fault in time when a certain core control device is down or other faults occur. , timely switching to other core control devices, thereby effectively The problem that the MGW cannot be normally switched due to the unexpected failure of the core control device in the prior art is avoided, and the occurrence of the call loss situation is effectively avoided. Moreover, the problem of confusion of the MGW registration can be effectively avoided, and the dual-homing function of the MGW is further improved.
  • the core control device When a core control device fails, the core control device with which it has a dual-homing relationship can handle the service of the faulty core control device, thereby greatly improving the reliability of the next-generation network, and because of the two cores with dual-homing relationship
  • the control device operates in a normal state, and therefore, the method of the present invention can improve the utilization of the core control device.
  • the signaling gateway interacting with it can detect that the core control device has failed, but does not consider that the destination signaling point of the signaling message is unreachable, but can pass the priority.
  • the lower link or route sends the signaling message to the core control device that has a mutual assistance relationship with the faulty core control device. For other signaling points in the network, there is no process from communication failure to recovery. Therefore, smooth switching of the signaling gateway can be implemented.
  • the link utilization can be improved. Rate, effectively guarantee the signaling transmission and processing capabilities of the next generation network.
  • the data processing scheme proposed by the present invention for a core control device having a dual-homing relationship can maintain data consistency between core control devices having dual-homing relationships, thereby supporting continuity of link management and service processing before and after MGW switching. , thus ensuring smooth switching of the MGW.
  • FIG. 1 is a schematic diagram of a dual-homing network based on an NGN network
  • FIG. 2 is a schematic diagram of a dual-homing networking based on a 3G network
  • FIG. 3 is a schematic diagram of a dual-homing network based on an NGN network according to the present invention.
  • FIG. 4 is a schematic diagram of a dual-homing networking based on a 3G network in the present invention.
  • FIG. 5 is a schematic diagram of networking for implementing SG dual-homing in an NGN network according to a preferred embodiment of the present invention
  • FIG. 6 is a schematic diagram of networking for implementing SG dual-homing in an NGN network according to another preferred embodiment of the present invention
  • FIG. 5 is a schematic diagram of networking for implementing SG dual-homing in an NGN network according to a preferred embodiment of the present invention
  • FIG. 6 is a schematic diagram of networking for implementing SG dual-homing in an NGN network according to another preferred embodiment of the present invention
  • FIG. 5 is a schematic diagram of networking for implementing SG dual-homing in an NGN network according to a preferred embodiment of the present invention
  • FIG. 6 is a schematic diagram of networking for implementing SG dual-homing in an NGN network according to another preferred embodiment of the present invention
  • FIG. 7 is a flowchart of implementing a SG dual-homing method based on a route priority according to FIG. 6;
  • FIG. 8 is a flowchart of a dual-homing implementation method according to a preferred embodiment of the present invention.
  • FIG. 9 is a network state diagram before a fault occurs in a preferred embodiment of the present invention.
  • FIG. 10 is a network state diagram when the MGW registers with the standby MGCF after the MC interface fails in the preferred embodiment shown in FIG. 9;
  • FIG. 11 is a network state diagram of the dual-homing function of the preferred embodiment of the present invention
  • FIG. 12 is a schematic diagram of a network structure for implementing the MGW dual-homing function according to the embodiment of the present invention
  • Flow chart of data processing
  • FIG. 14 is a structural diagram of a device for implementing data processing on a core control device of the present invention.
  • FIG. 15 is a schematic diagram of a dynamic dual-homing solution. Mode for carrying out the invention
  • the basic idea of the present invention is to prevent a core control device having a dual-homing relationship, such as a softswitch or an MSC Server, from showing only a unique signaling point to a peer network entity.
  • the dual-homed state saved in the core control device implements the link state management of the message transfer part (MTP), and uses the backup route of the MTP3 or the signaling link to implement automatic message switching to ensure that the peer network entity sees
  • MTP message transfer part
  • the NGN-based dual-homing network is used.
  • the core control device is a soft switch
  • the peer network entity is an MGW.
  • Each of the softswitches in this embodiment is provided with two primary and secondary signaling points, and corresponds to the primary and secondary links. Under normal circumstances, the interaction between the softswitch and the MGW uses only one signaling point and its corresponding link.
  • FIG. 3 is a schematic diagram of a dual-homing network based on an NGN network according to the present invention, as shown in FIG.
  • the networked system includes: softswitch 31-1 and softswitch 31-2, MGW 32-1 and MGW 32-2, and PSTN 33-1 and PSTN 33-2.
  • the softswitch 31-1 and the softswitch 31-2 are dual-homing offices that are mutually active and standby. Here, use "-number" to distinguish devices with the same function.
  • the solution in this embodiment is also applicable to the softswitch and media resource server, the application server, the smart home location register (SHLR), the PSTN, the service control point (SCP), and the soft control.
  • SHLR smart home location register
  • PSTN PSTN
  • SCP service control point
  • the soft control For the networking of the device, the specific implementation of the technical solution is described by using the softswitch and the MGW networking as an example. The specific implementation of other networking scenarios is similar to this embodiment.
  • PSTN 33-1 is connected to softswitch 31-1 and softswitch 31-2 through MGW 32-1
  • PSTN 33-2 is connected to softswitch 31-1 and softswitch 31-2 through MGW 32-2.
  • the link between the MGW 32 and the dual-homed two softswitches 31 is the load sharing link of the same link set.
  • the link 1 and the link 2 are the same link set
  • the link 3 is The link 4 is the same link set, and the configuration of the same link set can be completed on the MGW 32.
  • the link between the MGW 32 and the softswitch 31 to which it belongs is referred to as the primary link
  • the link between the other softswitch 31 that is the backup is referred to as the standby link.
  • the PSTN selects only the primary link.
  • the primary link is indicated by a solid line
  • the standby link is indicated by a broken line.
  • a primary signaling point OPC1 and a standby signaling point OPC2 are set, and in the softswitch 31-1, a primary signaling point 0PC2 and a standby signaling point 0PC1 are set, and it can be seen that OPC 1 is a softswitch.
  • OPC2 is the primary signaling point in softswitch 31-2, and the alternate signaling point in softswitch 31-1.
  • OPC1 is the only signaling point seen by PSTN 33-1, which is normally activated
  • OPC2 is the only signaling point seen by PSTN 33-2, which is normally in standby state
  • 0PC2 is the only signaling point seen by the PSTN 33-2 that is normally activated
  • 0PC1 is the only signaling point seen by the PSTN 33-1 that is normally in the standby state.
  • the softswitch 31 is configured to perform softswitch processing, detect the state of the softswitch 31 that is mutually active and standby, and determine whether to activate the third layer of the message transmission part of the standby signaling point according to the detection result (MTP3, Message Transfer Part Level 3) link.
  • the softswitch 31-2 When the softswitch 31-2 detects the softswitch 31-1 downtime with the active-standby relationship or other faults, activate the MTP3 link of the standby signaling point OPC1, that is, link 2, so that PSTN 33 The link of the A interface of the -1 is switched to the link 2, so that the message of the PSTN 33-1 is automatically sent to the softswitch 31-2, and the softswitch 31-2 will take over the service of the softswitch 31-1.
  • the functions and related configurations of the MGW 32 and the PSTN 33 are both prior art and will not be described in detail herein.
  • the dual-homed softswitch 31 blocks all MTP3 links of the local signaling point in the standby state by the management prohibition mode. Specifically, when the softswitches 31 -1 and 31-2 are both normal, the softswitch 31 -1 blocks the link 2, and the softswitch 31-2 blocks the link 4, so that the signaling message of the PSTN 33 can be prevented from being simultaneously sent to the two Softswitch 31.
  • the standby softswitch actively activates the M P3 link corresponding to the standby signaling point of the local office after detecting the peer fault.
  • the softswitches here are mutually active and standby, so the master and the backup are only relative concepts.
  • the softswitch 31-1 as the main softswitch as an example, when the softswitch 31-2 detects the softswitch 31-1 downtime or other fault occurs, the MTP3 link corresponding to the local signaling point OPC 1 is activated. 2. Switch the A-interface link of the PSTN 33-1 to the link. In this way, the PSTN 33-1 message is automatically sent to the softswitch 31-2. The softswitch 31-2 will successfully take over the softswitch 31-1. Business processing.
  • the primary softswitch 31 before the fault informs the standby softswitch 31 before the fault through the private protocol or the standard protocol, and the standby softswitch 31 before the fault actively disables the standby signaling of the local office. All the MTP3 links of the point are then notified to the primary softswitch 31 before the fault, and then the primary softswitch 31 before the fault actively activates all the links of its own primary signaling point, and restores all links corresponding to the primary signaling point. Management.
  • the solution in this embodiment is applicable to the dual-homing network of the softswitch and the SHLR, the PSTN, and the SCP.
  • the signaling transit point STP, Signalling Transfer Point
  • MTP3 configured to two softswitches is the same link set, Automatic switching of the SHLR to softswitch signaling link.
  • Another implementation may be employed for the sole point of signaling.
  • the specific solution is as follows: two softswitches of dual-homing serve as two application service points (ASP, Application Service Point), and a message transfer part of the third layer user adaptation (M3UA, MTP3 User Adaption) proxy or transfer mode is associated with the signaling.
  • ASP Application Service Point
  • M3UA MTP3 User Adaption
  • the two ASPs are configured as the primary and backup modes.
  • the SG is configured to support the M3UA, and adapts the service on the softswitch to the standby softswitch when the primary softswitch is down or other faults.
  • the SG may be an independent external device or embedded in the access side MGW.
  • the M3UA is supported by a standalone SG or an SG embedded in the MGW. Under this scheme, the signaling of the PSTN is terminated on the SG.
  • Embodiment 2 Embodiment 2:
  • This embodiment is directed to a 3G-based dual-homed network.
  • the core control device is an MSC Server
  • the peer network entity is an MGW.
  • two signaling points, primary and secondary are set to be intersected, and two links are configured for the primary and secondary devices.
  • the interaction between the softswitch and the MGW uses only one signaling point and its corresponding link.
  • the system of the dual-homing network includes: MSC Server 41-1 and MSC Server 41-2, MGW 42-1 and MGW 42- 2 and BSC 43-1 and BSC 43-2.
  • the MSC Server 41-1 and the MSC Server 41-2 are dual-homing offices that are mutually active and standby. Here, use "-number" to distinguish devices with the same function.
  • the solution in this embodiment is applicable to the networking of the MSC Server and the BSC, the Home Location Register (HLR, Home Location Register), the PSTN SCP, and the MSC.
  • This embodiment only uses the MSC Server and the BSC network.
  • the specific implementation of the technical solution is described, and the specific implementation of other networking scenarios is similar to this embodiment.
  • the BSC 43-1 is connected to the MSC Server 41-1 and the MSC Server 41-2 through the MGW 42-1
  • the BSC 43-2 is connected to the MSC Server 41-1 and the MSC Server 41-2 through the MGW 42-2.
  • the link between one MGW 42 and the dual-homed two MSC Servers 41 is the same link set.
  • the load sharing link specifically, link 1 and link 2 are the same link set
  • link 3 and link 4 are the same link set
  • the configuration of the same link set can be completed on the MGW 42.
  • the link between the MGW 42 and the MSC Server 41 to which it belongs is referred to as a primary link
  • the link between another MSC Server 41 that is a backup to each other is referred to as a backup link.
  • the primary link is indicated by a solid line
  • the standby link is indicated by a broken line.
  • the primary signaling point OPC1 and the standby signaling point OPC2 are set in the MSC Server 41-1.
  • the primary signaling point OPC2 and the standby signaling point OPC1 are set in the MSC Server 41-2.
  • the OPC1 is the MSC Server 41.
  • the primary signaling point in -1 the standby signaling point in MSC Server 41-2;
  • OPC2 is the primary signaling point in MSC Server 41-2, the secondary signaling point in MSC Server 41-1.
  • OPC1 is the only signaling point seen by BSC 43-1 that is normally activated
  • OPC2 is the only signaling point seen by BSC 43-2 that is normally in standby.
  • OPC2 is the only signaling point seen by BSC 43-2 that is normally activated.
  • OPC 1 is the only signaling point seen by BSC 43-2 in the standby state under normal conditions. .
  • the MSC Server 41 is configured to perform softswitch processing, detect the status of the MSC Server 41 that is in active standby, and determine whether to activate the MTP3 link of the standby signaling point according to the detection result. For example, when the MSC Server 41 - 2 detects that the MSC Server 41 - 1 is in active/standby relationship with the MSC Server 41 - 2, the MTP3 link of the standby signaling point OPC1 is activated, that is, the link 2, so that the A of the BSC 43-1 is The interface link is switched to link 2, so that the message of BSC 43-1 is automatically sent to MSC Server 41-2, and MSC Server 41-2 will take over the service processing of MSC Server 41-1.
  • the functions and related configurations of the MGW 42 and the BSC 43 are both prior art and will not be described in detail herein.
  • the dual-homed MSC Server 41 blocks all MTP3 links of the local signaling point in the standby state by the management prohibition mode. Specifically, when both MSC Servers 41-1 and 41-2 are normal, MSC Server 41-1 blocks link 2, and MSC Server 41-2 blocks link 4, so that signaling messages of BSC 43 can be prevented from being simultaneously sent to two. MSC Server 41. In the event that the primary MSC Server 41 is down, the standby MSC Server actively activates the alternate signaling point MTP3 link in the local office after detecting the peer failure. It should be noted that the MSC Server is a master-slave relationship, so the master and the backup are only relative.
  • MSC Server 41-1 as the primary MSC Server as an example, when MSC Server 41-2 detects that MSC Server 41-1 is down, it activates the MTP3 link corresponding to the standby signaling point OPC1 of the local office, that is, link 2, so that BSC The A interface link of 43-1 is switched to the link. In this way, the BSC 43-1 message is automatically sent to the MSC Server 41-2, and the MSC Server 41-2 will take over the service processing of the MSC Server 41-1.
  • the primary MSC Server 41 before the fault informs the standby MSC Server 41 before the fault through the private protocol, and the standby MSC Server 41 before the fault actively bans all the standby signaling points of the local office.
  • the MTP3 link then informs the primary MSC Server 41 before the failure, and then the primary MSC Server 41 before the failure actively activates all the links of its primary signaling point, and restores its own management of all links corresponding to the primary signaling point. .
  • the solution in this embodiment is applicable to the dual-homing networking of the MSC Server and the HLR, PSTN, SCP, and MSC.
  • the MTP3 configured to the two MSC Servers on the STP can be the same link set to implement automatic switching of the HLR to the MSC Server signaling link.
  • the two MSC servers that are dual-homed are associated with one of the two ASPs, the M3UA proxy or the transit mode, and the two ASPs are configured as the primary and backup modes.
  • the SG is used to support the M3UA. When the primary MSC Server is down, the service on the MSC Server is adapted to the standby MSC Server.
  • the SG may be an independent device of the external MSC Server or embedded in the access side MGW.
  • the M3UA is supported by a standalone SG or an SG embedded in the MGW. Under this scheme, the signaling of the BSC is terminated on the SG.
  • a core control device with a dual-homing relationship such as a softswitch or an MSC Server
  • a core control device with a dual-homing relationship such as a softswitch or an MSC Server
  • a signaling point for the access network so that In active/standby switchover, a failed softswitch or TDM between the MSC Server and the access network
  • the link resources can be continuously utilized, and the waste resource waste caused by the independent dual-homing signaling points is avoided; and the above solution only needs to be slightly modified for the softswitch or the MSC Server, and does not involve system upgrade, for other devices. Only the configuration changes, and the reliability of the dual-homed networking can be improved at a small cost.
  • the core control device is a switching device, where one switching device is in a softswitch network and the other switching device is in a signaling network No. 7.
  • the two switching devices are mutually homing to each other, and the SG connected to one of the two switching devices is connected to another switching device having a mutual aid relationship with the switching device, and at the same time, the two switching devices are
  • Each of the connected SGs is configured with a primary switching device and a standby switching device. When the two switching devices are working normally, each SG performs signaling interaction with the primary switching device to which it belongs. When a primary switching device fails.
  • the SG that performs the signaling interaction with the faulty switching device will be switched to another switching device, that is, the standby switching device that performs the switching of the SG, and the signaling interaction continues.
  • the SG dual-homing method can improve the reliability of next-generation networks without reducing the utilization of switching equipment.
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • FIG. 5 is a schematic diagram of networking for implementing SG dual-homing in a next-generation network according to the embodiment.
  • SG C and SG D are respectively connected to switching device A and switching device B.
  • Switching device A and switching device B have dual-homed mutual assistance relationship, and switching device A is the primary switching device of SG C.
  • the backup switching device of the SG D, and the switching device B is the standby switching device of the SG C, which is the primary switching device of the SG D.
  • any one of the switching devices may be referred to as a first switching device and the other switching device as a second switching device.
  • the signaling point c of the SG C performs signaling interaction with the source signaling point a of the switching device A
  • the signaling point d of the SG D performs signaling interaction with the source signaling point b of the switching device B.
  • the implementation method of the SG dual-homing in this embodiment is mainly Includes:
  • Two logical signaling points a and b that are logically independent of each other are respectively configured on the switching device A and the switching device B having the dual-homed mutual-assisted relationship.
  • the two source signaling points a and b have mutual assistance relationships.
  • One of the signaling points may also be referred to as a first signaling point, and another signaling point may be referred to as a second signaling point;
  • the signaling point c to the source signaling point a on the SG C includes two connections with different priorities: the higher priority signaling point c to the link of the source signaling point a on the switching device A, that is, the first Connection, as shown by the solid line in the figure, and the link of the lower priority signaling point c to the source signaling point a on the switching device B, that is, the second connection, as indicated by the dotted line in the figure;
  • configuring the signaling point d to the source signaling point b on the SG D includes two types of connections having different priorities. Connection: a higher priority signaling point d to the link of the source signaling point b on the switching device B That is, the first connection, as shown by the solid line in the figure, and the link of the lower priority signaling point d to the source signaling point b on the switching device A, that is, the second connection, as indicated by the dotted line in the figure.
  • the signaling message transmission process is as follows:
  • the SG C will first determine the signaling point c to the source. If the higher priority link is available, that is, if the switching device A is working normally, the uplink signaling message is sent to the switching device A through the high priority link.
  • the source signaling point a is processed; otherwise, when the switching device A exits the service for some reason, for example, when a failure occurs, the SG C sends the uplink signaling message to the switching device through the low priority link.
  • the source signaling point a on B is processed to implement dual-homing of SG C to switching device A and switching device B.
  • the link is the transmission channel of the signaling message, once the switching device fails, the link cannot send and receive messages normally. Therefore, the physical layer or the link layer of the SG C can easily detect whether the link is faulty or not. This selects the appropriate link to send the signaling message.
  • the implementation method of SG D dual-homing is basically the same as the above method, specifically, when the destination signaling point After the uplink signaling message of the source signaling point b reaches the signaling point d of the SG D, the SG D will also first select the link with the higher priority to send the uplink signaling message according to the priority of the link in the link set. To the source signaling point b on the switching device B, if the source signaling point b on the switching device B is unreachable, the uplink signaling message is sent to the source message on the switching device A through the low priority link. Let point b implement dual-homing of SG D to switching device B and switching device A.
  • the source signaling point a of the switching device A sends the downlink signaling message to the signaling point c of the SG C, and the source signaling point b of the switching device B sends the downlink message.
  • the signaling point d to the message to the SG D; in the case where one of the switching devices fails, the signaling points c and SG D to the SG C should be respectively sent by the two source signaling points on the switching device that has not failed.
  • the signaling point d sends a downlink signaling message.
  • the source signaling point a on the switching device B performs signaling interaction with the signaling point c of the SG C.
  • the method described in this embodiment can greatly improve the reliability of the next generation network, and since the switching device A and the switching device B interact with the SG C and the SG D respectively under normal conditions, it can be improved.
  • the utilization of the switching device since the switching device A and the switching device B interact with the SG C and the SG D respectively under normal conditions, it can be improved.
  • the downlink signaling message is sent to the signaling point on the SG D to cause the signaling message.
  • messages from lower priority links are discarded according to link priority, for example For SG C, the signaling message from switching device B will be discarded.
  • the SG C when the switching device A fails, the SG C detects that the link with higher priority is unavailable, but does not consider the source signaling point a. Unreachable, but smooth switching of the source message sent by the signaling message to the switching device B through the low priority link.
  • Embodiment 4 According to the protocol, the maximum number of links in the link set between the two signaling points is limited, and is generally up to 16 links. In the method described in this embodiment, the SG needs to be redundant.
  • the remaining link for example, the link from the signaling point c on the SG C to the switching device source signaling point a is equivalent to the backup link of the signaling point c on the SG C to the source signaling point a of the switching device A,
  • this part of the redundant link is not used to transmit signaling messages, resulting in lower link utilization between signaling points, and signaling point c and source signaling point in SG C
  • the smooth switching of the SG also proposes an implementation scheme based on routing priority.
  • FIG. 6 is a schematic diagram showing the networking of implementing SG dual-homing in a next-generation network according to the embodiment.
  • the SG C and the SG D are respectively connected to the switching device A and the switching device B, wherein the switching device A and the switching device B have a dual-homing mutual assistance relationship, and the switching device A is the primary switching device of the SG C.
  • the switching device B is the standby switching device of SG D
  • switching device B is the standby switching device of SG C, which is the primary switching device of SG D.
  • any one of the switching devices may be referred to as a first switching device and the other switching device as a second switching device.
  • the signaling point c of the SG C performs signaling interaction with the source signaling point a of the switching device A
  • the signaling point d of the SG D performs signaling interaction with the source signaling point b of the switching device B.
  • the implementation method of the SG dual-homing described in this embodiment includes:
  • Two logical signaling points a and b that are logically independent of each other are respectively configured on the switching device A and the switching device B having the mutual-assisted relationship, and the two source signaling points a and b are configured to have a mutual assistance relationship.
  • One of the signaling points may also be referred to as a first signaling point, and another signaling point may be referred to as a second signaling point;
  • the source signaling point b is regarded as a signaling transfer point (STP);
  • STP signaling transfer point
  • the dual assignment of SG C and SG D can also be implemented.
  • the signaling message transmission process is as shown in FIG. 7 .
  • Steps 701 to 703 After the destination signaling point is that the uplink signaling message of the source signaling point a reaches the signaling point c of the SG C, the SG C first determines the two routes of the signaling point c to the source signaling point a. Whether a medium-priority direct route is available,
  • step 702 is performed, and the uplink signaling message is directly sent to the source signaling point on the switching device A by using the high-priority direct route. a process, then end;
  • step 703 is performed, and the low-priority loop is used to pass the uplink signaling message between the SG C and the switching device B.
  • the link is sent to the source signaling point b on the switching device B, and then step 704 is performed;
  • Steps 704 to 706 The switching device B determines, according to the pre-configured source signaling point, whether the source signaling point a is the source signaling point of the switching device, and if yes, executing step 705, the source signaling point b is the source signaling point The message is forwarded to the source signaling point a, and the source signaling point a terminates and processes the signaling message. At this time, the source signaling point acts as an STP, and then ends; otherwise, step 706 is performed, and the method is discarded. The signaling message then ends.
  • the switching device A when the switching device A exits the service, if the source signaling point a of the switching device B needs to transmit the signaling message to the other switching device through the SG C, the source signaling is performed on the switching device B. There is no link between the point a and the signaling point c of the SG C.
  • the switching device B needs to first determine the mutual source signaling point b of the source signaling point a on the switching device B and the signaling point c on the SG C. Chain Whether the path is available, if available, the signaling message is sent to the SG C through the link between the source signaling point b and the signaling point c on the SG C, and then forwarded by the SG C. At this time, the source information
  • the role of the point b is still an STP; if the link between the source signaling point b and the signaling point c on the SG C is unavailable, the downlink signaling message cannot be sent.
  • the implementation method of the SG D dual-homing is basically the same as the above method, and will not be described again.
  • the signaling message is caused.
  • the SG receives the signaling messages from the switching device A and the switching device B at the same time, the SG will discard the message from the lower priority route according to the routing priority, for example, for the SG C. The signaling message from switching device B will be discarded.
  • the SG C when the switching device A fails, the SG C detects that the direct route with higher priority is unavailable, but does not consider the source signaling point a. The unsuppressed, but the low-priority route is used to send the signaling message to the switching device B. Therefore, it can be seen that the method in this embodiment can implement smooth switching of the SG when the switching device fails.
  • the method described in this embodiment has the same advantages as the third embodiment, that is, on the one hand, the utilization of the switching device can be improved while improving the reliability of the next generation network; Smooth switching of SG.
  • the method in this embodiment does not need to set a redundant link between the switching device and the signaling point of the SG, the link utilization rate is improved, and the next generation network is effectively guaranteed. Signaling processing performance when traffic is large.
  • the method described in Embodiment 4 configures two routes between the signaling point c of the SG C and the source signaling point a: a direct route and a loop path, wherein the loop is substantially occupied only by the loop Signaling point c on SG C and switching device B
  • the link between the source signaling point b does not occupy the link between the signaling point c and the source signaling point a on the switching device A or the switching device B. Therefore, under normal circumstances, the signaling on the SG C
  • the link between point c and the signaling point a on the switching device A can be fully configured, which greatly satisfies the demand of the traffic.
  • the signaling point d on the SG D and the signaling point b on the switching device B are usually used.
  • the signaling interaction is performed. Therefore, when the switching device A fails and the SG C uses the loop to transmit the signaling message, the link occupied by the signaling message does not affect other services, and at the same time, the signaling on the SG C
  • the link between point c and signaling point b on switching device B can also be fully configured, so as not to affect its own traffic.
  • MGW and the core control device both detect whether the MGW needs to be re-registered in real time, and further, can also be in the MGW and the core control device.
  • the heartbeat mechanism is set.
  • the switchover can be triggered by the core control device. For example, if only one link fails, the switchover can also be triggered by the MGW device, for example: the interface between a core control device and the MGW. A fault occurs, or a core control device fails.
  • the MGW can initiate a heartbeat interrupt.
  • FIG. 9 to FIG. 11 show the handover process of the dual-homing device MG, where the core control device is a media gateway control function entity (MGCF), and MGCF1 and MGCF2 are two mutual
  • the MGCF, MG1, MG2, and MG3 of the backup relationship are three media gateways, and LE1, LE2, and LE3 are three local exchange networks (LE, Local Exchange).
  • MGCF1 and MGCF2 are connected by MGCF, as indicated by a thin dotted line; MG1 and MG2 are connected to MGCF1 through user adaptation (UA) signaling and MC interface, and MG3 passes UA signaling and MC interface with MGCF2.
  • UA user adaptation
  • the thin solid line in the figure indicates the MC interface
  • the dotted line indicates the UA signaling
  • the MG1 and LE1 are connected through the narrowband signaling and the relay bearer
  • the MG2 and LE2 are connected through the narrowband signaling and the relay bearer
  • MG3 The connection between LE3 and LE3 is through narrowband signaling and relay bearer.
  • the thick solid line indicates the relay bearer
  • the thick dotted line indicates the narrowband signaling.
  • Narrowband signaling is usually transmitted to the MGCF through the corresponding UA signaling, such as SS7 (SS7).
  • SS7 SS7
  • M2UA, MTP2 User Adaptation MTP2 User Adaptation
  • M3UA MTP3 User Adaptation
  • the SG devices in Figures 9 through 11 are embedded in the MG, and in other application examples the SG can also be placed separately.
  • Step 801 Determine whether the MGW needs to be re-registered to the standby MGCF. If yes, proceed to the subsequent step. Otherwise, return to step 801 to continue monitoring.
  • Condition 1 After the MGW determines that the MC interface link is faulty, the MGW can automatically register with the standby MGCF. As shown in Figure 10, the MC interface of MG2 to MGCF1 is faulty. If the MC interface is faulty with "x" in Figure 10, MG2 needs to be re-registered with MGCF2.
  • the MGW may also consider the MC interface to be faulty, thereby triggering the process of registering to the alternate MGCF. In this case, the steps associated with the primary MGCF are not. It needs to be executed. Specifically, step 802 does not need to be performed. In step 804, the operation performed by the primary MGCF does not need to be performed.
  • the MGW receives a command from the primary MGCF to register with the alternate MGCF.
  • Step 802 If the primary MGCF is working normally and there is no fault, the primary MGCF closes the signaling link associated with the MGW that needs to be re-registered. Here, it is assumed that the primary MGCF is normal.
  • the primary MGCF finds that the MC interface is faulty, the primary MGCF can actively close all signaling links associated with the MGW that needs to be re-registered.
  • the primary MGCF actively closes all signaling links associated with the MGW to be re-registered.
  • the first method of shutdown is: For M2UA, M3UA, Link Access Protocol version 5 user adaptation (V5UA, LAPV5 User Adaptation), integration Service Digital Network Q.921 User Adaptation (IUA, ISDN Q.921-User Adaptation), Radio Access Network Application Part (RANAP), Base Station Application Part (BSAP), etc., are forwarded to the MGCF chain from other devices such as MGW or SG.
  • V5UA Link Access Protocol version 5 user adaptation
  • IUA Integration Service Digital Network Q.921 User Adaptation
  • RANAP Radio Access Network Application Part
  • BSAP Base Station Application Part
  • SCTP stream control transmission protocol
  • Inter-office signaling such as Bearer Independent Call Control (BICC), Session Initiation Protocol (SIP), etc.
  • BICC Bearer Independent Call Control
  • SIP Session Initiation Protocol
  • the signaling link related to the MGW refers to: signaling that is related to the MG W as long as the transmitted signaling is related to the voice resource of the specific MGW, for example: a start address message (I AM , In the Initial Address Message, the signaling of the MGW is occupied, and the signaling is related to the MGW, and the link transmitting the signaling is a signaling link related to the MGW resource, and the characteristics of the links are that they are transmitted.
  • the signaling is only related to the MGW session. As shown in Figure 9, the path and signaling of LE2 to MG1, when communicating with MG1, LE2 will interact with MGCF through this narrowband signaling.
  • Step 803 If the standby MGCF is normal and has no fault, when the new MGW is registered, all signaling links related to the MGW are actively activated. Here, it is assumed that the standby MGCF is normal.
  • the MGCF should take over the MGW-related signaling.
  • the first activation method For the M2UA, M3UA, V5UA, IUA and other links forwarded to the MGCF from other devices such as the MGW or the SG, after the MC interface of the new gateway is successfully registered, the MGW is controlled by the newly registered MGCF, MGCF. Actively activate or establish a signaling SCTP connection for the gateway.
  • the second activation method For the inter-office signaling of the type such as the BICC and the SIP, the MGCF directly connects to the external interface, and does not pass the MGW or the SG. After the gateway MC is successfully registered, the MGCF also actively opens and The gateway-related signaling link.
  • the type such as the BICC and the SIP
  • FIG. 10 is a network configuration after step 802 is performed
  • FIG. 11 is a network configuration after step 803 is performed.
  • MGCF1 finds that the MC interface of MG2 is faulty, it closes MG2 to its own UA signaling link.
  • MGCF2 finds that MG2 registers with itself, it activates the signaling link related to MG2.
  • Step 804 The primary and backup MGCFs refresh the called routing information.
  • the call between the different primary MGs in the original primary MGCF becomes the inter-office call between the primary and secondary MGCFs, and the other MGWs and new ones in the original standby MGCF.
  • the interoffice call between the registered MGWs becomes an intra-office call, so the called routing information needs to be modified.
  • the primary MGCF changes the intra-office call in the called routing information related to the MGW re-registered to the standby MGCF to an inter-office call, and the backup MGCF will between the other subordinate MGWs in the called routing information and the newly registered MGW.
  • the interoffice call is changed to an intra-office call.
  • the intra-office call related to MG2 in the called routing information that is, the call between MG1 and MG2 is changed to an inter-office call; for MGCF2, the MG2 and MG3 in the called routing information are Inter-office calls are changed to intra-office calls.
  • the physical entity corresponding to the MGCF is the Media Gateway Controller (MGC).
  • MGW Media Gateway Controller
  • the present invention also provides a relationship between the MGW and the home MGC. If the heartbeat is interrupted, the MGW detects that the MGC is faulty or the link connection with the home MGC is faulty. The MGW initiates a switchover and re-registers with another MGC.
  • one or more MGWs managed by the MGW are configured in advance for each MGC in the network, and at the same time, the two MGCs are mutually backed up.
  • the two MCUs have a backup relationship.
  • the MGCs are called each other's mutual help MGC:.
  • MGW1 and MGW2 are managed by MGC1
  • MGW3 and MGW4 are managed by MGC2, MGC1 and MGC2.
  • MGW1 and MGW2 are the primary MGWs of MGC1, which are the standby MGWs of MGC2; and MGW3 and MGW4 are the primary MGWs of MGC2, which are the standby MGWs of MGC1. It can be seen that the primary MGW and the standby MGW are relative concepts for a certain MGC.
  • the link established between each MGC and its active MGW is called the primary link, as shown by the double-arrow solid line between the MGC and the MGW in Figure 12; the link established between each MGC and its standby MGW is called As a backup link, as shown by the dotted line between the MGC and the MGW in FIG.
  • the primary MGW and the standby MGW information configured for each MGC are also stored in the database of the system network management center for query by the MGC.
  • the method described in this embodiment also pre-configures a primary MGC and a standby MGC for each MGW in the network.
  • the primary MGC is the MGC that manages the MGW
  • the standby MGC is the mutual-assisted MGC of the primary MGC of the MGW.
  • the primary MGC of MGW1 and MGW2 is MGC1
  • the standby MGC is MGC2
  • the primary MGC of MGW3 and MGW4 is MGC2
  • the standby MGC is MGC1.
  • the primary MGC and the standby MGC are also relative concepts for a certain MGW.
  • the MGC and the standby MGC information of each MGW are saved in the MGW's own database.
  • the MGW Under normal circumstances, the MGW will belong to its primary MGC, and in the event of a failure of the primary MGC, it will switch to its alternate MGC, belonging to its alternate MGC.
  • the MGW learns the working state of the current home MGC through the heartbeat mechanism between the current home MGC and determines whether the switching needs to be performed.
  • each MGC has the following two states during normal operation: In the case where its mutual-assisted MGC is working normally, the state in which the MGC only controls its own primary MGW is called Mutual help inactive state; in the case of mutual assistance MGC failure, MGC The state in which the master MGW and the standby MGW are controlled is called the mutual assisted state.
  • the MGC can learn the working state of the mutual-assisted MGC through the heartbeat mechanism between the MGCs, and actively perform the state transition between the two states according to the working state of the mutual-assisted MGC; the MGC can also The state transition between the two states is passively performed according to the state transition control command issued by the system network management center.
  • Example 1 Take the different working conditions of MGC1 in Figure 12 as an example.
  • ii MGCl MGC2 is in normal working condition.
  • MGCK MGC2 is in mutual help inactive state
  • MGC1 will perform the following operations in parallel:
  • the heartbeat signal sent by the active MGW is periodically responded to by the primary link, that is, the heartbeat signal is periodically sent to the active MGW, and the active MGW is notified to work normally;
  • each MGC needs to establish an MGW list during the initialization process to record all MGW information to be controlled by the MGC.
  • Each MGC judges whether to accept the registration request reported by the MGW according to its own MGW list. Under normal circumstances, each MGC can maintain its own MGW list by reading the system network management center database.
  • A4 according to the MGW list maintained by the user, processing the registration request reported by the MGW, that is, if the MGW reporting the registration request is in the MGW list maintained by itself, accepting the registration request reported by the MGW, otherwise, rejecting the registration request reported by the MGW;
  • the heartbeat signal is periodically sent to the mutual help MGC with mutual help relationship, and the mutual assistance MGC is notified to work normally;
  • MGW1 and MGW2 belong to MGC1, and MGC1.
  • the interactive control command, MGW3 and MGW4 belong to MGC2, and interact with MGC2 to control commands.
  • MGW1 and MGW2 need to send a heartbeat signal to MGC1 through their own primary link timing, and determine whether MGC1 or its own active link works normally by receiving the heartbeat signal sent back by MGC1.
  • MGW3 and MGW4 need to send a heartbeat signal to MGC2 through their own primary link timing, and determine whether MGC2 or its own active link works normally by receiving the heartbeat signal sent back by MGC2.
  • the MGC1 and MGC2 determine the working state of the other party by the heartbeat signal from the other party.
  • MGC1 is faulty and MGC2 is in normal working condition:
  • MGC1 due to the failure of MGC1, MGC1 will not be able to send the heartbeat signal to MGC2 and to the primary MGW of MGC1, namely MGW1 and MGW2. Therefore, MGW1, MGW2, and MGC2 can judge that the MGC1 has failed by the interruption time of the heartbeat signal.
  • MGW1 and MGW2 When MGW1 and MGW2 detect that the number of heartbeat interruptions sent by MGC1 reaches the pre-configured heartbeat interruption threshold, it will determine that MGC1 is faulty, and the two MGWs will actively send a registration request to the pre-configured backup MGC, that is, MGC2, and Wait for MGC2 to establish a standby link and continue the interaction of control commands.
  • MGC2 When MGC2 detects that the number of heartbeat interruptions sent by MGC1 reaches the pre-configured heartbeat interruption threshold, it will determine that MGC1 is faulty. At this time, MGC2 will transfer from the mutual assist inactive state to the mutual assisted activation state, and the state transition process is required.
  • the MGW configuration data is re-read from the system network management center database, and the backup MGWs, that is, the MGW1 and the MGW2, are added to the MGW list maintained by the system to implement the update of the MGW list. In this way, MGC2 will be able to process the registration requests reported by MGW1 and MGW2.
  • MGC2 moves to the mutual assist activation state.
  • the MGC2 in the mutual-assisted active state determines whether to accept the registration request according to the MGW list maintained by itself, and after receiving the registration request, establishes the The standby link is described, and then control of MGW1 and MG W2 is completed through the alternate link. At this time, MG W 1 and MG W2 will belong to MGC2.
  • the MGC 2 in the mutual assisted active state in addition to performing the operations described in the above al ⁇ a6, will also complete the control command interaction with the standby MGW, that is, the MGW 1 and the MGW 2 through its own standby link, and time.
  • the heartbeat signal is sent back to MGW1 and MGW2, and MGW1 and MGW2 are notified that they are working properly.
  • the MGW1 and the MGW2 may directly initiate the registration request, and the standby link is directly established, and the switching between the MGW1 and the MGW2 from the MGC1 to the MGC2 is initiated.
  • MGW1 and MGW2 are switched from MGC1 to MGC2, they will perform control command interaction with MGC2 through their own alternate link, and will also send a heartbeat signal to MGC2 periodically, and determine by receiving the heartbeat signal sent back by MGC2. Whether the MGC2 or standby link is working properly.
  • MGC1 and MGW3 and MGW4 can complete the switching of MGW3 and MGW4 from MGC2 to MGC1 through the above operations.
  • MGC1 When MGC1 recovers from a fault condition, restarts and completes system initialization, it will first detect the heartbeat signal from MGC2 to select the operating state it will transfer to after recovering from the fault condition.
  • Case 1 If the heartbeat signal sent by MGC2 can be detected, MGC1 will move to the mutual inactive state. Before moving to the mutual help inactive state, MGC1 will read the configuration data of the MGW from the system network management center database, and add its main MGW, that is, MGW1 and MGW2, to the MGW list controlled by itself to complete the update of the MGW list. The MGC will be able to process the registration messages reported by MGW1 and MG W2.
  • the MGC1 After transitioning to the mutual assisted inactive state, the MGC1 will wait for registration requests of MGW1 and MGW2 to prepare to establish the primary link. At the same time, the MGC1 will also resume the heartbeat signal sent to the MGC2 to notify the MGC2 that the current MGC has recovered from the fault. When MGC2 detects the heartbeat signal sent by MGC1, it will transfer from the mutual assisted active state to the mutual assisted inactive state. Before moving to the mutual assisted inactive state, the MGC2 performs the following steps in sequence: bl, traverses the MGW list controlled by the MGC, and obtains the standby MGW in the MGW list by querying the system network management center database;
  • MGC2 can immediately notify its own standby MGW, namely MGW1 and MGW2, by the exit service message when deciding to quit the service, so that MGW1 and MGW2 can know in time that MGC2 will withdraw from the service, and can promptly go to the service.
  • the other MGCs report the registration request, thereby speeding up the switching process of the MGW;
  • step b2 can also be implemented by the heartbeat mechanism between MGC2 and MGW1 and MGW2, that is, after performing step b1, MGC2 stops the heartbeat signal sent back to MGW1 and MGW2, and notifies MGW1 and MGW2 that the MGC does not. Then serve. In this way, MGW1 and MGW2 can judge that MGC2 has exited the service by the interruption time of the heartbeat signal.
  • this method has the disadvantage of being time consuming compared to the method described in step b2.
  • This step effectively avoids the error condition that the standby MGW of MGC2 still reports the registration request to MGC2 and is accepted by MGC2 after receiving the exit service message;
  • step b3 In addition, in order to ensure that the MGC2 can successfully send the exit service message to its own standby MGW, after the execution of step b2, it is preferable to delay the execution of the step b3;
  • the standby MGW of MGC2 that is, the primary MGW of MGC1, MGW1 and MGW2
  • MGW1 and MGW2 receives the MPC2 exit service message
  • the backup link established with MGC2 will be removed, and MGC1 sends a registration request.
  • the MGC1 After receiving the registration request reported by the MGW1 and the MGW2, the MGC1 determines whether to accept the registration request reported by the MGW according to the MGW list maintained by the MGC1, and after receiving the registration request, establishes the primary link to implement the MGW1. And MGW2 switching from MGC2 to MGC1. At this time, the MGW1 and the MGW2 belong to the MGC1.
  • the MGC1 may directly initiate the primary link and wait for the switching of the primary active MGW from the MGC2 to the MGC1 without waiting for the registration request reported by the active MGW. .
  • Case 2 If MGC1 cannot detect the heartbeat signal of MGC2 after the fault is recovered, which indicates that MGC2 has failed at this time, MGC1 will transfer to the mutual assist activation state. Before moving to the mutual assist activation state, MGC1 will first read the configuration data of the MGW from the system network management center database, and add its main MGWs - MGW1 and MGW2 and the standby MGW - MGW3 and MGW4 to the MGW list controlled by itself. The update of the MGW list is completed, so that the MGC 1 will be able to process the registration request reported by its primary MGW and the standby MGW.
  • the MGC1 After moving to the mutual assisted activation state, the MGC1 will wait for the registration request reported by its primary MGW or the standby MGW, MGW1, MGW2, MGW3 or MGW4, to prepare to establish the primary or backup link. After receiving the registration request reported by MGW1, MGW2, MGW3 or MGW4, MGC1 will accept the registration request and establish the primary link or backup link to resume control of MGW1, MGW2, MGW3 or MGW4.
  • the MGC1 may directly establish the primary link or the standby link without waiting for the registration request reported by the MGW1 MGW2 MGW3 or the MGW4.
  • the control command interaction with the MGW3 and the MGW4 is completed through the standby link, and the heartbeat signals are periodically sent back to the MGW3 and the MGW4 to notify the MGW3 and the MGW4 that the current MGC1 is working normally.
  • the MGC passively performs the state transition between the mutual assisted inactive state and the mutual assisted active state according to the state transition command of the system network management center
  • the operations performed by the MGC1, the MGC2, and the MGW1, the MGW2, the MGW3, and the MGW4 during the state transition The operations performed by MGC1, MGC2, and MGW1, MGW2, MGW3, and MGW4 in the three cases described in the above Example 1 are exactly the same, and will not be described in detail herein.
  • the method adds a heartbeat mechanism between the MGW and the MGC to which it belongs to the MGC, and ensures that the fault is caused by a failure or an unexpected power failure of the MGC.
  • the MGW can still implement switching to other MGCs, thereby effectively avoiding the problems of the prior art.
  • MGC1 when MGC1 recovers from a fault condition, it will directly enter the mutual assisted state or the mutual assisted inactive state, attempting to activate the control of its own active MGW.
  • the active MGW of the current MGC1 is being controlled by the MGC2 and the traffic may be large, if the MGW dual-homing switching is performed at this time, a large amount of call loss is bound to occur.
  • the present example improves the method described in the example 1, and adds a mutual assisted idling state in the working state of the original MGC.
  • the mutual assisted idling state means that, in this state, the MGC cannot control any MGW, whether it is the primary MGW or the standby MGW.
  • the method described in this example further sets that the MGC can only enter the mutual assisted air transition state after restarting the initialization, and cannot directly enter the mutual assisted active state or the mutual assisted inactive state. Moreover, the MGC in the mutual assisted air transition state can complete the transition from the mutual assisted idle state to the mutual assisted inactive state or the mutual assisted active state according to the state transition control signal issued by the system network management center.
  • the system network management center can select an appropriate switching opportunity according to the traffic volume between the active MGW currently in the mutual assisted air transition MGC and the MGC to which the MGW currently belongs.
  • the system network management center sends a state transition control command to the MG in the mutual assisted air transition state, so that it initiates a state transition from the mutual assist idle state to the mutual help inactive state or the mutual assisted active state.
  • the MGC Before moving to the mutual assisted active state, the MGC will still perform the operation performed when the MGC1 described in Example 1 recovers from the fault state, and implement the switching of the MGW.
  • MGC1 after MGC1 recovers from the fault state, it will directly enter the mutual assisted air-to-air state, and the system network management center will detect the traffic between the MGC2 and the MGC1's primary MGW, MGW1 and MGW2, and in the service. When the amount is small, the MGC1 is transferred from the mutual aid to the idle state to help the inactive or mutual assisted state, and then take over its own primary MGW.
  • the restarted MGC first enters the mutual assist idle state, and according to the state transfer control command issued by the system network management center, the traffic between the MGW to be switched and the MGC to which it belongs is small.
  • the method of state transfer at the time effectively avoids the call loss situation.
  • the MGC in the mutual assisted vacant state can also determine the working state of the mutual-assisted MGC by detecting the heartbeat signal sent by the mutual-assisted MGC, thereby automatically completing the mutual assisted idle state or the mutual assisted active state or mutual helpless Transfer of the active state.
  • the MGC in the mutual assisted idling state detects the heartbeat signal sent by the mutual-assisted MGC, it determines that the mutual-assisted MGC works normally, and will directly transfer to the mutual-assisted inactive state, taking over its own active MGW;
  • the MGC detects that the number of heartbeat interruptions sent by the mutual-assisted MGC is greater than or equal to the set heartbeat interruption threshold, it determines that the mutual assistance MGC failure will directly transfer to the mutual-assisted activation state, taking over its own primary and backup MGW.
  • both MGCs will determine the other party through the interruption of the heartbeat signal.
  • the fault at this time, the two MGCs will simultaneously transfer to the mutual assisted state, that is, the "double live" situation occurs.
  • both MGCs with mutual assistance will attempt to take over the MGWs belonging to the two MGCs, causing the MGW to fail to confirm the currently owned MGC.
  • the registration of the MGW has been confusing.
  • the method described in this example improves the method of Example 1, so that the MGW sends a heartbeat signal to its own primary MGC in any case, and selects according to the heartbeat signal returned by the primary MGC.
  • the home MGC that currently interacts with its own control commands.
  • the method for selecting the home MGC is: the MGW detects the heartbeat signal returned by the master MGC in real time, and if it can receive the heartbeat signal sent back by the primary MGC, determines that the primary MGC is the current home MGC; if the primary MGC returns the heartbeat If the number of signal interruptions is greater than or equal to the heartbeat interruption threshold set by the system, it is determined that the backup MGC is the current home MGC. In this way, even if there is a "double live" situation, it can ensure that the MGW is preferentially registered to its primary MGC.
  • MGCs of MGW1 and MGW2 are MGCl
  • MGCs of MGW3 and MGW4 are MGC2.
  • MGW1 and MGW2 will select the MGC1 interactive control command without being controlled by MGC2.
  • MGW3 and MGW4 will select the MGC2 interactive control command without being affected by MGC1. control.
  • MGW1 and the MGW2 have been switched to the MGC2
  • the two MGWs still need to periodically send a heartbeat signal to the MGC1
  • the state of the MGC1 is monitored in real time, and therefore, once the MGC1 returns to normal, the MGC1 echo is detected in the two MGWs.
  • MGC1 will be determined to be their home MGC, and will be actively switched back to MGC1.
  • MGW1 and MGW2 will choose to interact with the MGC1 control command without being controlled by MGC2.
  • the MGW can monitor the status of the active MGC in real time, and set the current home MGC according to the status of the primary MGC, which can effectively avoid the possibility of "double live".
  • the problem of MGW registration confusion has further improved the dual-homing function of MGW.
  • the problem of data consistency is also involved, how to ensure the primary core control device and the standby core control device The data consistency between the backups.
  • all configuration data on the switched core control device can support the continuity of the MGW link connection and service processing.
  • the core control device of the party the core control device with the dual-homing relationship with the core control device of the party is called the peer core control device. Then, the core control device of the party must first obtain and manage the data of the peer core control device, so as to use the data to control the device controlled by the core control device and take over the service of the other party.
  • the core control device of the other party sends its data to the core control device of the party at regular intervals, or the core control device of the party reaches the core control device of the other party at regular intervals.
  • the data is read in; then, the data information of the other party is saved in the database of the core control device and the core control device of the other party respectively.
  • the method for the core control device of the party to store the data of the core control device of the other party is as follows:
  • the media gateway device configuration table, the console configuration information table, the MTP link table, the M3UA link table, the IUA link table, the V5UA link table, the M2UA chain is added to the routing table, the V5 interface configuration table, the gateway domain name distribution, the SIP device registration information table, and the H323 device registration information table to distinguish whether each record in each table is the data of the core control device of the party or the other party.
  • the data of the core control device is a soft switch.
  • the same table in the core control device of the other party is re-established on the core control device and the core control device of the other party.
  • the core control device of the other party fails due to a failure or the like, the core of the core is directly used.
  • the table of the other party's core control device on the control device establishes the service of the other party's core control device and controls the device controlled by the other party's core control device.
  • the data of the core control device and the core control device of the other party can also be placed in a shared database, and the shared database can be placed in a separate server, and the core control device can read the database.
  • the core control device of the other party fails due to a failure or the like, the data in the shared database is directly used to establish the service of the core control device of the other party and control the device controlled by the peer core control device.
  • the following describes the process in which the core control device of the present party takes over the service of the core control device of the other party.
  • the status bit of the peer core control device is set in the core control device of the party, and the status bits of the peer core control device are: a normal state and a failure state.
  • the status bit of the counterpart core control device may change when the core control device of the party is started, or when the state of the counterpart core control device changes. For example, when the core control device of the local device is started, the status bit of the other core control device is set to a normal state; when the core control device of the own party fails to shake hands with the other core control device, the core control device of the other party is invalid, and the core control of the other party is controlled.
  • the status bit of the device is set to the failed state.
  • the status bit of the core control device of the other party may be first set to a normal state, thereby ignoring the data of the dual-homed flag bit being the identity of the core control device of the other party, so that the core control device of the party does not
  • the communication service related to the core control device of the other party is processed; the core control device of the party only manages and processes the data managed by itself, and processes the communication service according to the data.
  • the core control device of the party can receive and store the data with the core control device of the other party, but does not process the related service according to the data. .
  • the data processing process proposed by the present invention includes the following steps:
  • Step 1301 During the operation of the core control device of the party, the core control device of the party obtains data of the peer core control device.
  • Step 1302 Determine whether the core control device of the other party is normal. If it is normal, return to step 1301. Otherwise, step 1303 is performed.
  • judging whether the core control device of the other party is normal can be judged by the handshake mechanism, that is, the core control device of the party performs a handshake with the core control device of the other party at a specific time. If the handshake is successful, the core control device of the other party is normal, and the other party is The flag of the core control device is set to the normal state. Otherwise, it indicates that the core control device of the other party is invalid, and the flag of the other core control device is set to the invalid state.
  • Step 1303 When the core control device flag of the other party is invalid, the core control device of the core takes over the service of the core control device of the other party according to the data of the core control device of the other party, and controls the device of the core control device of the other party.
  • the core control device of the party establishes related services according to the data of the core control device of the other party, and runs the established service and controls the device related to the data of the core control device of the other party.
  • Step 1304 Determine whether the core control device of the other party returns to normal. If the operation returns to normal, go to step 1305. Otherwise, continue to step 1303.
  • Step 1305 The core control device of the party removes the related service according to the data of the core control device of the other party, and the service is returned to the core control device of the other party, and then returns to step 1301 to obtain the data of the core control device of the opposite party.
  • the core control device and the core control device of the other party are relatively speaking.
  • the above describes the process in which the core control device of the other party takes over the core control device of the other party when the core control device of the other party fails.
  • the process of taking over the core control device by the other core control device is exactly the same as the above process.
  • this solution can be applied to the case of single-homing.
  • the core control device of the party fails, the other core control device will take over the various services of the core control device of the other party, and when the other core control device fails, this solution The party core control device does not take over the business of the other core control device.
  • the present invention can also be applied to the case of multi-homing.
  • the core control device of the party fails, according to a certain strategy, the other core control device will take over various services of the core control device of the own party, and the core control of any other party.
  • the equipment fails, it can also be taken over by the core control equipment of the party. The business of the failed core control device.
  • FIG. 14 is a structural structure of a device for performing data processing in a core control device, and the device shown in FIG. 14 can be located at the core control device or the counterpart core control device of the present invention.
  • the display device includes: a storage unit that stores data of the counterpart core control device, a detection unit, an acquisition unit, a takeover unit, and a removal unit.
  • the storage unit is connected to the acquiring unit and configured to store data of the counterpart core control device acquired by the acquiring unit.
  • the detecting unit is connected to the core control device, the takeover unit and the dismantling unit of the opposite party, and is configured to detect the state of the core control device of the opposite party, and notify the takeover unit and the removal unit of the detected state of the core control device.
  • the obtaining unit is connected to the core control device and the storage unit, and is configured to acquire data of the core control device of the other party, and store the acquired data in the storage unit.
  • the take-over unit is connected to the detecting unit and the storage unit, and is configured to take over the service of the core control device of the other party and control the data of the counterpart core control device stored in the storage unit when the detecting unit detects that the state of the core control device of the other party is a failed state. The device controlled by the other party's core control device.
  • the removing unit is connected to the detecting unit and the storage unit, and is configured to: when the detecting unit detects that the core control device of the other party changes from a failure state to a normal state, the core control device is taken over according to the data of the counterpart core control device stored in the storage unit.
  • the other party's core control equipment business the business is handed over to the other core control equipment.
  • the composition of the data processing device in a core control device i.e., the single-homing scenario
  • the functions of the components and parts of the core control device of the other party are the same as those of the core control devices of the other party.
  • the components of each of the core control devices and the functions of the various components are the same as the core control devices of the single-homed scenario.
  • the data consistency scheme proposed by the present invention can recover the communication service of the failed core control device in time through the dual-homed data processing scheme when the core control device of any one fails due to a failure or the like, therefore, the scheme
  • the communication system itself has a strong self-healing capability.
  • two softswitches work in load-sharing mode, that is, two softswitches process services simultaneously under normal conditions.
  • Data such as signaling and relay can implement the backup function of the service.
  • two softswitches of mutual assistance access the NGN network at the same time.
  • the softswitch in the area 1 fails, the softswitch service can be switched to the softswitch in the area 2 by manual/automatic switching, and the NGN service is undertaken by the softswitch of the area 2. .
  • the dual-homing control mechanism of softswitch is mainly composed of two parts: one is the dual-homing mechanism controlled by the gateway, and the other is the dual-homing mechanism of service control.
  • the networking mode is shown in Figure 15: Two load-sharing softswitches are in physical They can be located in different geographical areas. They are represented on the group network as two independent exchanges. That is to say, in the case that one of the softswitches fails, the other softswitch also assumes the gateway control of the two exchanges. With business control features.
  • a heartbeat link is configured between the two softswitches, and the heartbeat communication can be performed by using a private protocol or a standard protocol, and is used to detect whether the peer softswitch works normally.
  • Each mutual-assisted softswitch is configured with both its master-controlled gateway device data and its slave-controlled gateway device data, and each gateway device and packet terminal, such as H.323 Phone, OpenEye, etc. are also configured with information about their primary home softswitch and secondary softswitch. In this way, when a softswitch fails or performs dual-homed switching, the gateway device controlled by the softswitch will automatically re-register to the slave softswitch or re-register to the slave soft-software command. Exchange.
  • Dual-homing mechanism for service control unified planning of local number first set, call source code, billing source code, user number segment, routing number, routing code, trunk group number, call prefix between two mutual softswitches
  • the equal-office data and the user data enable both softswitches to take over all services of the peer softswitch in the event of dual-homed switching. Before and after the switchover, all users' call, billing and other attributes are not affected.
  • the system is configured with a unified network management to centrally manage all the components in the network to ensure that the office data or user data of the two softswitches can be consistent or coordinated.
  • the switching method can be divided into manual mode and automatic mode: Manual switching mode refers to when a softswitch is in a mutual working mode. In this case, the mutual assistance status of the softswitch can be changed only after the maintenance personnel issue a switching operation command to the maintenance system through the terminal system or the network management system.
  • the automatic switching mode means that when a softswitch is in the mutual working mode, the softswitch automatically determines whether to change its mutual assistance state according to the state of the heartbeat link between the softswitch and the mutual softswitch.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Safety Devices In Control Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Hardware Redundancy (AREA)
  • Small-Scale Networks (AREA)
  • Telephonic Communication Services (AREA)

Abstract

L'invention concerne un procédé de réalisation d'une double inscription consistant à régler, d'une part, un des deux dispositifs de commande centraux pour qu'ils supportent respectivement et, d'autre part, une entité de réseau rattachée à un dispositif de commande central à connecter aux deux dispositifs de commande centraux via une liaison principale et une liaison de secours. Ce procédé consiste (a1) à activer la liaison principale connectée au dispositif de commande central et à interrompre la liaison de secours connectée au dispositif de commande central, (b1) à évaluer si le dispositif central correspondant à la liaison principale subit une défaillance, si tel est le cas, à activer la liaison de secours, si tel n'est pas le cas, à retourner à l'étape (b1). Un autre procédé de réalisation d'une double inscription permet d'accroître le taux d'utilisation d'un dispositif de commande central, tandis que la fiabilité du réseau est garantie, et d'effectuer une commutation en douceur entre les dispositifs avec une relation de double inscription et d'augmenter la fiabilité du réseau.
PCT/CN2005/001345 2004-08-29 2005-08-29 Procede de realisation d'une double inscription WO2006024225A1 (fr)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP05781860A EP1777893A4 (fr) 2004-08-29 2005-08-29 Procede de realisation d'une double inscription
AU2005279575A AU2005279575B2 (en) 2004-08-29 2005-08-29 A method for implementing dual-homing
BRPI0514699-2A BRPI0514699B1 (pt) 2004-08-29 2005-08-29 Método, sistema e peça de equipamento para implementação de homing duplo
US11/709,263 US8116760B2 (en) 2004-08-29 2007-02-22 Method for implementing dual-homing
US13/350,261 US8571546B2 (en) 2004-08-29 2012-01-13 Method for implementing dual-homing

Applications Claiming Priority (10)

Application Number Priority Date Filing Date Title
CN200410076730 2004-08-29
CN200410076730.6 2004-08-29
CN200510064728.1 2005-04-18
CNB2005100647281A CN1327727C (zh) 2005-04-18 2005-04-18 一种媒体网关双归属的实现方法
CN2005100776102A CN1882107B (zh) 2005-06-17 2005-06-17 一种在下一代网络中实现信令网关双归属的方法
CN200510077610.2 2005-06-17
CN200510035480.6 2005-06-21
CNB2005100354806A CN100459738C (zh) 2005-06-21 2005-06-21 控制和承载分离网络中的双归属实现方法
CN 200510087133 CN1905474A (zh) 2005-07-26 2005-07-26 一种实现双归属的方法和系统
CN200510087133.8 2005-07-26

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US11/709,263 Continuation US8116760B2 (en) 2004-08-29 2007-02-22 Method for implementing dual-homing

Publications (1)

Publication Number Publication Date
WO2006024225A1 true WO2006024225A1 (fr) 2006-03-09

Family

ID=35999702

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2005/001345 WO2006024225A1 (fr) 2004-08-29 2005-08-29 Procede de realisation d'une double inscription

Country Status (5)

Country Link
US (2) US8116760B2 (fr)
EP (1) EP1777893A4 (fr)
AU (1) AU2005279575B2 (fr)
BR (1) BRPI0514699B1 (fr)
WO (1) WO2006024225A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100450035C (zh) * 2006-08-16 2009-01-07 华为技术有限公司 一种双归属设备管理系统和双归属数据配置回滚的方法
RU2655648C1 (ru) * 2014-09-29 2018-05-29 Телефонактиеболагет Лм Эрикссон (Пабл) ПОЛУЧЕНИЕ Pсмах ПРИ ДВОЙНОМ СОЕДИНЕНИИ

Families Citing this family (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8886831B2 (en) * 2006-04-05 2014-11-11 Cisco Technology, Inc. System and methodology for fast link failover based on remote upstream failures
CN101836404B (zh) * 2007-11-02 2016-06-01 美国博通公司 移动无线通信架构
EP2141859B1 (fr) 2008-06-30 2012-08-29 Alcatel Lucent Fermeture d'un contrôleur de passerelle de média
US8300523B2 (en) * 2008-07-28 2012-10-30 Cisco Technology, Inc. Multi-chasis ethernet link aggregation
JP5042248B2 (ja) * 2009-01-22 2012-10-03 株式会社日立製作所 移動体通信システム、呼制御サーバ及びアクセスゲートウェイ装置
US8428021B2 (en) * 2009-05-14 2013-04-23 Avaya, Inc. Architecture using inexpensive, managed wireless switching points to deliver large scale WLAN
CN101674495B (zh) * 2009-10-20 2015-06-03 中兴通讯股份有限公司 数据容灾预处理方法及装置
JP5537667B2 (ja) * 2009-11-23 2014-07-02 アルカテル−ルーセント ハンドオフの維持のためのシステムおよび方法
US8510409B1 (en) * 2009-12-23 2013-08-13 Emc Corporation Application-specific outbound source routing from a host in a data network
US20110235505A1 (en) * 2010-03-29 2011-09-29 Hitachi, Ltd. Efficient deployment of mobility management entity (MME) with stateful geo-redundancy
US8416775B2 (en) * 2010-05-19 2013-04-09 Juniper Networks, Inc. Systems and methods for equal-cost multi-path virtual private LAN service
US8750093B2 (en) * 2010-08-17 2014-06-10 Ubeeairwalk, Inc. Method and apparatus of implementing an internet protocol signaling concentrator
IL209250A0 (en) * 2010-11-11 2011-01-31 Eci Telecom Ltd Technology for managing traffic via dual homed connections in communication networks
US9189347B2 (en) 2011-07-29 2015-11-17 Motorola Solutions, Inc. High reliability redundant voting system for a signal received by voting processors in a communication system
KR20130086823A (ko) * 2012-01-26 2013-08-05 삼성전자주식회사 Ｉｐ기반의 베어러 독립 호 제어 환경에서 장애감지를 위한 방법 및 장치
CN108601043B (zh) 2012-09-28 2022-01-14 瞻博网络公司 用于控制无线接入点的方法和设备
US9231820B2 (en) 2012-09-28 2016-01-05 Juniper Networks, Inc. Methods and apparatus for controlling wireless access points
CN102970700A (zh) * 2012-11-13 2013-03-13 中兴通讯股份有限公司 根据注册网关数量进行双归属自动倒换判决方法及系统
US10445758B1 (en) 2013-03-15 2019-10-15 Allstate Insurance Company Providing rewards based on driving behaviors detected by a mobile computing device
US9954906B2 (en) * 2015-03-27 2018-04-24 At&T Intellectual Property I, L.P. Method and system for providing media services in a communication system
CN106656580B (zh) * 2016-11-29 2020-06-26 华为技术有限公司 一种业务状态的迁移方法及装置
CN109787795B (zh) * 2017-11-13 2020-12-25 比亚迪股份有限公司 列车网络主节点故障的处理方法、节点及电子设备
CN112787840B (zh) * 2019-11-11 2022-07-22 华为技术有限公司 一种实现业务功能部署的方法、装置和系统
CN111083198B (zh) * 2019-11-22 2022-07-05 浙江中控技术股份有限公司 通信链路的切换方法、主域服务器、从域服务器及系统
CN111835555A (zh) * 2020-06-03 2020-10-27 视联动力信息技术股份有限公司 数据恢复方法、装置及可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6219546B1 (en) * 1998-07-22 2001-04-17 Ericsson Inc. System and method of reallocating satellite gateways in a radio telecommunications network
WO2002051078A2 (fr) * 2000-12-20 2002-06-27 Nortel Networks Limited Interface de reserve pour reseau du type open shortest path first (ospf)
CN1390035A (zh) * 2001-06-05 2003-01-08 华为技术有限公司 设置多链路捆绑用户服务器组的方法
US6662308B1 (en) 1999-12-21 2003-12-09 Lucent Technologies Inc. Dual-homing select architecture

Family Cites Families (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5375161A (en) * 1984-09-14 1994-12-20 Accessline Technologies, Inc. Telephone control system with branch routing
FR2735851B1 (fr) 1995-06-23 1997-08-01 Valeo Thermique Moteur Sa Condenseur a reservoir integre pour installation de climatisation de vehicule automobile
US5831969A (en) * 1996-06-28 1998-11-03 Lucent Technologies Inc. ISDN D channel restoration without loss of signaling or packet data
FI109757B (fi) * 1997-06-23 2002-09-30 Nokia Corp Menetelmä, laiterekisteri ja järjestelmä päätelaitteiden käytön rajoittamiseksi
US6876634B1 (en) * 1997-11-26 2005-04-05 Lg Information & Communications, Ltd. Architecture of mobile communication systems network and method for transmitting packet data using the same
FI108599B (fi) * 1999-04-14 2002-02-15 Ericsson Telefon Ab L M Toipuminen matkaviestinjärjestelmissä
US6885658B1 (en) * 1999-06-07 2005-04-26 Nortel Networks Limited Method and apparatus for interworking between internet protocol (IP) telephony protocols
US6515985B2 (en) * 2000-02-08 2003-02-04 Airslide Systems Ltd. Convergence of telephone signaling, voice and data over a packet-switched network
US7342873B1 (en) 2000-06-06 2008-03-11 Lucent Technologies Inc. Efficient architectures for protection against network failures
JP2002084363A (ja) * 2000-09-06 2002-03-22 Nec Corp ゲートウェイシステム及びそれに用いる回線制御方法
US20020152320A1 (en) * 2001-02-14 2002-10-17 Lau Pui Lun System and method for rapidly switching between redundant networks
US20020118686A1 (en) 2001-02-26 2002-08-29 Sudeep Gupta Multi-homing proxy apparatus, and associated method, for digital communication network
JP2002290551A (ja) 2001-03-28 2002-10-04 Nec Corp ゲートウェイシステム及びそれに用いる障害処理方法
CN100459722C (zh) 2001-10-08 2009-02-04 艾利森电话股份有限公司 在电信系统中管理呼叫的方法和系统
CN1423458A (zh) 2001-11-30 2003-06-11 深圳市中兴通讯股份有限公司 一种ip网中实现信令链路冗余备份的方法
CN1278517C (zh) 2002-05-27 2006-10-04 华为技术有限公司 实现宽窄带信令网互通的全分布式管理方法
CN1208934C (zh) 2002-05-27 2005-06-29 华为技术有限公司 实现宽窄带信令网互通的一种方法
US7023977B2 (en) 2002-12-16 2006-04-04 Alcatel Method and system for providing softswitch failure protection in a communication network
CN1536819B (zh) 2003-04-11 2010-08-04 华为技术有限公司 下一代网络中双归属的实现方法
CN1198407C (zh) 2003-07-08 2005-04-20 大唐移动通信设备有限公司 通信系统中实现高可用性（ha）的装置和方法
WO2005025143A1 (fr) 2003-09-05 2005-03-17 Utstarcom (China) Co. Ltd. Procede de detection d'etat de controleur de passerelle media par une passerelle media
CN1258935C (zh) 2003-11-12 2006-06-07 中兴通讯股份有限公司 移动软交换网络的容灾方法
CN100574486C (zh) 2004-08-29 2009-12-23 华为技术有限公司 通信网络中双归属组网的系统及其方法
CN1893684A (zh) 2005-07-08 2007-01-10 华为技术有限公司 控制和承载分离网络中的双归属实现方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6219546B1 (en) * 1998-07-22 2001-04-17 Ericsson Inc. System and method of reallocating satellite gateways in a radio telecommunications network
US6662308B1 (en) 1999-12-21 2003-12-09 Lucent Technologies Inc. Dual-homing select architecture
WO2002051078A2 (fr) * 2000-12-20 2002-06-27 Nortel Networks Limited Interface de reserve pour reseau du type open shortest path first (ospf)
CN1390035A (zh) * 2001-06-05 2003-01-08 华为技术有限公司 设置多链路捆绑用户服务器组的方法

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100450035C (zh) * 2006-08-16 2009-01-07 华为技术有限公司 一种双归属设备管理系统和双归属数据配置回滚的方法
RU2655648C1 (ru) * 2014-09-29 2018-05-29 Телефонактиеболагет Лм Эрикссон (Пабл) ПОЛУЧЕНИЕ Pсмах ПРИ ДВОЙНОМ СОЕДИНЕНИИ
US10412689B2 (en) 2014-09-29 2019-09-10 Telefonaktiebolaget Lm Ericsson (Publ) Deriving PCMAX in dual connectivity

Also Published As

Publication number Publication date
US8116760B2 (en) 2012-02-14
US8571546B2 (en) 2013-10-29
AU2005279575B2 (en) 2009-05-21
US20070183347A1 (en) 2007-08-09
AU2005279575A1 (en) 2006-03-09
EP1777893A4 (fr) 2007-11-07
US20120106318A1 (en) 2012-05-03
EP1777893A1 (fr) 2007-04-25
BRPI0514699B1 (pt) 2019-04-09
BRPI0514699A (pt) 2008-06-17

Similar Documents

Publication Publication Date Title
WO2006024225A1 (fr) Procede de realisation d'une double inscription
US7894410B2 (en) Method and system for implementing backup based on session border controllers
CN101365169B (zh) 路由控制的实现方法、系统、媒体网关及媒体网关控制器
CN100574486C (zh) 通信网络中双归属组网的系统及其方法
WO2003047156A1 (fr) Procede de sauvegardes redondantes de liaisons de signaux dans un reseau ip
WO2007000094A1 (fr) Procede pour effectuer un raccordement a double anneau de central de commutation mobile
EP2140670B1 (fr) Mise en oeuvre d'une solution de services d'urgence
WO2010034147A1 (fr) Procédé de réalisation sans déconnexion de passerelle de jonction à tolérance de sinistre, système et passerelle de support
JP5309350B2 (ja) 移動体通信ゲートウェイ装置及び移動体通信ゲートウェイ制御方法
WO2006136075A1 (fr) Procédé pour implémenter une double appartenance dans la séparation entre le réseau de contrôle et le réseau de relèvement
WO2007006198A1 (fr) Procédé de réalisation de guidage double dans un réseau avec contrôle et orientation séparés
CN112653661B (zh) 一种VoIP网络限制下的媒体恢复方法和系统
KR101369103B1 (ko) 접속 해제 처리 방법 및 접속 해제 처리 장치
US20130185409A1 (en) Method and system for determining ip bearer optimization based on virtual media gateway
WO2006136098A1 (fr) Procédé de traitement d’appel
WO2009070958A1 (fr) Procédé et dispositif de détection d'échec de circuit de jonction de plan utilisateur, de détection de récupération et d'établissement de rapport de celle-ci
WO2008151539A1 (fr) Procédé, système et dispositif pour commander un contrôleur de session en périphérie doublement attributif
CN103138998B (zh) 一种代理状态检测方法、装置和系统
CN101808136B (zh) 一种实现用户动态资源同步的方法、装置及系统
CN100428825C (zh) 双归属系统中业务倒换/倒回时恢复业务数据的方法
JP2006033004A (ja) 通信装置、呼処理制御装置および通信システム
WO2013189185A1 (fr) Procédé, dispositif et système de commutation lors d'une reprise après catastrophe
WO2008064601A1 (fr) Procédé de réalisation de connexion à double anneau, système et équipement de commutation logicielle
WO2007137515A1 (fr) Système et procédé permettant au contrôleur de passerelle média (mgc) d'obtenir le statut de support, passerelle média (mgw) et mgc
CN101166078A (zh) 一种双归属软交换设备及实现网关与软交换链路故障切换方法及系统

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU LV MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 11709263

Country of ref document: US

REEP Request for entry into the european phase

Ref document number: 2005781860

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2005781860

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2005279575

Country of ref document: AU

WWE Wipo information: entry into national phase

Ref document number: 942/CHENP/2007

Country of ref document: IN

ENP Entry into the national phase

Ref document number: 2005279575

Country of ref document: AU

Date of ref document: 20050829

Kind code of ref document: A

WWP Wipo information: published in national office

Ref document number: 2005279575

Country of ref document: AU

ENP Entry into the national phase

Ref document number: 2007110854

Country of ref document: RU

Kind code of ref document: A

WWP Wipo information: published in national office

Ref document number: 2005781860

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 11709263

Country of ref document: US

ENP Entry into the national phase

Ref document number: PI0514699

Country of ref document: BR