WO2002003336A2

WO2002003336A2 - System and method for automatic billing-system verification

Info

Publication number: WO2002003336A2
Application number: PCT/SE2001/001586
Authority: WO
Inventors: Carignan Hugues
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2000-07-06
Filing date: 2001-07-06
Publication date: 2002-01-10
Also published as: AU2001268013A1; WO2002003336A3

Abstract

A system for and method of verifying the accuracy and integrity of the billing system used to bill subscribers to a radio telecommunications network. A computer (350) operating independently of the billing system (360) is used to generate fictional biographical and credi information for one or more virtual test subscribers (VTSs) (362-366). The information is then added to the network databse (340) as if it were actual subscriber data, and a simulation device (350) operates to act as a VTS by placing and receiving calls and performing other network calling activity. The network billing system (360) records the calling activity of the VTS, enters the records in a log, and prepares a bill for the VTS as it would for any other subscriber. Outside the system, baseline records, logs, and bills are prepared for comparison with the actual records, logs, and bills, and any differences are reported to the network operator.

Description

S YSTEM AND METHOD FOR AUTOMATIC BILLING-SYSTEM VERIFICATION

BACKGROUND OF THE INVENTION Technical Field of the Invention

The present invention relates to telecommunication systems, and more specifically to a system and method of automatic billing verification in a radio telecommunications network. Description of Related Art Radio telecommunications networks, such as cellular phone systems, are experiencing a period of explosive growth. Not only are mobile phones increasing in popularity, but the areas covered by wireless networks are expanding and the services offered through them are multiplying. For example, it is now possible to not only call other mobile and wire-line phone subscribers, but to send data transmissions and alphanumeric pages, and to search the World Wide Web. News services are available to provide up-to the minute stock quotes and sports scores. Even more applications like these are expected to debut in the near future.

Users access these and other wireless communications services by purchasing or leasing a Mobile Station (MS) and subscribing with one of several wireless-network service providers. These providers maintain networks, sometimes referred to as Public

Land Mobile Networks (PLMNs), that are divided into geographic radio coverage areas such as cells or sub-cells. To send transmissions, an MS establishes a radio link to a fixed Radio Base Station (RBS) associated with the particular cell or area in which they are currently located. The RBS in turn connects the MS with a Mobile Switching Center (MSC), where the call is routed through the network toward its destination.

This destination may be another network subscriber, or an entity completely outside of the PLMN, for example a wire-line service subscriber. Calls directed to the MS are similarly routed through the MSC and RBS covering the area where the MS is currently located. Subscribers are billed by their network providers on a periodic basis, often monthly, according to a billing scheme agreed to when service is initiated (and sometimes as changed during the subscription period). There are a wide variety of different billing schemes in use today, including a simple flat-rate charged each billing period, or a flat-rate charged for each minute of connect time. The variations on these basic plans are numerous, however, and many subscribers pay a flat charge for service up to a pre-set maximum usage amount, and are then billed by the minute for any connect time over the maximum. Other subscribers are billed one rate for calls placed during the day and another for calls placed at night. Rates can also vary according to the location from which the call is placed or to which it is directed. Subscribers are often also charged for each optional service or feature that they subscribe to, such as call forwarding, call waiting, calling-line identification, etc. When a subscriber is activated, the rate plan and desired services are provisioned in a subscriber profile that is stored in the subscriber's Home Location Register (HLR) and in a Billing Post- Processing Center (BPPC). A wireless subscriber may make or receive several calls and be billed at a different rate for each of them, depending on the factors enumerated above and on others as well.

Of course, rates varying with the type of call made have long been a mainstay of the wire-line, or Plain-Old Telephone System (POTS), typified (in the United States) by a flat-rate for local calls, a different rate for in-state long-distance, and a third for interstate long-distance. Competition between long-distance carriers has somewhat complicated this scenario, although the fact that subscribers always remain with their local telephone service provider simplifies the billing process. Wire-line calls billable to one subscriber always originate from the same point and are connected through the same local switching office. And typically all similarly-situated subscribers are billed at the same rates (the different long-distance providers often simply send their own bill).

