ITU-T J 705-2011 IPTV client provisioning activation configuration and management interface definition (Study Group 9)《交互式网络电视(IPTV)客户端配置激活配置和管理接口定义 研究组9》.pdf

《ITU-T J 705-2011 IPTV client provisioning activation configuration and management interface definition (Study Group 9)《交互式网络电视(IPTV)客户端配置激活配置和管理接口定义 研究组9》.pdf》由会员分享，可在线阅读，更多相关《ITU-T J 705-2011 IPTV client provisioning activation configuration and management interface definition (Study Group 9)《交互式网络电视(IPTV)客户端配置激活配置和管理接口定义 研究组9》.pdf（20页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T J.705TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (01/2011) SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS Secondary distribution of IPTV services IPTV client provisioning, activation, configuratio

2、n and management interface definition Recommendation ITU-T J.705 Rec. ITU-T J.705 (01/2011) i Recommendation ITU-T J.705 IPTV client provisioning, activation, configuration and management interface definition Summary Recommendation ITU-T J.705 describes the i-2 interface, identified in Recommendatio

3、n ITU-T J.700, that enables the service client in the customer network to interface with the operations support systems (OSS) functions in the operator network to provision and manage the IPTV client functions in the customer network. Examples of OSS functions include client provisioning, activation

4、, configuration, and management (PACM). History Edition Recommendation Approval Study Group 1.0 ITU-T J.705 2011-01-13 9 ii Rec. ITU-T J.705 (01/2011) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and

5、 communication technologies (ICTs). The ITU Telecommunication 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 bas

6、is. The World Telecommunication Standardization Assembly (WTSA), 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 Resol

7、ution 1. In some areas of information technology which fall 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

8、and a recognized operating agency. Compliance with this Recommendation 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

9、 met. The words “shall“ or some other obligatory language such 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 pos

10、sibility that the practice or implementation of this Recommendation 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

11、 Recommendation development process. As of the date of approval 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 infor

12、mation and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2011 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.705 (01/2011) iii Table of Conte

13、nts Page 1 Scope 1 2 References. 1 3 Definitions 2 3.1 Terms defined elsewhere 2 3.2 Terms defined in this Recommendation . 2 4 Abbreviations and acronyms 2 5 Conventions 3 6 IPTV network reference points . 3 7 IPTV client provisioning, activation, configuration, and management interface . 4 7.1 Fun

14、ctions 4 7.2 Protocols . 5 7.3 Provisioning of settings 5 7.4 Reporting of faults and status . 5 7.5 Event accounting 6 7.6 Secure software download 6 Bibliography. 11 Rec. ITU-T J.705 (01/2011) 1 Recommendation ITU-T J.705 IPTV client provisioning, activation, configuration and management interface

15、 definition 1 Scope ITU-T J.700 describes the service requirements and functional framework architecture for the support of broadcasting services enhanced by IP technology over secondary distribution (e.g., cable and optical, etc.) networks. It addresses the service requirements, use cases and funct

16、ional components required to support these requirements. Where possible, ITU-T J.700 utilizes material already developed or under development in ITU-T Recommendations that are related to video service delivery over secondary networks. The scope of this Recommendation is the i-2 interface, identified

17、 in ITU-T J.700 and in Figure 1, that enables the service client in the customer network to interface with the operations support systems (OSS) functions in the operator network to provision and manage the IPTV client functions in the customer network. Examples of OSS functions include client provis

18、ioning, activation, configuration, and management (PACM). 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, the editions indicated were valid. All R

19、ecommendations 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 currently valid ITU-T Recommendations is regul

20、arly 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 H.740 Recommendation ITU-T H.740 (2010), Application event handling for IPTV services. ITU-T J.222.2 Recommendation ITU-T J.222.2 (2007), Third-ge

21、neration transmission systems for interactive cable television services IP cable modems: MAC and upper layer protocols. ITU-T J.360 Recommendation ITU-T J.360 (2006), IPCablecom2 architecture framework. ITU-T J.700 Recommendation ITU-T J.700 (2009), IPTV service requirements and framework for second

