# US 8,280,346 B2 · Usage measurement collection and analysis to dynamically regulate customer network usage

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 8,280,346 B2
- Document ID: US8280346B2
- Status: Granted
- Kind: B2
- Application number: 13/267,824
- Filed: 2011-10-06
- Published: 2012-02-02
- Granted: 2012-10-02
- Earliest claimed: 2008-08-06
- Assignees: Bridgewater Systems Corp.
- Inventors: D. Mark Jones; Martin Labelle; Edwin Gans
- Web page: https://patentgrep.com/patent/US8280346B2

## CPC

- H04L 67/306: User profiles
- G06Q 30/0251: Targeted advertisements
- G06Q 30/04: Billing or invoicing
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 63/108: {when the policy decisions are valid for a limited amount of time}
- H04M 15/44: {Augmented, consolidated or itemized billing statement or bill presentation}
- H04M 15/58: {based on statistics of usage or network monitoring}
- H04M 15/8207: {Time based data metric aspects, e.g. VoIP or circuit switched packet data}
- H04M 15/8214: {Data or packet based}
- H04M 15/8228: {Session based}
- H04M 15/85: {characterised by the type of condition triggering a notification}
- H04M 15/851: {Determined tariff}
- H04M 15/852: {Low balance or limit reached}
- H04M 15/857: {Cumulative charges}
- H04M 15/88: {Provision for limiting connection, or expenditure}
- 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
- H04M 2215/0116: Provision for limiting expenditure, e.g. limit on call expenses or account
- H04M 2215/0188: Network monitoring; statistics on usage on called/calling number
- H04M 2215/7813: Time based data, e.g. VoIP or circuit switched packet data
- H04M 2215/782: Data or packet based
- H04M 2215/7833: Session based
- H04M 2215/815: Notification when a specific condition, service or event is met
- H04M 2215/8158: Low balance or limit reached
- H04M 2215/8179: Cumulative charges
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)

## Abstract

In a network subscriber system, a method of determining how to monitor whether a subscriber's network usage exceeds a quota for the current billing period. The frequency at which the subscriber's usage data is collected and analyzed during the billing period is based upon the probability the subscriber's network usage exceeds the quota at a given point in time during the billing cycle. Usage data is collected more frequently as the probability increases. Usage analysis is performed if the probability exceeds a threshold.

## Claims

### Claim 1

A method for policing a usage total of a subscriber at a server to determine a level of processing for subscriber usage updates during a usage session, comprising:
determining a usage breach probability at a server, wherein the usage breach probability represents a probability that a subscriber will breach a usage quota during a usage session;
collecting by the server a subscriber usage update including an update of a measurement of subscriber usage;
determining by the server a type of processing for the subscriber usage update based upon an analysis of the usage breach probability, wherein:
when the usage breach probability exceeds a first threshold, updating a subscriber usage total,
when the usage breach probability exceeds a second threshold evaluating the subscriber usage total against the usage quota; or
when the usage breach probability exceeds one or more other thresholds, determining the type of processing for the subscriber usage update based on one or more thresholds that have been exceeded by the usage breach probability.

### Claim 2 (depends on 1)

The method according to claim 1, further comprising:
determining an interim interval at which subscriber usage updates are collected based at least in part on said usage breach probability.

### Claim 3 (depends on 2)

The method according to claim 2, further comprising:
determining a session time value that indicates when reauthorization is required based at least in part on said usage breach probability.

### Claim 4 (depends on 2)

The method according to claim 2, further comprising:
determining a time value that indicates when the interim interval will be updated, based at least in part on said usage breach probability.

### Claim 5 (depends on 4)

The method according to claim 4, further comprising:
communicating an updated interim interval using a change of authorization message.

### Claim 6 (depends on 1)

The method according to claim 1, further comprising:
updating said usage breach probability based at least in part on the subscriber usage update.

### Claim 7 (depends on 1)

The method according to claim 1, wherein determining a usage breach probability includes using at least in part any one or more of current date, billing date, number of breaches for the subscriber, number of breaches for all subscribers, when breaches have occurred for the subscriber, when breaches have occurred for all subscribers, knowledge of peak usage patterns, cumulative usage for the subscriber, and usage quota for the subscriber.

### Claim 8 (depends on 1)

The method according to claim 1, wherein determining a usage breach probability includes using at least in part anyone or more dynamic factors.

### Claim 9 (depends on 8)

The method according to claim 8, wherein the using at least in part anyone or more dynamic factors includes using at least in part any one or more of a type of service being provided to the subscriber, a usage total by the subscriber, a location of use by the subscriber, and a time of day.

### Claim 10 (depends on 1)

