1、 International Telecommunication Union ITU-T J.460.3TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (09/2008) SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS IPCablecom IPCablecom2 residential SIP telephony: Usage data recording Recommendation IT
2、U-T J.460.3 Rec. ITU-T J.460.3 (09/2008) i Recommendation ITU-T J.460.3 IPCablecom2 residential SIP telephony: Usage data recording Summary The purpose of Recommendation ITU-T J.460.3 is to define the collection of usage data needed to support accounting of residential SIP telephony (RST) features.
3、In addition to defining how the collection of usage data is done, this Recommendation details the various accounting events and their associated attributes. The IPCablecom2 Accounting framework and generic requirements are defined in Recommendation ITU-T J.363, IPCablecom2 data collection to support
4、 accounting, on which this Recommendation is based. This release of the Recommendation supports services described in Recommendation ITU-T J.460.0, Appendix II, and defined in detail in Recommendation ITU-T J.460.1. Source Recommendation ITU-T J.460.3 was approved on 19 September 2008 by ITU-T Study
5、 Group 9 (2005-2008) under the WTSA Resolution 1 procedure. ii Rec. ITU-T J.460.3 (09/2008) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunicati
6、on Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (W
7、TSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall
8、 within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Rec
9、ommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language su
10、ch as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recomme
11、ndation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of appro
12、val of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB p
13、atent database at http:/www.itu.int/ITU-T/ipr/. ITU 2010 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T J.460.3 (09/2008) iii CONTENTS Page 1 Scope 1 1.1 Introduction and purpose 1 2 References. 2 2
14、.1 Normative references 2 2.2 Informative references 2 2.3 Reference acquisition . 2 3 Terms and definitions . 2 4 Abbreviations, acronyms and conventions. 3 4.1 Abbreviations and acronyms 3 4.2 Conventions 4 5 Technical overview. 4 5.1 IPCablecom2 accounting architecture 4 5.2 Design goals . 5 5.3
15、Scope 5 6 IPCablecom2 services. 5 6.1 IPCablecom2 call configurations . 5 6.2 Specific services . 8 7 Definition of accounting information . 29 7.1 Data Description for RST offline accounting. 29 7.2 RST Specific Parameters 30 Annex A Region A 34 Annex B Region B 35 Annex C Region C 36 Rec. ITU-T J.
16、460.3 (09/2008) 1 Recommendation ITU-T J.460.3 IPCablecom2 residential SIP telephony: Usage data recording 1 Scope 1.1 Introduction and purpose The purpose of this Recommendation is to define the collection of usage data needed to support accounting of residential SIP telephony (RST) features. In ad
17、dition to defining how the collection of usage data is done, this Recommendation details the various accounting events and their associated attributes. The IPCablecom2 accounting framework and generic requirements are defined in the IPCablecom2 accounting Recommendation ITU-T J.363, on which this Re
18、commendation is based. This release of the Recommendation supports services described in Appendix II of ITU-T J.460.0, and defined in detail in ITU-T J.460.1. Future releases will support additional services that are described in Appendices I and III of ITU-T J.460.0, as they are developed. Resident
19、ial SIP telephony (RST) features are defined in the RST features Recommendation ITU-T J.460.1. Accounting procedures for a sub-set of those features defined by the RST specification are defined in this Recommendation. In particular, the RST specification defines both UE-based and network-based featu
20、res. UE-based features are executed locally by the UE-based on some locally defined criteria (i.e., matching a feature code to an internal digit map for feature execution). Such features cannot be accounted for, as there are no accounting records created by the UE. Sessions resulting from local feat
21、ure execution can be accounted for using standard accounting procedures. However, the reason for the session establishment will not always be known by the network. There are some locally executed features, e.g., three way calling, that may be detectable by the billing support system through post-pro
22、cessing of accounting records (i.e., if the billing support system sees two sets of seemingly unrelated accounting events for which both sessions were active at the same time, it can infer that a three way call was made). Network-based features, on the other hand, are executed in the network by an a
23、pplication server. This server provides feature execution as defined by the RST specification. Given that application servers can generate accounting events, the features executed by application servers can be accounted for. Given that IPCablecom2 accounting does not define accounting for applicatio
24、n servers, this Recommendation defines the accounting records the application server generates based on the feature being executed. It is an important objective of this work that interoperability between IPCablecom 2.0 and 3GPP IMS is provided. IPCablecom 2.0 is based upon 3GPP IMS, but includes add
25、itional functionality necessary to meet the requirements of cable operators. Recognizing developing converged solutions for wireless, wireline, and cable, it is expected that further development of IPCablecom 2.0 will continue to monitor and contribute to IMS developments in 3GPP, with the aim of al
26、ignment of 3GPP IMS and IPCablecom 2.0. NOTE The structure and content of this Recommendation have been organized for ease of use by those familiar with the original source material; as such, the usual style of ITU-T recommendations has not been applied. 2 Rec. ITU-T J.460.3 (09/2008) 2 References 2
27、.1 Normative references The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject
28、 to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document wit
29、hin this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T J.363 Recommendation ITU-T J.363 (2006), IPCablecom2 data collection to support accounting. ETSI TS 132 240 ETSI TS 132 240 v6.3.0 (2006), Charging Architecture and Principles. ETSI TS 132 260
30、ETSI TS 132 260 v.6.4.0 (2005), IP Multimedia Subsystem (IMS) charging. ETSI TS 132 299 ETSI TS 132 299 v.6.5.0 (2005), Diameter charging applications. 2.2 Informative references This Recommendation uses the following informative references. ITU-T J.366.4 Recommendation ITU-T J.366.4 (2006), IPCable
31、com2 IP Multimedia Subsystem (IMS): Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 Specification. ITU-T J.460.0 Recommendation ITU-T J.460.0 (2008), IPCablecom2 residential SIP telephony: Feature definition. ITU-T J.460.1 Recommendation ITU-T J.460.1 (2008), IPCabl
32、ecom2 residential SIP telephony: Feature specification. IETF RFC 3588 IETF RFC 3588 (2003), Diameter Base Protocol. 3GPP TS 23.228 3GPP TS 23.228 (2005), IP Multimedia Subsystem (IMS) Stage 2, Release 6, V6.12.0. 3GPP TS 32.251 3GPP TS 32.251 (2006), Telecommunication management; Charging management
33、; Packet Switched (PS) domain charging. 2.3 Reference acquisition Internet Engineering Task Force (IETF), Internet: http:/www.ietf.org Third Generation Partnership Project (3GPP), Internet: http:/www.3gpp.org 3 Terms and definitions This Recommendation uses the following terms defined in ITU-T J.363
34、: 3.1 accounting: The process of collecting usage data. 3.2 charging: The process of applying rating to usage data for a given session for the generation of a subscribers bill. 3.3 DIAMETER: The Diameter protocol provides an authentication, authorization and accounting (AAA) framework for applicatio
35、ns such as network access or IP mobility. 3.4 HFC access network: The hybrid-fibre coax network, which provides physical transport of video and high speed data services via DOCSIS. Rec. ITU-T J.460.3 (09/2008) 3 3.5 usage data: A collection of data representing the usage of network resources for a g
36、iven session. 4 Abbreviations, acronyms and conventions 4.1 Abbreviations and acronyms This Recommendation uses the following abbreviations: 3GPP Third Generation Partnership Project AC Automatic Callback ACA Accounting-Answer ACR Accounting-Request AR Auto Recall AS Application Server AVP Attribute
37、 Value Pair B2BUA Back-to-Back User Agent CDF Charging Data Function CF Call Forwarding CFDA Call Forwarding Dont Answer CFV Call Forwarding Variable CSCF Call Session Control Function ICID IMS Charging ID IMPU IMS Public Identity IMS IP Multimedia Subsystem IOI Inter-Operator Identifier IVR Interac
38、tive Voice Responder LIDB Line Identification Database OCB Outbound Call Blocking P-CSCF Proxy-CSCF RACF Remote Activation of Call Forwarding RST Residential SIP Telephony SCB Solicitor Call Blocking S-CSCF Serving-CSCF SIP Session Initiation Protocol UE User Equipment 4 Rec. ITU-T J.460.3 (09/2008)
39、 4.2 Conventions Throughout this Recommendation, the words that are used to define the significance of particular requirements are capitalized. These words are: “MUST“ This word means that the item is an absolute requirement of this Recommendation. “MUST NOT“ This phrase means that the item is an ab
40、solute prohibition of this Recommendation. “SHOULD“ This word means that there may exist valid reasons in particular circumstances to ignore this item, but the full implications should be understood and the case carefully weighed before choosing a different course. “SHOULD NOT This phrase means that
41、 there may exist valid reasons in particular circumstances when the listed behaviour is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behaviour described with this label. “MAY“ This word means that this item is truly
42、optional. One vendor may choose to include the item because a particular marketplace requires it or because it enhances the product, for example; another vendor may omit the same item. 5 Technical overview 5.1 IPCablecom2 accounting architecture Figure 1 depicts the IPCablecom2 accounting reference
43、architecture, as described in IPCablecom2 accounting ITU-T J.363. J.460.3(08)_F01S-CSCF CDF/CGFRST client CM CMTSApp mgr Policy serverRfRKSBilling systemRST ASISCMwGmUndefinedpkt-qos-1RfRfUndefinedP-CSCFpkt-mm-3pkt-mm-4pkt-mm-2pkt-mm-5pkt-mm-1Figure 1 IPCablecom2 accounting reference architecture Th
44、e IPCablecom2 residential SIP telephony (RST) feature specification ITU-T J.460.1 leverages IPCablecom2 as the underlying SIP-based network. The RST application server implements the application level network functionality for the RST service, and is essentially seen as an application server from th
45、e IPCablecom2 perspective. Consequently, communications between the IPCablecom2 network and the RST application server utilize the ISC interface defined in 3GPP TS 23.228. As described in the following clauses, only the RST application server is relevant for accounting of RST features. Rec. ITU-T J.
46、460.3 (09/2008) 5 5.1.1 Functional entities The next two clauses discuss the RST functional entities; RST client and RST application server are presented as described in ITU-T J.460.1. Also, different roles of the RST server that impact the RST accounting architecture are described. 5.1.1.1 RST clie
47、nt (UE) The RST client resides on the UE and is used to access RST services. References to simply a UE in this Recommendation imply a UE with an RST client accessing RST services. 5.1.1.2 RST application server The RST application server implements the application level network functionality for the
48、 RST service. The RST application server may be either a back-to-back user agent (B2BUA), or a forwarding proxy, depending on the feature definition in the RST Feature Recommendation. For the features covered by this Recommendation, the RST application server is expected to always act as a forwardin
49、g proxy. However, the accounting definitions should not prohibit B2BUA operation, should such an implementation be used. 5.2 Design goals The IPCablecom2 RST accounting architecture attempts to limit extensions of accounting events to the application server only. Changes to CSCF accounting events should be avoided whenever practically possible. Extensions to accounting events should be contained in an RST-Information AVP group within the Service-Information AVP group as defined in ETSI TS 132 260 and ETSI TS 132 299. 5.3 Sc
