|Publication number||US20030035414 A1|
|Application number||US 09/933,615|
|Publication date||Feb 20, 2003|
|Filing date||Aug 20, 2001|
|Priority date||Aug 20, 2001|
|Publication number||09933615, 933615, US 2003/0035414 A1, US 2003/035414 A1, US 20030035414 A1, US 20030035414A1, US 2003035414 A1, US 2003035414A1, US-A1-20030035414, US-A1-2003035414, US2003/0035414A1, US2003/035414A1, US20030035414 A1, US20030035414A1, US2003035414 A1, US2003035414A1|
|Original Assignee||Siemens Information|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (5), Referenced by (21), Classifications (12), Legal Events (1)|
|External Links: USPTO, USPTO Assignment, Espacenet|
 1. Field of the Invention
 The present invention relates to telecommunications systems and, particularly, to an improved, Internet Protocol telephony system.
 The International Telecommunications Union (ITU) Recommendation H.323 describes a set of devices and protocols for multimedia communication over packet-switched networks. The four main components defined by the specification are clients (also referred to as terminals or endpoints), multipoint control units, gateways, and gatekeepers.
 The H.323 Recommendation provides for separate call signaling, call control and media channels. Typically, call signaling and call control are routed through the gatekeeper, while the media channels (i.e., audio, data and/or video) are routed directly between the endpoints. For example, to place a call between two clients, the calling party client sends a message to a gatekeeper, which resolves the address of the receiving party and sends the appropriate signaling messages to the caller and receiver. Once the signaling and control channels have been established, the endpoints establish the media channel(s). There may be more than one media channel for a call, such as two unidrectional channels for an audio call. The H.225.0 signaling channel and the H.245 call control channel are also used to terminate the call.
 If the gatekeeper fails for any reason, existing calls are typically terminated, and new calls via the gatekeeper become impossible. While some call capability may exist using gatekeeper-less operation, many call features will be lost. One solution is to provide a backup gatekeeper on premises that will track other gatekeeper's operations, but providing such a backup can be expensive and may not necessarily provide the desired level of reliability.
 These disadvantages in the prior art are overcome in large part by a system and method according to the present invention. According to one embodiment of the invention, a gatekeeper is configured to act as a backup to multiple other gatekeepers. The backup gatekeeper maintains a database of users for which it provides the backup services. When one of the subscriber gatekeepers fails or is unavailable, gatekeeper traffic is automatically redirected to the backup. The backup may also maintain in its database a record of what services are provided to each of the subscriber gatekeepers.
 A telecommunication system according to one embodiment of the invention includes a plurality of Internet Protocol voice networks, such as telephony over LAN (ToL) networks, including primary gatekeepers. A Service Provider maintains a backup gatekeeper for each of the ToL networks. The backup gatekeeper maintains a database associated with all the ToL networks it provides backup service to. A proxy server at each of the networks receives all gatekeeper requests and first tries to forward the request to the primary gatekeeper. If the appropriate gatekeeper fails to respond, the proxy server forwards the request to the backup gatekeeper, which handles the call.
 A telecommunication system according to another embodiment of the invention includes a plurality of Internet Protocol voice networks including primary gatekeepers. System routers, such as load sharing routers, are adapted to route traffic to the primary gatekeepers if they are operational, and to the backup gatekeeper if the appropriate primary gatekeeper is not. The backup gatekeeper then accesses its database for the features it is to provide the user associated with the non-available primary gatekeeper.
 A method according to an embodiment of the present invention includes a service provider providing gatekeeper backup services to a plurality of off-site voice packet networks from a single central backup gatekeeper. The gatekeeper maintains a database of local gatekeepers for which the backup service is to be provided. The services provided may be identical to those provided by the corresponding local gatekeeper, or may be a more basic level of service to reduce the cost of the backup service.
 A better understanding of the invention is obtained when the following detailed description is considered in conjunction with the following drawings in which:
FIG. 1 is a diagram illustrating an H.323 system according to an embodiment of the invention;
FIG. 2 is a block diagram of a backup gatekeeper in accordance with an embodiment of the present invention;
FIG. 3 is a flowchart illustrating operation of an embodiment of the present invention;
FIG. 4 is a flowchart illustrating operation of an embodiment of the present invention; and
FIG. 5 is a flowchart illustrating operation of an embodiment of the present invention.
 Turning now to the drawings, and with particular attention to FIG. 1, a diagram illustrating an exemplary telecommunications system 100 according to an embodiment of the present invention is shown. It is noted that, while described herein with regard to an H.323 network, the invention is equally applicable to any voice packet network such as MGCP (Media Gateway Control Protocol), SIP+ (Inter MGS Protocol), SGCP, MEGACO, and generally, any voice or multimedia over IP scheme. Further, it is noted that, while described specifically in the context of voice packets, the present invention encompasses the use of any multimedia information, such as video, data, voice, or any combinations thereof. Finally, it is noted that an exemplary generic H.323 system is the HiPath series available from Siemens Corp.
 As shown, the telecommunications network 100 includes a plurality of ToL (telephony over LAN) networks 104 a, 104 b, 104 c coupled via the Internet 102. A Network Services Provider, such as an Internet Service Provider or Application Service Provider) 106 including a backup gatekeeper 107 according to an embodiment of the present invention couples to the ToL networks 104 a-104 c via the Internet 102, as well. In certain embodiments, the NSP 106 may include a proxy server 109, as well. In addition, as shown, routers 108 a-108 d may be used to route packets to the appropriate destinations. In practice, more or fewer than three ToL networks may be coupled in the network. Additional devices and networks, such as non-voice or multimedia devices, may also be coupled in the network. The network can include packet-switched Internet Protocol (IP) and Internet Packet Exchange (IPX) over Ethernet, Fast Ethernet and Token Ring networks. Thus, the figure is exemplary only.
 Each ToL network 104 a-104 c includes a local area network (LAN) or packet network 201 a-201 c. Coupled to the LANs 201 a-201 c may be a variety of H.323 terminals 202 a-202 c, 203 a-203 c, multi-point control units (MCU) 204 a-204 c, H.323 gateways 206 a-206 c, primary H.323 gatekeepers 208 a-208 c and a plurality of other devices such as personal computers (not shown). It is noted that each ToL network 104 a-104 c may include more or fewer of the various components illustrated.
 In the example illustrated, the H.323 terminals 202 a-202 c, 203 a-203 c are in compliance with the H.323 Recommendation. Thus, the H.323 terminals 202 a-202 c, 203 a-203 c support H.245 control signaling for negotiation of media channel usage, Q.931 (H.225.0) for call signaling and call setup, H.225.0 Registration, Admission and Status (RAS), and RTP/RTCP for sequencing audio and video packets. The H.323 terminals 202 a-202 c, 203 a-203 c may further implement audio and video codecs, T.120 data conferencing protocols and MCU capabilities.
 The gateways 206 a-206 c couple the ToL networks 104 a-104 c to external networks, such as the public switched telephone network (PSTN). The MCUs 204 a-204 c support multi-point operation in accordance with the H.323 Recommendation. The gatekeepers 208 a-208 c handle call signaling, call requests, address translation, etc. Further details concerning the H.323 Recommendation may be obtained from the International Telecommunications Union; the H.323 Recommendation is hereby incorporated by reference in its entirety as if fully set forth herein.
 In operation, the users of the ToL networks 104 a-104 c subscribe to the ISP 106 to provide backup services. When one of the local gatekeepers 208 a-208 c is unavailable, the call requests and other signaling is passed through the backup gatekeeper. The gatekeeper 107 thus stores a database of local gatekeeper profiles. It is noted, however, that the backup gatekeeper need not necessarily provide the same range of services as the local gatekeepers.
 The determination of whether backup services are needed may be accomplished in a variety of ways. For example, in one embodiment of the invention, the routers 108 implement load sharing and can identify if a local client gatekeeper is on line. If the local gatekeeper is offline, the routers can route the packets to the backup. In another embodiment, a proxy server is used to direct all signaling. The proxy server receives call requests, for example, and routes them to the local client gatekeeper if that gatekeeper is functioning. Otherwise, it routes the call signaling to the backup. Such a proxy server may be implemented as any system suitable to identify packet destinations and whether a destination is functioning such as a load sharing device, such as those available from Cisco Systems, Inc.