In the wireless environment, on the other hand, customers can change providers almost at will, and vigorous competition between carriers has resulted in numerous and changing rate plans. The billing scheme for one subscriber might be different than that for another who lives in the same neighborhood and works in the same office building. Complicating the billing process even further for wireless-service providers is subscriber mobility. Calls by a single subscriber may be may be placed and received from a wide variety of locations, including some locations that are covered only by another provider's network. The MS location can change, of course, even while calls are in-progress. It follows that maintaining a reliable system for billing network subscribers is of paramount importance. Accurate billing means that customers are charged only for the services they subscribe to and the calls that they make. Continually overcharged customers are likely to not only become irritated with their provider, but to switch to a new one as well. On the other hand, the costs associated with satisfactorily handling a large volume of complaints, perhaps coupled with the revenue lost through any under-billing that occurs, has the potential to dramatically change the profitability of network operations. Ensuring that the wireless network billing system is properly functioning, however, is a challenge in itself. The present-day wireless environment requires constant change, and even small adjustments to system hardware or software can have unpredicted and difficult-to-isolate effects on billing accuracy and integrity.

Currently, most billing-system verification is performed by technicians sent into the field to manually place test calls according to pre-planned scenarios. The results of these calls are recorded manually and then benchmarked manually with corresponding billing records generated by the MSC. This method is costly and time- consuming, and provides little flexibility to change the test scenario until after the fact, when all the disparate data can be accumulated and analyzed, and the test technicians redeployed. Some wire-line networks utilize a tool that generates test wire-line calls in order to generate billing records in the network switches. These records can then be captured and compared with the actual test calls generated by the tool. However, there is no comparable device for wireless calls, and only a limited aspect of the overall billing process is tested. Needed is a way to automatically test the billing system and procedures in a radio telecommunications network from end-to-end. The present invention is directed to just such a system and method. SUMMARY OF THE INVENTION

The present invention is directed to a system and method of automatically testing the accuracy and integrity of the billing system in a wireless telecommunications network, h one aspect, the invention is a method that includes the steps of activating one or more virtual test subscribers (VTSs), and remotely controlling at least one mobile station (MS) or mobile-station simulator to place a sequence of wireless test calls using the ID of the VTS. This is followed by logging the test calls in a central control point (CCP) database, using a Mediation Device (MD) to filter out VTS -related call data records (CDRs) generated by the network mobile switching center (MSC) in response to the test calls, and comparing the logs of the

CCP and the mediation device to discover any discrepancies. The method may also include the step of comparing bills generated in the Billing Post-Processing Center (BPPC) on the one hand, and the predicted billing based on the test-call logs in the CCP database on the other hand, to identify any discrepancies. The method may also test subscriber and service provisioning by providing the VTS profile or profiles to a network activation center for provisioning in the ordinary course of business, and next filtering out the VTS profile from the network home location register (HLR) or BPPC to determine if the input was performed and transmitted correctly. another aspect, the present invention is a system including at least one MS or mobile-station simulator, and a CCP for generating VTS profiles, remotely causing the MS or mobile-station simulator to execute a series of transmissions using the VTS ID, and for logging the results. The system also includes an MD to filter out CDRs relating to the VTS transmissions when the CDRs are sent from a network MSC to a network billing post-processing center. A CCP computer compares the CDRs filtered out by the MD with the results logged by the CCP to discover the discrepancies between the two, if any. The system may further include a MS or mobile-station simulator having a directional antenna that can be rotated to simulate a moving mobile station. BRIEF DESCRIPTION OF THE DRAWINGS

The invention will be better understood and its numerous objects and advantages will become more apparent to those skilled in the art by reference to the following drawings, in conjunction with the accompanying specification, in which: FIG. 1 (prior art) is a functional block diagram of an exemplary existing radio telecommunications network, such as one that may advantageously employ the system and method of the present invention;

