WO2002003336A2 - Systeme et procede de verification automatique d'un systeme de facturation - Google Patents

Systeme et procede de verification automatique d'un systeme de facturation Download PDF

Info

Publication number
WO2002003336A2
WO2002003336A2 PCT/SE2001/001586 SE0101586W WO0203336A2 WO 2002003336 A2 WO2002003336 A2 WO 2002003336A2 SE 0101586 W SE0101586 W SE 0101586W WO 0203336 A2 WO0203336 A2 WO 0203336A2
Authority
WO
WIPO (PCT)
Prior art keywords
vts
call
billing
baseline
subscriber
Prior art date
Application number
PCT/SE2001/001586
Other languages
English (en)
Other versions
WO2002003336A3 (fr
Inventor
Carignan Hugues
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to AU2001268013A priority Critical patent/AU2001268013A1/en
Publication of WO2002003336A2 publication Critical patent/WO2002003336A2/fr
Publication of WO2002003336A3 publication Critical patent/WO2002003336A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70—Administration or customization aspects; Counter-checking correct charges
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/48—Secure or trusted billing, e.g. trusted elements or encryption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/73—Validating charges
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01—Details of billing arrangements
    • H04M2215/0156—Secure and trusted billing, e.g. trusted elements, encryption, digital signature, codes or double check mechanisms to secure billing calculation and information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/20—Technology dependant metering
    • H04M2215/2026—Wireless network, e.g. GSM, PCS, TACS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/32—Involving wireless systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/70—Administration aspects, modify settings or limits or counter-check correct charges
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/70—Administration aspects, modify settings or limits or counter-check correct charges
    • H04M2215/7072—Validate charges

Definitions

  • the present invention relates to telecommunication systems, and more specifically to a system and method of automatic billing verification in a radio telecommunications network.
  • 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.
  • PLMNs Land Mobile Networks
  • MSC Mobile Switching Center
  • 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).
  • 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.
  • 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.
  • HLR Home Location Register
  • BPPC Billing Post- Processing Center
  • 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.
  • POTS Plain-Old Telephone System
  • a flat-rate for local calls 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).
  • 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 VTSs
  • VTSs virtual test subscribers
  • MS mobile station
  • MSC network mobile switching center
  • 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.
  • HLR network home location register
  • 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
  • FIG. 1 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.
  • the present invention provides a system for, and method of conducting automatic billing-system verification (ABV) in a wireless radio telecommunications network.
  • ABSV automatic billing-system verification
  • 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.
  • AC Activation Center
  • 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.
  • MS mobile station
  • PC personal computer
  • PDA personal digital assistant
  • 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.
  • the one receiving the strongest signal will generally be used for the connection.
  • the connection will be switched in what is referred to as a 'hand-off .
  • 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).
  • MSC Mobile Switching Center
  • 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).
  • MSC/VLR service area (delineated by broken lines in FIG. 1).
  • PLMN Public Land Mobile Network
  • 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 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.
  • registration a process called registration
  • the registration process enables other MSCs to detect its location in their respective MSC/VLR service areas.
  • each MSC reports registration information stored in its VLR to HLR 40.
  • the HLR 40 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
  • GMSC Gateway Mobile Switching Center
  • 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.
  • BPPC Billing Post-Processing Center
  • 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.
  • SMS short message service
  • 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.
  • MCS 30 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
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • AC Activation Center
  • the communication comiections 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.
  • 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.
  • 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.
  • 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.
  • RBSs 314, 315, and 316 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).
  • 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.
  • 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.
  • VTS Virtual Test Subscriber
  • the CCP 350 shown in FIG. 3 creates at least one Virtual Test Subscriber (VTS).
  • VTS Virtual Test Subscriber
  • 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.
  • the VTS should appear as an ordinary subscriber profile, except where it is necessary to filter out processed data and records for examination.
  • 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.
  • 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.
  • 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.
  • 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.
  • ACT Automatic Comparison Tool
  • the CCP 350 sends a copy of its VTS profile to the HLR
  • the comparison is accomplished by a third, perhaps centrally located device.
  • the comparison could be limited to only the HLR or the BPPC, or corresponding information in those two components themselves could be compared.
  • '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).
  • 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.
  • ABSV Automatic Billing-System Verification
  • 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.
  • 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.
  • 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.
  • 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).
  • CDRs Call Data Records
  • 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.
  • the CCP 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 420).
  • 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.
  • the Mobile Switching Center 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.
  • CDRs Call Data Records
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Meter Arrangements (AREA)

