US7577090B2 - Method and system for providing availability and reliability for a telecommunication network entity - Google Patents

Method and system for providing availability and reliability for a telecommunication network entity Download PDF

Info

Publication number
US7577090B2
US7577090B2 US10/597,950 US59795005A US7577090B2 US 7577090 B2 US7577090 B2 US 7577090B2 US 59795005 A US59795005 A US 59795005A US 7577090 B2 US7577090 B2 US 7577090B2
Authority
US
United States
Prior art keywords
network
entity
call server
over
network entity
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related, expires
Application number
US10/597,950
Other languages
English (en)
Other versions
US20070165516A1 (en
Inventor
Jianming Xu
Charles Marvin Berteau
Ghassan Naim
Seshagiri Rao Madhavapeddy
Pardeep Kohli
Shiang Yueng Feng
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alcatel Lucent SAS
Sound View Innovations LLC
Original Assignee
Alcatel Lucent USA Inc
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
Application filed by Alcatel Lucent USA Inc filed Critical Alcatel Lucent USA Inc
Publication of US20070165516A1 publication Critical patent/US20070165516A1/en
Assigned to ALCATEL USA MARKETING, INC. reassignment ALCATEL USA MARKETING, INC. MERGER (SEE DOCUMENT FOR DETAILS). Assignors: ALCATEL WIRELESS, INC.
Assigned to ALCATEL-LUCENT USA INC. reassignment ALCATEL-LUCENT USA INC. MERGER (SEE DOCUMENT FOR DETAILS). Assignors: ALCATEL USA MARKETING, INC.
Application granted granted Critical
Publication of US7577090B2 publication Critical patent/US7577090B2/en
Assigned to SOUND VIEW INNOVATIONS, LLC reassignment SOUND VIEW INNOVATIONS, LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ALCATEL LUCENT
Assigned to NOKIA OF AMERICA CORPORATION reassignment NOKIA OF AMERICA CORPORATION CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: ALCATEL-LUCENT USA INC.
Assigned to ALCATEL LUCENT reassignment ALCATEL LUCENT NUNC PRO TUNC ASSIGNMENT (SEE DOCUMENT FOR DETAILS). Assignors: NOKIA OF AMERICA CORPORATION
Expired - Fee Related legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
    • G06F11/2038—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant with a single idle spare processing component
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
    • G06F11/2023—Failover techniques
    • G06F11/2028—Failover techniques eliminating a faulty processor or activating a spare
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/22—Arrangements for detecting or preventing errors in the information received using redundant apparatus to increase reliability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/22—Alternate routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
    • 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
    • H04Q—SELECTING
    • H04Q3/00—Selecting arrangements
    • H04Q3/0016—Arrangements providing connection between exchanges
    • H04Q3/0025—Provisions for signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q3/00—Selecting arrangements
    • H04Q3/0016—Arrangements providing connection between exchanges
    • H04Q3/0062—Provisions for network management
    • H04Q3/0075—Fault management techniques
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
    • G06F11/2048—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant where the redundant components share neither address space nor persistent storage
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/14—Monitoring arrangements

Definitions

  • the present disclosure relates generally to a method and system for a telecommunications network entity and, more particularly, to a method and system for providing redundancy in a telecommunications network entity.
  • a network entity e.g., a serving entity
  • a switch In telecommunication systems, the performance of a network entity (e.g., a serving entity) such as a switch may be judged by its availability and redundancy capabilities. Generally, such systems are designed to operate with the full capacity of such serving entities available at all times. Taking a telecommunication switch as an example, certain components may be rendered to failure, and may reduce the capability of the switch to support a full load of traffic at which the switch is designed to handle. This problem may lead to the disconnection of a certain number of users who are using the switch during a call and may prevent a certain number of new users from making new calls. This problem may result in a lack of availability of services in emergency situations that affect whole geo-locations, such as natural disasters (e.g., an earthquake, tsunami, etc.).
  • natural disasters e.g., an earthquake, tsunami, etc.
  • the longer the down time of the telecommunications network the larger the financial losses to the network operator and the higher the impact on the human lives in our society. Accordingly, the operational abilities of a serving entity are important in the network because it aids in defining the reliability factor of a communication between two parties, and its failure may lead to the loss of calls and data information.
  • FIG. 1 A known network configuration of a partial solution for providing redundancy of a network entity is illustrated in FIG. 1 .
  • the network 100 illustrated in FIG. 1 includes redundancy protection by duplicating all the hardware and software of an active main entity 110 , and installing a standby redundant or duplicate entity 120 in relatively close proximity to the active main entity 110 .
  • the active main entity 110 and standby redundant entity 120 are generally in the same physical location 160 , such as in the same building and connected by a private local area network 130 . If the active main entity 110 becomes inoperative, e.g. unable to function properly, the redundant entity 120 becomes active and takes over all the services.
  • this solution may be unworkable in the event of a natural disaster that affects the entire location 1 . It is also relatively expensive given that a network operator has to purchase twice the amount of hardware and software for the functionality of a single entity.
  • this solution does not efficiently handle partial failure of the active main entity 110 .
  • the known solution is to completely shutdown the active main entity 110 and activate the redundant entity 120 .
  • this is not an efficient solution given that all the components that did not fail in the main active entity 110 become non-useable after the service is switched to the redundant entity 120 .
  • redundant trunks also need to be provided at the redundant entity 120 with alternate routes. This redundancy further increases the operational costs and complexity in network design.
  • the present invention provides for geographical redundancy between a first network entity at a first location and a second network entity at a second location.
  • the two locations are separated by sufficient distance so that natural disasters or other events that affect one location will most likely not affect the other location.
  • Each network entity transmits a primary heartbeat or status message over an IP network on a periodic basis. If no primary heartbeat message has been received from a network entity after a certain configurable time period, then a secondary heartbeat or status message can be transmitted over a signaling network, such as an SS7 network, on a periodic basis. If there is still no response from the first active network entity after a certain configurable time period, a switchover of traffic control from the first network entity to the second network entity can be initiated.
  • a signaling network such as an SS7 network
  • Partial switchover from the first network entity to the second network entity is also provided when the first network entity is only partially inoperative, e.g. when only one specific type of card has become inoperative.
  • the first network entity transmits a message over the IP network to the second network entity to initiate switchover to the same specific type of card in the second network entity.
  • the first network entity then informs the other cards in the first network entity to redirect messages to the same specific type of card in the second network entity.
  • FIG. 1 illustrates an example of a known solution for providing redundancy of a network entity.
  • FIG. 2 a illustrates one embodiment of a network architecture for providing geographical redundancy in a telecommunications system in accordance with the present invention.
  • FIG. 2 b illustrates one embodiment of an exemplary call server in the network architecture of FIG. 2 a.
  • FIG. 2 c illustrates another embodiment of an exemplary call server in the network architecture of FIG. 2 a.
  • FIG. 3 a illustrates an exemplary call establishment phase for a mobile to land call within the network architecture of FIG. 2 .
  • FIG. 3 b illustrates an exemplary call answer phase for a mobile to land call within the network architecture of FIG. 2 .
  • FIG. 4 a illustrates an exemplary switchover process when the main call server is unavailable.
  • FIG. 4 b illustrates an exemplary call establishment phase for a mobile to land call within the network architecture of FIG. 2 when the main call server is unavailable.
  • FIG. 4 c illustrates an exemplary call answer phase for a mobile to land call within the network architecture of FIG. 2 when the main call server is unavailable.
  • FIG. 5 a illustrates an exemplary partial switchover process when only a portion of the main call server is unavailable.
  • FIG. 5 b illustrates an exemplary call establishment phase for a mobile to land call within the network architecture of FIG. 2 when the main call server has a partial failure.
  • FIG. 5 c illustrates an exemplary call answer phase for a mobile to land call within the network architecture of FIG. 2 when the main call server has a partial failure.
  • FIG. 6 a illustrates an IP-based heartbeat operation between a main and a redundant call server when an IP network is operational.
  • FIG. 6 b illustrates an SS7-based heartbeat operation between a main and a redundant call server when an IP network is not operational.
  • FIG. 6 c illustrates a call server switchover from a main to a redundant call server when the main call server becomes isolated and the IP network between the call servers is not operational.
  • FIG. 6 d illustrates a call server switchover from a main to a redundant call server when the main call server becomes isolated and the IP network between the call servers is operational.
  • FIG. 6 e illustrates a call server switchover from a redundant to a main call server when the main call server recovers and becomes fully operational and the IP network between the call servers is operational.
  • the present disclosure relates generally to a method and system for a telecommunication node and, more particularly, to a method and system for providing geographical redundancy in a telecommunication network entity in an efficient manner.
  • Specific examples of components and arrangements are described below to simplify the present disclosure. These are, of course, merely examples and are not intended to be limiting.
  • the present disclosure may repeat reference numerals and/or letters in the various examples. This repetition of like numerals for similar parts is for the purpose of simplicity and clarity and does not in itself dictate a relationship between the various embodiments and/or configurations discussed. It is to be understood that the following disclosure provides one or more embodiments, and that there may be many different embodiments, or examples, for implementing different features of the disclosure as encompassed by the claims.
  • the invention provides for geographical redundancy and an efficient switchover process to redundant equipment. By separating active main equipment and standby redundant equipment in different geographical locations, failures can be avoided in the event of a natural disaster or other event that affects an entire building or region.
  • the present invention provides for partial switchover of only components and functions that are inoperative to the corresponding redundant components in the standby equipment. To provide further redundancy and prevent unneeded switchovers, status or heartbeat messages are transmitted between the active main equipment and standby redundant equipment over two different networks.
  • an exemplary network architecture 200 is illustrated in accordance with the present invention for providing geographical redundancy in an efficient manner.
  • the architecture is applied to a Soft-switch Mobile Serving Center (MSC), but it is understood that the architecture may be implemented using other types of network equipment and components.
  • the illustrated soft-switch includes a Call Server 210 at a first location 1 and a Wireless Media Gateway (WMG) 230 .
  • WMG Wireless Media Gateway
  • the Call Server 210 and the WMG 230 both include Soft-switch functionality.
  • the Call Server 210 and WMG 230 are shown in FIG. 2 as separate hardware devices, the Call Server and WMG functionality may also be included in one hardware device.
  • the Call Server 210 is responsible for all call processing and management, as well as controlling the WMG 230 .
  • the WMG 230 is responsible for setting up and establishing a connection for any given type of call upon the call server's request.
  • Location 1 and location 2 are separate geo-locations.
  • location 1 may be in Dallas, Tex. and location 2 may be Chicago, Ill.
  • the geo-locations are separated by sufficient distance (e.g. approximately 30 miles or more) so that natural disasters or other events that affect one geo-location will most likely not affect the other geo-location.
  • the call server 210 in location 1 is the active call server and the redundant call server 220 in location 2 is the standby call server.
  • the redundant call server 220 has the same hardware configuration as the main call server 210 .
  • the active call server controls the MGW 230 and performs call control signaling for voice and data calls.
  • the call servers can communicate control messages with the WMG 230 over the IP network.
  • the WMG 230 communicates with the main call server 210 through connection 234 to the IP network 280 and connection 224 a from the IP network to the main call server 210 .
  • the WMG 230 communicates to the redundant call server 220 through connection 234 to the IP network 280 and connection 224 b from the IP network to the redundant call server 220 .
  • the link 234 to the IP network 280 has a redundant counterpart connected to a redundant port on the WMG 230 .
  • the active call server uses one or more IP addresses to send management and administrative messages over the IP network 280 to the MGW 230 depending on the number of ports connecting the MGW 230 to the IP network 280 .
  • the MGW 230 has the same IP address regardless of the active call server, i.e. the same IP address is used by either the main call server 210 or the redundant call server 220 , whichever is active at the time, to transmit control messages to the MGW 230 over the IP network 280 .
  • each of the call servers 210 and 220 has one or more IP addresses assigned to it, depending on the number of ports each one has connected to the IP network.
  • the MGW 230 uses the assigned IP addresses of the active call server to transmit management and administrative messages (such as in SNMP protocol or other appropriate protocol) to it.
  • the MGW 230 does not transmit messages to the standby call server, as explained in more detail below.
  • the IP network 280 is also used to exchange management and administrative messages between the main call server 210 and the redundant call server 220 over links 226 a and 226 b.
  • the call servers 210 and 220 communicate signaling information with the WMG 230 over signaling links 232 a and 232 b respectively over the wireless network 250 .
  • the MGW 230 only transmits signaling information to the call server that is currently active, as explained in more detail below.
  • the WMG 230 also connects to one or more base station systems (BSS) 240 over links 242 and 244 .
  • BSS base station systems
  • the WMG 230 acts as a cross-connect entity wherein the signaling channels on the links 242 and 244 with the BSS 240 are extracted and cross connected to the call servers 210 and 220 .
  • BSS 240 a is connected to the WMG 230 by signaling links 242 .
  • BSS signaling channels from link 242 are extracted and cross connected to be transmitted over the wireless network 250 to the main call server 210 .
  • the same functions are performed for BSS 240 b .
  • BSS signaling channels from link 244 are extracted and switched for transmission over the wireless network 250 to the main call server 210 .
  • Links 232 , 242 and 244 are preferably TDM links such T1/E1 or SONET/SDH links but may be any other appropriate type or protocol.
  • the BSS message transmission via the wireless network 250 is accomplished through known protocols, such as BSSAP and SCCP over TDM.
  • FIG. 2 a also illustrates a signaling network 290 that is shown in this embodiment as an SS7 network though it may be of any other type of signaling network.
  • the SS7 network includes STPs 300 a , 300 b , 300 c and 300 d .
  • the STPs 300 are part of the SS7 network 290 and act as transfer points between the call servers 210 , 220 and the destination of messages from the call servers 210 , 220 .
  • the main server 210 and the redundant call server 220 each have their own SS7 Point Code as well as a common Alias Point Code for addressing in the SS7 network.
  • the individual SS7 Point Codes are used to transmit heartbeat status messages over the SS7 network as described in more detail with reference to FIG. 6 .
  • the Alias Point Code is used by the SS7 network 290 to support the geographical redundancy solution presented herein.
  • the STP nodes are configured such that all signaling messages from the SS7 network 290 are routed to the active call server using the Alias Point Code.
  • Two routes are assigned to the Alias Point Code, a Primary route (R P ) that terminates at the main call server 210 and a secondary route (R S ) that terminates at the redundant call server 220 .
  • the primary route R P includes two route diverse paths connecting the main call server 210 to the SS7 network 290 .
  • Signaling messages terminating to the redundant call server 220 follow the Secondary route (R S ) shown in FIG. 2 a .
  • the secondary route R S also includes two route diverse paths connecting the redundant call server 210 to the SS7 network 290 as seen in FIG. 2 a .
  • the SS7 network 290 transmits signaling messages over the Secondary route R S to the redundant call server 210 using the same Alias Point Code.
  • FIG. 2 b illustrates one embodiment of the main call server 210 . Since there may be other cards or modules of various types in a call server, FIG. 2 b illustrates only an example of the types of cards that can be used to implement the present invention.
  • Main call server 210 includes the following modules or cards: ESM cards 260 , SIM cards 270 , CCM cards 310 , SAM cards 320 and DDM cards 330 .
  • the ESM cards 260 are the interface to the IP network 280 and are used to send any message from the call server 210 to the IP network 280 and receive any message from the IP network 280 .
  • Each ESM card 260 has its own IP address, and two ESM cards 260 with two different IP addresses are preferably used to provide redundancy.
  • the SIM cards 270 are the interface for signaling links to the SS7 network 290 and the Wireless network 250 .
  • the SIM cards 270 distributes signaling loads among DDM cards 330 .
  • Each SIM card 270 can forward signaling information to any of the DDM modules within the network entity 210 .
  • two SIM cards 220 are used to provide two connections to the MGW 230 over the wireless network 250 and two more SIM cards 220 used to connect to two different STPs 300 in the SS7 network 290 .
  • the DDM card 330 receives messages from the SIM card 310 and distributes the messages to the appropriate CCM card 310 . Each DDM card 330 uses a message distribution process to forward a particular call instance to one CCM card 310 for the complete duration of the call for a specific subscriber.
  • the CCM cards 310 provide call processing for any type of call, voice or data, mobility management, VLR functionality and signaling gateway functions. Mobility management includes the processes necessary for mobile users, such as updating location, handoffs from one cell to another, etc. while the VLR is a database for information on subscribers currently using the system resources.
  • the SAM card 320 performs the operations, maintenance and administration (OAM) functions and billing functions of the call server 210 . It monitors the status of all other cards in the call server 210 and informs the CCM card 310 about available resources for the WMG 230 .
  • the SAM card is also interfaces with peripheral devices 360 such as CD-ROM, disk drive, fan, etc.
  • Additional cards or modules include an alarm indication module (AIM) 370 for providing a physical display of alarms and faults generated by any of the cards within the call server 210 .
  • a power supply card or module (PSM) 350 distributes power to the cards within the call server 210 .
  • the main call server 210 does not include any redundant or standby cards. Any required standby or redundant cards are located only in the redundant call server 220 shown in FIG. 2 a .
  • the redundant call server 220 has a similar hardware configuration with the same type of cards as in the main call server 210 . Again, it does not include extra redundant or standby cards for example, for the CCM and SAM cards. Thus, there is a more efficient use of equipment to provide geographical redundancy than in known solutions.
  • the main call server 210 does include active and standby cards, such as for CCM card 310 and SAM card 320 .
  • the redundant call server 220 may have the same active and standby cards. Though this embodiment requires additional equipment, it may be preferred for simplicity and additional protection. It is also possible that redundant call server 220 may have a somewhat different hardware configuration from the main call server 210 , such as different hardware and software releases, or different number or types of cards provided that the hardware configuration is consistent.
  • the network nodes and call server illustrated in FIG. 2 are provided as one example of equipment that may perform the functionality of the present invention as defined in the claims.
  • functionality described herein in one or more cards may be combined into a single card or module, or additional functionality added or excluded, without varying from the scope of the present invention.
  • other configurations, types of cards, interfaces and modules within telecommunications nodes may perform the same processes to achieve geographical and partial redundancy of the present invention.
  • FIG. 3 a an example of a mobile to land call within the architecture of FIG. 2 is illustrated.
  • FIG. 3 a provides the call establishment phase of the call during normal operations when the main call server 210 is active and the redundant call server 220 is on standby.
  • a mobile device 340 b sends a call initiation request (such as a CM Service request message in GSM protocols or other appropriate protocol) to WMG 230 from the BSS 240 b .
  • the WMG 230 relays this call initiation request to the main call server 210 via the wireless network 250 over signaling link 232 a .
  • a call initiation request such as a CM Service request message in GSM protocols or other appropriate protocol
  • the WMG 230 switches and transmits all signaling messages, such as the call initiation request, to the signaling links 232 a terminating on the main call server 270 b in location 1 .
  • the redundant call server 220 receives no messages on signaling links 232 b from the WMG 230 .
  • the main call server 210 upon receiving the call initiation request at the SIM card 270 a , the main call server 210 initiates the necessary procedures with the BSS 240 b and the mobile 340 b in order to provide the requested services and authenticate the mobile 340 b .
  • the procedures include mobile Authentication, Cyphering, TMSI reallocation and radio resources assignment.
  • step 3 once the call initiation request is accepted, the main call server 210 sends an initial address message (such as an IAM message in the ISDN User Part protocol or other signaling type protocol) to the SS7 network 290 with destination as the “called party number” as requested by the mobile 340 b .
  • the main call server 210 establishes the appropriate termination points at the WMG 230 to reserve the necessary resources for the call.
  • step 5 the main call server 210 synchronizes the call state information with the redundant call server 220 in location 2 by sending call state information over the IP network 280 . This transfer ensures synchronization of real time call state information between the main call server 210 and redundant call server 220 .
  • the standby CCM card 310 b in the redundant call server 220 can continue to process the call.
  • a reply message (such as an ANM message in the ISDN User Part protocol or other signaling type protocol) is received at the main call server 210 from an STP 300 c in the SS7 network 290 .
  • the main call server 210 informs WMG 230 to complete the resource establishment for a 2-way connection.
  • the main call server 210 sends a connection message (such as a DTAP connect message or other protocol used to transfer messages from the MSC to the mobile) to the mobile 340 b , hence connecting the mobile 340 b with the called party.
  • the main call server 210 synchronizes the call state information with the redundant call server 220 in location 2 by transmitting the call state information over the IP network 280 .
  • synchronization of billing data and VLR data between the main call server 210 and redundant call server can also be performed to facilitate switchover.
  • the transfer of billing data in real time over the IP network 280 will minimize the loss of billing data after a switchover.
  • the VLR data includes subscriber information of each subscriber currently in the service area of the main call server 210 . So the synchronization of VLR data with the redundant call server 220 will reduce the call setup time and success rate for calls by subscribers after a switchover. If VLR data is not synchronized, it must be collected and stored on a call by call basis after a switchover.
  • FIG. 4 illustrates the operation of the present invention in the event that a telecommunication entity is completely unavailable.
  • call servers are illustrated in the Figures, the same process may be followed for any other type of network entity.
  • the complete switchover process 400 in the event of a complete failure of the active call server is illustrated in FIG. 4 a .
  • the main call server 210 is the active call server that becomes inoperative.
  • the standby call server in this example redundant call server 220 , will raise an alarm indicating that the main call server 210 is not operational.
  • the mechanisms for monitoring status of main call server 210 and redundant call server 220 and raising an alarm is explained in more detail in relation to FIG. 6 .
  • a switchover process is then initiated in step 420 either manually through an element or network management system or automatically by the redundant call server 220 .
  • the switchover process involves two main parts. The first part is de-activating the active call server and the second part is activating the standby call server.
  • the active call server In the first part of de-activating the active call server, the following actions are taken by the active call server, in this case the main call server 210 .
  • the links to the main call server 210 from the SS7 network are locked, and no more communications are transmitted to the main call server 210 from the SS7 network 290 as shown in step 430 .
  • the SS7 network 290 is informed of the deactivation of the main call server 210 or has already detected its failure and stopped transmission to the main call server 210 over the primary route R p .
  • the communications by the main call server 210 to the MGW 230 are also halted in step 440 .
  • the redundant call server 220 is informed of the unavailability of the main call server 210 .
  • the existing calls in the setup stage may be maintained if state information has been synchronized to the redundant call server 220 . Otherwise, the calls may be dropped.
  • the redundant call server 220 performs the following actions to become the active call server.
  • the redundant call server 220 verifies that the main call server 210 is not operational in step 450 . If verified, the redundant call server takes control of the MGW 230 in step 460 . It transmits control message over the IP network 280 instructing the MGW 230 to use its IP addresses for sending management and administrative messages (such as status messages in SNMP protocol or other appropriate protocol) over the IP network 280 —rather than the IP addresses of the main call server 210 .
  • management and administrative messages such as status messages in SNMP protocol or other appropriate protocol
  • the MGW 230 will then transmit any management and administrative messages (for example SNMP protocol messages or other appropriate types of protocols) over the IP network 280 to the redundant call server 220 using the IP addresses assigned to the redundant call server 220 .
  • the MGW 230 will also reconfigure its cross connections to switch the signaling channels from the BSS 340 a and 340 b received over signaling links 242 and 244 to the signaling links 232 b terminating on the redundant call server 220 as shown in step 470 .
  • the SAM card 320 b in the redundant call server 220 informs the other cards to start the processing of call requests from the MGW 230 .
  • the SS7 network 290 will begin to transmit signaling messages to the redundant call server 220 over the secondary route (R S ) as shown in step 480 .
  • the SS7 network 290 will only transmit to the active call server, now redundant call server 220 , and so no traffic is transmitted over the primary route R P to the main call server 220 .
  • the redundant call server 220 will in turn unlock its SS7 links to the SS7 network and accept the messages from the SS7 network 290 received by its SIM card 270 b.
  • the redundant call server 220 is now the active call server as shown in step 490 . If VLR data was not synchronized prior to switchover, it must be collected and stored on a call by call basis by the redundant call server 220 . The above switchover process can be repeated for any other media gateways in the network.
  • FIG. 4 b an example of a mobile to land call after the complete switchover to redundant call server 220 is illustrated.
  • the example in FIG. 4 b provides the call establishment phase of the call.
  • the mobile 340 b sends a call initiation request to the wireless network 250 .
  • the MGW 230 switches and transmits the signaling channels to the redundant call server 220 now acting as the active call server.
  • the redundant call server 220 upon receiving the call initiation request from the mobile 340 b , the redundant call server 220 starts the necessary procedures with the BSS 240 b and the mobile 340 b . These procedures include mobile Authentication, Cyphering, TMSI reallocation and radio resources assignment.
  • step 3 once the call is accepted, the redundant call server 220 in location 2 sends an initial address message (such as an IAM message in the ISDN User Part protocol or other signaling type protocol) out to the SS7 network 290 with destination as the “called party number” as requested by the mobile 340 b .
  • step 4 the redundant call server 220 establishes the appropriate termination points at the WMG 230 to reserve the necessary resources for the call.
  • Step 1 a reply message (such as an ANM message in the ISDN User Part protocol or other signaling type protocol) is received at the redundant call server 210 from the SS7 network 290 over the secondary route R s .
  • the SS7 network 290 now uses the secondary route R S to transmit signaling message to the redundant call server 220 since the route R P to the main call server 210 in location 1 is not available.
  • the redundant call server 220 informs WMG 230 to complete the resources establishment for a 2-way connection.
  • the redundant call server 220 sends a connection message (such as a DTAP: Connect message in the GSM protocol) to the call originating mobile 340 b , hence connecting the mobile 340 b with the called party.
  • a connection message such as a DTAP: Connect message in the GSM protocol
  • FIG. 5 illustrates the operation of the network in the event of a partial failure of a telecommunication entity.
  • call servers are illustrated in the figures, the same process may be followed for any other type of telecommunication entity.
  • a partial switchover process 500 is illustrated from an active call server to redundant call server.
  • a partial switchover may help prevent dropped calls and lost data that may occur in a complete switchover. In addition, it provides a more efficient use of resources of the active call server.
  • a partial switchover can be performed if the active call server is not in complete failure and can still communicate with the SS7 network 290 and perform most of its primary functions.
  • the active call server and standby call server can be configured to determine when a partial switchover is to be initiated versus a complete switchover to the redundant call server.
  • the active call server may be configured to perform a partial switchover upon failure of a specific type of one or more cards but perform a complete switchover in the event of failure of other types of cards.
  • the active call server has a configuration as shown in FIG. 2 b wherein standby cards are located only in the redundant call server, a partial switchover must occur in the event of active card failure in the main call server 210 .
  • a partial switchover may occur only in the event of active and standby card failure in the main call server 210 .
  • the main call server 210 is the active call server and only its CCM card 310 a becomes inoperative.
  • the same process shown in FIG. 5 a can be performed in the event of failure of one or more other cards or modules on an active call server or other network entity.
  • the main call server 210 determines that one of its cards, in this case the CCM card 310 a , has become inoperative.
  • the CCM card 310 a fails, alarms are generated and the SAM card 320 a of the main call server 210 is notified of its failed status.
  • the SAM card 320 a informs all the other cards in the main call server 210 of the status of the failed CCM card 310 a as shown in step 520 . Since the main call server 210 is still operational except for the CCM card 310 a and the links to the WMG 230 and SS7 network 290 are available, the main call server 210 does not initiate a complete switchover as described in FIG. 4 a . Rather only a partial switchover is initiated in step 530 . In step 540 , the functions of the CCM card 310 a are transferred to the CCM card 310 b in redundant call server 310 b .
  • the SAM card 320 a determines the IP address for the standby CCM card 310 b in the redundant call server 220 and informs the other cards to transmit messages to the IP address for standby CCM card 310 b rather than to CCM card 310 a .
  • the SAM card 320 a also initiates a message over the IP network 280 to the SAM card 320 b in the redundant call server 220 to activate the CCM card 310 b .
  • the WMG 230 will continue to transmit all BSS signaling channels to the links 232 a terminating on the main call server 210 in location 1 .
  • the SS7 network will continue to transmit signaling messages to the main call server 210 over the primary route R P .
  • FIG. 5 b provides an example of a mobile to land call after a partial switchover when the main call server 210 has a failure of its CCM card 310 a .
  • the example in FIG. 5 b provides the call establishment phase of the call.
  • the mobile 340 b sends a call initiation request to the wireless network 230 .
  • the WMG 230 relays this message to main call server 210 via signaling links 232 a over the wireless network 250 .
  • the WMG 230 will continue to transmit all BSS signaling channels to the links terminating on the main call server 210 in location 1 .
  • step 2 upon receiving the call initiation request, the DDM card 330 a in the main call server 210 forwards the call request to the redundant CCM card 310 b in the redundant call server 220 . Since the DDM card 330 a was previously informed of the partial switchover, it transmits the call requests over IP network 280 to the IP address of the CCM card 310 b .
  • the CCM card 310 b in the redundant call server 220 starts the necessary radio procedures with the BSS 240 b and the mobile 340 b . These procedures include mobile Authentication, Cyphering, TMSI reallocation and radio resources assignment.
  • step 3 once the call is accepted, the main call server 210 transmits an initial address message (such as an IAM message in the ISDN User Part protocol or other signaling type protocol) message to the SS7 network 290 with destination as the “called party number” as requested by the mobile 340 b .
  • step 4 the CCM card 310 b in the redundant call server 220 establishes the appropriate termination points at the WMG 230 to reserve the necessary resources.
  • a continuation of the mobile to land call is illustrated when the main call server 210 has a partial failure.
  • the example provides the call answer phase of a call.
  • a reply message (such as an ANM message in the ISDN User Part protocol or other signaling type protocol) is received from the SS7 network 290 at the main call server 210 .
  • the SS7 network continues to transmit signaling messages to the main call server 210 over the primary route R P .
  • the DDM 330 a in the main call server forwards the message to the appropriate CCM card 310 b in the call server 220 in location 2 .
  • step 3 the CCM 310 b in the redundant call server 220 informs WMG 230 to complete the resources establishment for a 2-way connection.
  • step 4 the CCM 310 b in the redundant call server 220 then transmits a connection message (such as a DTAP: Connect message in the GSM protocol) to the call originating mobile 340 b via the SIM card 270 a in the main call server 210 in location 1 .
  • the mobile is now connected to the called party.
  • a mobile to land call was used for purposes of illustration, it is understood that a similar process may be applied to any call scenario, including mobile-to-mobile, land-to-mobile, land-to-land, and others.
  • the above example of the CCM card 310 a failure was used to represent a partial failure scenario in the main call server 210 .
  • the above described process may similarly be applied to any card failure in the active call server, such as failure of a SAM card.
  • the present disclosure may be applied to failures of multiple cards and to any kind of failure in a call server.
  • the present disclosure may be applied to other scenarios wherein the traffic load from the MGW 230 and SS7 network 290 is shared and sent to either the main call server 210 or the redundant call server 220 .
  • the CCM cards can then route the call messages to the appropriate SIM cards in the main call server 210 or redundant call server 220 in order to balance the load between the main and the redundant call servers.
  • the present disclosure may also be applied if the standby CCM cards are located in the main call server 210 with the other active CCM cards as shown in FIG. 2 c above.
  • the messages may be forwarded to the standby CCM card in the same call server.
  • the partial switchover described above may also be applied if both active and standby CCM cards in the same call server fail.
  • a status or “heartbeat” message is used to inform the call servers 210 and 220 in both locations about the availability of the other call server. This signal informs each call server of the other's status, such as that the other call server is active and is handling calls with no problems.
  • This procedure allows the redundant call server 220 to know when to take over a service when the main call server 210 cannot process calls, and the main call server 210 to take over the service from the redundant call server 220 after it has fully recovered.
  • the heartbeat procedure includes transferring a message from one location to another on a periodic basis.
  • the transmission frequency may be configurable and defined in the call server. If a call server does not receive a primary heartbeat over a first network, it may use another mechanism to exchange a secondary heartbeat over a different network. If the secondary heartbeat is not received, the call server is configured to assume that the other call server has a problem and cannot handle any calls. A switchover process can then be initiated.
  • a primary heartbeat solution is presented to inform each of the call servers 210 and 220 of their respective status.
  • each call server 210 and 220 sends an IP-based heartbeat message to the other call server over the IP network 280 .
  • This message is initiated from the SAM card 320 a and 320 b of each call server and sent to the local ESM card 260 .
  • the local ESM card 260 forwards the message over the IP network 280 to the ESM card 260 located in the other call server.
  • the ESM card 260 receiving the message then forwards the message to its local SAM card 320 .
  • it is considered that the main call server 210 in location 1 is active and processing calls, while the redundant call server 220 in location 2 is in standby mode.
  • a secondary heartbeat solution over a different network is presented to inform the call servers of their status.
  • This secondary heartbeat mechanism may be used alternatively when the primary heartbeat message over the IP network ( FIG. 6 a ) is not received from the other call server.
  • a call server may send a secondary heartbeat message using the SS7 network.
  • the SAM card 320 a transmits a trigger to the SCCP application residing on its local SIM card 270 a .
  • the SIM card 270 a then sends an “SCCP Connection Request” message to the SIM card 270 b in the redundant call server 220 over the SS7 network 290 .
  • Another solution includes having the SCCP application transmit a subsystem test message (such as a SubSystem_Test (SST)) to the SIM card 270 b in the redundant call server 220 over the SS7 network 290 .
  • the SCCP messages “Connection Request” and “SubSystem Test” are merely representative of two types of messages that may be used for the secondary heartbeat message between call servers over the SS7 network 290 . Other types of messages or other protocols may be used to transmit similar information over a different network.
  • each call server is equipped with and identified by a different Point Code (PC).
  • This PC may be private and may not be known to any other node in the network.
  • the SIM card 270 b in the redundant call server 220 receives the SCCP message, it transmits a trigger to its local SAM card 320 b , informing it the main call server 210 is available.
  • the secondary heartbeat messages over the SS7 network 290 may be achieved by having each call server transmit an SCCP message on a periodic basis. The period of heartbeat transmission may be the same as that used for the primary heartbeat over the IP network 280 , or may be another configurable parameter.
  • the main call server 210 in location 1 is active and processing calls, while the redundant call server 220 in location 2 is on standby during the duration of the IP network failure 280 .
  • the secondary heartbeat messages via the SS7 network 290 can be suspended.
  • This method of transmitting a heartbeat message over two different networks prevents unnecessary switchovers. For example, in FIG. 6 b , if only an IP heartbeat message over the IP network 280 was implemented, a complete switchover may have occurred to the redundant call server 220 without need. Such an unneeded switchover could result in dropped calls and delay and require a further switchover back from the redundant call server 220 to the main call server 210 . Thus, the secondary heartbeat message over a different network, in this case an SS7 network, prevents unneeded switchovers in the event that the first network becomes unavailable.
  • FIG. 6 c an example is illustrated where the heartbeat of the main call server 210 is not received at the redundant call server 220 because the IP network 280 and the SS7 links at the main call server 210 are down.
  • the switchover process in FIG. 4 a is initiated wherein the redundant call server 220 becomes the active call server.
  • FIG. 6 d an example is illustrated where the IP heartbeat of the main call server 210 is exchanged over the IP network 280 successfully.
  • the SS7 links are down in the main call server 210 .
  • the main call server 210 cannot handle calls, and it initiates a switch-over command to the redundant call server 220 by requesting that the redundant call server 220 bring itself into service and take over all the calls as described in FIG. 4 a.
  • FIG. 6 e an example is illustrated where, after the SS7 links at the main call server 210 are recovered, it initiates a switch-back command to the redundant call server 220 by requesting that the redundant call server 220 transfer control to the main call server 210 .
  • a similar process is then followed as described in FIG. 4 a , except that the redundant call server performs actions required to transfer to standby mode and the main call server becomes active.
  • the present disclosure provides reliability in a telecommunication network entity despite events that affect an entire geographical location, such as fire, earthquake, etc.
  • it provides an efficient partial switchover process in the event of failure of only one or more modules, for example due to hardware stress, and hardware failure, as well as other causes such as software failures and others.
  • a primary and secondary heartbeat message are transmitted over different networks to prevent unneeded switchovers.
  • the above disclosure provides many different embodiments, or examples, for implementing the disclosure. However, specific examples, and processes are described to help clarify the disclosure. These are, of course, merely examples and are not intended to limit the disclosure from that described in the claims. For instance, even though a wireless telecom entity was used for purposes of illustration, the present disclosure may be applied to wireline telecom entities. In addition, even though a soft-switch was used in the various embodiments, the present disclosure may be applied to any switch technology, including those that do not use a physical split between the bearer and signaling plans. Also, even though a wireless network and wireless services were used to describe the disclosure, the present disclosure may be applied to non-wireless applications and non-wireless networks.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Environmental & Geological Engineering (AREA)
  • Health & Medical Sciences (AREA)
  • Cardiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)
