Method and apparatus for generating user-specified reports from radius information

Abstract

A method and apparatus are provided for generating a report that summarizes performance of a network based on actual network performance data formatted according to the RADIUS protocol. A network access server generates and stores RADIUS accounting information. An archiver, operating under the control of archive configuration control information, and stores it in archive data. A report generator reads the archive data, under control of report configuration control information, and generates a report. The report configuration control information specifies a report type (accumulate values, count values, or determine a maximum value); one or more categories of RADIUS attributes that are to be accumulated, counted, or otherwise reported; and a title and related information. Thus, a user of a network management system may define custom reports by modifying the report configuration control information, thereby reducing the need for custom report programming, reducing engineering time and project management time, and reducing concomitant costs.

Claims

What is claimed is:

1. A method of generating a report that describes performance characteristics of a computer network based on RADIUS accounting information that is produced by the network in operation, the method comprising the steps of:

creating and storing archive data comprising a selected portion of the RADIUS accounting information;

creating and storing configuration information that defines the report and comprises a report type identifier that is associated with one or more RADIUS attributes that identify data values in the archive data and that is associated with a generic report type; and one or more attribute values that specify bounds of ranges of the data values;

retrieving and parsing the configuration information to create and store one or more buckets associated with the ranges of the data values for receiving data values falling within such ranges;

reading the archive data and selectively storing its data values in the buckets based on the configuration information; and

generating a report by displaying the values that are in the buckets.

2. A method as recited in claim 1, wherein creating and storing configuration information comprises:

creating and storing configuration information that defines the report and comprises a report type identifier that is associated with one or more RADIUS attributes that identify data values in the archive data and that is associated with a generic report type; one or more attribute values that specify bounds of ranges of the data values; and an abbreviation of a name associated with the report;

storing a label, which includes the abbreviation, in a section of the configuration information that identifies the bounds of ranges.

3. A method as recited in claim 1, wherein the step of generating a report comprises the step of generating a report by displaying the values that are in the buckets only when an attribute in the archive data indicates that an end of the report has been reached.

4. A method as recited in claim 1, wherein the step of reading the archive data and selectively storing its data values further includes the step of rolling the data values in the buckets when a new time period is identified in the archive data.

5. A method as recited in claim 1, wherein the step of generating a report further comprises the step of creating and storing report data in the form of a matrix having rows corresponding to time periods and columns corresponding to customers, and wherein the step of reading the archive data and selectively storing its data values further includes the step of, when a new customer is identified in the archive data, creating a new column in the matrix and creating rows containing zero data from the starting time period up to the time period currently being processed.

6. A method as recited in claim 1, wherein the step of reading the archive data and selectively storing its data values in associated buckets only when the data values are needed by the current report and its associated buckets.

7. A method as recited in claim 1, wherein creating and storing configuration information comprises:

creating and storing configuration information that defines a plurality of reports, the configuration information comprising, for each of the plurality of reports:

a report type identifier that is associated with one or more RADIUS attributes that identify data values in the archive data and that is associated with a generic report type;

a time interval value that indicates a period of time to be covered by information in the report; and

one or more category values that specify bounds of ranges of the data values.

8. A method as recited in claim 7, wherein creating and storing configuration information comprises:

creating and storing configuration information that defines a plurality of reports, the configuration information comprising, for each of the plurality of reports:

a report type identifier that is associated with one or more RADIUS attributes that identify data values in the archive data and that is associated with a generic report type;

a time interval value that indicates a period of time to be covered by information in the report; and

one or more category values that specify bounds of ranges of the data values; and

an abbreviation of a name associated with the report;

storing a label, which includes the abbreviation, in a section of the configuration information that identifies the bounds of ranges.

9. A method as recited in claim 7, wherein creating and storing configuration information comprises:

creating and storing configuration information that defines a plurality of reports, the configuration information comprising, for each of the plurality of reports:

a report type identifier that is associated with one or more RADIUS attributes that identify data values in the archive data and that is associated with a generic report type selected from among: a numeric value counting report type; a string value counting report type; and an accumulating report type.

10. A method as recited in claim 1, further comprising the steps of:

receiving and storing non-RADIUS network accounting data;

selectively archiving a portion of the non-RADIUS network accounting data in a non-RADIUS archive;

storing a sub-portion of information from the non-RADIUS archive in the archive data, based on non-RADIUS archive configuration control information.

