Method and apparatus for network-assisted automatic confirmation of short message service delivery

Abstract

In a mobile communications network, a delivery acknowledgement receipt can be sent to indicate a SMS message is delivered. A system can be based on currently-existing protocols, such as described in the IS-136 standard. Existing network signals that acknowledge receipt of a message can be captured and utilized to notify the originator when the SMS message is delivered. A variety of other scenarios (e.g., unsuccessful delivery) can also be supported.

Description

FIELD

[0002] The present invention relates generally to short message service in mobile networks, and, more particularly to confirmation of short message service delivery in mobile networks.

BACKGROUND

[0003] Various mobile telecommunication standards include specifications for a subscriber service known in the art as short message service (SMS) (otherwise known as cellular message teleservice, text messaging, PCS messaging, and a variety of other names) which provides for the transmission of short text messages to a subscriber at her or his mobile terminal. For example, the existing IS-136 TDMA Standard describes a one-way messaging service that allows text of 180 characters or less to be sent by a short message service center (SMSC) to an IS-136 capable mobile phone. In the current implementation of the service, the originator of the text message receives no verification that the recipient's phone ever received the message.

[0004] Nevertheless, numerous technologies have been developed which allow for confirmation of whether a message has been delivered to a subscriber terminal. Existing services based on SMS fall into one of three categories: (1) There are two-way paging systems wherein the paging subscriber can initiate a manual response to a message, which often requires new devices or new interfaces on cell phones. (2) Some systems provide a unique confirmation number to each message and the sender can call the system later to track the delivery status of a message using the confirmation code. (3) There are enhanced protocols being proposed to enable advanced wireless information services including confirmed message delivery, an example being the ReFLEX system of MOTOROLA. However, such protocols are not in widespread use.

[0005] Accordingly, a network-assisted system that uses existing protocol standards, that does not require recipients to manually acknowledge receipt of each message, or that does not require the sender to repeatedly check message delivery status would be beneficial.

SUMMARY

[0006] An improved message verification technique based on currently-existing protocols, such as described in the above-mentioned IS-136 standard can be provided. Existing network signals that acknowledge receipt of a message can be captured and utilized to notify the originator when the SMS message is delivered.

[0007] In one embodiment, a short message service center either accesses a database of delivery acknowledgement preferences or parses a short message for encoded delivery acknowledgement preferences and, upon receipt of the relevant network message delivery signal, initiates a delivery acknowledgement back to the originator in accordance with the originator's preferences. The delivery acknowledgement can utilize any of a number of forms of communication infrastructures that can act as external short message entities to the short message service center, including, and without limitation, an e-mail gateway to the Internet, a paging system, a wireless application protocol proxy server, etc. The delivery acknowledgement preferences can express, for example, whether the sender wishes to have each SMS message acknowledged by default or on a message-by-message basis, what type of acknowledgement the sender desires, as well as to what particular address to send the acknowledgement.

[0008] Thus, message verification can be improved in certain embodiments in that a system can utilize existing protocols, need not require a sender to repeatedly check message delivery status, and need not require a recipient to explicitly acknowledge receipt of each message manually.

[0009] These and other advantages of certain embodiments will be apparent to those of ordinary skill in the art by reference to the following detailed description and the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] FIG. 1 sets forth an example of a short message service (SMS) system architecture used to illustrate a preferred embodiment of the present invention.

[0011] FIGS. 2A through 2D are signal diagrams illustrating network signals exchanged during a SMS message delivery attempt.

DETAILED DESCRIPTION

[0012] With reference to FIG. 1, an exemplary short message service (SMS) system architecture is shown to illustrate a preferred embodiment of the present invention. A short message service center (SMSC), exemplified in FIG. 1 as a cellular message teleservice (CMT) node 110, acts as an intermediary between a mobile network and one or more external short message entities. The CMT node 110 stores message service profiles detailing the preferences and subscription details of each subscriber with respect to messages for each of the mobile units which it services. The CMT node 110 uses a standard protocol such as Short Message Peer to Peer (SMPP) to communicate with any external short message entities, such as (and without limitation) a wireless application protocol (WAP) proxy server, an e-mail gateway or other type of messaging gateway, a voice processing system for handling voicemail alerts, a paging system, etc.

[0013] For example, FIG. 1 shows an e-mail gateway 150 connected to a standard packet-switched network 102, such as the Internet, where the gateway 150 is capable of initiating SMPP sessions with the CMT node 110. The CMT node 110 has been augmented to enable it to ascertain whether a delivery acknowledgement is desired—e.g., from data received during the SMPP session, from the content of the particular message, or from stored preferences of the originator of the message. For example, and without limitation, the preferences of the originator can be encoded in the message, as and the CMT node 110 could parse the message and, based on the content of the message, decide whether and how to send a delivery acknowledgement.

