IP Library Patent Application 14291674
Patent Application
App. No. 14/291,674

METHOD AND SYSTEM FOR MANAGING DROPPED CALL OPERATIONS

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/291,674
Abstract

Methods and systems for managing dropped call operations are provided here. In some embodiments a method for managing dropped call operations may include receiving a first notification of a change in network connectivity during a communication session between a first user device and a second user device; receiving a second notification of a change in network connectivity; generating communication data for the communication session based on a time that the first notification of a change in network connectivity was received; and transmitting the communication data to a service provider.

Claims (38)

1 . A computer-implemented method for managing dropped call operations, comprising:

receiving a first notification of a change in network connectivity during a communication session between a first user device and a second user device;

receiving a second notification of a change in network connectivity;

generating communication data for the communication session based on a time that the first notification of a change in network connectivity was received; and

transmitting the communication data to a service provider.

2 . The method of claim 1 , wherein the first notification of a change in network connectivity identifies that network connectivity to the first user device is lost.

3 . The method of claim 1 , wherein the first notification of a change in network connectivity indicates a disconnection of the communication session between the first user device and the second user device.

4 . The method of claim 3 , further comprising storing a time associated with the first notification of a change in network connectivity.

5 . The method of claim 1 , wherein the first notification and the second notification are received by a Voice over Internet Protocol (VoIP) telecommunication application disposed on the first user device.

6 . The method of claim 1 , wherein the second notification of a change in network connectivity identifies that network connectivity to the first user device is restored.

7 . The method of claim 1 , wherein the communication session is a Session Initiation Protocol (SIP) session.

8 . The method of claim 1 , wherein the communication session is established using a Voice over Internet Protocol (VoIP) telecommunication application disposed on a first user device.

9 . The method of claim 1 , wherein generating communication data comprises:

identifying one or more communications that had an active status when the first notification was received; and

identifying for each of the identified one or more communications at least one of a start time of the communication, an end time of the communication, a length of the communication, a dialed number, a communication identifier, a caller number, or a callee number.

10 . The method of claim 9 , further comprising at least one of prompting a user of the first user device to redial at least one of the identified one or more communications or prompting the first user device to auto-redial at least one of the identified one or more communications.

11 . The method of claim 1 , further comprising:

receiving an acknowledgement response from the service provider; and

deleting data regarding one or more communication sessions that had an active status when the first notification was received.

12 . A computer-implemented method for managing dropped call operations comprising:

receiving communication data for at least one dropped communication from a user device;

verifying the at least one dropped communication has an active status; and

at least one of tearing down the at least one dropped communication, removing the at least one communications from a list of active communications in a current communications memory, or providing billing information for a communication session associated with the at least one dropped communication to a billing server.

13 . The method of claim 12 , wherein the communication data comprises at least one of a start time of the communication session, an time when network connectivity was lost during the communication session, a length of the communication, a dialed number, a communication identifier, a caller number, or a callee number for each of the at least one dropped communications.

14 . The method of claim 12 , wherein providing billing information comprises providing an end time of the communication session associated with when the communication data was received.

15 . The method of claim 12 , wherein providing billing information comprises providing an end time of the communication session associated with a time when network connectivity was lost during the communication session.

16 . A system for managing dropped call operations, comprising:

a mobile application configured to:

receive a first notification of a change in network connectivity during a communication session between a first user device and a second user device;

receive a second notification of a change in network connectivity;

generate communication data for the communication session based on a time that the first notification of a change in network connectivity was received; and

transmit the communication data to a service provider.

17 . The system of claim 16 , wherein the first notification of a change in network connectivity identifies that network connectivity to the first user device is lost, and wherein the second notification of a change in network connectivity identifies that network connectivity to the first user device is restored.

18 . The system of claim 16 , wherein the first notification of a change in network connectivity indicates a disconnection of the communication session between the first user device and the second user device.

19 . The system of claim 16 , wherein the communication session is established using a Voice over Internet Protocol (VoIP) telecommunication application disposed on a first user device, and the communication session is a Session Initiation Protocol (SIP) session.

20 . The system of claim 16 , wherein generating communication data comprises:

identifying one or more communications that had an active status when the first notification was received; and

identifying for each of the identified one or more communications at least one of a start time of the communication, an end time of the communication, a length of the communication, a dialed number, a communication identifier, a caller number, or a callee number.

Assignments (6)
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 →
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 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 18, 2014
From: MEGHANI, JAYA
To: VONAGE NETWORK LLC
Reel/Frame 033130/0317 →