FIG. 2 (prior art) is a simplified flow chart illustrating one method by which the radio telecommunications network of FIG. 1 generates subscriber bills; FIG. 3 is a functional block diagram showing the relationship of various components of an embodiment of the system of the present invention as configured for use in verifying the accuracy and integrity of the billing system of a radio telecommunication system such as the network shown in FIG. 1; and

FIG 4 is a flow diagram illustrating a method of automatic billing system verification in a radio telecommunications network in accordance with an embodiment of the present invention.

DETAILED DESCRIPTION OF EMBODIMENTS

In a preferred embodiment, the present invention provides a system for, and method of conducting automatic billing-system verification (ABV) in a wireless radio telecommunications network. Note that as used here, the word 'automatic' means that operation of the system, and execution of the method disclosed herein is most advantageously used in a way that requires a minimum of human intervention. There may be circumstances, however, where greater involvement by a human operator is desirable or even necessary. Regardless, the relative presence or absence of manual operation is not an element of the present invention unless explicitly required as an element of the appended claims.

FIG. 1 is a functional block diagram of an exemplary existing radio telecommunications network 100, such as one that may advantageously employ the ABV system and method of the present invention. The network 100 is divided into a multitude of areas such as cells 1-7, each associated with its own Radio Base Station (RBS) 11-17, respectively. Although seven cells are shown, there are usually dozens in a network, ranging in size from two to twelve miles across. A network may also have numerous smaller sub-cells or larger overlapping cells (not shown), each having their own RBS, in order to more efficiently handle dense or rapidly moving communications traffic. An Activation Center (AC) 10, while not actually part of the network, provisions, or initiates, new subscribers, and is the normal origin of the new information concerning them. A new subscriber may communicate through network 100 as soon as the subscriber is provisioned and the necessary information is entered into the Home Location Register (HLR) 40. An individual subscriber connects to the network 100 using a radio transmitter- receiver called a mobile station (MS), for example cell phone 20. Although cellular telephones are the most common form of MS in use today, other types are already in use and gaining popularity. For example, personal computer (PC) 22 or personal digital assistant (PDA) 24 may also be equipped with circuitry providing the ability to communicate with the wireless network 100. Mobile stations are usually, as the name denotes, mobile, and they make contact with network 100 through an RBS covering the area in which they are currently located. Since more than one RBS is usually within range of a given mobile station at any one time, the one receiving the strongest signal will generally be used for the connection. When an MS relocates during a transmission so that another RBS becomes the most appropriate, the connection will be switched in what is referred to as a 'hand-off . h some instances, hand-offs may add to the billing complexity since an MS may start a call in a cell where a first billing rate is in effect, and then move to another cell where a second (higher or lower) billing rate is in effect during the same call. Errors can occur when the billing system must accurately parse the call and apply the correct billing rate for each portion of the call.

Each RBS is connected to the network through a Mobile Switching Center (MSC). For example, in FIG. 1 base stations 11-13 and 14-17 are connected with MSC 30 or MSC 32, respectively. MSCs 30 and 32 are associated with Visitor Location Registers (VLRs) 31 and 33, respectively. VLRs 31 and 33 are data storage devices where MSCs 30 and 32 can store information relating to the wireless activity in its MSC/VLR service area (delineated by broken lines in FIG. 1). One or more, and usually many MSC/VLR service areas make up the wireless network 100, which is sometimes referred to as a Public Land Mobile Network (PLMN). A wireless service provider may have several PLMNs. Each PLMN has an HLR, such as HLR 40, that communicates with the individual MSCs and maintains information concerning the network itself and its subscribers.

HLR 40, for example, maintains in its database subscriber profiles that contain information (input during provisioning) about each subscriber having the PLMN as its home network. This information will include, for example, the subscriber's mobile- station identification number or code (MSID), the specific services subscribed to, and other subscriber information. The HRL 40 may also maintain a database containing the area or cell in which the subscriber's MS, such as MS 20, is currently located.