US10/597,950 2004-02-13 2005-02-14 Method and system for providing availability and reliability for a telecommunication network entity Expired - Fee Related US7577090B2 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US54462204P 2004-02-13 2004-02-13
US64084404P 2004-12-30 2004-12-30
PCT/US2005/004422 WO2005081447A1 (en) 2004-02-13 2005-02-14 Method and system for providing availability and reliability for a telecommunication network entity

Publications (2)

Publication Number Publication Date
US20070165516A1 US20070165516A1 (en) 2007-07-19
US7577090B2 true US7577090B2 (en) 2009-08-18

Family

ID=34890472

Family Applications (1)

Application Number Title Priority Date Filing Date
US10/597,950 Expired - Fee Related US7577090B2 (en) 2004-02-13 2005-02-14 Method and system for providing availability and reliability for a telecommunication network entity

Country Status (4)

Country Link
US (1) US7577090B2 (zh)
EP (1) EP1719282B1 (zh)
CN (1) CN1969494B (zh)
WO (1) WO2005081447A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080144785A1 (en) * 2006-12-19 2008-06-19 Dae-Hyun Lee Call setup method and terminal in a IP network
US20090135723A1 (en) * 2007-11-28 2009-05-28 Davidson Mark E Methods, systems, and computer program products for performing ip link proving using heartbeat messages
US20090182853A1 (en) * 2008-01-15 2009-07-16 Samsung Electronics Co., Ltd. UPnP APPARATUS AND METHOD FOR PROVIDING UPnP NETWORK WITH MULTIPLE REMOTE ACCESS SERVICE
US20090291675A1 (en) * 2008-05-21 2009-11-26 Mediatek Inc. Methods for handling conference communication and the communication apparatuses utilizing the same
US8200283B2 (en) 2009-04-01 2012-06-12 Mediatek Inc. Communication apparatuses for handling apparatus terminated or originated communication requests with increased communication capability and methods thereof
US8462637B1 (en) * 2005-01-04 2013-06-11 Sheridan Ross P.C. Dial plan routing for fragmented networks

