Network accounting and billing system and method

• US 6,418,467 B1
• Filed: 11/18/1999
• Issued: 07/09/2002
• Est. Priority Date: 11/20/1997
• Status: Expired due to Term

• Current Assignee: Amdocs Development Limited (Amdocs Ltd.), Amdocs Ltd.
• Original Assignee: Xacct Technologies Ltd.
• Inventors: Wagner, Eran, Givoly, Tal, Schweitzer, Limor
• Primary Examiner(s): WILEY, DAVID ARMAND
• Application Number:
  US09/442,876
• Time in Patent Office: 964 Days
• Field of Search: 705/1, 705/14, 705/17, 705/44, 709/223-226, 707/4, 235/380, 395/241, 380/25
• US Class Current: 709/223
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 40/12 Accounting
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 12/1428 Invoice generation, e.g. customization, lay-out, database processing, algorithms for calculating the bill or formatting invoices as WWW pages invoicing in general G06Q30/04
• CPC Class Codes: H04L 41/5025 by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade
• CPC Class Codes: H04L 41/5067 Customer-centric QoS measurements
• CPC Class Codes: H04L 43/022 by sampling
• CPC Class Codes: H04L 43/026 using flow identification
• CPC Class Codes: H04L 43/0876 Network utilisation, e.g. volume of load or congestion level
• CPC Class Codes: H04M 15/00 Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
• CPC Class Codes: H04M 15/31 Distributed metering or calculation of charges
• CPC Class Codes: H04M 15/41 Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
• CPC Class Codes: H04M 15/43 Billing software details
• CPC Class Codes: H04M 15/44 Augmented, consolidated or itemized billing statement or bill presentation
• CPC Class Codes: H04M 15/53 using mediation
• CPC Class Codes: H04M 15/55 for hybrid networks
• CPC Class Codes: H04M 15/56 for VoIP communications
• CPC Class Codes: H04M 15/80 Rating or billing plans; Tariff determination aspects
• CPC Class Codes: H04M 15/8214 : Data or packet based
• CPC Class Codes: H04M 2215/0104 : Augmented, consolidated or itemised billing statement, e.g. additional billing information, bill presentation, layout, format, e-mail, fax, printout, itemised bill per service or per account, cumulative billing, consolidated billing
• CPC Class Codes: H04M 2215/0152 : General billing plans, rate plans, e.g. charge rates, numbering plans, rate centers, customer accounts
• CPC Class Codes: H04M 2215/0164 : Billing record, e.g. Call Data Record [CDR], Toll Ticket[TT], Automatic Message Accounting [AMA], Call Line Identifier [CLI], details, i.e. parameters, identifiers, structure
• CPC Class Codes: H04M 2215/0172 : Mediation, i.e. device or program to reformat CDRS from one or more switches in order to adapt to one or more billing programs formats
• CPC Class Codes: H04M 2215/2013 : Fixed data network, e.g. PDN, ATM, B-ISDN
• CPC Class Codes: H04M 2215/202 : VoIP; Packet switched telephony
• CPC Class Codes: H04M 2215/22 : Bandwidth or usage-sensitve billing
• CPC Class Codes: H04M 2215/44 : Charging/billing arrangements for connection made over different networks, e.g. wireless and PSTN, ISDN, etc.
• CPC Class Codes: H04M 2215/782 : Data or packet based
• CPC Class Codes: H04M 2215/96 : Distributed calculation of charges, e.g. in different nodes like for mobiles between HLR and VLR, or between the terminal and the billing function
• CPC Class Codes: Y02D 30/50 : in wire-line communication networks, e.g. low power modes or reduced link rate

Abstract

In some embodiments, network traffic information is captured at network information sources. These sources provide detailed information about the network communications transactions at a network device. Importantly, different types of sources can provide different types of information. Gatherer devices gather the detailed information from the various information source devices and convert the information into standardized information. The gatherer devices can correlate the gathered information with account information for network transaction accounting. Manager devices manage the gatherer devices and store the gathered standardized information. The manager devices eliminate duplicate network information that may exist in the standardized information. The manager devices also consolidate the information. Importantly, the information stored by the manager devices represents the consolidated, account correlated, network transaction information that can be used for billing or network accounting. The system thereby provides a distributed network accounting and billing system.