FIG. 2 depicts a backup gatekeeper in accordance with an embodiment of the present invention. The backup gatekeeper 107 include a control processor 250, a memory 252, a router 256, and a network interface 258. The control processor may be implemented, for example, as a Pentium series processor running a Windows NT operating system. The memory 252 maintains a database of gatekeeper users or user profiles 254 a-254 n for which backup services are provided. For example, the users may be arranged by IP address. In addition, the memory may store an “EnterpriseSelect” software module 257 executable by the control processor 250. Packets are inspected for their IP address or destination and used to determine which party needs backup services. Then, the packets are routed to the backup gatekeeper 107. The control processor 250 checks the memory database of the user gatekeepers to determine which services are enabled for that user (e.g., call forwarding, etc.), and whether there are any customer specific items that apply (e.g., closed user groups, dialing plans, etc.). Then the gatekeeper feature associated with the user can be activated and configured appropriately including, for example, billing services. Either multiple instances of gatekeeper software may be implemented (i.e., one per user, preconfigured) or a single gatekeeper program configured with all possible features can select which features are to be afforded a user. The backup gatekeeper 107 then functions as the signaling and routing gatekeeper for the call. It is noted that, while illustrated as a single discrete unit, the backup gatekeeper functionality could also be implemented, for example, as a plurality of individual gatekeepers controlled by a control module. Thus, the figure is exemplary only.
FIG. 3 illustrates a method for gatekeeper operation according to an embodiment of the present invention. In a step 302, the gatekeeper user profiles are stored in the backup gatekeeper. For example, local client gatekeepers may be identified by their own IP addresses, or by the IP addresses of clients they serve. In a step 304, the backup gatekeeper receives data packets. In one embodiment, the packets are received from a proxy server which has identified whether a particular client gatekeeper is functioning. In another embodiment, the packets are received from a router which has done the same identification. The router or proxy server may make this determination, for example, by sending one or more control signals to the local gatekeeper and waiting a predetermined period before no reply is received. In 306, the backup gatekeeper identifies that backup functions are needed. In step 308, the backup gatekeeper accesses the backup gatekeeper profile for the system identified by the sender or receiver IP address in the packets. In step 310, the backup gatekeeper provides the appropriate backup services to the client.
FIG. 4 illustrates signal flow for system operation according to one embodiment of the invention. Shown schematically are, for example, a caller (UA1) 202 a, called party (UA2) 202 b, a router 108 a, a client (local) gatekeeper 208 a and a backup gatekeeper (GKB) 107. The reference numerals refer to components identified in FIG. 1; it is noted, however, that other components may be operable in a similar manner. If the endpoint UA1 wants to establish a call to another user UA2, the endpoint UA1 sends an ARQ message (AdmissionRequest) 402 a, which is to be routed by the router or proxy server to the gatekeeper GK. Either the router or the proxy server determines, however, that the client gatekeeper GK is not in service. The backup gatekeeper GKB receives the ARQ message from the router, identifies the user local gatekeeper, and, in 404, accesses the gatekeeper profile database to identify the services to be provided for the non-functioning gatekeeper GK. The backup gatekeeper GKB responds to the ARQ with an ACF (Admission Confirm) message 406 to the client UA1. Next, in response to the ACF message, the client UA1 sends an H.225.0 set-up message 408 to the backup gatekeeper GKB. The Call Setup message includes the identity of the called party. It is noted that in alternate embodiments, the gatekeeper GKB does not access the database until the call setup message is received.
 In 410, the backup gatekeeper GKB will forward the call setup message to the destination UA2. In response, the endpoint UA2 conducts an ARQ/ACF exchange 412 with the backup gatekeeper GKB. The endpoint UA2 then sends H.225.0 Alerting and Connect messages 414 to the backup gatekeeper GKB as the call progresses to the connect state. The backup gatekeeper GKB, in turn provides the Alerting and Connect messages 416 to the endpoint UA1. The Alerting or Connect message include the Gatekeeper H.245 Control Channel Transport Address, which is used to establish the H.245 control channel 418. Next, an H. 245 capability exchange 420 is undertaken. Finally, the media channel 422 is opened between endpoint UA1 and UA22.
FIG. 5 illustrates signaling for another implementation of the invention and, in particular, an embodiment using a direct call model. As in FIG. 4, shown schematically are a caller (UA1) 202 a, called party (UA2) 202 b, a router 108 a, a client (local) gatekeeper (GK) 208 a and a backup gatekeeper (GKB) 107. In 502, the UA1 sends an ARQ message requesting that a call to endpoint UA2 be allowed using a direct call model. The ARQ message is to be routed by the router or proxy server to the gatekeeper GK. Either the router or the proxy server determines, however, that the client gatekeeper GK is not in service. The backup gatekeeper GKB receives the ARQ message from the router in 504, and, in 506, accesses the gatekeeper profile database to identify the services to be provided for the non-functioning gatekeeper GK. In 508, the backup gatekeeper GKB responds with an ACF message to the endpoint UA1. The ACF message includes a Call Signaling Transport Channel Address of the endpoint UA2. In response to the ACF message, the endpoint UA1 sends an H.225.0 Setup message 510 directly to endpoint UA2. In response to the setup message, the endpoint UA2 conducts an ARQ/ACF exchange 512 with the gatekeeper GKB (a router on its end, not shown, having identified that the backup is to be used). Next, the endpoint UA2 sends an H.225.0 Connect message 510 to the endpoint UA1 to progress the call to a connect state. The endpoint UA1 and UA2 then exchange H.245 terminal capability messages 516. The endpoints next exchange H.245 master-slave determination messages 518 and any other needed H.245 messages, and establish the media channel 520.
 The invention described in the above detailed description is not intended to be limited to the specific form set forth herein, but is intended to cover such alternatives, modifications and equivalents as can reasonably be included within the spirit and scope of the appended claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US2151733||May 4, 1936||Mar 28, 1939||American Box Board Co||Container|
