System and method for call forwarding synchronization in a communication system

Abstract

In one aspect of the invention, a method for call forwarding synchronization includes allowing a telephone subsystem to forward calls for a telephonic device to a first call forwarding destination. The method also includes allowing a wireless subsystem to forward calls for a mobile station to a second call forwarding destination. The mobile station is associated with the telephonic device. The method further includes determining a registration state of the mobile station. In addition, the method includes synchronizing the call forwarding destinations for the mobile station and the telephonic device in response to a change to at least one of the registration state, the first call forwarding destination, and the second call forwarding destination.

Description

CROSS-REFERENCE TO OTHER APPLICATIONS

[0001] This application shares a common specification with U.S. application Ser. No. ______filed on Feb. 12, 2001 for a “System and Method for Call Forwarding in a Communication System.”

TECHNICAL FIELD OF THE INVENTION

[0002] This invention relates generally to the field of communication systems, and more particularly to a system and method for call forwarding synchronization in a communication system.

BACKGROUND OF THE INVENTION

[0003] Call forwarding is a feature typically supported in many communication systems. Call forwarding allows a user in the communication system to forward telephone calls directed at one telephone device to another telephone device. To use the call forwarding feature, the user or “subscriber” typically needs to enter a code in the telephone being forwarded and instruct the telephone system where to forward the calls.

[0004] A problem with conventional communication systems is that the user typically needs to manually activate and deactivate the call forwarding feature. For example, an employee of a company may have a wireless mobile phone, also called a “mobile station,” and a desk phone. To forward calls from the desk phone to the mobile phone, the employee needs to manually instruct the telephone system to forward calls for the desk phone to the mobile phone. If the employee wants to deactivate the call forwarding feature before leaving work, the employee must pick up a phone and manually deactivate the call forwarding feature in the telephone system. This is a time consuming process. If the employee often changes locations throughout the day, it becomes even more time consuming to forward and unforward multiple telephones.

[0005] Because the user typically must activate and deactivate the call forwarding feature manually, the user may forgot to turn the call forwarding feature for one or more telephones on or off. As a result, the call forwarding for the telephones may become unsynchronized. For example, a user's mobile phone may be forwarded to one location while the user's desk phone may be forwarded to another location. When the call forwarding becomes unsynchronized, the user may receive calls at unwanted times or at unwanted telephones. Also, a person attempting to contact the user may be unable to reach the user because calls to the user's telephones are being forwarded to different locations.

[0006] As a result of any of these or other disadvantages, previous call forwarding synchronization techniques have been inadequate in many communication systems.

SUMMARY OF THE INVENTION

[0007] In accordance with the present invention, a system and method for call forwarding synchronization in a communication system are provided that substantially eliminate or reduce disadvantages and problems associated with conventional systems. In particular, a communication system helps to ensure that a mobile station and a telephonic device are either forwarded to the same location, or one of the devices is forwarded to the other device.

[0008] According to one embodiment of the present invention, a system for call forwarding synchronization includes a telephone subsystem operable to communicate with a telephonic device. The telephone subsystem is also operable to forward calls for the telephonic device to a first call forwarding destination. The system also includes a wireless subsystem operable to communicate with a mobile station. The mobile station is associated with the telephonic device. The wireless subsystem is also operable to forward calls for the mobile station to a second call forwarding destination. The wireless subsystem is further operable to determine a registration state of the mobile station and to synchronize the call forwarding destinations for the mobile station and the telephonic device in response to a change to at least one of the registration state, the first call forwarding destination, and the second call forwarding destination.

[0009] In another embodiment of the invention, a method for call forwarding synchronization includes allowing a telephone subsystem to forward calls for a telephonic device to a first call forwarding destination. The method also includes allowing a wireless subsystem to forward calls for a mobile station to a second call forwarding destination. The mobile station is associated with the telephonic device. The method further includes determining a registration state of the mobile station. In addition, the method includes synchronizing the call forwarding destinations for the mobile station and the telephonic device in response to a change to at least one of the registration state, the first call forwarding destination, and the second call forwarding destination.

[0010] In yet another embodiment of the invention, a system for call forwarding synchronization includes a telephone subsystem operable to communicate with a telephonic device. The telephone subsystem is also operable to forward calls for the telephonic device to a first call forwarding destination. The system also includes a client operable to communicate with the telephonic subsystem. The client is associated with the telephonic device. The system further includes a gateway operable to communicate with the client. In addition, the system includes a gatekeeper operable to instruct the gateway to forward calls for the client to a second call forwarding destination. The gatekeeper is also operable to determine an activation state of the client and to synchronize the call forwarding destinations for the telephonic device and the client in response to a change to at least one of the activation state, the first call forwarding destination, and the second call forwarding destination.

[0011] Numerous technical advantages are provided according to various embodiments of the present invention. Particular embodiments of the invention may exhibit none, some, or all of the following advantages. For example, in one embodiment, a system for call forwarding synchronization is provided. In a particular embodiment, the system helps to synchronize the call forwarding destinations of a telephonic device and a mobile station when the mobile station registers with the communication system. For example, after detecting the mobile station registration, the system may determine whether the mobile station and the telephonic device are forwarded to the same location, or whether one of the devices is forwarded to the other device. If not, the system forwards one of the devices to the appropriate location. By detecting the registration of the mobile station in the communication system and synchronizing the call forwarding destinations, the system reduces or eliminates the need for the subscriber to manually synchronize the call forwarding destinations. The system may forward telephone calls to the subscriber's mobile station, the subscriber's telephonic device, or another location without having to wait for the subscriber to manually forward the calls. The system may also change or deactivate the call forwarding feature when needed to maintain synchronization between the mobile station and the telephonic device. This also reduces or eliminates the need for the subscriber to manually deactivate or change the call forwarding feature.

[0012] Another advantage of at least some embodiments of the invention is that the subscriber may be contacted using a single telephone number and/or extension number. In a particular embodiment, the system helps to ensure that a telephonic device and a mobile station are forwarded to the same destination, or that one of the devices is forwarded to the other. As a result, a person attempting to contact the subscriber may need to dial only one telephone number to reach the subscriber. By maintaining synchronization between the call forwarding destinations, the system helps to ensure that a telephone call to the subscriber is delivered to the same destination, whether the person calling the subscriber dials the subscriber's mobile station or telephonic device. This helps to increase the ease at which the subscriber may be contacted.

[0013] Other technical advantages are readily apparent to one of skill in the art from the attached figures, description, and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

[0014] To provide a more complete understanding of the present invention and features and advantages thereof, reference is made to the following description in conjunction with the accompanying drawings, in which:

[0015] FIG. 1 is a block diagram illustrating an exemplary system for call forwarding;

[0016] FIG. 2 is a block diagram illustrating another exemplary system for call forwarding;

[0017] FIG. 3 is a flow diagram illustrating an exemplary method for call forwarding in a communication system;

[0018] FIG. 4 is a flow diagram illustrating an exemplary method for forwarding calls for a telephone to a mobile station;

[0019] FIG. 5 is a flow diagram illustrating another exemplary method for forwarding calls for a telephone to a mobile station;

[0020] 5 FIG. 6 is a flow diagram illustrating yet another exemplary method for forwarding calls for a telephone to a mobile station;

[0021] FIG. 7 is a flow diagram illustrating an exemplary method for synchronizing call forwarding in a communication system;

[0022] FIG. 8 is a flow diagram illustrating an exemplary method for establishing a call forwarding destination for a mobile station;

[0023] FIG. 9 is a flow diagram illustrating an exemplary method for establishing a call forwarding destination for a telephone associated with a mobile station;

[0024] FIG. 10 is a flow diagram illustrating another exemplary method for establishing a call forwarding destination for a telephone associated with a mobile station;

[0025] FIG. 11 is a flow diagram illustrating an exemplary method for establishing a call forwarding destination for a telephone associated with a deregistered mobile station;

[0026] FIG. 12 is a block diagram illustrating yet another exemplary system for call forwarding;

[0027] FIG. 13 is a block diagram illustrating still another exemplary system for call forwarding; and

[0028] FIG. 14 is a flow diagram illustrating another exemplary method for call forwarding in a communication system.

DETAILED DESCRIPTION OF THE INVENTION

[0029] FIG. 1 is a block diagram illustrating an exemplary system 100 for call forwarding. In the illustrated embodiment, system 100 includes a wireless subsystem 102, a packet subsystem 104, and a telephone subsystem 106. Other embodiments of system 100 may be used without departing from the scope of the present invention.