11. A method as recited in claim 1, wherein generating a report comprises:

generating a maximum-sessions-exceeded report that presents, for a pre-determined time period that is identified in the configuration information, a number of sessions of the clients and the network that exceeded a maximum allowed number of sessions.

12. A method as recited in claim 11, wherein the step of receiving connection information comprises the step of receiving Non-RADIUS accounting information from the network access servers, and wherein the step of generating a report comprises generating the report based, in part, on the Non-RADIUS accounting information.

13. A method as recited in claim 1, wherein generating a report comprises:

generating a number-of-sessions-by-entity report that presents, for a pre-determined time period that is identified in the configuration information, a number of sessions carried out between clients that are associated with a particular entity and the network, and a number of maximum simultaneous sessions allowed for the entity.

14. A method as recited in claim 1, wherein generating a report comprises:

generating a call duration report that presents, for a pre-determined time period that is identified in the configuration information, a plurality of numbers of calls that are carried out in each of a plurality of time ranges for a particular entity.

15. A method as recited in claim 1, wherein generating a report comprises:

generating a connect hours report that presents, for a pre-determined time period that is identified in the configuration information, a cumulative total time that a particular entity is connected to the network.

16. A method as recited in claim 1, wherein generating a report comprises:

generating a disconnect reason report that presents, for a pre-determined time period that is identified in the configuration information, reasons that calls between a particular entity and the network are disconnected, and a count of a number of calls that are disconnected for each of the reasons.

17. A method as recited in claim 1, wherein generating a report comprises:

generating a connection speed report that presents, for a predetermined time period that is identified in the configuration information, a plurality of number of connection speed values that are used in each of a plurality of speed categories.

18. A method as recited in claim 1, wherein generating a report comprises:

generating a count number report that presents, for a pre-determined time period that is identified in the configuration information, a plurality of number values that are counted in each of a plurality of categories.

19. A method as recited in claim 1, wherein generating a report comprises:

generating a count string report that presents, for a predetermined time period that is identified in the configuration information, a plurality of string values that are counted in each of a plurality of string values.

20. A method as recited in claim 1, wherein generating a report comprises:

generating an accumulate report that presents, for a pre-determined time period that is identified in the configuration information, a sum of a plurality of numeric values.

21. The method recited in claim 1, wherein:

the step of creating and storing archive data is performed using a first computer; and

the step of creating and storing configuration information and the step of retrieving and parsing the configuration information are performed using a second computer;

wherein the first computer and the second computer are different computers.

22. A method for dynamically generating a network performance report based on RADIUS network accounting information, the method comprising the steps of:

receiving first connection information that defines one or more connections of clients to the network over a particular period of time and that is stored in RADIUS attribute format;

receiving archive configuration control information that identifies attributes that are associated with data that should be maintained for generating report data;

storing second connection information that represents data values associated with the identified attributes that are found in the first connection information;

receiving report configuration control information that specifies a network performance report type and one or more data classifications for representing the first or second connection information within the network performance report; and

dynamically generating the report data based on the specified report type and the data classifications.

23. A method as recited in claim 22, wherein the step of receiving connection information comprises the step of receiving RADIUS accounting information from one or more network access servers that interface the clients to the network.

24. A computer-readable medium carrying one or more sequences of one or more instructions for generating a report that describes performance characteristics of a computer network based on RADIUS accounting information that is produced by the network in operation, the one or more sequences of one or more instructions including instructions which, when executed by one or more processors, cause the one or more processors to perform the steps of:

creating and storing archive data comprising a selected portion of the RADIUS accounting information;

creating and storing configuration information that defines the report and comprises a report type identifier that is associated with one or more RADIUS attributes that identify data values in the archive data and that is associated with a generic report type; and one or more attribute values that specify bounds of ranges of the data values;

retrieving and parsing the configuration information to create and store one or more buckets associated with the ranges of the data values for receiving data values falling within such ranges;

reading the archive data and selectively storing its data values in the buckets based on the configuration information; and

generating a report by displaying the values that are in the buckets.

25. A system for generating a report that describes performance characteristics of a computer network based on RADIUS accounting information that is produced by the network in operation, the system comprising:

one or more storage mediums;

one or more processors coupled to the one or more storage mediums; and

one or more sets of computer instructions associated with said one or more storage mediums, the one or more sets of computer instructions including computer instructions which when executed by the one or more processors, cause the one or more processors to perform the steps of:

creating and storing archive data comprising a selected portion of the RADIUS accounting information;

creating and storing configuration information that defines the report and comprises a report type identifier that is associated with one or more RADIUS attributes that identify data values in the archive data and that is associated with a generic report type; and one or more attribute values that specify bounds of ranges of the data values;

retrieving and parsing the configuration information to create and store one or more buckets associated with the ranges of the data values for receiving data values falling within such ranges;

reading the archive data and selectively storing its data values in the buckets based on the configuration information; and

generating a report by displaying the values that are in the buckets.

Description

FIELD OF THE INVENTION

The present invention generally relates to data processing. The invention relates more specifically to generating reports that show information relating to networks, and further relates to methods and apparatus for generating user-specified reports of network accounting information.

BACKGROUND OF THE INVENTION

A network system generally includes a number of network devices, such as switches, routers, and others, connected so as to allow communication among the devices and end station devices such as desktop machines, servers, hosts, printers, fax machines, and others. Many companies have a desire to provide remote access to their computer networks. By allowing remote access, individuals can connect to the computer network to use it to work and obtain resource information while located at a remote site.

A popular method of providing remote access to a network is through the use of a dial-in network access server (NAS) that controls access to the network. For example, the server model AS5300, commercially available from Cisco Systems Inc., can be used to provide dial-in access to a company's network. Individuals can access the network system by dialing into the network access server from a Remote Node to establish a connection. In this context, the term Remote Node refers to a client device such as a personal computer (PC) or router that can be used to dial in and establish a connection with the network access server.

Managing the dial-in connections that are made to a large number of network access servers can require significant administrative support. Not only must administrative support personnel ensure that network security is maintained, but they must also ensure that remote access to the network is properly provided to those individuals that are authorized to access the network remotely, and that appropriate response times are maintained once a connection is established. When the network access servers are part of an Internet Service Provider (ISP) or other commercial institution, accurate accounting of connection time is required so that customers may be billed correctly. These functions are generically known as authorization, authentication and accounting (AAA).

One method of managing connections to a group of network access servers is through use of a shared accounting server, such as authorization, authentication and accounting (AAA) server software component of CiscoSecure ACS, which is commercially available from Cisco Systems Inc. With a shared accounting server, connection accounting information that is associated with the dial-in connections that are established with the different network access servers can be maintained at one location. In this context, the connection accounting information represents statistical data about the connections that were made or which were attempted to be made with a group of network access servers. For standardization purposes, certain accounting protocols have been developed that define the accounting information that is to be communicated between a network access server and a shared accounting server. For example, the Remote Authentication Dial In User Service (RADIUS) Accounting protocol can be used for carrying accounting information between network access servers and a shared accounting server. The RADIUS Accounting protocol is defined in detail in such documents as Request For Comment (RFC) 2138 and RFC 2139. Existing network systems are based on standard accounting protocols such as the RADIUS Accounting protocol. In these systems, a shared accounting server typically stores the accounting information in one or more files.

FIG. 3 illustrates RADIUS accounting data 300 in a file containing two exemplary RADIUS Accounting records 302, 304 that describe connections that were made between a shared accounting server and a group of network access servers. Timestamp values 306, 308 indicate the respective creation date and time for records 302, 304. Once the RADIUS Accounting information is stored, an administrator may access the information to determine specific information about particular connection that was established with a particular network access server.

However, a drawback with storing the RADIUS Accounting information in a file, as depicted in Table 1, is that interpreting the significance of the data can be both difficult and extremely time consuming. Thus, to aid in the interpretation of the data, a mechanism may generate a report that summarizes or interprets certain information about the connections. For example, a report may indicate the number of times a particular port was used by each of the network access servers. Alternatively, a report may indicate the connection speed used for a particular connection. In another alternative, a report indicates the total number of connections that were established with the group of network access servers for a particular day.

However, a drawback with generating such reports is that different information may be important to different network administrators. For example, a particular administrator may require a report that depicts the number of connections that were established with a particular network access server, while a different administrator may require a report that depicts the connection speed that was established for each connection.

In addition, different administrators may require that the information be displayed in different formats. For example, one administrator may require that a report be generated that depicts the number of connections that were established with a network access server on a week-by-week basis. Alternatively, another administrator may require that a report be generated that depicts the number of connections that were established with a network access server on an hour-by-hour basis. Thus, each administrator may require that different types of reports be generated.