[0014] As is known in the art and as further described herein, the CMT node 110 has access to the mobile network and can ascertain where a mobile subscriber is roaming and transmit a short message to the subscriber's mobile unit 140. Thus, the CMT node 110 can contact elements of the mobile network, such as a home location register (HLR) 120 or a mobile service center (MSC) 130, using standard signaling, e.g. shown in FIG. 1 as an SS7 signaling network 101. The CMT node 110 can transmit a short message service request using a standard short message service protocol to the HLR 120 in order to determine where the subscriber is roaming. The HLR 120 receives the SMS request, consults subscriber data, and responds with a return result identifying the appropriate mobile switching center 130, e.g. by MSCID. Or the HLR 120 can return a result indicating that the subscriber's mobile 140 is inactive (e.g., powered down or outside of the coverage area) or that the subscriber's mobile is incapable of receiving SMS. If the subscriber is inactive, the CMT node 110 can keep the short message in queue for a set period while the HLR 120 keeps a flag that shows a message is waiting. Once the subscriber roams back to an MSC in the “home” area, the HLR 120 sends an SMS notification back to the CMT node 110 which can then attempt message delivery. The CMT node 110 can send a Short Message Delivery Point to Point (SMDPP) message to the relevant MSC 130 where the text of the short message is contained within the SMDPP message. The MSC 130 can, in turn, contact a base station 135 and have the particular mobile unit 140 paged using standard R-Data/SMS protocols, e.g. in accordance with the IS-136 TDMA standard in North America. If the mobile unit 140 responds, the system delivers the message to the mobile unit 140. If the message transmission is successful, a SMDPP return result goes from the MSC 130 back to the CMT node 110 which can set the status of the message to “sent” and will not attempt to send the message again.

[0015] This series of messages exchanged between the CMT node 110 and the mobile network (e.g. across standard ANSI/TIA/EIA-41 network interfaces) is illustrated in greater detail in FIGS. 2A through 2D. FIG. 2A shows the messages exchanged during a successful SMS delivery from a message center 110 to a registered and active mobile station 140. FIG. 2B shows the messages exchanged during a successful delivery of a pending SMS (e.g., where the message center 110 has stored the message and awaits the activation and registration of the mobile station 140). FIG. 2C shows the messages exchanged during an attempted SMS delivery to a registered mobile station 140 where there has been a delivery failure between the MSC 130 and the mobile station 140. FIG. 2D shows the messages exchanged during an attempted SMS delivery from a message center 110 to an inactive mobile station 140.

[0016] In accordance with a preferred embodiment of the present invention, the existing network signals—such as the SS7 smdpp[ACK] return result shown above in FIGS. 2A and 2B—are captured at the CMT node 110 and a delivery acknowledgement receipt generated for delivery to the originator 100 of the short message. The delivery acknowledgement receipt can constitute confirmation of the SMS delivery. Similarly, other signals such as a smdpp[NAK] signal in FIG. 2C can be recorded and an acknowledgement receipt generated indicating that a SMS delivery attempt had failed (e.g., because the mobile station 140 was inactive and not registered). The acknowledgement receipt can be generated and delivered in any of a number of ways, which advantageously can depend on the method the originator 100 used to request the short message service or on the express preferences of the originator 100.

[0017] For example, with reference to FIG. 1, where the originator 100 has sent an e-mail to the e-mail gateway 150 in order to generate the SMS delivery request at the CMT node 110, the CMT node 110 can parse the e-mail for the message originator's e-mail address, conventionally found in the e-mail's “to:” header field. The receipt of a smdpp[ACK] signal can be matched up with the originator's stored e-mail address and an e-mail notification reply automatically generated and sent through the e-mail gateway 150 to the originator's e-mail address.

[0018] As another example, the SMS message could have an identification number of the originator's pager encoded in the message, and the CMT node 110 can parse the number and initiate a page containing a delivery status code upon receipt of the relevant status signal. As another example, the SMS message could have the originator's mobile phone number encoded in the message, and the CMT node 110 could initiate its own SMS message back to the originator's mobile.

[0019] The originator of the SMS message can choose whether to have each SMS message acknowledged by default or on a message-by-message basis. For example, as mentioned above, the preference can be encoded in the body of the SMS message that can be deciphered by the server. The wireless service provider can choose to deliver or block such feedback.

