METHOD AND APPARATUS TO VALIDATE A SUBSCRIBER LINE

• US 20110187494A1
• Filed: 11/01/2010
• Published: 08/04/2011
• Est. Priority Date: 08/23/2001
• Status: Active Grant

• Current Assignee: Jolly Seven, Series 70 of Allied Security Trust I (Allied Security Trust)
• Original Assignee: Paymentone Corporation
• Inventors: Truitt, Jennifer R., Lynam, Joe M., Dawson, Ken R., Philbin, M. Brendan
• Granted Patent: US 8,379,815 B2
• Time in Patent Office: Days
• US Class Current: 340/5.8
• CPC Class Codes: G06Q 20/305 using wired telephone networks
• CPC Class Codes: G06Q 20/3224 Transactions dependent on location of M-devices
• CPC Class Codes: G06Q 20/325 using wireless networks
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 20/4014 Identity check for transactions
• CPC Class Codes: H04M 15/00 Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
• CPC Class Codes: H04M 15/41 Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
• CPC Class Codes: H04M 15/51 for resellers, retailers or service providers
• CPC Class Codes: H04M 15/68 Payment of value-added services
• CPC Class Codes: H04M 15/70 Administration or customization aspects; Counter-checking correct charges
• CPC Class Codes: H04M 15/73 Validating charges
• CPC Class Codes: H04M 15/88 Provision for limiting connection, or expenditure
• CPC Class Codes: H04M 2215/0116 Provision for limiting expenditure, e.g. limit on call expenses or account
• CPC Class Codes: H04M 2215/0164 Billing record, e.g. Call Data Record [CDR], Toll Ticket[TT], Automatic Message Accounting [AMA], Call Line Identifier [CLI], details, i.e. parameters, identifiers, structure
• CPC Class Codes: H04M 2215/0196 Payment of value-added services, mainly when their charges are added on the telephone bill, e.g. payment of non-telecom services, e-commerce, on-line banking
• CPC Class Codes: H04M 2215/54 Resellers-retail or service providers billing, e.g. agreements with telephone service operator, activation, charging/recharging of accounts
• CPC Class Codes: H04M 2215/70 Administration aspects, modify settings or limits or counter-check correct charges
• CPC Class Codes: H04M 2215/7072 Validate charges
• CPC Class Codes: H04M 3/38 Graded-service arrangements, i.e. some subscribers prevented from establishing certain connections queuing arrangements H04Q3/64
• CPC Class Codes: H04M 3/42068 where the identifier is used to access a profile

Abstract

A method is described of providing validation data associated with a subscriber line of a telecommunication network using a validation system. The method includes obtaining line data of the subscriber line wherein the line data is suitable for interrogating a line identification database (LIDB). The method interrogates the LIDB with the line data to obtain reference subscriber data associated with the line data, and processes the reference subscriber data to obtain validation data associated with the subscriber line. The method includes identifying a local exchange carrier (LEC) associated with the subscriber line to determine if a billing arrangement exists between the validation system and the LEC. The invention extends to a subscriber line validation system to validate a subscriber line of a communication network.

Claims

1. (canceled)

2. A computer-implemented method, the method comprising:

receiving a first request via the Internet for a first transaction for goods or services between a user and a vendor;

obtaining a billing telephone number of the user;

automatically, utilizing an application programming interface, charging the first transaction to a subscriber account associated with the billing telephone number;

receiving a second request via the Internet for a second transaction for goods or services between the user and a vendor;

automatically, using one or more processors, detecting that charging to the account associated with the billing telephone number has not occurred;

automatically, in response to an event indicative of an option to charge the second transaction to the user, using an alternative payment method, the event being subsequent to the charging of the first transaction to the subscriber account associated with the billing telephone number; and

completing the second transaction using the alternative payment method and not billing the subscriber account.

3. The method of claim 2, wherein the alternative payment method is a credit card payment method.

4. The method of claim 2, wherein the alternative payment method is a debit card payment method.

5. The method of claim 2, wherein the subscriber account is a telephone account.

6. The method of claim 5, wherein the charging has not occurred as the subscriber account has been blocked from further billing.

7. The method of claim 5, wherein the telephone number is associated with a wireless device.

8. The method of claim 5, wherein the telephone number is associated with a landline device.

9. The method of claim 2, wherein the first request and the second request are received from a device operatively connected to the Internet.

10. The method of claim 9, wherein the first transaction for goods or services is associated with an online game.

11. The method of claim 2, wherein the billing telephone number is sourced from the user.

12. The method of claim 11, wherein the first transaction for goods or services is associated with an online game.

13. The method of claim 2, wherein the first transaction for goods or services is associated with an online game.

14. The method of claim 2, wherein:

the receiving of the first request is from a first vendor computer system, the first vendor computer system being controlled by a first vendor; and

the receiving of the second request is from a second vendor computer system, the second vendor computer system being controlled by a second vendor.

15. The method of claim 2, wherein the receiving of the second request is from a user device, the user device being controlled by the user.

16. The method of claim 2, wherein the obtaining of the billing telephone number of the user comprises utilizing an automatic number identification service.

17. The method of claim 2, wherein the detecting that billing to the subscriber account associated with the billing telephone number has not occurred includes detecting a response code associated with a telephone number associated with a wireless service provider.

