Unified messaging system configured for management of short message service-type messages

• US 7,269,432 B2
• Filed: 02/10/2006
• Issued: 09/11/2007
• Est. Priority Date: 12/20/2000
• Status: Expired due to Term

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Lockwood, Robert James, Sealey, Robert Raymond, Gress, David Stephen
• Primary Examiner(s): ZEWDU, MELESS NMN
• Application Number:
  US11/350,811
• Publication Number:
  US 20060128409A1
• Time in Patent Office: 578 Days
• Field of Search: 4554141-4144, 455/466, 455 59- 61, 455/72, 455/418, 455/412.1, 455/412.2, 455/422.1, 455433-434, 455/463, 455/445, 455/432.3, 455/550.1, 455/556.1, 455560-561, 455/403, 455/415, 455/432.2, 455/566, 455/556.2, 455557-558, 710/11, 710105-106, 710314-315, 379 881- 8814, 379/93.31, 379/88.07, 379/88.8, 379/100.13, 709/230, 709/203, 709 1- 9, 709100-102, 709/104.1, 709/206, 709218-219, 725/32, 370/312, 370/313, 370/349, 370/390, 370/395.21, 370/395.5, 370/395.52, 370/203, 370/310, 370/310.1, 370/328, 370/338, 370/401, 370464-471
• US Class Current: 455/466
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression
• CPC Class Codes: H04L 51/56 Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04W 4/14 Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
• CPC Class Codes: H04W 4/18 Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
• CPC Class Codes: H04W 8/20 Transfer of user or subscriber data
• CPC Class Codes: H04W 80/08 Upper layer protocols network arrangements or communication protocols for networked applications H04L67/00
• CPC Class Codes: H04W 88/184 Messaging devices, e.g. message centre

Abstract

A unified communications system is configured for receiving, storing, and/or sending SMS messages based on management of the SMS messages according to a prescribed open standards-based protocol. The unified communications system includes an SMS module configured for receiving SMS messages according to SMPP protocol. The SMS module obtains source and destination information from the received SMS message, and accesses a subscriber profile directory for subscriber profile information based on at least one of the source and destination information. The SMS module generates a common format message that includes the SMS message, and selectively supplies the common format message to selected destinations based on the accessed subscriber profile information. The common format message may be stored in a prescribed message store, for example an IMAP directory, or output as an e-mail message to a prescribed destination. The SMS module also is configured for selectively supplying stored messages to a unified messaging subscriber as an SMS message based on the profile information on the unified messaging subscriber. Hence, the unified communications system enables SMS messaging users to send SMS messages to non SMS-type devices (e.g., telephones, e-mail clients, etc.) and retrieve stored common format messages (e.g., fax, e-mail, voice messages) using the SMS message system.

Claims

1. A method in a unified messaging server, the method comprising:

receiving a short message service (SMS) message by the unified messaging server according to short message peer-to-peer (SMPP) protocol;

accessing by the unified messaging server a subscriber directory, according to an open network protocol, for subscriber attribute information based on the received SMS message;

generating, based on the subscriber attribute information, at least one common format message based on enclosing the SMS message into the common format message by the unified messaging server; and

supplying the common format message by the unified messaging server to a selected destination according to a selected access protocol based on the subscriber attribute information.

2. The method of claim 1, wherein the supplying step includes storing the common format message in a subscriber message store, the selected destination corresponding to a messaging folder for a selected subscriber.

3. The method of claim 2, wherein the supplying step further includes storing the common format message as an e-mail message according to Internet Message Access Protocol (IMAP).

4. The method of claim 2, wherein the generating step includes generating within the at least one common format message a destination address based on the subscriber attribute information.

5. The method of claim 4, wherein the subscriber attribute information specifies at least one of a distribution list specified by an identified source of the SMS message, or a destination preference specified by an identified destination of the SMS message.