The location of MS 20 is determined through a process called registration, where the MS transmits its MSID when it is turned on and periodically thereafter, so as to alert MSCs within range to its presence. Naturally, when the MS moves from place to place, the registration process enables other MSCs to detect its location in their respective MSC/VLR service areas. From time to time, each MSC reports registration information stored in its VLR to HLR 40. The HLR 40 then stores this location information in case it is needed to route a transmission to MS 20. The HLR may also receive and store a record, if applicable, that MS 20 has roamed beyond the

PLMN, and through which other network contact can be made through a Gateway Mobile Switching Center (GMSC) (not shown), assuming that MS 20 has registered its MSID and home PLMN information there.

For example, MSC 32 may receive notice that a transmission to MS 20 is being attempted. If MS 20's current location is not stored in VRL 33 (or if an attempt to contact MS 20 at the stored location has failed), then MSC 32 may send a query to HRL 40 to ascertain the information. If the information is not there, HRL 40 may query other MSCs in the PLMN in an attempt to find it. Eventually, either the correct location information is obtained and the appropriate connection made, or a determination is made that MS 20 cannot currently be found and the attempted transmission is abandoned. Records describing each completed transmission are collected and forwarded by the responsible MSC to a Billing Post-Processing Center (BPPC) 60, as described more fully below.

Unless the subscriber pays only a simple flat-rate for unlimited wireless service, which is most often not the case, the tracking of subscriber activity is very important to ensuring that an accurate bill (invoice) is prepared and sent out. Call activity information is also important for settling accounts between service providers (wireless and otherwise), who often permit access to their network for a fee. FIG. 2 is a simplified flow chart illustrating one existing method by which the radio telecommunications network 100 of FIG. 1 generates bills based on subscriber calling activity. The process begins at step 200, at which point the subscriber to be billed has had their service provisioned in the network. The process continues with step 202 when notice is received that a transmission directed from or to a network-subscriber MS is being attempted. This transmission may be a terminating call to the MS, an outgoing call from the MS, or it may be a page or short message service (SMS) message. As explained above, the MSC or GMSC notified of the attempted transmission will locate the target MS (step 204), and (assuming the target MS can be located) eventually the transmission will be routed through the appropriate MSC (step 206), such as MSC 30 shown in FIG. 1.

When the transmission is completed (step 208), MCS 30 creates a call data record (CDR) containing pertinent information about the call such as its duration, the originating or terminating MSID, and the time the call occurred (step 210). MSC 30 then stores the CDR in a CDR log (step 212). From time to time, MSC 30 sends the accumulated CDRs to BPPC 60 (step 214) and later deletes them from the CDR log (step not shown). Each billing cycle (or more often, if desired), BPPC 60 collates by MSID (or other subscriber identification number) all of the CDRs it receives from the

MSCs in the PLMN (step 216). Subscriber billing-profile information, previously sent from the AC 10 to the BPPC 60 is then applied to the CDRs (step 218) to determine the appropriate charge for the call. A bill or invoice is then created and sent to the subscriber (step 220). FIG. 3 is a functional block diagram showing the relationship of various components of an embodiment of the system of the present invention as configured for use in verifying the accuracy and integrity of the billing system of a radio telecommunication system such as network 100 shown in FIG. 1. To direct the automatic verification process, a Central Control Point (CCP) 350 is placed into communication with the network (although it is not actually part of the network itself), as shown in FIG. 3. The connections shown may be direct or indirect, depending on the particular application and the scope of the testing protocol to be implemented. The CCP 350 is typically a computer having an associated data storage device. The CCP can comprise either a single computer or several computing devices working in concert. The CCP 350 may also be configured from existing network components, which would continue to perform their network functions.

In one embodiment, CCP 350 generates one or more test subscriber profiles and the sequence or pattern of calls to be placed by the test MSs 362, 364, and 366, during the testing process. The sequence is generated based on a set of preprogramed criteria ranging from random selection to complex rules designed to effect a test of specific services, billing rates, or types of subscribers. In another embodiment, the test sequence and subscribe profiles are manually formulated and input to the CCP.

