SMS+: short message service plus context support for social obligations

• US 20070067398A1
• Filed: 09/21/2005
• Published: 03/22/2007
• Est. Priority Date: 09/21/2005
• Status: Active Grant

• Current Assignee: U Owe Me, Inc.
• Original Assignee: U Owe Me, Inc.
• Inventors: Karmarkar, Amit
• Granted Patent: US 7,580,719 B2
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04W 4/14 Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]

Abstract

A Short Message Service (SMS) enables a sender to send an asynchronous short message (often informal) from his source device to one or more receiving devices that are specified by the sender and represent one or more recipients. The SMS associates with each particular short message specific context information about that particular message (including its originator, recipient, type, reason for sending, and the sending time). The SMS may associate further specific context information it has already about previous messages or previously-established links and patterns, without further input from the sender, and display that associated specific context information to the recipient. By parsing and analyzing the combined asynchronous short message and its associated specific context information, using cultural, linguistic, and reverse-association means, a SMS can provide context-driven support for any social or formal obligation(s) conveyed by an individual short message.

Claims

1. A computer-implemented method whereby a Short Message Service provides contextual support for social obligations, said method comprising:

taking a Short Message from a Sender for at least one Recipient through a first Unit;

processing the Short Message through at least one Server, said processing further comprising;

parsing the Short Message;

generating the Short Message'"'"'s Context Metadata; and

,

associating explicitly the Context Metadata to the Short Message;

and,

delivering the Short Message and its Context Metadata to the Recipient through a second Unit.

2. A method as in claim 1, wherein the Sending Unit may translate between Wireless Access Protocol (‘

WAP’

) and Internet Protocol by translating WAP POST to HTTP POST before sending the SM from a WAP Unit to the Server, and by translating WAP GET to HTTP GET before sending any SM from the Server to a WAP Unit.

3. A method as in claim 1, further comprising:

allowing a Sender to explicitly enter Context Metadata; and

,

using Context Metadata permutations entered by the Sender to explicitly govern any sending of prepared SMs.

4. A method as in claim 1, further comprising:

attaching a current Global Positioning System (‘

GPS’

) location for the Sender as Context Metadata; and

,

allowing at least one geographical reference to be used when examining, analyzing, or responding to the SM.

5. A method as in claim 1, wherein the step of processing the Short Message through at least one Server further comprises:

storing the Short Message and its Context Metadata;

identifying the Sender;

then comparing the Sender against a database containing all previous Senders; and

,

incorporating the Sender into the database if not already present;

identifying the Recipient;

then comparing the Recipient against a database containing all previous Recipients; and

,

incorporating the Recipient into the database if not already present;

analyzing the parsed Short Message and its Context Metadata to identify at least one key token and then;

comparing each identified key token against a database containing all previous key tokens, said database containing each previous key token and its respective association with the Sender; and

,

incorporating into the database each identified key token not already present and its association with the Sender;

and,

further analyzing the parsed Short Message and its Context Metadata to identify at least one message structure pattern and then;

comparing each identified message structure pattern against a database of previous message structure patterns, said database containing each previous message structure pattern and its respective association with the Sender; and

,

incorporating into the database each identified message structure pattern not already present and its association with the Sender.

6. A method as in claim 5, further comprising:

searching through the database for each offer matching at least one key token, each said offer coming from a third party (neither Sender nor Recipient);

and,

upon finding any offer matching at least one key token;

attaching the offer to the Short Message and its Context Metadata;

sending the Short Message and its Context Metadata and the offer to the Recipient;

creating a duplicate of the Short Message and its Context Metadata with the attached offer;

and,

sending the duplicate of the Short Message and its Context Metadata with the attached offer back to the Sender.

7. A method as in claim 6, further comprising:

searching through the database for each offer matching at least a message structure pattern of the Short Message, each said offer coming from a third party (neither Sender nor Recipient); and

,

upon finding any offer matching at least a message structure pattern of the Short Message;

attaching the offer to the Short Message and its Context Metadata;

