IP Library Granted Patent US 8,971,858
Granted Patent B2
US 8,971,858 · App. 13/274,303 · Granted Mar 3, 2015

Information messaging system

Inventor: Nitesh Ratnakar (Elkins, WV)
H04M1/274516H04M1/274508H04M3/4931H04M2203/253H04W8/18
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,971,858
App. No.
13/274,303
Granted
Mar 3, 2015
Kind
B2
Abstract

A method of transmitting contact information to an approved mobile communication device includes receiving an input representative of desired contact information located on a first web page and an input representative of the identity of a desired mobile communication device. The method also includes saving information representative of the desired contact information in a contact information database. The method also includes determining whether the desired mobile communication device is an approved device and transmitting to the desired mobile communication device information representative of a notification to send the information representative of the desired contact information. The method also includes receiving an input from the desired mobile communication device information representative of an acceptance to receive the information representative of the desired contact information, and transmitting to the desired mobile communication device information representative of the desired contact information.

Claims (26)

1. A method, performed by a sever running a software server application, for sending messages from vendors to respective mobile communication addresses of mobile users, the server application having access to a plurality of mobile user accounts each including mobile address identification information identifying a mobile communication address of a respective mobile user, the plurality of mobile user accounts containing a first mobile user account including first mobile address identification information identifying a first mobile communication address of a first mobile user, the server application having one or more vendor accounts each including vendor identification information identifying a respective vendor and a plurality of vendor messages of the respective vendor, the one or more vendor accounts containing a first vendor account including first vendor identification information identifying a first vendor and a first and second vendor messages of the first vendor, the method comprising:

sending, by the server application through the server, the first vendor message of the first vendor to the first mobile communication address of the first mobile user;

receiving, by the server application through the server, from the first mobile communication address of the first mobile user, acceptance information indicating the first mobile user's acceptance of the first vendor message of the first vendor;

verifying, by the server application through the server, from the received acceptance information that the first mobile user has accepted the first vendor message of the vendor; and

sending, by the server application through the server, the second vendor message of the first vendor, to the first mobile communication address of the first mobile user only after the verifying of the first mobile user having accepted the first vendor message of the first vendor.

2. The method of claim 1 , wherein the sending of the first vendor message of the first vendor to the first mobile communication address of the first mobile user is only performed when the server application receives mobile-user-interest-indicating information indicating or otherwise suggesting that the first mobile user may be interested in products or services provided by the first vendor.

3. The method of claim 2 , wherein the mobile-user-interest-indicating information received by the server application comprises information indicating that a mobile communication device of the first mobile user has downloaded or otherwise affirmatively acquired contact information of the first vendor.

4. The method of claim 1 , wherein the plurality of mobile user accounts further contain a second mobile user account including second mobile address identification information identifying a second mobile communication address of a second mobile user, the vendor accounts further containing a second vendor account including second vendor identification information identifying a second vendor and a message of the second vendor; and

wherein the method further comprises sending, by the server application through the server, the message of the second vendor, to the first mobile communication address of the first mobile user only after the verifying of the first mobile user having accepted the first vendor message of the first vendor.

5. The method of claim 4 , wherein the first and second vendors are competitors competing in one same industry.

6. The method of claim 1 , wherein for each of the one or more vendor accounts, each of the plurality of vendor messages of the respective vendor comprises at least one of text, an audio, an image and a video.

7. The method of claim 1 , wherein for each of the plurality of mobile user accounts, the mobile communication address of the mobile address identification information comprises at least one of a unique device ID identifying a mobile communication device of the respective mobile user, a phone number assigned to a mobile communication device of the respective mobile user, and a messaging address of the respective mobile user.

8. A server for sending messages from vendors to respective mobile communication addresses of mobile users, the server comprising:

one or more processors; and

one or more system memories, said system memories storing a software server application, the server application having access to a plurality of mobile user accounts each including mobile address identification information identifying a mobile communication address of a respective mobile user, the plurality of mobile user accounts containing a first mobile user account including first mobile address identification information identifying a first mobile communication address of a first mobile user, the server application having one or more vendor accounts each including vendor identification information identifying a respective vendor and a plurality of vendor messages of the respective vendor, the one or more vendor accounts containing a first vendor account including first vendor identification information identifying a first vendor and a first and second vendor messages of the first vendor, said server application adapted to perform, when executed by the one or more processors, a set of steps comprising:

sending the first vendor message of the first vendor to the first mobile communication address of the first mobile user;

receiving from the first mobile communication address of the first mobile user acceptance information indicating the first mobile user's acceptance of the first vendor message of the first vendor;

verifying from the received acceptance information that the first mobile user has accepted the first vendor message of the first vendor; and

sending the second vendor message of the first vendor to the first mobile communication address of the first mobile user only after the verifying of the first mobile user having accepted the first vendor message of the first vendor.

9. The server of claim 8 , wherein the sending of the first vendor message of the first vendor to the first mobile communication address of the first mobile user is only performed when the server application receives mobile-user-interest-indicating information indicating or otherwise suggesting that the first mobile user may be interested in products or services provided by the first vendor.

10. The server of claim 9 , wherein the mobile-user-interest-indicating information received by the server application comprises information indicating that a mobile communication device of the first mobile user has downloaded or otherwise affirmatively acquired contact information of the first vendor.

11. The server of claim 8 , wherein the plurality of mobile user accounts further contain a second mobile user account including second mobile address identification information identifying a second mobile communication address of a second mobile user, the vendor accounts further containing a second vendor account including second vendor identification information identifying a second vendor and a message of the second vendor; and

wherein the set of steps performed by the server application further comprises a step of sending the message of the second vendor to the first mobile communication address of the first mobile user only after the verifying of the first mobile user having accepted the first vendor message of the first vendor.

12. The server of claim 11 , wherein the first and second vendors are competitors competing in one same industry.

13. The server of claim 8 , wherein for each of the one or more vendor accounts, each of the plurality of vendor messages of the respective vendor comprises at least one of text, an audio, an image and a video.

14. The server of claim 8 , wherein for each of the plurality of mobile user accounts, the mobile communication address of the mobile address identification information comprises at least one of a unique device ID identifying a mobile communication device of the respective mobile user, a phone number assigned to a mobile communication device of the respective mobile user, and a messaging address of the respective mobile user.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 8, 2025
From: MIRA ADVANCED TECHNOLOGY SYSTEMS, INC.
To: CONTACTWAVE LLC
Reel/Frame 069778/0811 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 12, 2024
From: RATNAKAR, NITESH, DR.
To: MIRA ADVANCED TECHNOLOGY SYSTEMS, INC.
Reel/Frame 068880/0971 →
Continuity (12)
Continuation In Part 11164318 · Nov 17, 2005
Continuation In Part 11306336 · Dec 23, 2005
Continuation In Part 11308900 · May 24, 2006
Continuation In Part 11966020 · Dec 28, 2007
Continuation In Part 12046358 · Mar 11, 2008
Continuation In Part 12049326 · Mar 15, 2008
Continuation In Part 12122705 · May 18, 2008
Continuation In Part 12140684 · Jun 17, 2008
Continuation In Part 12464097 · May 11, 2009
Continuation In Part 12508550 · Jul 23, 2009
Continuation In Part 12784978 · May 21, 2010
Related Publication 20120190350A1 · Jul 26, 2012