[0030] In one aspect of operation, one or more mobile stations 108 communicate with wireless subsystem 102, and one or more telephones 110 communicate with telephone subsystem 106. A mobile station 108 may be associated with one or more telephones 110, such as when a subscriber using mobile station 108 also has a desk telephone 110 in an office. When mobile station 108 registers with wireless subsystem 102 and/or packet subsystem 104, telephone calls directed at telephone 110 may be forwarded to mobile station 108. For example, a call forwarding feature (CF) 112 in telephone subsystem 106 may be used to forward calls for the associated telephone 110 to mobile station 108. When mobile station 108 deregisters with wireless subsystem 102 and/or packet subsystem 104, system 100 may stop forwarding calls for telephone 110 to mobile station 108. By forwarding telephone calls to mobile station 108 when mobile station 108 registers with system 100 and unforwarding telephone 110 when mobile station 108 deregisters with system 100, system 100 reduces or eliminates the need for a subscriber to manually forward and unforward telephone 110. This also reduces or eliminates the likelihood that the subscriber using mobile station 108 will forget to activate or deactivate the call forwarding feature. In addition, the subscriber using mobile station 108 may be contacted using a single telephone number and/or extension number. Because system 100 automatically forwards telephone calls for telephone 110 to mobile station 108, a person attempting to contact the subscriber need dial only one telephone number, and the subscriber will receive the telephone call on mobile station 108.

[0031] Wireless subsystem 102 is coupled to packet subsystem 104. In this document, the term “couple” refers to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another. Wireless subsystem 102 communicates with mobile station 108 over a wireless interface. Wireless subsystem 102 also allows mobile station 108 to communicate with telephone subsystem 106 through packet subsystem 104. Wireless subsystem 102 may, for example, receive information from mobile station 108 and communicate the information to packet subsystem 104. Wireless subsystem 102 may also receive information from packet subsystem 104 and communicate the information to mobile station 108. Wireless subsystem 102 may comprise any hardware, software, firmware, or combination thereof operable to communicate with mobile station 108 over a wireless interface. Wireless subsystem 102 may, for example, comprise a Global System for Mobile communication (GSM) system, an Electronic Industry Alliance/Telecommunication Industry Association (EIA/TIA) IS-136 system, or a Code Division Multiple Access (CDMA) system.

[0032] Packet subsystem 104 is coupled to wireless subsystem 102 and telephone subsystem 106. Packet subsystem 104 is operable to transfer information between wireless subsystem 102 and telephone subsystem 106. Packet subsystem 104 may, for example, transport datagrams containing information between wireless subsystem 102 and telephone subsystem 106. Packet subsystem 104 may comprise any hardware, software, firmware, or combination thereof operable to transport datagrams between wireless subsystem 102 and telephone subsystem 106. In one embodiment, packet subsystem 104 supports the International Telecommunications Union-Telecommunications (ITU-T) H.323 protocols to transport datagrams between wireless subsystem 102 and telephone subsystem 106.

[0033] Packet subsystem 104 may communicate with telephone subsystem 106 using one or more interfaces. In one embodiment, packet subsystem 104 communicates bearer traffic over an interface 114, and packet subsystem 104 communicates signaling information over interface 114 and/or a Computer Telephony Integration (CTI) interface 116. Interface 114 may comprise any suitable interface operable to transport bearer and/or signaling traffic, such as a trunk interface or a plurality of line interfaces. CTI interface 116 may, for example, comprise an Ethernet or an X.25 packet interface.

[0034] Packet subsystem 104 may communicate with wireless subsystem 102 using one or more clients 122. Client 122 may, for example, receive information from mobile station 108 through wireless subsystem 102, place the information into one or more datagrams, and communicate the datagrams across packet subsystem 104. Client 122 may also receive one or more datagrams over packet subsystem 104 from telephone subsystem 106, extract the information contained in the datagrams, and communicate the information to mobile station 108 through wireless subsystem 102. Client 122 may comprise any hardware, software, firmware, or combination thereof operable to facilitate communication between wireless subsystem 102 and packet subsystem 104. In one embodiment, client 122 comprises a wireless adjunct internet platform or other suitable gateway to wireless subsystem 102.

[0035] Telephone subsystem 106 is coupled to packet subsystem 104 and to one or more telephones 110. Telephone subsystem 106 facilitates communication with telephones 110. Telephone subsystem 106 may, for example, establish a telephone call between a first telephone 110a and a second telephone 110b. Telephone subsystem 106 may also facilitate communication between a telephone 110 and a mobile station 108 by communicating with packet subsystem 104 over interfaces 114 and/or 116. Telephone subsystem 106 may comprise any suitable hardware, software, firmware, or combination thereof operable to facilitate communication between telephone 110 and mobile station 108. Telephone subsystem 106 may, for example, comprise a private branch exchange (PBX), a Key System, a central office switch, a wireless telephone switch, a packet-based soft switch, or any other suitable circuit-switched and/or packet-switched system.

[0036] In the illustrated embodiment, telephone subsystem 106 includes at least one processor 118 operable to execute instructions stored in a memory 120, and packet subsystem 104 includes at least one processor 124 operable to execute instructions stored in a memory 126. In a particular embodiment, processor 118 may be operable to execute a CTI server software program to support CTI interface 116, and processor 124 may be operable to execute a corresponding CTI client software package to support CTI interface 116. The CTI software may, for example, implement the European Computer Manufacturers Association (ECMA) standards ECMA-179 and ECMA-180 for Computer Supported Telecommunications Applications (CSTA). In a particular embodiment, processors 118 and 124 execute the CT CONNECT software package. Processors 118 and 124 may use the CTI interface, for example, to activate and deactivate call forwarding feature 112 or otherwise control telephone subsystem 106.

[0037] Mobile station 108 communicates with wireless subsystem 102 over a wireless interface. Mobile station 108 may comprise any suitable wireless device operable to communicate with and roam within wireless subsystem 102. Mobile station 108 may, for example, comprise a mobile telephone or a computer coupled to a wireless modem or radio unit. In one embodiment, mobile station 108 may register with wireless subsystem 102 using the method described in U.S. application Ser. No. ______ , entitled “Method and System for Selecting a Preferred Cell in a Wireless Communication System.” Mobile station 108 may also comprise a dual mode mobile station operable to communicate with wireless subsystem 102 using a first protocol and with a public network using a second protocol. In a particular embodiment, mobile station 108 comprises a dual mode GSM/IS-136 mobile handset. Other embodiments of mobile station 108 may be used without departing from the scope of the present invention.

[0038] Telephone 110 is coupled to telephone subsystem 106. Telephone 110 may comprise any suitable wireline or wireless telephonic device operable to communicate with telephone subsystem 106. In this document, the phrase “telephonic device” refers to any hardware, software, firmware, or combination thereof operable to provide voice phone services. Telephone 110 may, for example, comprise a fixed telephone, a wireless mobile station, a voice over packet telephone, or a computer executing a telephonic application.

[0039] In one aspect of operation, mobile station 108 may be associated with one or more telephones 110. In one embodiment, mobile station 108 is associated with one telephone 110. Mobile station 108 may register with system 100, such as when mobile station 108 is turned on or roams into wireless subsystem 102. When mobile station 108 registers with system 100, packet subsystem 104 signals telephone subsystem 106 to forward calls for the associated telephone 110 to mobile station 108. While mobile station 108 is registered in system 100, each call for the subscriber is directed to mobile station 108. For example, if a call is made to the subscriber's telephone 110, the call is forwarded to the subscriber's mobile station 108 through the packet subsystem 104 and the wireless subsystem 102. If another mobile station 108 calls the subscriber's mobile station 108 or the subscriber's telephone 110, the call is routed through wireless subsystem 102 without being routed through telephone subsystem 106.

[0040] Mobile station 108 may also deregister with system 100, such as when mobile station 108 is turned off or roams out of wireless subsystem 102. When mobile station 108 deregisters with system 100, packet subsystem 104 signals telephone subsystem 106 to stop forwarding calls for the associated telephone 110 to mobile station 108. In a particular embodiment, packet subsystem 104 also forwards calls for the deregistered mobile station 108 to the telephone 110 associated with mobile station 108. In this embodiment, while mobile station 108 is deregistered with system 100, each call for the subscriber is directed to telephone 110. If a call is made to the subscriber's mobile station 108, the call is routed to telephone 110 through packet subsystem 104 and telephone subsystem 106.

[0041] System 100 may use any suitable method to forward calls for a telephone 110 to a mobile station 108. In one embodiment, as mobile station 108 registers and deregisters with system 100, processor 124 may instruct processor 118 over CTI interface 116 or interface 114 to activate or deactivate the call forwarding feature 112. When mobile station 108 is registered, processor 118 may forward calls for telephone 110 to packet subsystem 104, which communicates the calls to mobile station 108 through wireless subsystem 102.

[0042] In another embodiment, processor 124 may use a remote call forwarding feature 128 in telephone subsystem 106 to forward calls for telephone 110 to mobile station 108. Remote call forwarding feature 128 may, for example, allow one telephone 110 to activate or deactivate the call forwarding feature 112 for another telephone 110. Using remote call forwarding feature 128, processor 124 may instruct processor 118 to forward calls for telephone 110 to packet subsystem 104, which communicates the call to mobile station 108.

