Re: [sipcore] Does SIP support "Reverse Charging" function?

gao.yang2@zte.com.cn Sat, 25 September 2010 05:12 UTC

Return-Path: <gao.yang2@zte.com.cn>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A9E053A68BF; Fri, 24 Sep 2010 22:12:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.958
X-Spam-Level:
X-Spam-Status: No, score=-99.958 tagged_above=-999 required=5 tests=[AWL=1.280, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_32=0.6, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5-9VrzgRkw7o; Fri, 24 Sep 2010 22:12:35 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 8B2E33A69C5; Fri, 24 Sep 2010 22:12:34 -0700 (PDT)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 205952001811080; Sat, 25 Sep 2010 13:10:51 +0800 (CST)
Received: from [10.30.3.19] by [192.168.168.16] with StormMail ESMTP id 85748.5647140985; Sat, 25 Sep 2010 13:01:51 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o8P5Cwem050879; Sat, 25 Sep 2010 13:12:58 +0800 (CST) (envelope-from gao.yang2@zte.com.cn)
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE2173212E6@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.1 January 17, 2006
Message-ID: <OFB59AC847.5C8BD073-ON482577A9.001BD2F5-482577A9.001CA1EB@zte.com.cn>
From: gao.yang2@zte.com.cn
Date: Sat, 25 Sep 2010 13:10:49 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2010-09-25 13:12:48, Serialize complete at 2010-09-25 13:12:48
Content-Type: multipart/alternative; boundary="=_alternative 001CA1E9482577A9_="
X-MAIL: mse2.zte.com.cn o8P5Cwem050879
Cc: "sipcore@ietf.org" <sipcore@ietf.org>, sipcore-bounces@ietf.org
Subject: Re: [sipcore] Does SIP support "Reverse Charging" function?
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Sep 2010 05:12:42 -0000

Hi Keith,

> P-Charging-Vector and P-Charging-Function-Addresses header fields 
> are not specifically any form of charging.

Yes. So, I said that they are syntax level standardization for the SIP 
extension.
 
> I would suggest that to do reverse charging, you need a charging 
> model in the first place. That does not exist in IETF. Even in 3GPP,
> it would need additional work, because you would need to address 
> signalling transactions to the entities performing the charging, 
> rather than those collecting the data.

IMO, this work should do it's function level things in 3GPP and syntax 
level standardization for SIP extension in IETF.

I guess you(or ALU) would alos have reverse charging requirement for your 
deployed IMS network. Then, may us propose the requirement to the SA1 
group, and then, SIP extension work in IETF?

Thanks,

Gao


--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.