As a result, in past approaches, generating such different reports has required custom, hard-coded software that must be modified whenever a new report is created. In addition, if an administrator later determines that a new report type is required, additional software will typically be required to produce the new report type. The software that generates a particular report is typically fixed and must undergo frequent revision as the administrator requests new capabilities. Based on the foregoing, there is a clear need for a mechanism that can produce reports that contain accounting information that is desired by a particular individual.

There is also a need for a mechanism that can produce reports that contain information in the particular format that is desired by the individual.

Requests for new reports may cause projects to have larger than normal maintenance efforts. Further, requests for new reports typically are handled by the vendor of the network equipment or the vendor of the AAA server software. If the vendor has insufficient engineering resources available, further delay is caused until an engineer becomes available. Thus, there is a need for a mechanism whereby a third party, such as a customer or a value-added reseller (VAR) of the vendor's equipment or software, can create reports or modify existing reports.

SUMMARY OF THE INVENTION

The foregoing needs, and other needs and objects that will become apparent from the following description, are achieved in the present invention, which comprises, in one aspect, a method of generating a report that describes performance characteristics of a computer network based on RADIUS accounting information that is produced by the network in operation, comprising the steps of creating and storing archive data comprising a selected portion of the RADIUS accounting information; creating and storing configuration information that defines the report and comprises a report type identifier that is associated with one or more RADIUS attributes that identify data values in the archive data and that is associated with a generic report type; and one or more attribute values that specify bounds of ranges of the data values; retrieving and parsing the configuration information to create and store one or more buckets associated with the ranges of the data values for receiving data values falling within such ranges; reading the archive data and selectively storing its data values in the buckets based on the configuration information; and generating a report by displaying the values that are in the buckets.

According to one feature, creating and storing the configuration information comprises creating and storing configuration information that defines the report and comprises a report type identifier that is associated with one or more RADIUS attributes that identify data values in the archive data and that is associated with a generic report type; one or more attribute values that specify bounds of ranges of the data values; and an abbreviation of a name associated with the report; storing a label, which includes the abbreviation, in a section of the configuration information that identifies the bounds of ranges.

According to another feature, the step of generating a report comprises the step of generating a report by displaying the values that are in the buckets only when an attribute in the archive data indicates that an end of the report has been reached. Another feature is that the step of reading the archive data and selectively storing its data values further includes the step of rolling the data values in the buckets when a new time period is identified in the archive data.

According to another feature, the step of generating a report further comprises the step of creating and storing report data in the form of a matrix having rows corresponding to time periods and columns corresponding to customers, and wherein the step of reading the archive data and selectively storing its data values further includes the step of, when a new customer is identified in the archive data, creating a new column in the matrix and creating rows containing zero data from the starting time period up to the time period currently being processed.

In another feature, the step of reading the archive data and selectively storing its data values in associated buckets only when the data values are needed by the current report and its associated buckets. In still another feature, creating and storing configuration information comprises creating and storing configuration information that defines a plurality of reports, the configuration information comprising, for each of the plurality of reports: a report type identifier that is associated with one or more RADIUS attributes that identify data values in the archive data and that is associated with a generic report type; a time interval value that indicates a period of time to be covered by information in the report; and one or more category values that specify bounds of ranges of the data values. In a related feature, the configuration information includes one or more category values that specify bounds of ranges of the data values; and an abbreviation of a name associated with the report. Creating and storing the configuration information may involve a label, which includes the abbreviation, in a section of the configuration information that identifies the bounds of ranges.

According to another feature, the method further comprises the steps of receiving and storing non-RADIUS network accounting data; selectively archiving a portion of the non-RADIUS network accounting data in a non-RADIUS archive; storing a sub-portion of information from the non-RADIUS archive in the archive data, based on non-RADIUS archive configuration control information.

In another feature, creating and storing configuration information comprises creating and storing configuration information that defines a plurality of reports, the configuration information comprising, for each of the plurality of reports: a report type identifier that is associated with one or more RADIUS attributes that identify data values in the archive data and that is associated with a generic report type selected from among: a numeric value counting report type; a string value counting report type; and an accumulating report type.

The invention also encompasses a computer-readable medium, and a computer data signal embodied in a carrier wave, configured to carry out the foregoing steps.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which:

FIG. 1 is a block diagram of a computer system hardware arrangement that can be used to implement aspects of the invention;

FIG. 2 is a block diagram of a system in which embodiments can be used;

FIG. 3 illustrates an example of connection information that may be stored by an accounting server;

FIG. 4 illustrates report configuration control information that may be used as input to a report generator for defining a user-specified report;

FIG. 5 is a block diagram of a system in which embodiments can be used;

FIG. 6A depicts an example of a user-specified report;

FIG. 6B depicts another example of a user-specified report;

FIG. 6C depicts another example of a user-specified report;

FIG. 6D depicts another example of a user-specified report;

FIG. 6E depicts another example of a user-specified report;

FIG. 6F depicts another example of a user-specified report;

FIG. 7A is a flow diagram that illustrates steps involved in a method for generating user-specified reports;

FIG. 7B is a flow diagram that shows further steps in the method of FIG. 7A;

FIG. 7C is a flow diagram that shows further steps in the method of FIG. 7A.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

A method and apparatus for generating reports based on RADIUS accounting information from network systems is described. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the present invention.

FUNCTIONAL OVERVIEW

A method is provided in which reports of RADIUS accounting information are dynamically generated based on a set of report criteria that is submitted by a user. In particular, the method allows users to generate report data that is individually tailored to the users' specific needs.

FIG. 2 is a block diagram of a system 200 that includes one or more network access servers (NAS) 202a-d, an accounting server 204, a RADIUS archiver 206, a report generator 208, RADIUS accounting data 210, report archive data 212, archive configuration control information 214, report configuration control information 216 and report data 218.

Each of the network access servers 202a-d are computers, or one or more hardware or software components or processes that cooperate or execute in one or more computer systems. Each of network access servers 202a-d is configured to receive connection requests from clients that are attempting to access an associated network system. The connection requests generally represent dial-in requests that are typically made using one of the Internet's standard dial-in protocols, such as Point-to-Point Protocol (PPP) or the Serial Line Internet Protocol (SLIP). However, any type of connection may be made between a client and network access servers 202a-d.

Accounting server 204 is a computer, or one or more hardware or software components or processes that cooperate or execute in one or more computer systems. In one embodiment, accounting server 204 is an Authorization, Authentication and Accounting (AAA) server. When one of the network access servers 202a-d receives a connection request from a client, the network access server communicates with accounting server 204 to determine whether a connection should be established with the particular client. Thus, accounting server 204 is responsible for receiving connection requests from the network access servers 202a-d, determining whether the connection requests should be authorized, and for returning response messages to the network access servers 202a-d that indicate whether or not a connection should be established for the requesting client. The accounting server 204 provides an important control point that prevents over-subscription of the system and enables management to determine whether enough connections are available for actual throughput.

In addition to determining whether a particular request should be authorized, accounting server 204 maintains accounting information about the connections that are established with the network access servers 202a-d. In one embodiment, network access servers 202a-d operate as clients of the accounting server 204 and are responsible for passing connection information to the accounting server 204. This connection information is maintained by the accounting server 204 and provides a mechanism for monitoring the performance of the network system.

In a preferred embodiment, accounting server 204 communicates with network access servers 202a-d using the RADIUS Accounting protocol. In one embodiment, as RADIUS accounting information is received from the network access servers 202a-d, accounting server 204 periodically stores the information in the form of RADIUS accounting data 210. In one embodiment, RADIUS accounting data 210 is maintained in nonvolatile memory. The RADIUS accounting data 210 may be stored on the same machine as accounting server 204 or on a machine that is separate from accounting server 204. In a preferred embodiment, the accounting server 204 maintains the RADIUS accounting data 210 in a plurality of files, and each file is associated with one of the network access server 202a-d.

Archiver 206 is a computer, or one or more hardware or software components or processes that cooperate or execute in one or more computer systems. Archiver 206 is configured to read the RADIUS accounting data 210 and to store some or all of the information as report archive data 212. The RADIUS accounting data 210 may comprise a large volume of information. Accordingly, in one embodiment, archiver 206 functions as a filter to reduce the amount of information that is stored as report archive data 212. In this manner, the archiver 206 may filter out information that is not required for generating report data 218.

