Method and apparatus to validate a subscriber line

• US 7,848,504 B2
• Filed: 04/06/2006
• Issued: 12/07/2010
• Est. Priority Date: 08/23/2001
• Status: Expired due to Fees

• Current Assignee: Jolly Seven, Series 70 of Allied Security Trust I (Allied Security Trust)
• Original Assignee: Paymentone Corporation
• Inventors: Lynam, Joseph M, Philbin, M. Brendan, Dawson, Ken R., Truitt, Jennifer
• Primary Examiner(s): ADDY, THJUAN KNOWLIN
• Application Number:
  US11/400,737
• Publication Number:
  US 20070036341A1
• Time in Patent Office: 1,706 Days
• Field of Search: 379/220.01, 379/114.14, 379/207.13, 379/207.15, 379/142.01, 379/142.04, 379/142.05, 379/142.06, 379/88.2, 379/88.19, 705/44
• US Class Current: 379/207.13
• 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. An identity verification method, the method comprising:

obtaining automatic number identification (ANI) data or billing telephone number (BTN) data associated with a subscriber line of a telecommunications network;

obtaining identification data associated with a subscriber, said identification data being different from the ANI data or the BTN data;

searching a first database using the ANI data or the BTN data to determine first reference subscriber data;

searching a second database using the identification data to determine second reference subscriber data;

comparing the first reference subscriber data to the second reference subscriber data; and

verifying an identity of the subscriber if the first reference subscriber data corresponds to the second reference subscriber data.

2. The identity verification method of claim 1, wherein the obtaining of the ANI data or the BTN data comprises obtaining the ANI data or the BTN data from a merchant of goods or services.

3. The identity verification method of claim 1, wherein the obtaining of the identification data associated with a subscriber comprises obtaining the identification data from a merchant of goods or services.

4. The identity verification method of claim 1, wherein the obtaining of the ANI data or the BTN data, and the identification data, comprises obtaining the ANI data or the BTN data, and the identification data, from a merchant, the merchant being in the process of selling goods or services to the subscriber.

5. The identity verification method of claim 1, wherein the identification data is a ZIP code.

6. The identity verification method of claim 5, wherein the second database is a ZIP data source.

7. The identity verification method of claim 1, wherein the identification data is address data.

8. The identity verification method of claim 7, wherein the second database is an address data source.

9. The identity verification method of claim 1, wherein the first database is a line identification database (LIDB).

10. The identity verification method of claim 1, wherein the second database is distinct from the first database.

11. The identity verification method of claim 1, wherein the second reference subscriber data comprises an address of the subscriber.

12. The identity verification method of claim 1, wherein the comparing of the first reference subscriber data to the second reference subscriber data comprises determining whether a match exists within a predefined range or geographic area.

13. The identity verification method of claim 1, wherein the verifying of the identity of the subscriber comprises verifying the identity of the subscriber if the first reference subscriber data corresponds to the second reference subscriber data within a predetermined range.

14. The identity verification method of claim 1, further comprising providing a verification status notification to a merchant.

15. The identity verification method of claim 1, wherein the searching of the first database further comprises using the ANI data to determine the BTN data.

16. The identity verification method of claim 1, further comprising:

receiving a transaction amount to be charged to an account associated with the subscriber line; and

in response to the verifying of the identity of the subscriber, approving the transaction.

17. The identity verification method of claim 1, wherein the first reference subscriber data and the second reference subscriber data are in a form of one or more LIDB codes.

18. The identity verification method of claim 17, further comprising generating modified codes from the one or more LIDB codes.

19. The identity verification method of claim 18, further comprising arranging the modified codes into a billable group and a non-billable group.

20. The identity verification method of claim 1, further comprising, prior to the searching, ascertaining if the ANI data or the BTN data corresponds to a billable subscriber line.

21. The identity verification method of claim 20, wherein the ascertaining comprises checking if an area code associated with the line data has changed and checking if the ANI data or the BTN data are missing from the record.

22. The identity verification method of claim 20, wherein the ascertaining comprises interrogating a network database with the ANI data to determine if the subscriber line is a billable subscriber line, and, if so, generating a decline status or an approved status in response to the interrogation.

23. The identity verification method of claim 20, wherein the ascertaining comprises searching a threshold database to determine whether an account associated with the subscriber line has reached a maximum monetary amount.

24. The identity verification method of claim 20, wherein the ascertaining comprises searching an off network (OFFNET) database to determine whether an industry standard Numbering Plan Area (NPA), an NXX, or an operating company number (OCN) of the subscriber line is present in the OFFNET database.

