Subscribers of local telephone services often sign up for telephone services that are billed out on a monthly basis. Occasionally, some subscribers who are financially capable of paying their bills have difficulty making timely payments for their local telephone services. These late payments result in late payment penalties for the subscriber and added costs to the telephone service provider. In extreme cases the subscriber's delinquency can adversely affect her credit rating. In an attempt to solve this problem, several types of prepaid telephone services are available that allow for a subscriber to prepay for services.
One existing type of system treats prepaid local telephone services (hereinafter “prepaid dialtone”) in the same manner as a conventional long distance prepaid card service. The local exchange carrier (LEC) and/or interexchange carrier (IXC) for a particular subscriber will forward all calls to a dedicated prepaid dialtone switch that will determine if the caller has a credit balance in her account. If the prepaid dialtone switch determines that the call can go through, it then routes the call to the local end office and maintains an active connection to the call so that the prepaid dialtone switch may monitor the call and update its database after the call. A disadvantage of this form of prepaid dialtone is that the telephone network needs to maintain a continuous connection to the database monitoring the prepaid subscriber so that the time of the call is monitored and the charges will be debited on, for instance, a per second basis.
Another version of a prepaid dialtone system utilizes a separate billing service that generates monthly statements and posts deposits received. This system acts to accept prepayment of services but does not adequately address the problem of late payments because there is no mechanism for automatically limiting a subscriber's usage or automatically shutting off the subscriber's service at the end of the prepaid service period.
Accordingly, there is a need for an improved system and method of implementing prepaid dialtone services.
The present invention provides for an efficient and configurable system and method for implementing and monitoring prepaid dialtone services that avoids the billing difficulties and telephone network resource usage of existing versions of prepaid dialtone services.
The service center 14 includes at least one customer service agent 20 for receiving initial prepaid dialtone service requests and general customer service questions. Each customer service agent 20 receives a call from a subscriber after the subscriber has been screened by the VRU 18 to determine the subscriber's needs. Alternatively, the subscriber may access the customer service center without going through the VRU. The service center is in communication with an application server 22, such as those commonly available from IBM Corporation, containing a prepaid dialtone database 24, a processor 26 and a memory 28. Preferably the processor 26 of the applications server 22 monitors the status of the various subscriber records and manages communications with the telephone network 16 and other resources. In one embodiment, the customer service center 14, VRU 18 and application server 22 may communicate through a hub 29. A provisioning network 31 receives account activation and subsequent account status information generated by the customer service center 14 or applications server 22, via hub 19, when a prepaid dialtone subscriber establishes an account or when the account status changes. The provisioning information generated by the customer service center 14 or application server 22 may reach the LEC 17 for the subscriber through any of a number of provisioning channels that the particular LEC already uses when provisioning services.
As shown in
The account status field 42 reflects whether a prepaid dialtone subscriber account is active or on hold. The service plan field 36 of the subscriber record 30 contains a product code representative of the specific version of prepaid dialtone service applicable to the subscriber. The service dates field 40 stores the start and end dates of the present period for which the prepaid dialtone service is active.
As shown in
The SSP 44 is a programmable switch having the ability to recognize AIN triggers for calls requiring special services. The SSP 44 may be an end office or tandem switch and communicates with a SCP 46. The subscriber telephone 12 communicates with the SSP 44 over a voice/information channel such as an ordinary telephone line. Multiple connections and combinations of network elements are usable with the present invention. For example, a subscriber on a subscriber telephone 12 may also communicate with a SSP 44 through one or more ordinary switches. In one preferred embodiment, the SSP is configured to receive and store line class codes from the LEC provisioning system 31 (
The service control point (SCP) 46 is a network element containing logic and data necessary to provide functionality required for the execution of a desired communication service. A SCP 46 generally permits separation of service logic from switching functionality such that additional services may be developed without the need to provision significant software in each individual SSP. A suitable SCP 46 is the Advantage SCP manufactured by Lucent Technologies. In a preferred embodiment, the SCP 46 contains service logic for prepaid dialtone services and is also configured to receive a set of records of subscriber names, their telephone numbers and the service time limit at provisioning. This subscriber information originates in the service center 14 and the records are stored in the application server 22 and the memory 50 in the SCP 46. The memory 50 may be integral with the SCP or may be a separate memory device accessible by the SCP 46.
The SCP 46 communicates with SSPs 44 over a data channel via at least one service transfer point (STP) 48. A suitable data signal intended for use with the STPs is the American National Standards Institute (ANSI) signalling system No. 7 (SS7). A suitable SCP/SSP communication protocol is the AIN 0.1 SCP/SSP protocol set forth in Bellcore Technical Reference TR-NWT-001285, entitled AIN Switch-Service Control Point Application Protocol Interface Generic Requirements, Issue 1, August 1992. Other configurations of AIN capable networks may be used to implement a preferred method and system for providing prepaid dialtone services. Additionally, multiple service provider networks, also referred to herein as local exchange carriers (LECs) 17, may access the services of the prepaid dialtone provisioning system 10 so that the prepaid dialtone provisioning system will monitor and maintain all subscriber account records for each of the LECs 17.
In one embodiment, the SSP 44 may be configured to recognize an off-hook delay trigger from a subscriber line when a subscriber picks up the telephone and dials a number. If the subscriber is a prepaid dialtone subscriber, the SSP preferably contains a line class code associated with the subscriber's telephone number. The line class code for prepaid dialtone subscribers contains instructions for the SSP to verify that the telephone number dialed by the subscriber is a non-toll intra-LATA (Local Access and Transport Area), toll-free, or 911 call. If the SSP determines that the number does not fall within the allowable category of calls, the call is not connected. Instead, the off-hook delay trigger is escaped and the call is terminated to treatment in the SSP. If the call made by the prepaid dialtone subscriber is an allowable call, the SSP communicates with the SCP and the SCP verifies that the prepaid dialtone account for the subscriber is valid. If the account is still valid, the SCP instructs the SSP to connect the call.
Referring now to
To initiate service after purchasing a card 11, the subscriber 12 will call into the service center 14 to initiate service. In one embodiment, all calls to the service center first arrive at a VRU that screens the call and offers a menu of touchtone response options to direct the call to an appropriate location. In other embodiments, calls to the service center may arrive directly at the service center 14. The service center 14 may be a live operator who, in real time, assists the caller. In another embodiment, the service center may be an Internet-based service center capable of accepting and processing service requests. The subscriber 12 will provide the customer service agent 20 with information such as the address for the service and the VIN number 13 of the card 11. After verifying the address information and verifying that the VIN number 13 is valid, the customer service agent 20 will provide the subscriber with a telephone number and installation date for the service.
The customer service agent will communicate with the applications server 22 to initiate a service order that may be processed through a standard automated provisioning system in communication with the LEC 17 for the subscriber 12. Preferably the interface used for provisioning the prepaid dialtone service is an interface such as a standard electronic data interface (EDI) or other type of interface which is capable of connecting to customized interfaces used by the specific LECs of the subscribers to the prepaid dialtone service. After receiving a new prepaid dialtone service request, the service order is entered on the prepaid dialtone database and a provisioning request will be sent to provisioning system 31 and, in a preferred embodiment, results in all the necessary Universal Service Order Codes (USOCs), line class code orders, and field identifiers (FIDs) for the requested version of prepaid dialtone being delivered to the LEC. The USOC is preferably a package USOC that defines a set of individual feature USOCs (e.g., call waiting, voicemail, etc.). Thus, the package USOC represents to the LEC the general type of service order and all the individual features packaged into the service order. In another embodiment, individual feature USOCs may be used in an unbundled form to provide the service order. Line class codes refer to a switch based translator for a particular service that decides which call features are allowed and FIDs refer to codes in a service order that are related to particular services or features.
In a preferred embodiment, the LEC 17 may implement the prepaid dialtone service in one of two ways depending on the state rules for handling local telephone calls. In states such as Ohio and Indiana where there is no metered service for local calls, the LEC may implement the prepaid dialtone service for a particular subscriber by storing a line class code associated with the subscriber and the prepaid dialtone service in the SSP. In a preferred embodiment, the SCP does not interact with the SSP and the SSP handles all prepaid dialtone calls. In another embodiment, the LEC of states with no metered service for local calls may provide the appropriate SCP with the subscriber's telephone number and an account status indicator (e.g., a variable indicating whether the subscriber account is current or expired) to a memory 50 (see
In states where the local telephone services are metered, for example in Illinois, Wisconsin or Michigan, the LEC 17 will again preferably provide the SSP with a line class code associated with the subscriber's telephone number that will cause the SSP to permit local calls. In metered states, however, the prepaid telephone services are implemented in the SCP by providing the SCP 46 with the subscriber's telephone number, a day counter and a call counter to provide a fixed number of local telephone calls to a subscriber for a given service period. The number of calls allowed may be set at a number greater than the average number of calls subscribers make in a given time period to allow for normal calling habits. For example, assuming that 270 calls per month is the average number of calls, the SCP may be programmed to allow 400 calls in a thirty day period for prepaid dialtone subscribers. As with LECs in the non-metered states, the SCP and SSP do not continuously monitor prepaid telephone calls, do not associate a value/rate with a call or debit a value from an account, and do not limit the length of local telephone calls. In the metered call states, however, the SCP will keep track of a set service period, decrement a call counter every time a local call is completed, and prohibit all calls after a predetermined number of calls have been completed in the service period.
In either situation, metered state or non-metered state, the SCP preferably does not communicate with the prepaid database. As shown in
After determining the service period, the applications server 22 monitors the subscriber service periods by scanning the prepaid dialtone database 24 on a daily basis (at 74). At a desired time before the expiration of a subscriber's service period, the applications server will send instructions to a notification service to automatically notify the subscriber that the service period will expire in a certain number of days (at 76). In one embodiment, the automatic notification may be in the form of a voice mail that supplies termination date information and is automatically generated and delivered five days before the service period expires. In another embodiment, the notification service may be an automatic calling device that will telephone the subscriber and play a prerecorded reminder message. In other embodiments, an additional renewal reminder message may be provided, other reminder periods may be implemented or the subscriber may be given the option of selecting how far in advance she wishes to be reminded to renew and/or informed of a service termination date.
After notifying the subscriber, the applications server continues to keep track of subscriber account status and check on whether the subscriber has renewed (at 78). If the subscriber has renewed, the process begins again with the applications server calculating the new service period and so on. If the service period expires and the subscriber has not renewed in time, the applications server generates an instruction directed to the subscriber's LEC 17 to change the subscriber account status (at 80). In a preferred embodiment, the applications server allows the subscriber a grace period in which to renew her account by instructing the LEC to put the account on hold, such as a vacation-type hold or other suspend/hold-type account, for example where no dialtone service is provided but where the telephone line is still connected. In this manner, the prepaid dialtone subscriber is given a period of time to renew the account without the account being terminated and the subscriber having to pay a fee for reconnecting the telephone service and receiving a new telephone number in addition to renewing the prepaid dialtone service. In another embodiment, the prepaid dialtone service may allow for emergency calls, such as a 911 call, during the grace period while blocking all other call attempts.
The applications server will continue to monitor the subscriber's account on a daily basis during a predetermined grace period to see if a renewal has been received (at 82). The grace period may be any desired length of time and in a preferred embodiment is five days. At the end of the grace period, the applications server will automatically send instructions to the LEC to terminate and disconnect the subscriber's telephone service (at 84). In other embodiments, the applications server may just automatically send a termination order to the LEC at the end of the subscriber's service period so that the prepaid telephone service and the telephone line are terminated immediately after the service period expiration date.
Referring now to
When the VRU receives the subscriber's menu selection, the VRU will then request information from the subscriber including the VIN number of the prepaid dialtone card that the subscriber purchased (at 96). In one embodiment, the VRU 18 will determine if the caller is calling from her home and match the automatic number identification (ANI) information of the home number to an established prepaid dialtone account. The VRU 18, via the applications server 14, will verify with the prepaid dialtone card database that the VIN is valid and that the monetary value represented by the card is sufficient for the services requested. The applications server will renew the subscriber's account for another service period once the VIN and amount are verified (at 98). The VRU may also inform the subscriber of the new end date of the prepaid dialtone service she has just purchased.
In another embodiment, subscribers may pay for prepaid telephone service using a credit card rather than a single use prepaid dialtone card purchased at a retailer. In this embodiment, the VRU would ask the subscriber to select between a prepaid card or a credit card as a method of payment, and the applications server would interact with the appropriate credit agency to determine if the credit card transaction is valid.
An advantage of the presently preferred system and method is that use of LEC resources is minimized. The LEC is not required to constantly monitor prepaid telephone calls and does not keep track of monetary values associated with subscriber accounts. Communication with the service center 14 is minimal and does not tie up LEC resources. In one embodiment, the LEC will maintain a call counter and a service period clock for prepaid dialtone subscribers in metered states. In non-metered states, no call counter or service period clock is necessary. Preferably, the service center, via a provisioning network, only communicates with an LEC to initially establish prepaid dialtone services or to change the status of an account if a subscriber fails to renew or renews late.
Unless the service center communicates information to the contrary, the LECs will automatically maintain active status for currently active prepaid dialtone subscribers. In metered states, the LEC will automatically reset the service period and call counter stored in memory 50 in the SCP 46 at the end of a given subscriber's service period. In non-metered states, the LEC will maintain active status for the prepaid subscribers unless a special instruction (such as a hold or a disconnect instruction) is received. In this manner, LEC resources are not burdened by the bulk of the administrative overhead of managing the prepaid subscribers. Instead, the subscriber accounts and account maintenance are handles by the remotely located service center 14.
In a preferred embodiment, different types of prepaid dialtone services may offered using the disclosed system and method. For example, in embodiment subscribers may be able to select a basic or a premium service for prepaid dialtone. Both basic and premium services could be based on a 30-day service period. The basic service features may include basic dialtone, a state-specific local calling plan, a directory listing, toll call blocking, PIC none (designating a feature that blocks a subscriber from utilizing long distance services), directory assistance (DA) and directory assistance with call completion (DACC) blocking, operator call (0+/0−) blocking except in areas without 911, listing services, and no customer billing. The state-specific local calling plans may be as follows based on state/regional call metering regulations: Indiana and Ohio—unlimited local calling; Illinois (bands A & B calling permitted, band C blocked), Michigan, and Wisconsin—a preset limit on the number of local telephone calls allowed per service period. The basic prepaid dialtone service preferably has its own USOC, line class codes and FIDs and these would be invoked by the service instructions sent out to the LEC by the applications server. The premium service may include all the features of the basic service and the following features: voice mail, caller ID with name, call waiting, and non-published listing. As with the basic service, the premium service preferably has its own packaged USOC defining all the aspects of the service to the LEC supporting the subscriber.
In addition to the basic sign-up and renewal functions described above, the service center, via the VRU may allow subscribers who have existing prepaid dialtone service to retrieve account information on an as-needed basis. Utilizing the same telephone number that allows for the subscriber to sign-up for and renew service, preferably a toll-free number, a subscriber may access information offered by menu driven commands at the VRU. Such information may include the type of prepaid service the subscriber has established, the date the prepaid service will expire, etc. The VRU 18 preferably also allows subscribers to select an option to be connected to a customer service agent 20.
As has been described above, by using a remotely located prepaid dialtone service center and an automated application server that tracks service periods and provides electronic provisioning instructions, and by providing local calls limited by service period and not a per-call time charge, LEC resources are not burdened by the continuous monitoring and administrative tasks of previous systems. Additionally, the customer service center and application server provide prepaid dialtone plan flexibility and avoids the need to replicate efforts and specially program hardware at each and every LEC interested in offering the prepaid dialtone service described above. The preferred method can permit automated sign-up and renewal of prepaid dialtone services. The prepaid dialtone services provide subscribers with the ability to manage their telephone costs and allow LECs to reduce the billing difficulties associated with subscribers.
It is intended that the foregoing detailed description be regarded as illustrative rather than limiting, and that it be understood that the following claims, including all equivalents, are intended to define the scope of this invention.
Number | Name | Date | Kind |
---|---|---|---|
2298487 | Kiner | Oct 1942 | A |
2615972 | Hubbard | Oct 1952 | A |
3022381 | Pferd | Feb 1962 | A |
3087018 | Pferd | Apr 1963 | A |
3169168 | Capranica | Feb 1965 | A |
3571799 | Coker, Jr. et al. | Mar 1971 | A |
3594727 | Braun | Jul 1971 | A |
3662111 | Rubinstein | May 1972 | A |
3665397 | DiNapoli et al. | May 1972 | A |
3702392 | St. Jean | Nov 1972 | A |
3723655 | Zucker et al. | Mar 1973 | A |
3728522 | Norwich | Apr 1973 | A |
3752904 | Waterbury | Aug 1973 | A |
3769463 | Graham et al. | Oct 1973 | A |
3784793 | Ito et al. | Jan 1974 | A |
3787623 | Stephenson, Jr. | Jan 1974 | A |
3929278 | Balavoine et al. | Dec 1975 | A |
3937925 | Boothroyd | Feb 1976 | A |
3959607 | Vargo | May 1976 | A |
3982103 | Goldman | Sep 1976 | A |
4023014 | Goldberg | May 1977 | A |
4048475 | Yoshida | Sep 1977 | A |
4068213 | Nakamura et al. | Jan 1978 | A |
4197986 | Nagata | Apr 1980 | A |
4326123 | Hosterman | Apr 1982 | A |
4371751 | Hilligoss, Jr. et al. | Feb 1983 | A |
4404433 | Wheeler et al. | Sep 1983 | A |
4417100 | Carlson et al. | Nov 1983 | A |
4439636 | Newkirk et al. | Mar 1984 | A |
4492820 | Kennard et al. | Jan 1985 | A |
4510350 | Wagner et al. | Apr 1985 | A |
4517412 | Newkirk et al. | May 1985 | A |
4518824 | Mondardini | May 1985 | A |
4525601 | Bartnich et al. | Jun 1985 | A |
4577066 | Bimonte et al. | Mar 1986 | A |
4585904 | Mincone et al. | Apr 1986 | A |
4587379 | Masuda | May 1986 | A |
RE32263 | Kaminsky | Oct 1986 | E |
4706275 | Kamil | Nov 1987 | A |
4717815 | Tomer | Jan 1988 | A |
4743892 | Zayle | May 1988 | A |
4756020 | Fodale | Jul 1988 | A |
4776000 | Parienti | Oct 1988 | A |
4777646 | Harris | Oct 1988 | A |
4799255 | Billinger et al. | Jan 1989 | A |
4853952 | Jachmann et al. | Aug 1989 | A |
4860346 | Mellon | Aug 1989 | A |
4866761 | Thornborough et al. | Sep 1989 | A |
4877947 | Mori | Oct 1989 | A |
4879744 | Tasaki et al. | Nov 1989 | A |
4897870 | Golden | Jan 1990 | A |
4935956 | Hellwarth et al. | Jun 1990 | A |
4964156 | Blair | Oct 1990 | A |
4975942 | Zebryk | Dec 1990 | A |
5003584 | Benyacar et al. | Mar 1991 | A |
5003585 | Richer | Mar 1991 | A |
5023868 | Davidson et al. | Jun 1991 | A |
5036533 | Carter et al. | Jul 1991 | A |
5068891 | Marshall | Nov 1991 | A |
5077788 | Cook et al. | Dec 1991 | A |
5101098 | Naito | Mar 1992 | A |
5109405 | Morganstein | Apr 1992 | A |
5128979 | Reich et al. | Jul 1992 | A |
5138650 | Stahl et al. | Aug 1992 | A |
5146067 | Sloan et al. | Sep 1992 | A |
5155342 | Urano | Oct 1992 | A |
5161180 | Chavous | Nov 1992 | A |
5163086 | Ahearn et al. | Nov 1992 | A |
5166972 | Smith | Nov 1992 | A |
5192947 | Neustein | Mar 1993 | A |
5193110 | Jones et al. | Mar 1993 | A |
5195126 | Carrier et al. | Mar 1993 | A |
5204894 | Darden | Apr 1993 | A |
5222120 | McLeod et al. | Jun 1993 | A |
5222125 | Creswell et al. | Jun 1993 | A |
5225666 | Amarena et al. | Jul 1993 | A |
5241586 | Wilson et al. | Aug 1993 | A |
5264689 | Maes et al. | Nov 1993 | A |
5266782 | Alanara et al. | Nov 1993 | A |
5309504 | Morganstein | May 1994 | A |
5311572 | Friedes et al. | May 1994 | A |
5315636 | Patel | May 1994 | A |
5327482 | Yamamoto | Jul 1994 | A |
5333173 | Seazholtz et al. | Jul 1994 | A |
5339351 | Hoskinson et al. | Aug 1994 | A |
5359182 | Schilling | Oct 1994 | A |
5375161 | Fuller et al. | Dec 1994 | A |
5409092 | Itako et al. | Apr 1995 | A |
5416833 | Harper et al. | May 1995 | A |
5436957 | McConnell | Jul 1995 | A |
5440621 | Castro | Aug 1995 | A |
5448633 | Jamaleddin et al. | Sep 1995 | A |
5479494 | Clitherow | Dec 1995 | A |
5511114 | Stimson et al. | Apr 1996 | A |
5524145 | Parker | Jun 1996 | A |
5524146 | Morrisey et al. | Jun 1996 | A |
5572579 | Orriss et al. | Nov 1996 | A |
5598460 | Tendler | Jan 1997 | A |
5613006 | Reese | Mar 1997 | A |
5659605 | Voit et al. | Aug 1997 | A |
5666405 | Weber | Sep 1997 | A |
5719926 | Hill | Feb 1998 | A |
5729598 | Kay | Mar 1998 | A |
5761278 | Pickett et al. | Jun 1998 | A |
5762376 | Taskett | Jun 1998 | A |
5774533 | Patel | Jun 1998 | A |
5774535 | Castro | Jun 1998 | A |
5787429 | Nikolin, Jr. | Jul 1998 | A |
5790636 | Marshall | Aug 1998 | A |
5805670 | Pons et al. | Sep 1998 | A |
5844972 | Jagadish et al. | Dec 1998 | A |
5854975 | Fougnies et al. | Dec 1998 | A |
5870459 | Phillips et al. | Feb 1999 | A |
5909485 | Martin et al. | Jun 1999 | A |
5946380 | Cohen et al. | Aug 1999 | A |
5963859 | Keating | Oct 1999 | A |
5970129 | Asfar et al. | Oct 1999 | A |
6201856 | Orwick et al. | Mar 2001 | B1 |
6434227 | Nakamura | Aug 2002 | B1 |
Number | Date | Country |
---|---|---|
WO 9015496 | Dec 1990 | WO |
Number | Date | Country | |
---|---|---|---|
20020061092 A1 | May 2002 | US |