22、ary distribution. ITU-T J.702 Recommendation ITU-T J.702 (2008), Enablement of current terminal devices for the support of IPTV services. ATIS-0300092 ATIS-0300092 (2007), High Level OSS/BSS Functional Requirements and Reference Architecture for IPTV. ATIS-0800009 ATIS-0800009 (2009), Remote Managem

23、ent of Devices in the Consumer Domain for IPTV Services. ATIS-0800014 ATIS-0800014 (2009), Secure Download and Messaging Interoperability Specification. BBF TR-069 Broadband Forum TR-069 (2007), CPE WAN Management Protocol v1.1, plus Amendment 2. 2 Rec. ITU-T J.705 (01/2011) ETSI TS 102 824 ETSI TS

24、102 824 V1.2.1 (2010), Digital Video Broadcasting (DVB); Remote Management and Firmware Update System for DVB IPTV Services (Phase 2). IETF RFC 793 IETF RFC 793 (1981), Transmission Control Protocol. IETF RFC 1350 IETF RFC 1350 (1992), The TFTP Protocol (Revision 2). IETF RFC 1901 IETF RFC 1901 (199

25、6), Introduction to Community-based SNMPv2. IETF RFC 2616 IETF RFC 2616 (1999), Hypertext Transfer Protocol HTTP/1.1. IETF RFC 2818 IETF RFC 2818 (2000), HTTP Over TLS. IETF RFC 3411 IETF RFC 3411 (2002), An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks.

26、 IETF RFC 3418 IETF RFC 3418 (2002), Management Information Base (MIB) for the Simple Network Management Protocol (SNMP). IETF RFC 3584 IETF RFC 3584 (2003), Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework. ISO/IEC 13818-6 ISO/IEC 13818-6

27、:1998, Information technology Generic coding of moving pictures and associated audio information Part 6: Extensions for DSM-CC. OMA DM FUMO Open Mobile Alliance, OMA DM FUMO (2009), Firmware Update Management Object V.1.0.2. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the foll

28、owing term defined elsewhere: 3.1.1 Threshold crossing alerts b-ITU-T M.2140: A transient condition declared when a performance monitoring parameter reaches or exceeds a preset threshold. 3.2 Terms defined in this Recommendation None. 4 Abbreviations and acronyms This Recommendation uses the followi

29、ng abbreviations and acronyms: ACS Auto Configuration Server BSS Business Support System CA Conditional Access CAS Central Authentication Service CPE Customer Premises Equipment CVT Code Version Table DHCP Dynamic Host Configuration Protocol DM Device Management DRM Digital Rights Management DSM-CC

30、Digital Storage Media Command and Control Rec. ITU-T J.705 (01/2011) 3 DVB Digital Video Broadcasting EAS Emergency Alert System FUMO Firmware Update Management Object HTTP HyperText Transfer Protocol NAT Network Address Translation OSS Operations Support Systems PACM Provisioning, Activation, Confi

31、guration, and Management PPV Pay Per View QoS Quality of Service RG Residential Gateway RMS-FUS Remote Management and Firmware Update Services SCP Service and Content Protection SIP Session Initiation Protocol SLA Service Level Agreement SNMP Simple Network Management Protocol TCA Threshold Crossing

32、 Alerts TCP Transmission Control Protocol TD Terminal Device TFTP Trivial File Transfer Protocol TLS Transport Layer Security UPnP Universal Plug and Play VQE Visual Quality Experience XCAP XML Configuration Access Protocol XML eXtensible Markup Language 5 Conventions This clause is intentionally le

33、ft blank. 6 IPTV network reference points ITU-T J.700 identifies significant reference points, shown in Figure 1 below, between the CPE and the various network functions with which it interfaces, between the session/resource/policy management functions and the IPTV application servers, and between t

34、he IP content sources and the content processing, distribution, and storage functions. The CPE reference points are meant to address IP interfaces for hybrid and IP CPE. Network interface points for MPEG CPE and the MPEG portion of hybrid CPE are of a legacy nature and therefore not addressed. 4 Rec