Families Citing this family (63)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7139565B2 (en) 2002-01-08 2006-11-21 Seven Networks, Inc. Connection architecture for a mobile network
US7532568B1 (en) * 2002-07-09 2009-05-12 Nortel Networks Limited Geographic redundancy for call servers in a cellular system based on a bearer-independent core network
US9913300B2 (en) * 2011-12-14 2018-03-06 Kodiak Networks, Inc. Push-to-talk-over-cellular (PoC)
WO2006108259A1 (en) * 2005-04-14 2006-10-19 Armor Technologies Corporation Secure client operating system for connection to an unsecure network
US8593939B2 (en) * 2005-04-19 2013-11-26 At&T Intellectual Property Ii, L.P. Method and apparatus for maintaining active calls during failover of network elements
US8438633B1 (en) 2005-04-21 2013-05-07 Seven Networks, Inc. Flexible real-time inbox access
WO2006133165A2 (en) * 2005-06-03 2006-12-14 Sonus Networks, Inc. Pstn signalling at a media gateway for a packet-based network
WO2006136660A1 (en) 2005-06-21 2006-12-28 Seven Networks International Oy Maintaining an ip connection in a mobile network
US7711391B2 (en) * 2005-07-29 2010-05-04 Varia Holdings Llc Multiple processor communication circuit cards and communication devices that employ such cards
BRPI0616948A2 (pt) * 2005-10-07 2011-07-05 Tekelec Us métodos, sistemas e produtos de programa de computador para propiciar translação de endereço utilizando informação de endereço subseqüente
US8166197B2 (en) * 2005-10-25 2012-04-24 Oracle International Corporation Multipath routing process
US9264455B2 (en) * 2005-11-15 2016-02-16 Alcatel Lucent Clustering call servers to provide protection against call server failure
US8223687B2 (en) * 2005-11-23 2012-07-17 Cisco Technology, Inc. Method for providing home agent geographic redundancy via a service redundancy protocol
US8437305B2 (en) 2005-11-23 2013-05-07 Cisco Technology, Inc. Method for providing home agent geographic redundancy
US8565070B2 (en) * 2005-11-23 2013-10-22 Cisco Technology, Inc. System and method for active geographic redundancy
US20070147233A1 (en) * 2005-12-23 2007-06-28 Tolga Asveren Graceful failover mechanism for SSCOP service access point for SS7 links
CN100386997C (zh) * 2005-12-30 2008-05-07 华为技术有限公司 一种基于点对点连接的电信设备间的数据传输系统和方法
US7715843B2 (en) * 2006-04-20 2010-05-11 At&T International Property I, L.P. Electronic message exchange over multiple wireless communication networks with a single device
US8805425B2 (en) 2007-06-01 2014-08-12 Seven Networks, Inc. Integrated messaging
US8254553B2 (en) * 2007-08-10 2012-08-28 Tekelec, Inc. Systems, methods, and computer program products for number translation with local directory number support
US20090041223A1 (en) * 2007-08-10 2009-02-12 Devesh Agarwal Systems, methods, and computer readable media for triggerless call redirection with release
US9002828B2 (en) 2007-12-13 2015-04-07 Seven Networks, Inc. Predictive content delivery
CN101904192B (zh) * 2007-12-17 2014-12-17 艾利森电话股份有限公司 移动核心网络节点冗余
US8862657B2 (en) 2008-01-25 2014-10-14 Seven Networks, Inc. Policy based content service
US20090193338A1 (en) 2008-01-28 2009-07-30 Trevor Fiatal Reducing network and battery consumption during content delivery and playback
US8909759B2 (en) 2008-10-10 2014-12-09 Seven Networks, Inc. Bandwidth measurement
US8264956B2 (en) * 2009-02-27 2012-09-11 Cisco Technology, Inc. Service redundancy in wireless networks
US8395988B2 (en) * 2009-03-30 2013-03-12 Alcatel Lucent Method and system for providing voice survivability
CN101562513B (zh) * 2009-05-25 2012-02-29 中兴通讯股份有限公司 一种单板主备倒换的方法及装置
US8582502B2 (en) 2009-06-04 2013-11-12 Empire Technology Development Llc Robust multipath routing
EP3407673B1 (en) 2010-07-26 2019-11-20 Seven Networks, LLC Mobile network traffic coordination across multiple applications
US8838783B2 (en) 2010-07-26 2014-09-16 Seven Networks, Inc. Distributed caching for resource and mobile network traffic management
US8484314B2 (en) 2010-11-01 2013-07-09 Seven Networks, Inc. Distributed caching in a wireless network of content delivered for a mobile application over a long-held request
WO2012060995A2 (en) 2010-11-01 2012-05-10 Michael Luna Distributed caching in a wireless network of content delivered for a mobile application over a long-held request
US8903954B2 (en) 2010-11-22 2014-12-02 Seven Networks, Inc. Optimization of resource polling intervals to satisfy mobile device requests
US8843153B2 (en) 2010-11-01 2014-09-23 Seven Networks, Inc. Mobile traffic categorization and policy for network use optimization while preserving user experience
US8499336B2 (en) 2010-11-23 2013-07-30 Cisco Technology, Inc. Session redundancy among a server cluster
WO2012094675A2 (en) 2011-01-07 2012-07-12 Seven Networks, Inc. System and method for reduction of mobile network traffic used for domain name system (dns) queries
EP2700021A4 (en) 2011-04-19 2016-07-20 Seven Networks Llc MANAGEMENT OF COMMON RESOURCES AND VIRTUAL RESOURCES IN A NETWORKED ENVIRONMENT
GB2493473B (en) 2011-04-27 2013-06-19 Seven Networks Inc System and method for making requests on behalf of a mobile device based on atomic processes for mobile network traffic relief
US8621075B2 (en) 2011-04-27 2013-12-31 Seven Metworks, Inc. Detecting and preserving state for satisfying application requests in a distributed proxy and cache system
US9197900B2 (en) * 2011-09-14 2015-11-24 Mobitv, Inc. Localized redundancy for fragment processing
US8934414B2 (en) 2011-12-06 2015-01-13 Seven Networks, Inc. Cellular or WiFi mobile traffic optimization based on public or private network destination
EP2789138B1 (en) * 2011-12-06 2016-09-14 Seven Networks, LLC A mobile device and method to utilize the failover mechanisms for fault tolerance provided for mobile traffic management and network/device resource conservation
US9277443B2 (en) 2011-12-07 2016-03-01 Seven Networks, Llc Radio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol
GB2498064A (en) 2011-12-07 2013-07-03 Seven Networks Inc Distributed content caching mechanism using a network operator proxy
EP2792188B1 (en) 2011-12-14 2019-03-20 Seven Networks, LLC Mobile network reporting and usage analytics system and method using aggregation of data in a distributed traffic optimization system
US8909202B2 (en) 2012-01-05 2014-12-09 Seven Networks, Inc. Detection and management of user interactions with foreground applications on a mobile device in distributed caching
US8812695B2 (en) 2012-04-09 2014-08-19 Seven Networks, Inc. Method and system for management of a virtual network connection without heartbeat messages
WO2013155208A1 (en) 2012-04-10 2013-10-17 Seven Networks, Inc. Intelligent customer service/call center services enhanced using real-time and historical mobile application and traffic-related statistics collected by a distributed caching system in a mobile network
WO2014011216A1 (en) 2012-07-13 2014-01-16 Seven Networks, Inc. Dynamic bandwidth adjustment for browsing or streaming activity in a wireless network based on prediction of user behavior when interacting with mobile applications
US9161258B2 (en) 2012-10-24 2015-10-13 Seven Networks, Llc Optimized and selective management of policy deployment to mobile clients in a congested network to prevent further aggravation of network congestion
CN103023694B (zh) * 2012-11-27 2015-06-17 中国科学院声学研究所 一种atca架构中双管理板的协调启动方法及其系统
US9307493B2 (en) 2012-12-20 2016-04-05 Seven Networks, Llc Systems and methods for application management of mobile device radio state promotion and demotion
US9241314B2 (en) 2013-01-23 2016-01-19 Seven Networks, Llc Mobile device with application or context aware fast dormancy
US8874761B2 (en) 2013-01-25 2014-10-28 Seven Networks, Inc. Signaling optimization in a wireless network for traffic utilizing proprietary and non-proprietary protocols
US8750123B1 (en) 2013-03-11 2014-06-10 Seven Networks, Inc. Mobile device equipped with mobile network congestion recognition to make intelligent decisions regarding connecting to an operator network
JP6153250B2 (ja) * 2013-06-21 2017-06-28 Kddi株式会社 耐災害性ネットワークトポロジ導出システムおよび方法、および耐災害性ネットワークトポロジ導出用プログラム
US9065765B2 (en) 2013-07-22 2015-06-23 Seven Networks, Inc. Proxy server associated with a mobile carrier for enhancing mobile traffic management in a mobile network
US20150215158A1 (en) * 2014-01-28 2015-07-30 Qualcomm Incorporated Discriminating or prioritizing users during failover in a voip system
CN105515812A (zh) * 2014-10-15 2016-04-20 中兴通讯股份有限公司 资源的故障处理方法及装置
CN110213778B (zh) * 2018-02-28 2021-11-05 中兴通讯股份有限公司 一种网元主备智能配对的方法及装置
US11563627B2 (en) * 2019-11-08 2023-01-24 Verizon Patent And Licensing Inc. Remote probing for failover

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020165944A1 (en) * 2001-05-07 2002-11-07 Wisner Steven P. System and method for providing network services using redundant resources
US20030061319A1 (en) * 2001-09-27 2003-03-27 Manzardo Marcel B. Method and apparatus for providing back-up capability in a communication system
US7334064B2 (en) * 2003-04-23 2008-02-19 Dot Hill Systems Corporation Application server blade for embedded storage appliance

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002084363A (ja) 2000-09-06 2002-03-22 Nec Corp ゲートウェイシステム及びそれに用いる回線制御方法
US7023794B2 (en) * 2002-02-11 2006-04-04 Net2Phone, Inc. Method and architecture for redundant SS7 deployment in a voice over IP environment

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020165944A1 (en) * 2001-05-07 2002-11-07 Wisner Steven P. System and method for providing network services using redundant resources
US20030061319A1 (en) * 2001-09-27 2003-03-27 Manzardo Marcel B. Method and apparatus for providing back-up capability in a communication system
US7334064B2 (en) * 2003-04-23 2008-02-19 Dot Hill Systems Corporation Application server blade for embedded storage appliance

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8462637B1 (en) * 2005-01-04 2013-06-11 Sheridan Ross P.C. Dial plan routing for fragmented networks
US8600017B2 (en) * 2006-12-19 2013-12-03 Samsung Electronics Co., Ltd. Call setup method and terminal in an IP network
US20080144785A1 (en) * 2006-12-19 2008-06-19 Dae-Hyun Lee Call setup method and terminal in a IP network
US20090135723A1 (en) * 2007-11-28 2009-05-28 Davidson Mark E Methods, systems, and computer program products for performing ip link proving using heartbeat messages
US7907533B2 (en) * 2007-11-28 2011-03-15 Tekelec Methods, systems, and computer program products for performing IP link proving using heartbeat messages
US8402122B2 (en) * 2008-01-15 2013-03-19 Samsung Electronics Co., Ltd. UPnP apparatus and method for providing UPnP network with multiple remote access service
US20090182853A1 (en) * 2008-01-15 2009-07-16 Samsung Electronics Co., Ltd. UPnP APPARATUS AND METHOD FOR PROVIDING UPnP NETWORK WITH MULTIPLE REMOTE ACCESS SERVICE
US8019323B2 (en) * 2008-05-21 2011-09-13 Mediatek Inc. Methods for handling an apparatus terminated communication request and communication apparatuses utilizing the same
US8185093B2 (en) * 2008-05-21 2012-05-22 Mediatek Inc. Methods for handling an apparatus terminated communication request and communication apparatuses utilizing the same
US8121584B2 (en) 2008-05-21 2012-02-21 Mediatek Inc. Methods for handling conference communication and the communication apparatuses utilizing the same
US20090291710A1 (en) * 2008-05-21 2009-11-26 Mediatek Inc. Methods for handling an apparatus terminated communication request and communication apparatuses utilizing the same
US20090291675A1 (en) * 2008-05-21 2009-11-26 Mediatek Inc. Methods for handling conference communication and the communication apparatuses utilizing the same
US8200283B2 (en) 2009-04-01 2012-06-12 Mediatek Inc. Communication apparatuses for handling apparatus terminated or originated communication requests with increased communication capability and methods thereof