Test MSs 362, 364, and 366 are mobile stations that can be strategically placed in various locations throughout the PLMN for executing the test sequence. Although three MSs are shown, there could be a much larger number. These test MSs are preferably remote-controlled, and can perform the functions of any kind of MS normally utilized in the network. Test MSs 362, 364, and 366 are placed in communication with CCP 350, which can remotely control the MSs and direct them to execute test calls. The test MSs should also be able to report back to the CCP regarding whether the test calls were executed as planned, or with some described deviation. Connections between the test MSs and CCP 350 can be made though a wire-line, by radio, or through a nearby base station. A secondary, back-up option for communicating between the CCP 350 and the test MSs is desirable.

In an alternate embodiment, the test MSs of the present invention are not separate devices, but are constructed by adapting the RBSs in a selected area to generate traffic-related data as if called by a test MS whenever testing is in progress.

In another embodiment, one or more test MSs may be equipped with a directional antenna (rather than the omni-directional one found in most conventional cell phones or mobile terminals). Initially, the antenna is directed toward a first RBS. The direction of the antenna is then rotated during transmission to simulate MS movement toward another RBS and generate a hand-off within the cellular network. In yet another embodiment, a test MS could actually be mounted to a regularly moving vehicle, such as a municipal bus or train car, to achieve the same effect. Note that the test MSs can be situated relatively near to each other or spread far apart. Preferably, they operate in several different metropolitan areas to make sure the testing is not overly isolated. Returning to the embodiment of FIG. 3, CCP 350 is also preferably in communication with an Activation Center (AC) 310 (sometimes referred to as a provisioning center), where new subscribers are recruited, and subsequently from where their profile information is entered into the HLR 340 and into the BPPC 360, which are also in communication with AC 310. The communication comiections, of course, may be electronic or by some other means, and may be permanent or ad hoc, and preferably allow the testing process to be initiated from the beginning, that is, from the provisioning of a new subscriber onward. During provisioning, information from the subscriber's (or VTS' s) profile is input into the appropriate HLR 340 and the BPPC 360. The profile information may contain, for example, the subscriber's name and address, a list of the services subscribed to, the rates for those services, etc. Note that the AC 310 may send less than all of the profile data to HLR 340 or BPPC 310, and preferably limits the transmitted information to what will actually be used by the receiving component.

As the test is being run, MSs 362, 364, and 366 communicate with the network in the usual fashion, that is, by going through, for example, RBSs 314, 315, and 316, respectively. Each test MS is not, however, necessarily confined to communicating only though a single RBS. The RBSs in turn access their respective MSCs (such as 330, 332, and 334, respectively). As is explained more fully below, the MSCs make a record of the transmissions that pass through them, including those involved in testing, and pass these records on to the BPPC 360 for use in preparing bills. On their way, the records pass through a Mediation Device (MD) 355 that not only routes them to their proper destination, but in accordance with the present invention detects and filters out VTS CDRs for use in the testing process. Finally, note that the HLR 340 and the BPPC 360 are also in communication with the CCP 350 and with each other so that the data residing in each can be compared, as explained more fully below. FIG 4 is a flow diagram illustrating a method of automatic billing system verification in a radio telecommunications network 100 in accordance with an embodiment of the present invention. The process begins at step 400, where a system such as the one illustrated in FIG. 3 has been configured, and the basic parameters and goals for the test have been defined. The process then moves to step 401, where the CCP 350 (shown in FIG. 3) creates at least one Virtual Test Subscriber (VTS). Note that one VTS maybe adequate under certain conditions, but normally there are many. At least two VTSs are required, of course, if they are to place calls or send messages to each other during the test, and three or more are required if they are to test services such as call forwarding among themselves. The VTS is a fictional subscriber created for testing purposes, and its information profile does not necessarily correspond to an actual network customer. Each VTS profile generated, however, will contain the same types of information as an actual subscriber profile, such as name, address, MSID, list of services subscribed to, and selected billing plan. To the network, the VTS should appear as an ordinary subscriber profile, except where it is necessary to filter out processed data and records for examination. To permit filtering out of test data, the VTS profile contains a VTS identifier, such as a designated phone number, reserved for testing purposes.