25. The identity verification method of claim 20, wherein the ascertaining comprises searching an on network (ONNET) database to determine whether an industry standard Numbering Plan Area (NPA), an NXX, or an operating company number (OCN) of the subscriber line is present in the ONNET database.

26. The identity verification method of claim 20, wherein the ascertaining comprises searching a competitive local exchange carrier (CLEC) database to determine whether the ANI data or the BTN data is known to have ported to a CLEC and whether transactions cannot be billed to an account associated with the subscriber line.

27. The identity verification method of claim 20, wherein the ascertaining comprises searching a 42 BLOCK database to determine whether a billing block has been imposed on the subscriber line.

28. The identity verification method of claim 20, wherein the ascertaining comprises searching a block and cancel database to determine whether a request has been made to prevent further transactions from being billed to an account associated with the subscriber line.

29. The identity verification method of claim 20, wherein the ascertaining comprises searching an unbilled database to determine whether there is a history of unbillable bills associated with the subscriber line.

30. The identity verification method of claim 20, wherein the ascertaining comprises searching an unpaid bills database to determine whether there is a history of unpaid bills associated with the subscriber line.

31. The identity verification method of claim 1, further comprising, after determining of the first reference subscriber data, using the first reference subscriber data to search a regional account office (RAO) database to determine whether the RAO is billable.

32. The identity verification method of claim 1, further comprising, after determining the first reference subscriber data, receiving an operating company number (OCN) from the first database, and determining whether the OCN corresponds to a known competitive local exchange carrier (CLEC), and determining whether the OCN corresponds to an off network (OFFNET) CLEC.

33. The identity verification method of claim 1, further comprising, after determining the first reference subscriber data, using the first reference subscriber data to determine if a new Numbering Plan Area (NPA)/NXX and an operating company number (OCN) combination for the subscriber line are guidable to a correct telephone company for billing.

34. The identity verification method of claim 1, further comprising interrogating a customer account record exchange (CARE) database.

35. The identity verification method of claim 34, further comprising receiving, from the CARE database, a billing name and address (BNA) associated with the subscriber line.

36. The identity verification method of claim 1, further comprising interrogating an ANI watch database to determine whether an account associated with the subscriber line has been previously adjusted.

37. The identity verification method of claim 36, wherein the interrogating of the ANI watch database comprises ascertaining ANI watch database a request has been made by the subscriber for financial credit.

38. The identity verification method of claim 36, wherein the interrogating of the ANI watch database comprises obtaining data associated with a written-off amount for charges that were billed to an account associated with the subscriber line.

39. The identity verification method of claim 1, further comprising determining whether the subscriber line is associated with a business line indicator.

40. The identity verification method of claim 1, further comprising determining whether the subscriber line has been in service for less than a predetermined amount of time.

41. The identity verification method of claim 1, wherein the method is performed in real-time.

42. The identity verification method of claim 1, further comprising:

receiving a monetary amount from a merchant of a sales transaction between the merchant and the subscriber; and

electronically billing the amount to an account associated with the subscriber line.

43. An identity verification method, the method comprising:

obtaining automatic number identification (ANI) data or billing telephone number (BTN) data associated with a subscriber line of a telecommunications network;

obtaining identification data associated with a subscriber, where said identification data is different from the ANI data or the BTN data;

requesting a search of a first database using the ANI data or the BTN data to determine first reference subscriber data;

requesting a search of a second database using the identification data and the first reference subscriber data to determine second reference subscriber data;

comparing the first reference subscriber data to the second reference subscriber data; and

verifying an identity of a subscriber based on the second subscriber data corresponding to the first reference subscriber data.

44. The identity verification method of claim 43, wherein the obtaining of the ANI data or the BTN data and of the identification data comprises obtaining the ANI data or the BTN data and the identification data from a merchant, the merchant being in a process of selling goods or services to the subscriber.

45. The identity verification method of claim 43, wherein the identification data is a ZIP code and the second database is a ZIP data source.

46. The identity verification method of claim 43, wherein the identification data is address data and the second database is an address data source.

47. The identity verification method of claim 43, wherein the second database is distinct from the first database.

48. The identity verification method of claim 43, wherein the second reference subscriber data comprises an address of the subscriber.

49. The identity verification method of claim 43, wherein the verifying of the identity of the subscriber comprises verifying whether the first reference subscriber data corresponds to the second reference subscriber data within a predetermined range.

50. The identity verification method of claim 43, further comprising providing a verification status notification to a merchant.

51. The identity verification method of claim 43, wherein the searching of the first database further comprises using the ANI data to determine the BTN data.

52. The identity verification method of claim 43, further comprising:

receiving a transaction amount to be charged to an account associated with the subscriber line; and

in response to the verifying of the identity of the subscriber, approving a transaction associated with the transaction amount.

53. The identity verification method of claim 43, further comprising, prior to the searching, ascertaining whether the BTN data or the ANI data corresponds to a billable subscriber line.

54. The identity verification method of claim 53, wherein the ascertaining comprises:

determining whether an area code associated with the subscriber line has changed; and

determining whether the ANI data or the BTN data are missing from a record.

55. The identity verification method of claim 53, wherein the ascertaining comprises:

interrogating a network database with the ANI data to determine whether the subscriber line is a billable subscriber line; and

if the subscriber line is a billable subscriber line, selectively generating an approved status.

56. The identity verification method of claim 53, wherein the ascertaining comprises searching a threshold database to determine whether an account associated with the subscriber line has reached a maximum monetary amount.

57. The identity verification method of claim 53, wherein the ascertaining comprises searching an off network (OFFNET) database to determine whether an industry standard Numbering Plan Area (NPA), an NXX, or an operating company number (OCN) of the subscriber line is present in the OFFNET database.

58. The identity verification method of claim 53, wherein the ascertaining comprises searching an on network (ONNET) database to determine whether an industry standard Numbering Plan Area (NPA), an NXX, or an operating company number (OCN) of the subscriber line is present in the ONNET database.

59. The identity verification method of claim 53, wherein the ascertaining comprises searching a competitive local exchange carrier (CLEC) database to determine whether the ANI data or the BTN data is known to have ported to the CLEC.

60. The identity verification method of claim 53, wherein the ascertaining comprises searching a 42 BLOCK database to determine whether a billing block has been imposed on the subscriber line.

61. The identity verification method of claim 53, wherein the ascertaining comprises searching a block and cancel database to determine whether a request has been made to prevent further transactions from being billed to an account associated with the subscriber line.

62. The identity verification method of claim 53, wherein the ascertaining comprises searching an unbilled database to determine if there is a history of unbillable bills associated with the subscriber line.

63. The identity verification method of claim 53, wherein the ascertaining comprises searching an unpaid bills database to determine if there is a history of unpaid bills associated with the subscriber line.

64. The identity verification method of claim 43, further comprising, in response to determining the first reference subscriber data, using the first reference subscriber data to search a regional account office (RAO) database to determine whether the RAO database is billable.

65. The identity verification method of claim 43, further comprising, in response to determining the first reference subscriber data, receiving an operating company number (OCN) from the first database, and determining if the OCN corresponds to a known competitive local exchange carrier (CLEC) and whether the OCN corresponds to an off network (OFFNET) CLEC.

66. The identity verification method of claim 43, further comprising, in response to determining the first reference subscriber data, using the first reference subscriber data to determine whether a new Numbering Plan Area (NPA)/NXX, and an operating company number (OCN) combination for the subscriber line are guidable to a correct telephone company for billing.

67. The identity verification method of claim 43, further comprising interrogating a customer account record exchange (CARE) database.

68. The identity verification method of claim 67, further comprising receiving, from the CARE database, a billing name and address (BNA) associated with the subscriber line.

69. The identity verification method of claim 43, further comprising interrogating an ANI watch database to determine whether an account associated with the subscriber line has been previously adjusted.

70. The identity verification method of claim 69, wherein the interrogating comprises ascertaining whether previous requests have been made by the subscriber for financial credit.

71. The identity verification method of claim 69, wherein the interrogating comprises obtaining data associated with written-off amounts for charges that were billed to an account associated with the subscriber line.

72. The identity verification method of claim 43, further comprising determining whether the subscriber line is associated with a business line indicator.

73. The identity verification method of claim 43, further comprising determining whether the subscriber line has been in service for less than a predetermined amount of time.

74. The identity verification method of claim 43, wherein the method is performed in real-time.

75. The identity verification method of claim 43, further comprising:

receiving a monetary amount from a merchant, the merchant being associated with a sales transaction between the merchant and the subscriber; and

electronically billing the monetary amount to an account associated with the subscriber line.

76. An identity verification method, comprising:

obtaining, from a merchant, first identification data and second identification data, the first identification data and the second identification data being associated with a subscriber;

transmitting a first request for a search of a first database using the first identification data;

receiving first reference subscriber data in response to the first request;

transmitting a second request for a search of a second database using the first reference subscriber data and the second identification data;

receiving second reference subscriber data in response to the second request;

comparing the first reference subscriber data to the second reference subscriber data; and

verifying an identity of the subscriber based on the first reference subscriber data corresponding to the second subscriber data.

