A.3 User terminating AOC service

24.6473GPPAdvice Of Charge (AOC) using IP Multimedia (IM) Core Network (CN) subsystemRelease 17TS

A.3.1 AOC-S

A.3.1.1 AOC-S with AOC information during session set-up

Figure A.3.1.1: Charging info during session set-up on the terminating side

General

The AOC information is provided for every call. This is provisioned in the AS. The AOC information is sent to the terminal in an INVITE request. Since this is a service that is charged an acknowledgement is required to ensure that the charging info is transferred.

Call flows

1-5 The call is initiated by UE-A by sending an INVITE request. The Request URI will include the URI of UE-B. The INVITE request is routed to the Originating AS and the Terminating AS. The INVITE request will indicate that 100rel extension is supported.

6-7 The Terminating AS will include the charging info in the INVITE request sent to the UE-B.

8-28 UE-B sends a reliable provisional response to indicate that INVITE request is being processed.

29-35 UE-B answers with a 200 (OK) response (to the INVITE request) and sends it to UE-A.

36-42 UE-A sends an ACK request to acknowledge the 200 (OK) response (to the INVITE request) and the session is established successfully.

A.3.1.2 AOC-S with AOC information in INFO messages

Figure A.3.1.2: Charging info during the communication (terminating)

This can be a continuation of figure A.3.1.1.

General

The AOC information is provided to the UE in the content body of a mid-dialog request forwarded by the AS or an INFO request generated by the AS, if the charging rates change during the communication.

Call flows

1-4. When the charging rate changes, an INFO request is send from the terminating AS to UE-B. The AOC information is included in the INFO request.

A.3.2 AOC-D

Figure A.3.2.1: Charging info during the call (terminating)

This can be a continuation of figure A.3.1.1.

General

The AOC information is provided to the UE in the content body of a mid-dialog request or mid-dialog response forwarded by the terminating AS, or an INFO message generated by the terminating AS. The charing information indicates a cumulative charge incurred so far for the communication.

Call flows

1-4 In order to send an update on the cumulative charge incurred so far, an INFO request is send from the terminating AS to UE-B. The AOC information is included in the INFO request.

A.3.3 AOC-E

Calling party clears

Figure A.3.3.1: Calling party clears

The AOC information is provided for every communication after the communication has finished. This is provisioned in the AS. The AOC information is sent to the terminating user in the BYE request which is originated from UE-A.

Call Flow

The communication has been set up as a normal communication.

1-5 UE-A generates a BYE request to terminate the session, which is routed to the UE-B. When the Terminating AS receives the BYE request, it adds the AOC information.

6-10 UE-B sends a 200 (OK) response towards UE-A.

Called party clears

Figure A.3.3.2: Called party clears

The AOC information is provided for every communication after the communication has finished. This is provisioned in the AS. The charging info is sent to the terminating user in the 200 (OK) response, which is originated from UE-A.

Call Flow

The communication has been set-up as a normal communication.

1-5 UE-B generates a BYE request to terminate the session, which is routed to UE-A.

6-.10 UE-A sends a 200 (OK) response towards UE-B. When the Terminating AS receives the 200 (OK) response, it adds the AOC information.

Annex B (informative):
Example of Filter Criteria

This annex provides an example of a filter criterion that triggers SIP requests that are subject to initial filter criteria evaluation.

An example of an IFC when the AOC service is active at the originating S-CSCF is:

– Method: INVITE.

Annex C (normative):
Charging Information Elements