Method And System For Associating Related Messages Of Different Types
Abstract
Associating related messages of different types at a client device includes receiving user input via a user interface of a client device. The user input is for associating a first message of a first type with at least one other message of a different type. A common session ID is associated with the first message and the at least one message of a different type. The first message is sent with the associating common session ID according to a first messaging protocol corresponding to the first message type. The at least one message of a different type is sent with the associating common session ID according to a messaging protocol different than the first messaging protocol and corresponding to the at least one message of a different type. The message types consist of voice, email, SMS, MMS, FTP, and HTTP.
Claims
exact text as granted — not AI-modified1 . A method for associating related messages of different types at a client device, the method comprising:
receiving user input via a user interface of a client device, the user input for associating a first message of a first type with at least one other message of a different type, wherein the first type and the different type are selected from the group of message types consisting of a voice message, an email, a short messaging service (SMS) message, a multimedia messaging service (MMS) message, a file transfer protocol FTP file, and a hyper-text transfer protocol (HTTP) link; associating a common session ID with the first message and the at least one message of a different type; sending the first message with the associating common session ID according to a first messaging protocol corresponding to the first message type; and sending the at least one message of a different type with the associating common session ID according to a messaging protocol different than the first messaging protocol and corresponding to the at least one message of a different type.
2 . The method of claim 1 , wherein associating a common session ID with the first message and the at least one message of a different type comprises:
determining whether a current session ID is associated with the first message; responsive to determining that a former session ID is associated with the first message, associating the current session ID with the at least one message of a different type as a common session ID; and responsive to determining that a current session ID is not associated with the first message, associating a common session ID with the first message and with the at least one message of a different type.
3 . The method of claim 2 wherein associating a common session ID with the first message and with the at least one message of a different type includes creating a common session ID by the client device.
4 . The method of claim 2 wherein associating a common session ID with the first message and with the at least one message of a different type includes negotiating a common session ID with an outside source by the client device.
5 . The method of claim 1 wherein receiving user input includes receiving user input for creating the first message at the client device.
6 . A computer readable medium storing a computer program, executable by a machine, for associating related messages of different types at a client device, the computer program comprising executable instructions for:
receiving user input via a user interface of a client device, the user input for associating a first message of a first type with at least one other message of a different type, wherein the first type and the different type are selected from the group of message types consisting of a voice message, an email, a short messaging service (SMS) message, a multimedia messaging service (MMS) message, a file transfer protocol FTP file, and a hyper-text transfer protocol (HTTP) link; associating a common session ID with the first message and the at least one message of a different type; sending the first message with the associating common session ID according to a first messaging protocol corresponding to the first message type; and sending the at least one message of a different type with the associating common session ID according to a messaging protocol different than the first messaging protocol and corresponding to the at least one message of a different type.
7 . The computer readable medium of claim 6 , wherein associating a common session ID with the first message and the at least one message of a different type comprises:
determining whether a current session ID is associated with the first message; responsive to determining that a former session ID is associated with the first message, associating the current session ID with the at least one message of a different type as a common session ID; and responsive to determining that a current session ID is not associated with the first message, associating a common session ID with the first message and with the at least one message of a different type.
8 . The computer readable medium of claim 7 wherein associating a common session ID with the first message and with the at least one message of a different type includes creating a common session ID by the client device.
9 . The computer readable medium of claim 7 wherein associating a common session ID with the first message and with the at least one message of a different type includes negotiating a common session ID with an outside source by the client device.
10 . The computer readable medium of claim 6 wherein receiving user input includes receiving user input for creating the first message at the client device.
11 . A system for associating related messages of different types at a client device, the system comprising:
a processor in communication with a memory, the processor and memory in conjunction configured to:
receive user input via a user interface of a client device, the user input for associating a first message of a first type with at least one other message of a different type, wherein the first type and the different type are selected from the group of message types consisting of a voice message, an email, a short messaging service (SMS) message, a multimedia messaging service (MMS) message, a file transfer protocol FTP file, and a hyper-text transfer protocol (HTTP) link;
associate a common session ID with the first message and the at least one message of a different type;
send the first message with the associating common session ID according to a first messaging protocol corresponding to the first message type; and
send the at least one message of a different type with the associating common session ID according to a messaging protocol different than the first messaging protocol and corresponding to the at least one message of a different type.
12 . The system of claim 11 , wherein associating a common session ID with the first message and the at least one message of a different type comprises:
determining whether a current session ID is associated with the first message; responsive to determining that a former session ID is associated with the first message, associating the current session ID with the at least one message of a different type as a common session ID; and responsive to determining that a current session ID is not associated with the first message, associating a common session ID with the first message and with the at least one message of a different type.
13 . The system of claim 12 wherein associating a common session ID with the first message and with the at least one message of a different type includes creating a common session ID by the client device.
14 . The system of claim 12 wherein associating a common session ID with the first message and with the at least one message of a different type includes negotiating a common session ID with an outside source by the client device.
15 . The system of claim 11 wherein receiving user input includes receiving user input for creating the first message at the client device.Join the waitlist — get patent alerts
Track US2009067592A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.