1、 International Telecommunication Union ITU-T J.164TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (12/2007) SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS IPCablecom Event message requirements for the support of real-time services over cable tel
2、evision networks using cable modems ITU-T Recommendation J.164 ITU-T Rec. J.164 (12/2007) i ITU-T Recommendation J.164 Event message requirements for the support of real-time services over cable television networks using cable modems Summary ITU-T Recommendation J.164 describes the concept of Event
3、Messages used to collect usage for the purposes of billing within the IPCablecom architecture. It details the RADIUS protocol used to carry these messages, defines the various Event Messages, lists the attributes each Event Message contains, and lists the required and optional Event Messages associa
4、ted with each type of end-user service supported. Source ITU-T Recommendation J.164 was approved on 14 December 2007 by ITU-T Study Group 9 (2005-2008) under the ITU-T Recommendation A.8 procedure. History Edition Approval 1.0 J.164 2001-03-09 2.0 J.164 2005-11-29 3.0 J.164 2007-12-14 ii ITU-T Rec.
5、J.164 (12/2007) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is resp
6、onsible 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 (WTSA), which meets every four years, establishes the topics for study by the
7、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 within ITU-Ts purview, the necessary standards are prepared on a collaborat
8、ive 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 Recommendation is voluntary. However, the Recommendation may contain certain ma
9、ndatory 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 such as “must“ and the negative equivalents are used to express requirements.
10、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 Recommendation may involve the use of a claimed Intellectual Property Right. ITU ta
11、kes 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 approval of this Recommendation, ITU had not received notice of intellectual prop
12、erty, 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 patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2008 All rights reserved
13、. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. ITU-T Rec. J.164 (12/2007) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Terms and definitions . 2 4 Abbreviations and conventions. 2 4.1 Abbreviations . 2 4.2 Conventions 3 5 Backg
14、round. 3 5.1 Traditional telephony billing formats. 4 5.2 Motivation for event-based billing . 4 5.3 Originating/terminating call model to support customer billing and settlements 4 5.4 Real-time billing. 5 5.5 Real-time and batch event message delivery 5 5.6 Terminology and concepts . 5 5.7 Support
15、ing documentation 7 6 IPCablecom objectives . 7 6.1 IPCablecom required services and capabilities 7 6.2 Additional IPCablecom supported services and capabilities 7 6.3 Assumptions . 8 7 Event messages architecture. 9 7.1 IPCablecom Event Message collection 10 7.2 IPCablecom network elements . 10 7.3
16、 General IPCablecom network element requirements . 13 7.4 Event Message interfaces . 14 8 IPCablecom services and their associated Event Messages . 15 8.1 IPCablecom call configurations . 15 8.2 Specific services . 18 9 IPCablecom Event Message structure 25 9.1 Event Message structure. 29 9.2 Servic
17、e_Instance. 29 9.3 Service_Activation . 31 9.4 Signalling_Start 32 9.5 Signalling_Stop 35 9.6 Service_Deactivation 36 9.7 Database_Query . 37 9.8 Intelligent_Peripheral_Usage_Start 38 9.9 Intelligent_Peripheral_Usage_Stop 38 9.10 Interconnect_Start. 38 iv ITU-T Rec. J.164 (12/2007) Page 9.11 Interco
18、nnect_Stop. 39 9.12 Call_Answer. 39 9.13 Call_Disconnect . 41 9.14 QoS_Reserve 42 9.15 QoS_Release. 42 9.16 Time_Change . 43 9.17 QoS_Commit 43 9.18 RTP_Connection_Parameters event message 44 9.19 Media_Alive. 44 9.20 Media_Statistics . 46 10 IPCablecom Event Message attributes . 47 10.1 EM_Header a
19、ttribute structure . 59 10.2 Call termination cause attribute structure. 63 10.3 Trunk group ID attribute structure . 64 10.4 QoS descriptor attribute structure. 65 10.5 Redirected-from-info attribute structure. 66 10.6 Electronic-surveillance-indication attribute structure 66 10.7 Attributes for co
20、nference parties 67 11 Transport-independent event message attribute TLV format. 67 12 IPCablecom event message file format 68 12.1 File bit/Byte order. 68 12.2 File header 68 12.3 File-naming convention 69 12.4 Configuration items 70 12.5 File EM structure header 71 13 Transport protocol 71 13.1 Ra
21、dius protocol introduction 71 13.2 RADIUS accounting protocol 71 13.3 File transport protocol (FTP) 75 Bibliography. 76 ITU-T Rec. J.164 (12/2007) 1 ITU-T Recommendation J.164 Event message requirements for the support of real-time services over cable television networks using cable modems 1 Scope T
22、his Recommendation describes the concept of Event Messages used to collect usage for the purposes of billing within the IPCablecom architecture. It details the RADIUS protocol used to carry these messages, defines the various Event Messages, lists the attributes each Event Message contains, and list
23、s the required and optional Event Messages associated with each type of end-user service supported. 2 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
24、, the editions indicated were valid. All Recommendations and other references are subject 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 curr
25、ently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T J.112 ITU-T Recommendation J.112 (1998), Transmission systems for interactive cable television services.
26、 ITU-T J.112-A ITU-T Recommendation J.112 Annex A (2001), Digital Video Broadcasting: DVB interaction channel for Cable TV (CATV) distribution systems. ITU-T J.112-B ITU-T Recommendation J.112 Annex B (2004), Data-over-cable service interface specifications: Radio-frequency interface specification.
27、ITU-T J.162 ITU-T Recommendation J.162 (2007), Network call signalling protocol for the delivery of time-critical services over cable television networks using cable modems. ITU-T J.163 ITU-T Recommendation J.163 (2007), Dynamic quality of service for the provision of real-time services over cable t
28、elevision networks using cable modems. ITU-T J.170 ITU-T Recommendation J.170 (2005), IPCablecom security specification. ITU-T J.171.x ITU-T Recommendation J.171.x (2005), IPCablecom trunking gateway control protocol (TGCP). ITU-T X.680 ITU-T Recommendation X.680 (2002), Information technology Abstr
29、act Syntax Notation One (ASN.1): Specification of basic notation. ITU-T X.681 ITU-T Recommendation X.681 (2002), Information technology Abstract Syntax Notation One (ASN.1): Information object specification. ITU-T X.682 ITU-T Recommendation X.682 (2002), Information technology Abstract Syntax Notati
30、on One (ASN.1): Constraint specification. ITU-T X.683 ITU-T Recommendation X.683 (2002), Information technology Abstract Syntax Notation One (ASN.1): Parameterization of ASN.1 specifications. 2 ITU-T Rec. J.164 (12/2007) ITU-T X.690 ITU-T Recommendation X.690 (2002), Information technology ASN.1 enc
31、oding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER). IETF RFC 2865 IETF RFC 2865 (2000), Remote Authentication Dial In User Service (RADIUS). IETF RFC 2866 IETF RFC 2866 (2000), RADIUS Accounting. 3 Terms and definitions Thi
32、s Recommendation defines the following terms: 3.1 cable modem: A cable modem is a layer two termination device that terminates the customer end of the J.112 connection. 3.2 attribute: An Event Message Attribute is a predefined data element described by an attribute definition and attribute type. 3.3
33、 call: A call is an instance of user-initiated voice communication capabilities. In traditional telephony, a call is generally considered as the establishment of connectivity directly between two points: originating party and terminating party. In the IPCablecom context, as noted above, the communic
34、ation between the parties is “connectionless“ in the traditional sense. 3.4 event message: An Event Message is a set of data, representative of an event in the IPCablecom architecture that could be indicative of usage of one or more billable IPCablecom capabilities. An Event Message by itself may no
35、t be fully indicative of a customers billable activities, but an Event Message correlated with other Event Messages builds the basis of a billable Usage Detail Record. 3.5 IPCablecom: An ITU-T project that includes an architecture and a series of Recommendations that enable the delivery of real-time
36、 services over cable television networks using cable modems. 3.6 IPCablecom transaction: An IPCablecom transaction is a collection of events on the IPCablecom network when delivering a service to a subscriber. Event Messages for the same transaction are identified by one unique billing correlation I
37、D (as described in Table 39). For some services, multiple transactions may be required to provide information that is necessary to collect the total usage for the service. Multiple Event Messages may be required to track resources for each individual service used. A transaction may persist over time
38、. 3.7 service: A service is an individual or package of communications features a subscriber may select. A service is identified by a set of one or more “calls“ or transactions that deliver the desired functionality to the subscriber. Examples of a service include: a voice communication between two
39、local IPCablecom subscribers, a 3-way call, pay-per-view movie, and a web-surfing session. A service may be instantaneous or persist over time. 4 Abbreviations and conventions 4.1 Abbreviations This Recommendation uses the following abbreviations: AMA Automated Message Accounting CDR Call Detail Rec
40、ord CM Cable Modem CMS Call Management Server ITU-T Rec. J.164 (12/2007) 3 CPE Customer Premises Equipment FID Flow Identifier HFC Hybrid Fibre Coax IP Internet Protocol MGC Media Gateway Controller MTA Media Terminal Adapter OSS Operations Support System PSTN Public Switched Telephone Network RKS R
41、ecord-Keeping Server SS7 Signalling System No. 7 VAD Voice Activity Detection 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 or the adjective “REQUIRED“ means that the it
42、em is an absolute requirement of this Recommendation. “MUST NOT“ This phrase means that the item is an absolute prohibition of this Recommendation. “SHOULD“ This word or the adjective “RECOMMENDED“ means that there may exist valid reasons in particular circumstances to ignore this item, but the full
43、 implications should be understood and the case carefully weighed before choosing a different course. “SHOULD NOT“ This phrase means that there may exist valid reasons in particular circumstances when the listed behaviour is acceptable or even useful, but the full implications should be understood a
44、nd the case carefully weighed before implementing any behaviour described with this label. “MAY“ This word or the adjective “OPTIONAL“ means that this item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because it enhances the product, fo
45、r example; another vendor may omit the same item. 5 Background An Event Message is a data record containing information about network usage and activities. A single Event Message may contain a complete set of data regarding usage or it may only contain part of the total usage information. When corre
46、lated by the record-keeping server (RKS), information contained in multiple Event Messages provides a complete record of the service. This complete record of the service is often referred to as a call detail record (CDR). Event Messages or CDRs may be sent to one or more back-office applications suc
47、h as a billing system, fraud detection system, or prepaid services processor. The structure of the Event Message data record is designed to be flexible and extensible in order to carry information about network usage for a wide variety of services. Examples of these services include IPCablecom voice
48、, video and other multimedia services, such as video-on-demand, pay-per-view and J.112 high-speed data services. 4 ITU-T Rec. J.164 (12/2007) This IPCablecom Event Messages Recommendation defines a transport protocol independent Event Message attribute TLV format, an Event Message file format, as we
49、ll as the mandatory RADIUS protocol and the optional FTP transport protocol. Although the scope of this Event Message Recommendation is limited to defining Event Messages for simple voice communication activities, it is expected that this Recommendation will be expanded to support additional IPCablecom services as well as high-speed data services. 5.1 Traditional telephony billing formats The telephony industry has traditionally recorded call detail transactions on telephone switches utilizing various standard and proprietary billing form