35、. ITU-T J.705 (01/2011) Figure 1 IPTV network reference points The focus of this Recommendation is the i-2 interface, OSS functions service client. The i-2 interface enables the service client in the customer network to interface with the OSS functions in the operator network to provision and manage

36、 the IPTV client functions in the customer network. The customer network includes CPE and RG. 7 IPTV client provisioning, activation, configuration, and management interface The IPTV client provisioning, activation, configuration, and management interface makes use of multiple protocols to access or

37、 implement several of the IPTV OSS and services functions, or portions thereof, identified in ITU-T J.700. 7.1 Functions The following types of functions are supported over the interface: 1) Configuration functions at the network level, including setting transport parameters, installing and initiati

38、ng routing services and consumer specific policy management in the CPE as part of the providers network. 2) Accounting management, including different commercial arrangements between the service providers and consumers, inter-carrier support, retail billing and QoS monitoring in support of SLA manag

39、ement. 3) Security management including CPE-based service and content protection, content control, and protection mechanisms for content in transit (within the CPE) and storage, if not addressed in the i-3 interface. 4) Fault management in the CPE, including assuring service reliability to reduce or

40、 eliminate packet loss and rerouting due to failure in the network. An example is VQE (Visual quality experience) on the client. Rec. ITU-T J.705 (01/2011) 5 In particular, the following functions are supported, aligned with ATIS-0300092: a) Service(s) management including messaging, and management

41、of 3rd party applications. b) CAS/DRM control processing and client handling (complementing i-3). c) Event accounting, e.g., pay per view. d) Subscriber resource management, such as QoS management, and resource performance management, such as statistical data collection and TCAs; performance statist

42、ics for managed IPTV services resources; resource performance metrics; IP layer metrics such as packet loss, delay, jitter, and packet sequencing or duplication. e) Service quality and performance management, such as CPE performance data through BBF TR-069 ACS or other probes (e.g., channel changes,

43、 dropped packets, MPEG); and VQE statistics. f) CPE and RG management (remotely), including secure software download, protocol handling/processing, diagnostics/logging, provisioning, CPE/RG administrative settings, configuration settings, and NAT settings. g) Service problem management and resource

44、trouble management, including actively monitoring the CPE and RG to report alarms in the event of faults, and collecting status information from the CPE and RG remotely. 7.2 Protocols Potential supporting protocols include the following: 1) Web services (HTTP, XML, XCAP) 2) SIP configuration framewo

45、rk 3) TFTP for client configuration 4) TR-069 5) SNMP 6) OMA DM 7) DSM-CC for data carousel; polling and report back for event accounting 8) DHCP not strictly a management protocol, but used in discovery 9) UPnP not strictly a management protocol, but used in discovery. 7.3 Provisioning of settings

46、See use of SIP in IPCablecom2 ITU-T J.360. Security and NAT traversal of management protocols in IPCablecom2 are specifically not specified ITU-T J.360. 7.4 Reporting of faults and status This clause defines protocols and functional requirements for the reporting of faults and status of CPE. 7.4.1 P

47、rotocols for reporting At least one of the following protocols is required to be supported by the CPE if it is designed for the use with an embedded-DOCSIS cable modem. SNMPv3 defined in IETF Standard 62 IETF RFC 3411 through IETF RFC 3418 SNMPv1/v2c coexistence IETF RFC 3584 SNMPv2 community-based

48、access IETF RFC 1901 6 Rec. ITU-T J.705 (01/2011) If the CPE uses a baseband IP communication method such as Ethernet, one of the following protocols is required to be used ITU-T H.740. HTTP version 1.1 IETF RFC 2616. HTTP over TLS IETF RFC 2818. TFTP IETF RFC 1350. TCP IETF RFC 793. 7.4.2 Initiatio

49、n of the collecting process It is required that the process of collecting CPE report-backs be initiated and managed by the head-end controller. This means that a manager (for SNMP) or a client (for others) resides in the head-end controller, and an agent (for SNMP) or a server (for others) is implemented in the CPE. It can be optionally initiated by the CPE in the form of an “unsolicited report-back“. In this case, necessary components such as a server and a clien