[0043] In yet another embodiment, processor 124 may instruct processor 118 to monitor a telephone 110 using a monitoring feature (MF) 130. When processor 118 detects an incoming call for a telephone 110 using monitoring feature 130, processor 118 informs processor 124 of the call. If the mobile station 108 associated with the telephone 110 is registered in system 100, processor 124 instructs processor 118 to deflect the call to packet subsystem 104 through interface 114 using a deflection feature (DF) 132. Packet subsystem 104 receives the call over interface 114 and communicates the call to mobile station 108.

[0044] Although FIG. 1 illustrates one embodiment of system 100, various changes may be made to system 100 without departing from the scope of the present invention. For example, packet subsystem 104 may communicate with telephone subsystem 106 over interface 114, without the use of a CTI interface 116. Also, any suitable number and/or types of telephones 110 may be used with telephone subsystem 106, and any suitable number of mobile stations 108 may communicate with wireless subsystem 102. Further, although FIG. 1 illustrates wireless subsystem 102, packet subsystem 104, and telephone subsystem 106 as distinct entities, one or more of the subsystems may be combined without departing from the scope of the present invention. For example, packet subsystem 104 may be contained within wireless subsystem 102. In addition, functions described as residing within one element of system 100 may be implemented in other elements of system 100. Beyond that, the invention may be implemented in system 100 using any logic stored in at least one computer processable medium. The logic may be encoded in hardware, software instructions, and/or firmware instructions stored in any suitable device such as, for example, a random access memory (RAM), a read-only memory (ROM), an application-specific integrated circuit (ASIC), or a field programmable gate array (FPGA). Other changes may be made without departing from the scope of the present invention.

[0045] FIG. 2 is a block diagram illustrating another exemplary system 200 for call forwarding. In the illustrated embodiment, system 200 includes one or more base stations (BTS) 250, one or more Wireless Adjunct Internet Platforms (WARP) 252, a packet network 254, an integrated communications server 256, a gateway 258, and a PBX 260. Other embodiments of system 200 may be used without departing from the scope of the present invention.

[0046] Base station 250 is coupled to WARP 252. Base station 250 provides bidirectional communication with mobile stations 208 in a specified geographic area over a wireless interface 262. Base station 250 also transfers information between mobile station 208 and WARP 252. Base station 250 may comprise any hardware, software, firmware, or combination thereof operable to communicate with mobile stations 208 over a wireless interface. Base station 250 may, for example, comprise one or more transceivers operable to exchange circuit-switched and/or packet-switched information with mobile station 208.

[0047] Wireless interface 262 facilitates communication between mobile station 208 and base station 250. Wireless interface 262 may comprise any wireless interface operable to transfer circuit-switched and/or packet-switched information between mobile station 208 and base station 250. Interface 262 may, for example, comprise a GSM General Packet Radio Service (GSM/GPRS) interface or a GSM Enhanced Data rates for GSM Evolution (GSM/EDGE) interface.

[0048] WARP 252 is coupled to base station 250 by an interface 264 and to packet network 254. WARP 252 facilitates communication between mobile stations 208 and PBX 260 by transporting voice and/or data information between base station 250 and packet network 254. In one embodiment, WARP 252 communicates with mobile station 208 through base station 250 using a circuit-switched protocol, and WARP 252 communicates with packet network 254 using a packet-switched protocol. In this embodiment, WARP 252 also performs an interworking function to translate between the circuit-switched and packet-switched protocols. For example, WARP 252 may convert between the GSM 04.08 and 08.60 protocols used by mobile station 208 and the ITU-T H.323 protocols used by integrated communications server 256 and gateway 258. In addition, WARP 252 packetizes information from mobile station 208 into datagrams for transmission over packet network 254, and WARP 252 depacketizes information contained in datagrams received over packet network 254. WARP 252 may comprise any hardware, software, firmware, or combination thereof operable to facilitate communication between base station 250 and packet network 254.

[0049] Interface 264 is coupled to base station 250 and WARP 252. Interface 264 may comprise any suitable interface operable to transfer circuit-switched and/or packet-switched information between base station 250 and WARP 252. Interface 264 may, for example, comprise a GSM Abis wireline interface.

[0050] Packet network 254 is coupled to WARP 252, integrated communications server 256, and gateway 258. Packet network 254 transports datagrams from one network address in packet network 254 to another network address. In addition, packet network 254 may be coupled to and communicate with external data or voice networks, such as the Internet or a public land mobile network. Packet network 254 may comprise any suitable packet-switched network. Packet network 254 may, for example, comprise a Local Area Network (LAN), a Wide Area Network (WAN), a Metropolitan Area Network (MAN), a portion of a global computer network such as the Internet, or any other communications system or systems at one or more locations.

[0051] In the illustrated embodiment, integrated communications server 256 includes a gatekeeper 266, a Wireless Application Protocol (WAP) server 268, a subscriber location register (SLR) 270, and a teleworking server 272. Although FIG. 2 illustrates integrated communications server 256 as comprising all four of these components, any or all of these components may be implemented on a separate platform or platforms without departing from the scope of the present invention.

[0052] Gatekeeper 266 provides call control services for mobile stations 208, WARPs 252, and gateway 258. For example, gatekeeper 266 tracks the location of mobile stations 208, and gatekeeper 266 routes calls for a mobile station 208 to and from the WARP 252 currently serving that mobile station 208. This allows subscribers using mobile stations 208 to roam between geographic areas covered by different base stations 250. Gatekeeper 266 also performs address translation to convert the phone number associated with mobile station 208 to a network address of WARP 252 serving that mobile station 208. In addition, gatekeeper 266 performs call forwarding functions in system 200. Gatekeeper 266 may, for example, instruct PBX 260 to forward calls for a telephone 210 to a mobile station 208. Gatekeeper 266 may communicate signaling information to PBX 260 over CTI interface 216 or through gateway 258. Gatekeeper 266 may comprise any hardware, software, firmware, or combination thereof operable to provide call control services in system 200.

[0053] WAP server 268 stores subscriber information used to allow mobile stations 208 to execute data-based applications and receive data-based services. WAP server 268 may, for example, allow mobile stations 208 to send and receive e-mail, access an enterprise's intranet such as packet network 254, or access the Internet. WAP server 268 may comprise any suitable hardware, software, firmware, or combination thereof operable to provide WAP functionality to mobile stations 208.

[0054] Subscriber location register 270 stores subscriber management information for mobile stations 208. For example, subscriber location register 270 may store general subscriber management information downloaded from a public network when mobile station 208 roams into system 200. Subscriber location register 270 also stores each subscriber's extension number, direct dial number, and any other information that is specific to system 200. Subscriber location register 270 may comprise any hardware, software, firmware, or combination thereof operable to store subscriber management information. Subscriber location register 270 may, for example, comprise a SUN workstation with a database.

[0055] Teleworking server 272 supports teleworking services in system 200. Teleworking server 272 may, for example, allow a user of system 200 to access information and/or communication capabilities of system 200 from remote locations. The user of telephone 210 may access teleworking server 272 and inform teleworking server 272 of the user's current location. Teleworking server 272 may allow the user to use a remote telephone and to receive the same features as if the user was using telephone 210, even if the remote telephone is outside of system 200. Teleworking server 272 may comprise any hardware, software, firmware, or combination thereof operable to provide teleworking services in system 200.

[0056] Gateway 258 is coupled to packet network 254 and PBX 260. Gateway 258 may also be coupled to a public network, such as a public switched telephone network. Gateway 258 transfers information between packet network 254 and PBX 260. In one embodiment, gateway 258 communicates with packet network 254 using a packet-switched protocol and with PBX 260 using a circuit-switched protocol. In this embodiment, gateway 258 also performs an interworking function to translate between the packet-switched and circuit-switched protocols. In a particular embodiment, gateway 258 converts between the ITU-T H.323 protocols used by WARP 252 and integrated communications server 256 and the circuit-switched protocols used by PBX 260. In addition, gateway 258 packetizes information into datagrams for transmission over packet network 254, and gateway 258 depacketizes information contained in datagrams received over packet network 254. Gateway 258 may communicate bearer and signaling information to PBX 260 over interface 214. Gateway 258 may comprise any hardware, software, firmware, or combination thereof operable to facilitate communication between packet network 254 and PBX 260.

[0057] PBX 260 is coupled to gateway 258 and to one or more telephones 210. PBX 260 may also be coupled to one or more public networks, such as a public land mobile network and a public switched telephone network. PBX 260 transfers information between telephones 210 and/or between gateway 258 and telephones 210. PBX 260 may comprise any suitable circuit-switched and/or packet-switched network operable to facilitate communication between telephone 210 and gateway 258.

[0058] In one aspect of operation, mobile station 208 may register with WARP 252, and WARP 252 informs gatekeeper 266 that mobile station 208 has registered in system 200. Registration may occur, for example, when a subscriber turns on mobile station 208 or roams into a geographic area monitored by base station 250. After registration, system 200 forwards calls for a telephone 210 associated with mobile station 208 to that mobile station 208. System 200 may also stop forwarding calls to mobile station 208 when mobile station 208 deregisters with system 200. Deregistration may occur, for example, when a subscriber turns off mobile station 208 or roams out of the geographic area monitored by base stations 250 in system 200. After deregistration, system 200 may route calls for the deregistered mobile station 208 to the telephone 210 associated with mobile station 208.