6. The method of claim 5, wherein the accessing step includes accessing the subscriber directory according to Lightweight Directory Access Protocol (LDAP) as the open network protocol for the subscriber attribute information.

7. The method of claim 1, wherein the supplying step includes outputting the common format message to the selected destination according to SMTP protocol.

8. The method of claim 1, wherein the generating step includes enclosing the SMS message within a body of a MIME data structure, and specifying within the MIME data structure that the body has an SMS type.

9. The method of claim 1, further comprising:

second generating a new SMS message including subscriber messaging information for a selected subscriber; and

outputting the new SMS message for the selected subscriber according to SMPP protocol.

10. The method of claim 9, wherein the second generating step includes obtaining subscriber messaging information, specifying stored unified messages within an assigned directory for the selected subscriber, from a subscriber message store according to a prescribed open network protocol.

11. The method of claim 10, wherein the subscriber messaging information specifies at least one of a stored SMS message, a voice message, a fax message, or an e-mail message, as a corresponding at least one of the stored unified messages.

12. The method of claim 10, wherein the obtaining step includes obtaining the subscriber messaging information from the subscriber message store according to IMAP protocol.

13. The method of claim 9, wherein the second generating step generates the new SMS message for the selected subscriber based on the corresponding subscriber attribute information for the selected subscriber.

14. The method of claim 9, wherein the second generating step includes:

retrieving from a subscriber message store at least one of a stored SMS message, a voice message, a fax message, or an e-mail message from a directory assigned for the selected subscriber; and

inserting the at least one message into the new SMS message.

15. The method of claim 14, wherein the inserting step includes converting the voice message into a text-based message, and inserting the text-based message into the new SMS message.

16. The method of claim 1, wherein the generating includes specifying the selected destination in a destination address field of the common format message based on the selected destination being specified by the subscriber attribute information.

17. A unified messaging server comprising:

a short message service (SMS) module configured for receiving SMS messages according to short message peer to peer (SMPP) protocol, the SMS module configured for generating a query for subscriber attribute information based on the received SMS message, and generating at least one common format message based on the subscriber attribute information and based on enclosing the SMS message into the at least one common format message;

a first interface resource configured for accessing the subscriber attribute information based on the query from a subscriber directory according to a prescribed open network protocol; and

a second interface resource configured for outputting the at least one common format message according to at least one of SMTP protocol or IMAP protocol.

18. The server of claim 17, wherein the first interface resource is configured for accessing the subscriber attribute information from the subscriber directory according to LDAP protocol.

19. The server of claim 18, wherein the SMS module is configured for generating a plurality of common format messages for respective destinations based on retrieval from the subscriber attribute information of a distribution list specified by the SMS message.

20. The server of claim 17, wherein the SMS module is configured for enclosing the SMS message within a body of a MIME data structure, and specifying within the MIME data structure that the body has an SMS type.

21. The server of claim 17, wherein the SMS module is configured for generating a new SMS message including subscriber messaging information for a selected subscriber, the SMS module outputting the new SMS message for the selected subscriber according to SMPP protocol.

22. The server of claim 21, wherein the SMS module obtains the subscriber messaging information from a subscriber message store according to NAP protocol based on the subscriber attribute information for the corresponding selected subscriber accessed by the first interface from the subscriber directory.

23. The server of claim 21, wherein the subscriber messaging information specifies at least one of a stored SMS message, a voice message, a fax message, or an e-mail message for the selected subscriber.

24. The server of claim 17, wherein the SMS module is configured for specifying a selected destination in a destination address field of the common format message based on the selected destination being specified by the subscriber attribute information.

25. A computer readable medium having stored thereon sequences of instructions for receiving a short message service (SMS) message by a unified messaging server, the sequences of instructions including instructions for performing the steps of:

receiving a short message service (SMS) message by the unified messaging server according to short message peer-to-peer (SMPP) protocol;

accessing by the unified messaging server a subscriber directory, according to an open network protocol, for subscriber attribute information based on the received SMS message;

