rfc2924.txt

radius服务器

   The RTFM QoS attributes are:

        98      QoSService
        99      QoSStyle
       100      QoSRate
       101      QoSSlackTerm
       102      QoSTokenBucketRate
       103      QoSTokenBucketSize
       104      QoSPeakDataRate
       105      QoSMinPolicedUnit
       106      QoSMaxPolicedUnit

   The RSVP MIB contains a large number of objects, arranged within the
   following sections:

       General Objects
       Session Statistics Table
       Session Sender Table
       Reservation Requests Received Table
       Reservation Requests Forwarded Table
       RSVP Interface Attributes Table
       RSVP Neighbor Table

   The Session tables contain information such as the numbers of senders
   and receivers for each session, while the Reservation Requests tables
   contain details of requests handled by the RSVP router.  There are
   too many objects to list here, but many of them could be used for
   accounting.  In particular, RSVP Requests contain the specification
   of the service parameters requested by a user; these, together with
   the actual usage data for the connection make up an accounting record
   for that usage.

5.  ITU-T Documents

5.1.  Q.825: Call Detail Recording

   ITU-T Recommendation Q.825 specifies how CDRs (Call Detail Records)
   are produced and managed in Network Elements for POTS, ISDN and IN
   (Intelligent Networks).

   Uses of Call Detail information for various purposes are discussed.



Brownlee & Blount            Informational                     [Page 13]

RFC 2924        Accounting Attributes and Record Formats  September 2000


   Each call produces one or more records describing events that
   occurred during the life of a call.  Data may be produced in real
   time (single CDRs), near real-time (blocks of CDRs), or as batch
   files of CDRs.

   The information model for Call Detail Recording is formally described
   in terms of an Entity-Relationship model, and an object model
   specified in terms of GDMO templates (Guidelines for the Definition
   of Managed Objects).  Note that this model includes the ways in which
   CDRs are transported from the (NE) Network Element where they are
   generated to the OS (Operations System) where they are used.

5.2.  Q.825 Attributes

   The following attributes are defined.  The explanations given are
   very brief summaries only, see [Q-825] for the complete text.

   1  accessDelivery
        Indicates that the call was delivered to the called subscriber

   2  accountCodeInput
        Account code (for billing), supplied by subscriber.

  78  additionalParticipantInfo
        (No details given)

   5  b-PartyCategory
        Subscriber category for called subscriber.

   4  bearerService
        Bearer capability information (only for ISDN calls).

  13  cDRPurpose
        Reason for triggering this Call Data Record.

  70  callDetailDataId
        Unique identifier for the CallDetailData object.

  79  callDuration
        Duration of call

   6  callIdentificationNumber
        Identification number for call; all records produced for this
        call have the same callIdenfificationNumber.

  73  callStatus
        Identifies whether the call was answered or not.




Brownlee & Blount            Informational                     [Page 14]