[0059] System 200 may use any suitable method for forwarding calls directed at a telephone 210 to a mobile station 208. In one embodiment, PBX 260 includes a call forwarding feature 212, such as a Call Forward Unconditional feature. This feature 212 may, for example, be supported by CTI software stored in memory 220 and executed by processor 218 in PBX 260. In a particular embodiment, WARP 252 and/or gatekeeper 266 instructs PBX 260 to invoke feature 212 and forward calls for telephone 210 to gateway 258. For example, processor 224 in gatekeeper 266 may execute CTI software stored in memory 226, and processor 224 may instruct processor 218 in PBX 260 to activate or deactivate call forwarding feature 212. Gateway 258 receives and forwards the calls to mobile station 208 over packet network 254, WARP 252, and base station 250. WARP 252 or gatekeeper 266 may instruct PBX 260 to invoke call forwarding feature 212 and forward calls to gateway 258 using the CTI interface 216 or through an administration port (ADMIN) 278.

[0060] In another embodiment, WARP 252 and/or gatekeeper 266 may include a telephone emulator card 274. Card 274 appears to PBX 260 as a telephone 210. In this embodiment, PBX 260 may support a Remote Call Forwarding feature (RCF) 228, which allows call forwarding feature 212 to be activated and deactivated from another telephone 210. Using the telephone emulator card 274, WARP 252 or gatekeeper 266 instructs PBX 260 to activate or deactivate call forwarding feature 212 using the remote call forwarding feature 228.

[0061] In yet another embodiment, PBX 260 may support a call monitoring feature 230 and a call deflection feature 232. These features may, for example, be supported by CTI software stored in memory 220 and executed by processor 218. Processor 218 in PBX 260 may monitor a telephone 210 using monitoring feature 230 and wait for an alert event, which indicates that an incoming call for telephone 210 exists. When processor 218 detects an alert event for a monitored telephone 210, processor 224 determines if the mobile station 208 associated with telephone 210 is registered in system 200. If the mobile station 208 is registered, processor 224 instructs processor 218 in PBX 260 to deflect the incoming call to gateway 258 over interface 214 using deflection feature 232.

[0062] In still another embodiment, when mobile station 208 registers in system 200, WARP 252 or gatekeeper 266 may instruct teleworking server 272 to treat mobile station 208 as a remote location for telephone 210. Teleworking server 272 then instructs PBX 260 to forward calls for telephone 210 to mobile station 208 using remote call forwarding feature 228.

[0063] Although FIG. 2 illustrates one embodiment of system 200, various changes may be made to system 200 without departing from the scope of the present invention. For example, any number of base stations 250 may be coupled to each WARP 252, and any number of WARPs 252 may be coupled to packet network 254. Also, although FIG. 2 illustrates a PBX 260 coupled to gateway 258, other telephone systems may be coupled to gateway 258, such as a Key System, a central office switch, a wireless telephone switch, a packet-based soft switch, or any other suitable circuit-switched and/or packet-switched system. Further, although gatekeeper 266 and gateway 258 are illustrated as separate entities, both may be implemented in an integrated platform. In addition, functions described as residing within one element of system 200 may be implemented in other elements of system 200. Beyond that, the invention may be implemented in system 200 using any logic stored in at least one computer processable medium. Other changes may be made to system 200 without departing from the scope of the present invention.

[0064] FIG. 3 is a flow diagram illustrating an exemplary method 300 for call forwarding in a communication system. System 100 directs calls to a telephone 110 in a telephone subsystem 106 at step 302. This may include, for example, telephone subsystem 106 receiving a call from a public network, another telephone 110 in telephone subsystem 106, or a mobile station 108. System 100 detects a mobile station 108 associated with a telephone 110 at step 304. This may include, for example, mobile station 108 registering with wireless subsystem 102 and/or packet subsystem 104, such as by communicating a registration signal to wireless subsystem 102. System 100 forwards calls for the telephone 110 in the telephone subsystem 106 to the mobile station 108 at step 306. This may include, for example, wireless subsystem 102 and/or packet subsystem 104 instructing telephone subsystem 106 to forward calls for telephone 110 to mobile station 108. System 100 loses contact with mobile station 108 at step 308. This may include, for example, mobile station 108 deregistering from system 100, such as when a subscriber turns off mobile station 108 or roams outside the geographic area covered by wireless subsystem 102. System 100 stops forwarding calls for telephone 110 to mobile station 108 at step 310. This may include, for example, wireless subsystem 102 and/or packet subsystem 104 clearing the call forwarding feature in telephone subsystem 106.

[0065] Although FIG. 3 has been described with respect to system 100, method 300 may be used with any suitable communication system. Method 300 may be used, for example, in a system having a packet subsystem 104 and a telephone subsystem 106, without a wireless subsystem 102. In this embodiment, method 300 may forward calls directed at telephone 110 to a packet-based client coupled to packet subsystem 104.

[0066] FIG. 4 is a flow diagram illustrating an exemplary method 400 for forwarding calls for a telephone to a mobile station. A mobile station 208 registers with system 200 at step 402. This may include, for example, a subscriber turning on mobile station 208 or roaming into the geographic area covered by system 200. This may also include mobile station 208 communicating a registration signal to base station 250, which communicates the signal to WARP 252. WARP 252 may then inform gatekeeper 266 of the registration. System 200 instructs PBX 260 to forward telephone calls for a telephone 210 associated with mobile station 208 to mobile station 208 at step 404. This may include, for example, gatekeeper 266 or WARP 252 invoking one or more features 212, 228, 230, 232 of PBX 260 using at least one of CTI interface 216, trunk or line interface 214, administration port 278, teleworking server 272, and telephone emulator card 274. PBX 260 forwards calls for telephone 210 to mobile station 208 at step 406. This may include, for example, PBX 260 receiving a telephone call for a telephone 210 and forwarding the call to gateway 258.

[0067] FIG. 5 is a flow diagram illustrating another exemplary method 500 for forwarding calls for a telephone 210 to a mobile station 208. A mobile station 208 registers with system 200 at step 502. This may include, for example, a subscriber turning on mobile station 208 or roaming into range of a base station 250 in system 200. This may also include mobile station 208 communicating a registration message to base station 250, base station 250 forwarding the information to WARP 252, and WARP 252 informing gatekeeper 266 of the registration. System 200 instructs PBX 260 to monitor a telephone 210 at step 504. This may include, for example, a processor 224 in WARP 252 or gatekeeper 266 instructing a processor 218 in PBX 260 to monitor a particular telephone 210 using monitoring feature 230. PBX 260 listens for an alert event at step 506. An alert event is generated when an incoming call for a telephone 210 has been received by PBX 260. PBX 260 detects an alert at step 508. This indicates that someone has placed an incoming call to telephone 210, and an alert signal has been communicated to telephone 210 to cause telephone 210 to ring. PBX 260 deflects the incoming call from the monitored telephone 210 to mobile station 208 at step 510. This may include, for example, processor 218 in PBX 260 redirecting the incoming call using deflection feature 232 to gateway 258, which forwards the incoming call to mobile station 208.

[0068] FIG. 6 is a flow diagram illustrating yet another exemplary method 600 for forwarding calls for a telephone 210 to a mobile station 208. Mobile station 208 registers with system 200 at step 602. This may include, for example, a subscriber turning on mobile station 208 or roaming into system 200. Teleworking server 272 is instructed to treat mobile station 208 as a remote location for a telephone 210 at step 604. This may include, for example, mobile station 208, WARP 252, and/or gatekeeper 266 communicating the instructions to teleworking server 272. Teleworking server 272 instructs PBX 260 to forward calls for telephone 210 to mobile station 208 at step 606. This may include, for example, teleworking server 272 instructing PBX 260 to forward the calls to gateway 258 using remote call forwarding feature 228 and call forwarding feature 212. PBX 260 forwards calls for telephone 210 to mobile station 208 at step 608. This may include, for example, PBX 260 forwarding the calls for telephone 210 to gateway 258, which forwards the calls to mobile station 208.

[0069] FIG. 7 is a flow diagram illustrating an exemplary method 700 for synchronizing call forwarding in a communication system. A mobile station 208 registers with system 200 at step 702. This may include, for example, mobile station 208 being turned on or roaming into system 200. System 200 synchronizes the call forwarding destinations in the different components of system 200 at step 704. If neither mobile station 208 nor telephone 210 is forwarded to a specific destination, this may include system 200 forwarding telephone 210 to mobile station 208. If one of mobile station 208 or telephone 210 is forwarded to a specific destination, this may include ensuring that both mobile station 208 and telephone 210 are forwarded to the same destination. If mobile station 208 and telephone 210 are forwarded to different destinations, this may include forwarding one of the devices 208, 210 to the destination of the other 210, 208.

