Question: In a PCC architecture, how do a BBERF and a PCRF (visited or home) advertise support for Gxx specific Application after establishing a transport connection?
Option 1: By including the application identifier in the User-Name AVP of the Device-Watchdog-Request command.
Option 2: Through the use of a custom-built, non-standard protocol extension.
Option 3: Via the Acct-Application-Id AVP in the Accounting-Request command.
Option 4: By including the application identifier in the Auth-Application-Id AVP and the 3GPP Vendor-Id in the Vendor-Specific-Application-Id AVP of Capabilities-Exchange messages.
Explanation: This is correct because, as per the standard protocol initialization procedures between Diameter nodes (like BBERF and PCRF), advertising application support specifically for Gxx involves exchanging capability information. This is achieved by including the relevant application identifier and vendor ID within the Capabilities-Exchange messages, which are part of the Diameter Base Protocol. This process ensures both nodes are aware of each other’s supported applications, facilitating proper communication setup.