[0020] The foregoing merely illustrates the principles of the invention. Thus, for example, although the invention is illustrated in the context of known mobile cellular architectures and particular short message service standards, those skilled in the art will be able to implement the invention in any of a variety of mobile architectures. It will thus be appreciated that those skilled in the art will be able to devise numerous arrangements that, although not explicitly shown or described herein, nevertheless embody the principles of the invention and are within its spirit and scope.

Claims

1. A method of operating a short message service center comprising: receiving a short message service request from a sender; determining delivery acknowledgement preferences of the sender; transmitting through a mobile network a short message to a mobile unit in accordance with the short message service request; receiving a signal from the mobile network acknowledging delivery of the short message to the mobile unit; and transmitting a delivery acknowledgement in accordance with the delivery acknowledgement preferences of the sender.

2. The method of claim 1 wherein the delivery acknowledgement preference is stored in a database.

3. The method of claim 1 wherein the delivery acknowledgement preference is encoded in the short message service request.

4. The method of claim 1 wherein the delivery acknowledgement is an e-mail transmitted to the sender's e-mail address.

5. The method of claim 1 wherein the delivery acknowledgement is transmitted using a short message service.

6. The method of claim 1 wherein the delivery acknowledgement is a page in a paging system.

7. The method of claim 1 wherein the delivery acknowledgement is transmitted to a wireless application protocol proxy server.

8. A short message service center comprising: a first interface to a mobile network; a second interface to an external short message entity; a central processing unit connected to first and second interface for executing computer program instructions, the computer program instructions causing the central processing unit to perform the following: receiving a short message service request from a sender; determining delivery acknowledgement preferences of the sender; transmitting through the mobile network a short message to a mobile unit in accordance with the short message service request; receiving a signal from the mobile network acknowledging delivery of the short message to the mobile unit; and transmitting through the external short message entity a delivery acknowledgement in accordance with the delivery acknowledgement preferences of the sender.

9. The short message service center of claim 8 further comprising a storage device and wherein the delivery acknowledgement preference is stored in a database on the storage device.

10. The short message service center of claim 8 wherein the delivery acknowledgement preference is encoded in the short message service request.

11. The short message service center of claim 8 wherein the external short message entity is an e-mail gateway and the delivery acknowledgement is an e-mail transmitted to the sender's e-mail address.

12. The short message service center of claim 8 wherein the external short message entity is a paging system and the delivery acknowledgement is a page in the paging system.

13. The short message service center of claim 8 wherein the external short message entity is a wireless application protocol proxy server.

14. A computer-readable medium comprising computer-executable instructions for performing the following in a short message service center comprising a first interface to a mobile network, a second interface to an external short message entity, and a central processing unit connected to the first and second interface: receiving a short message service request from a sender; determining delivery acknowledgement preferences of the sender; transmitting through the mobile network a short message to a mobile unit in accordance with the short message service request; receiving a signal from the mobile network acknowledging delivery of the short message to the mobile unit; and transmitting through the external short message entity a delivery acknowledgement in accordance with the delivery acknowledgement preferences of the sender.

15. A network node operable to communicate with at least one mobile communication device, the network node comprising: a processor configured to perform at least the following: receiving an SMDPP acknowledgement message as a result of attempting communications with the mobile communication device; and responsive to receiving the SMDPP acknowledgement message, transmitting a delivery acknowledgement receipt.

16. The network node of claim 15 wherein the SMDPP acknowledgement message indicates an acknowledgement status related to the mobile communication device.

17. The network node of claim 15 wherein the network node is further operable to communicate with at least one short message entity, the processor further configured to perform at least the following: receiving an SMS message from the short message entity; transmitting an SMDPP message addressed to the mobile communication device; wherein the SMDPP acknowledgement received acknowledges transmission of the SMDPP message addressed to the mobile communication device.

18. The network of claim 17, wherein the processor is further configured to perform at least the following: associating an email address with the SMS message; and transmitting, in the transmitting step, an indication of the delivery acknowledgement receipt to the email address.

19. The network node of claim 17 wherein the delivery acknowledgement receipt is sent to a pre-specified destination.

20. The network node of claim 19 wherein the pre-specified destination is stored as destination preferences modifiable by a user of the short message entity.

21. The network of claim 15, wherein the short message entity is a mobile communication device in communication with the node; and the delivery acknowledgement receipt is transmitted the mobile communication device in communication with the node.

22. The network of claim 15, wherein the processor is further configured to perform at least the following: capturing the SMDPP acknowledgement message.

23. The network of claim 15 wherein the SMDPP acknowledgement message indicates unsuccessful communication with the mobile communication device.

24. The network of claim 15 wherein the SMDPP acknowledgement message indicates the mobile communication device is inactive.

25. The network of claim 15 wherein the SMDPP acknowledgement message indicates the mobile communication device is incapable of receiving SMS.