The specific VTS profile characteristics can be manually formulated by system engineers to test a particular function, or they can be automatically generated by the system. For example, the profiles of randomly selected new or existing subscribers may be copied and associated with VTS names and MS identification numbers. (Although it is not necessary that the VTS duplicate any one existing subscriber profile.) The VTS may be designed to detect a suspected problem, or simply to test the system after a known modification has been made. The VTS could even be constructed to test service charges or billing plans that have not actually been implemented yet, so that potential problems in billing can be discovered before actual customer bills are processed. Once generated, the VTS is transmitted to the AC 310. If desired, the VTS profile may be given to AC personnel without divulging that a test is being conducted, in order to avoid uncustomary measures being taken to guarantee its accuracy. In steps 403 and 404, AC personnel input the VTS profile into the network as if they were actually provisioning a new subscriber by sending the appropriate profile information to the HLR 340 and the BPPC 360, respectively, where it will be stored for later use. In actual practice, these steps may be performed together or by they may be performed by different personnel at different times. The initial data input is then verified by determining whether the VTS profile in the HLR 340 and the BPPC 360 matches that generated by the CCP 350 (step 406). This comparison can be accomplished in any reliable way. hi one embodiment, a copy of the profile information in the HLR and BPPC is filtered out by the CCP, which uses an Automatic Comparison Tool (ACT) written for making the comparison. In another embodiment, the CCP 350 sends a copy of its VTS profile to the HLR

340 or BPPC 360, where an ACT has been loaded for conducting the comparison there. In yet another embodiment (not shown), the comparison is accomplished by a third, perhaps centrally located device. Of course, the comparison could be limited to only the HLR or the BPPC, or corresponding information in those two components themselves could be compared.

Note that as used in reference to the present invention, 'filtered out' means that a copy of relevant data has been captured and preserved for comparison without disturbing the original data or significantly affecting its regular processing (except where it is intended to do so, for example by delaying further processing until the comparison step is completed). Also, in most embodiments the matching comparisons between regular network-generated billing-system records and those records generated by the Automatic Billing-System Verification (ABV) system of the present invention can be done at such time and in such location as the information is available. By the same token, discrepancy reports can be made at any convenient time, either as the comparison is made or later on in the process.

In the embodiment illustrated in FIG. 4, if the CCP-generated VTS profile information does not match the that stored in the HLR 340 or BPPC 360, then a discrepancy report points out that an error has occurred in the provisioning process (step 407). Reporting the problem at this time not only isolates the link needing correction (or at least one of them), but also gives the network operator an opportunity to address the problem before the testing process continues. Often such continued testing will prove inefficient, especially if the remedial action indirectly affects the downstream testing or repairs. On the other hand, it is possible that only one of many VTS profiles are corrupted and therefore continuing the test may still be useful if known discrepancies are taken into account. At step 408, the decision is made whether to continue testing. If testing is not to continue, the process returns to step 401 and begins again, generally after an attempt is made at corrective action (step not shown). Otherwise, the testing can simply continue using the improperly entered data, either as it is (and as the basis for later calculations) or as it is corrected by simply replacing it with the correct data. In this way at least some testing of the rest of the billing process can be performed immediately. If the VTS profile comparison of step 406 results in a match (or if it did not, but continuation of the testing process was selected at step 408), then the CCP creates and runs the test sequence (step 410).

The test sequence is a pattern of planned network transmissions to be carried out using test MSs such as MSs 362, 364, and 366 at the remote direction of CCP 350. Of course, CCP 350 could alternately have created the test sequence earlier, perhaps when the VTSs were being generated, or it could be one of several standard sequences stored for use in certain situations. The test sequence can be generated according to certain rules previously input to the CCP 350, such as rules that require a certain number of short messages or the use of call forwarding. If desired, the sequence could also be written manually and input to the CCP 350 for execution.