Claims

1. A method for billing and charging for network usage, comprising:

(a) collecting network communications usage information in real-time from network devices at a plurality of layers utilizing multiple gatherers each including a plurality of information source modules each interfacing with one of the network devices and capable of communicating using a protocol specific to the network device coupled thereto, the network devices selected from the group consisting of routers, switches, firewalls, authentication servers, web hosts, proxy servers, netflow servers, databases, mail servers, RADIUS servers, and domain name servers, the gatherers being positioned on a segment of the network on which the network devices coupled thereto are positioned for minimizing an impact of the gatherers on the network;

(b) translating the network communications usage information collected from the network devices utilizing the information source modules;

(c) caching the network communications usage information collected from the network devices utilizing the gatherers;

(d) normalizing the network communications usage information with the gatherers by excluding fields not required by a central event manager coupled to the gatherers;

(e) defining an enhancement procedure utilizing the central event manager by;

(i) accessing the central event manager,

(ii) naming the enhancement procedure,

(iii) selecting a trigger for the enhancement procedure, the trigger corresponding to at least one of the information source modules,

(iv) identifying a field type to be enhanced,

(v) listing a plurality of fields that match the field type to be enhanced,

(vi) listing a plurality of functions available based on the information source module corresponding to the trigger,

(vii) allowing the user to choose at least one of the listed fields, and

(viii) allowing a user to choose at least one of the listed functions;

(f) displaying the enhancement procedure on a graphical user interface by representing each function as a separate graphical representation, wherein the graphical representations are shown to be joined to each other in accordance with the enhancement procedure;

(g) coordinating the collection of the network communications usage information by the gatherers utilizing the central event manager;

(h) filtering the network communications usage information utilizing the central event manager;

(i) aggregating the network communications usage information and the data records utilizing the central event manager for reducing a number of the data records;

(j) enhancing the aggregation in accordance with the defined enhancement procedure, the enhancement including;

(i) receiving the network communications usage information,

(ii) determining whether the trigger has occurred,

(iii) if the trigger has occurred, applying the at least one chosen function associated with the enhancement procedure to the network communications usage information,

(iv) identifying results of the function,

(v) using the results of the function to gather additional network communications usage information from other gatherers, and

(vi) enhancing the chosen field with the additional network communications usage information;

(k) completing a plurality of data records from the filtered network communications usage information by accessing user account information, and determining for each data record a corresponding source IP address, a corresponding domain name, a corresponding type of service used, and a corresponding amount of time that the service was used, the plurality of data records corresponding to network usage by a plurality of users;

(l) merging duplicate records in the plurality of data records for enhancing efficiency;

(m) billing the users based on the data records;

(n) time stamping the data records;

(o) storing the time stamped data records in tables in a central database coupled to the central event manager at a user-specified interval;

(p) deleting the stored data records upon the cessation of a predetermined amount of time after the storage utilizing the timestamp;

(q) periodically determining whether the network devices are currently licensed;

(r) submitting network activity queries to the central database for retrieving information on activity of the network;

(s) outputting a network activity report based on the network activity queries;

(t) submitting resource consumption queries to the central database for retrieving information on resource consumption in the network;

(u) outputting a resource consumption report based on the resource consumption queries;

(v) continuously monitoring a state of the gatherers;

(w) detecting a fault;

(x) utilizing the state of the gatherers and the stored data records to recover from the fault upon the detection thereof;

(y) generating an alert upon the occurrence of an event utilizing the information source modules;

(z) wherein the data records are in a data record format having a plurality of fields including a source IP field, a destination IP field, a source host field, a destination host field, a service type field, a date and time field, a duration field, a total number of bytes field, and a counter field.