Abstract

Un système et un procédé de vérification de l'exactitude et de l'intégrité d'un système de facturation utilisé pour facturer les abonnés d'un réseau de radiotélécommunication. On utilise un ordinateur (350) fonctionnant indépendamment du système de facturation (360) pour générer des informations biographiques et de solvabilité fictives sur au moins un abonné test virtuel (VTS) (362-366). On ajoute ces informations à la base de données en réseau (340) comme de véritables données abonné, et un dispositif de simulation (350) simule un VTS qui passe et reçoit des appels et exerce d'autres activités d'appel réseau. Le système de facturation réseau (360) enregistre l'activité d'appel du VTS, entre les enregistrements dans un journal et prépare une facture au VTS comme pour n'importe quel autre abonné. On prépare, en dehors du système, des enregistrements ligne de base, des journaux et des factures pour les comparer à de véritables enregistrements, journaux et factures, toute différence étant signalée à l'opérateur réseau.
PCT/SE2001/001586 2000-07-06 2001-07-06 Systeme et procede de verification automatique d'un systeme de facturation WO2002003336A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2001268013A AU2001268013A1 (en) 2000-07-06 2001-07-06 System and method for automatic billing-system verification

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US61136000A 2000-07-06 2000-07-06
US09/611,360 2000-07-06

Publications (2)

Publication Number Publication Date
WO2002003336A2 true WO2002003336A2 (fr) 2002-01-10
WO2002003336A3 WO2002003336A3 (fr) 2002-06-20

Family

ID=24448714

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2001/001586 WO2002003336A2 (fr) 2000-07-06 2001-07-06 Systeme et procede de verification automatique d'un systeme de facturation

Country Status (2)

Country Link
AU (1) AU2001268013A1 (fr)
WO (1) WO2002003336A2 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2427328A (en) * 2005-06-14 2006-12-20 John Paul Davies Revenue assurance system
WO2009131499A1 (fr) * 2008-04-21 2009-10-29 Telefonaktiebolaget L M Ericsson (Publ) Procédé pour déterminer un possible trafic commuté localement dans un site de réseau cellulaire
EP2369822A1 (fr) * 2008-10-27 2011-09-28 Huawei Technologies Co., Ltd. Procédé et dispositif de test d un montant de facturation mensuelle
WO2014200427A1 (fr) * 2013-06-14 2014-12-18 Nt8 Software Solutions (Singapore) Pte Ltd Procédé et système de validation

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999009733A1 (fr) * 1997-08-14 1999-02-25 Telia Ab (Publ) Ameliorations relatives a des systemes de telecommunications
WO1999014933A1 (fr) * 1997-09-15 1999-03-25 Swisscom Ag Systeme et procede de tarification dans un reseau de telecommunication
US5982864A (en) * 1997-05-01 1999-11-09 At& T Corp Telephone billing with customized billing information
EP0957644A1 (fr) * 1998-05-13 1999-11-17 BRITISH TELECOMMUNICATIONS public limited company Système de facturation
WO2000008865A2 (fr) * 1998-08-01 2000-02-17 Samsung Electronics Co., Ltd. Procede de facturation dans un commutateur electronique de reseau cellulaire

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5982864A (en) * 1997-05-01 1999-11-09 At& T Corp Telephone billing with customized billing information
WO1999009733A1 (fr) * 1997-08-14 1999-02-25 Telia Ab (Publ) Ameliorations relatives a des systemes de telecommunications
WO1999014933A1 (fr) * 1997-09-15 1999-03-25 Swisscom Ag Systeme et procede de tarification dans un reseau de telecommunication
EP0957644A1 (fr) * 1998-05-13 1999-11-17 BRITISH TELECOMMUNICATIONS public limited company Système de facturation
WO2000008865A2 (fr) * 1998-08-01 2000-02-17 Samsung Electronics Co., Ltd. Procede de facturation dans un commutateur electronique de reseau cellulaire

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2427328A (en) * 2005-06-14 2006-12-20 John Paul Davies Revenue assurance system
GB2427328B (en) * 2005-06-14 2010-04-14 John Paul Davies Revenue assurance system
WO2009131499A1 (fr) * 2008-04-21 2009-10-29 Telefonaktiebolaget L M Ericsson (Publ) Procédé pour déterminer un possible trafic commuté localement dans un site de réseau cellulaire
US8477646B2 (en) 2008-04-21 2013-07-02 Telefonaktiebolaget L M Ericsson (Publ) Method for determining possible locally switched traffic within a cellular network site
EP2369822A1 (fr) * 2008-10-27 2011-09-28 Huawei Technologies Co., Ltd. Procédé et dispositif de test d un montant de facturation mensuelle
EP2369822A4 (fr) * 2008-10-27 2012-03-28 Huawei Tech Co Ltd Procédé et dispositif de test d un montant de facturation mensuelle
WO2014200427A1 (fr) * 2013-06-14 2014-12-18 Nt8 Software Solutions (Singapore) Pte Ltd Procédé et système de validation

