X hits on this document

Word document

Meeting SA5#51, 22 - 26 Jan 2007, Seville, SPAIN - page 6 / 8

18 views

0 shares

0 downloads

0 comments

6 / 8

The OCS online charging function can send multiple concatenated PS Furnish Charging Information elements per online charging session in the Ro interface. The OCS online charging function can also send multiple concatenated PS Furnish Information Element per each online charged service data flow.

The total maximum of free format data is 160 octets per service so the total maximum of free format data per online session is n*160 octets, where n indicates the number of services activated per online session. .

In the OCS online charging function a PS online charging session shall be identified by the GGSN-C address and the ChargingId. In the GGSN, the PS online charging session and the PS offline charging session shall be identified by the same ChargingId. Therefore the ChargingId shall allow the GGSN to correlate an online charging session with an offline charging session. According TS23.203 [72] the service data flow shall be identified by the charging key and, optionally, the service identifier.

This procedure shall only apply when online and offline charging is performed simultaneously for the same session (PDP Context) or service. In any other case, the GGSN shall discard the additional charging information sent by the OCS in the Diameter Credit Control Credit-Control-Answer messages.

When the OCS sends session specific charging information, it must send the “PS-Furnish-Charging-Information” AVP at command level in the Credit-Control-Answer message. In this case, the information is added to the main body of the eG-CDR. When the OCS sends service specific charging information , it must send the “PS-Furnish-Charging-Information” AVP at service level in the Credit-Control-Answer message. In this case, the information is added to the specific service container in the eG-CDR.

The PS Furnish Charging Information AVP is described in TS 32.299 [50].

Next Modified Section

5.3.2.4Support of Failure Situations

In case the OCS fails the GGSN must support the Failure Handling procedure and Failover mechanism described in 3GPP TS 32.299 [50].

The Failure Handling Procedure affects the whole online session so in case FBC is enabled, the procedure shall affect all services activated during the PDP Context triggering the online charging session.

According to 3GPP TS 32.299 [50], timer Tx determines the maximum interval the GGSN shall wait for an answer to each credit control request sent to the OCS. In case FBC is enabled, it is possible that several concurrent Credit Control Request messages are triggered for the same online charging session. In this case, each Credit Control Request message shall reset the Tx timer. When Tx expires, GGSN shall execute the Failover and Failure Handling mechanisms according to the behaviour described in Annex B.

Three different actions are described in [402]. In PS domain GGSN shall support the following  actions when the failure handling mechanism is executed:

Terminate: The online session is finished. The associated PDP Context is released (ongoing sessions) or not established (new sessions). Failover for ongoing sessions is not supported. Failover for new sessions is always supported.

Retry&Terminate: The online session is finished. The associated PDP Context is released (ongoing sessions) or not established (new sessions). Failover for ongoing sessions is supported. Failover for new sessions is always supported.

Continue: The online session is finished. The associated PDP Context is established (new sessions) or not released (ongoing sessions). Failover for ongoing sessions is supported. Failover for new sessions is always supported. It shall be operator configurable to limit the maximum duration of the PDP Context in this situation.

In case the user is simultaneously online and offline charged, the failure situation must be registered in the eG-CDR. When the user is only online charged, the execution of the Failure Handling mechanism with value equal to Continue shall imply that a new eG-CDR is opened.

Document info
Document views18
Page views18
Page last viewedFri Dec 02 22:53:01 UTC 2016
Pages8
Paragraphs347
Words3429

Comments