[0070] A change to the call forwarding feature in either telephone 210 or mobile station 208 is made at step 706. This may include, for example, a subscriber forwarding mobile station 208 or telephone 210 to a new destination. System 200 maintains call forwarding synchronization at step 708. This may include, for example, ensuring either that mobile station 208 and telephone 210 are forwarded to the same destination, telephone 210 is forwarded to mobile station 208, or mobile station 208 is forwarded to telephone 210. Mobile station 208 deregisters with system 200 at step 710. This may include, for example, a subscriber turning off mobile station 208 or roaming outside of system 200. System 200 restores the call forwarding in system 200 at step 712. This may include, for example, system 200 determining if telephone 210 is forwarded to mobile station 208 or to another destination. If telephone 210 is forwarded to mobile station 208, system 200 turns the call forwarding feature off for telephone 210. Otherwise, system 200 does not change the call forwarding destination for telephone 210.

[0071] Although FIG. 7 has been described with respect to system 200, method 700 may be used with any suitable communication system. Method 700 may be used, for example, in a system having a packet subsystem 104 and a telephone subsystem 106, without a wireless subsystem 102. In this embodiment, method 700 may synchronize call forwarding for a telephone 110 and a packet-based client coupled to packet subsystem 104. Method 700 could also be used in a system having a wireless subsystem 102 and a telephone subsystem 106, without a packet subsystem 104.

[0072] FIG. 8 is a flow diagram illustrating an exemplary method 800 for establishing a call forwarding destination for a mobile station 208. Telephone 210 is forwarded to a specific destination, called “location X,” at step 802. This may include, for example, a user of telephone 210 manually forwarding telephone 210 to the specific destination. Mobile station 208 registers with system 200 at step 804. System 200 forwards calls for mobile station 208 to the specific destination at step 806. This may include, for example, gatekeeper 266 and/or WARP 252 receiving the specific destination from PBX 260. This may also include WARP 252 and/or gatekeeper 266 routing datagrams destined for mobile station 208 to the forwarded location. This helps to synchronize call forwarding in system 200 by ensuring that calls for the subscriber are routed to the same location, whether the incoming calls are directed at mobile station 208 or telephone 210.

[0073] The subscriber turns off the call forwarding feature for mobile station 208 at step 808. This may include the subscriber manually entering a code on mobile station 208 to deactivate the call forwarding. This may also include WARP 252 and/or gatekeeper 266 receiving the instruction to deactivate call forwarding for the mobile station 208. System 200 sets the call forwarding for the telephone 210 to the mobile station 208 at step 810. This may include, for example, WARP 252 and/or gatekeeper 266 instructing PBX 260 to forward calls for telephone 210 to mobile station 208. This also helps to synchronize call forwarding in system 200 by ensuring that calls for the subscriber are routed to the mobile station 208.

[0074] FIG. 9 is a flow diagram illustrating an exemplary method 900 for establishing a call forwarding destination for a telephone 210 associated with a mobile station 208. Method 900 begins at step 902, where the call forwarding feature of a mobile station 208 is turned off, or not set to a specified location. Mobile station 208 registers with system 200 at step 904, and system 200 forwards calls for the associated telephone 210 to the mobile station 208 at step 906. This helps to ensure call forward synchronization in system 200 by directing calls for the subscriber to the subscriber's mobile station 208.

[0075] The subscriber activates the call forwarding feature and forwards calls for mobile station 208 to a specific destination, labeled “location Y,” at step 908. This may include, for example, the subscriber manually entering a code on mobile station 208 to forward mobile station 208 to the specific destination. This may also include WARP 252 and/or gatekeeper 266 receiving the new destination for mobile station 208. System 200 forwards calls for the associated telephone 210 to the same destination at step 910. This may include, for example, WARP 252 and/or gatekeeper 266 instructing PBX 260 to forward calls for telephone 210 to the new destination. This helps to synchronize call forwarding in system 200 by ensuring that calls for the subscriber are forwarded to the same destination, whether the calls are directed at the subscriber's mobile station 208 or telephone 210.

[0076] FIG. 10 is a flow diagram illustrating another exemplary method 1000 for establishing a call forwarding destination for a telephone 210 associated with a mobile station 208. Mobile station 208 registers with system 200 at step 1002. A subscriber forwards calls for a telephone 210 associated with mobile station 208 to a specific destination, called “location Z,” at step 1004. System 200 also activates the call forwarding feature for mobile station 208 and forwards calls for mobile station 208 to the same specific destination at step 1006. Calls for the subscriber are forwarded to the destination at step 1008, whether the calls are directed at the mobile station 208 or the telephone 210.

[0077] Call forwarding is deactivated for the telephone 210 at step 1010, such as by manually deactivating the call forwarding feature. System 200 starts a timer at step 1012. Gatekeeper 266 and/or WARP 252 may set the timer to any suitable duration, such as fifteen seconds. System 200 determines if another call forwarding destination for telephone 210 is entered at step 1014. This may include, for example, WARP 252 and/or gatekeeper 266 determining if another destination has been entered. If another destination is entered before the timer elapses, system 200 sets the call forwarding destination for the telephone 210 to the new destination at step 1016. To maintain synchronization, system 200 also forwards mobile station 208 to the new destination at step 1018.

[0078] If system 200 does not detect a new destination at step 1014, system 200 checks whether the timer has elapsed at step 1020. If the timer has not elapsed, system 200 returns to step 1014 to await a new call forwarding destination. When the timer elapses, system 200 sets the call forwarding destination for telephone 210 to mobile station 208. System 200 maintains call forwarding synchronization by ensuring that calls for the subscriber are routed to the mobile station 208.

[0079] FIG. 11 is a flow diagram illustrating an exemplary method 1100 for establishing a call forwarding destination for a telephone 210 associated with a deregistered mobile station 208. A mobile station 208 deregisters with system 200 at step 1102. This may include, for example, a subscriber turning off mobile station 208 or roaming outside of system 200. System 200 determines if telephone 210 is forwarded at step 1104. This may include, for example, WARP 252 and/or gatekeeper 266 determining if the call forwarding feature 212 for telephone 210 has been activated. If telephone 210 is not forwarded, method 1100 ends. Call forwarding in system 200 is synchronized because telephone 210 is not forwarded to a deregistered mobile station 208.

[0080] If call forwarding for telephone 210 is active, system 200 determines if telephone 210 is forwarded to the mobile station 208 at step 1106. This may include, for example, WARP 252 and/or gatekeeper 266 determining if telephone 210 has been forwarded to gateway 258. If not, method 1100 ends. Call forwarding in system 200 is synchronized because telephone 210 is not forwarded to a deregistered mobile station 208. If telephone 210 is forwarded to the mobile station 208 at step 1106, system 200 deactivates the call forwarding for telephone 210 at step 1108. Because telephone 210 is forwarded to a deregistered mobile station 208, system 200 deactivates call forwarding for telephone 210 to maintain synchronization in system 200.

[0081] FIG. 12 is a block diagram illustrating yet another exemplary system 1200 for call forwarding. In the illustrated embodiment, system 1200 includes a base station 1250, a central office 1280, a cable box 1282, and a converter box 1284. Other embodiments of system 1200 may be used without departing from the scope of the present invention.

[0082] Central office 1280 is coupled to telephones 1210 and cable box 1282. Central office 1280 facilitates communication in system 1200, such as between two telephones 1210 or between a telephone 1210 and cable box 1282. Central office 1280 may comprise any suitable circuit-switched and/or packet-switched system, such as one or more Class 5 switches.

[0083] Cable box 1282 is coupled to central office 1280 and converter box 1284. Cable box 1282 facilitates communication between central office 1280 and converter box 1284. In one embodiment, cable box 1282 communicates with central office 1280 using a first protocol and with converter box 1284 using a second protocol. For example, cable box 1282 may communicate with converter box 1284 using a packet over cable protocol, and cable box 1282 may communicate with central office 1280 using a Bellcore GR-303 interface, a V5.2 interface, or a V5.3 interface. In this embodiment, cable box 1282 may convert and packetize information from central office 1280 for communication to converter box 1284. Cable box 1282 may also convert and depacketize information from converter box 1284 for communication to central office 1280. Cable box 1282 may comprise any hardware, software, firmware, or combination thereof operable to facilitate communication of voice information between central office 1280 and converter box 1284.

[0084] Converter box 1284 is coupled to cable box 1282, one or more devices 1286, and base station 1250. Converter box 1284 is operable to receive information from cable box 1282 and to communicate the information to one or more devices 1286 or base station 1250. In one embodiment, converter box 1284 may receive audio and video information, voice information, and/or data from cable box 1282. Converter box 1284 may communicate the audio and video information to a television 1286a, the voice information to a telephone 1286b or base station 1250, and the data to a computing device 1286c. Converter box 1284 may also receive information from devices 1286 and/or base station 1250, such as voice information from device 1286b and/or base station 1250. Converter box 1284 is operable to communicate the information to central office 1280 through cable box 1282.