Also Published As

Publication number Publication date
CN1969494A (zh) 2007-05-23
EP1719282B1 (en) 2015-09-09
WO2005081447A1 (en) 2005-09-01
EP1719282A4 (en) 2009-06-17
EP1719282A1 (en) 2006-11-08
CN1969494B (zh) 2012-10-17
US20070165516A1 (en) 2007-07-19

Similar Documents

Publication Publication Date Title
US7577090B2 (en) Method and system for providing availability and reliability for a telecommunication network entity
US7995564B1 (en) Geographic redundancy for call servers in a cellular system based on a bearer-independent core network
JP3974652B2 (ja) 通信システムにおけるノードのためのハードウェアおよびデータ冗長アーキテクチャ
US7675853B2 (en) Communication system architecture and operating methods thereof
EP2238782B1 (en) Mobile core network node redundancy
US8452331B2 (en) Method and system for implementing mobile switch center dual homing
CN100574486C (zh) 通信网络中双归属组网的系统及其方法
AU738158B2 (en) Database updating in a mobile communication system
JP4830081B2 (ja) ワイヤレスモビリティサービスプラットフォーム
US6717939B1 (en) Virtual transport server in a telecommunication network
US7023977B2 (en) Method and system for providing softswitch failure protection in a communication network
US8559940B1 (en) Redundancy mechanisms in a push-to-talk realtime cellular network
Busche et al. Network architecture for critical communications requirements
EP1668795A1 (en) Method for reducing the time delay in a telephone system
IE20001067A1 (en) A wireless mobility services platform
KR20050023674A (ko) 브이5.2 프로토콜 처리 시스템의 이중화 처리 방법
JPH0983572A (ja) フレームリレーのバックアップ回線接続・切断方式及びｆｒａｄのバックアップ通信方式