RFC 2924        Accounting Attributes and Record Formats  September 2000


   9  calledPartyNumber
        Telephone number of the called subscriber (may be a
        "diverted-to" or "translated" number.

   7  callingPartyCategory
        Calling subscriber category.

   8  callingPartyNumber
        Telephone number of the calling party.

  10  callingPartyNumberNotScreened
        An additional, user-provided (not screened) number to the
        calling party.

  11  callingPartyType
        Calling subscriber type.

  74  carrierId
        Carrier ID to which the call is sent.

  12  cause
        Cause and location value for the termination of the call.

  14  chargedDirectoryNumber
        Charged directory number (where the charged participant
        element can't indicate the number).

  16  chargedParticipant
        Participant to be charged for the usage.

  15  chargingInformation
        Charging information generated by a Network Element which is
        capable of charging.

  17  configurationMask
        Time consumption, e.g. from B-answer to termination time,
        between partial call records, etc.

  18  conversationTime
        Time consumption from B-answer to end of call.

  19  creationTriggerList
        List of trigger values which will create Call Detail data
        objects.

  75  dPC
        Destination point code (for analysis purposes).




Brownlee & Blount            Informational                     [Page 15]

RFC 2924        Accounting Attributes and Record Formats  September 2000


  20  dataValidity
        Indicates that the NE is having problems, contents of the
        generated Call Detail record is not reliable.

  23  durationTimeACM
        Time consumption from seizure until received ACM.

  21  durationTimeB-Answer
        Time consumption from seizure until B-answer.

  22  durationTimeNoB-Answer
        Time from seizure to termination when no B-answer was
        received.

  25  exchangeInfo
        Identity of exchange where Call Detail record was generated.

  26  fallbackBearerService
        Fallback bearer capability information for a call.

  27  glare
        Indicates if a glare condition was encountered.

  31  iNServiceInformationList
        Contains information about the use of IN (Intelligent Network)
        services.

  32  iNSpecificInformation
        Contains information about the use of one IN service.

  33  iSUPPreferred
        Indicate whether an ISUP preference was requested.

  28  immediateNotificationForUsageMetering
        Indicates that the Call Detail records requires
        immediate data transfer to the Operations System.

  34  maxBlockSize
        Maximum number of Call Detail records in a block.

  35  maxTimeInterval
        Maximum latency allowable for near-real-time Call Detail
        data delivery.

  36  networkManagementControls
        Indicates which Traffic Management Control has affected
        the call.




Brownlee & Blount            Informational                     [Page 16]

RFC 2924        Accounting Attributes and Record Formats  September 2000


  37  networkProviderId
        Indicates the Network Provider for whom the CDR is generated.

  76  oPC
        Originating point code for a failed call (for analysis
        purposes).

  38  operatorSpecific1AdditionalNumber
  40  operatorSpecific2AdditionalNumber
  42  operatorSpecific3AdditionalNumber
        Operator-defined additional participant information.

  39  operatorSpecific1Number
  41  operatorSpecific2Number
  43  operatorSpecific3Number
        Operator-defined participant information.

  44  originalCalledNumber
        Telephone number of the original called party.

  45  partialGeneration
        Included if the CDR (Call Detail record) output is partial.
        Such CDRs have a field indicating their partial record number.

  77  participantInfo
        (No details given).

  46  percentageToBeBilled
        Percentage to be billed when normal billing rules are
        not to be followed.

  47  periodicTrigger
        Defines the intervals at which the CDR file should be created.

  48  personalUserId
        Internationally unique personal User Identity (for UPT calls).

  49  physicalLineCode
        Identifies the call subscriber's physical line.

  50  progress
        Describes an event which occurred during the life of a call.

  51  queueInfo
        Used to record usage of queueing resources with IN calls.






Brownlee & Blount            Informational                     [Page 17]

RFC 2924        Accounting Attributes and Record Formats  September 2000


  52  receivedDigits
        The digits dialed by the subscriber.  (Normally only included
        for customer care purposes).

  53  recordExtensions
        Information elements added by network operators and/or
        manufacturers in addition to the standard ones above.

6.  Other Documents

6.1.  TIPHON: ETSI TS 101 321

   TIPHON [TIPHON] is an XML-based protocol, carried by HTTP, which
   handles accounting and authorization requests and responses.

   The following are elements selected from TIPHON's DTD that are used
   for accounting.

   <!ELEMENT Currency (#PCDATA)> <!ELEMENT Amount (#PCDATA)>
       Identifies a numeric value.  Expressed using the period (.) as a
       decimal separator with no punctuation as the thousands separator.

   <!ELEMENT CallId (#PCDATA)>
       Contains a call's H.323 CallID value, and is thus used to
       uniquely identify individual calls.

   <!ELEMENT Currency (#PCDATA)>
       Defines the financial currency in use for the parent element.

   <!ELEMENT DestinationInfo type ( e164 | h323 | url | email |
                                    transport | international |
                                    national | network | subscriber |
                                    abbreviated | e164prefix )
       Gives the primary identification of the destination for a call.

   <!ELEMENT Increment (#PCDATA)>
       Indicates the number of units being accounted.

   <!ELEMENT Service EMPTY>
       Indicates a type of service being priced, authorized, or
       reported.  An empty Service element indicates basic Internet
       telephony service, which is the only service type defined by
       V1.4.2 of the specification.  The specification notes that "Later
       revisions of this standard are expected to specify more enhanced
       service definitions to represent quality of service,
       availability, payment methods, etc."





Brownlee & Blount            Informational                     [Page 18]

RFC 2924        Accounting Attributes and Record Formats  September 2000


   <!ELEMENT DestinationInfo type ( e164 | h323 | url | email |
                                    transport | international |
                                    national | network | subscriber |
                                    abbreviated | e164prefix)
       Gives the primary identification of the source of a call.


   <!ELEMENT Timestamp (#PCDATA)>
       A restricted form of [ISO-DATE] that indicates the time at which
       the component was generated.

   <!ELEMENT TransactionId (#PCDATA)>