1、 I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T J.1104 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (10/2016) SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS Switched digital video over cable networks Control speci
2、fication for IP-based switched digital video using data over cable service interface specifications Recommendation ITU-T J.1104 Rec. ITU-T J.1104 (10/2016) i Recommendation ITU-T J.1104 Control specification for IP-based switched digital video using data over cable service interface specifications S
3、ummary Recommendation ITU-T J.1104 describes the operator control specifications of IP-based switched digital video (SDV) using data over cable service interface specifications (DOCSIS) in digital cable networks. The cable broadcasting system has been changed to use resources efficiently and to tran
4、smit them to easily accommodate the varying needs of the subscriber. Therefore, it is necessary to define the transmission specifications for Recommendation ITU-T J.1101, which supports the maintaining of quality of service (QoS) and using bandwidth effectively in a hybrid fiber/coaxial (HFC) networ
5、k environment. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T J.1104 2016-10-14 9 11.1002/1000/13056 * To access the Recommendation, type the URL http:/handle.itu.int/ in the address field of your web browser, followed by the Recommendations unique ID. For example, http:/ha
6、ndle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T J.1104 (10/2016) 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
7、 (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 (WTSA), which meets every f
8、our 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 within ITU-Ts purview, t
9、he 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 Recommendation is voluntary.
10、 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 such as “must“ and the neg
11、ative 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 RIGHTSITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the u
12、se 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 approval of this Recommendatio
13、n, ITU had 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 patent database at http:/www.i
14、tu.int/ITU-T/ipr/. ITU 2017 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.1104 (10/2016) iii Table of Contents Page 1 Scope . 1 2 References . 1 3 Definitions 1 3.1 Terms defined elsewhere 1 3.2
15、Terms defined in this Recommendation . 1 4 Abbreviations and acronyms 1 5 Conventions 2 6 IP-based SDV reference model 2 6.1 Transmission function 3 6.2 Subscriber function . 3 7 Operator control specification 3 7.1 Operator control 3 7.2 Control and management sub-function 4 7.3 Performance monitor
16、ing sub-function 6 7.4 Alarm status reporting sub-function . 11 Bibliography. 12 Rec. ITU-T J.1104 (10/2016) 1 Recommendation ITU-T J.1104 Control specification for IP-based switched digital video using data over cable service interface specifications 1 Scope This Recommendation defines the operator
17、 control specifications of the IP-based switched digital video (SDV) using data over cable service interface specification (DOCSIS). The operator control specifications described in this Recommendation are defined as follows: system control and monitoring by operator. 2 References The following ITU-
18、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 to revision; users of this Recommendation
19、 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 within this Recommendation does not give it,
20、as a stand-alone document, the status of a Recommendation. ITU-T J.222.2 Recommendation ITU-T J.222.2 (2007), Third-generation transmission systems for interactive cable television services IP cable modems: MAC and Upper Layer protocols. ITU-T J.1101 Recommendation ITU-T J.1101 (2012), Functional re
21、quirements for IP-based switched digital video using data over cable service interface specifications. ITU-T J.1102 Recommendation ITU-T J.1102 (2015), Interface specifications for IP-based switched digital video using DOCSIS. ITU-T J.1103 Recommendation ITU-T J.1103 (2015), Transmission specificati
22、on for IP-based switched digital video using data over cable service interface specifications. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following term defined elsewhere: 3.1.1 IP-based switched digital video (SDV) ITU-T J.1101: A service mechanism which provides interfa
23、ces and functionalities to enable cable television system operators to offer QoS guaranteed broadcasting and multicasting. 3.2 Terms defined in this Recommendation None. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: CM Cable Modem CMTS Cable Modem Te
24、rmination System DOCSIS Data Over Cable Service Interface Specifications 2 Rec. ITU-T J.1104 (10/2016) DS Downstream GBE Giga Bit Ethernet HFC Hybrid Fiber/Coaxial IP Internet Protocol IPC Inter Process Communications MAC Media Access Control NSI Network Service Interface PHY Physical Layer QAM Quad
25、rature Amplitude Modulation QoS Quality of Service RPC Remote Procedure Call SDV Switched Digital Video VSI Video Service Interface 5 Conventions The keywords “is required to“ indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this Recom
26、mendation is to be claimed. The keywords “is recommended“ indicate a requirement which is recommended but which is not absolutely required. Thus this requirement need not be present to claim conformance. The keywords “is prohibited from“ indicate a requirement which must be strictly followed and fro
27、m which no deviation is permitted if conformance to this Recommendation is to be claimed. The keywords “can optionally“ indicate an optional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendors implementation must prov
28、ide the option and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with the specification. In the body of this Recommendation and its annexes, the words shall, shall not, should
29、, and may sometimes appear, in which case they are to be interpreted, respectively, as is required to, is prohibited from, is recommended, and can optionally. The appearance of such phrases or keywords in an appendix or in material explicitly marked as informative are to be interpreted as having no
30、normative intent. 6 IP-based SDV reference model As shown in Figure 1, functionally IP-based SDV using the DOCSIS system can be categorized into three parts, for example, Transmission function, Subscriber function and Control function. Rec. ITU-T J.1104 (10/2016) 3 Figure 1 Diagram of an IP-based sw
31、itched digital video system 6.1 Transmission function The transmission function processes the DOCSIS frame header and transmits it to the multicast service group. The transmission function consists of an SDV transmission function and a downstream (DS) physical layer (PHY) function. The SDV transmiss
32、ion function processes service flow and packet header processing on the DOCSIS media access control (MAC) layer ITU-T J.222.2. The downstream PHY function transmits the DOCSIS header processed video stream to the subscriber. 6.2 Subscriber function The subscriber function processes the video data st
33、ream from the transmission function. The subscriber function consists of the SDV client service function and SDV receiver function. The subscriber function also sends the request information of an SDV video service programme to the control function. 7 Operator control specification 7.1 Operator cont
34、rol The operator control function is required to input the following information: System control and device management System performance monitoring System alarm System event The operator control function transmits and receives messages between device management function and operator interface funct
35、ion. The device management function exchanges information through inter process communications (IPC) messages. All messages being received and transmitted by IPC management unit use IPC message type. The message format of an operator control specification is shown in Figure 2. A detailed definition
36、is provided in Table 1. It has message ID per feature of message and per message type as header, 4 Rec. ITU-T J.1104 (10/2016) depending on the format of receiving and transmission of messages. Message data can be defined in different length and format depending on message types. Figure 2 Message fo
37、rmat Table 1 Message header Field Length(byte) Function GUI_ID 4 (Integer) ID MESSAGE_TYPE 4 (Integer) 1000: Command 2000: configuration file load 3000: configuration file save 4000: library call for statistic 5000: library call for port monitoring 6000: notify alarm RESULT 4 (Integer) 0: NO RESULT
38、1: OK Operation 64 (String) Depend on MESSAGE_TYPE COMMAND (IF MESSAGE_TYPE =1000) File Path (IF MESSAGE_TYPE=2000 or 3000) NAME OF CALL METHOD (IF MESSAGE_TYPE=4000 or 5000) NO USED : IF MESSAGE_TYPE=6000 NO USED: IF RESULT: NO CONTINUE_FLAG 4 (integer) 0: NO CONTINUE 1: CONTINUE DATA 944 (String)
39、COMMAND RESULT CONFIGURATION FILE INFORMATION STATISTIC INFORMATION PORT MONITORING INFORMATION NOTIFY ALARM INFORMATION REASON INFORMATION AS NO RESULT 7.2 Control and management sub-function Control and management sub-function consists of the following two sub-functions: Device management Configur
40、ation file load For device management, the request/response message communication between the device-managing block, which is located in target board, and the GUI operator interfacing block of the monitoring system, which is located in remote server, is carried out using TCP/IP. Rec. ITU-T J.1104 (1
41、0/2016) 5 As shown in Figure 3, the monitoring system sends a req_dev_manage( ) message to the target system. When the target system receives the req_dev_manage( ) message, it sends a rsp_dev_manage( ) message to the monitoring system. Figure 3 Message communication procedure for device management T
42、he req_dev_manage( ) message is the request message for device management. It uses the message format shown in Table 2. Table 2 Req_dev_manage( ) Type Name Length Description 1 int guiId 4 bytes GUI ID 2 int messageType 4 bytes Command = 1000 3 int dataSize 4 bytes Message size 4 int operation 64 by
43、tes Command 5 int continue 4 bytes Continue flag 6 String data 944 bytes No used The rsp_dev_manage( ) message is the response message for device management. It uses the message format as shown in Table 3. Table 3 Rsp_dev_manage( ) Type Name Length Description 1 int guiId 4 bytes GUI ID 2 int messag
44、eType 4 bytes Command = 1000 3 int dataSize 4 bytes Message size 4 int operation 64 bytes Command 5 int continue 4 bytes Continue flag 6 String data 944 bytes Command result When the configuration file is uploaded, the monitoring system sends a req_cfg_fileload( ) message to the target system. When
45、the target system receives the req_cfg_fileload( ) message, it sends a rsp_cfg_fileload ( ) message to the monitoring system. 6 Rec. ITU-T J.1104 (10/2016) Figure 4 Message communication procedure for configuration file load The req_cfg_fileload( ) message shown in Figure 4 is the request message fo
46、r configuration of file loading. It uses the message format shown in Table 4. Table 4 Req_cfg_fileload( ) Type Name Length Description 1 int guiId 4 bytes GUI ID 2 int messageType 4 bytes ConfigFile_Load = 2000 3 int dataSize 4 bytes Message size 4 int operation 64 bytes Command 5 int continue 4 byt
47、es Continue flag 6 String data 944 bytes No used The rsp_cfg_fileload( ) message is the response message for configuration of file loading. It uses the message format shown in Table 5. Table 5 Rsp_cfg_fileload( ) Type Name Length Description 1 int guiId 4 bytes GUI ID 2 int messageType 4 bytes Confi
48、gFile_Load = 2000 3 int dataSize 4 bytes Message size 4 int operation 64 bytes Command 5 int continue 4 bytes Continue flag 6 String data 944 bytes File result 7.3 Performance monitoring sub-function Performance monitoring sub-function consists of the following sub-functions: Start collecting the st
49、atistic information Stop collecting the statistic information Start collecting the channel statistic information Stop collecting the channel statistic information The block displays the failure and status collecting and analysing the overall status information, and delivers the result to operator. The status information delivered to an operator through operator interface shall be easily recognizable to an operator on the status and failure information in real-time. When failure occurs, it shall be made possible for a