The method according to claim 1, wherein determining a usage breach probability includes using at least in part anyone or more static factors.

### Claim 11 (depends on 10)

The method according to claim 10, wherein the using at least in part anyone or more static factors includes using at least in part any one or more of a subscriber profile.

### Claim 12 (depends on 1)

The method according to claim 1, wherein determining a usage breach probability includes using at least in part anyone or more of a heuristic approach, a regression analysis, and an analysis of variance approach.

### Claim 13 (depends on 1)

The method according to claim 1, wherein determining a usage breach probability includes choosing a calculation method based on a confidence level in the calculation method.

### Claim 14 (depends on 1)

The method according to claim 1, further comprising:
generating a marketing message if the usage breach probability exceeds a marketing threshold.

### Claim 15

A system for policing a usage total of a subscriber to determine a level of processing for subscriber usage updates, comprising:
a breach probability calculation module adapted to determine a usage breach probability, wherein the usage breach probability represents a probability that a subscriber will breach a usage quota during a usage session;
a breach analysis module adapted to analyze usage data based in part on the usage breach probability;
a network provider interface adapted to communicate with network provider facilities;
a subscriber profile interface adapted to interface with a subscriber profile repository; and
a subscriber usage interface adapted to interface with a subscriber usage repository;
wherein the breach analysis module is further adapted to:
collect a subscriber usage update including an update of a measurement of subscriber usage;
update a subscriber usage total upon determination that the usage breach probability exceeds a first threshold;
evaluate the subscriber usage total against a usage quota, upon determination that the usage breach probability exceeds a second threshold; and
determine the type of processing for the subscriber usage update upon determination that the usage breach probability exceeds one or more other thresholds, based on one or more thresholds that have been exceeded by the usage breach probability.

### Claim 16 (depends on 15)

The system according to claim 15, wherein the breach analysis module is further adapted to:
determine a session time value that indicates when reauthorization is required based at least in part on the usage breach probability.

### Claim 17 (depends on 15)

The system according to claim 15, wherein a usage update interval module is adapted to determine an interim interval at which subscriber usage updates are collected based at least in part on the usage breach probability, and wherein the breach analysis module is further adapted to:
determine a time value that indicates when the interim interval will be updated, based at least in part on the usage breach probability.

### Claim 18 (depends on 15)

The system according to claim 15, wherein a usage update interval module is adapted to determine an interim interval at which subscriber usage updates are collected based at least in part on the usage breach probability, and wherein the breach analysis module is further adapted to:
communicate an updated interim interval via the network provider interface using a change of authorization message.

### Claim 19 (depends on 15)

The system according to claim 15, wherein the network provider interface is coupled to a user interface.

### Claim 20 (depends on 15)

The system according to claim 15, wherein the breach probability calculation module is further adapted to:
update the usage breach probability based at least in part on a subscriber usage update.

### Claim 21 (depends on 15)

The system according to claim 15, wherein the breach probability calculation module is further adapted to determine a usage breach probability based at least in part on any one or more of current date, billing date, number of breaches for the subscriber, number of breaches for all subscribers, when breaches have occurred for the subscriber, when breaches have occurred for all subscribers, knowledge of peak usage patterns, cumulative usage for the subscriber, and usage quota for the subscriber.

### Claim 22 (depends on 15)

The system according to claim 15, wherein the network provider interface is adapted to communicate according to at least one of RADIUS and Diameter protocols.

### Claim 23 (depends on 22)

The system according to claim 22, wherein a usage update interval module is adapted to determine an interim interval at which subscriber usage updates are collected based at least in part on the usage breach probability, and wherein the network provider interface is further adapted to communicate the interim interval in an access accept message.

### Claim 24 (depends on 22)

The system according to claim 22, wherein the breach analysis module is further adapted to determine a session time value that indicates when reauthorization is required based at least in part on the usage breach probability, and communicate the session time value in an access accept message.

### Claim 25 (depends on 22)

The system according to claim 22, wherein a usage update interval module is adapted to determine an interim interval at which subscriber usage updates are collected based at least in part on the usage breach probability, and wherein the network provider interface module is further adapted to communicate an updated interim interval in a change of authorization message.

### Claim 26 (depends on 22)

The system according to claim 22, wherein the breach probability calculation module is further adapted to update the usage breach probability based at least in part on a subscriber usage update received in an accounting request message via the network provider interface.

### Claim 27 (depends on 22)

The system according to claim 22, wherein the breach analysis module is a server that communicates with a network access server via the network provider interface.

### Claim 28 (depends on 15)

The system according to claim 15, further comprising:
a marketing system interface coupled to the breach probability calculation module and adapted to output a marketing message if the usage breach probability exceeds a market threshold.