[0085] In one aspect of operation, when mobile station 1208 comes within range of base station 1250, a signal may be sent through converter box 1284 and cable box 1282 to central office 1280. A call forwarding feature 1212 or other feature in central office 1280 may cause calls directed at a telephone 1210 to be forwarded to mobile station 1208. Also, because calls for telephone 1286b may be routed through central office 1280, call forwarding feature 1212 or another feature of central office 1280 may be used to forward calls for telephone 1286b to mobile station 1208. When mobile station 1208 roams outside of the range of base station 1250, a signal may be sent to central office 1280 instructing central office 1280 to stop forwarding calls to mobile station 1208.

[0086] In a particular embodiment, devices 1286 may be located in a residence 1292, such as a house or apartment. As an example, television 1286a may receive cable television services, phone 1286b may receive voice over cable services, and computing device 1286c may receive cable modem services through converter box 1284. To provide wireless services in residence 1292, a base station 1250, such as an antenna with a range of 300 feet, may be installed in residence 1292. When mobile station 1208 roams within the range of base station 1250, central office 1280 may be instructed to forward calls for a telephone 1210 to mobile station 1208. Telephone 1210 could, for example, represent a desk phone at the office of the subscriber using mobile station 1208, and calls directed to the subscriber's office would be forwarded to mobile station 1208. Also, because calls for telephone 1286b may be routed through central office 1280, central office 1280 may forward calls for telephone 1286b to mobile station 1208. This may allow, for example, all calls for the subscriber to be forwarded to mobile station 1208, whether the calls are directed at telephone 1210, telephone 1286b in residence 1292, or mobile station 1208.

[0087] Although FIG. 12 illustrates one embodiment of system 1200, various changes may be made to system 1200 without departing from the scope of the present invention. For example, system 1200 may include some or none of devices 1286. Also, in another embodiment, converter box 1284 may not possess the ability to directly communicate information to and receive information from base station 1250, and a WARP may be coupled between base station 1250 and converter box 1284 to facilitate communication.

[0088] FIG. 13 is a block diagram illustrating still another exemplary system 1300 for call forwarding. In the illustrated embodiment, system 1300 includes a voice over packet subsystem 1304 and a telephone subsystem 1306. Other embodiments of system 1300 may be used without departing from the scope of the present invention.

[0089] In the illustrated embodiment, telephone subsystem 1306 may be the same or similar to telephone subsystem 106 of FIG. 1 and/or PBX 260 of FIG. 2. For example, telephone subsystem 1306 may include a call forwarding feature 1312, a remote call forwarding feature 1328, a call monitoring feature 1330, a call deflection feature 1332, a processor 1318, and a memory 1320. Telephone subsystem 1306 may also communicate with one or more telephones 1310.

[0090] In the illustrated embodiment, packet subsystem 1304 includes a voice over packet client 1350, a gateway 1358, and a gatekeeper 1366. Client 1350 is coupled to gatekeeper 1366 and gateway 1358. Client 1350 facilitates the communication of packet voice information to telephone subsystem 1306. Client 1350 may, for example, receive voice information, packetize the information, and communicate the packets to gateway 1358. Client 1350 may also receive packets of voice information from gateway 1358 and extract the information. In one embodiment, client 1350 may operate in an active state or a non-active state. The active state indicates that calls directed at a telephone 1310 associated with client 1350 should be forwarded to client 1350. The non-active state indicates that calls directed at client 1350 should be forwarded to the telephone 1310 associated with client 1350. Client 1350 may comprise any hardware, software, firmware, or combination thereof operable to provide packet voice services in system 1300. Client 1350 may, for example, comprise a voice over packet telephone, a computing device, or a gateway operable to communicate with another communications system. In a particular embodiment, client 1350 comprises a Wireless Adjunct Internet Platform operable to facilitate communication between packet subsystem 1304 and a wireless system.

[0091] Gateway 1358 and gatekeeper 1366 may be the same or similar to gateway 258 and gatekeeper 266, respectively, of FIG. 2. In the illustrated embodiment, gatekeeper 1366 is coupled to client 1350, gateway 1358, and telephone subsystem 1306. Gatekeeper 1366 is operable to communicate signaling information to client 1350, gateway 1358, and telephone subsystem 1306. Gatekeeper 1366 may communicate the signaling information to telephone subsystem 1306 over CTI interface 1316 or through gateway 1358. Gatekeeper 1366 is also operable to instruct telephone subsystem 1306 to forward a call for a telephone 1310 to a client 1350 when client 1350 is in the active state. Gatekeeper 1366 is further operable to instruct gateway 1358 to forward a call for a client 1350 to a telephone 1310 when client 1350 is in the non-active state. Gatekeeper 1366 may comprise any hardware, software, firmware, or combination thereof operable to instruct telephone subsystem 1306 and/or gateway 1358 to forward calls in system 1300.

[0092] Gateway 1358 is coupled to client 1350, gatekeeper 1366, and telephone subsystem 1306. Gateway 1358 facilitates communication between client 1350 and telephone subsystem 1306. Gateway 1358 may, for example, receive packets containing voice information from client 1350, extract the voice information, and communicate the information to telephone subsystem 1306. Gateway 1358 may also receive voice information from telephone system 1306, packetize the information, and communicate the packets to client 1350. In addition, gateway 1358 may facilitate the communication of signaling information between gatekeeper 1366 and telephone subsystem 1306 over interface 1314. Gateway 1358 may comprise any hardware, software, firmware, or combination thereof operable to facilitate communication between client 1350 and telephone subsystem 1306.

[0093] In one aspect of operation, when client 1350 is activated, client 1350 registers with gatekeeper 1366. Gatekeeper 1366 instructs telephone subsystem 1306 to forward calls directed at the telephone 1310 associated with client 1350 to gateway 1358. Gatekeeper 1366 may also instruct gateway 1358 not to forward calls for client 1350 to telephone subsystem 1306. When telephone subsystem 1306 receives a call directed at client 1350 or the associated telephone 1310, telephone subsystem 1306 forwards the call to gateway 1358, which communicates the call to client 1350. If a second client 1350 attempts to call the first client 1350, the call may be routed through packet subsystem 1304 without being routed through telephone subsystem 1306.

[0094] When client 1350 is deactivated, or enters the non-active state, client 1350 deregisters with gatekeeper 1366. Gatekeeper 1366 instructs telephone subsystem 1306 to stop forwarding calls to client 1350, and gatekeeper 1366 instructs gateway 1358 to forward calls for client 1350 to the associated telephone 1310. If packet subsystem 1304 receives a call for the deactivated client 1350, such as from another client 1350, gatekeeper 1366 routes the call through telephone subsystem 1306 to the telephone 1310 associated with the deactivated client 1350.

[0095] In a particular embodiment, client 1350 comprises a gateway to a wireless network, such as a Wireless Adjunct Internet Platform. In this embodiment, client 1350 may operate in an active state when a mobile station is registered with the wireless network. Similarly, client 1350 may operate in a non-active state when no mobile stations are registered with the wireless network.

[0096] Gatekeeper 1366 may use any suitable method for instructing telephone subsystem 1306 to forward calls for a telephone 1310 to gateway 1358. Gatekeeper 1366 may, for example, use method 1400 illustrated in FIG. 14, or the methods illustrated in FIGS. 3-6 where client 1350 takes the place of the mobile station in methods 300-600. Also, system 1300 may use any suitable method for maintaining call forwarding synchronization. This may include, for example, system 1300 using the methods illustrated in FIGS. 7-11, with client 1350 taking the place of the mobile station in methods 700-1100.

[0097] Although FIG. 13 illustrates one embodiment of system 1300, various changes may be made without departing from the scope of the present invention. For example, any number and/or types of clients 1350 may be coupled to a gatekeeper 1366 and a gateway 1358. Also, any number of gatekeepers 1366 and/or gateways 1358 may be coupled to telephone subsystem 1306. Other changes may be made to system 1300 without departing from the scope of the present invention.

[0098] FIG. 14 is a flow diagram illustrating another exemplary method 1400 for call forwarding in a communications system. System 1300 determines the state of a client 1350 at step 1402. This may include, for example, gatekeeper 1366 determining if the client 1350 is registered with gatekeeper 1366. Registered clients 1350 may be in an active state, while unregistered clients 1350 are in the non-active state. System 1300 determines if client 1350 is in an active state at step 1404. If client 1350 is in an active state, system 1300 instructs telephone subsystem 1306 to forward calls directed at a telephone 1310 to the associated client 1350 at step 1406. This may include, for example, gatekeeper 1366 instructing telephone subsystem 1306 to forward calls for telephone 1310 using call forwarding feature 1312, remote call forwarding feature 1328, call monitoring feature 1330, and/or call deflection feature 1332. At this point, system 1300 may route calls for a user of client 1350 to client 1350, whether the calls are directed at client 1350 or telephone 1310.