77. The identity verification method of claim 76, wherein the first identification data is a billing telephone number (BTN) associated with a subscriber line of a telecommunications network.

78. The identity verification method of claim 76, wherein the second identification data is a ZIP code or address data associated with the subscriber.

79. The identity verification method of claim 76, wherein the second database is distinct from the first database.

80. The identity verification method of claim 76, wherein the second reference subscriber data comprises an address of the subscriber.

81. The identity verification method of claim 76, wherein the verifying of the identity of the subscriber comprises determining whether the first reference subscriber data corresponds to the second reference subscriber data within a predetermined range.

82. The identity verification method of claim 76, further comprising providing a verification status notification to the merchant.

83. The identity verification method of claim 76, further comprising, prior to the searching, determining whether an area code associated with data subscriber line has changed and determining whether a billing telephone number (BTN) associated with a subscriber line of a telecommunications network is missing from a record.

84. The identity verification method of claim 76, further comprising:

prior to the searching, interrogating a network database with a billing telephone number (BTN) associated with a subscriber line of a telecommunications network to determine whether the subscriber line is a billable subscriber line; and

if the subscriber line is a billable subscriber line, selectively generating an approved status.

85. The identity verification method of claim 76, further comprising, prior to the searching, interrogating a threshold database to determine whether an account associated with a subscriber line has reached a maximum monetary amount that may be charged to an account associated with the subscriber line.

86. The identity verification method of claim 76, further comprising, prior to the searching, interrogating an off network (OFFNET) database to determine whether an industry standard Numbering Plan Area (NPA), an NXX, or an operating company number (OCN) of a subscriber line is present in the OFFNET database.

87. The identity verification method of claim 76, further comprising, prior to the searching, interrogating an on network (ONNET) database to determine whether an industry standard Numbering Plan Area (NPA), an NXX, or an operating company number (OCN) of a subscriber line is present in the ONNET database.

88. The identity verification method of claim 76, further comprising, prior to the searching, interrogating a competitive local exchange carrier (CLEC) database to determine whether a billing telephone number (BTN) associated with a subscriber line of a telecommunications network is known to have ported to the CLEC.

89. The identity verification method of claim 76, further comprising, prior to the searching, interrogating a 42 BLOCK database to determine whether a billing block has been imposed on a subscriber line associated with the subscriber.

90. The identity verification method of claim 76, further comprising, prior to the searching, interrogating a block and cancel database to determine whether a request has been made to prevent further transactions from being billed to an account associated with a subscriber line associated with the subscriber.

91. The identity verification method of claim 76, further comprising, prior to the searching, interrogating an unbilled database to determine whether there is a history of unbillable bills associated with a subscriber line associated with the subscriber.

92. The identity verification method of claim 76, further comprising, prior to the searching, interrogating an unpaid bills database to determine whether there is a history of unpaid bills associated with a subscriber line associated with the subscriber.

93. The identity verification method of claim 76, further comprising using the first reference subscriber data to search a regional account office (RAO) database to determine if the RAO database is billable.

94. The identity verification method of claim 76, further comprising, after determining the first reference subscriber data, receiving an operating company number (OCN) from the first database, and determining whether the OCN corresponds to a known competitive local exchange carrier (CLEC) or whether the OCN corresponds to an off network (OFFNET) CLEC.

95. The identity verification method of claim 76, further comprising using the first reference subscriber data to determine whether a new Numbering Plan Area (NPA)/NXX, and an operating company number (OCN) combination for a subscriber line associated with the subscriber are guidable to a correct telephone company for billing.

96. The identity verification method of claim 76, further comprising interrogating a customer account record exchange (CARE) database.

97. The identity verification method of claim 76, further comprising determining whether a subscriber line associated with the subscriber is associated with a business line indicator.

98. The identity verification method of claim 76, further comprising determining whether a subscriber line associated with the subscriber has been in service for less than a predetermined amount of time.

99. The identity verification method of claim 76, wherein the method is performed in real-time.

100. The identity verification method of claim 76, further comprising:

receiving a monetary amount from a merchant, the merchant being associated with a sales transaction between the merchant and the subscriber;

and electronically billing the monetary amount to an account associated with a subscriber line associated with the subscriber.

101. A non-transitory machine-readable medium for storing a set of instructions that, when executed by a machine, cause the machine to:

obtain automatic number identification (ANI) data or billing telephone number (BTN) data associated with a subscriber line of a telecommunications network;

obtain identification data associated with a subscriber, said identification data being different from the ANI data or the BTN data;

request a search of a first database using the ANI data or the BTN data to determine first reference subscriber data;