18. The method of claim 2, further comprising receiving a PIN number from a user device.

19. The method of claim 18, wherein the charging to the subscriber account does not occur in the event of a threshold for bad PIN attempts being exceeded.

20. The method of claim 2, further comprising receiving location data from a user and selectively denying charging to the subscriber account associated with the billing telephone number based on reference location data.

21. The method of claim 2, further comprising receiving a ZIP code associated with the user.

22. The method of claim 21, further comprising processing the received ZIP code and denying billing to the account associated with the billing telephone number in the event of the received ZIP code not matching a ZIP code provided in a database.

23. The method of claim 2, wherein the telephone number is associated with a cellular telephone.

24. The method of claim 2, wherein the first transaction for goods or services is for music or software.

25. A system comprising:

means for receiving a first request via the Internet for a first transaction for goods or services between a user and a vendor;

means for obtaining a billing telephone number of the user;

means for automatically, utilizing an application programming interface, charging the first transaction to a subscriber account associated with the billing telephone number;

means for receiving a second request via the Internet for a second transaction for goods or services between the user and a vendor;

means for automatically, using one or more processors, detecting that charging to the subscriber account associated with the billing telephone number has not occurred;

means for automatically, in response an event indicative of an option to charge the second transaction to the user, using an alternative payment method, the event being subsequent to the charging of the first transaction to the subscriber account associated with the billing telephone number; and

means for completing the second transaction using the alternative payment method and not billing the subscriber account.

26. A computer-implemented system comprising:

a receiving module configured to receive a first request via the Internet for a first transaction for goods or services between a user and a vendor and a second request via the Internet for a second transaction for goods or services between the user and a vendor;

a billing telephone number module to obtain a billing telephone number of the user;

a first charging module to charge, automatically, utilizing an application programming interface, the first transaction to a subscriber account associated with the billing telephone number;

a first detector to detect, automatically, using one or more processors, that charging to the subscriber account associated with the billing telephone number has been not occurred;

a second detector to detect, automatically, an event indicative of an option to charge the second transaction to the user using an alternative payment method, the event being subsequent to the charging of the first transaction to the account associated with the billing telephone number; and

a second charging module to complete the second transaction using the alternative payment method and not debiting the subscriber account.

27. The system of claim 26, wherein one or more of the modules are combined into a software program.

28. The system of claim 26, wherein the alternative payment method is a credit card payment method.

29. The system of claim 26, wherein the alternative payment method is a debit card payment method.

30. The system of claim 26, wherein the subscriber account is a telephone account.

31. The system of claim 26, wherein the charging to the subscriber account does not occur as the subscriber account has been blocked from further billing.

32. The system of claim 26, wherein the telephone number is associated with a wireless device.

33. The system of claim 26, wherein the telephone number is associated with a landline device.

34. The system of claim 26, wherein the first and second requests are received from a device operatively connected to the Internet.

35. The system of claim 34, wherein the first transaction for goods or services is associated with an online game.

36. The system of claim 26, wherein the billing telephone number is sourced from the user.

37. The system of claim 36, wherein the first transaction for goods or services is associated with an online game.

38. The system of claim 26, wherein the first transaction for goods or services is associated with an online game.

39. The system of claim 26, wherein:

the first request is from a first vendor computer system, the first vendor computer system being controlled by a first vendor; and

the second request is from a second vendor computer system, the second vendor computer system being controlled by a second vendor.

40. The system of claim 26, wherein the second request is from a user computer system, the user computer system being controlled by the user.

41. The system of claim 26, wherein the billing telephone number of the user is obtained utilizing an automatic number identification service.

42. The system of claim 26, wherein detecting that charging to the account associated with the billing telephone number has not occurred includes detecting a response code associated with telephone number associated with a wireless service provider.

43. The system of claim 26, further comprising receiving a PIN number from a user device.

44. The system of claim 43, wherein the charging to the subscriber account does not occur in the event of a threshold for bad PIN attempts being exceeded.

45. The system of claim 26, further comprising receiving location data from a user and selectively denying charging to the subscriber account associated with the billing telephone number based on reference location data.

46. The system of claim 26, further comprising receiving a ZIP code associated with the user.

47. The system of claim 46, further comprising processing the received ZIP code and denying billing to the subscriber account associated with the billing telephone number in the event of the received ZIP code not matching a ZIP code provided in a database.

48. The system of claim 26, wherein the billing telephone number is associated with a cellular telephone.

49. The system of claim 26, wherein the first transaction for goods or services is for music or software.

50. A machine-readable non-transitory medium having instruction data to cause a machine to:

receive a first request via the Internet for a first transaction for goods or services between a user and a vendor;

obtain a billing telephone number of the user;

automatically, utilizing an application programming interface, charge the first transaction to a subscriber account associated with the billing telephone number;

receive a second request via the Internet for a second transaction for goods or services between the user and a vendor;

automatically, using one or more processors, detecting that charging to the account associated with the billing telephone number has not occurred;

automatically in response an event indicative of an option to charge the second transaction to the user using an alternative payment method, the event being subsequent to the charging of the first transaction to the subscriber account associated with the billing telephone number; and

complete the second transaction using the alternative payment method and not billing the subscriber account.