IP Library Patent Application 14300905
Patent Application
App. No. 14/300,905

SYSTEMS AND METHODS FOR IDENTIFYING AND UPDATING SERVICE ACCOUNT INFORMATION

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 None
App. No.
14/300,905
Abstract

Systems and methods for identifying and updating service account information on a service provider system are provided herein. In some embodiments, a method for identifying and updating service account information on a service provider system may include receiving a first request to register a user account from a mobile app installed on a user device, wherein the first request includes a unique communication identifier, sending a communication message directed to the unique communication identifier including a uniform resource locator (URL) address of a website, receiving, via the website, payment information, an indication of the user account, and an indication of a purchased amount, and updating account balance information associated with the user account based on the indication of the purchased amount.

Claims (49)

1 . A computer-implemented method for identifying and updating service account information on a service provider system, comprising:

receiving a first request to register a user account from a mobile app installed on a user device, wherein the first request includes a unique communication identifier;

sending a communication message directed to the unique communication identifier including a uniform resource locator (URL) address of a website;

receiving, via the website, payment information, an indication of the user account, and an indication of a purchased amount; and

updating account balance information associated with the user account based on the indication of the purchased amount.

2 . The computer-implemented method of claim 1 , wherein the communication message is one of an email message, an Short Message Service (SMS) message, or a Multimedia Messaging Service (MMS) message.

3 . The computer-implemented method of claim 1 , wherein the communication message sent is triggered by a successful registration of the user account.

4 . The computer-implemented method of claim 1 , wherein the communication message sent is triggered when an account balance is below a predefined threshold.

5 . The computer-implemented method of claim 1 , wherein the URL address in the communication message sent includes user account information.

6 . The computer-implemented method of claim 5 , wherein the user account information is obtained from the first request.

7 . The computer-implemented method of claim 5 , wherein the user account information was stored in a database associated with the user account before the first request is received.

8 . The computer-implemented method of claim 5 , the method further comprising:

receiving a second request for the website at the URL address from the user device; and

sending the requested website to the user device pre-populated with at least some of the user account information.

9 . The computer-implemented method of claim 1 , wherein the method further comprises sending the updated account balance information to the first device.

10 . The computer-implemented method of claim 1 , wherein the communication message is sent to the first device.

11 . The computer-implemented method of claim 1 , further comprising:

receiving a request to access paid services from the mobile app;

providing access to the paid services by the mobile app; and

deducting an amount from the account balance associated with the mobile app for the paid services accessed by the mobile app.

12 . The computer-implemented method of claim 1 , wherein the unique communication identifier is one of a phone number or an email address.

13 . The computer-implemented method of claim 1 , wherein the mobile app is a Voice over Internet Protocol (VoIP) telecommunication app, and the purchased amount can be used for paid VoIP telecommunication services.

14 . A computer-implemented method for registering a mobile app and obtaining mobile app credits, comprising:

downloading the mobile app from a first entity;

sending a first request to register a user account associated with the mobile app to a second entity, wherein the request includes a unique communication identifier;

receiving, responsive to the first request sent, a communication message directed to the unique communication identifier including a uniform resource locator (URL) address of a website; and

displaying the website in a browser application responsive to receiving a selection of the URL address; and

submitting, via the browser, payment information, an indication of the user account, and a purchase amount for use with the mobile app.

15 . The computer-implemented method of claim 14 , wherein the URL address in the communication message received includes user account information.

16 . The computer-implemented method of claim 15 , wherein the user account information is obtained from at least one of the communication message received or the mobile app.

17 . The computer-implemented method of claim 15 , wherein the website displayed is pre-populated with at least some of the user account information.

18 . The computer-implemented method of claim 14 , wherein the method further comprises receiving updated account balance information.

19 . The computer-implemented method of claim 14 , wherein the mobile app is a Voice over Internet Protocol (VoIP) telecommunication app, and the mobile app credits can be used for paid VoIP telecommunication services.

20 . The computer-implemented method of claim 19 , wherein the second entity is a VoIP telecommunication service provider.

21 . A system for identifying and updating service account information on a service provider system, comprising:

a user account database that stores user account information;

an account services system including at least one processor comprising:

a registration module configured to receive a first request to register a user account from a mobile app installed on a user device, wherein the first request includes a unique communication identifier; and

an account balance monitor module configured to send a communication message directed to the unique communication identifier including a uniform resource locator (URL) address of a secure transaction processing system website; and

the secure transaction processing system including a website configured to:

receive payment information, and indication of the user account, and a purchase amount; and

update account balance information associated with the user account based on the indication of the purchased amount.

22 . The system of claim 21 , wherein the communication message is one of an email message, a Short Message Service (SMS) message, or a Multimedia Messaging Service (MMS) message.

23 . The system of claim 21 , wherein the account balance monitor module is configured to send the communication message upon a successful registration of the user account.

24 . The system of claim 21 , wherein the account balance monitor module is configured to send the communication message when an account balance is below a predefined threshold.

25 . The system of claim 21 , wherein the URL address in the communication message sent includes user account information.

26 . The system of claim 25 , wherein the user account information is obtained from the first request.

27 . The system of claim 25 , wherein the user account information was stored in a database associated with the user account before the first request is received.

28 . The system of claim 21 , wherein the unique communication identifier is one of a phone number or an email address.

Assignments (7)
RELEASE OF SECURITY INTEREST Recorded Jul 28, 2022
From: JPMORGAN CHASE BANK, N.A.
To: VONAGE AMERICA INC.; VONAGE HOLDINGS CORP.; VONAGE BUSINESS INC.; NEXMO INC.; TOKBOX, INC.
Reel/Frame 061002/0340 →
MERGER Recorded Mar 31, 2016
From: VONAGE NETWORK LLC
To: VONAGE AMERICA INC.
Reel/Frame 038320/0327 →
CORRECTIVE ASSIGNMENT TO CORRECT THE PATENT APPLICATION NUMBER 13966486 PREVIOUSLY RECORDED ON REEL 033545 FRAME 0424. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY INTEREST. Recorded Jan 21, 2016
From: VONAGE HOLDINGS CORP.; VONAGE NETWORK LLC; VONAGE BUSINESS SOLUTIONS INC.; VONAGE AMERICA INC.
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 037570/0203 →
SECURITY INTEREST Recorded Jul 29, 2015
From: VONAGE HOLDINGS CORP.; VONAGE AMERICA INC.; VONAGE BUSINESS SOLUTIONS, INC.; VONAGE NETWORK LLC
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 036205/0485 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 16, 2014
From: ARAZI, CHEN
To: VONAGE NETWORK LLC
Reel/Frame 033748/0294 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 16, 2014
From: ORNOY, VAL
To: VONAGE HOLDINGS CORP.
Reel/Frame 033748/0455 →
SECURITY INTEREST Recorded Aug 14, 2014
From: VONAGE HOLDINGS CORP.; VONAGE NETWORK LLC; VONAGE BUSINESS SOLUTIONS INC.; VONAGE AMERICA INC.
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 033545/0424 →