A user of a wireless device associated with a wireless network may employ the wireless device to send and receive data via the wireless network while the wireless device is in communication with the wireless network. However, when a user of the wireless device turns the wireless device off, or the wireless device is outside an area covered by the wireless network, the user loses the ability to send and receive data via the wireless network. If data is sent to the user while the wireless device is not in communication with the wireless network, the data will not be delivered to the user via the wireless device until the wireless device is turned on and is in a geographic area served by the wireless network. As a result, the user may be unaware of the sent data for an unacceptable period of time. Thus, there exists a need for an apparatus, system and method for forwarding data sent to a wireless device to another address when the wireless device is not in communication with the wireless network.
According to one embodiment, the present invention provides an apparatus for forwarding data sent to a wireless device having a first address to a second address. The apparatus includes a server in communication with a wireless network and an external network, wherein the server includes a processor. The processor includes a data forwarding module for forwarding the data to the second address via the external network when the wireless device is not in communication with the wireless network.
According to another embodiment, the invention provides an apparatus for editing a profile of a user associated with a wireless network. The apparatus includes a database machine in communication with the wireless network. The database machine includes a processor, and the processor includes an edit request module for receiving a request to alter the profile of the user and an update module for altering the profile of the user.
According to another embodiment, the invention provides a system for forwarding data sent to a wireless device having a first address to a second address. The system includes a gateway in communication with a wireless network and an external network, wherein the gateway includes a server. The server includes a processor, and the processor includes a data forwarding module for forwarding the data to the second address via the external network when the wireless device is not in communication with the wireless network.
According to another embodiment, the invention provides a system for editing a profile of a user associated with a wireless network. The system includes a gateway in communication with the wireless network, wherein the gateway includes a database machine. The database machine includes a processor, and the processor includes an edit request module for receiving a request to alter the profile of the user and an update module for altering the profile of the user.
According to another embodiment, the invention provides a method for forwarding data sent to a wireless device having a first address to a second address. The method includes receiving data sent to the first address, the data having a header portion that identifies the first address as a data delivery address, modifying the data, and transmitting the modified data to the second address.
These and various other embodiments of the invention are pointed out with particularity in the claims annexed hereto and forming a part hereof. For a better understanding of the invention, however, reference should be made to the drawings which form a further part hereof, and to the accompanying descriptive matter, in which there are illustrated and described specific examples of an apparatus and method in accordance with the invention.
It is to be understood that the figures and descriptions of the present invention have been simplified to illustrate elements that are relevant for a clear understanding of the present invention, while eliminating, for purposes of clarity, other elements of a conventional communications network. Those of ordinary skill in the art will recognize, however, that these and other elements may be desirable in a typical communications network. However, because such elements are well known in the art, and because they do not facilitate a better understanding of the present invention, a discussion of such elements is not provided herein.
The communications between the gateway 16 and the wireless network 12 may use, for example, the X.25 protocol. The wireless network 12 may also be in communication with a wireless device 18 such as, for example, a wireless pager, and may communicate with the wireless device 18 using an over-the-air protocol such as HP98 or the Blackberry protocol developed by RIM (Research in Motion). According to other embodiments, the wireless device 18 may be a personal digital assistant (PDA), a wireless telephone, a wireless personal computer, a wireless modem, or any wireless device configured to communicate with the wireless network 12. According to one embodiment, the wireless network 12 may be a Mobitex® network operated by Cingular Interactive, and the communications between the wireless device 18 and the wireless network 12 may be text messages. The wireless network 12 and the gateway 16 are described in more detail hereinbelow with respect to
The external network 14 may be any communication network other than the wireless network 12, and may be in communication with an end device 20. For example, the external network 14 may be a second wireless network, the Internet, or a telephone network such as the Public Switched Telephone Network (PSTN). According to another embodiment of the present invention, the system 10 may include a plurality of external networks 14, and each external network 14 may be in communication with the gateway 16. Thus, the communication between the gateway 16 and any one external network 14 may use, for example, the X.25 protocol, the TCP/IP protocol, or a Telocator Alphanumeric Protocol such as XTAP. The end device 20 may be, for example, a wireless device in communication with a second wireless network, a terminal or a computer in communication with the Internet, a telephone in communication with the PSTN, or a facsimile machine in communication with the PSTN.
The message store 28 is in communication with the server 26, and may be implemented as a database configured with a directory structure. The message store 28 may include a mailbox for storing data that has been sent to a wireless device 18 having a first address and associated with the wireless network 12. Data stored in the mailbox may include a data delivery address, and may be held in one or more of the fields of a record in the database. The message store 28 may also include a plurality of mailboxes, each mailbox being associated with a different user that is associated with the wireless network 12, and the directory structure may be used to identify a particular mailbox. The message store 28 may comprise a portion of the server 26 or may be located external to the server 26. According to one embodiment, the gateway 16 may also include a plurality of message stores 28, and each message store 28 may serve as a backup to the other message stores 28.
The gateway 16 may also include an internal network 30, a database machine 32 having a user database 34 associated therewith, a network router 36, a mail router 38, and a protocol handler 40. The internal network 30 may be connected to the server 26, the database machine 32, the network router 36, the mail router 38, and the protocol handler 40, and may, for example, be implemented as a local area network (LAN).
The database machine 32 may be implemented as a c-tree server manufactured by FairCom Corporation, and will be described in more detail hereinbelow with respect to
The primary address may be associated with the wireless device 18, and may indicate where the user wishes to receive data such as, for example, an e-mail message. The alternate delivery address may be associated with the end device 20, and may indicate where the user wishes to receive data addressed to the primary address when the wireless device 18 is turned off or is outside the coverage area of the wireless network 12. The primary address may have a plurality of alternate delivery addresses associated therewith. The waiting time may represent the minimum period of time that the user wishes to have data sent to the primary address remain undelivered before the data is forwarded to the alternate delivery address. For example, there may be instances when the user knows that the wireless device 18 will be turned off or outside the coverage area of the wireless network 12 for a relatively short period of time. In such instances, the waiting time may be set to prevent the data from being forwarded to an alternate delivery address.
The profile may be represented by data held in one or more fields of a record in the user database 34, and may be created or edited at any time. According to one embodiment, the user may send a message to the gateway 16, wherein the message includes information specifying the primary address to be associated with the wireless device 18, one or more alternate delivery addresses, and a value for the waiting time. The gateway 16 may then create or edit the profile according to the information included in the message. According to another embodiment, the user may send a message to the gateway 16, wherein the message includes information instructing the gateway 16 to enable or disable the data forwarding function of the present invention.
The user database 34 may also include a plurality of profiles, each profile being associated with a different user that is associated with the wireless network 12. The user database 34 may include a directory structure, and the directory structure may be used to identify a particular profile. The user database 34 may comprise a portion of the database machine 32 or may be located external to the database machine 32. According to one embodiment, the gateway 16 may include a plurality of database machines 32 that may serve as a backup to the other database machines 32. According to another embodiment of the present invention, the database machine 32 and the server 26 may be combined into a single computer (not shown) that is in communication with the message store 28, the user database 34, and the internal network 30.
The network router 36 is connected to the wireless network 12 and the internal network 30, and may use the X.25 protocol to communicate with one or more of the wireless network switches 24 via fixed communication links. The network router 36 may include up to two dual-ported connectivity cards. Thus, the network router 36 may include up to four fast-sequenced transport (FST) connections. The network router 36 may receive message packets from and send message packets to the wireless network 12. The network router 36 may also route the message packets received from the wireless network 12 to the protocol handler 40 via the internal network 30. Communications between the network router 36 and the protocol handler 40 may use the user datagram protocol (UDP) that comprises a part of the TCP/IP protocol suite. According to one embodiment, the gateway 16 may include up to 255 network routers 36, and each network router 36 may serve as a backup to the other network routers 36.
The mail router 38 may be connected to the Internet and the internal network 30, and may use the TCP/IP protocol to communicate with the Internet via a fixed communication link. The mail router 38 may receive message packets from and send message packets to the Internet. The mail router 38 may also route the message packets received from the Internet to the protocol handler 40 via the internal network 30. Communications between the mail router 38 and the protocol handler 40 may use the user datagram protocol (UDP). According to one embodiment, the gateway 16 may include a plurality of mail routers 38, and each mail router 38 may serve as a backup to the other mail routers 38.
The protocol handler 40 is connected to the internal network 30, and may process communications received by the gateway 16 from the wireless network 12 or the external network 14. The underlying protocol for decoding messages received from or packaging messages sent to the wireless network 12 and the external network 14 may be simple mail transfer protocol (SMTP). The protocol handler 40 may communicate with the server 26, the database machine 32, the network router 36 and the mail router 38 using X-sockets over internal network 30. Such sockets may be, for example, point-to-point, two-way software communications interfaces that direct the protocol handler 40 to access the internal network 30 by creating a communications end-point or socket and returning a file descriptor with which to access the socket. The protocol handler 40 may also maintain a database cache (not shown), i.e., a small, fast memory holding recently accessed data, to speed up internal network communications and to limit database access requests over the LAN.
The protocol handler 40 may handle protocols associated with the wireless network 12 and the external network 14. The protocol handler 40 may be a UNIX machine, and the protocols handled by the protocol handler 40 may specify that the storage of and access to data in the message store 28 may be handled by a UNIX-based network file system (NFS) that allows data to be shared across the internal network 30 regardless of the protocol. According to one embodiment, the gateway 16 may include a plurality of protocol handlers 40, and each protocol handler 40 may serve to back up the other protocol handlers 40.
The gateway 16 may also include one or more subsystems 42 that are in communication with the internal network 30 and an external network 14. The subsystems 42 may include, for example, a faxmail system, a pagemail system, a phonemail system, or an interactive voice response system (IVRS).
According to one embodiment, the gateway 16 may be configured as a standard Santa Cruz Operation (SCO) UNIX system. The gateway 16 may use both TCP/IP and UDP for communications, and hypertext markup language (HTML) may be used to support Internet web browsers, including those provided by Netscape and Microsoft. The application programs used by the gateway components may be written in, for example, the C programming language, Java or HTML.
The data forward module 46 may be implemented, for example, as microcode configured into the logic of the processor 44, or may be implemented as programmable microcode stored in an electrically erasable programmable read only memory (EEPROM). According to another embodiment, the data forward module 46 may be implemented as software code to be executed by the processor 44. The software code may be written in any suitable programming language using any suitable programming technique. For example, the software code may be written in C using procedural programming techniques, or in Java or C++ using object-oriented programming techniques. The software code may be stored as a series of instructions or commands on a computer readable medium, such as a random access memory (RAM) or a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a CD-ROM.
The modules 50, 52 may be implemented as microcode configured into the logic of the processor 48, or may be implemented as programmable microcode stored in an electrically erasable programmable read only memory (EEPROM). According to another embodiment, the modules 50, 52 may be implemented as software code to be executed by the processor 48. The software code may be written in any suitable programming language using any suitable programming technique. For example, the software code may be written in C using procedural programming techniques, or in Java or C++ using object-oriented programming techniques. The software code may be stored as a series of instructions or commands on a computer readable medium, such as a random access memory (RAM) or a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a CD-ROM.
The process begins at block 60, where data sent to a user of the wireless device 18 are received at the gateway 16. From block 60, the process proceeds to block 62, where the data are stored at the message store 28 in a mailbox associated with the user. From block 62, the process proceeds to block 64, where the gateway 16 determines whether or not the wireless device 18 is in communication with the wireless network 12 (i.e., whether the wireless device 18 is “on-air” or “off-air”). The gateway 16 may determine the status of the wireless device 18 by querying a location register associated with the wireless network 12. The location register may be a database associated with the wireless network 12, and may include information associated with the status of the wireless device 18. Such information may include, for example, whether the wireless device 18 is “on-air” or “off-air.”
If the query indicates that the wireless device 18 is “on-air,” the process proceeds from block 64 to block 66, where the data are forwarded from the gateway 16 to the wireless device 18. However, if the query indicates that the wireless device 18 is “off-air,” the process proceeds from block 64 to block 68, where the gateway 16 determines whether the waiting time specified in the user profile maintained in the user database 34 has been exceeded.
If the waiting time has not been exceeded, the process proceeds from block 68 back to block 64, where the process proceeds as described hereinabove. If the waiting time has been exceeded, the process proceeds from block 68 to block 70, where the gateway 16 modifies the data. The gateway 16 may modify the data by changing the delivery address of the data, and the data may be modified in a variety of ways. According to one embodiment, the delivery address may be removed from the header portion of the data stored in the mailbox, and replaced with an alternate delivery address that is listed in the user profile maintained in the user database 34. According to another embodiment, a copy of the non-header portion of the data stored in the mailbox may be created, and a header including an alternate delivery address that is listed in the user profile may be attached thereto. According to another embodiment, a plurality of copies of the non-header portion of the data stored in the mailbox may be created. Thereafter, each copy may have a header attached thereto, wherein each header includes a different alternate delivery address, and wherein each alternate delivery address is listed in the user profile maintained in user database 34. From block 70, the process proceeds to block 72, where the gateway 16 transmits the modified data to the alternate delivery address indicated in the header portion of the data via the external network 14. According to one embodiment, the gateway 16 may transmit the data to a plurality of different addresses via one or more external networks 14, and the transmission of the data to the plurality of different addresses may occur simultaneously or sequentially.
While several embodiments of the invention have been described, it should be apparent, however, that various modifications, alterations and adaptations to those embodiments may occur to persons skilled in the art with the attainment of some or all of the advantages of the present invention. It is therefore intended to cover all such modifications, alterations and adaptations without departing from the scope and spirit of the present invention as defined by the appended claims.
This application is a continuation of U.S. application Ser. No. 12/984,107, filed Jan. 4, 2011 (now U.S. Pat. No. 8,583,083), which is a continuation of U.S. application Ser. No. 11/610,762, filed Dec. 14, 2006 (now U.S. Pat. No. 7,865,175), which is a continuation of U.S. application Ser. No. 10/097,310, filed Mar. 14, 2002 (now U.S. Pat. No. 7,187,921), which claims the benefit of U.S. Provisional Patent Application No. 60/339,975, filed Dec. 10, 2001, the entireties of which are herein incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
5559800 | Mousseau et al. | Sep 1996 | A |
5570366 | Baker et al. | Oct 1996 | A |
5572528 | Shuen | Nov 1996 | A |
5761290 | Farris et al. | Jun 1998 | A |
5903845 | Buhrmann | May 1999 | A |
5933477 | Wu | Aug 1999 | A |
6147977 | Thro et al. | Nov 2000 | A |
6182120 | Beaulieu et al. | Jan 2001 | B1 |
6208854 | Roberts et al. | Mar 2001 | B1 |
6208998 | Marcus | Mar 2001 | B1 |
6219694 | Lazaridis et al. | Apr 2001 | B1 |
6263064 | O'Neal et al. | Jul 2001 | B1 |
6272339 | Wiedeman | Aug 2001 | B1 |
6353852 | Nestoriak, III et al. | Mar 2002 | B1 |
6356543 | Hall et al. | Mar 2002 | B2 |
6430604 | Ogle et al. | Aug 2002 | B1 |
6463145 | O'Neal et al. | Oct 2002 | B1 |
6463462 | Smith et al. | Oct 2002 | B1 |
6510381 | Grounds et al. | Jan 2003 | B2 |
6587684 | Hsu et al. | Jul 2003 | B1 |
6625135 | Johnson et al. | Sep 2003 | B1 |
6678361 | Rooke | Jan 2004 | B2 |
6697354 | Borella | Feb 2004 | B1 |
6697474 | Hanson | Feb 2004 | B1 |
6728357 | O'Neal et al. | Apr 2004 | B2 |
6892074 | Tarklainen et al. | May 2005 | B2 |
6928468 | Leemakers | Aug 2005 | B2 |
6934532 | Coppinger et al. | Aug 2005 | B2 |
6965765 | Creemer et al. | Nov 2005 | B2 |
7082116 | Reza | Jul 2006 | B2 |
7120435 | Usher et al. | Oct 2006 | B2 |
7158497 | Li | Jan 2007 | B2 |
7162237 | Silver et al. | Jan 2007 | B1 |
7187921 | Jordan, Jr. | Mar 2007 | B1 |
7194252 | Jordan, Jr. | Mar 2007 | B1 |
7212505 | Saint-Hillaire et al. | May 2007 | B2 |
7245925 | Zellner | Jul 2007 | B2 |
7269431 | Gilbert | Sep 2007 | B1 |
7272662 | Chesnals et al. | Sep 2007 | B2 |
7359720 | Hartmaier et al. | Apr 2008 | B2 |
7363345 | Austin-Lane et al. | Apr 2008 | B2 |
7373144 | Kiilpatrick et al. | May 2008 | B1 |
7376957 | Scurlock, Jr. | May 2008 | B1 |
7383052 | Moton et al. | Jun 2008 | B2 |
7388950 | Elsey | Jun 2008 | B2 |
7428410 | Petry et al. | Sep 2008 | B2 |
7457616 | Link et al. | Nov 2008 | B2 |
7502362 | Koskinen et al. | Mar 2009 | B1 |
7804821 | Wilhoite et al. | Sep 2010 | B2 |
7984099 | Horstmann et al. | Jul 2011 | B1 |
20010005857 | Lazaridis et al. | Jun 2001 | A1 |
20010037407 | Dragulev et al. | Nov 2001 | A1 |
20010043273 | Herrod et al. | Nov 2001 | A1 |
20020019880 | Sakakura | Feb 2002 | A1 |
20020087704 | Chesnais | Jul 2002 | A1 |
20020090963 | Avalos et al. | Jul 2002 | A1 |
20020160757 | Shavit et al. | Oct 2002 | A1 |
20020164983 | Raviv | Nov 2002 | A1 |
20020167488 | Hinckley et al. | Nov 2002 | A1 |
20030018796 | Chou et al. | Jan 2003 | A1 |
20030028671 | Mehta | Feb 2003 | A1 |
20030048751 | Han et al. | Mar 2003 | A1 |
20030058853 | Gorbatov et al. | Mar 2003 | A1 |
20030060240 | Graham et al. | Mar 2003 | A1 |
20030109247 | Lindgren et al. | Jun 2003 | A1 |
20040058673 | Irlam et al. | Mar 2004 | A1 |
20050010694 | Ma et al. | Jan 2005 | A1 |
20060029038 | Jungck | Feb 2006 | A1 |
20060089126 | Frank et al. | Apr 2006 | A1 |
20070087729 | Jordan | Apr 2007 | A1 |
20080275950 | Jordan | Nov 2008 | A1 |
20110099240 | Jordan, Jr. | Apr 2011 | A1 |
Entry |
---|
U.S. Office Action dated Mar. 27, 2013 in U.S. Appl. No. 12/984,107. |
U.S. Notice of Allowance dated Jul. 11, 2013 in U.S. Appl. No. 12/984,107. |
U.S. Office Action dated Oct. 7, 2008 in U.S. Appl. No. 11/610,762. |
U.S. Office Action dated Apr. 1, 2009 in U.S. Appl. No. 11/610,762. |
U.S. Office Action dated Nov. 17, 2009 in U.S. Appl. No. 11/610,762. |
U.S. Office Action dated Apr. 29, 2010 in U.S. Appl. No. 11/610,762. |
U.S. Notice of Allowance dated Aug. 31, 2010 in U.S. Appl. No. 11/610,762. |
U.S. Office Action dated Nov. 3, 2004 in U.S. Appl. No. 10/097,310. |
U.S. Office Action dated Jun. 16, 2005 in U.S. Appl. No. 10/097,310. |
U.S. Office Action dated Jan. 3, 2006 in U.S. Appl. No. 10/097,310. |
U.S. Office Action dated Jun. 19, 2006 in U.S. Appl. No. 10/097,310. |
U.S. Notice of Allowance dated Oct. 27, 2006 in U.S. Appl. No. 10/097,310. |
Number | Date | Country | |
---|---|---|---|
20150334542 A1 | Nov 2015 | US |
Number | Date | Country | |
---|---|---|---|
60339975 | Dec 2001 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12984107 | Jan 2011 | US |
Child | 14077520 | US | |
Parent | 11610762 | Dec 2006 | US |
Child | 12984107 | US | |
Parent | 10097310 | Mar 2002 | US |
Child | 11610762 | US |