RFC 3588:Diameter Base Protocol
RFC-Ref

accounting


Click on the red underlined text to get to the source

... Authentication, Authorization and Accounting (AAA) protocols such as TACACS ...
... per-packet confidentiality. In accounting, [RADACCT] assumes that replay protection is ...
... reliability varies between implementations. As described in [ACCMGMT], this is a major issue in accounting, where packet loss may translate directly into revenue loss. In order to ...
... Basic services necessary for applications, such as handling of user sessions or accounting All data delivered by the protocol is in the form of an AVP ...
... - Exchanging resource usage information, which MAY be used for accounting purposes, capacity planning, etc. - Relaying, proxying and redirecting of Diameter ...
... AAAREQ]. The base protocol may be used by itself for accounting purposes only, or it may be used with a Diameter application, such as Mobile IPv4 ...
... AVPs. At this time the focus of Diameter is network access and accounting applications. A truly generic AAA protocol used by many applications might provide functionality not provided by ...
... client generates Diameter messages to request authentication, authorization, and accounting services for the user. A Diameter ...
... base protocol specification for AAA, which includes support for accounting. The Mobile IPv4 and the NASREQ ...
... specification for Authentication, Authorization and Accounting. ...
... authentication/authorization applications - Creating new accounting applications - Application authentication procedures ...
... ABNF] grammar (see Section 3.2). If the Diameter application has accounting requirements, it MUST also specify the AVPs that are to be present in the Diameter Accounting messages ...
... accounting requirements, it MUST also specify the AVPs that are to be present in the Diameter Accounting messages (see Section 9.3). However, just because a new authentication application id is required, does not ...
... because a new authentication application id is required, does not imply that a new accounting application id is required. When possible, a new Diameter application ...
... Creating New Accounting Applications ...
... There are services that only require Diameter accounting. Such services need to define the AVPs ...
... services need to define the AVPs carried in the Accounting-Request (ACR)/ Accounting-Answer ...
... Accounting-Request (ACR)/ Accounting-Answer (ACA) messages, but do not need to define new command codes. An implementation MAY add arbitrary non-mandatory ...
... vendor-specific AVPs, without needing to define a new accounting application. Please refer to Section 11.1.1 for details. ...
... Diameter capability exchange. Every Diameter accounting application specification MUST have an IANA assigned Application Identifier ...
... Every Diameter implementation MUST support accounting. Basic accounting support is sufficient to handle any application that uses ...
... Diameter implementation MUST support accounting. Basic accounting support is sufficient to handle any application that uses the ACR/ACA ...
... AVP is defined as one which has the "M" bit set when sent within an accounting command, regardless of whether it is required or optional within the ABNF for ...
... regardless of whether it is required or optional within the ABNF for the accounting application. The creation of a new accounting ...
... accounting application. The creation of a new accounting application should be viewed as a last resort and MUST NOT be used unless a new command or additional mechanisms (e.g., application defined state machine ...
... ABNF. Within an accounting command, setting the "M" bit implies that a backend server (e.g., billing server) or the accounting ...
... accounting command, setting the "M" bit implies that a backend server (e.g., billing server) or the accounting server itself MUST understand the AVP in order to compute a correct bill. If the ...
... AVP is not relevant to the billing process, when the AVP is included within an accounting command, it MUST NOT have the "M" bit set, even if the "M" bit ...
... A DIAMETER base accounting implementation MUST be configurable to advertise supported accounting applications in order to prevent the ...
... DIAMETER base accounting implementation MUST be configurable to advertise supported accounting applications in order to prevent the accounting server from accepting accounting requests ...
... advertise supported accounting applications in order to prevent the accounting server from accepting accounting requests for unbillable services ...
... accounting applications in order to prevent the accounting server from accepting accounting requests for unbillable services. The combination of the home domain ...
... services. The combination of the home domain and the accounting application Id can be used in order to route the request to the ...
... application Id can be used in order to route the request to the appropriate accounting server. When possible, a new Diameter ...
... When possible, a new Diameter accounting application SHOULD attempt to reuse existing AVPs, in order to avoid defining multiple AVPs ...
... carry similar information. If the base accounting is used without any mandatory AVPs, new commands or additional mechanisms (e.g., application defined state machine ...
... commands or additional mechanisms (e.g., application defined state machine), then the base protocol defined standard accounting application Id (Section 2.4) MUST be used in ACR/ACA ...
... Authentication, Authorization and Accounting. Accounting ...
... Accounting. Accounting The act of collecting information on resource usage for the purpose of capacity planning, auditing, billing or cost ...
... allocation. Accounting Record An accounting record represents a summary of the resource ...
... Accounting Record An accounting record represents a summary of the resource consumption of a user over the entire session. Accounting ...
... accounting record represents a summary of the resource consumption of a user over the entire session. Accounting servers creating the accounting record may do so by processing interim ...
... session. Accounting servers creating the accounting record may do so by processing interim accounting events or accounting ...
... creating the accounting record may do so by processing interim accounting events or accounting events from several devices serving the same user. ...
... accounting record may do so by processing interim accounting events or accounting events from several devices serving the same user. ...
... authentication, authorization or accounting information. Broker ...
... authentication, authorization and accounting requests for a particular realm. By its very nature, a Diameter Server MUST support Diameter applications ...
... Diameter Server. Interim accounting An interim accounting message provides a snapshot of usage during ...
... Interim accounting An interim accounting message provides a snapshot of usage during a user's session. It is typically implemented in order to provide ...
... a user's session. It is typically implemented in order to provide for partial accounting of a user's session in the case of a device reboot or other network ...
... Real-time Accounting Real-time accounting ...
... Accounting Real-time accounting involves the processing of information on resource usage within a defined time window. Time constraints are ...
... session) or serially. These changes in sessions are tracked with the Accounting-Sub-Session-Id. Transaction ...


... The base Diameter protocol may be used by itself for accounting applications, but for use in authentication and authorization ...
... Clients MUST support the base protocol, which includes accounting. In addition, they MUST fully support each Diameter application that is needed to implement the client's service ...
... Diameter Servers MUST support the base protocol, which includes accounting. In addition, they MUST fully support each Diameter application that is needed to implement the intended service, e.g., ...
... transparent, and MUST transparently support the Diameter base protocol, which includes accounting, and all Diameter applications. ...
... proxies MUST support the base protocol, which includes accounting. In addition, they MUST fully support each Diameter application that is needed to implement proxied services, e.g., ...
... DIAMMIP] Diameter Base Accounting 3 Relay 0xffffffff ...
... AVPs containing keys and passwords should be considered sensitive. Accounting AVPs may be considered sensitive. Any AVP for which the P bit ...
... A home realm may also wish to check that each accounting request message corresponds to a Diameter response authorizing the session ...
... Diameter response authorizing the session. Accounting requests without corresponding authorization responses SHOULD be subjected to further scrutiny, as should accounting requests ...
... Accounting requests without corresponding authorization responses SHOULD be subjected to further scrutiny, as should accounting requests indicating a difference between the requested and provided service. ...
... establishing credit limits for intermediate realms and refusing to accept responses which would violate those limits. By issuing an accounting request corresponding to the authorization response, the local realm implicitly indicates its agreement ...
... provided by the local realm, then a DIAMETER_UNABLE_TO_COMPLY error message MUST be sent within the accounting request; a Diameter client ...
... perform MUST NOT substitute an alternate service, and then send accounting requests for the alternate service instead. ...