sending the Short Message and its Context Metadata and the offer to Recipient;

creating a duplicate of the Short Message and its Context Metadata with the attached offer; and

,

sending the duplicate of the Short Message and its Context Metadata with the attached offer back to the Sender.

8. A method as in claim 6, further comprising:

searching the database containing all previous Senders periodically and for each previous Sender;

retrieving each stored Short Message and its Context Metadata sent by that Sender;

passing the retrieved Short Message and its Context Metadata sent by that Sender through a text analyzer;

analyzing the text and Context Metadata;

identifying a date and time element for the Short Message;

comparing the current date and time to the date and time element of the Context Metadata; and

,

determining whether the text and Context Metadata represents an uncompleted commitment, and if so, then;

generating a follow-up message; and

,

sending the follow-up message to the Sender.

9. A method as in claim 8, wherein the step of analyzing the text and Context Metadata further comprises identifying a User who is responsible for taking action at or before a particular date and time;

and, upon determining that the text and Context Metadata represents an uncompleted commitment, the Server generates and sends a follow-up message to that User.

10. A method as in claim 1, A method as in claim 1, wherein the step of processing the Short Message through at least one Server further comprises:

analyzing the SM and associated Context Metadata for Cultural Linkages, by comparing the SM and associated Context Metadata to a Cultural Database with patterns and data specific to Users of the SMS.

11. A method as in claim 10, wherein the Server includes at least two different Cultural Databases and the step of processing the Short Message through at least one Server further comprises:

comparing the SM and associated Context Metadata to each Cultural Database with patterns and data specific to Users of the SMS until finding a Sender'"'"'s Cultural Database containing the closest match to the Sender;

comparing the SM and associated Context Metadata to each Cultural Database with patterns and data specific to Users of the SMS until finding a Recipient'"'"'s Cultural Database containing the closest match to the Recipient; and

,

comparing the SM according to a translation norm for translating a SM from the Sender'"'"'s Cultural Database to the Recipient'"'"'s Cultural Database.

12. A method as in claim 11, further comprising incorporating an evolving set of common norms between a particular Sender and a particular Recipient arising from mutual interactions creating this new set of cultural norms through shared joint behavior and message forms

13. A method as in claim 11, further comprising making explicit a determined cultural differentiation by display differentiation according to cultural linkage.

14. A method as in claim 1, wherein the step of parsing the Short Message further comprises using a Language Parser designed for SMS Slang.

15. A method as in claim 14, wherein the step of parsing the Short Message further comprises using a Language Parser for different language representations including at least two distinct language representations.

16. A method as in claim 15, wherein a first language representation is for a standard alphabetic language and the second language representation is for an informal, character-derived, compilation of known emotional associations to particular punctuation groupings.

17. A method as in claim 11, wherein the step of processing the SM according to a translation norm for translating a SM from the Sender'"'"'s Cultural Database to the Recipient'"'"'s Cultural Database further comprises using software that allows SM transmission and translation across at least two Alternative Cultural Norms.

18. A method as in claim 17, wherein the transmission and translation across at least two Alternative Cultural Norms includes:

using software that allows SM transmission and translation across at least two different human languages.

19. A method as in claim 17, wherein the transmission and translation across at least two Alternative Cultural Norms includes:

using software that allows SM transmission and translation across at least two different Alternative Cultural Norms distinguished by the respective geographic locations of the Sender and the Recipient.

20. A method as in claim 5, wherein the step of processing the Short Message through at least one Server further comprises using software having pattern-completion means which, through decoding and variable binding from one or more SMs, generates suggested responses to a received SM.

21. A method as in claim 5, wherein the step of processing the Short Message through at least one Server further comprises using software enabling translation across different media display capabilities.

22. A method as in claim 21, wherein the step of using software enabling translation across different media display capabilities includes, for translating between Internet and cellphone SMs:

when moving from Wireless Access Protocol (‘

WAP’

) to Internet;

for each WAP GET, substituting a HTTP GET; and

,

