Content for TS 23.203 Word version: 19.0.0

0… 4… 5… 6… 6.1.4… 6.1.7… 6.1.10… 6.1.17… 6.2… 6.2.2… 6.2.3… 6.3 6.4… 6.8… 7… 7.3… 7.4… 7.7… 7.7.3… 7.8… A… A.4… D… P… P.4.2.4… P.7… P.7.5… P.8 Q… S… S.7… S.8.8 T…

S.8.8 Procedures AAA based charging using accounting signalling

S.8.8 Procedures AAA based charging using accounting signalling p. 258

S.8.8.0 General p. 258

This clause describes the AAA-based charging. The basic assumption is that B interface is not modified.

S.8.8.1 Charging Session Initiation p. 259

This procedure is performed for initiation of charging session

Copy of original 3GPP image for 3GPP TS 23.203, Fig. S.8.8.1: AAA-based Charging Session Initiation

Figure S.8.8.1: AAA-based Charging Session Initiation
(⇒ copy of original 3GPP image)

The steps included in Block A and B are mutually exclusive.

Step 1.

The 3GPP UE EAP-based authentication or BBF Fixed device authentication is performed.

Step A.1.

If AAA-based accounting applies, the 3GPP UE/BBF device is successfully authenticated and this triggers the interaction with the OCS system. This step is outside the 3GPP scope.

Step A.2.

The Accounting Interworking Function that will activate the online-charging session, and provide relevant input information for the OCS decision. i.e. subscriber identifier and charging keys obtained in step A.1.

Step A.3.

If online charging is applicable, the OCS provides the possible credit information to the Accounting Interworking Function and may provide re-authorisation triggers for each of the credits.

Step 2.

If PCC is supported, the IP-CAN session establishment procedure may be established as define in clause S.7.2. The steps from 1 to 14 defined in clause 7.2 are performed with the following exception:

Steps 9 - 10 are performed only if TDF based accounting is supported and AAA-based accounting is not supported.
Steps 13 - 14 are performed only if PCEF accounting is supported and AAA-based accounting is not supported.

Step B.1.

If AAA-based accounting applies, the start of accounting session is triggered in BBF AAA. This step is out of the scope of 3GPP specifications.

Step B.2.

The same step as step A.1

Step B.3.

The same step as step A.2

Step 3.

The IP-CAN session establishment as defined in clause 7.2 steps from 15 to 17 are performed.

S.8.8.2 Charging Session Modification p. 260

This procedure is performed for updating the charging information, such as the available quota.

Copy of original 3GPP image for 3GPP TS 23.203, Fig. S.8.8.2: AAA-based Charging Session modification

Figure S.8.8.2: AAA-based Charging Session modification
(⇒ copy of original 3GPP image)

Step 1.

The BNG can sent a RADIUS-Start accounting message or a RADIUS-Intermediate-Accounting message.

Step 2.

When the Accounting Interworking Function receives the message, it determines if it is required to update the accounting information which triggers an interaction with the OCS.

Step 3.

The Accounting Interworking Function may contact the OCS to request credit for new charging keys and/or to issue final report and return remaining credit for charging keys no longer active, i.e. when the accounting session is terminated.

Step 4.

The OCS may instruct the Accounting Interworking Function on the further handling of the session (terminate, continue, etc), provide credit information (possibly with re-authorisation trigger), and/or acknowledge the credit report.

S.8.8.3 Charging Session Termination p. 261

S.8.8.3.1 Charging Session Termination BNG-initiated p. 261

This procedure is performed when BNG send a stop accounting message to the Accounting Interworking Function, for example the IP-CAN session termination procedure is initiated by PCRF or when Subscriber IP session terminated (for example when the 3GPP UE disassociates from the fixed broadband network, the RG is switched off, etc.).

Copy of original 3GPP image for 3GPP TS 23.203, Fig. S.8.8.3.1-1: AAA-based Charging Session Termination

Figure S.8.8.3.1-1: AAA-based Charging Session Termination
(⇒ copy of original 3GPP image)

Step 1.

The BNG determines that the Subscriber IP session is terminated (e.g. the device has left the fixed broadband network) and consequently a PCEF-Initiated IP-CAN session termination is initiated or it shall be terminated, when PCRF-Initiated IP-CAN session termination procedure is performed.

Step 2.

The BNG send a RADIUS-Stop-accounting message to the ACC_If. This step is outside the scope of 3GPP specifications.

Step 3.

The Accounting Interworking Function determines that the Accounting Session shall be terminated.

Step 4.

The Accounting Interworking Function shall issue the final reports and return the remaining credit to the OCS.

Step 5.

The OCS acknowledges the credit report and terminates the online charging session.