The present application relates generally to messaging and, more particularly, to systems and methods for providing delayed message delivery.
Short Message Service (SMS) allows users to exchange text messages between capable mobile phones and other devices within a wireless communications network. SMS is a store and forward service. In other words, text messages are not sent directly from sender to recipient. Rather, text messages are sent to an SMS Center (SMSC). Each wireless communications network can include multiple SMSCs to manage the receipt, storage, and forwarding of text messages.
SMS features message delivery confirmation so that the sender can receive a return message notifying them whether or not the short message has been delivered. SMS messages can be sent and received simultaneously with GSM (Global System for Mobile Communications) voice, data, and fax calls. This is possible because SMS messages are sent using the signaling path and not a dedicated radio channel. As such, users of SMS rarely, if ever, get a busy or engaged signal as they can do during peak network usage times. SMS delivery, however, is not guaranteed. In some instances, the message is lost and never sent to the recipient.
Multimedia Messaging Service (MMS) allows users to exchange multimedia communications between capable mobile phones and other devices. MMS is an extension of the SMS protocol and defines a way to send and receive messages that include images, audio, and video in addition to text.
The present application provides various systems and methods for delayed message delivery. In a first aspect of the present application, a system for delayed message delivery includes an IP Multimedia Subsystem (IMS) network that is in communication with at least one of a first user equipment and a second user equipment, and a message application server. The message application server can be configured to receive a message sent from the first user equipment, store the message temporarily in accordance with a time parameter, and send the message to a gateway when the time parameter is satisfied. The gateway can be configured to receive a message formatted in accordance with a first protocol used by the IMS network and convert the message into a format in accordance with a second protocol used by a message center. The message center can be configured to receive the message formatted in accordance with the second protocol and forward the message to the second user equipment.
In another aspect of the present application, a method for providing a delayed message delivery feature includes creating a message on a first user equipment. The message can include a message body, a telephone number, and a time parameter sending the message in a format of a first protocol to an IP Multimedia Subsystem (IMS) network. The IMS network can send the message to a message application server for temporary storage in accordance with the time parameter. The message application server can send the message to a message gateway when the time parameter is satisfied. The message gateway can convert the message from the first protocol to a second protocol compatible with a message center and send the message to the message center. The message center can send the message to a second user equipment identified by the telephone number.
In yet another aspect of the present application, a system for delayed message delivery includes a first user equipment, a second user equipment, a message center, capable of communication with the first user equipment and the second user equipment, and a message application server, in communication the message center. The message application server can be configured to receive a message sent from the first user equipment, store the message temporarily in accordance with a time parameter, and send the message to the message center when the time parameter is satisfied.
In still another aspect of the present application, a method for providing a delayed message delivery feature includes creating a message on a first user equipment. The message can include a message body, a telephone number, and a time parameter. The method further includes establishing a data session between the first user equipment and a message application server, sending the message to the message application server for temporary storage in accordance with the time parameter, sending the message from the message application server to a message center when the time parameter is satisfied, and sending the message from the message center to a second user equipment identified by the telephone number.
In another aspect of the present application, a method for providing a delayed message delivery feature includes specifying a time parameter and creating a message on a user equipment. The message can include a message body, a telephone number associated with the user equipment, and the time parameter. The method can further include establishing a data session between the user equipment and a message application server, sending the message to the message application server for temporary storage in accordance with the time parameter, sending the message from the message application server to a message center when the time parameter is satisfied, and sending the message from the message center to the user equipment identified by the telephone number.
In one embodiment of the aforementioned aspects, the time parameter can include at least one of a date and time when the message is sent. In another embodiment, the time parameter can include a time value for a timer, the expiration of which prompts the message to be sent.
In one embodiment of the aforementioned aspects, the first protocol is Session Initiation Protocol (SIP) and the second protocol is Short Message Service (SMS) protocol. In another embodiment, the first protocol is SIP protocol and the second protocol is Multimedia Message Service (MMS) protocol. In yet another embodiment, the first protocol is SIP protocol and the second protocol is a voicemail protocol.
In one embodiment of the aforementioned aspects, the message center is an SMS center (SMSC). In another embodiment, the message center is an MMS center (MMSC). In yet another embodiment, the message center is a voicemail platform.
As required, detailed embodiments of the present application are disclosed herein. It must be understood that the disclosed embodiments are merely exemplary examples of the application that may be embodied in various and alternative forms, and combinations thereof. As used herein, the word “exemplary” is used expansively to refer to embodiments that serve as an illustration, specimen, model or pattern. The figures are not necessarily to scale and some features may be exaggerated or minimized to show details of particular components. In other instances, well-known components, systems, materials or methods have not been described in detail in order to avoid obscuring the present application. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present application.
Referring to the drawings wherein like numerals represent like elements throughout the several views,
The illustrated wireless communications network 100 includes a calling party user equipment (UE) 102 that is configured to create a message that includes a future date and/or time for delivery to one or more recipients. The calling party UE 102 can be a mobile phone, handheld computer, other computer, messaging device, or other device, for example. In one embodiment, the calling party UE 102 is in communication with an IP Multimedia Subsystem (IMS) network 104 that is configured to receive the message and a date and/or time for future delivery. The message can be formatted in accordance with the Session Initiation Protocol (SIP) used by the IMS network 104, for example. It should be understood that other protocols are contemplated, such as, but not limited to, evolutions, improvements, and extensions of the SIP protocol and related IMS protocols.
The IMS network 104 is access-network-independent as it supports multiple access types including GSM, WCDMA, CDMA2000, WLAN, wireline broadband and other packet data applications, for example. IMS is a standardized reference architecture. IMS consists of session control, connection control, and an applications services framework along with subscriber and services data. IMS enables new converged voice and data services, while allowing for the interoperability of these converged services between Internet and cellular subscribers. IMS uses open standard IP protocols, defined by the IETF (Internet Engineering Task Force). Users can execute all their services when roaming as well as from their home networks.
The illustrated IMS network 104 is in communication with an IP messaging gateway 106 that, in turn, is in communication with a home subscriber server (HSS) 108 and a message application server 110. The message application server 110 is also in communication with the IMS network 104.
The IP messaging gateway 106 provides a gateway function to a message center 112. The IP messaging gateway 106 can also convert messages from IP protocols, such as SIP, to a protocol used by the message center 112, such as SMS protocol, for example. The message center 112 can be, but is not limited to, an SMS center (SMSC), an MMS center (MMSC), or a voicemail server, for example. Accordingly, the message center 112 can be configured to manage text, multimedia, and voice messages. The message center 112 is illustrated as being in communication with the HSS 108, a home location register 114, and a legacy message application server 116. The message center 112 is also illustrated as being in communication with a called party UE 118.
If the calling party UE 102 is not compatible with the IMS network 104, the calling party UE 102 can send messages to the legacy application server 116. Accordingly, in this embodiment, the message can be formatted in accordance with the message protocol used by the message center 112 and no conversion is necessary. The legacy application server 116 can be a separate network entity or can be combined with other network elements, such as the message center 112.
Referring now to
Referring now to
The method 300 begins and flow proceeds to step 302, wherein a message is created based upon user input. For example, a user operating the calling party UE 102 can enter text and/or select an image, select or enter one or more recipients' telephone numbers, and select or enter a future date and/or time the user desires the message to be sent. The calling party UE 102 creates a corresponding message. The message can be formatted as a SIP message, for example. The message is sent to the IMS network 104, at step 304.
At step 306, the IMS network 104 sends a query to the HSS 108 to determine if the user has the delayed message delivery feature is enabled on the user's account. It should be understood that a delayed message delivery feature can be provided as a free feature for message service subscribers or can be provided with a one-time charge, per-use charge, or monthly recurring charge. A delayed message delivery feature can be offered to prepaid and/or post-paid subscribers.
At step 308, it is determined if the user has the delayed message feature enabled on their account. If the delayed message feature is enabled for the user's account, the method 300 proceeds to step 310 and the message is delivered to the message application server 110 for storage until the date and/or time specified in the message. Otherwise, the message is not sent or the message is sent immediately in accordance with current protocols and the method 300 ends.
At step 312, one or more timers can be enabled with one or more time values as a countdown to the future date and/or time specified in the message. When the timer expires the message is sent to the IP message gateway 106, at step 314. Alternatively or in addition, one or more trigger events can be set for the specified date and time. In addition, a timer or a trigger event can be set to expire or activate at a time different from the specified time such that any delay in receiving the message at the called party UE 118 can be minimized.
At step 316, the IP message gateway 106 converts the message from SIP protocol to the appropriate message protocol and sends the message to the message center 112 for delivery to the called party UE 118. The message is sent to the called party UE 118. At step 318, the called party UE 118 receives the message. The method 300 ends.
Referring now to
The method 400 begins and flow proceeds to step 402, wherein a message is created based upon user input. For example, a user operating the calling party UE 102 can enter text and/or select an image, select or enter one or more recipients telephone numbers, and select or enter a future date and time the user desires the message to be sent. The calling party UE 102 creates a corresponding message.
At step 404, a data session is established between the calling party UE 102 and the legacy message application server 116. At step 406, the message and the future date and time are sent to the legacy message application server 116 for temporary storage.
At step 408, a timer is enabled for the future date and time specified in the message. When the timer expires the message is forwarded to the message center 112 for delivery to the called party UE 118, at step 410. At step 412, the called party UE 118 receives the message. The method 400 ends
Alternatively, a trigger event can be set for the specified date and time. In addition, a timer or a trigger event can be set to expire or activate at a time different from the specified time such that any delay in receiving the message at the called party UE 118 can be minimized. It should be understood that more than one timer and/or more than one trigger event can be set or a combination thereof.
As an alternative to the aforementioned methods described in
Referring now to
As illustrated, the device 500 can be a single-mode or multi-mode mobile communications device.
Generally, applications can include routines, program modules, programs, components, data structures, and the like. Applications can be implemented on various system configurations, including single-processor or multiprocessor systems, minicomputers, mainframe computers, personal computers, hand-held computing devices, microprocessor-based, programmable consumer electronics, combinations thereof, and the like.
The device 500 includes a display 502 for displaying multimedia such as, for example, text, images, video, telephony functions, caller line ID data, setup functions, menus, messages, wallpaper, graphics, and the like. The device 500 also includes a processor 504 for controlling and/or processing data. A memory 506 can interface with the processor 504 for the storage of data and/or applications 508. The memory 506 can include a variety of computer readable media including, but not limited to, volatile media, non-volatile media, removable media, and non-removable media. Computer-readable media can include device storage media and communication media. Storage media can include volatile and/or non-volatile, removable and/or non-removable media such as, for example, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, DVD, or other optical disk storage, magnetic tape, magnetic disk storage, other magnetic storage devices, or any other medium that can be used to store the desired information and that can be accessed by the device 500.
The memory 506 can be configured to store one or more applications 508. The applications 508 can also include a user interface (UI) application 510. The UI application 510 can interface with a client 512 (e.g., an operating system) to facilitate user interaction with device functionality and data, for example, answering/initiating calls, entering/deleting data, configuring settings, address book manipulation, multi-mode interaction, and the like. The applications 508 can include other applications 514, such as, for example, a delayed messaging application. The applications 508 can be stored in the memory 506 and/or in a firmware 516, and can be executed by the processor 504. The firmware 516 can also store code for execution during initialization of the device 500.
A communications component 518 can interface with the processor 504 to facilitate wired/wireless communications with external systems including, for example, cellular networks, VoIP networks, LAN, WAN, MAN, PAN, that can be implemented using WiFi, WiMax, combinations and/or improvements thereof, and the like. The communications component 518 can also include a multi-mode communications subsystem for providing cellular communications via different cellular technologies. For example, a first cellular transceiver 520 can operate in one mode, for example, GSM, and an Nth transceiver 522 can operate in a different mode, for example WiFi. While only two transceivers 520, 522 are illustrated, it should be appreciated that a plurality of transceivers can be included. The communications component 518 can also include a transceiver 524 for unlicensed RF communications using technology such as, for example, WiFi, WiMAX, near-field communications, other RF, and the like. The transceiver 524 can also be configured for line-of-sight technologies, such as, infrared and IRDA, for example. Although a single transceiver 524 is illustrated, multiple transceivers for unlicensed RF and line-of-sight technologies are contemplated.
The communications component 518 can also facilitate communications reception from terrestrial radio networks, digital satellite radio networks, Internet-based radio services networks, combinations thereof, and the like. The communications component 518 can process data from a network, such as, for example, the Internet, a corporate WAN, an intranet, a home broadband network, and the like, via an ISP, DSL provider, or other broadband service provider.
An input/output (I/O) interface 526 can be provided for input/output of data and/or signals. The I/O interface 526 can be a hardwire connection, such as, for example, a USB, PS2, IEEE 1394, serial, parallel, IEEE 802.3 (e.g., Ethernet—RJ45, RJ48), traditional telephone jack (e.g., RJ11, RJ14, RJ25) and the like, and can accept other I/O devices, such as, for example, a keyboard, keypad, mouse, interface tether, stylus pen, printer, plotter, jump/thumb drive, touch screen, multi-touch screen, touch pad, trackball, joy stick, controller, monitor, display, LCD, plasma, OLED, combinations thereof, and the like.
Audio capabilities can be provided by an audio I/O component 528 that can include a speaker (not shown) for the output of audio signals and a microphone (not shown) to collect audio signals.
The device 500 can include a slot interface 530 for accommodating a subscriber identity system 532, such as, for example, a SIM or universal SIM (USIM). The subscriber identity system 532 instead can be manufactured into the device 500, thereby obviating the need for a slot interface 530.
The device 500 can include an image capture and processing system 534. Photos and/or videos can be obtained via an associated image capture subsystem of the image system 534, for example, a camera. The device 500 can also include a video systems component 536 for processing, recording, and/or transmitting video content.
A location component 538 can be included to send and/or receive signals, such as, for example, GPS data, assisted GPS data, triangulation data, combinations thereof, and the like. The device 500 can use the received data to identify its location or can transmit data used by other devices to determine the device 500 location.
The device 500 can include a power source 540 such as batteries and/or other power subsystem (AC or DC). The power source 540 can be single-use, continuous, or rechargeable. In the case of the latter, the power source 540 can interface with an external power system or charging equipment via a power I/O component 542.
The law does not require and it is economically prohibitive to illustrate and teach every possible embodiment of the present claims. Hence, the above-described embodiments are merely exemplary illustrations of implementations set forth for a clear understanding of the principles of the application. Variations, modifications, and combinations may be made to the above-described embodiments without departing from the scope of the claims. All such variations, modifications, and combinations are included herein by the scope of this disclosure and the following claims.
This application claims priority to U.S. Provisional Application No. 60/896,728, filed Mar. 23, 2007, the entirety of which is hereby incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
5692032 | Seppanen et al. | Nov 1997 | A |
5894506 | Pinter | Apr 1999 | A |
5905959 | Foladare et al. | May 1999 | A |
5943399 | Bannister et al. | Aug 1999 | A |
6044275 | Boltz et al. | Mar 2000 | A |
6085201 | Tso | Jul 2000 | A |
6138008 | Dunn et al. | Oct 2000 | A |
6182059 | Angotti et al. | Jan 2001 | B1 |
6278968 | Franz et al. | Aug 2001 | B1 |
6356633 | Armstrong | Mar 2002 | B1 |
6393421 | Paglin | May 2002 | B1 |
6411947 | Rice et al. | Jun 2002 | B1 |
6477551 | Johnson et al. | Nov 2002 | B1 |
6480484 | Morton | Nov 2002 | B2 |
6522877 | Lietsalmi et al. | Feb 2003 | B1 |
6718368 | Ayyadurai | Apr 2004 | B1 |
7058652 | Czarnecki et al. | Jun 2006 | B2 |
7137070 | Brown et al. | Nov 2006 | B2 |
7149782 | Sommerer | Dec 2006 | B2 |
7383250 | Scian et al. | Jun 2008 | B2 |
7546131 | Sidi et al. | Jun 2009 | B1 |
7657600 | Auhagen | Feb 2010 | B2 |
7844666 | Horvitz et al. | Nov 2010 | B2 |
7925620 | Yoon | Apr 2011 | B1 |
8069143 | Swanburg et al. | Nov 2011 | B2 |
20010041566 | Xanthos et al. | Nov 2001 | A1 |
20020007346 | Qiu et al. | Jan 2002 | A1 |
20020035684 | Vogel et al. | Mar 2002 | A1 |
20020138582 | Chandra et al. | Sep 2002 | A1 |
20020169841 | Carlson et al. | Nov 2002 | A1 |
20020178041 | Krantz et al. | Nov 2002 | A1 |
20030154256 | Hadano et al. | Aug 2003 | A1 |
20030193951 | Fenton et al. | Oct 2003 | A1 |
20040059700 | Park et al. | Mar 2004 | A1 |
20040128151 | Mock et al. | Jul 2004 | A1 |
20040208297 | Valentine | Oct 2004 | A1 |
20050021551 | Silva et al. | Jan 2005 | A1 |
20050074169 | Filatov et al. | Apr 2005 | A1 |
20050120084 | Hu et al. | Jun 2005 | A1 |
20050198582 | Hennum et al. | Sep 2005 | A1 |
20050209861 | Hewes et al. | Sep 2005 | A1 |
20060030297 | Coble et al. | Feb 2006 | A1 |
20060052091 | Onyon et al. | Mar 2006 | A1 |
20060095575 | Sureka et al. | May 2006 | A1 |
20060104429 | Wouterse et al. | May 2006 | A1 |
20060115062 | Gonder et al. | Jun 2006 | A1 |
20060246881 | Winkler et al. | Nov 2006 | A1 |
20060250987 | White et al. | Nov 2006 | A1 |
20060274721 | Flanagan | Dec 2006 | A1 |
20060277176 | Liao | Dec 2006 | A1 |
20070022099 | Yoshimura et al. | Jan 2007 | A1 |
20070026852 | Logan et al. | Feb 2007 | A1 |
20070064920 | Ruckart | Mar 2007 | A1 |
20070073810 | Adams et al. | Mar 2007 | A1 |
20070088798 | Merrill et al. | Apr 2007 | A1 |
20070136431 | Sun | Jun 2007 | A1 |
20070233736 | Xiong et al. | Oct 2007 | A1 |
20070249379 | Bantukul | Oct 2007 | A1 |
20070266118 | Wilkins | Nov 2007 | A1 |
20070266156 | Wilkins | Nov 2007 | A1 |
20080004005 | Jensen | Jan 2008 | A1 |
20080133677 | Pattabhiraman et al. | Jun 2008 | A1 |
20080189293 | Strandel et al. | Aug 2008 | A1 |
20080235242 | Swanburg et al. | Sep 2008 | A1 |
20080250332 | Farrell et al. | Oct 2008 | A1 |
20080300982 | Larson et al. | Dec 2008 | A1 |
20090022285 | Swanburg et al. | Jan 2009 | A1 |
20100179991 | Lorch et al. | Jul 2010 | A1 |
20100287241 | Swanburg et al. | Nov 2010 | A1 |
20120066177 | Swanburg et al. | Mar 2012 | A1 |
Number | Date | Country |
---|---|---|
1359777 | Nov 2003 | EP |
1569426 | Aug 2005 | EP |
1755294 | Feb 2007 | EP |
9949679 | Sep 1999 | WO |
02087197 | Oct 2002 | WO |
2005015927 | Feb 2005 | WO |
2008118878 | Oct 2008 | WO |
Entry |
---|
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Support of SMS and MMS Over Generic 3GPP IP Access”, 3GPP TR 23.804 v7.1.0 (Sep. 2005). |
U.S. Office Action dated Jul. 16, 2010 in U.S. Appl. No. 12/051,336. |
U.S. Office Action dated Dec. 27, 2010 in U.S. Appl. No. 12/051,336. |
U.S. Notice of Allowance dated Jul. 15, 2011 in U.S. Appl. No. 12/051,336. |
U.S. Office Action dated Sep. 21, 2011 in U.S. Appl. No. 12/053,525. |
U.S. Office Action dated Aug. 6, 2012 in U.S. Appl. No. 12/053,525. |
U.S. Office Action dated Dec. 23, 2010 in U.S. Appl. No. 12/279,756. |
U.S. Office Action dated Jul. 8, 2011 in U.S. Appl. No. 12/279,756. |
U.S. Office Action dated Dec. 7, 2009 in U.S. Appl. No. 11/873,031. |
U.S. Office Action dated May 26, 2010 in U.S. Appl. No. 11/873,031. |
U.S. Office Action dated Feb. 16, 2012 in U.S. Appl. No. 11/873,031. |
U.S. Office Action dated Jul. 25, 2012 in U.S. Appl. No. 11/873,031. |
Pearlman, L., “A Community Authorization Service for Group Collaboration,” Jun. 2002, IEEE 3rd International Workshop, pp. 50-59. |
Notice of Allowance mailed on Mar. 6, 2014 in U.S. Appl. No. 12/053,525. |
Office Action mailed on Sep. 11, 2013 in U.S. Appl. No. 12/279,756. |
Office Action mailed on Nov. 25, 2012 in U.S. Appl. No. 13/296,374. |
Non-final Office Action mailed on Apr. 8, 2014 in U.S. Appl. No. 12/279,756. |
International Application No. PCT/US2008/058052 Written Opinion dated Sep. 29, 2009. |
International Application No. PCT/US2008/058052 International Search Report dated Oct. 7, 2008. |
International Application No. PCT/US2008/058055 Written Opinion dated Sep. 29, 2009. |
International Application No. PCT/US2008/058055 International Search Report dated Jul. 3, 2009. |
International Application No. PCT/US2008/058057 Written Opinion dated Sep. 29, 2009. |
International Application No. PCT/US2008/058057 International Search Report dated Jul. 7, 2008. |
International Application No. PCT/US2008/058064 Written Opinion dated Sep. 29, 2009. |
International Application No. PCT/US2008/058064 International Search Report dated Aug. 21, 2008. |
International Application No. PCT/US2008/058067 Written Opinion dated Sep. 29, 2009. |
International Application No. PCT/US2008/058067 International Search Report dated Oct. 27, 2008. |
Office Action mailed Oct. 21, 2104, in U.S. Appl. No. 12/279,756. |
Number | Date | Country | |
---|---|---|---|
20090285129 A1 | Nov 2009 | US |
Number | Date | Country | |
---|---|---|---|
60896728 | Mar 2007 | US |