Legal Events

Date Code Title Description
FEPP Fee payment procedure

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

AS Assignment

Owner name: ALCATEL-LUCENT USA INC., NEW JERSEY

Free format text: MERGER;ASSIGNOR:ALCATEL USA MARKETING, INC.;REEL/FRAME:022861/0067

Effective date: 20081101

Owner name: ALCATEL USA MARKETING, INC., TEXAS

Free format text: MERGER;ASSIGNOR:ALCATEL WIRELESS, INC.;REEL/FRAME:022861/0001

Effective date: 20070101

STCF Information on status: patent grant

Free format text: PATENTED CASE

CC Certificate of correction
FPAY Fee payment

Year of fee payment: 4

FEPP Fee payment procedure

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

AS Assignment

Owner name: SOUND VIEW INNOVATIONS, LLC, NEW JERSEY

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ALCATEL LUCENT;REEL/FRAME:032086/0016

Effective date: 20131223

FPAY Fee payment

Year of fee payment: 8

AS Assignment

Owner name: NOKIA OF AMERICA CORPORATION, DELAWARE

Free format text: CHANGE OF NAME;ASSIGNOR:ALCATEL-LUCENT USA INC.;REEL/FRAME:050476/0085

Effective date: 20180103

AS Assignment

Owner name: ALCATEL LUCENT, FRANCE

Free format text: NUNC PRO TUNC ASSIGNMENT;ASSIGNOR:NOKIA OF AMERICA CORPORATION;REEL/FRAME:050662/0204

Effective date: 20190927

FEPP Fee payment procedure

Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

LAPS Lapse for failure to pay maintenance fees

Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STCH Information on status: patent discontinuation

Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362

FP Lapsed due to failure to pay maintenance fee

Effective date: 20210818