[0099] If client 1350 is in the non-active state at step 1404, system 1300 instructs gateway 1358 to forward calls for client 1350 to telephone 1310 at step 1408. This may include, for example, gatekeeper 1366 instructing gateway 1358 to forward calls for client 1350 to telephone subsystem 1306. At this point, system 1300 routes calls for the user of client 1350 to the associated telephone 1310, whether the calls are directed at client 1350 or telephone 1310.

[0100] Although the present invention has been described with several embodiments, a number of changes, substitutions, variations, alterations, and modifications may be suggested to one skilled in the art, and it is intended that the invention encompass all such changes, substitutions, variations, alterations, and modifications that fall within the spirit and scope of the appended claims.

Claims

1. A method for call forwarding synchronization, comprising: allowing a telephone subsystem to forward calls for a telephonic device to a first call forwarding destination; allowing a wireless subsystem to forward calls for a mobile station to a second call forwarding destination, the mobile station associated with the telephonic device; determining a registration state of the mobile station; and synchronizing the call forwarding destinations for the mobile station and the telephonic device in response to a change to at least one of the registration state, the first call forwarding destination, and the second call forwarding destination.

2. The method of claim 1, wherein the first call forwarding destination is not set before registration of the mobile station; and wherein synchronizing the call forwarding destinations comprises: instructing the telephone subsystem upon registration of the mobile station to set the first call forwarding destination to the mobile station; and instructing the wireless subsystem to clear the second call forwarding destination.

3. The method of claim 1, wherein the first call forwarding destination is set to a destination other than the mobile station before registration of the mobile station; and wherein synchronizing the call forwarding destinations comprises instructing the wireless subsystem upon registration of the mobile station to set the second call forwarding destination to the same destination as the first call forwarding destination.

4. The method of claim 1, wherein the second call forwarding destination is set to a destination other than the telephonic device after registration of the mobile station; and wherein synchronizing the call forwarding destinations comprises instructing the telephone subsystem to set the first call forwarding destination to the same destination as the second call forwarding destination.

5. The method of claim 1, wherein the first call forwarding destination is set to a destination other than the mobile station after registration of the mobile station; and wherein synchronizing the call forwarding destinations comprises instructing the wireless subsystem to set the second call forwarding destination to the same destination as the first call forwarding destination.

6. The method of claim 1, wherein the second call forwarding destination is cleared after registration of the mobile station; and wherein synchronizing the call forwarding destinations comprises instructing the telephone subsystem to set the first call forwarding destination to the mobile station.

7. The method of claim 1, wherein the first call forwarding destination is cleared after registration of the mobile station; and wherein synchronizing the call forwarding destinations comprises: starting a timer; instructing the telephone subsystem to set the first call forwarding destination to the mobile station and instructing the wireless subsystem to clear the second call forwarding destination if a new destination is not provided before the timer elapses; and instructing the telephone subsystem to set the first call forwarding destination to the new destination and instructing the wireless subsystem to set the second call forwarding destination to the same destination as the first call forwarding destination if the new destination is provided before the timer elapses.

8. The method of claim 1, wherein synchronizing the call forwarding destinations comprises: determining upon deregistration of the mobile station if the first call forwarding destination is set to the mobile station; and instructing the telephone subsystem to clear the first call forwarding destination if the first call forwarding destination is set to the mobile station.

9. A system for call forwarding synchronization, comprising: at least one computer processable medium; and logic encoded on the at least one computer processable medium and operable to: allow a telephone subsystem to forward calls for a telephonic device to a first call forwarding destination; allow a wireless subsystem to forward calls for a mobile station to a second call forwarding destination, the mobile station associated with the telephonic device; determine a registration state of the mobile station; and synchronize the call forwarding destinations for the mobile station and the telephonic device in response to a change to at least one of the registration state, the first call forwarding destination, and the second call forwarding destination.

10. The system of claim 9, wherein the first call forwarding destination is not set before registration of the mobile station; and wherein the logic is operable to synchronize the call forwarding destinations by: instructing the telephone subsystem upon registration of the mobile station to set the first call forwarding destination to the mobile station; and instructing the wireless subsystem to clear the second call forwarding destination.

11. The system of claim 9, wherein the first call forwarding destination is set to a destination other than the mobile station before registration of the mobile station; and wherein the logic is operable to synchronize the call forwarding destinations by instructing the wireless subsystem upon registration of the mobile station to set the second call forwarding destination to the same destination as the first call forwarding destination.

12. The system of claim 9, wherein the second call forwarding destination is set to a destination other than the telephonic device after registration of the mobile station; and wherein the logic is operable to synchronize the call forwarding destinations by instructing the telephone subsystem to set the first call forwarding destination to the same destination as the second call forwarding destination.

13. The system of claim 9, wherein the first call forwarding destination is set to a destination other than the mobile station after registration of the mobile station; and wherein the logic is operable to synchronize the call forwarding destinations by instructing the wireless subsystem to set the second call forwarding destination to the same destination as the first call forwarding destination.

14. The system of claim 9, wherein the second call forwarding destination is cleared after registration of the mobile station; and wherein the logic is operable to synchronize the call forwarding destinations by instructing the telephone subsystem to set the first call forwarding destination to the mobile station.

15. The system of claim 9, wherein the first call forwarding destination is cleared after registration of the mobile station; and wherein the logic is operable to synchronize the call forwarding destinations by: starting a timer; instructing the telephone subsystem to set the first call forwarding destination to the mobile station and instructing the wireless subsystem to clear the second call forwarding destination if a new destination is not provided before the timer elapses; and instructing the telephone subsystem to set the first call forwarding destination to the new destination and instructing the wireless subsystem to set the second call forwarding destination to the same destination as the first call forwarding destination if the new destination is provided before the timer elapses.

16. The system of claim 9, wherein the logic is operable to synchronize the call forwarding destinations by: determining upon deregistration of the mobile station if the first call forwarding destination is set to the mobile station; and instructing the telephone subsystem to clear the first call forwarding destination if the first call forwarding destination is set to the mobile station.

17. A system for call forwarding synchronization, comprising: a telephone subsystem operable to communicate with a telephonic device, the telephone subsystem also operable to forward calls for the telephonic device to a first call forwarding destination; and a wireless subsystem operable to communicate with a mobile station, the mobile station associated with the telephonic device, the wireless subsystem also operable to forward calls for the mobile station to a second call forwarding destination, the wireless subsystem further operable to determine a registration state of the mobile station and to synchronize the call forwarding destinations for the mobile station and the telephonic device in response to a change to at least one of the registration state, the first call forwarding destination, and the second call forwarding destination.

18. The system of claim 17, wherein the first call forwarding destination is not set before registration of the mobile station; and wherein the wireless subsystem is operable to synchronize the call forwarding destinations by: instructing the telephone subsystem upon registration of the mobile station to set the first call forwarding destination to the mobile station; and clearing the second call forwarding destination.

19. The system of claim 17, wherein the first call forwarding destination is set to a destination other than the mobile station before registration of the mobile station; and wherein the wireless subsystem is operable to synchronize the call forwarding destinations by setting the second call forwarding destination to the same destination as the first call forwarding destination upon registration of the mobile station.

20. The system of claim 17, wherein the second call forwarding destination is set to a destination other than the telephonic device after registration of the mobile station; and wherein the wireless subsystem is operable to synchronize the call forwarding destinations by instructing the telephone subsystem to set the first call forwarding destination to the same destination as the second call forwarding destination.

21. The system of claim 17, wherein the first call forwarding destination is set to a destination other than the mobile station after registration of the mobile station; and wherein the wireless subsystem is operable to synchronize the call forwarding destinations by setting the second call forwarding destination to the same destination as the first call forwarding destination.

22. The system of claim 17, wherein the second call forwarding destination is cleared after registration of the mobile station; and wherein the wireless subsystem is operable to synchronize the call forwarding destinations by instructing the telephone subsystem to set the first call forwarding destination to the mobile station.

23. The system of claim 17, wherein the first call forwarding destination is cleared after registration of the mobile station; and wherein the wireless subsystem is operable to synchronize the call forwarding destinations by: starting a timer; instructing the telephone subsystem to set the first call forwarding destination to the mobile station and clearing the second call forwarding destination if a new destination is not provided before the timer elapses; and instructing the telephone subsystem to set the first call forwarding destination to the new destination and setting the second call forwarding destination to the same destination as the first call forwarding destination if the new destination is provided before the timer elapses.

24. The system of claim 17, wherein the wireless subsystem is operable to synchronize the call forwarding destinations by: determining upon deregistration of the mobile station if the first call forwarding destination is set to the mobile station; and instructing the telephone subsystem to clear the first call forwarding destination if the first call forwarding destination is set to the mobile station.

