1

Title: eHRPD offline charging proposal

Sources: China Telecom

Contact: CT: Peirong Xie(xiepr@gsta.com), Wenyi Li(liwenyi@gsta.com) ZTE: Rajesh Bhalla (rabhalla@zteusa.com) Mao Yuxin (mao.yuxin@zte.com.cn) Qualcomm ： Jun wang （ jwang@qualcomm.com） Alcatel-Lucent:Mike Dolan (mike.dolan@alcatel-lucent.com)

Abstract: Charging interfaces and procedures are not defined clearly in X.S0057. This contribution proposes two proposals for how to resolve this issue.

Recommendation: Discuss and suggest to adopt Option 2 or Option 3

Contributing companies grant a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner's name any Organizational Partner's standards publication even though it may include all or portions of this contribution; and at the Organizational Partner's sole discretion to permit others to reproduce in whole or in part such contribution or the resulting Organizational Partner's standards publication. Contributing companies are also willing to grant licenses under such contributor copyrights to third parties on reasonable, non-discriminatory terms and conditions for purpose of practicing an Organizational Partner’s standard which incorporates this contribution.This document has been prepared by Contributing companies to assist the development of specifications by 3GPP2. It is proposed to the Committee as a basis for discussion and is not to be construed as a binding proposal on contributors . Contributing companies specifically reserve the right to amend or modify the material contained herein and to any intellectual property of contributors other than provided in the copyright statement above.

2

Background In X.S0057-0 3.0, HSGW has charging function

described as following: “Accounting functionality is provided by the HSGW and the P-

GW. The BBERF function in the HSGW shall collect accounting information for each UE i.e., the amount of data transmitted in uplink and downlink directions. The accounting related functionality provided by the HSGW is aligned with the accounting functionality defined for the S-GW in TS 23.401[19] . The charging functions in the HSGW, with associated interfaces shall be supported as specified in TS 32.240 [32] . The behavior of the charging functions in eHRPD EPC domain, the reporting of the chargeable events, and creation of the CDRs shall be as specified in TS 32.240 [32] and TS 32.251 [33] .”

3

Background （ cont. ） 3GPP TS32.240 define the logical offline charging

architecture.

CN Domain

Service element

Sub - system

Billing Domain

R f G a B x

C

T

F

C

D

F

C

G

F

3GPP network

Rf interface using diameter protocol

Ga interface using GTP’ protocol

SGW includes CTF and CDF logical functions and supports Ga charging interface

4

Problem statement and proposals

Issue:

X.S0057 only defines the skeleton of charging architecture for HSGW, but doesn’t describe exactly the interfaces/protocols and procedures which should be supported in HSGW. Additionally, there is no CG function explicitly mentioned in eHRPD.

Proposals:

Clearly defines the charging interfaces/protocols and procedures in HSGW

Clearly defines the charging IEs in HSGW

Specifies eHRPD charging architecture

Adds additional charging parameters if 3GPP2 specific charging IEs are needed

Propose eHRPD charging architecture

5

Proposal—Option1 HSGW supports Ga interface with GTP’ Protocol HSGW acts as CTF and CDF, and should be

enhanced to support GTP’ protocol HSGW sends charging messages directly to 3GPP CG

via Ga interface 3GPP CGF should be upgraded to receive HSGW

charging messages and generate HSGW CDR GTP’ protocol may need to be extended to convey

3GPP2 specific charging IEs

6

Proposal—Option2 HSGW supports Rf interface with Diameter Protocol HSGW acts as CTF and only supports Diameter

protocol HSGW sends charging event informations to

3GPP2 AAA via Rf interface 3GPP2 AAA (proxy) should contain CDF and CGF,

and be upgraded to receive HSGW charging IEs and generate HSGW CDR

No impact on 3GPP specifications

7

Proposal—Option3

HSGW supports Rf interface with Diameter Protocol HSGW acts as CTF and only supports Diameter

protocol HSGW sends charging event information to 3GPP

CDF via Rf interface 3GPP CDF generates HSGW CDR May have some impact on 3GPP specifications

8

9

Recommendations

Discuss and suggest to adopt Option 2 or Option 3

10

•Thanks