|CH283612A *||Title not available|
|FR1392029A *||Title not available|
|FR2166276A1 *||Title not available|
|GB533718A||Title not available|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US6938182 *||Dec 31, 2001||Aug 30, 2005||Cisco Technology, Inc.||System and method for providing reliable telephony web-based features|
|US7203166 *||Oct 28, 2005||Apr 10, 2007||At&T Corp.||Method for providing voice-over-IP service|
|US7353293 *||Nov 29, 2002||Apr 1, 2008||Siemens Aktiengesellschaft||Method for making available features for alternative connections of primary connections|
|US7602704 *||Aug 20, 2002||Oct 13, 2009||Cisco Technology, Inc.||System and method for providing fault tolerant IP services|
|US7685284||Feb 2, 2006||Mar 23, 2010||Nec Corporation||Network, network terminal device, IP address management method using the same, and program therefor|
|US7756139 *||Nov 21, 2005||Jul 13, 2010||Electronics And Telecommunications Research Institute||Apparatus and method for converting megaco protocol|
|US7773734 *||Dec 30, 2005||Aug 10, 2010||At&T Intellectual Property Ii, L.P.||Method and apparatus for advancing a call setup signaling message|
|US7817542 *||Jun 21, 2007||Oct 19, 2010||Huawei Technologies Co., Ltd||Method and network device for fast service convergence|
|US7848229 *||May 16, 2003||Dec 7, 2010||Siemens Enterprise Communications, Inc.||System and method for virtual channel selection in IP telephony systems|
|US8125888 *||Aug 23, 2006||Feb 28, 2012||Multi-Tech Systems, Inc.||Session initiation protocol survivable server|
|US8203946||Jul 29, 2008||Jun 19, 2012||At&T Intellectual Property Ii, L.P.||Method for providing voice-over-IP service|
|US8948045 *||Jun 8, 2006||Feb 3, 2015||Alcatel Lucent||Communication system and method of configuring a communication interface|
|US20040190442 *||Dec 24, 2003||Sep 30, 2004||Lg Electronics Inc.||Gatekeeper cluster and method for operating the same in communication system|
|US20040193951 *||Dec 31, 2001||Sep 30, 2004||Shmuel Shaffer||System and method for providing reliable telephony web-based features|
|US20040228327 *||May 16, 2003||Nov 18, 2004||Anil Punjabi||System and method for virtual channel selection in IP telephony systems|
|US20050021849 *||Nov 29, 2002||Jan 27, 2005||Walter Hipfinger||Method for making available features for alternative connections of primary connections|
|US20060109862 *||Nov 21, 2005||May 25, 2006||Seung-Han Choi||Apparatus and method for converting megaco protocol|
|US20060173988 *||Feb 2, 2006||Aug 3, 2006||Tetsuya Yamashita||Network, network terminal device, IP address management method using the same, and program therefor|
|US20070047571 *||Aug 23, 2006||Mar 1, 2007||Kandikonda Prasad V||Session initiation protocol survivable server|
|US20070286094 *||Jun 8, 2006||Dec 13, 2007||Alcatel||Communication system and method of configuring a communication interface|
|EP1689147A2 *||Feb 2, 2006||Aug 9, 2006||NEC Corporation||Network, network terminal and program for IP address management|
|U.S. Classification||370/352, 370/401|
|International Classification||H04M3/12, H04L29/06, H04M7/00|
|Cooperative Classification||H04M7/006, H04M3/12, H04L65/1009, H04L29/06027|
|European Classification||H04M7/00M, H04L29/06C2, H04L29/06M2H4|
|Aug 20, 2001||AS||Assignment|
Owner name: SIEMENS INFORMATION AND COMMUNICATION NETWORKS, IN
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BEYDA, WILLIAM J.;REEL/FRAME:012111/0485
Effective date: 20010817