request a search of a second database using the identification data and the first reference subscriber data to determine second reference subscriber data;

compare the first reference subscriber data to the second reference subscriber data; and

verify an identity of the subscriber based on the comparison.

102. An identity verification system comprising:

a network interface device to receive;

automatic number identification (ANI) data or billing telephone number (BTN) data associated with a subscriber line of a telecommunications network, and

identification data associated with a subscriber, said identification data being different from the ANI data or the BTN data;

a processor to execute instructions stored in memory, the instructions comprising;

requesting a search of a first database using the ANI data or the BTN data to determine first reference subscriber data,

requesting a search of a second database using the identification data and the first reference subscriber data to determine second reference subscriber data,

comparing the first reference subscriber data to the second reference subscriber data, and

verifying an identity of the subscriber based on the comparison.

103. The identity verification system of claim 102, wherein network interface device is to receive the ANI data, the BTN data, and the identification data from a remotely located merchant.

104. The identity verification system of claim 102, wherein the first database and the second database are remotely located from the network interface device and the processor.

105. The identity verification system of claim 102, wherein the processor is to execute the instructions stored in memory in real-time.

106. The identity verification system of claim 102, wherein the processor is to execute instructions to search one or more remote databases selected from the group consisting of a competitive local exchange carrier (CLEC) database, a 42 BLOCK database, a Block and Cancel database, an unpaid bills database, an off network database, an on network database, an address verification database, a regional account office (RAO) database, an operating company number (OCN) database, a customer account record exchange (CARE) database.

107. A method to determine billability of a subscriber line, the method comprising:

obtaining automatic number identification (ANI) data or billing telephone number (BTN) data associated with the subscriber line;

using the ANI data or the BTN data to determine whether the subscriber line is billable by performing one or more searches selected from a group consisting of;

searching a threshold database to determine whether an account associated with the subscriber line has reached a maximum monetary amount that may be charged to the account;

searching an off network (OFFNET) database to determine whether an industry standard Numbering Plan Area (NPA), an NXX, or an operating company number (OCN) of the subscriber line is present in the OFFNET database;

searching an on network (ONNET) database to determine whether an industry standard Numbering Plan Area (NPA), an NXX, or an operating company number (OCN) of the subscriber line is present in the ONNET database;

searching a competitive local exchange carrier (CLEC) database to determine whether the ANI data or the BTN data are known to have ported to a CLEC;

searching a 42 BLOCK database to determine whether a billing block has been imposed on the subscriber line;

searching a block and cancel database to determine whether a request has been made to prevent further transactions from being billed to an account associated with the subscriber line;

searching an unbilled database or an unpaid bills database to determine whether there is a history of unpaid bills or unbillable bills associated with the subscriber line; and

notifying the merchant if the subscriber line is not billable.

108. The method of claim 107, further comprising:

obtaining, from the merchant, identification data associated with the subscriber, said identification data being different from the ANI data or the BTN data;

if the subscriber line is billable;

searching a first database using the ANI data or the BTN data to determine first reference subscriber data;

searching a second database using the identification data to determine second reference subscriber data;

determining whether the first reference subscriber data corresponds to the second reference subscriber data; and

notifying the merchant that the identity of the subscriber has been verified, if the first reference subscriber data corresponds to the second reference subscriber data.

109. A system comprising:

a network interface device to obtain from a merchant automatic number identification (ANI) data or billing telephone number (BTN) data associated with a subscriber line of a telecommunications network;

a processor configured to execute instructions stored in memory, the instructions comprising;

using the ANI data or the BTN data to determine whether the subscriber line is billable by performing one or more searches selected from a group consisting of;

searching a threshold database to determine whether an account associated with the subscriber line has reached a maximum monetary amount that may be charged to the account;

searching an off network (OFFNET) database to determine whether an industry standard Numbering Plan Area (NPA), an NXX, or an operating company number (OCN) of the subscriber line is present in the OFFNET database;

searching an on network (ONNET) database to determine whether an industry standard Numbering Plan Area (NPA), an NXX, or an operating company number (OCN) of the subscriber line is present in the ONNET database;

searching a competitive local exchange carrier (CLEC) database to determine whether the ANI data or the BTN data is known to have ported to a CLEC;

searching a 42 BLOCK database to determine whether a billing block has been imposed on the subscriber line;

searching a block and cancel database to determine whether a request has been made to prevent further transactions from being billed to an account associated with the subscriber line;

searching an unbilled database or an unpaid bills database to determine whether there is a history of unpaid bills or unbillable bills associated with the subscriber line; and

notifying the merchant via the network interface device if the subscriber line is not billable.