As the test sequence runs, the MSCs involved in routing the calls create Call Data Records (CDRs) that contain information about each call, such as start and finish time, origin and destination, type of call, etc. (step 414). The CDRs, along with the subscriber profiles already stored in the BPPC 360, form the basis for customer billing. Once the CDRs are created, the MSC transmits the them to the MD 355 (step 415). While this may be done one at a time as the VTS CDRs are created, more usually a number of CDRs are accumulated before all being transmitted. The MD 355 receives the CDRs from the network MSCs and routes them to the BPPC 360, filtering out the VTS CDRs associated with the test sequence, that is, those made or received by a VTS (step 416). Typically, the MD 355 will collate the CDRs associated with each VTS separately into a CDR log before sending them on to the BPPC.

The CCP 350 also generates a CDR for each test call and a CDR log for each VTS involved in the test sequence (step 412). Preferably, these CDRs are created as each transmission is made so as to be able to account for any deviation from the planned test sequence (rather than being based simply on the planned sequence itself). A comparison between the baseline CCP-generated CDRs and those generated by the MSCs is then performed (step 418). If they do not match, a report issues that an MSC-CDR generation error exists (step 419). As before, corrective action can be taken at this point or the test allowed to continue. If the CDRs do match (or if the test is to continue anyway), then the CCP generates baseline bills based on the baseline CDRs and VTS profiles involved in the test sequence (step 420). In the normal course of operations, the BPPC 360 also creates bills (step

417) based on the MSC CDR logs received from the MD 355 and the VTS billing profiles that it received previously from the AC 10. The actual bills created by the BPPC are then compared to the baseline bills previously generated by the CCP 350 (step 422). This comparison can be made based on the electronic billing records or the actual bill printed out and compared. If a match occurs, then a compliance report is generated (step 423). If they do not match, the report instead indicates a BPPC bill preparation error (step 424). Corrective action can then be taken and the test rerun (step 425), either with the same VTSs and test sequence or with new ones. When the process of FIG.4 is completed, the bills prepared by BPPC 360 would normally be printed and mailed. Although mailing the actual VTS bills may be too expensive to justify in all cases, it maybe useful at times in order to gage the amount of time needed to get a bill delivered once the billing period ends (assuming the address used for the VTS is a location to which mail can actually be delivered for later collection by the network provider). In general, it should be noted that the steps of the method of the present invention have been disclosed above as a preferred embodiment, but maybe done in any logically-allowed sequence. The testing process could also be adapted to allow changing the test sequence during the test process based on real-time reports made to a human or electronic operator. The system could also be used to test the billing process as it relates to calculating charges for the use of other networks, such as by making test MS calls from an area not covered by the provider's network.

It should also be noted that many of the terms (and especially initialisms) used in describing embodiments of the present invention above are employed because they are recognizable to those skilled in this art. Their use, however, does not imply that the present invention may only be used with radio telecommunications networks whose components are so named. For example, the Mobile Switching Center (MSC) referred to above is a switching center that handles calls to and from mobile-service subscribers. When it handles such calls, it keeps Call Data Records (CDRs), which are simply records of calls including enough data so that they can later be used to ensure the subscriber is correctly billed for the services used. CDR's may also be generated by nodes such as the message center (MXE) for voice mail and short message service messages. Calls may also be routed using packet switches, but some type of charging records are still required to be generated and processed.

Based on the foregoing description, one of ordinary skill in the art should readily appreciate that the present invention advantageously provides a system and method for automatically testing the billing system of a wireless telecommunications network. It is thus believed that the operation and construction of the present invention will be apparent from the foregoing description. While the method shown and described has been characterized as being preferred, it will be readily apparent that various changes and modifications could be made therein without departing from the scope of the invention as defined in the following claims.

Claims

WHAT IS CLAIMED IS:

