Transfer identification software enabling electronic communication system

• US 20060210040A1
• Filed: 03/16/2005
• Published: 09/21/2006
• Est. Priority Date: 03/16/2005
• Status: Abandoned Application

• Current Assignee: Vonage Network LLC (Telefonaktiebolaget LM Ericsson)
• Original Assignee: Vonage Network LLC (Telefonaktiebolaget LM Ericsson)
• Inventors: Wason, Andrew, Citron, Jeffrey, Shah, Nilesh
• Application Number:
  US11/081,186
• Publication Number:
  US 20060210040A1
• Time in Patent Office: Days
• US Class Current: 379/189
• CPC Class Codes: H04M 7/003 Click to dial services

Abstract

A third party call control (3PCC) application program interface (API) provides the capability for users to use a web browser or other Internet capable software to place a call. A third party call control application program interface comprises a first uniform resource locator operable over the Internet to effect a call between a first telephonic device and a second telephonic device. The first uniform resource locator includes identification of the first telephonic device and identification of the second telephonic device.

Claims

1. A telephonic control method for effecting a telephone call comprising:

(a) receiving a software object comprising a software control operable to initiate a telephone call to a predetermined telephonic device;

(b) operating the software control to initiate the telephone call; and

(c) generating, with the software control, a uniform resource locator operable over a computer network to effect a call between the predetermined telephonic device and a second telephonic device.

2. The method of claim 1, wherein the uniform resource locator comprises means for identifying the predetermined telephonic device and identification of the second telephonic device.

3. The method of claim 2, wherein the identification of the predetermined telephonic device comprises a telephone number.

4. The method of claim 3, wherein the identification of the second telephonic device comprises a telephone number.

5. The method of claim 4, wherein the telephone number of the second telephonic device is entered by a receiver of the software object.

6. The method of claim 4, wherein the telephone number of the second telephonic device is defined in the software object.

7. The method of claim 1, wherein the uniform resource locator comprises a token operable to obtain identification of the predetermined telephonic device and identification of the second telephonic device.

8. The method of claim 7, wherein the token comprises a telephone number of the predetermined telephonic device.

9. The method of claim 7, wherein the token is operable to obtain identification and password information, said information being authenticated and validated before completion of the telephone call.

10. The method of claim 9, wherein the identification and password information is obtained from a database.

11. The method of claim 7, wherein the token comprises expiration information.

12. The method of claim 11, wherein the expiration information comprises at least one selected from expiration date and time of day, and wherein a restriction information on the second telephonic device is stored in a database.

13. A method of telephonic call completion comprising:

(a) receiving information indicating a call to be completed between a first telephonic device and a second telephonic device, said information comprising an account to which the call is to be billed, and wherein the information is generated by a software object;

(b) validating the account to which the call is to be billed; and

(c) completing the call between the first telephonic device and the second telephonic device.

14. The method of claim 13, wherein the received information comprises a token.

15. The method of claim 14, wherein the step (b) of validating the account to which the call is to be billed comprises:

(i) obtaining identification information and password information using the token; and

(ii) validating and authenticating the identification information and the password information.

16. The method of claim 15, wherein the identification and password information are obtained from a database using the token.

17. The method of claim 15, wherein the identification information comprises a telephonic number.

18. A software object for telephonic call completion comprising:

a software control comprising means for generating a uniform resource locator operable over a computer network to effect a call between a first telephonic device and a second telephonic device.

19. The software object of claim 18, wherein the uniform resource locator comprises identification of the first telephonic device and identification of the second telephonic device.

20. The software object of claim 19, wherein the identification of the at least one of the first and second telephonic devices is a telephone number.

21. The software object of claim 19, wherein the identification of the second telephonic device is a telephone number.

22. The software object of claim 21, wherein the telephone number of the second telephonic device is entered by a receiver of the software object.

23. The software object of claim 21, wherein the telephone number of the second telephonic device is predefined.

24. The software object of claim 18, wherein the uniform resource locator comprises a token, said token operable to obtain identification of the first telephonic device and identification of the second telephonic device.

25. The software object of claim 24, wherein the token comprises the telephone number of at least one of the first and second telephonic devices.

26. The software object of claim 24, wherein the token comprises means for obtaining identification information and password information, and means for authenticating and validating the identification information and password information before completion of the call.

27. The software object of claim 26, wherein the identification information and password information is obtained from a database.

28. The software object of claim 24, wherein the token comprises expiration information, includes time of day restrictions, or includes restrictions on the second telephonic device.

29. The software object of claim 28, wherein the expiration information comprising date and the time of day information, and wherein the expiration information for the second telephonic device is stored in a database.