25. The system of claim 17, wherein the wireless subsystem comprises: a base station operable to communicate with the mobile station; a wireless adjunct internet platform operable to communicate with the base station; a gateway operable to communicate with the wireless adjunct internet platform and the telephone subsystem; and a gatekeeper operable to generate signaling messages to control the telephone subsystem.

26. The system of claim 25, wherein: the telephone subsystem comprises a private branch exchange; the wireless adjunct internet platform is operable to communicate with the mobile station through the base station using a Global System for Mobile communication (GSM) standard; and the wireless adjunct internet platform, the gateway, and the gatekeeper communication using an International Telecommunications Union-Telecommunications (ITU-T) H.323 standard.

27. A method for call forwarding synchronization, comprising: allowing a telephone subsystem to forward calls for a telephonic device to a first call forwarding destination; allowing a wireless subsystem to forward calls for a mobile station to a second call forwarding destination, the mobile station associated with the telephonic device; determining a registration state of the mobile station; instructing the telephone subsystem upon registration of the mobile station to set the first call forwarding destination to the mobile station and instructing the wireless subsystem to clear the second call forwarding destination if the first call forwarding destination is not set; instructing the wireless subsystem upon registration of the mobile station to set the second call forwarding destination to the same destination as the first call forwarding destination if the first call forwarding destination is set to a destination other than the mobile station; instructing the telephone subsystem to set the first call forwarding destination to the same destination as the second call forwarding destination if the second call forwarding destination is set to a destination other than the telephonic device after registration of the mobile station; instructing the wireless subsystem to set the second call forwarding destination to the same destination as the first call forwarding destination if the first call forwarding destination is set to a destination other than the mobile station after registration of the mobile station; instructing the telephone subsystem to set the first call forwarding destination to the mobile station if the second call forwarding destination is cleared after registration of the mobile station; instructing the telephone subsystem to set the first call forwarding destination to the mobile station and instructing the wireless subsystem to clear the second call forwarding destination if a new destination is not provided before a timer elapses when the first call forwarding destination is cleared after registration of the mobile station; instructing the telephone subsystem to set the first call forwarding destination to a new destination and instructing the wireless subsystem to set the second call forwarding destination to the same destination as the first call forwarding destination if a new destination is provided before the timer elapses when the first call forwarding destination is cleared after registration of the mobile station; and instructing the telephone subsystem upon deregistration of the mobile station to clear the first call forwarding destination if the first call forwarding destination is set to the mobile station.

28. A system for call forwarding synchronization, comprising: at least one computer processable medium; and logic encoded on the at least one computer processable medium and operable to: allow a telephone subsystem to forward calls for a telephonic device to a first call forwarding destination; allow a wireless subsystem to forward calls for a mobile station to a second call forwarding destination, the mobile station associated with the telephonic device; determine a registration state of the mobile station; instruct the telephone subsystem upon registration of the mobile station to set the first call forwarding destination to the mobile station and instructing the wireless subsystem to clear the second call forwarding destination if the first call forwarding destination is not set; instruct the wireless subsystem upon registration of the mobile station to set the second call forwarding destination to the same destination as the first call forwarding destination if the first call forwarding destination is set to a destination other than the mobile station; instruct the telephone subsystem to set the first call forwarding destination to the same destination as the second call forwarding destination if the second call forwarding destination is set to a destination other than the telephonic device after registration of the mobile station; instruct the wireless subsystem to set the second call forwarding destination to the same destination as the first call forwarding destination if the first call forwarding destination is set to a destination other than the mobile station after registration of the mobile station; instruct the telephone subsystem to set the first call forwarding destination to the mobile station if the second call forwarding destination is cleared after registration of the mobile station; instruct the telephone subsystem to set the first call forwarding destination to the mobile station and instructing the wireless subsystem to clear the second call forwarding destination if a new destination is not provided before a timer elapses when the first call forwarding destination is cleared after registration of the mobile station; instruct the telephone subsystem to set the first call forwarding destination to a new destination and instructing the wireless subsystem to set the second call forwarding destination to the same destination as the first call forwarding destination if a new destination is provided before the timer elapses when the first call forwarding destination is cleared after registration of the mobile station; and instruct the telephone subsystem upon deregistration of the mobile station to clear the first call forwarding destination if the first call forwarding destination is set to the mobile station.

29. A system for call forwarding synchronization, comprising: a telephone subsystem operable to communicate with a telephonic device, the telephone subsystem also operable to forward calls for the telephonic device to a first call forwarding destination; a wireless subsystem operable to communicate with a mobile station, the mobile station associated with the telephonic device, the wireless subsystem comprising: a base station operable to communicate with the mobile station over a wireless interface; a wireless adjunct internet platform operable to communicate with the base station; a gateway operable to communicate with the wireless adjunct internet platform and the telephone subsystem; a gatekeeper operable to forward calls for the mobile station to a second call forwarding destination and to determine a registration state of the mobile station; the gatekeeper operable to instruct the telephone subsystem upon registration of the mobile station to set the first call forwarding destination to the mobile station and to clear the second call forwarding destination if the first call forwarding destination is not set; the gatekeeper operable upon registration of the mobile station to set the second call forwarding destination to the same destination as the first call forwarding destination if the first call forwarding destination is set to a destination other than the mobile station; the gatekeeper operable to instruct the telephone subsystem to set the first call forwarding destination to the same destination as the second call forwarding destination if the second call forwarding destination is set to a destination other than the telephonic device after registration of the mobile station; the gatekeeper operable to set the second call forwarding destination to the same destination as the first call forwarding destination if the first call forwarding destination is set to a destination other than the mobile station after registration of the mobile station; the gatekeeper operable to instruct the telephone subsystem to set the first call forwarding destination to the mobile station if the second call forwarding destination is cleared after registration of the mobile station; the gatekeeper operable to instruct the telephone subsystem to set the first call forwarding destination to the mobile station and to clear the second call forwarding destination if a new destination is not provided before a timer elapses when the first call forwarding destination is cleared after registration of the mobile station; the gatekeeper operable to instruct the telephone subsystem to set the first call forwarding destination to a new destination and to set the second call forwarding destination to the same destination as the first call forwarding destination if a new destination is provided before the timer elapses when the first call forwarding destination is cleared after registration of the mobile station; and the gatekeeper operable to instruct the telephone subsystem upon deregistration of the mobile station to clear the first call forwarding destination if the first call forwarding destination is set to the mobile station.

30. A system for call forwarding synchronization, comprising: a telephone subsystem operable to communicate with a telephonic device, the telephone subsystem also operable to forward calls for the telephonic device to a first call forwarding destination; a client operable to communicate with the telephonic subsystem, the client associated with the telephonic device; a gateway operable to communicate with the client; and a gatekeeper operable to instruct the gateway to forward calls for the client to a second call forwarding destination, the gatekeeper also operable to determine an activation state of the client and to synchronize the call forwarding destinations for the telephonic device and the client in response to a change to at least one of the activation state, the first call forwarding destination, and the second call forwarding destination.

31. The system of claim 30, wherein: the client comprises a gateway to a wireless subsystem, the wireless subsystem operable to communicate with a mobile station; the client activates when the mobile station registers with the wireless subsystem; and the client deactivates when the mobile station deregisters with the wireless subsystem.

32. The system of claim 30, wherein the client comprises at least one of a voice over packet telephone, a computing device, and a gateway operable to communicate with another communication system.

33. A method for call forwarding synchronization, comprising: allowing a telephone subsystem to forward calls for a telephonic device to a first call forwarding destination; allowing a gateway to forward calls for a client to a second call forwarding destination, the client associated with the telephonic device; determining an activation state of the client; and synchronizing the call forwarding destinations for the telephonic device and the client in response to a change to at least one of the activation state, the first call forwarding destination, and the second call forwarding destination.

34. The method of claim 33, wherein: the client comprises a gateway to a wireless subsystem, the wireless subsystem operable to communicate with a mobile station; the client activates when the mobile station registers with the wireless subsystem; and the client deactivates when the mobile station deregisters with the wireless subsystem.

35. The method of claim 33, wherein the client comprises at least one of a voice over packet telephone, a computing device, and a gateway operable to communicate with another communication system.

36. A system for call forwarding synchronization, comprising: at least one computer processable medium; and logic encoded on the at least one computer processable medium and operable to: allow a telephone subsystem to forward calls for a telephonic device to a first call forwarding destination; allow a gateway to forward calls for a client to a second call forwarding destination, the client associated with the telephonic device; determine an activation state of the client; and synchronize the call forwarding destinations for the telephonic device and the client in response to a change to at least one of the activation state, the first call forwarding destination, and the second call forwarding destination.

37. The system of claim 36, wherein: the client comprises a gateway to a wireless subsystem, the wireless subsystem operable to communicate with a mobile station; the client activates when the mobile station registers with the wireless subsystem; and the client deactivates when the mobile station deregisters with the wireless subsystem.

38. The system of claim 36, wherein the client comprises at least one of a voice over packet telephone, a computing device, and a gateway operable to communicate with another communication system.