1. A method of verifying subscriber activation and service provisioning in a radio telecommunications network, said method comprising the steps of: creating a baseline subscriber profile for a Virtual Test Subscriber (VTS); providing the baseline subscriber profile to a subscriber activation center for input into a Home Location Register (HLR) as a VTS profile; and comparing the baseline subscriber profile data with the VTS profile data in the HLR to identify any discrepancies indicating data-entry or process errors.

2. The method of verifying subscriber activation and service provisioning of claim 1, wherein the baseline subscriber profile provided to the subscriber activation center is also provided for input to a billing center, and further comprising the step of comparing the baseline subscriber profile data with the VTS profile data in the billing center to identify any discrepancies indicating data-entry or process errors.

3. A method of verifying a billing process in a radio telecommunications network, said method comprising the steps of: inputting a subscriber profile for a Virtual Test Subscriber (VTS) into the network, said profile including a rate plan; creating a set of baseline call-data records from a VTS call sequence; executing the VTS call sequence through a switching center in the network; generating by the switching center, VTS call-data records from the VTS call sequence; and comparing the baseline call-data records with the VTS call-data records from the switching center to identify any errors in creating call-data records by the switching center.

4. The method of verifying a billing process in a radio telecommunications network of claim 3 further comprising the steps of: determining that the baseline call-data records match the VTS call-data records; sending the VTS call-data records from the switching center to a billing center; applying by the billing center, the rate plan to the VTS call-data records to create a VTS invoice; applying the rate plan to the baseline call-data records to create a baseline invoice; and comparing the VTS invoice to the baseline invoice to identify any errors by the billing center in applying the rate plan.

5. A method of verifying a billing process in a radio telecommunications network, said method comprising the steps of: creating a baseline subscriber profile for a Virtual Test Subscriber (VTS), said profile including a rate plan; providing the baseline subscriber profile to a subscriber activation center for input into a Home Location Register (HLR) as a VTS profile; comparing the baseline subscriber profile with the VTS profile in the HLR to identify any profile data entry or process errors; creating a set of baseline call-data records from a VTS call sequence; executing the VTS call sequence through a switching center in the network; generating by the switching center, VTS call-data records from the VTS call sequence; and comparing the baseline call-data records with the VTS call-data records from the switching center to identify any errors in creating call-data records by the switching center.

6. The method of verifying a billing process in a radio telecommunications network of claim 5 wherein the baseline subscriber profile provided to the subscriber activation center is also provided for input to a billing center, and further comprising the step of comparing the baseline subscriber profile data with the VTS profile data in the billing center to identify any discrepancies indicating data-entry or process errors.

7. The method of verifying a billing process in a radio telecommunications network of claim 5 further comprising the steps of: determining that the baseline call-data records match the VTS call-data records; sending the VTS call-data records from the switching center to a billing center; applying by the billing center, the rate plan to the VTS call-data records to create a VTS invoice; applying the rate plan to the baseline call-data records to create a baseline invoice; and comparing the VTS invoice to the baseline invoice to identify any errors by the billing center in applying the rate plan.

8. A system for radio-telecommunications-network billing-system verification, the system comprising: at least one mobile station for conducting transmission activity involving the network in order to initiate generation by the network of identifiable billing- system test-subscriber records; a central control point (CCP) for directing the at least one mobile station to conduct the transmission activity; means for creating outside of the network, baseline billing records based on the transmission activity and corresponding to the network billing-system test- subscriber records; and comparison means for comparing the baseline billing records and the corresponding billing-system test-subscriber records to identify discrepancies.

9. The system of claim 8 , wherein the transmission activity is directed according to a predetermined testing sequence.

10. The system of claim 9, wherein the predetermined testing sequence is based at least in part on selected network-subscriber transmission patterns.

11. The system of claim 9, wherein the predetermined testing sequence is based at least in part on feedback received from previous system verification testing.

12. The system of claim 9, wherein the baseline billing records are created based on the transmission activity as specified in the predetermined testing sequence.

13. The system of claim 8, wherein the mobile station comprises a directional transmitter for simulating a moving mobile station.

14. The system of claim 8, wherein the mobile station is mounted on a transport means for relocating the mobile station during the test transmission activity.