Also Published As

Publication number Publication date
AU2001268013A1 (en) 2002-01-14
WO2002003336A3 (fr) 2002-06-20

Similar Documents

Publication Publication Date Title
US8244208B2 (en) Network-based system and method for global roaming
US8406731B2 (en) Charging efficiency for a mobile subscriber based on pre-paid or flat-rate billing arrangements
EP2215746B1 (fr) Gestion de la connectivité et diagnostic pour les dispositifs de données cellulaires
CN100382636C (zh) 在移动系统中控制漫游的方法以及网络部件
EP1052841A2 (fr) Système et méthode de facturation dans un résau de télécommunications radio
US6985446B1 (en) Intelligent network services in packet-switched network
CN101374055A (zh) 计费处理方法和网络系统、分组数据网络网关及计费系统
US20130103558A1 (en) Wireless local area network (wlan) gateway system
JP2002305763A (ja) 移動体データ・ネットワーク
EP1266535B1 (fr) Transmission d'enregistrements detailles des appels dans un systeme de telecommunication
EP2149275B1 (fr) Système et procédé d'utilisation d'un réseau partagé ayant un code de réseau mobile
EP1649708A1 (fr) Procede et systeme permettant l'introduction d'une information de position dans un message ussd par un noeud de reseau
WO2002003336A2 (fr) Systeme et procede de verification automatique d'un systeme de facturation
CN101330661B (zh) 一种网间漫游用户的短信计费方法及系统
CN100514995C (zh) 面向移动通信网的短消息业务计费准确性检测装置及方法
US7424283B1 (en) Method and system for billing for multicast communications to wireless terminals
US20040008672A1 (en) Wireless telephone usage management
CN101577625A (zh) 定位业务计费方法、服务节点、移动定位中心及计费网关
CN100496153C (zh) 叠加方式预付费被叫用户漫游计费的方法
JP2000270360A (ja) 課金情報通知装置、方法、無線端末、通信システム及びコンピュータ読み取り可能な記憶媒体
CN111787497B (zh) 一种使用数据库集群存储计费原始话单的方法
EP2506454B1 (fr) Relais, procédé et système de fourniture de service
CN107567091A (zh) 位置区更新方法和移动台
GB2365678A (en) Call detail record generation in a telecommunications system
CN101448280B (zh) WiMAX系统中监听切换事件的方法

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
AK Designated states

Kind code of ref document: A3

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A3

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase in:

Ref country code: JP