... application the message is applicable for. The application can be an authentication application, an accounting application or a vendor specific application. See Section 11.3 for the possible ...
... Abort-Session-Answer ASA 274 8.5.2 Accounting-Request ACR 271 9.7.1 Accounting-Answer ...
... Accounting-Request ACR 271 9.7.1 Accounting-Answer ACA 271 9.7.2 Capabilities-Exchange- CER ...


... Diameter AVPs carry specific authentication, accounting, authorization, routing ...
... Unsigned32 | M | P | | V | Y | Interim-Interval | | | | | | Accounting- 483 9.8.7 Enumerated | M | P | | V | Y | Realtime-Required | | | | | | Acct- 50 9.8.5 UTF8String | M | P | | V | Y | ...
... Multi-Session-Id | | | | | | Accounting- 485 9.8.3 Unsigned32 | M | P | | V | Y | Record-Number | | | | | | ...
... Unsigned32 | M | P | | V | Y | Record-Number | | | | | | Accounting- 480 9.8.1 Enumerated | M | P | | V | Y | Record-Type | | | | | | Accounting ...
... Accounting- 480 9.8.1 Enumerated | M | P | | V | Y | Record-Type | | | | | | Accounting- 44 9.8.4 OctetString| M | P | | V | Y | Session-Id ...
... Session-Id | | | | | | Accounting- 287 9.8.6 Unsigned64 | M | P | | V | Y | Sub-Session-Id ...