generating, based on the subscriber attribute information, at least one common format message based on enclosing the SMS message into the common format message by the unified messaging server; and

supplying the common format message by the unified messaging server to a selected destination according to a selected access protocol based on the subscriber attribute information.

26. The medium of claim 25, wherein the supplying step includes storing the common format message in a subscriber message store, the selected destination corresponding to a messaging folder for a selected subscriber.

27. The medium of claim 26, wherein the supplying step further includes storing the common format message as an e-mail message according to Internet Message Access Protocol (IMAP).

28. The medium of claim 26, wherein the generating step includes generating within the at least one common format message a destination address based on the subscriber attribute information.

29. The medium of claim 28, wherein the subscriber attribute information specifies at least one of a distribution list specified by an identified source of the SMS message, or a destination preference specified by an identified destination of the SMS message.

30. The medium of claim 29, wherein the accessing step includes accessing the subscriber directory according to Lightweight Directory Access Protocol (LDAP) as the open network protocol for the subscriber attribute information.

31. The medium of claim 25, wherein the supplying step includes outputting the common format message to the selected destination according to SMTP protocol.

32. The medium of claim 25, wherein the generating step includes enclosing the SMS message within a body of a MIME data structure, and specifying within the MIME data structure that the body has an SMS type.

33. The medium of claim 25, further comprising instructions for performing the steps of:

second generating a new SMS message including subscriber messaging information for a selected subscriber; and

outputting the new SMS message for the selected subscriber according to SMPP protocol.

34. The medium of claim 33, wherein the second generating step includes obtaining subscriber messaging information, specifying stored unified messages within an assigned directory for the selected subscriber, from a subscriber message store according to a prescribed open network protocol.

35. The medium of claim 34, wherein the subscriber messaging information specifies at least one of a stored SMS message, a voice message, a fax message, or an e-mail message, as a corresponding at least one of the stored unified messages.

36. The medium of claim 34, wherein the obtaining step includes obtaining the subscriber messaging information from the subscriber message store according to IMAP protocol.

37. The medium of claim 34, wherein the second generating step includes:

retrieving from a subscriber message store at least one of a stored SMS message, a voice message, a fax message, or an e-mail message from a directory assigned for the selected subscriber; and

inserting the at least one message into the new SMS message.

38. The medium of claim 37, wherein the inserting step includes converting the voice message into a text-based message, and inserting the text-based message into the new SMS message.

39. The medium of claim 33, wherein the second generating step generates the new SMS message for the selected subscriber based on the corresponding subscriber attribute information for the selected subscriber.

40. The medium of claim 25, wherein the generating includes specifying the selected destination in a destination address field of the common format message based on the selected destination being specified by the subscriber attribute information.

41. A unified messaging server comprising:

means for receiving a short message service (SMS) message according to short message peer-to-peer (SMPP) protocol;

means for accessing a subscriber directory, according to an open network protocol, for subscriber attribute information based on the received SMS message;

means for generating, based on the subscriber attribute information, at least one common format message based on enclosing the SMS message into the common format message; and

means for supplying the common format message to a selected destination according to a selected access protocol based on the subscriber attribute information.

42. The server of claim 41, wherein the supplying means is configured for storing the common format message in a subscriber message store, the selected destination corresponding to a messaging folder for a selected subscriber.

43. The server of claim 41, wherein the supplying means is configured for outputting the common format message to the selected destination according to SMTP protocol.

44. The server of claim 41, wherein the generating means includes means for enclosing the SMS message within a body of a MIME data structure, and specifying within the MIME data structure that the body has an SMS type.

45. The server of claim 41, further comprising:

means for generating a new SMS message including subscriber messaging information for a selected subscriber; and

means for outputting the new SMS message for the selected subscriber according to SMPP protocol.

46. The ser of claim 41, wherein the means for generating is configured for specifying the selected destination in a destination address field of the common format message based on the selected destination being specified by the subscriber attribute information.