In one embodiment, archiver 206 stores report archive data 212 in one or more files. In a preferred embodiment, the report archive data 212 is stored in a plurality of separate files on a day-by-day basis by the RADIUS archiver 206. For example, in one embodiment, a separate file is created for storing the report archive data 212 that is generated during a particular day. The files may be maintained in a single directory, or in separate directories, in which each directory corresponds to a particular day.

In certain embodiments, a user or administrator can control the type of information that is stored in report archive data 212. For example, archive configuration control information 214 may be used by archiver 206 to control the set of RADIUS accounting data 210 that is stored in report archive data 212. How archive configuration control information 214 may used to determine and control what RADIUS accounting data 210 is stored as report archive data 212 is explained further below.

Report generator 208 is a computer, or one or more hardware or software components or processes that cooperate or execute in one or more computer systems. Report generator 208 is configured to read report archive data 212 and to dynamically generate report data 218 based on the particular needs of a user or administrator. In one embodiment, the report data 218 is maintained as a plurality of separate report files based on the particular information that is of interest to the user. In a preferred embodiment, report data 218 is stored as one or more comma-separated-value files (".csv files") to allow the information to be read or imported by other software. In another embodiment, report data 218 is stored in a database system and is accessible by a user through a database application program.

In certain embodiments, report configuration control information 216 is used by report generator 208 to determine the information that is to be stored as report data 218. How the report configuration control information 216 may be used to control the information that is stored as report data 218 is explained further below. Generally, report generator 208 is table driven, thereby providing flexibility for future reporting requirements. It accommodates reports of several generic types. The user may configure specific reports based on the generic types. The user may configure new reports involving different RADIUS accounting attributes if the new reports fall within one of the supported generic types.

STORING RADIUS ACCOUNTING DATA

In certain embodiments, network access servers 202a-d and accounting server 204 communicate using the RADIUS Accounting protocol. Table 1 represents a list of RADIUS Accounting attributes that may be included in the packets that are communicated between network access servers 202a-d and accounting server 204, and an attribute number that accounting server 204, in the preferred embodiment, associates with each of the attributes. Storage of RADIUS accounting information may be minimized by storing the associated attribute numbers rather than the attribute names.

                             TABLE 1
                   RADIUS ACCOUNTING ATTRIBUTES
              NUMBER           ATTRIBUTE
                1              User-Name
                2              User-Password
                3              CHAP-Password
                4              NAS-IP-Address
                5              NAS-Port
                6              Service-Type
                7              Framed-Protocol
                8              Framed-IP-Address
                9              Framed-IP-Netmask
                10             Framed-Routing
                11             Filter-Id
                12             Framed-MTU
                13             Framed-Compression
                14             Login-IP-Host
                15             Login-Service
                16             Login-TCP-Port
                18             Reply-Message
                19             Callback-Number
                20             Callback-Id
                22             Framed-Route
                23             Framed-IPX-Network
                24             State
                25             Class
                26             Vendor-Specific
                27             Session-Timeout
                28             Idle-Timeout
                29             Termination-Action
                30             Called-Station-Id
                31             Calling-Station
                32             NAS-Identifier
                33             Proxy-State
                34             Login-LAT-Service
                35             Login-LAT-Node
                36             Login-LAT-Group
                37             Framed-AppleTalk-Link
                38             Framed-AppleTalk-Network
                39             Framed-AppleTalk-Zone
                60             CHAP-Challenge
                61             NAS-Port-Type
                62             Port-Limit
                63             Login-LAT-Port

        [Reports]
        M                    MSE `Maximum Sessions Exceeded`
        S                    SBC `Sessions by Customer`
        T 5, 15, 60          DUR `Call Duration`
        T                    TIM `Connect Time`
        D =2, =11, =20       DIS `Disconnect Reason`
        R 2800, 5600, 9600   SPD `Data Rate`

• Inventors
  Hartmann, Charles L.; Clark, Glenwood Ray;
• Assignee
  Cisco Technology, Inc. (San Jose, CA)
• Published
  Apr-23-2002
• Current US Classes:
  707/10
  707/104.1
  707/4
  707/9
  709/225
  709/229
• Application #
  281754
• International Classes
  G06F 017/30
• Field of Search
  707/10 707/9 707/4 707/104 709/225 709/229 709/217 709/203
• Examiner
  Corrielus; Jean M.
• Agent
  Hickman Palermo Truong & Becker LLP
• US Patent References:
  5889958
  6070243
  6097719
  6151628
  6189096
  6205479
  6212561
  6233616
  6243749