... AVP Code 259) is of type Unsigned32 and is used in order to advertise support of the Accounting portion of an application (see Section 2.4). The Acct-Application-Id MUST also be ...
... application (see Section 2.4). The Acct-Application-Id MUST also be present in all Accounting messages. Exactly one of the Auth- Application-Id and Acct-Application-Id AVPs ...


... DIAMETER_OUT_OF_SPACE 4002 A Diameter node received the accounting request but was unable to commit it to stable storage due to a temporary lack of space. ...


... authentication and authorization, and can optionally make use of accounting. The second only makes use of accounting. ...
... optionally make use of accounting. The second only makes use of accounting. When a service ...
... AVP, which is used in subsequent messages (e.g., subsequent authorization, accounting, etc) relating to the user's session. The Session-Id ...
... When a service only makes use of the Accounting portion of the Diameter protocol, even in combination with an application, the ...
... session termination messages are not used, since a session is signaled as being terminated by issuing an accounting stop message. ...
... Accounting Session State Machine ...
... The following state machines MUST be supported for applications that have an accounting portion or that require only accounting services. ...
... state machines MUST be supported for applications that have an accounting portion or that require only accounting services. The first state machine ...
... clients. See Section 9.7 for Accounting Command Codes and Section 9.8 for Accounting AVPs. ...
... See Section 9.7 for Accounting Command Codes and Section 9.8 for Accounting AVPs. The server side ...
... The server side in the accounting state machine depends in some cases on the particular application. The Diameter ...
... server side state machine requires the reception of accounting records in any order and at any time, and does not place any standards requirement on the processing of these records. ...
... Diameter specifications. Applications MAY define requirements on when to accept accounting records based on the used value of Accounting-Realtime-Required AVP ...
... requirements on when to accept accounting records based on the used value of Accounting-Realtime-Required AVP, credit limits checks, and so on. ...
... keeping track of the session state at the accounting server. Note that such tracking is incompatible with the ability to sustain long duration connectivity problems. Therefore, the use of this state machine ...
... duration connectivity problems. Therefore, the use of this state machine is recommended only in applications where the value of the Accounting-Realtime-Required AVP is DELIVER_AND_GRANT, and hence accounting ...
... Accounting-Realtime-Required AVP is DELIVER_AND_GRANT, and hence accounting connectivity problems are required to cause the serviced user to be disconnected. Otherwise, records produced by the client ...
... higher than the Acct_Interim_Interval value. Ts MAY be set to two times the value of the Acct_Interim_Interval so as to avoid the accounting session in the Diameter server to change to Idle state ...
... DIAMETER_LOOP_DETECTED in the Result-Code AVP of the Accounting Answer command. ...
... client received a non-transient failure notification in the Accounting Answer command. Note that the action 'Disconnect user/dev' MUST have an effect also ...
... authentication/authorization and accounting portions. The states PendingS, PendingI, PendingL, PendingE and PendingB stand ...
... The states PendingS, PendingI, PendingL, PendingE and PendingB stand for pending states to wait for an answer to an accounting request related to a Start, Interim, Stop, Event or buffered record, ...
... CLIENT, ACCOUNTING State Event Action New State ...
... Idle Client or device requests Send PendingS access accounting start req. ...
... Client or device requests Send PendingE a one-time service accounting event req ...
... record PendingS Successful accounting Open start answer received ...
... GRANT_AND_LOSE PendingS Failed accounting start answer Open received and realtime equal ...
... to GRANT_AND_LOSE PendingS Failed accounting start answer Disconnect Idle received and realtime not user/dev ...
... Open Interim interval elapses Send PendingI accounting interim record ...
... Open User service terminated Send PendingL accounting stop req. ...
... stop req. PendingI Successful accounting interim Open answer received ...
... not equal to GRANT_AND_LOSE PendingI Failed accounting interim Open answer received and realtime equal to GRANT_AND_LOSE ...
... equal to GRANT_AND_LOSE PendingI Failed accounting interim Disconnect Idle answer received and realtime user/dev not equal to GRANT_AND_LOSE ...
... stop record PendingE Successful accounting Idle event answer received ...
... space available PendingE Failed accounting event answer Idle received ...
... received PendingB Successful accounting answer Delete Idle received record ...
... PendingB Failure to send Idle PendingB Failed accounting answer Delete Idle received record ...
... received record PendingL Successful accounting Idle stop answer received ...
... space available PendingL Failed accounting stop answer Idle received ...
... SERVER, STATELESS ACCOUNTING State Event Action New State ...
... ------------------------------------------------------------- Idle Accounting start request Send Idle received, and successfully accounting ...
... Accounting start request Send Idle received, and successfully accounting processed. start ...
... answer Idle Accounting event request Send Idle received, and successfully accounting ...
... Idle Accounting event request Send Idle received, and successfully accounting processed. event answer ...
... Idle Interim record received, Send Idle and successfully processed. accounting interim answer ...
... answer Idle Accounting stop request Send Idle received, and successfully accounting ...
... Idle Accounting stop request Send Idle received, and successfully accounting processed stop answer ...
... processed stop answer Idle Accounting request received, Send Idle no space left to store accounting ...
... Idle Accounting request received, Send Idle no space left to store accounting records answer, Result-Code ...
... SPACE SERVER, STATEFUL ACCOUNTING State Event Action New State ...
... ------------------------------------------------------------- Idle Accounting start request Send Open received, and successfully accounting ...
... Accounting start request Send Open received, and successfully accounting processed. start ...
... Start Ts Idle Accounting event request Send Idle received, and successfully accounting ...
... Idle Accounting event request Send Idle received, and successfully accounting processed. event answer ...
... answer Idle Accounting request received, Send Idle no space left to store accounting ...
... Idle Accounting request received, Send Idle no space left to store accounting records answer, Result-Code ...
... Open Interim record received, Send Open and successfully processed. accounting interim answer, ...
... Restart Ts Open Accounting stop request Send Idle received, and successfully accounting ...
... Open Accounting stop request Send Idle received, and successfully accounting processed stop answer, Stop Ts ...
... Stop Ts Open Accounting request received, Send Idle no space left to store accounting ...
... Open Accounting request received, Send Idle no space left to store accounting records answer, Result-Code ...
... session without reference to any other information, and may be needed to correlate historical authentication information with accounting information. The Session-Id includes a mandatory portion and an implementation-defined ...
... Session-Id MAY be used for both the authorization and accounting commands of a given application. ...
... session. ACCOUNTING 4 When set, all accounting messages for this session ...
... ACCOUNTING 4 When set, all accounting messages for this session MUST NOT include the Destination-Host ...
... Destination-Host AVP, if known, MUST be present in all accounting messages for this session. ...
... re-authorization, session termination and accounting messages. Class AVPs ...
... Event-Timestamp (AVP Code 55) is of type Time, and MAY be included in an Accounting-Request and Accounting-Answer messages to record the time that the reported event occurred, in seconds since ...
... AVP Code 55) is of type Time, and MAY be included in an Accounting-Request and Accounting-Answer messages to record the time that the reported event occurred, in seconds since January 1, 1900 00:00 UTC ...


