name: RAA
full_form: Re-Auth-Answer
context: The DCCA RAA message format is defined according to the Diameter Base Protocol in RFC 6733 [401] and DCCA specification in RFC 4006 [402]: <RAA> ::= < Diameter Header: 258, PXY > < Session-Id > { Result-Code } { Origin-Host } { Origin-Realm } [ User-Name ] [ Origin-State-Id ] [ Error-Message ] [ Error-Reporting-Host ] [ Failed-AVP ] *[ Redirect-Host ] [ Redirect-Host-Usage ] [ Redirect-Host-Cache-Time ] *[ Proxy-Info ] [ CC-Sub-Session-Id ] [ G-S-U-Pool-Identifier ] [ Service-Identifier ] [ Rating-Group ] *[ AVP ] Table 6.4.5.1 illustrates the basic structure of a Diameter Credit-Control Re-Auth-Answer message as used for online charging. Table 6.4.5.1: RAA message contents for online charging
description: The Re-Auth-Answer (RAA) is a Diameter message used in online charging for credit control re-authentication. It adheres to the Diameter Base Protocol and DCCA specification, carrying attributes like Result-Code, Origin-Host, and Session-Id.
explanation: The RAA is classified as a Message because it functions as a carrier of specific information between network entities during the online charging credit control re-authentication process, as defined by 3GPP TS 32.299.
section_title: 6.4.5Re-Auth-Answer message
biotag_Context: O,B-Protocol,B-Message,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,B-Protocol,O,O,B-Specification,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O
biotag_Description: O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O