for each WAP POST, substituting a HTTP POST;

and,

when moving from Internet to WAP;

for each HTTP GET, substituting a WAP GET; and

,

for each HTTP POST, substituting a WAP POST.

23. A method as in claim 22, further comprising sending to the Recipient a further SM by downloading the context-support message from the SMS.

24. A method as in claim 5, wherein the step of processing the Short Message through at least one Server further comprises generating additional linked information that enhances the context available but not specifically incorporated in the original SM.

25. A method as in claim 24, wherein the step of generating additional linked information that enhances the context available but not specifically incorporated in the original SM further comprises including a ‘

return receipt’

SM that would, upon confirmation of a successful transmission to the Receiving Unit, notify the Sender of a completed and therefore now-available communication between Sending and Receiving Units.

26. A method as in claim 25, further comprising sending the ‘

return receipt’

SM to the original Sender upon actual activation, and thus presumed reading, of the SM by the Recipient.

27. A method as in claim 5, wherein the step of processing the Short Message through at least one Server further comprises comparing the Core Text to Third-Party offers stored in the database as open-ended messages to which both Sender and Recipient match the intended offerees of the Third Party, upon analysis of the Core Text, Context Metadata and Cultural Linkages of the SM.

28. A method as in claim 5, wherein the step of processing the Short Message through at least one Server further comprises measuring the entire SM, including the Core Text, Context Metadata, and Cultural Linkages, against formalization norms contained in the database to determine the extent to which the SM matches any such norm and thus can be said to have committed the Sender to an informal contract, formal contract, or fully-binding and even assignable commitment.

29. A method as in claim 28, further comprising allowing the SMS to suggest a response that will match one or more partially-completed formal norms.

30. A method as in claim 28, further comprising allowing the SMS to send at least one additional message to the parties, signaling the completion of any formal norm.

31. A method as in claim 28, further comprising the SMS:

analyzing and comparing the partially-created pattern against a matching set of potential completed patterns; and

,

suggesting for each potential completed pattern at least one inferential further step that would complete that potential completed pattern.

32. A method as in claim 28, further comprising allowing the SMS to indicate when the absence of any overt responsive effort will passively allow the creation of a formalization norm.

33. A method as in claim 28, wherein the SMS, after processing the SM, offers the party closest to converting the less-than-formal commitment into a final commitment, advice as to either strengthening, or deliberately removing, such from the dealings between the two parties.

34. A method as in claim 5, wherein the step of processing the Short Message through at least one Server further comprises, when a culturally-supported even though less than formal commitment has been instantiated through the SMS, having the SMS provide both an explicit record of the less-than-formal commitment, and link the Sender and Recipient to the goods and services of a third party who may wish to offer the same.

35. A computer-implemented method whereby a Short Message Service provides contextual support for social obligations, said method comprising:

storing on a first Unit a SM intended for at least one particular Recipient, said SM having already been;

previously prepared by and sent from a Server; and

,

an association of both Core Text and Context Metadata;

using the first Unit to detect a Receiving Unit that the Context Metadata indicates is both within Close Message Proximity of the first Unit and associated with the particular Recipient;

using the first Unit to send the SM directly to the Receiving Unit; and

,

using the first Unit to send to the Server notice that the SM has been sent to that particular Recipient.

36. A method as in claim 35, further comprising adding to the SM send directly to the Receiving Unit a notification that the SMS can be contacted for interpretative support.

37. A method as in claim 35, further comprising:

allowing each of a first Unit and second Unit to test its respective locality for the presence of a different Unit; and

,

upon detection of mutual Close Message Proximity, permitting direct exchange of SMs between the first Unit and second Unit without requiring the SMS Central to handle the exchange.

38. A method as in claim 37, further comprising:

sending to the Server a copy of each SM plus its associated Context Metadata directly exchanged between the first Unit and the second Unit; and

,

processing the SM the Server, said processing further comprising;

parsing the SM;

generating the SM'"'"'s Context Metadata; and

,

associating explicitly the Context Metadata to the Short Message.