... Accounting ...
... This accounting protocol is based on a server directed model with capabilities for real-time delivery ...
... capabilities for real-time delivery of accounting information. Several fault resilience methods [ACCMGMT ...
... methods [ACCMGMT] have been built in to the protocol in order minimize loss of accounting data in various fault situations and under different assumptions about the capabilities of the used devices. ...
... The server directed model means that the device generating the accounting data gets information from either the authorization server (if contacted) or the accounting ...
... accounting data gets information from either the authorization server (if contacted) or the accounting server regarding the way accounting data shall be forwarded. This information includes accounting ...
... authorization server (if contacted) or the accounting server regarding the way accounting data shall be forwarded. This information includes accounting record ...
... accounting server regarding the way accounting data shall be forwarded. This information includes accounting record timeliness requirements ...
... As discussed in [ACCMGMT], real-time transfer of accounting records is a requirement, such as the need to perform credit limit checks and ...
... is a requirement, such as the need to perform credit limit checks and fraud detection. Note that batch accounting is not a requirement, and is therefore not supported by Diameter ...
... and is therefore not supported by Diameter. Should batched accounting be required in the future, a new Diameter application will need to be created ...
... Note, however, that even if at the Diameter layer accounting requests are processed one by one, transport protocols used under Diameter ...
... agents) uses the Acct-Interim-Interval and Accounting-Realtime-Required AVPs to control the operation of the Diameter ...
... AVP, when present, instructs the Diameter node acting as a client to produce accounting records continuously even during a session. Accounting-Realtime-Required ...
... accounting records continuously even during a session. Accounting-Realtime-Required AVP is used to control the behavior of the client ...
... AVP is used to control the behavior of the client when the transfer of accounting records from the Diameter client ...
... The Diameter accounting server MAY override the interim interval or the realtime requirements by including the Acct-Interim-Interval ...
... requirements by including the Acct-Interim-Interval or Accounting-Realtime-Required AVP in the Accounting-Answer message. ...
... Accounting-Realtime-Required AVP in the Accounting-Answer message. When one of these AVPs is present, the latest value received SHOULD ...
... When one of these AVPs is present, the latest value received SHOULD be used in further accounting activities for the same session. ...
... authorization messages from the Home AAA server MUST collect accounting information for the session. The Accounting-Request ...
... accounting information for the session. The Accounting-Request message is used to transmit the accounting information to the Home ...
... session. The Accounting-Request message is used to transmit the accounting information to the Home AAA server, which MUST reply with the Accounting-Answer ...
... accounting information to the Home AAA server, which MUST reply with the Accounting-Answer message to confirm reception. The Accounting-Answer message includes the ...
... AAA server, which MUST reply with the Accounting-Answer message to confirm reception. The Accounting-Answer message includes the Result-Code AVP ...
... Result-Code AVP, which MAY indicate that an error was present in the accounting message. A rejected Accounting-Request message MAY cause the user's session ...
... AVP, which MAY indicate that an error was present in the accounting message. A rejected Accounting-Request message MAY cause the user's session to be terminated, depending on the value of the ...
... the user's session to be terminated, depending on the value of the Accounting-Realtime-Required AVP received earlier for the session in ...
... Each Diameter Accounting protocol message MAY be compressed, in order to reduce network bandwidth usage. If IPsec ...
... Service-Specific AVPs that MUST be present in the Accounting-Request message in a section entitled "Accounting AVPs". The application ...
... AVPs that MUST be present in the Accounting-Request message in a section entitled "Accounting AVPs". The application MUST assume that the AVPs described in this document will be present ...
... MUST assume that the AVPs described in this document will be present in all Accounting messages, so only their respective service-specific AVPs ...
... agents or related off-line processing systems MUST detect duplicate accounting records caused by the sending of same record to several servers and duplication of messages ...
... in transit. This detection MUST be based on the inspection of the Session-Id and Accounting-Record-Number AVP pairs. Appendix C discusses duplicate detection needs and implementation issues. ...
... Diameter clients MAY have non-volatile memory for the safe storage of accounting records over reboots or extended network failures, network ...
... partitions, and server failures. If such memory is available, the client SHOULD store new accounting records there as soon as the records are created and until a positive acknowledgement of their ...
... client MUST starting sending the records in the non-volatile memory to the accounting server with appropriate modifications in termination cause, session length, and other relevant information in ...
... A further application of this protocol may include AVPs to control how many accounting records may at most be stored in the Diameter client ...
... The client SHOULD NOT remove the accounting data from any of its memory areas before the correct Accounting-Answer has been received. ...
... remove the accounting data from any of its memory areas before the correct Accounting-Answer has been received. The client MAY remove ...
... client MAY remove oldest, undelivered or yet unacknowledged accounting data if it runs out of resources such as memory. It is an implementation dependent matter for the client to accept new sessions ...
... Accounting Records ...
... In all accounting records, the Session-Id AVP MUST be present; the ...
... authentication purposes. Different types of accounting records are sent depending on the actual type of accounted service and the authorization ...
... service and the authorization server's directions for interim accounting. If the accounted service is a one-time event, meaning that the start ...
... one-time event, meaning that the start and stop of the event are simultaneous, then the Accounting-Record-Type AVP MUST be present and set to the value EVENT_RECORD. ...
... INTERIM_RECORD. If the authorization server has not directed interim accounting to be enabled for the session, two accounting records MUST ...
... accounting to be enabled for the session, two accounting records MUST be generated for each service of type session ...
... session. When the initial Accounting-Request for a given session is sent, the Accounting- ...
... Accounting-Request for a given session is sent, the Accounting- Record-Type AVP MUST be set to the value START ...
... AVP MUST be set to the value START_RECORD. When the last Accounting-Request is sent, the value MUST be STOP_RECORD. If the authorization ...
... If the authorization server has directed interim accounting to be enabled, the Diameter client ...
... Diameter client MUST overwrite any previous interim accounting records that are locally stored for delivery, if a new record is ...
... session. A particular value of Accounting-Sub-Session-Id MUST appear only in one sequence of accounting records from a DIAMETER ...
... A particular value of Accounting-Sub-Session-Id MUST appear only in one sequence of accounting records from a DIAMETER client, except for ...
... the purposes of retransmission. The one sequence that is sent MUST be either one record with Accounting-Record-Type AVP set to the value EVENT_RECORD, or several records starting ...
... Correlation of Accounting Records ...
... Session-Id AVP to identify sessions. Accounting messages MAY use a different Session-Id from that sent in ...
... authorization messages. Specific applications MAY require different a Session-ID for accounting messages. However, there are certain applications that require multiple ...
... However, there are certain applications that require multiple accounting sub-sessions. Such applications would send messages with a constant Session-Id ...
... a constant Session-Id AVP, but a different Accounting-Sub-Session-Id AVP. In these cases, correlation is performed using the Session-Id ...
... It is important to note that receiving a STOP_RECORD with no Accounting-Sub-Session-Id AVP when sub-sessions were originally used ...
... Acct-Multi-Session-Id AVP, which the access device MUST include in all subsequent accounting messages. The Acct-Multi-Session-Id ...
... Accounting Command-Codes ...
... Command-Code values that MUST be supported by all Diameter implementations that provide Accounting services. ...
... Accounting-Request ...
... The Accounting-Request (ACR) command, indicated by the Command-Code ...
... Diameter node, acting as a client, in order to exchange accounting information with a peer. ...
... The AVP listed below SHOULD include service specific accounting AVPs, as described in Section 9.3. ...
... { Destination-Realm } { Accounting-Record-Type } { Accounting-Record-Number } ...
... { Accounting-Record-Type } { Accounting-Record-Number } [ Acct-Application-Id ] ...
... [ User-Name ] [ Accounting-Sub-Session-Id ] [ Acct-Session-Id ] ...
... [ Acct-Interim-Interval ] [ Accounting-Realtime-Required ] [ Origin-State-Id ] ...
... Accounting-Answer ...
... The Accounting-Answer (ACA) command, indicated by the Command-Code ...
... field set to 271 and the Command Flags' 'R' bit cleared, is used to acknowledge an Accounting-Request command. The Accounting-Answer command contains the same Session-Id ...
... bit cleared, is used to acknowledge an Accounting-Request command. The Accounting-Answer command contains the same Session-Id and includes the usage AVPs ...
... receipt of these AVPs in an end-to-end fashion. If the Accounting- Request was protected by end-to-end security, then the corresponding ...
... Diameter Server, known as the home Diameter Server, SHOULD respond with the Accounting-Answer command. One of Acct-Application-Id ...
... The AVP listed below SHOULD include service specific accounting AVPs, as described in Section 9.3. ...
... { Origin-Realm } { Accounting-Record-Type } { Accounting-Record-Number } ...
... { Accounting-Record-Type } { Accounting-Record-Number } [ Acct-Application-Id ] ...
... [ User-Name ] [ Accounting-Sub-Session-Id ] [ Acct-Session-Id ] ...
... [ Acct-Interim-Interval ] [ Accounting-Realtime-Required ] [ Origin-State-Id ] ...
... Accounting AVPs ...
... This section contains AVPs that describe accounting usage information related to a specific session. ...
... Accounting-Record-Type AVP ...
... The Accounting-Record-Type AVP (AVP Code 480) is of type Enumerated ...
... AVP (AVP Code 480) is of type Enumerated and contains the type of accounting record being sent. The following values are currently defined for the Accounting-Record-Type AVP ...
... and contains the type of accounting record being sent. The following values are currently defined for the Accounting-Record-Type AVP: ...
... EVENT_RECORD 1 An Accounting Event Record is used to indicate that a one-time event has occurred (meaning that the start and end of the event ...
... START_RECORD 2 An Accounting Start, Interim, and Stop Records are used to indicate that a service ...
... indicate that a service of a measurable length has been given. An Accounting Start Record is used to initiate an accounting session ...
... Accounting Start Record is used to initiate an accounting session, and contains accounting ...
... accounting session, and contains accounting information that is relevant to the initiation of the session. ...
... INTERIM_RECORD 3 An Interim Accounting Record contains cumulative accounting information for an existing accounting ...
... INTERIM_RECORD 3 An Interim Accounting Record contains cumulative accounting information for an existing accounting session ...
... Accounting Record contains cumulative accounting information for an existing accounting session. Interim Accounting ...
... accounting session. Interim Accounting Records SHOULD be sent every time a re-authentication or re-authorization ...
... STOP_RECORD 4 An Accounting Stop Record is sent to terminate an accounting session ...
... STOP_RECORD 4 An Accounting Stop Record is sent to terminate an accounting session and contains cumulative accounting ...
... accounting session and contains cumulative accounting information relevant to the existing session. ...
... client uses information in this AVP to decide how and when to produce accounting records. With different values in this AVP, service ...
... AVP, service sessions can result in one, two, or two+N accounting records, based on the needs of the home-organization. The following accounting ...
... accounting records, based on the needs of the home-organization. The following accounting record production behavior is directed by the inclusion of this AVP: ...
... is the nominal interval between these records in seconds. The Diameter node that originates the accounting information, known as the client, MUST produce the first INTERIM_RECORD record roughly ...
... The client MUST ensure that the interim record production times are randomized so that large accounting message storms are not created either among records or around a common service ...
... Accounting-Record-Number AVP ...
... The Accounting-Record-Number AVP (AVP Code 485) is of type Unsigned32 ...
... AVPs are globally unique, the combination of Session-Id and Accounting- Record-Number AVPs is also globally unique, and can be used in ...
... Record-Number AVPs is also globally unique, and can be used in matching accounting records with confirmations. An easy way to produce unique numbers is to set the value to 0 for records of type EVENT_RECORD and START ...
... Session-Id AVP is used to link together multiple related accounting sessions, where each session ...
... Diameter server in an authorization answer, and MUST be used in all accounting messages for the given session. ...
... Accounting-Sub-Session-Id AVP ...
... The Accounting-Sub-Session-Id AVP (AVP Code 287) is of type ...
... AVP Code 287) is of type Unsigned64 and contains the accounting sub-session identifier. The combination of the Session-Id ...
... AVP implies no sub-sessions are in use, with the exception of an Accounting-Request whose Accounting-Record-Type is set to STOP_RECORD. A STOP_RECORD ...
... sessions are in use, with the exception of an Accounting-Request whose Accounting-Record-Type is set to STOP_RECORD. A STOP_RECORD message with no Accounting-Sub-Session-Id AVP ...
... whose Accounting-Record-Type is set to STOP_RECORD. A STOP_RECORD message with no Accounting-Sub-Session-Id AVP present will signal the termination of all sub-sessions ...
... Accounting-Realtime-Required AVP ...
... The Accounting-Realtime-Required AVP (AVP Code 483) is of type ...
... the Diameter client or in the Accounting-Answer from the accounting server. The client ...
... Diameter client or in the Accounting-Answer from the accounting server. The client uses information in this AVP ...
... client uses information in this AVP to decide what to do if the sending of accounting records to the accounting server has been temporarily prevented due to, for instance, a network ...
... AVP to decide what to do if the sending of accounting records to the accounting server has been temporarily prevented due to, for instance, a network problem. ...
... service MUST only be granted as long as there is a connection to an accounting server. Note that the set of alternative accounting servers are treated as one server in this sense. Having to move ...
... connection to an accounting server. Note that the set of alternative accounting servers are treated as one server in this sense. Having to move the accounting ...
... accounting servers are treated as one server in this sense. Having to move the accounting record stream to a backup server is not a reason to discontinue the service ...


... The table in this section is limited to the non-accounting Command Codes defined in this specification. ...
... Acct-Interim- |0 |0 |0 |0 |0 |0 |0-1|0 |0 |0 |0 |0 | Interval | | | | | | | | | | | | | Accou