Add files using upload-large-folder tool

marked/J/T-REC-J.1002-201303-I_PDF-E/raw.md

@@ -0,0 +1,664 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**J.1002**
+
+(03/2013)
+
+SERIES J: CABLE NETWORKS AND TRANSMISSION  
+OF TELEVISION, SOUND PROGRAMME AND OTHER  
+MULTIMEDIA SIGNALS
+
+Conditional access and protection
+
+# --- **Pairing protocol specification for renewable conditional access system**
+
+Recommendation ITU-T J.1002
+
+
+
+## Recommendation ITU-T J.1002
+
+# Pairing protocol specification for renewable conditional access system
+
+## Summary
+
+Recommendation ITU-T J.1002 specifies the pairing protocol that supports the conditional access module (CAM) and descrambler (DSC) pairing function, which is specified in Recommendation ITU-T J.1001.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group |
+|---------|----------------|------------|-------------|
+| 1.0     | ITU-T J.1002   | 2013-03-01 | 9           |
+
+## 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 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 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 within ITU-T's 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 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 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 possibility 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 Recommendation development process.
+
+As of the date of approval of this Recommendation, 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.itu.int/ITU-T/ipr/>.
+
+© ITU 2013
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+|                                                                  | Page |
+|------------------------------------------------------------------|------|
+| 1 Scope .....                                                    | 1    |
+| 2 References.....                                                | 1    |
+| 3 Definitions .....                                              | 1    |
+| 3.1 Terms defined elsewhere .....                                | 1    |
+| 3.2 Terms defined in this Recommendation.....                    | 1    |
+| 3.3 Security symbols .....                                       | 2    |
+| 3.4 Parameter definitions.....                                   | 2    |
+| 3.5 Security function definitions .....                          | 3    |
+| 4 Abbreviations and acronyms .....                               | 3    |
+| 5 Conventions .....                                              | 3    |
+| 6 Overview of RCAS pairing protocol .....                        | 4    |
+| 7 Details of RCAS pairing protocol.....                          | 5    |
+| 7.1 Initialization.....                                          | 5    |
+| 7.2 Pairing.....                                                 | 6    |
+| 7.3 CWEK generation .....                                        | 10   |
+| 8 CAM and DSC interface message format and encryption.....       | 12   |
+| 8.1 DscCertReq message .....                                     | 13   |
+| 8.2 DscCertRsp message .....                                     | 13   |
+| 8.3 CWEKGenInfo message .....                                    | 14   |
+| 8.4 CWEKGenInfoCnfm message .....                                | 14   |
+| Appendix I – The functional structures for the CAM and DSC ..... | 16   |
+| I.1 Functional structure for CAM .....                           | 16   |
+| I.2 Functional structure for DSC.....                            | 17   |
+| Bibliography.....                                                | 18   |
+
+## Introduction
+
+Recommendation ITU-T J.1001 specifies the requirements for renewable conditional access system (RCAS), and it identifies the pairing protocol that is one of the functional requirements.
+
+The RCAS is a new paradigm technology for renewing conditional access (CA) client software by securely downloading the new version of software through the digital cable two-way environment. The benefit of RCAS is that no additional budget is required for issuing a new security hardware module when the multiple systems operator (MSO) wants to upgrade the old CA client software to a new one.
+
+The pairing protocol is an authentication protocol between the conditional access module (CAM) and descrambler (DSC). The authentication process between the CAM and DSC is one of the most important security requirements for the RCAS. If the pairing is not performed properly, it may cause a control word (CW) disclosure problem. For example, a hacked DSC could intercept CWs transferred from the CAM through impersonation attack. As a result, a hacker could watch pay broadcasting programs without proper entitlement by taking advantage of the intercepted CW.
+
+If the pairing is not performed properly, this may cause another problem – of managing paid-viewers. For example, a malicious user could remove the physically-implemented CAM from one set-top box that stores entitlement information, and connect the removed CAM to another set-top box. Then a malicious user could watch pay broadcasting programs on multiple set-top boxes with one CAM. As a result, MSO cannot properly manage pay subscribers, and undergoes unwanted business losses.
+
+To prevent the above drawbacks, a pairing protocol is specified in this Recommendation, which can provide a mutual authentication and security channel establishment between the CAM and the DSC. Using the pairing protocol can efficiently prevent a hacked DSC from eavesdropping CWs, which are transferred from the CAM to DSC, as well as unwanted usage of one CAM to multiple set-top boxes.
+
+## Recommendation ITU-T J.1002
+
+# Pairing protocol specification for renewable conditional access system
+
+# 1 Scope
+
+This Recommendation specifies the pairing protocol that provides the conditional access module (CAM) and descrambler (DSC) pairing function of renewable conditional access system (RCAS), which is specified in [ITU-T J.1001].
+
+# 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 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 currently 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.1001] Recommendation ITU-T J.1001 (2012), *Requirements for renewable conditional access system*.
+
+[ITU-T X.509] Recommendation ITU-T X.509 (2008) | ISO/IEC 9594-8:2008, *Information technology – Open Systems Interconnection – The Directory: Public-key and attribute certificate frameworks*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 conditional access (CA)** [b-ITU-T J.193]: The conditional granting of access to cable services and content based upon what service suite has been purchased by the customer.
+
+**3.1.2 descrambling** [b-ITU-T J.93]: The processes of reversing the scrambling function (see "scrambling") to yield usable pictures, sound, and data services.
+
+**3.1.3 entitlement control messages (ECMs)** [b-ITU-T J.290]: An ECM is an encrypted message that contains access criteria to various service tiers and a control word (CW).
+
+**3.1.4 entitlement management messages (EMMs)** [b-ITU-T J.290]: The EMM contains the actual authorization data and shall be sent in a secure method to each CPE device.
+
+**3.1.5 scrambling** [b-ITU-T J.93]: The process of using an encryption function to render television and data signals unusable to unauthorized parties.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 authorization centre (AC)**: An entity which issues identification information of CAM and performs authentication process when CAM requests renewing of CACS.
+
+**3.2.2 conditional access module (CAM)**: A cryptographic functional module which is located in set-top boxes, whose main function is entitlement validation, key management and authentication. Set-top boxes can have one chip of secure hardware that includes the functions of CAM and
+
+descrambler, or physically separated CAM in the form of a secure hardware IC or smart-card. The form of CAM can be determined by the policy of the MSO or CAS vendor.
+
+**3.2.3 conditional access client software (CACS):** An image of conditional access client software code downloaded onto the CRS CAM.
+
+**3.2.4 control word (CW):** The value which is used to scramble and descramble transport streams; it is refreshed frequently during the service operation to enhance security.
+
+## 3.3 Security symbols
+
+| Security symbols    | Descriptions                                                                                                                                                                                               |
+|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Pub(X)              | RSA public key of 'X'                                                                                                                                                                                      |
+| Prv(X)              | RSA private key of 'X'                                                                                                                                                                                     |
+| E(k,m)              | Encryption of a message 'm' with key 'k'. RSAES-OAEP is used to encrypt a message when the encryption key is a public key. AES-ECB is used to encrypt a message when the encryption key is a symmetric key |
+| S(k,m)              | Digital signature for a message 'm' with signing key 'k'. RSASSA-PSS is used for message signing                                                                                                           |
+| H(m)                | SHA-256 hashing for a message 'm'                                                                                                                                                                          |
+| HMAC(k,m)           | HMAC-SHA1 for a message 'm' with key 'k'                                                                                                                                                                   |
+| X  Y                | Concatenation of 'X' and 'Y'                                                                                                                                                                               |
+| Cert(X)             | ITU-T X.509 certificate of 'X'                                                                                                                                                                             |
+| PRF(X)              | Pseudo random function having a seed value of 'X'                                                                                                                                                          |
+| X <sub>msb(Y)</sub> | 'Y' bits from MSB of 'X'                                                                                                                                                                                   |
+
+## 3.4 Parameter definitions
+
+| Parameter names | Descriptions                                                                                                                                                                                                                                                                             |
+|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| DSC_ID          | The value of identification of DSC having a size of 40 bytes                                                                                                                                                                                                                             |
+| CAM_ID          | The value of identification of CAM having a size of 8 bytes                                                                                                                                                                                                                              |
+| KeyPairingID    | The value of concatenation with CAM_ID and DSC_ID, i.e., CAM_ID  DSC_ID                                                                                                                                                                                                                  |
+| CWEK            | The abbreviation of control words encryption key, and used to encrypt <i>control words</i><br>The CWEK generation method is<br>$CWEK = H(CWEK  CAM\_ID  DSC\_ID)_{msb(128)}$                                                                                                             |
+| KPK             | The abbreviation of key pairing key. The AC generates the KPK if KeyPairingID is valid                                                                                                                                                                                                   |
+| HMAC_KEY        | An HMAC secret key. The CAM uses HMAC_KEY to generate an HMAC value for the message including <i>control words</i><br>The HMAC_KEY generation method is<br>$HMAC\_KEY = H(RAND_{HMAC}  CAM\_ID  DSC\_ID)_{msb(160)}$ Here RAND <sub>HMAC</sub> is achieved by PRF(X) <sub>msb(320)</sub> |
+| RAND            | A random number with 320 bits                                                                                                                                                                                                                                                            |
+| K <sub>i</sub>  | The pre-shared key having the size of 128 bits. AC uniquely assigns three K <sub>i</sub> to each CAM                                                                                                                                                                                     |
+
+## 3.5 Security function definitions
+
+| Security functions                 | Requirements                                                                                                                                                                                                                                                                                                                                                                                 |
+|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| RSA digital signature (RSASSA-PSS) | <ul style="list-style-type: none"> <li>• Modulus (n): 1024 bits</li> <li>• Exponent: F4 (65537)</li> <li>• Message Encoding: RSASSA-PSS               <ul style="list-style-type: none"> <li>– Hash algorithm (default): SHA-1</li> <li>– MGF (default): MGF1 with SHA-1</li> <li>– Trailer field: 1 (corresponds to '0xbc')</li> <li>– Salt length: 160/8 = 20 bytes</li> </ul> </li> </ul> |
+| RSA encryption (RSAES-OAEP)        | <ul style="list-style-type: none"> <li>• Modulus (n): 1024 bits</li> <li>• Exponent: F4 (65537)</li> <li>• MGF1 with SHA-1 for the mask generation function</li> <li>• The empty string for the encoding parameter string</li> </ul>                                                                                                                                                         |
+| AES encryption                     | <ul style="list-style-type: none"> <li>• Block cipher mode: AES 128 ECB</li> </ul>                                                                                                                                                                                                                                                                                                           |
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                                     |
+|------|-------------------------------------|
+| AC   | Authorization Centre                |
+| AES  | Advanced Encryption Standard        |
+| CACS | Conditional Access Client Software  |
+| CAM  | Conditional Access Module           |
+| CASS | CAM Authentication Sub-System       |
+| CW   | Control Word                        |
+| CWEK | Control Words Encryption Key        |
+| DSC  | Descrambler                         |
+| ECB  | Electric Code Block                 |
+| HMAC | Hashed Message Authentication Code  |
+| KPK  | Key Pairing Key                     |
+| MSO  | Multiple Systems Operator           |
+| PSI  | Pairing Status Information          |
+| RCAS | Renewable Conditional Access System |
+
+# 5 Conventions
+
+In this Recommendation:
+
+The keywords "**is required to**" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this Recommendation 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 from 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 vendor's implementation must provide 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*, 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* is to be interpreted as having no normative intent.
+
+### 6 Overview of RCAS pairing protocol
+
+The components of RCAS that participate in the pairing protocol are the 'CAM authentication sub-system', 'authorization centre', 'CAM' and 'descrambler' of RCAS, as shown in Figure 1.
+
+![Figure 1 – Reference architecture of the RCAS and RCAS pairing protocol components](f519a5be118c846f631c992412353fb9_img.jpg)
+
+The diagram illustrates the reference architecture between the Headend and Customer premises.   
+**Headend side:**  
+ - **CRS headend:** Contains 'CAM authentication sub-system' (yellow box) and 'Authorization centre' (yellow box).  
+ - **CAS operation block:** Contains 'Content sources', 'Billing', and 'Headend CAS system (including scrambler)'.  
+ - A 'Secure CACS download sub-system' sits between the CRS headend and CAS operation block.  
+**Customer premises side:**  
+ - **CRS set-top box:** Contains a 'Client CAS block' which includes 'CAM' (yellow box) and 'Descrambler' (yellow box).  
+ - The 'CAM' and 'Descrambler' are connected via 'CW' (Control Word).  
+ - The 'Descrambler' outputs to a 'TV' (Clear content output).  
+**Connectivity:**  
+ - A 'Cable network (two-way network (e.g., DOCSIS) for CRS)' connects the Headend and Customer premises.  
+ - Flows include: 'Authentication and CACS encryption key establishment', 'CA client S/W', 'Secure channel', 'ECM/EMM', and 'Encrypted content'.
+
+Figure 1 – Reference architecture of the RCAS and RCAS pairing protocol components
+
+**Figure 1 – Reference architecture of the RCAS and RCAS pairing protocol components**
+
+The specification of RCAS pairing function includes:
+
+- **A pairing protocol that supports CAM and DSC pairing:** The participants of the protocol should be authorization centre (AC), CAM authentication sub-system (CASS), CAM and DSC.
+- **A control words encryption key (CWEK) establishment protocol:** If the control words are delivered in plaintext from CAM to DSC, a malicious user could possibly watch pay programmes by using the disclosed control words for decrypting the scrambled video streams. Therefore, the CAM must provide confidentiality for the control words by encrypting them with the CWEK.
+- **AC participation in CWEK establishment:** Since a successful CWEK establishment between CAM and DSC means that the CAM believes the DSC as its correct pair, or vice versa, CWEK establishment must not be performed before the AC confirms that the CAM and DSC are correctly paired. For this reason, the RCAS CAM and DSC pairing protocol should make sure that the CAM and DSC establish a CWEK after they have received confirmation that the CAM and DSC are correctly paired from the AC.
+
+4 Rec. ITU-T J.1002 (03/2013)
+
+The RCAS pairing protocol consists of three sequences of phases: initialization, pairing and CWEK generation. The brief descriptions of each phase are as follows.
+
+- **Phase I:** Phase I is the 'Initialization'. At the initialization phase, the pairing protocol between the CAM and DSC is initiated. The CAM monitors the triggering conditions of the protocol, and starts the protocol procedures if it meets one of the triggering conditions. Then, the CAM and DSC exchange their own ITU-T X.509 certificates [ITU-T X.509] with each other.
+- **Phase II:** Phase II is the 'Pairing'. At the pairing phase, when the CAM transmits identification information of itself (i.e., CAM\_ID) and the DSC (i.e., DSC\_ID) to the AC via CASS, the AC verifies validation of the identification information. If the identification information of the CAM and the DSC are validated, the CAM and the DSC are managed in pair. Then, AC transmits a validation verification message containing encryption seed key (i.e., KPK) to the CAM via CASS.
+- **Phase III:** Phase III is the 'CWEK generation'. At the CWEK generation phase, the CAM and the DSC generates the control word encryption key (CWEK) and encrypts mutual traffic with the generated CWEKs. If the CAM is paired with the DSC, a CWEK of the CAM is the same as a CWEK of the DSC.
+
+In the following clause, each procedure of the security authentication method using the pairing protocol will be described in detail.
+
+# 7 Details of RCAS pairing protocol
+
+The detail descriptions of each RCAS pairing protocol steps are defined in the following clauses.
+
+## 7.1 Initialization
+
+Figure 2 illustrates a flowchart of the initialization for security authentication between the CAM and DSC. Referring to Figure 2, a pairing protocol between the CAM and the DSC is initiated if present initialization conditions are satisfied. Here, the initialization may be conducted when the CAM is newly booted due to newly supplied power or due to the reset, when the CAM in a virgin state receives a security announce message from the CASS or when the CAM in a non-virgin state receives a client update request from the CASS through a RCAS download message.
+
+When any of the initialization conditions are satisfied, the CAM generates a certification request message (hereinafter referred to as DscCertReq message) including certificate information (CAM ITU-T X.509 CERTIFICATE) of the CAM and transmits the DscCertReq message to the DSC. In response to the receipt of the DscCertReq message from the CAM, the DSC verifies certificate signature using an AC root certificate. If the verification is successful, the DSC stores the certificate information of the CAM in a non-volatile memory of the DSC.
+
+Then, the DSC generates a certification response message (hereinafter referred to as DscCertRsp message) and transmits the DscCertRsp message to the CAM. Then, in response to the receipt of the DscCertRsp message, the CAM verifies a certificate signature using the AC root certificate. If the verification is successful, the CAM stores certificate information (DSC ITU-T X.509 CERTIFICATE) of the DSC, which is included in the DscCertRsp message, in a non-volatile memory of the CAM.
+
+![Figure 2 – Flowchart of the initialization phase. The diagram shows four lifelines: AC, CASS, CAM, and DSC. The sequence starts with a 'POWER ON' event on the CAM lifeline. The CASS sends a 'Security announce MESSAGE' to the CAM. The CASS then sends a 'RCAS download MESSAGE' to the CAM. The CAM sends a 'DscCertReq MESSAGE' to the DSC. The DSC sends a 'DscCertRsp MESSAGE' back to the CAM. The diagram is labeled J.1002(13)_F02 at the bottom right.](d4af765160d04ecef538e5066006dc77_img.jpg)
+
+```
+
+sequenceDiagram
+    participant AC
+    participant CASS
+    participant CAM
+    participant DSC
+    Note right of CAM: POWER ON
+    CASS->>CAM: Security announce MESSAGE
+    CASS->>CAM: RCAS download MESSAGE
+    CAM->>DSC: DscCertReq MESSAGE
+    DSC->>CAM: DscCertRsp MESSAGE
+  
+```
+
+Figure 2 – Flowchart of the initialization phase. The diagram shows four lifelines: AC, CASS, CAM, and DSC. The sequence starts with a 'POWER ON' event on the CAM lifeline. The CASS sends a 'Security announce MESSAGE' to the CAM. The CASS then sends a 'RCAS download MESSAGE' to the CAM. The CAM sends a 'DscCertReq MESSAGE' to the DSC. The DSC sends a 'DscCertRsp MESSAGE' back to the CAM. The diagram is labeled J.1002(13)\_F02 at the bottom right.
+
+**Figure 2 – Flowchart of the initialization phase**
+
+The summarized procedures of the initialization phase are as follows.
+
+- Step 1: If the CAM meets one of the below conditions, the CAM sends its ITU-T X.509 certificate to the DSC through a DscCertReq message. Note that a CAM can achieve the CASS ITU-T X.509 certificate from the SecurityAnnounce message that is supposed to be delivered from the CASS.
+  - \* Condition 1: when CAM is powered up or reset,
+  - \* Condition 2: when a virgin CAM receives a SecurityAnnounce message from a CASS,
+  - \* Condition 3: when a CAM receives a SecurityAnnounce message from a CASS right after the CAM moves to another MSO network, or
+  - \* Condition 4: when a non-virgin CAM is requested to update CA client images from a CASS via a RCASDownload message.
+- Step 2: Right after the DSC receives a DscCertReq message from the CAM, the DSC verifies the signature of the CAM ITU-T X.509 certificate using the public key of the AC. Only if the DSC can successfully verify the CAM ITU-T X.509 certificate, does the DSC store the CAM\_ID and RSA public key of the CAM extracted from the CAM ITU-T X.509 certificate in the secure area of non-volatile memory. Otherwise, the DSC terminates this protocol. Finally, the DSC sends a DscCertRsp message including its ITU-T X.509 certificate to the CAM.
+- Step 3: Right after the CAM receives the DscCertRsp message from the DSC, the CAM verifies the signature of the DSC ITU-T X.509 certificate using the public key of the AC. Only if the CAM can successfully verify the DSC ITU-T X.509 certificate, does the CAM store the DSC\_ID and RSA public key of the DSC extracted from the DSC ITU-T X.509 certificate in the secure area of non-volatile memory, and goes to the next phase. Otherwise, the CAM terminates this protocol.
+
+## 7.2 Pairing
+
+Figure 3 illustrates a flowchart of an example of a method of pairing a CAM and a DSC for security authentication. Referring to Figure 3, the CAM transmits a CAM identifier (CAM\_ID) and DSC identifier (DSC\_ID) to a CASS, and an AC verifies the validation of the respective identification information. In detail, the CAM encrypts a key request message including a pair of identifiers (hereinafter referred to as KeyPairingID) of the CAM and the DSC, and transmits the KeyPairingID
+
+to the AC via the CASS. The KeyPairingID is a concatenated value of the CAM identifier and the DSC identifier.
+
+The AC which has received the key request message verifies the validation of the KeyPairingID. For the validation verification, the AC compares originally issued identifier (ID) values of the CAM and the DSC with ID values of the CAM and the DSC, which are received through the key request message. Only when the originally-issued ID values are identical with the ID values received through the key request message, does the AC verify that the KeyPairingID is validated.
+
+![Sequence diagram of the pairing phase showing interactions between AC, CASS, CAM, and DSC.](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg)
+
+```
+
+sequenceDiagram
+    participant AC
+    participant CASS
+    participant CAM
+    participant DSC
+
+    CAM->>CASS: KeyPairingID
+    CASS->>AC: KeyPairingID
+    Note left of AC: VALIDATION VERIFICATION
+    AC->>CASS: KeyResponse MESSAGE
+    Note right of CASS: [SUCCESSFUL VALIDATION]
+    CASS->>CAM: VALIDATION VERIFICATION MESSAGE
+    Note right of CASS: [FAILURE IN VALIDATION]
+    CASS->>CAM: STATUS MESSAGE
+  
+```
+
+The diagram illustrates the sequence of messages during the pairing phase. It starts with the CAM sending a KeyPairingID to the CASS. The CASS then forwards this to the AC. The AC performs a validation verification (indicated by a circle on its lifeline). The AC sends a KeyResponse MESSAGE to the CASS. The CASS then sends a VALIDATION VERIFICATION MESSAGE to the CAM, accompanied by a status message indicating either [SUCCESSFUL VALIDATION] or [FAILURE IN VALIDATION]. The DSC lifeline is shown but has no messages.
+
+Sequence diagram of the pairing phase showing interactions between AC, CASS, CAM, and DSC.
+
+**Figure 3 – Flowchart of the pairing phase**
+
+The AC generates a key response message based on the validation verification result of the KeyPairingID. If the KeyPairingID is validated, the AC generates a key pairing key (KPK) that is a seed encryption key, and transmits a validation verification message indicating the validation of the KeyPairingID to the CAM via the AC. If the KeyPairingID is invalid, the AC transmits a status message indicating that the KeyPairingID is invalid. In this case, a status message that sets all bytes of the KPK to '0xff' is transmitted to the CAM via the CASS.
+
+The KeyPairingID validation process at AC utilizes pairing status information (PSI) as shown in Table 1. The PSI is maintained by the AC based on the pairing state diagram shown in Figure 4. As the pairing state diagram shows, PSI is classified into three types. The first type is Virgin('0x00'). The AC sets the PSI type as Virgin('0x00') when it issues identification information of the CAM and DSC and there have been no CAM-DSC pairing validation check requests from the MSO RCAS headend for them. The second type is Auth/Paired('0x01'). The AC changes the PSI type from Virgin('0x00') or Paired\_Only('0x10') to Auth/Paired('0x01') when the RCAS host devices in either a Virgin('0x00') state or Paired\_Only('0x10') state are connected to the MSO network and have passed the CAM-DSC pairing validation check in the AC. The third type is Paired\_Only('0x10'). The AC sets the PSI type to Paired\_Only('0x10') when the RCAS host devices in an Auth/Paired('0x01') state leave the MSO network.
+
+**Table 1 – Pairing state information**
+
+| CAM state | DSC state | Pairing state information |
+|-----------|-----------|---------------------------|
+| 0x00      | 0x00      | Virgin                    |
+| 0x01      | 0x01      | Auth/Paired               |
+| 0x10      | 0x10      | Paired Only               |
+
+![Pairing state diagram showing three states: Virgin, Auth/Paired, and Paired Only. Transitions are 'The first join' from Virgin to Auth/Paired, 'Leave' from Auth/Paired to Paired Only, and 'Join' from Paired Only back to Auth/Paired. Reference J.1002(13)_F04.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> Virgin
+    Virgin --> Auth/Paired : The first join
+    Auth/Paired --> Paired Only : Leave
+    Paired Only --> Auth/Paired : Join
+    note right of Paired Only : J.1002(13)_F04
+  
+```
+
+Pairing state diagram showing three states: Virgin, Auth/Paired, and Paired Only. Transitions are 'The first join' from Virgin to Auth/Paired, 'Leave' from Auth/Paired to Paired Only, and 'Join' from Paired Only back to Auth/Paired. Reference J.1002(13)\_F04.
+
+**Figure 4 – Pairing state diagram**
+
+**Table 2 – Generation method of the KeyPairingID and KPK**
+
+| Parameters   | Generation method                                                                                            |
+|--------------|--------------------------------------------------------------------------------------------------------------|
+| KeyPairingID | CAM_ID    DSC_ID                                                                                             |
+| KPK          | $\text{PRF}( H ( K_1    K_2    K_3    \text{CAM\_ID}    \text{DSC\_ID}    \text{RAND} ) )_{\text{msb}(160)}$ |
+
+The generation method of the security parameters is defined in Table 2. The following are detailed descriptions of the pairing phase.
+
+- Step 1: The CAM sends a KeyRequest message to the CASS. As shown in Figure 2, the KeyPairingID is encrypted with the public key of the CASS, and the content is signed with the private key of the CAM. Note that a CAM ITU-T X.509 certificate is added to the tail of this message without encryption.
+- Step 2: The CASS receives the KeyRequest message from the CAM, and verifies the digital signature of the message. The CASS also stores the CAM ITU-T X.509 certificate for future communication with the CAM. If the CASS fails to verify the digital signature of the message, it discards this message and terminates the protocol. Otherwise, the CASS decrypts the KeyPairingID and generates a KeyRequest message including E(Pub(AC), KeyPairingID) instead of E(Pub(CASS), KeyPairingID). After that, the CASS sends this KeyRequest message to the AC. At this time, a CAM ITU-T X.509 certificate is not attached to this message.
+
+![Flowchart of identification validation procedures at the AC. The process starts with 'Start', followed by 'Receive KeyRequest message from CASS and extract CAM_ID and DSC_ID from KeyPairingID', then 'Find PSI having the same CAM_ID and DSC_ID in AC's DB'. A decision 'Found?' follows. If 'NO', it goes to 'End'. If 'YES', it checks 'PSI == 'Virgin(0x00)''? If 'YES', it changes the 'Pairing State' into 'Auth/Paired(0x01)' and judges the CAM and DSC as valid. If 'NO', it checks 'PSI == 'Paired Only(0x10)''? If 'YES', it changes the 'Pairing State' into 'Auth/Paired(0x01)' and judges the CAM and DSC as valid. If 'NO', it judges the CAM and DSC as invalid. Both valid and invalid judgments lead to 'End'. The label J.1002(13)_F05 is at the bottom right.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg)
+
+```
+
+graph TD
+    Start([Start]) --> Step1[Receive KeyRequest message from CASS and extract CAM_ID and DSC_ID from KeyPairingID]
+    Step1 --> Step2[Find PSI having the same CAM_ID and DSC_ID in AC's DB]
+    Step2 --> Found{Found?}
+    Found -- NO --> End([End])
+    Found -- YES --> Virgin{PSI == 'Virgin(0x00)'?}
+    Virgin -- YES --> Change[Change the 'Pairing State' into 'Auth/Paired(0x01)']
+    Virgin -- NO --> PairedOnly{PSI == 'Paired Only(0x10)'?}
+    PairedOnly -- YES --> Change
+    PairedOnly -- NO --> Invalid[AC judges that the CAM and the DSC are invalid]
+    Change --> Valid[AC judges that the CAM and the DSC are valid]
+    Valid --> End
+    Invalid --> End
+  
+```
+
+J.1002(13)\_F05
+
+Flowchart of identification validation procedures at the AC. The process starts with 'Start', followed by 'Receive KeyRequest message from CASS and extract CAM\_ID and DSC\_ID from KeyPairingID', then 'Find PSI having the same CAM\_ID and DSC\_ID in AC's DB'. A decision 'Found?' follows. If 'NO', it goes to 'End'. If 'YES', it checks 'PSI == 'Virgin(0x00)''? If 'YES', it changes the 'Pairing State' into 'Auth/Paired(0x01)' and judges the CAM and DSC as valid. If 'NO', it checks 'PSI == 'Paired Only(0x10)''? If 'YES', it changes the 'Pairing State' into 'Auth/Paired(0x01)' and judges the CAM and DSC as valid. If 'NO', it judges the CAM and DSC as invalid. Both valid and invalid judgments lead to 'End'. The label J.1002(13)\_F05 is at the bottom right.
+
+**Figure 5 – Identification validation procedures at the AC**
+
+- Step 3: The AC receives the KeyRequest message from the CASS, and verifies the digital signature of the message. If the AC fails to verify the digital signature of the message, it discards this message and terminates the protocol. Otherwise, the AC decrypts the KeyPairingID and starts to validate the KeyPairingID based on the PSI as shown in Figure 5. The descriptions of Figure 5 are as follows.
+  - After the AC receives a KeyRequest message from the CASS, it extracts the CAM\_ID and DSC\_ID from the KeyPairingID.
+  - Then, the AC searches the PSI regarding the CAM\_ID and DSC\_ID from its own database.
+  - If the AC fails to find the record in its database regarding the CAM\_ID and DSC\_ID, it terminates the protocol.
+  - If the PSI for the CAM\_ID and DSC\_ID is equal to Virgin('0x00'), the AC changes the PSI from Virgin('0x00') to Auth/Paired('0x01') and judges that the CAM\_ID and DSC\_ID have successfully passed the CAM-DSC pairing validation check.
+  - If the PSI for the CAM\_ID and DSC\_ID is not equal to Virgin('0x00') but the same as Paired\_Only('0x10'), the AC changes the PSI from Paired\_Only('0x10') to Auth/Paired('0x01') and judges that the CAM\_ID and DSC\_ID have successfully passed the CAM-DSC pairing validation check.
+  - For all other cases, the AC judges that the CAM\_ID and DSC\_ID have failed to pass the CAM-DSC pairing validation check.
+
+After finishing the CAM-DSC pairing validation check, the AC generates a KeyResponse message including the encrypted KPK and signed KPK. At this time, the AC generates a KPK, which is uniquely assigned to the CAM, using the generation method shown in
+
+Table 2. Otherwise, the AC sets all bytes of the KPK as '0xff' to indicate that the CAM\_ID and DSC\_ID pairing validation result is a failure. Finally, the AC sends the KeyResponse message to the CASS.
+
+- Step 4: The CASS receives the KeyResponse message from the DSC, and verifies the digital signature of the message. If the CASS fails to verify the digital signature of the message, it discards this message and terminates the protocol. Otherwise, the CASS generates the KeyResponse message including E(Pub(CAM), KPK) instead of E(Pub(CASS), KPK), and sends this message to the CAM. At this time, the signed value of the KPK, i.e., S(Prv(AC),KPK), is inserted into the message content as it is received from the AC.
+
+## 7.3 CWEK generation
+
+![Flowchart of the CWEK generation phase showing interactions between AC, CASS, CAM, and DSC. The CAM initiates the process with 'CWEK AND HMAC_KEY GENERATION', then sends a 'CWEKGenInfo MESSAGE' to the DSC, which responds with a 'CWEKGenInfoCnfm MESSAGE'.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg)
+
+```
+
+sequenceDiagram
+    participant CAM
+    participant DSC
+    Note right of CAM: CWEK AND HMAC_KEY GENERATION
+    CAM->>DSC: CWEKGenInfo MESSAGE
+    DSC-->>CAM: CWEKGenInfoCnfm MESSAGE
+  
+```
+
+J.1002(13)\_F06
+
+Flowchart of the CWEK generation phase showing interactions between AC, CASS, CAM, and DSC. The CAM initiates the process with 'CWEK AND HMAC\_KEY GENERATION', then sends a 'CWEKGenInfo MESSAGE' to the DSC, which responds with a 'CWEKGenInfoCnfm MESSAGE'.
+
+**Figure 6 – Flowchart of the CWEK generation phase**
+
+Figure 6 illustrates a flowchart of a key generation method for security authentication between a CAM and a DSC. Referring to Figure 6, a control word encryption key (CWEK) for encrypting traffic between the CAM and the DSC is generated. Since the CWEK is generated using the above-described KPK, it is possible for the CAM and the DSC to generate the same CWEKs only when the pairing of the CAM and the DSC is normally performed. The CWEK is formed by the equation in Table 3.
+
+More specifically, in response to the receipt of the validation verification message from the CASS, the CAM generates the CWEK and a hashed message authentication code key (hereinafter referred to as HMAC\_KEY). Then, the CAM generates a CWEK message (hereinafter referred to as CWEKGenInfo message) and transmits the generated CWEKGenInfo message to the DSC. The CWEKGenInfo message is encrypted with a public key of the DSC, and electronically signed with a private key of the CAM. Alternatively, if the CAM receives a key response message that indicates the failure of the validation from the CASS, a key response message which has all bytes of the KPK set to '0xff', the CAM transmits to the DSC a CWEKGenInfo message that includes the KPK having all bytes set to '0xff'. Note that HMAC\_KEY of the CAM is obtained by applying SHA1 to a concatenated value of the CAM\_ID, the DSC\_ID and a random number produced by a RAND function as shown in Table 3.
+
+**Table 3 – Generation method of the CWEK and HMAC\_KEY**
+
+| Parameters | Generation method                                                                              |
+|------------|------------------------------------------------------------------------------------------------|
+| CWEK       | $H(\text{KPK} \parallel \text{CAM\_ID} \parallel \text{TP\_ID})\text{msb}(128)$                |
+| HMAC_KEY   | $H(\text{RAND}_{\text{HMAC}} \parallel \text{CAM\_ID} \parallel \text{TP\_ID})\text{msb}(160)$ |
+
+In response to the receipt of the KPK and HMAC\_KEY through the CWEK message from the CAM, the DSC generates a CWEK. The CWEK generated by the DSC is the same as the CWEK generated by the CAM if the DSC has been paired with the CAM.
+
+Then, the DSC transmits a CWEK confirmation message (hereinafter referred to as CWEKGenInfoCnfm message) including the generated CWEK and the HMAC\_KEY to the CAM. If all bytes of the KPK received from the CAM are set as '0xff', the DSC terminates the pairing protocol. The CWEKGenInfoCnfm message is encrypted with a public key of the CAM and electronically signed with a private key of the DSC.
+
+Subsequently, in response to the receipt of the CWEKGenInfoCnfm message the CAM checks whether the CWEK generated by the CAM and the HMAC\_KEY are the same as those included in the CWEKGenInfoCnfm message. If the CWEK and the HMAC\_KEY of the CAM are identical with those included in the CWEKGenInfoCnfm message, the CAM shares the CWEK and the HMAC\_KEY with the DSC. Then, the CAM encrypts control words and transmits them to the DSC.
+
+The summarized procedures of the CWEK generation phase are as follows.
+
+- Step 1: The CAM receives the KeyResponse message from the CASS, and verifies the digital signature of the message. If the CAM fails to verify the digital signature of the message, it discards this message and terminates the protocol. Otherwise, the CAM decrypts the KPK, and verifies  $S(\text{Prv}(\text{AC}), \text{KPK})$  with the decrypted value of the KPK using the public key of the AC. Note that the DSC already has the AC root certificate in its memory. If the CAM fails to verify the digital signature of the KPK, it also discards the KeyResponse message and terminates the protocol. Otherwise, the CAM generates the CWEK and HMAC\_KEY as shown in Table 3. Then, the CAM also generates a CWEKGenInfo message including a KPK and  $\text{RAND}_{\text{HMAC}}$  except when all bytes of the KPK are '0xff'. If all bytes of KPK are '0xff', it terminates this RCAS CAM and DSC pairing protocol since the value of '0xff' means that the CAM\_ID and DSC\_ID pairing validation result is a failure. Finally, the CAM sends the CWEKGenInfo message to the DSC. Note that the value of  $S(\text{Prv}(\text{AC}), \text{KPK})$  is inserted into the message content as it is received from the CASS through a KeyResponse message.
+- Step 2: The DSC receives the CWEKGenInfo message from the CAM, and verifies the digital signature of the message. If the DSC fails to verify the digital signature of the message, it discards this message and terminates the protocol. Otherwise, the DSC decrypts the KPK and  $\text{RAND}_{\text{HMAC}}$ . After that, the DSC verifies  $S(\text{Prv}(\text{AC}), \text{KPK})$  with the decrypted value of KPK using the public key of the AC. Note that the DSC already has the AC root certificate in its memory. If the DSC fails to verify the digital signature of the KPK, it also discards the CWEKGenInfo message and terminates the protocol. Otherwise, the DSC generates a CWEK and HMAC\_KEY with the KPK and  $\text{RAND}_{\text{HMAC}}$  as shown in Table 3. Finally, the DSC generates a CWEKGenInfoCnfm message including  $H(\text{CWEK})||H(\text{HMAC\_KEY})$  and sends this message to the CAM.
+- Step 3: The CAM receives the CWEKGenInfoCnfm message from the DSC, and verifies the digital signature of the message. If the CAM fails to verify the digital signature of the message, it discards this message and terminates the protocol. Otherwise, the CAM decrypts  $H(\text{CWEK})||H(\text{HMAC\_KEY})$  from the CWEKGenInfoCnfm message, and generates the hashed value with the CWEK and HMAC\_KEY that were generated in Step 1. Finally, the CAM compares the hashed values received from the DSC with those generated by the CAM itself. If the two hashed values are mismatched, the CAM terminates the protocol.
+- Step 4: After the CAM and DSC share the same CWEK and HMAC\_KEY, the CWEK is used for encrypting the control words with the symmetric encryption algorithm, and HMAC\_KEY is used for applying the HMAC algorithm to the messages, which includes control words, for the purpose of message authentication. Note that the CAS headend sends
+
+updated control words very frequently, e.g., 1~20 seconds, to the CAM. Therefore, CAM also has to deliver control words from the CAS headend to DSC whenever CAM receives the updated control words from headend. In this circumstance, the primary decision criteria for a message authentication algorithm should be a computational overload, not a security concern. As a result, the HMAC algorithm is selected instead of a digital signature algorithm for the practical reason of reducing computational overload.
+
+# 8 CAM and DSC interface message format and encryption
+
+![Figure 7: CAM and DSC interface message format diagram showing a stack of three fields: CAM-DSC HEADER, CAM-DSC CONTENT, and HMAC. A label J.1002(13)_F07 is present at the bottom right of the stack.](dfe556fea00682b09a59427aaf72051c_img.jpg)
+
+Figure 7: CAM and DSC interface message format diagram showing a stack of three fields: CAM-DSC HEADER, CAM-DSC CONTENT, and HMAC. A label J.1002(13)\_F07 is present at the bottom right of the stack.
+
+Figure 7 – CAM and DSC interface message format
+
+![Figure 8: CAM-DSC CONTENT encryption and HMAC processes diagram. The diagram is split into two horizontal sections: CAM (top) and DSC (bottom). In the CAM section, the CAM-DSC HEADER is input to an HMAC-SHA1 block, which outputs an HMAC value. The CAM-DSC CONTENT is input to an AES-128-ECB Encryption block. The output of the encryption block and the HMAC value are combined (indicated by a circle with a plus sign) to form the final message structure: CAM-DSC HEADER, CAM-DSC CONTENT, and HMAC. In the DSC section, the CAM-DSC HEADER is input to an HMAC-SHA1 block, which outputs an HMAC value. The CAM-DSC CONTENT is input to an AES-128-ECB Decryption block. The output of the decryption block and the HMAC value are combined (indicated by a circle with a plus sign) to form the final message structure: CAM-DSC HEADER, CAM-DSC CONTENT, and HMAC. A dashed line labeled 'HMAC Verification' connects the HMAC value in the CAM section to the HMAC value in the DSC section. A label J.1002(13)_F08 is present at the bottom right of the diagram.](9b9d2abd741ed4bafe7f78f89961c663_img.jpg)
+
+Figure 8: CAM-DSC CONTENT encryption and HMAC processes diagram. The diagram is split into two horizontal sections: CAM (top) and DSC (bottom). In the CAM section, the CAM-DSC HEADER is input to an HMAC-SHA1 block, which outputs an HMAC value. The CAM-DSC CONTENT is input to an AES-128-ECB Encryption block. The output of the encryption block and the HMAC value are combined (indicated by a circle with a plus sign) to form the final message structure: CAM-DSC HEADER, CAM-DSC CONTENT, and HMAC. In the DSC section, the CAM-DSC HEADER is input to an HMAC-SHA1 block, which outputs an HMAC value. The CAM-DSC CONTENT is input to an AES-128-ECB Decryption block. The output of the decryption block and the HMAC value are combined (indicated by a circle with a plus sign) to form the final message structure: CAM-DSC HEADER, CAM-DSC CONTENT, and HMAC. A dashed line labeled 'HMAC Verification' connects the HMAC value in the CAM section to the HMAC value in the DSC section. A label J.1002(13)\_F08 is present at the bottom right of the diagram.
+
+Figure 8 – CAM-DSC CONTENT encryption and HMAC processes
+
+The encryption is performed on the CAM-DSC CONTENT field of a message, and HMAC authentication is performed on both a CAM-DSC HEADER field and the CAM-DSC CONTENT field. RSA encryption and RSA electronic signature verification is performed on the CAM-DSC CONTENT field of the CWEK message. For example, the RSA encryption is performed using an RSAES\_OAEP scheme, and RSA electronic signature verification is performed using an RSASSA-PSS scheme.
+
+Figure 7 illustrates a configuration of a message to be transmitted between the CAM and DSC. Referring to Figure 7, the message includes a CAM-DSC HEADER field, a CAM-DSC CONTENT field and a hashed message authentication code (HMAC) field.
+
+Advanced encryption standard (AES) encryption and HMAC authentication are performed on all messages described with reference to Figures 2, 3 and 6, except the DscCertReq message, the DscCertRsp message and the CWEKGenInfo message.
+
+In detail, the CAM and the DSC perform AES encryption selectively on such important fields as a control word in the CAM-DSC CONTENT field using the CWEK as an encryption key. The CAM and the DSC encrypt data to be transmitted to each other using the CWEK. The advanced encryption standard 128 electric code block (AES 128 ECB) scheme is used for the encryption. The AES 128 ECB scheme encrypts elements of a message, which requires encryption and is communicated between the CAM and the DSC, using the SWEK as an encryption key. For HMAC authentication, a 160-bit value produced by HMAC-SHA1 scheme with respect to the CAM-DSC HEADER and the CAM-DSC CONTENT is concatenated with the CAM-DSC CONTENT as shown in Figure 8.
+
+## 8.1 DscCertReq message
+
+The format of DscCertReq message is defined in Table 4.
+
+**Table 4 – The format of DscCertReq message**
+
+| Field description | Type(Length)<br>(ASN.1 notation) | Note                                             |
+|-------------------|----------------------------------|--------------------------------------------------|
+| CAM-DSC_header{   |                                  |                                                  |
+| Message_Type      | OCTET STRING (SIZE(2))           | Value: 0x0011                                    |
+| Message_Length    | OCTET STRING (SIZE(4))           | The length of CAM-DSC_header and CAM-DSC_content |
+| Message_Nonce     | OCTET STRING (SIZE(8))           |                                                  |
+| Protocol_Version  | OCTET STRING (SIZE(1))           |                                                  |
+| Reserved          | OCTET STRING (SIZE(1))           | Value: 0x00                                      |
+| }                 |                                  |                                                  |
+| CAM-DSC content{  |                                  |                                                  |
+| Cert(CAM)         | BIT STRING                       |                                                  |
+| }                 |                                  |                                                  |
+
+## 8.2 DscCertRsp message
+
+The format of DscCertRsp message is defined in Table 5.
+
+**Table 5 – The format of DscCertRsp message**
+
+| Field description | Type(Length)<br>(ASN.1 notation) | Note                                             |
+|-------------------|----------------------------------|--------------------------------------------------|
+| CAM-DSC_header{   |                                  |                                                  |
+| Message_Type      | OCTET STRING (SIZE(2))           | Value: 0x0012                                    |
+| Message_Length    | OCTET STRING (SIZE(4))           | The length of CAM-DSC_header and CAM-DSC_content |
+| Message_Nonce     | OCTET STRING (SIZE(8))           |                                                  |
+| Protocol_Version  | OCTET STRING (SIZE(1))           |                                                  |
+| Reserved          | OCTET STRING (SIZE(1))           | Value: 0x00                                      |
+| }                 |                                  |                                                  |
+| CAM-DSC content{  |                                  |                                                  |
+
+**Table 5 – The format of DscCertRsp message**
+
+| Field description | Type(Length)<br>(ASN.1 notation) | Note |
+|-------------------|----------------------------------|------|
+| Cert(DSC)         | BIT STRING                       |      |
+| }                 |                                  |      |
+
+## 8.3 CWEKGenInfo message
+
+The format of CWEKGenInfo message is defined in Table 6.
+
+**Table 6 – The format of CWEKGenInfo message**
+
+| Field description                                             | Type(Length)<br>(ASN.1 notation) | Note                                             |
+|---------------------------------------------------------------|----------------------------------|--------------------------------------------------|
+| CAM-DSC_header{                                               |                                  |                                                  |
+| Message_Type                                                  | OCTET STRING (SIZE(2))           | Value: 0x0013                                    |
+| Message_Length                                                | OCTET STRING (SIZE(4))           | The length of CAM-DSC_header and CAM-DSC_content |
+| Message_Nonce                                                 | OCTET STRING (SIZE(8))           |                                                  |
+| Protocol_Version                                              | OCTET STRING (SIZE(1))           |                                                  |
+| Reserved                                                      | OCTET STRING (SIZE(1))           | Value: 0x00                                      |
+| }                                                             |                                  |                                                  |
+| CAM-DSC content{                                              |                                  |                                                  |
+| E(Pub(DSC), KPK    RAND <sub>HMAC</sub> )    S(Prv(DSC), KPK) | OCTET STRING (SIZE(128))         |                                                  |
+| }                                                             |                                  |                                                  |
+| S(Prv(CAM), (CAM-DSC_header    CAM-DSC_content))              | OCTET STRING (SIZE(128))         |                                                  |
+
+## 8.4 CWEKGenInfoCnfm message
+
+The format of CWEKGenInfoCnfm message is defined in Table 7.
+
+**Table 7 – The format of CWEKGenInfoCnfm message**
+
+| Field description | Type(Length)<br>(ASN.1 notation) | Note                                             |
+|-------------------|----------------------------------|--------------------------------------------------|
+| CAM-DSC_header{   |                                  |                                                  |
+| Message_Type      | OCTET STRING (SIZE(2))           | Value: 0x0014                                    |
+| Message_Length    | OCTET STRING (SIZE(4))           | The length of CAM-DSC_header and CAM-DSC_content |
+| Message_Nonce     | OCTET STRING (SIZE(8))           |                                                  |
+| Protocol_Version  | OCTET STRING (SIZE(1))           |                                                  |
+| Reserved          | OCTET STRING (SIZE(1))           | Value: 0x00                                      |
+
+**Table 7 – The format of CWEGenInfoCnfm message**
+
+| Field description                                 | Type(Length)<br>(ASN.1 notation) | Note |
+|---------------------------------------------------|----------------------------------|------|
+| }                                                 |                                  |      |
+| CAM-DSC content{                                  |                                  |      |
+| H(CWEK)    H(HMAC_KEY)                            | OCTET STRING (SIZE(128))         |      |
+| }                                                 |                                  |      |
+| S(Prv(DSC), (CAM-DSC_header<br>  CAM-DSC_content) | OCTET STRING (SIZE(128))         |      |
+
+# Appendix I
+
+## The functional structures for the CAM and DSC
+
+(This appendix does not form an integral part of this Recommendation.)
+
+### I.1 Functional structure for CAM
+
+Figure I.1 illustrates a functional structure of a CAM. Referring to Figure I.1, the CAM includes a CAM pairing unit, a CAM key generating unit, a CAM encrypting unit and a CAM control unit.
+
+When a preset initialization condition is satisfied, the CAM pairing unit transmits to the DSC a certification request message (DscCertReq message) including the certificate information (CAM ITU-T X.509 CERTIFICATE) of the CAM, and receives a certification response message (DscCertRsp message) including the certificate information (DSC ITU-T X.509 CERTIFICATE) of the DSC from the DSC.
+
+In response to the receipt of the DscCertRsp message, the CAM pairing unit encrypts a key request message including an identifier pair consisting of a CAM identifier (CAM\_ID) and a DSC identifier (DSC\_ID), and transmits the encrypted key request message to a headend. In response, the CAM pairing unit receives a key response message including a KPK, which is a seed key for the identifier pair from the headend. The KPK produces a pseudo-random number sequence using a KeyPairingID value, which is obtained by concatenating the CAM\_ID and the DSC\_ID as a seed value when the KeyPairingID value is validated.
+
+According to the result of verifying validation of the KeyPairingID value by the headend, the key response message to be received by the CAM includes the KPK when the KeyPairingID is validated, and values of all bytes of the KPK included in the key response message are set to '0xff' when the KeyPairingID is invalid.
+
+The CAM key generating unit generates a CWEK message (CWEKGenInfo message), which includes a CWEK and an HMAC\_KEY, based on the KPK, and transmits the generated CWEKGenInfo message to the DSC. The CWEKGenInfo message is encrypted with a public key of the DSC and electronically signed with a private key of the CAM.
+
+Thereafter, when the DSC generates a CWEK and an HMAC\_KEY, the CAM key generating unit receives a CWEK confirmation message (CWEKGenInfoCnfm message) including the generated CWEK and HMAC\_KEY from the DSC. The CWEKGenInfoCnfm message is encrypted with a public key of the CAM, and electronically signed with a private key of the DSC. When the values of all bytes of the KPK transmitted from the CAM are set as '0xff', the DSC terminates the pairing protocol.
+
+When the CAM key generating unit receives the CWEKGenInfoCnfm message, the CAM encrypting unit checks whether the CWEK and the HMAC\_KEY, which are included in the CWEKGenInfoCnfm message, are identical with the CWEK and the HMAC\_KEY that are generated by the CAM key generating unit. If the CWEK and the HMAC\_KEY are the same as those of the CWEKGenInfoCnfm, the CAM shares the generated CWEK and the HMAC\_KEY with the DSC, and the CAM encrypting unit encrypts a control word using CWEK and transmits the encrypted control word and keys to the DSC.
+
+The CAM control unit controls the CAM pairing unit, the CAM key generating unit and the CAM encrypting unit.
+
+![Figure I.1 – CAM functional structure diagram. The diagram shows four functional units: CAM CONTROL UNIT, CAM PAIRING UNIT, CAM KEY GENERATING UNIT, and CAM ENCRYPTING UNIT. The CAM CONTROL UNIT is connected to the CAM PAIRING UNIT and the CAM KEY GENERATING UNIT. The CAM PAIRING UNIT is connected to the CAM ENCRYPTING UNIT and has external connections to CASS and DSC. The CAM KEY GENERATING UNIT is connected to the CAM ENCRYPTING UNIT and has an external connection to DSC. The diagram is labeled J.1002(13)_FI.1.](c914f51f4427bc672dd0526cfc90ebe9_img.jpg)
+
+Figure I.1 – CAM functional structure diagram. The diagram shows four functional units: CAM CONTROL UNIT, CAM PAIRING UNIT, CAM KEY GENERATING UNIT, and CAM ENCRYPTING UNIT. The CAM CONTROL UNIT is connected to the CAM PAIRING UNIT and the CAM KEY GENERATING UNIT. The CAM PAIRING UNIT is connected to the CAM ENCRYPTING UNIT and has external connections to CASS and DSC. The CAM KEY GENERATING UNIT is connected to the CAM ENCRYPTING UNIT and has an external connection to DSC. The diagram is labeled J.1002(13)\_FI.1.
+
+**Figure I.1 – CAM functional structure**
+
+### I.2 Functional structure for DSC
+
+Figure I.2 illustrates a functional structure of a DSC. Referring to Figure I.2, the DSC includes a DSC pairing unit, a DSC key generating unit, a DSC encrypting unit and a DSC control unit.
+
+The DSC pairing unit receives a DscCertReq message including CAM ITU-T X.509 CERTIFICATE of the CAM, and transmits a DscCertRsp including CAM ITU-T X.509 CERTIFICATE of the DSC to the CAM.
+
+When a headend verifies the validation of a KeyPairingID, which is an identifier pair consisting of a CAM identifier and a DSC identifier and is received from the CAM, the DSC pairing unit receives a CWEKGenInfo message including a KPK and an HMAC\_KEY for the KeyPairingID from the CAM. The KPK produces a pseudo-random number sequence using a KeyPairingID value as a seed value when the KeyPairingID value is validated.
+
+![Figure I.2 – DSC functional structure diagram. The diagram shows four functional units: DSC CONTROL UNIT, DSC PAIRING UNIT, DSC KEY GENERATING UNIT, and DSC ENCRYPTING UNIT. The DSC CONTROL UNIT is connected to the DSC PAIRING UNIT and the DSC KEY GENERATING UNIT. The DSC PAIRING UNIT is connected to the DSC ENCRYPTING UNIT and has an external connection to CASS. The DSC KEY GENERATING UNIT is connected to the DSC ENCRYPTING UNIT and has an external connection to CAM. The diagram is labeled J.1002(13)_FI.2.](ab846b81e78dbc8da2a6f9511e2f248a_img.jpg)
+
+Figure I.2 – DSC functional structure diagram. The diagram shows four functional units: DSC CONTROL UNIT, DSC PAIRING UNIT, DSC KEY GENERATING UNIT, and DSC ENCRYPTING UNIT. The DSC CONTROL UNIT is connected to the DSC PAIRING UNIT and the DSC KEY GENERATING UNIT. The DSC PAIRING UNIT is connected to the DSC ENCRYPTING UNIT and has an external connection to CASS. The DSC KEY GENERATING UNIT is connected to the DSC ENCRYPTING UNIT and has an external connection to CAM. The diagram is labeled J.1002(13)\_FI.2.
+
+**Figure I.2 – DSC functional structure**
+
+The DSC key generation unit generates a CKEK using the KPK and the HMAC\_KEY of the received CWEKGenInfo message, then, the DSC key generating unit transmits a CWEKGenInfoCnfm message including the generated CWEK and HMAC\_KEY to the CAM. If all bytes of the KPK received from the CAM are set as '0xff', the DSC key generating unit terminates the pairing protocol. The CWEKGenInfoCnfm message may be encrypted with a public key of the CAM and electronically signed with a private key of the DSC.
+
+The DSC encrypting unit shares the CWEK and the HMAC\_KEY, which are transmitted through the CWEKGenInfoCnfm message to the CAM, with the CAM if the transmitted CWEK and HMAC\_KEY are identical with those of the CAM. In addition, the DSC encrypting unit encrypts data to be transmitted to the CAM, and performs hashed message authentication on a message to be transmitted.
+
+The DSC control unit controls the DSC pairing unit, the DSC key generating unit and the DSC encrypting unit.
+
+# Bibliography
+
+- [b-ITU-T J.93] Recommendation ITU-T J.93 (1998), *Requirements for conditional access in the secondary distribution of digital television on cable television systems.*
+- [b-ITU-T J.122] Recommendation ITU-T J.122 (2007), *Second-generation transmission systems for interactive cable television services – IP cable modems.*
+- [b-ITU-T J.128] Recommendation ITU-T J.128 (2008), *Set-top gateway specification for transmission systems for interactive cable television services.*
+- [b-ITU-T J.193] Recommendation ITU-T J.193 (2004), *Requirements for the next generation of set-top-boxes.*
+- [b-ITU-T J.290] Recommendation ITU-T J.290 (2006), *Next generation set-top box core architecture.*
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+|                 |                                                                                                    |
+|-----------------|----------------------------------------------------------------------------------------------------|
+| Series A        | Organization of the work of ITU-T                                                                  |
+| Series D        | General tariff principles                                                                          |
+| Series E        | Overall network operation, telephone service, service operation and human factors                  |
+| Series F        | Non-telephone telecommunication services                                                           |
+| Series G        | Transmission systems and media, digital systems and networks                                       |
+| Series H        | Audiovisual and multimedia systems                                                                 |
+| Series I        | Integrated services digital network                                                                |
+| <b>Series J</b> | <b>Cable networks and transmission of television, sound programme and other multimedia signals</b> |
+| Series K        | Protection against interference                                                                    |
+| Series L        | Construction, installation and protection of cables and other elements of outside plant            |
+| Series M        | Telecommunication management, including TMN and network maintenance                                |
+| Series N        | Maintenance: international sound programme and television transmission circuits                    |
+| Series O        | Specifications of measuring equipment                                                              |
+| Series P        | Terminals and subjective and objective assessment methods                                          |
+| Series Q        | Switching and signalling                                                                           |
+| Series R        | Telegraph transmission                                                                             |
+| Series S        | Telegraph services terminal equipment                                                              |
+| Series T        | Terminals for telematic services                                                                   |
+| Series U        | Telegraph switching                                                                                |
+| Series V        | Data communication over the telephone network                                                      |
+| Series X        | Data networks, open system communications and security                                             |
+| Series Y        | Global information infrastructure, Internet protocol aspects and next-generation networks          |
+| Series Z        | Languages and general software aspects for telecommunication systems                               |

marked/J/T-REC-J.1015.1-202004-I_PDF-E/raw.md

@@ -0,0 +1,318 @@
+
+
+**ITU-T**
+
+**J.1015.1**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+(04/2020)
+
+SERIES J: CABLE NETWORKS AND TRANSMISSION  
+OF TELEVISION, SOUND PROGRAMME AND OTHER  
+MULTIMEDIA SIGNALS
+
+Conditional access and protection – Exchangeable  
+embedded conditional access and digital rights  
+management solutions
+
+---
+
+**Embedded common interface for exchangeable  
+CA/DRM solutions: The advanced security  
+system – Key ladder block: Authentication of  
+control word-usage rules information and  
+associated data 1**
+
+Recommendation ITU-T J.1015.1
+
+
+
+# Recommendation ITU-T J.1015.1
+
+## **Embedded common interface for exchangeable CA/DRM solutions: The advanced security system – Key ladder block: Authentication of control word-usage rules information and associated data 1**
+
+## Summary
+
+Recommendation ITU-T J.1015.1 is part of a series covering the advanced security system key ladder block for the embedded common interface for exchangeable conditional access/digital rights management (CA/DRM) solutions specification.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T J.1015.1 | 2020-04-23 | 9           | <a href="http://handle.itu.int/11.1002/1000/13837">11.1002/1000/13837</a> |
+
+## Keywords
+
+Conditional access, CA, digital rights management, DRM, swapping.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 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 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 within ITU-T's 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 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 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 possibility 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 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 information and are therefore strongly urged to consult the TSB patent database at <http://www.itu.int/ITU-T/ipr/>.
+
+© ITU 2020
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+|                                                                                     | Page |
+|-------------------------------------------------------------------------------------|------|
+| 1 Scope.....                                                                        | 1    |
+| 2 References.....                                                                   | 1    |
+| 3 Definitions .....                                                                 | 1    |
+| 3.1 Terms defined elsewhere .....                                                   | 1    |
+| 3.2 Terms defined in this Recommendation.....                                       | 1    |
+| 4 Abbreviations and acronyms .....                                                  | 2    |
+| 5 Conventions .....                                                                 | 2    |
+| 6 Authentication of control word-usage rules information and associated data 1..... | 3    |
+| 6.1 Authentication of control word-usage rules information .....                    | 4    |
+| 6.2 Authentication of associated data 1 .....                                       | 4    |
+| Appendix I – Areas for further development.....                                     | 5    |
+| Bibliography.....                                                                   | 7    |
+
+# Introduction
+
+The objective of this Recommendation<sup>1</sup> is to facilitate interoperability and competition in electronic communications services and, in particular, in the market for broadcast and audio-visual devices. However, other technologies are available and may also be appropriate and beneficial depending on the circumstances in Member States.
+
+A content provider encrypts their digital content and uses a **content protection system**<sup>2</sup> in order to protect the content against unauthorized access. A consumer uses a **content receiver** to access protected content. To this end, the **content receiver** contains a chipset that implements one or more content decryption operations. A cryptographic key establishment protocol is used to secure the transport of content decryption keys from the **content protection system** to the chipset. The steps of the protocol that are implemented within the chipset are referred to as a key ladder.
+
+The key ladder and the protocol may also be used to secure the transport of content encryption keys to the chipset. Such keys are required for use cases in which the chipset re-encrypts content. The chipset may implement one or more content encryption operations for this purpose. Personal video recording and exporting protected content to a different **content protection system** are typical examples of content re-encryption use cases. Content decryption keys and content encryption keys are both referred to as **control words (CWs)** throughout this Recommendation.
+
+This Recommendation also specifies an authentication mechanism. This mechanism is closely related to the key ladder and may be used for entity authentication; in other words, this mechanism may be used to authenticate the chipset.
+
+The key ladder and authentication mechanism specified in this Recommendation are agnostic to both the **content protection system** and the **content provider**. This enables a **content provider** to use any compliant **content protection system**, and it enables a consumer to use the **content receiver** for accessing content of any **content provider** that uses a compliant **content protection system**.
+
+A **certification authority** manages a public-key certificate of each chipset in the mechanisms specified in this Recommendation. In particular, the **certification authority** distributes such certificates and certificate revocation information to **content providers** who wish to make use of the key ladder and/or the authentication mechanism. Next, **content providers** use the certificates and certificate revocation information as input to their compliant **content protection system**; as detailed in clause 7 of [ITU-T J.1015]; knowledge of the public key in the certificate of a chipset enables the **content protection system** to generate suitable input messages for the key ladder and authentication mechanism of the chipset.
+
+---
+
+<sup>1</sup> Several areas for further development have been identified in Appendix I
+
+<sup>2</sup> The use of boldface in the text of this Recommendation indicates terms with definitions specific to the context of the embedded common interface that may differ from common use.
+
+# Recommendation ITU-T J.1015.1
+
+## Embedded common interface for exchangeable CA/DRM solutions: The advanced security system – Key ladder block: Authentication of control word-usage rules information and associated data 1
+
+# 1 Scope
+
+This Recommendation specifies a key ladder block for implementation in a chipset of a **content receiver**. The key ladder block comprises a key ladder to secure the transport of **control words** (CWs) to the chipset and an authentication mechanism. This Recommendation also specifies aspects of the personalization of a compliant chipset.
+
+This Recommendation is intended for use by chipset manufacturers.
+
+# 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 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 currently 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.1015] Recommendation ITU-T J.1015 (2020), *Embedded common interface for exchangeable CA/DRM solutions; The advanced security system – Key ladder block*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+None.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 certification authority:** Party that is responsible for managing public-key certificates in an embedded common interface (**ECI ecosystem**). A certification authority is trusted by all other parties in the system to perform operations associated with certificates.
+
+**3.2.2 chipset-ID:** Non-secret number that is used to identify a chipset within an **ECI ecosystem**.
+
+**3.2.3 content protection system:** System in an **ECI ecosystem** that employs cryptographic techniques to manage access to content and services. The term may be interchanged frequently with the alternate Service Protection system. Typical systems of this sort are either conditional access (CA) systems or digital rights management (DRM) systems.
+
+**3.2.4 content provider:** Party that distributes digital content to a **content receiver** in an **ECI ecosystem**.
+
+**3.2.5 content receiver:** Device that is used to access digital content within an **ECI ecosystem**. A **content receiver** contains a chipset with a **content descrambler**.
+
+**3.2.6 content descrambler:** Component in the chipset of an **ECI ecosystem** that is capable of decrypting content. A content descrambler may also be capable of encrypting content (for the purpose of content re-encryption). In this Recommendation content encryption/decryption uses a **symmetric encryption scheme**. For MPEG-2 content, content encryption and decryption are also referred to as scrambling and descrambling, respectively.
+
+**3.2.7 control word:** Secret key used to encrypt and decrypt content within an **ECI ecosystem**. In digital rights management systems, a control word is typically referred to as a content key.
+
+**3.2.8 cryptographic hash function:** Unkeyed cryptographic function in an **ECI ecosystem** that takes data of arbitrary size, referred to as the message, as input and produces an output data block of fixed size, referred to as the message digest. Assumed properties of the **cryptographic hash function** in this Recommendation are that the **cryptographic hash function** behaves as a random function and is second preimage resistant.
+
+**3.2.9 digital signature scheme:** Keyed asymmetric cryptographic scheme that is used to protect the authenticity of data in an **ECI ecosystem**. A **digital signature scheme** consists of a key generation algorithm, a signature generation operation and a signature verification operation. Keys are generated as (secret/private key, public key) pairs. The data is signed using a secret/private key and the corresponding public key is used to verify the signature. The **digital signature scheme** specified in this Recommendation is used to protect the authenticity of messages as defined in [b-ROEL]; in particular, the scheme is not used to provide non-repudiation or source authentication in this Recommendation.
+
+**3.2.10 ECI ecosystem:** A commercial operation consisting of a trust authority and several platforms and **ECI** – compliant customer premises equipment in the field.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|     |                           |
+|-----|---------------------------|
+| AD1 | Associated Data 1         |
+| AK  | Authentication Key        |
+| CA  | Conditional Access        |
+| CW  | Control Word              |
+| DRM | Digital Rights Management |
+| ECI | Embedded Common Interface |
+| ID  | Identifier                |
+| LK  | Link Key                  |
+| SHA | Secure Hash Algorithm     |
+| SPK | Sender Public Key         |
+| SSK | Sender Secret/private Key |
+| T   | Tag                       |
+| URI | Usage Rules Information   |
+
+# 5 Conventions
+
+The use of boldface in the text of this Recommendation indicates terms with definitions specific to the context of the embedded common interface that may differ from those in common use.
+
+# 6 Authentication of control word-usage rules information and associated data 1
+
+Concerning specification details in clause 7 of [ITU-T J.1015], several inputs to the key ladder block are specified, covering among others: CW-URI, AD1,  $\tau_b$ , SPK-URI, SPK<sub>i</sub>, encrypted LK as well as signed Chipset-ID. Some of these inputs, such as LK and Chipset-ID, are encrypted and applied with a digital signature scheme. On the other hand, CW-URI, AD1,  $\tau_b$ , SPK-URI and SPK<sub>i</sub> are delivered without any cryptographic schemes applied. The authentication of these inputs relies on the implicit authentication; in case that a non-authentic value for any of the key ladder inputs is provided, an invalid value of CW is computed and the content cannot be descrambled successfully.
+
+It is possible that a sender can send SPK<sub>i</sub>, SPK-URI and  $\tau_b$  without any cryptographic schemes applied when considering the nature of input characteristics. Especially,  $\tau_b$  can be verified using the Associated Data verification routines and thus applying an explicit authentication scheme is not required.
+
+If it is required by service providers, they can introduce an additional explicit authentication method for CW-URI and AD1 inputs of the key ladder block. Such functionality could allow to achieve an increase of convenience for users as well as operational advantages for service providers.
+
+This Recommendation specifies a way to apply such an authentication scheme to the CW-URI and AD1 when they are inputs to a key ladder block. This can be achieved by applying a digital signature scheme that is already used for Chipset-ID || E(CPK, LK) with SSK. Service operators can individually or collectively authenticate the CW-URI or AD1.
+
+If service operators wish to protect the CW-URI or AD1, then the use of the scheme specified in this Recommendation is required.
+
+See Figure 1.
+
+![Figure 1: Authentication of control word-usage rules information and associated data 1. The diagram shows a Processor on the left and a Key ladder block on the right. The Processor sends several inputs to the Key ladder block: CW-URI || S(SSK, CW-URI) (dashed box), tau_b, AD1 || S(SSK, AD1) (dashed box), SPK-URI, SPK_1, SPK_2, ..., SPK_m, (chipset-ID || E(CPK, LK) || S(SSK_2, chipset-ID || E(CPK, LK)))), and e(LK, r). The Key ladder block contains a verification (V) block that takes SPK_2 and the chipset-ID part of the fifth input to produce E(CPK, LK). This E(CPK, LK) is then decrypted (D) using CSK to produce LK. The LK is then decrypted (d) using e(LK, r) to produce r. The Key ladder block also outputs CW-U and CW. The diagram is labeled J.1015.1(20)_F01.](0b87abe67b21a93777287649c33e755d_img.jpg)
+
+The diagram illustrates the authentication process within a Key ladder block. On the left, a **Processor** provides various inputs. These include **CW-URI || S(SSK, CW-URI)** and **AD1 || S(SSK, AD1)** (both in dashed boxes),  $\tau_b$ , **SPK-URI**, **SPK<sub>1</sub>**, **SPK<sub>2</sub>**, a vertical ellipsis, **SPK<sub>m</sub>**, a complex input **(chipset-ID || E(CPK, LK) || S(SSK<sub>2</sub>, chipset-ID || E(CPK, LK))))**, and **e(LK, r)**. Inside the **Key ladder block**, the **SPK<sub>2</sub>** input and the **chipset-ID** part of the complex input are fed into a verification block **V**, which outputs **E(CPK, LK)**. This output is then processed by a decryption block **D** using **CSK** to produce **LK**. The **LK** is then processed by a decryption block **d** using **e(LK, r)** to produce **r**. The **Key ladder block** also outputs **CW-U** and **CW**. A hash function **h** is shown combining inputs to produce **CW**. The diagram is labeled **J.1015.1(20)\_F01**.
+
+Figure 1: Authentication of control word-usage rules information and associated data 1. The diagram shows a Processor on the left and a Key ladder block on the right. The Processor sends several inputs to the Key ladder block: CW-URI || S(SSK, CW-URI) (dashed box), tau\_b, AD1 || S(SSK, AD1) (dashed box), SPK-URI, SPK\_1, SPK\_2, ..., SPK\_m, (chipset-ID || E(CPK, LK) || S(SSK\_2, chipset-ID || E(CPK, LK)))), and e(LK, r). The Key ladder block contains a verification (V) block that takes SPK\_2 and the chipset-ID part of the fifth input to produce E(CPK, LK). This E(CPK, LK) is then decrypted (D) using CSK to produce LK. The LK is then decrypted (d) using e(LK, r) to produce r. The Key ladder block also outputs CW-U and CW. The diagram is labeled J.1015.1(20)\_F01.
+
+Figure 1 – Authentication of control word-usage rules information and associated data 1
+
+## 6.1 Authentication of control word-usage rules information
+
+#### Compute CW-URI ||signature (sender)
+
+- 1) Sign the bit string CW-URI using  $SSK_i$ ; the signature is denoted by  $S(SSK_i, CW-URI)$ .
+- 2) Append this signature to the bit string CW-URI
+
+#### Retrieve CW-URI (key ladder block)
+
+- 1) Check the length of the input data. If the length of the CW-URI is 64 bits, then the key ladder block shall perform the normal process specified in clause 7.3.1 of [ITU-T J.1015] and abort the CW-URI authentication process. Otherwise, i.e., if the length is more than 64 bits, then take the CW-URI authentication process and go to the next step.
+- 2) Check whether the SPK-URI and the usage rule as specified in clause 7.3.2 of [ITU-T J.1015] allow V to use  $SPK_i$  to verify the signature. If this is not allowed, then the key ladder block shall abort the computations.
+- 3) Use the received (CW-URI ||signature) and  $SPK_i$  to verify the signature. If the signature is invalid, then the key ladder block shall abort the computations.
+- 4) Retrieve CW-URI.
+
+## 6.2 Authentication of associated data 1
+
+#### Compute AD1 ||signature (sender)
+
+- 1) Sign the bit string AD1 using  $SSK_i$ ; the signature is denoted by  $S(SSK_i, AD1)$ .
+- 2) Append this signature to the bit string AD1.
+
+#### Retrieve associated data 1 (key ladder block)
+
+- 1) Check the length of input data. If the length of the AD1 is 256 bits, then the key ladder block shall perform the normal process specified in clause 7.3.1 of [ITU-T J.1015] and abort the AD1 authentication process. Otherwise, i.e., if the length is more than 256 bits, then take the AD1 authentication process and go to the next step.
+- 2) Check whether the SPK-URI and the usage rule as specified in clause 7.3.2 of [ITU-T J.1015] allow V to use  $SPK_i$  to verify the signature. If this is not allowed, then the key ladder block shall abort the computations.
+- 3) Use the received (AD1 ||signature) and  $SPK_i$  to verify the signature. If the signature is invalid, then the key ladder block shall abort the computations.
+- 4) Retrieve AD1.
+
+# Appendix I
+
+## Areas for further development
+
+(This appendix does not form an integral part of this Recommendation.)
+
+It has been identified that this Recommendation needs further development and validation for it to meet the requirements set out in [b-ITU-T J.1010], and that [b-ITU-T J.1010] needs to be updated to reflect the requirements of the MovieLabs Enhanced Content Protection (ECP) specification [b-ECP]. Recommendations [b-ITU-T J.1011], [b-ITU-T J.1012], [b-ITU-T J.1013], [b-ITU-T J.1014], [ITU-T J.1015] and ITU-T J.1015.1 should in the future be updated to reflect those updates to [b-ITU-T J.1010].
+
+A number of ITU Member States, as well as stakeholders from a variety of industries – including manufacturers of devices and electronic components, owners and licensees of copyrighted content, providers of over-the-top (OTT) and linear television services, and providers of conditional access system (CAS) and digital rights management (DRM) solutions – based all around the world have expressed concern that the Embedded Common Interface (ECI) does not fully meet the requirements of ECP, nor wider industry content protection requirements.
+
+More specifically, their concerns were raised in contributions to the ITU-T Study Group 9 (SG9) meeting (16-23 April 2020). Contributions from Israel, Australia, ITU-T Sector Member Samsung, and SG9 Associates Sky Group and MovieLabs proposed that a number of changes be included in the ECI Recommendations, but agreement on them was not reached. These items are inventoried in [b-SG9 Report 17 Ann.1].
+
+They include proposals to:
+
+- 1) Simplify the ECI system by reducing its scope;
+- 2) Remove DRM;
+- 3) Remove the re-encryption of content;
+- 4) Remove software management;
+- 5) Add APIs for secure storage and cryptographic operations;
+- 6) Allow vendor-specific key ladders;
+- 7) Use ITU-T J.1207 TEE requirements;
+- 8) Include TEE implementation for VM;
+- 9) Upgrade the strength of the cryptographic algorithms, e.g., using SHA-384;
+- 10) Use standard certificates, like ITU-T X.509;
+- 11) Reconsider communications between clients;
+- 12) Perform additional liaisons with ETSI;
+- 13) Perform additional peer-review;
+- 14) Explore alternatives to the Trust Authority model;
+- 15) Define further the technical aspects of ECI compliance and robustness rules;
+- 16) Add requirements for diversity, e.g., address space randomization;
+- 17) Add requirements on runtime integrity checking.
+
+These proposals reflect that content protection and the threats of its compromise are continuously evolving. ECI was originally conceived nearly a decade before approval of this ITU-T Recommendation. Systems like ECI need to be assessed on a regular basis against the current state-of-the-art in both attack techniques and industry protection requirements.
+
+Other mechanisms exist to enable interoperability. In particular for the DRM use case, most internet video services have deployed other solutions to provide interoperability and to address their needs.
+
+Further clarity is important as many Member States regard ITU standards as influential sources of guidance for the development of their markets and industries. The list of concerns ensures ECI's implementation in their domestic markets can involve a full appreciation of implications of this ITU-T Recommendation and ensure that the issues are considered when legislation, regulation or market need requiring consumer digital television equipment to be interoperable are being considered. It also ensures that technology equipment manufacturers, who may prefer to use a unique set of requirements or other standards to design the products, can consider these issues in developing products for different markets.
+
+# Bibliography
+
+- [b-ITU-T J.1010] Recommendation ITU-T J.1010 (2016), *Embedded common interface for exchangeable CA/DRM solutions; Use cases and requirements.*
+- [b-ITU-T J.1011] Recommendation ITU-T J.1011 (2016), *Embedded common interface for exchangeable CA/DRM solutions; Architecture, definitions and overview.*
+- [b-ITU-T J.1012] Recommendation ITU-T J.1012 (2020), *Embedded common interface for exchangeable CA/DRM solutions; CA/DRM container, loader, interfaces, revocation.*
+- [b-ITU-T J.1013] Recommendation ITU-T J.1013 (2020), *Embedded common interface for exchangeable CA/DRM solutions; The virtual machine.*
+- [b-ITU-T J.1014] Recommendation ITU-T J.1014 (2020), *Embedded common interface for exchangeable CA/DRM solutions; Advanced security – ECI-specific functionalities.*
+- [b-SG9 Report 17 Ann.1] ITU-T SG9 meeting report, SG9-R17-Annex 1 (2020), Annex 1 to Report 17 of the SG9 fully virtual meeting held 16-23 April 2020.  
+<https://www.itu.int/md/T17-SG09-R-0017/en>
+- [b-ECP] MovieLabs Specification for Enhanced Content Protection – Version 1.2 Available at:  
+[https://movielabs.com/ngvideo/MovieLabs\\_ECP\\_Spec\\_v1.2.pdf](https://movielabs.com/ngvideo/MovieLabs_ECP_Spec_v1.2.pdf)
+
+
+
+
+
+# SERIES OF ITU-T RECOMMENDATIONS
+
+|                 |                                                                                                                                                           |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A        | Organization of the work of ITU-T                                                                                                                         |
+| Series D        | Tariff and accounting principles and international telecommunication/ICT economic and policy issues                                                       |
+| Series E        | Overall network operation, telephone service, service operation and human factors                                                                         |
+| Series F        | Non-telephone telecommunication services                                                                                                                  |
+| Series G        | Transmission systems and media, digital systems and networks                                                                                              |
+| Series H        | Audiovisual and multimedia systems                                                                                                                        |
+| Series I        | Integrated services digital network                                                                                                                       |
+| <b>Series J</b> | <b>Cable networks and transmission of television, sound programme and other multimedia signals</b>                                                        |
+| Series K        | Protection against interference                                                                                                                           |
+| Series L        | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M        | Telecommunication management, including TMN and network maintenance                                                                                       |
+| Series N        | Maintenance: international sound programme and television transmission circuits                                                                           |
+| Series O        | Specifications of measuring equipment                                                                                                                     |
+| Series P        | Telephone transmission quality, telephone installations, local line networks                                                                              |
+| Series Q        | Switching and signalling, and associated measurements and tests                                                                                           |
+| Series R        | Telegraph transmission                                                                                                                                    |
+| Series S        | Telegraph services terminal equipment                                                                                                                     |
+| Series T        | Terminals for telematic services                                                                                                                          |
+| Series U        | Telegraph switching                                                                                                                                       |
+| Series V        | Data communication over the telephone network                                                                                                             |
+| Series X        | Data networks, open system communications and security                                                                                                    |
+| Series Y        | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities                               |
+| Series Z        | Languages and general software aspects for telecommunication systems                                                                                      |

marked/J/T-REC-J.1040-202410-I_PDF-E/raw.md

@@ -0,0 +1,457 @@
+
+
+# Recommendation**ITU-T J.1040 (10/2024)**
+
+SERIES J: Cable networks and transmission of television, sound programme and other multimedia signals
+
+Conditional access and protection – Digital rights management for video and audio content distribution
+
+---
+
+# **Digital rights management for video and audio content distribution – Requirements**
+
+![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg)
+
+The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with white lines representing latitude and longitude, and the letters 'ITU' in a bold, blue, sans-serif font overlaid on the globe.
+
+ITU logo
+
+## ITU-T J-SERIES RECOMMENDATIONS
+
+### **Cable networks and transmission of television, sound programme and other multimedia signals**
+
+|                                                                                                 |                      |
+|-------------------------------------------------------------------------------------------------|----------------------|
+| GENERAL RECOMMENDATIONS                                                                         | J.1-J.9              |
+| GENERAL SPECIFICATIONS FOR ANALOGUE SOUND-PROGRAMME TRANSMISSION                                | J.10-J.19            |
+| PERFORMANCE CHARACTERISTICS OF ANALOGUE SOUND-PROGRAMME CIRCUITS                                | J.20-J.29            |
+| EQUIPMENT AND LINES USED FOR ANALOGUE SOUND-PROGRAMME CIRCUITS                                  | J.30-J.39            |
+| DIGITAL ENCODERS FOR ANALOGUE SOUND-PROGRAMME SIGNALS - PART 1                                  | J.40-J.49            |
+| DIGITAL TRANSMISSION OF SOUND-PROGRAMME SIGNALS                                                 | J.50-J.59            |
+| CIRCUITS FOR ANALOGUE TELEVISION TRANSMISSION                                                   | J.60-J.69            |
+| ANALOGUE TELEVISION TRANSMISSION OVER METALLIC LINES AND INTERCONNECTION WITH RADIO-RELAY LINKS | J.70-J.79            |
+| DIGITAL TRANSMISSION OF TELEVISION SIGNALS                                                      | J.80-J.89            |
+| ANCILLARY DIGITAL SERVICES FOR TELEVISION TRANSMISSION                                          | J.90-J.99            |
+| OPERATIONAL REQUIREMENTS AND METHODS FOR TELEVISION TRANSMISSION                                | J.100-J.109          |
+| INTERACTIVE SYSTEMS FOR DIGITAL TELEVISION DISTRIBUTION (DOCSIS FIRST AND SECOND GENERATIONS)   | J.110-J.129          |
+| TRANSPORT OF MPEG-2 SIGNALS ON PACKETIZED NETWORKS                                              | J.130-J.139          |
+| MEASUREMENT OF THE QUALITY OF SERVICE - PART 1                                                  | J.140-J.149          |
+| DIGITAL TELEVISION DISTRIBUTION THROUGH LOCAL SUBSCRIBER NETWORKS                               | J.150-J.159          |
+| IPCABLECOM (MGCP-BASED) - PART 1                                                                | J.160-J.179          |
+| DIGITAL TRANSMISSION OF TELEVISION SIGNALS - PART 1                                             | J.180-J.189          |
+| CABLE MODEMS AND HOME NETWORKING                                                                | J.190-J.199          |
+| APPLICATION FOR INTERACTIVE DIGITAL TELEVISION - PART 1                                         | J.200-J.209          |
+| INTERACTIVE SYSTEMS FOR DIGITAL TELEVISION DISTRIBUTION (DOCSIS THIRD TO FIFTH GENERATIONS)     | J.210-J.229          |
+| MULTI-DEVICE SYSTEMS FOR CABLE TELEVISION                                                       | J.230-J.239          |
+| MEASUREMENT OF THE QUALITY OF SERVICE - PART 2                                                  | J.240-J.249          |
+| DIGITAL TELEVISION DISTRIBUTION THROUGH LOCAL SUBSCRIBER NETWORKS                               | J.250-J.259          |
+| IPCABLECOM (MGCP-BASED) - PART 2                                                                | J.260-J.279          |
+| DIGITAL TRANSMISSION OF TELEVISION SIGNALS - PART 2                                             | J.280-J.289          |
+| CABLE SET-TOP BOX                                                                               | J.290-J.299          |
+| APPLICATION FOR INTERACTIVE DIGITAL TELEVISION - PART 2                                         | J.300-J.309          |
+| MEASUREMENT OF THE QUALITY OF SERVICE - PART 3                                                  | J.340-J.349          |
+| IPCABLECOM2 (SIP-BASED) - PART 1                                                                | J.360-J.379          |
+| DIGITAL TRANSMISSION OF TELEVISION SIGNALS - PART 3                                             | J.380-J.389          |
+| MEASUREMENT OF THE QUALITY OF SERVICE - PART 4                                                  | J.440-J.449          |
+| IPCABLECOM2 (SIP-BASED) - PART 2                                                                | J.460-J.479          |
+| DIGITAL TRANSMISSION OF TELEVISION SIGNALS - PART 4                                             | J.480-J.489          |
+| TRANSPORT OF LARGE SCREEN DIGITAL IMAGERY                                                       | J.600-J.699          |
+| SECONDARY DISTRIBUTION OF IPTV SERVICES                                                         | J.700-J.799          |
+| MULTIMEDIA OVER IP IN CABLE                                                                     | J.800-J.899          |
+| TRANSMISSION OF 3-D TV SERVICES                                                                 | J.900-J.999          |
+| CONDITIONAL ACCESS AND PROTECTION                                                               | J.1000-J.1099        |
+| Renewable conditional access system                                                             | J.1000-J.1004        |
+| Digital rights management for cable television multiscreen service                              | J.1005-J.1009        |
+| Exchangeable embedded conditional access and digital rights management solutions                | J.1010-J.1019        |
+| Downloadable system for multi-CA/DRM service of mobile broadcasting                             | J.1020-J.1025        |
+| Downloadable conditional access system for unidirectional networks                              | J.1026-J.1029        |
+| Downloadable conditional access system for bidirectional networks                               | J.1031-J.1035        |
+| Factual subscriber-base reporting and protected content delivery in conditional access systems  | J.1036-J.1039        |
+| <b>Digital rights management for video and audio content distribution</b>                       | <b>J.1040-J.1044</b> |
+| SWITCHED DIGITAL VIDEO OVER CABLE NETWORKS                                                      | J.1100-J.1119        |
+| SMART TV OPERATING SYSTEM                                                                       | J.1200-J.1209        |
+| IP VIDEO BROADCAST                                                                              | J.1210-J.1219        |
+| CABLE SET-TOP BOX - PART 2                                                                      | J.1290-J.1299        |
+| CLOUD-BASED CONVERGED MEDIA SERVICES FOR IP AND BROADCAST CABLE TELEVISION                      | J.1300-J.1309        |
+| CLOUD-BASED SERVICES FOR IP DELIVERY OVER INTEGRATED BROADBAND CABLE NETWORK                    | J.1310-J.1319        |
+| TELEVISION TRANSPORT NETWORK AND SYSTEM DEPLOYMENT IN DEVELOPING COUNTRIES                      | J.1400-J.1409        |
+| ARTIFICIAL INTELLIGENCE (AI) ASSISTED CABLE NETWORKS                                            | J.1600-J.1649        |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+## Recommendation ITU-T J.1040
+
+## Digital rights management for video and audio content distribution – Requirements
+
+## Summary
+
+The service requirements for the application of new generation video and audio technologies, along with new video service models coupled with a diverse range of consumer devices used for the reception of content, bring new demands and opportunities to the video industry, especially broadcast and television video services, and raise higher requirements on digital rights management (DRM). The DRM system not only needs to have well defined security levels to meet the content protection requirements of different quality and different distribution window periods, but also needs to have sufficient platform compatibility to cover various terminal devices. In addition, higher encryption/decryption efficiency and encryption/decryption modes decoupled from content encapsulation are required to match the rapid development and transformation of video and audio technologies. In addition, an interoperability mechanism is required to achieve a more open DRM ecosystem.
+
+This Recommendation is part 1 of a multiparty deliverable composed of four parts. Part 1 provides the requirements of digital rights management for video and audio content distribution, including DRM service requirements and DRM client requirements.
+
+### History \*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T J.1040   | 2024-10-29 | 9           | 11.1002/1000/16192 |
+
+### Keywords
+
+Digital rights management, video and audio content distribution, video and audio content protection.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and 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 basis.
+
+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 Resolution 1.
+
+In some areas of information technology which fall within ITU-T's 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 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 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 possibility 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 Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, 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 appropriate ITU-T databases available via the ITU-T website at <http://www.itu.int/ITU-T/ipr/>.
+
+© ITU 2025
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+|                                               | Page |
+|-----------------------------------------------|------|
+| 1 Scope .....                                 | 1    |
+| 2 References.....                             | 1    |
+| 3 Definitions .....                           | 1    |
+| 3.1 Terms defined elsewhere .....             | 1    |
+| 3.2 Terms defined in this Recommendation..... | 1    |
+| 4 Abbreviations and acronyms .....            | 2    |
+| 5 Conventions .....                           | 2    |
+| 6 Scenarios.....                              | 3    |
+| 6.1 Linear programme scenario .....           | 3    |
+| 6.2 VoD scenario .....                        | 3    |
+| 7 Business requirements analysis .....        | 3    |
+| 7.1 Service provider mode.....                | 3    |
+| 7.2 Content provider mode .....               | 4    |
+| 8 Technical requirements.....                 | 4    |
+| 8.1 Overview .....                            | 4    |
+| 8.2 Key requirements.....                     | 5    |
+| 8.3 DRM service.....                          | 6    |
+| 8.4 DRM client .....                          | 7    |
+| Bibliography.....                             | 9    |
+
+
+
+## Recommendation ITU-T J.1040
+
+## Digital rights management for video and audio content distribution – Requirements
+
+# 1 Scope
+
+This Recommendation is part 1 of a multiparty deliverable composed of four parts. Part 1 depicts the content protection requirements from different scenarios, and describes the requirements of digital rights management for video and audio content distribution, including content encryption requirements, key management requirements, content authorization requirements and DRM client requirements.
+
+## 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 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 currently 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.
+
+None.
+
+# 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 authorization** [b-ITU-T J.260]: The act of determining if a particular privilege, such as access to telecommunications resource, can be granted to the presenter of a particular credential.
+
+**3.1.2 content encryption key** [b-ITU-T Y.4500.3]: Symmetric key used to encrypt plaintext to produce the ciphertext and generate a message integrity check (MIC).
+
+**3.1.3 content provider** [b-ITU-T Y.1910]: The entity that owns or is licenced to sell content or content assets.
+
+**3.1.4 digital rights management** [b-ITU-T X.1193]: A synonym for service and content protection or content protection, depending upon the context of use.
+
+**3.1.5 service provider** [b-ITU-T M.1400]: A general reference to an operator that provides telecommunication services to customers and other users, either on a tariff or contract basis. A service provider may or may not operate a network. A service provider may or may not be a customer of another service provider. See clause 1.4.6 of [ITU-T M.3320]
+
+**3.1.6 video on demand (VoD)** [b-ITU-T Y.1910]: A service in which the end user can, on demand, select and view video content and where the end user can control the temporal order in which the video content is viewed (e.g., the ability to start the viewing, pause, fast forward, rewind, etc.).
+
+### 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 digital rights management (DRM) content:** Digital media content managed by DRM technology.
+
+**3.2.2 digital rights management (DRM) client:** A trusted entity in the digital media content playback device responsible for execution of DRM content-related permissions and restrictions.
+
+**3.2.3 digital rights management (DRM) server:** The entity that provides the licence service to the DRM client.
+
+**3.2.4 licence:** A description of control information such as access permissions, usage rules, and keys for digital media content.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|         |                                              |
+|---------|----------------------------------------------|
+| AVS     | Advanced Video Coding Standard               |
+| CEK     | Content Encryption Key                       |
+| CMAF    | Common Media Application Format              |
+| DASH    | Dynamic Adaptive Streaming over HTTP         |
+| DRM     | Digital Rights Management                    |
+| DRMVACD | DRM for Video and Audio Content Distribution |
+| HLS     | HTTP Live Streaming                          |
+| IPTV    | Internet Protocol Television                 |
+| PKI     | Public Key Infrastructure                    |
+| SDK     | Software Development Kit                     |
+| STB     | Set-Top-Box                                  |
+| TS      | Transport Stream                             |
+| VoD     | Video-on-Demand                              |
+
+## 5 Conventions
+
+In this Recommendation:
+
+The keywords "**is required to**" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this Recommendation 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 from 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 vendor's implementation must provide 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 this Recommendation, the words shall, shall not, should 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 normative intent.
+
+# 6 Scenarios
+
+The application scenarios of digital rights management for video and audio content distribution include linear programme and video-on-demand (VoD). Linear programme is classified into cable linear programme and IPTV linear programme. VoD is classified into cable digital TV VoD, IPTV VoD, Internet TV VoD and Internet video service.
+
+## 6.1 Linear programme scenario
+
+In a linear programme scenario, a television station or the like, distributes a produced programme to a distribution channel such as a cable channel or an IPTV channel in a channel manner, and the distribution channel sends a linear programme to a terminal such as a set-top-box (STB) or a smart television.
+
+In a cable linear programme scenario, a cable TV operator receives a linear programme from a television station, and broadcasts the programme to a cable TV STB through the cable TV network. The STB demodulates a cable TV modulation signal to get linear programme transport streams (TSs), and decodes and plays the streams.
+
+In an IPTV linear programme scenario, the linear programme from the TV station is sent to the IPTV service provider. The IPTV service provider distributes the linear programme to the IPTV STB in IP multicast mode through the IPTV network. The IPTV STB receives multicast IP signals to get linear programme TSs, decodes and plays the streams.
+
+## 6.2 VoD scenario
+
+The VoD scenario refers to a scenario in which a user browses a content list provided by a service provider via a STB, a smart television, etc., and selects content to play. VoD scenarios can be classified into the following types: digital cable TV VoD, IPTV VoD, Internet TV VoD and Internet video service.
+
+## 7 Business requirements analysis
+
+The digital rights management for video and audio content distribution have two application modes: encryption and authorization by service provider, and encryption and authorization by content provider.
+
+### 7.1 Service provider mode
+
+In service provider mode, the service provider receives linear programme content and VoD content in a secure manner and encrypts the content. The terminal gets the linear programme content and VoD content by obtaining the authorization of the content from the service provider, as shown in Figure 1.
+
+![Figure 1: Service provider mode. A flowchart showing the interaction between a Content provider and a Service provider. The Content provider has 'Content production' leading to 'Content provision'. The Service provider has 'Content receiving', 'Content encryption', 'Content distribution', and 'Content authorization'. Arrows show content flow from production to receiving, then through encryption and distribution to a Terminal. The Business operation supporting system and Content authorization are connected to the Terminal and the Service provider's internal processes. J.1040(24) is noted in the bottom right.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg)
+
+```
+
+graph LR
+    subgraph Content_provider [Content provider]
+        CP[Content production] --> CV[Content provision]
+    end
+    subgraph Service_provider [Service provider]
+        CR[Content receiving] --> CE[Content encryption]
+        CE --> CD[Content distribution]
+        CA[Content authorization] <--> CE
+    end
+    CV --> CR
+    CD --> T[Terminal]
+    BOS[Business operation supporting system] --> T
+    CA --> T
+    T --> BOS
+    J104024[J.1040(24)]
+  
+```
+
+Figure 1: Service provider mode. A flowchart showing the interaction between a Content provider and a Service provider. The Content provider has 'Content production' leading to 'Content provision'. The Service provider has 'Content receiving', 'Content encryption', 'Content distribution', and 'Content authorization'. Arrows show content flow from production to receiving, then through encryption and distribution to a Terminal. The Business operation supporting system and Content authorization are connected to the Terminal and the Service provider's internal processes. J.1040(24) is noted in the bottom right.
+
+Figure 1 – Service provider mode
+
+## 7.2 Content provider mode
+
+In content provider mode, the content provider encrypts the linear programme content and VoD content, and the terminal gets the linear programme content and VoD content from the service provider. The terminal obtains the authorization of the content from the content provider, as shown in Figure 2.
+
+![Figure 2: Content provider mode. A flowchart showing the interaction between a Content provider and a Service provider. The Content provider has 'Content production', 'Content encryption', 'Content provision', and 'Content authorization'. The Service provider has 'Content receiving', 'Content distribution', and 'Business operation supporting system'. Arrows show content flow from production to encryption, then to provision, then to the Service provider's receiving, and finally to distribution and the Terminal. The Content authorization is connected to the Terminal. J.1040(24) is noted in the bottom right.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg)
+
+```
+
+graph LR
+    subgraph Content_provider [Content provider]
+        CP[Content production] --> CE[Content encryption]
+        CE --> CV[Content provision]
+        CA[Content authorization] <--> CE
+    end
+    subgraph Service_provider [Service provider]
+        CR[Content receiving] --> CD[Content distribution]
+        BOS[Business operation supporting system]
+    end
+    CV --> CR
+    CD --> T[Terminal]
+    CA --> T
+    T --> BOS
+    J104024[J.1040(24)]
+  
+```
+
+Figure 2: Content provider mode. A flowchart showing the interaction between a Content provider and a Service provider. The Content provider has 'Content production', 'Content encryption', 'Content provision', and 'Content authorization'. The Service provider has 'Content receiving', 'Content distribution', and 'Business operation supporting system'. Arrows show content flow from production to encryption, then to provision, then to the Service provider's receiving, and finally to distribution and the Terminal. The Content authorization is connected to the Terminal. J.1040(24) is noted in the bottom right.
+
+Figure 2 – Content provider mode
+
+## 8 Technical requirements
+
+### 8.1 Overview
+
+The application and deployment of DRM technology for the video and audio content distribution requires the collaboration among various players: video and audio content provider, service provider, smart terminal device manufacturer, chipset manufacturer, DRM client software development kit (SDK) provider, trust authority, evaluation and certification agency, etc. The overall framework is shown in Figure 3.
+
+![Figure 3 – Overall framework of application and deployment of DRM technology. The diagram shows a top section with content providers and operators (Internet video service operator, Internet TV service operator, IPTV operator, Cable operator) connected to networks (Internet, IPTV network, Cable network), which then connect to various devices (Smart TV, STB, Mobile, PC, IPTV STB, Cable STB). Below this is a dashed box containing the DRM service (Content encryption, Key management, Key gateway, Content authorization), DRM client, Evaluation and certification, Trust authority, and DRM client SDK. Arrows indicate the flow of data and control between these components.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg)
+
+J.1040(24)
+
+Figure 3 – Overall framework of application and deployment of DRM technology. The diagram shows a top section with content providers and operators (Internet video service operator, Internet TV service operator, IPTV operator, Cable operator) connected to networks (Internet, IPTV network, Cable network), which then connect to various devices (Smart TV, STB, Mobile, PC, IPTV STB, Cable STB). Below this is a dashed box containing the DRM service (Content encryption, Key management, Key gateway, Content authorization), DRM client, Evaluation and certification, Trust authority, and DRM client SDK. Arrows indicate the flow of data and control between these components.
+
+**Figure 3 – Overall framework of application and deployment of DRM technology**
+
+The core functions of the DRM service, such as content encryption, key management, key gateway, and content authorization, are deployed to encrypt and authorize linear programme content and VoD content.
+
+- The content encryption function uses the content encryption key (CEK) to encrypt the video and audio content.
+- The key management function is responsible for synchronizing the CEK to the key gateway after receiving the CEK.
+- The key gateway function stores the CEK confidentially after receiving the synchronized key, and serves the key query of the content authorization module.
+- The content authorization function generates licence responses with a licence object containing the CEK and key usage rules based on DRM client's request, which is securely sent to the trusted DRM client.
+
+After the DRM client receives the licence object, it decrypts the CEK according to the key usage rules, and decrypts the content with the CEK to play. The DRM service and the DRM client establish a trust relationship based on public key infrastructure (PKI) technology, and perform secure communication with each other based on this trust relationship.
+
+## 8.2 Key requirements
+
+The key requirements of digital rights management for video and audio content distribution includes:
+
+[DRM-GRL-1] Digital rights management for video and audio content distribution (DRMVACD) is required to support elementary stream level content encryption mechanisms, which shall not affect the conversion of content encapsulation formats to support different delivery and transmission modes.
+
+- [DRM-GRL-2] DRMVACD is recommended to support linear programme encryption, key distribution and synchronization.
+- [DRM-GRL-3] DRMVACD is recommended to support new video coding formats, such as advanced video coding standard (AVS).
+- [DRM-GRL-4] DRMVACD is required to have a client-server communication protocol with interoperability of a server and a client from different implementers.
+- [DRM-GRL-5] DRMVACD is required to provide standard DRM client function interfaces and execution environment interfaces to facilitate the integration of a DRM client.
+- [DRM-GRL-6] DRMVACD is required to have compliance and robustness rules.
+
+## 8.3 DRM service
+
+### 8.3.1 General security requirements of a DRM service
+
+The general security requirements are as follows:
+
+- [DRM-SRV-1] The cryptographic functions such as key generation, encryption, decryption, and signature is required to be implemented in the cryptographic module.
+- [DRM-SRV-2] The private key, content encryption key, session key and temporary key is required to not be disclosed in plaintext outside the cryptographic module.
+- [DRM-SRV-3] The cryptographic module is recommended to be certificated for security by a trusted and certified third party.
+- [DRM-SRV-4] When the cryptographic module is removed, service is required to be stopped.
+- [DRM-SRV-5] A software component integrity verification mechanism is required to be provided. When a software component is tampered, service shall stop.
+- [DRM-SRV-6] DRM service of DRMVACD is required to support security log recording and log review. All operations, including software upgrade, software component modification, unauthorized tampering, and cryptographic module removal, are required to be securely recorded.
+- [DRM-SRV-7] A security upgrade mechanism is required to be available to rectify security risks or vulnerabilities in a timely manner.
+
+### 8.3.2 Content encryption
+
+The requirements for a content encryption function are as follows:
+
+- [DRM-SRV-8] A content encryption function in a DRM service of DRMVACD is required to support elementary stream level content encryption mechanism, which is required to not affect the conversion of content encapsulation formats to support different delivery and transmission modes.
+- [DRM-SRV-9] A content encryption function in a DRM service of DRMVACD is recommended to support encapsulation formats of linear programme content such as TS, HTTP live streaming (HLS), dynamic adaptive streaming over HTTP (DASH), and common media application format (CMAF).
+- [DRM-SRV-10] A content encryption function in a DRM service of DRMVACD is recommended to support video encoding formats of linear programme content such as AVS+, AVS2, AVS3, ITU-T H.264, and ITU-T H.265.
+- [DRM-SRV-11] A content encryption function in a DRM service of DRMVACD is recommended to support encapsulation formats of VoD content such as TS, HLS, DASH, and CMAF.
+
+- [DRM-SRV-12] A content encryption function in a DRM service of DRMVACD is recommended to support video encoding formats of VoD content such as AVS+, AVS2, AVS3, H.264, and H.265.
+- [DRM-SRV-13] Content encryption keys is required to be applied through key management.
+- [DRM-SRV-14] The content encryption key for linear programme content encryption is required to be updated at a configurable frequency.
+- [DRM-SRV-15] The linear programme content encryption latency is recommended to be less than 500ms.
+- [DRM-SRV-16] A content encryption function in a DRM service of DRMVACD is recommended to avoid 00 00 00, 00 00 01, 00 00 02, and 00 00 03 in the encoded data after content encryption. The initial vector may be changed to prevent the emulation of the start code.
+
+### 8.3.3 Key management
+
+The requirements for the key management function are as follows:
+
+- [DRM-SRV-17] A key management function in a DRM service of DRMVACD is required to receive and process content encryption key applications.
+- [DRM-SRV-18] A key management function in a DRM service of DRMVACD is required to support the secure storage of content encryption keys.
+- [DRM-SRV-19] Content encryption keys are required to be synchronized to the key gateway.
+
+### 8.3.4 Key gateway
+
+The requirements for the key gateway function are as follows:
+
+- [DRM-SRV-20] A key gateway function in a DRM service of DRMVACD is required to receive and process content encryption key requests from the key management function.
+- [DRM-SRV-21] A key gateway function in a DRM service of DRMVACD is required to support the secure storage of content encryption keys.
+- [DRM-SRV-22] A key gateway function in a DRM service of DRMVACD is required to support receiving and processing the content encryption key requests sent by the content authorization.
+
+### 8.3.5 Content authorization
+
+The requirements for the content authorization function are as follows:
+
+- [DRM-SRV-23] A content authorization function in a DRM service of DRMVACD is required to support receiving and processing the content authorization licence request sent by the DRM client.
+- [DRM-SRV-24] The content encryption key is required to request from the key gateway function.
+
+## 8.4 DRM client
+
+The DRM client is integrated with an audio or video player. The DRM client receives content authorization messages from the DRM server and decrypts content based on the playback rules specified in the content authorization messages to ensure the security of video or audio content during decryption, decoding and playback.
+
+DRM client security levels are classified into software security level, hardware security level, and enhanced hardware security level. The security requirements of DRM clients at each security level are listed in Table 1.
+
+**Table 1 – DRM client security level requirements**
+
+| <b>number</b> | <b>DRM client security level</b> | <b>Security requirements</b>                                                                                                                                                                                |
+|---------------|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1             | Software security level          | Parts or all of the DRM client execution environment is required to be implemented based on the software security mechanism.                                                                                |
+| 2             | Hardware security level          | The DRM client execution environment is required to be implemented based on the hardware security mechanism.                                                                                                |
+| 3             | Enhanced hardware security level | Based on the hardware security level, the execution environment of the DRM client is required to have capabilities including side channel attack resistance and session-based forensic watermark insertion. |
+
+Generally, video and audio content should be authorized based on the security level of the DRM client. The higher the security level of the DRM client, the higher the quality or commercial value of the video and audio content that can be decrypted and played. 4K and higher content is generally authorized only to the enhanced hardware security level DRM client for decryption and playback. 1080p content should be decrypted and played only by DRM clients of the hardware security level or higher. Software-based DRM clients should decrypt and play only content of 720p or lower.
+
+## Bibliography
+
+- [b-ITU-T J.260] Recommendation ITU-T J.260 (2005), *Requirements for preferential telecommunications over IPCablecom networks.*
+- [b-ITU-T M.1400] Recommendation ITU-T M.1400 (2015), *Designations for interconnections among operator's networks.*
+- [b-ITU-T X.1193] Recommendation ITU-T X.1193 (2011), *Key management framework for secure internet protocol television (IPTV) services.*
+- [b-ITU-T Y.1910] Recommendation ITU-T Y.1910 (2008), *IPTV functional architecture.*
+- [b-ITU-T Y.4500.3] Recommendation ITU-T Y.4500.3 (2023), *oneM2M - Security solutions.*
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+|                 |                                                                                                                                                           |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A        | Organization of the work of ITU-T                                                                                                                         |
+| Series D        | Tariff and accounting principles and international telecommunication/ICT economic and policy issues                                                       |
+| Series E        | Overall network operation, telephone service, service operation and human factors                                                                         |
+| Series F        | Non-telephone telecommunication services                                                                                                                  |
+| Series G        | Transmission systems and media, digital systems and networks                                                                                              |
+| Series H        | Audiovisual and multimedia systems                                                                                                                        |
+| Series I        | Integrated services digital network                                                                                                                       |
+| <b>Series J</b> | <b>Cable networks and transmission of television, sound programme and other multimedia signals</b>                                                        |
+| Series K        | Protection against interference                                                                                                                           |
+| Series L        | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M        | Telecommunication management, including TMN and network maintenance                                                                                       |
+| Series N        | Maintenance: international sound programme and television transmission circuits                                                                           |
+| Series O        | Specifications of measuring equipment                                                                                                                     |
+| Series P        | Telephone transmission quality, telephone installations, local line networks                                                                              |
+| Series Q        | Switching and signalling, and associated measurements and tests                                                                                           |
+| Series R        | Telegraph transmission                                                                                                                                    |
+| Series S        | Telegraph services terminal equipment                                                                                                                     |
+| Series T        | Terminals for telematic services                                                                                                                          |
+| Series U        | Telegraph switching                                                                                                                                       |
+| Series V        | Data communication over the telephone network                                                                                                             |
+| Series X        | Data networks, open system communications and security                                                                                                    |
+| Series Y        | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities                               |
+| Series Z        | Languages and general software aspects for telecommunication systems                                                                                      |

marked/J/T-REC-J.1103-201508-I_PDF-E/raw.md

@@ -0,0 +1,891 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**J.1103**
+
+(08/2015)
+
+SERIES J: CABLE NETWORKS AND TRANSMISSION  
+OF TELEVISION, SOUND PROGRAMME AND OTHER  
+MULTIMEDIA SIGNALS
+
+Switched digital video over cable networks
+
+---
+
+**Transmission specification for IP-based  
+switched digital video using data over cable  
+service interface specifications**
+
+Recommendation ITU-T J.1103
+
+
+
+# Recommendation ITU-T J.1103
+
+# Transmission specification for IP-based switched digital video using data over cable service interface specifications
+
+## Summary
+
+Recommendation ITU-T J.1103 describes the transmission specifications of IP-based switched digital video (SDV) using data over cable service interface specifications (DOCSIS) in a digital cable network. The cable broadcasting system has been changed to use resources efficiently and to transmit said resources in such a way that the varying needs of subscribers are easily accommodated. The transmission specifications described in this Recommendation are defined according to Recommendation ITU-T J.1101, *Functional requirements for IP-based switched digital video using data over cable service interface specifications*. These specifications are designed to maintain quality of service (QoS) while using bandwidth effectively in a hybrid fibre/coaxial (HFC) network environment.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T J.1103   | 2015-08-13 | 9           | <a href="http://handle.itu.int/11.1002/1000/12572">11.1002/1000/12572</a> |
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 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 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 within ITU-T's 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 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 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 possibility 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 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 information and are therefore strongly urged to consult the TSB patent database at <http://www.itu.int/ITU-T/ipr/>.
+
+© ITU 2015
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+|                                                         | Page |
+|---------------------------------------------------------|------|
+| 1 Scope.....                                            | 1    |
+| 2 References.....                                       | 1    |
+| 3 Definitions .....                                     | 1    |
+| 3.1 Terms defined elsewhere .....                       | 1    |
+| 3.2 Terms defined in this Recommendation.....           | 1    |
+| 4 Abbreviations and acronyms .....                      | 2    |
+| 5 Conventions .....                                     | 3    |
+| 6 IP-based SDV reference model .....                    | 3    |
+| 6.1 Transmission function .....                         | 4    |
+| 6.2 Subscriber function.....                            | 4    |
+| 7 Transmission specification .....                      | 5    |
+| 7.1 Service flow processing.....                        | 5    |
+| 7.2 Packet scheduling .....                             | 6    |
+| 7.3 MAC header processing .....                         | 7    |
+| 7.4 MPEG-2 TS convergence.....                          | 12   |
+| Annex A – The service flow classification process ..... | 15   |
+| Annex B – Examples of MPEG-2 TS encapsulation .....     | 19   |
+| Bibliography.....                                       | 21   |
+
+
+
+# Recommendation ITU-T J.1103
+
+# Transmission specification for IP-based switched digital video using data over cable service interface specifications
+
+# 1 Scope
+
+This Recommendation defines the transmission specifications of the IP-based switched digital video (SDV) using data over cable service interface specification (DOCSIS). The transmission specifications described in this Recommendation are defined according to [[ITU-T J.1101](#)]. The transmission specifications described in this Recommendation are defined as follows:
+
+- multicast service flow processing transmission specifications
+- multicast packet scheduling transmission specifications
+- media access control (MAC) header processing transmission specifications
+- MPEG-2 TS convergence transmission specifications.
+
+# 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 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 currently 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.210](#)] Recommendation ITU-T J.210 (2006), *Downstream RF interface for cable modem termination systems*.
+
+[[ITU-T J.222.1](#)] Recommendation ITU-T J.222.1 (2007), *Third-generation transmission systems for interactive cable television services – IP cable modems: Physical layer specification*.
+
+[[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 requirements 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 SDV [[ITU-T J.1101](#)]:** A service mechanism which provides interfaces 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:
+
+|        |                                                  |
+|--------|--------------------------------------------------|
+| CCP    | Channel Charge Protocol                          |
+| CM     | Cable Modem                                      |
+| CMTS   | Cable Modem Termination System                   |
+| CRC    | Cyclic Redundancy Check                          |
+| DA     | Destination Address                              |
+| DC     | Downstream Channel                               |
+| DCID   | Downstream Channel Identifier                    |
+| DEPI   | Downstream External PHY Interface                |
+| DMPI   | DOCSIS MAC-PHY Interface                         |
+| DOCSIS | Data Over Cable Service Interface Specifications |
+| DRFI   | Downstream Radio Frequency Interface             |
+| DS     | Downstream                                       |
+| DSID   | Downstream Service Identifier                    |
+| EH     | Extended Header                                  |
+| EHDR   | Extended MAC Header                              |
+| FC     | Frame Control                                    |
+| FEC    | Forward Error Correction                         |
+| FTP    | File Transfer Protocol                           |
+| GBE    | Giga Bit Ethernet                                |
+| HCS    | Header Check Sequence                            |
+| HFC    | Hybrid Fibre/Coaxial                             |
+| IGMP   | Internet Group Management Protocol               |
+| IP     | Internet Protocol                                |
+| IPC    | Inter Process Communications                     |
+| MAC    | Media Access Control                             |
+| M-CMTS | Modular Cable Modem Termination System           |
+| MDD    | MAC Domain Descriptor                            |
+| MIB    | Management Information Base                      |
+| MPEG   | Moving Picture Experts Group                     |
+| MSB    | Most Significant Bit                             |
+| NSI    | Network Service Interface                        |
+| PDU    | Protocol Data Unit                               |
+| PHY    | Physical Layer                                   |
+| PID    | Packet Identifier                                |
+| PUSI   | Payload Unit Start Indicator                     |
+
+|      |                                 |
+|------|---------------------------------|
+| QAM  | Quadrature Amplitude Modulation |
+| QoS  | Quality of Service              |
+| RPC  | Remote Procedure Call           |
+| SA   | Source Address                  |
+| SDV  | Switched Digital Video          |
+| SF   | Service Flow                    |
+| SFID | Service Flow Identifier         |
+| SID  | Service Identifier              |
+| SIP  | Session Initiation Protocol     |
+| STB  | Set-Top Box                     |
+| VSI  | Video Service Interface         |
+
+# 5 Conventions
+
+In this Recommendation:
+
+The keywords "**is required to**" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this document 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 from which no deviation is permitted if conformance to this document 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 vendor's implementation must provide 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*, 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 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:
+
+- the transmission function
+- the subscriber function
+- the control function.
+
+![Diagram of an IP-based switched digital video system showing the flow of video, data, and control signals between a video server, IP backbone, transmission function, and subscriber function.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg)
+
+The diagram illustrates the architecture of an IP-based switched digital video system. On the left, a **Video server** is connected to an **IP backbone**. From the IP backbone, three types of flows emerge: a **Downstream video service flow** (red arrow), a **Downstream data service flow** (blue arrow), and **Programme information** (dashed pink arrow). These flows enter the **Transmission function** block, which contains an **SDV transmission function** and a **Downstream PHY function**. Above this block is a **Control function** containing **Session management**, **Resource management**, and a **Master control**. The Master control is connected to the SDV transmission function via **IPC/RPC** (dashed black line) and to the Downstream PHY function via a blue line. The Control function also connects to the IP backbone via **NSI/GBE** and to the **Subscriber function** via **DOCSIS upstream** (blue line). The Downstream PHY function sends **Downstream RF signals** (pink arrows) through **RF channels** to the **Subscriber function**. The Subscriber function contains an **SDV receiver function** and an **SDV client function**. The SDV receiver function sends **SDV control signals** (dashed pink arrows) back to the Master control. A legend at the bottom defines the arrow types: red for downstream video, blue for downstream data, pink for downstream RF, dashed blue for upstream data, dashed pink for programme information, and dashed pink for SDV control signals. The identifier **J.1103(15)\_F01** is in the bottom right.
+
+Diagram of an IP-based switched digital video system showing the flow of video, data, and control signals between a video server, IP backbone, transmission function, and subscriber function.
+
+**Figure 1 – Diagram of an IP-based switched 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 PHY function. The SDV transmission function processes service flow and packet header processing on the DOCSIS MAC layer [ITU-T J.222.2]. The downstream PHY function transmits the DOCSIS header processed video stream to the subscriber.
+
+### 6.1.1 SDV transmission function
+
+The SDV transmission function processes service flow and does packet header processing on the DOCSIS MAC layer.
+
+### 6.1.2 Downstream PHY function
+
+The downstream PHY [ITU-T J.222.1] function transmits the DOCSIS header processed video stream to the subscriber.
+
+## 6.2 Subscriber function
+
+The subscriber function processes the video data stream from the transmission function. The subscriber function consists of the SDV client service function and SDV receiver function. The subscriber function also sends request information of an SDV video service programme to the control function.
+
+### 6.2.1 SDV client function
+
+The SDV client function recovers an IP-based received video data stream from an MPEG-2 based video stream and outputs it to the set-top box (STB).
+
+### 6.2.2 SDV receiver function
+
+The SDV receiver function processes physical signal processing; it is a function of the DOCSIS cable modem.
+
+# 7 Transmission specification
+
+Figure 2 shows the structure of an IP-based SDV transmission module. The IP-based SDV transmission module is required to consist of service flow processing, packet scheduling, MAC header processing and MPEG-2 TS convergence. Service flow processing is required to obtain the following information on input packets: the packet type, the service flow ID, the downstream service ID, the transmission priority and the available downstream transmission channel list. Packet scheduling is required to schedule the service flow by deciding on the available downstream channel, multiplexing the DOCSIS management message and multicasting the video data packet. MAC header processing is required to process the packet according to the transmission priority and to create the DOCSIS MAC header according to the service flow information of the input packet. MPEG-2 TS convergence is required to place the DOCSIS MAC frame in the queue and to map the DOCSIS MAC frame to MPEG-2 TS.
+
+![Diagram of the SDV transmission module architecture showing four functional blocks: Multicast service flow processing, Multicast packet scheduling, MAC header processing, and MPEG-2 TS convergence.](e9314c83043183351ed74908e9bf2f90_img.jpg)
+
+The diagram illustrates the architecture of the SDV transmission module. It is a rectangular box titled "SDV transmission module" containing four blue rectangular blocks arranged in a 2x2 grid. The top-left block is labeled "Multicast service flow processing". The top-right block is labeled "Multicast packet scheduling". The bottom-left block is labeled "MAC header processing". The bottom-right block is labeled "MPEG-2 TS convergence". Below the diagram, the text "J.1103(15)\_F02" is displayed.
+
+Diagram of the SDV transmission module architecture showing four functional blocks: Multicast service flow processing, Multicast packet scheduling, MAC header processing, and MPEG-2 TS convergence.
+
+**Figure 2 – The architecture of IP-based SDV transmission**
+
+## 7.1 Service flow processing
+
+The service flow processing block is required to obtain the following information from the input packet:
+
+- packet type, downstream service identifier (DSID), service flow identifier (SFID)
+- priority
+- downstream channel (DC) list bitmask
+
+The packet scheduling block is required to determine the available channel using this information.
+
+The packet format of a transmission specification is shown in Figure 3. Detailed definitions of the header elements are provided in Table 1. The TYPE part consists of five elements as follows: TYPE\_CAST, TYPE\_BOND, TYPE\_PRIORITY, TYPE\_MESSAGE and TYPE\_RSVD.
+
+![Diagram of the data packet format showing the internal header and the 802.3 MAC packet PDU. The internal header is 32 bits long and contains fields: TYPE (2 bits), Priority (4 bits), DSID (20 bits), DC list bitmask (32 bits), and SFID addr (32 bits). The 802.3 MAC packet PDU is 18-1518 bytes long.](d4af765160d04ecef538e5066006dc77_img.jpg)
+
+The diagram illustrates the structure of a data packet. It consists of an internal header and an 802.3 MAC packet PDU. The internal header is 32 bits long and is divided into several fields: TYPE (2 bits), Priority (4 bits), DSID (20 bits), DC list bitmask (32 bits), and SFID addr (32 bits). The 802.3 MAC packet PDU is 18-1518 bytes long. The bit positions are marked at 0, 8, 16, 24, and 32.
+
+Diagram of the data packet format showing the internal header and the 802.3 MAC packet PDU. The internal header is 32 bits long and contains fields: TYPE (2 bits), Priority (4 bits), DSID (20 bits), DC list bitmask (32 bits), and SFID addr (32 bits). The 802.3 MAC packet PDU is 18-1518 bytes long.
+
+**Figure 3 – The data packet format**
+
+**Table 1 – Data packet frame header**
+
+| Field         | Length (bits) | Function                                                                   |
+|---------------|---------------|----------------------------------------------------------------------------|
+| TYPE_CAST     | 2             | TYPE:<br>00 – Unicast<br>01 – Multicast<br>10 – Broadcast<br>11 – Reserved |
+| TYPE_BOND     | 1             | TYPE BONDING CONDITION<br>0 – Channel non-bonded<br>1 – Channel bonded     |
+| TYPE_PRIORITY | 1             | TYPE ZERO PRIORITY<br>0 – Zero priority<br>1 – Non-zero priority           |
+| TYPE_MESSAGE  | 1             | TYPE MESSAGE<br>0 – User packet<br>1 – MAC management message              |
+| TYPE_RSVD     | 3             | TYPE Reserved                                                              |
+| PRIORITY      | 4             | PRIORITY<br>0x 0 ~ 7: High value is high priority                          |
+| DSID          | 20            | Downstream ID                                                              |
+| DC LIST MASK  | 32            | Service available channel list                                             |
+| SFID_ADDR     | 32            | Service flow ID                                                            |
+
+The service flow classification process is shown in Figure A.1.
+
+## 7.2 Packet scheduling
+
+Packet scheduling is required to determine the available downstream channel. It is possible to transmit a management message for a determined channel. The management packet format of a transmission specification is shown in Figure 4. Detailed definitions of the header elements are provided in Table 2.
+
+![Diagram of the management packet format showing fields: DCID, UCID, LEN (DA ~ CRC), DA, SA, msg LEN, DSAP (0x00), SSAP (0x00), Control (0x03), Version, Type, RSVD, Management message payload, and CRC. It also labels the 'Internal header' and 'MAC management message header'.](af7916c89a458fdab6c3f443217388ae_img.jpg)
+
+The diagram illustrates the structure of a management packet. The packet starts with an 'Internal header' (bits 0-31) containing DCID (0-7), UCID (8-15), and LEN (DA ~ CRC) (16-31). This is followed by a 'MAC management message header' which includes DA (bits 32-63), SA (bits 64-95), msg LEN (bits 96-127), DSAP (0x00) (bits 128-135), SSAP (0x00) (bits 136-143), Control (0x03) (bits 144-151), Version (bits 152-159), Type (bits 160-167), and RSVD (bits 168-175). The 'Management message payload' follows, indicated by a dashed box. The packet ends with a CRC field.
+
+Diagram of the management packet format showing fields: DCID, UCID, LEN (DA ~ CRC), DA, SA, msg LEN, DSAP (0x00), SSAP (0x00), Control (0x03), Version, Type, RSVD, Management message payload, and CRC. It also labels the 'Internal header' and 'MAC management message header'.
+
+J.1103(15)\_F04
+
+**Figure 4 – The management packet format**
+
+**Table 2 – Management packet frame header**
+
+| Field | Length (Bit) | Function        |
+|-------|--------------|-----------------|
+| DCID  | 8            | Down channel ID |
+| UCID  | 8            | Up channel ID   |
+| LEN   | 16           | Length          |
+
+## 7.3 MAC header processing
+
+The MAC header processing unit is required to classify the packet and store it in the queue according to the transmission priority. The MAC header processing unit is required to process the stored packets according to the queue priority shown in Table 3.
+
+**Table 3 – Queue priority**
+
+| Input packet priority | Queue priority |
+|-----------------------|----------------|
+| 15                    | 2              |
+| 7, 6, 5, 4            | 1              |
+| 3, 2, 1, 0            | 0              |
+
+Different MAC header types are created according to the packet type as shown in Table 4.
+
+**Table 4 – MAC packet header type**
+
+| MAC header type    | Value    | Packet type                                                 |
+|--------------------|----------|-------------------------------------------------------------|
+| Five-Byte DS EHDR  | 00110xxx | Channel bonding unicast packet                              |
+|                    |          | Zero length packet                                          |
+|                    | 01110xxx | Channel bonding multicast packet                            |
+| Three-Byte DS EHDR | 01010xxx | Non-bonding multicast packet                                |
+| One-Byte DS EHDR   | 00010xxx | Non-bonding and the priority of service flow is not zero    |
+| No DS EHDR         | 00000xxx | Non-bonding and the priority of service flow is not defined |
+|                    | 10000xxx | Non-bonding, broadcast and unknown MAC address message      |
+|                    | 00001xxx | Unicast MAC management message                              |
+|                    | 01001xxx | Multicast MAC management message                            |
+
+The format of MAC header processing for a user data packet is shown in Figure 5 and the format of MAC header processing for a management packet is shown in Figure 6.
+
+![Diagram of MAC header processing for a user data packet showing fields like DOCSIS MAC header, DA, SA, Type/LEN, Control, ORG Code, Type, Data, and CRC with bit positions 0, 8, 16, 24, 32.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg)
+
+The diagram illustrates the structure of a MAC packet for user data. At the top, bit positions 0, 8, 16, 24, and 32 are marked. The packet structure is as follows:
+
+- DOCSIS MAC header (five, three, one or no DS EHDR)**: A green-shaded block at the top, corresponding to the first 6 to 12 bytes.
+- DA**: Destination Address field, 6 bytes long.
+- DA** and **SA**: Source Address field, 6 bytes long, split into two 3-byte halves.
+- Type/LEN**: Type or Length field, 2 bytes long.
+- DSAP (0xAA)** and **SSAP (0xAA)**: Service Access Point fields, 1 byte each.
+- Control (0x03)** and **ORG Code (0x00)**: Control and Organization Code fields, 1 byte each.
+- Type (0x0800, 0x0806, 0x0835)**: EtherType field, 2 bytes long.
+- Data (38 ~ 1492 bytes)**: The payload data.
+- CRC**: Cyclic Redundancy Check field, 4 bytes long.
+
+Brackets on the right side of the diagram indicate that the first 6-12 bytes constitute the **DOCSIS MAC header (6 ~ 12 bytes)** and the remaining fields constitute the **802.3 MAC packet PDU (18-1518 bytes)**.
+
+J.1103(15)\_F05
+
+Diagram of MAC header processing for a user data packet showing fields like DOCSIS MAC header, DA, SA, Type/LEN, Control, ORG Code, Type, Data, and CRC with bit positions 0, 8, 16, 24, 32.
+
+**Figure 5 –MAC header processing for a user data packet**
+
+![Figure 6: MAC header processing for a management packet. The diagram shows a packet structure with fields: FC, MAC PARM, LEN, HCS, DA, DA, SA, SA, msg LEN, DSAP (0x00), SSAP (0x00), Control (0x03), Version, Type, RSVD, Management message payload, and CRC. Bit positions 0, 8, 16, 24, and 32 are marked at the top. Brackets on the right indicate the 'DOCSIS MAC header' (first two rows) and 'MAC management message header' (rows 3 through 7).](33ed1f9b27c7c21c797aa928b0f06851_img.jpg)
+
+Figure 6: MAC header processing for a management packet. The diagram shows a packet structure with fields: FC, MAC PARM, LEN, HCS, DA, DA, SA, SA, msg LEN, DSAP (0x00), SSAP (0x00), Control (0x03), Version, Type, RSVD, Management message payload, and CRC. Bit positions 0, 8, 16, 24, and 32 are marked at the top. Brackets on the right indicate the 'DOCSIS MAC header' (first two rows) and 'MAC management message header' (rows 3 through 7).
+
+**Figure 6 –MAC header processing for a management packet**
+
+The message format of a five-byte DS EHDR DOCSIS MAC header is shown in Figure 7. MAC header processing is required to operate the sequence count and count initialization at each DSID if the input packet is a bonded packet (Type=1).
+
+The setting of a five-byte DS EHDR DOCSIS MAC header is shown in Table 5.
+
+![Figure 7: Message format of five-byte DS EHDR DOCSIS MAC header. The diagram shows a 32-bit header structure with fields: FC, MAC PARM, LEN, EH_TYPE, EH_LEN, TP, SCC, DSID, PSN, and HCS. Bit positions 0, 8, 16, 24, and 32 are marked at the top. A bracket on the right indicates the 'Bonded DOCSIS MAC header (12 bytes)' covering the first three rows.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg)
+
+Figure 7: Message format of five-byte DS EHDR DOCSIS MAC header. The diagram shows a 32-bit header structure with fields: FC, MAC PARM, LEN, EH\_TYPE, EH\_LEN, TP, SCC, DSID, PSN, and HCS. Bit positions 0, 8, 16, 24, and 32 are marked at the top. A bracket on the right indicates the 'Bonded DOCSIS MAC header (12 bytes)' covering the first three rows.
+
+**Figure 7 – Message format of five-byte DS EHDR DOCSIS MAC header**
+
+**Table 5 – Setting of a five-byte DS EHDR DOCSIS MAC header**
+
+| Field     | Size (bits) | Value |                                                |
+|-----------|-------------|-------|------------------------------------------------|
+| FC        | 8           | 0x01  | EHDR_ON = 1                                    |
+| MAC_PARAM | 8           | 0x06  | Extended header length                         |
+| LEN       | 16          |       | packet PDU length + 6 (extended header length) |
+| EH_TYPE   | 4           | 0x8   |                                                |
+| EH_LEN    | 4           | 0x5   |                                                |
+| TP        | 3           |       | Priority of additional area                    |
+| SCC       | 1           |       | DSID of initialization flag bit                |
+
+**Table 5 – Setting of a five-byte DS EHDR DOCSIS MAC header**
+
+| Field | Size (bits) | Value |                                      |
+|-------|-------------|-------|--------------------------------------|
+| DSID  | 20          |       | DSID of additional area              |
+| PSN   | 16          |       | DSID of current sequence count value |
+| HCS   | 16          |       | Calculation of FC to PSN             |
+
+- LEN: the sum of the length of the input packet and the value of the DOCSIS extended header length (6)
+- TP: the priority value of the internal additional header in the input packet
+- SCC: the initialization flag bit of the relevant DSID
+- DSID: the DSID value of the internal additional header of the input packet
+- PSN: the current sequence count value which the input packet belongs to
+- HCS: the value created by the polynomial  $X^{16} + X^{12} + X^5 + 1$  from FC to PSN
+
+The message format of a null packet DOCSIS MAC header is shown in Figure 8. MAC header processing is required to create null packets and increase the counter value by 1, if the DSID has no input packet (TYPE=0). The setting of a null packet DOCSIS MAC header is shown in Table 6.
+
+![Figure 8: Message format of a null packet DOCSIS MAC header. The diagram shows a 32-bit header structure with fields FC, MAC PARM, LEN, EH_TYPE, EH_LEN, TP, SCC, DSID, PSN, and HCS. A bracket on the right indicates the 'Bonded DOCSIS MAC header (12 bytes)' covering the first 24 bits (FC through DSID). Bit positions 0, 8, 16, 24, and 32 are marked at the top.](16152cf1d84aea10848758f51a91ff6a_img.jpg)
+
+J.1103(15)\_F08
+
+Figure 8: Message format of a null packet DOCSIS MAC header. The diagram shows a 32-bit header structure with fields FC, MAC PARM, LEN, EH\_TYPE, EH\_LEN, TP, SCC, DSID, PSN, and HCS. A bracket on the right indicates the 'Bonded DOCSIS MAC header (12 bytes)' covering the first 24 bits (FC through DSID). Bit positions 0, 8, 16, 24, and 32 are marked at the top.
+
+**Figure 8 – Message format of a null packet DOCSIS MAC header**
+
+**Table 6 – Setting of a null packet DOCSIS MAC header**
+
+| Field     | Size (bits) | Value |                                      |
+|-----------|-------------|-------|--------------------------------------|
+| FC        | 8           | 0x01  | EHDR_ON = 1                          |
+| MAC_PARAM | 8           | 0x06  | Extended header length               |
+| LEN       | 16          |       | 6 (extended header length)           |
+| EH_TYPE   | 4           | 0x8   |                                      |
+| EH_LEN    | 4           | 0x5   |                                      |
+| TP        | 3           | 0x0   |                                      |
+| SCC       | 1           |       | DSID of initialization flag bit      |
+| DSID      | 20          |       | DSID of additional area              |
+| PSN       | 16          |       | DSID of current sequence count value |
+| HCS       | 16          |       | Calculation of FC to PSN             |
+
+- LEN: the value of the DOCSIS extended header length (6)
+- SCC: the initialization flat bit of the relevant DSID
+- DSID: the DSID value of the internal additional header of the input packet
+- PSN: the current sequence count value which the input packet belongs to
+
+- HCS: the value created by the polynomial  $X^{16} + X^{12} + X^5 + 1$  from FC to PSN
+
+The message format of a three-byte DS EHDR DOCSIS MAC header is shown in Figure 9. MAC header processing is required to create the three-byte DS EHDR DOCSIS MAC header if the input packet is a non-bonded multicast packet (Type=2).
+
+The setting of a three-byte DS EHDR DOCSIS MAC header is shown in Table 7.
+
+![Figure 9: Message format of a three-byte DS EHDR DOCSIS MAC header. The diagram shows a 32-bit header structure. Bit 0 to 8: FC (8 bits). Bit 8 to 16: MAC PARM (8 bits). Bit 16 to 32: LEN (16 bits). Below FC are EH_TYPE (4 bits) and EH_LEN (4 bits). Below MAC PARM are TP (3 bits) and x (1 bit). Below LEN is DSID (20 bits). Below EH_TYPE and EH_LEN is HCS (16 bits). A vertical double-headed arrow on the right indicates the 'Unbonded and group DOCSIS MAC header (10 bytes)' covering the first 80 bits (10 bytes). The diagram is labeled J.1103(15)_F09.](8307f6b04df072c9332f9987e034272c_img.jpg)
+
+Figure 9: Message format of a three-byte DS EHDR DOCSIS MAC header. The diagram shows a 32-bit header structure. Bit 0 to 8: FC (8 bits). Bit 8 to 16: MAC PARM (8 bits). Bit 16 to 32: LEN (16 bits). Below FC are EH\_TYPE (4 bits) and EH\_LEN (4 bits). Below MAC PARM are TP (3 bits) and x (1 bit). Below LEN is DSID (20 bits). Below EH\_TYPE and EH\_LEN is HCS (16 bits). A vertical double-headed arrow on the right indicates the 'Unbonded and group DOCSIS MAC header (10 bytes)' covering the first 80 bits (10 bytes). The diagram is labeled J.1103(15)\_F09.
+
+Figure 9 – Message format of a three-byte DS EHDR DOCSIS MAC header
+
+Table 7 – Setting of a three-byte DS EHDR DOCSIS MAC header
+
+| Field     | Size (bits) | Value |                                                |
+|-----------|-------------|-------|------------------------------------------------|
+| FC        | 8           | 0x01  | EHDR_ON = 1                                    |
+| MAC_PARAM | 8           | 0x04  | Extended header length                         |
+| LEN       | 16          |       | packet PDU length + 4 (extended header length) |
+| EH_TYPE   | 4           | 0x8   |                                                |
+| EH_LEN    | 4           | 0x3   |                                                |
+| TP        | 3           |       | Priority of additional area                    |
+| Reserved  | 1           |       | DSID of initialization flag bit                |
+| DSID      | 20          |       | DSID of additional area                        |
+| HCS       | 16          |       | Calculation of FC to DSID                      |
+
+- LEN: the length of the input packet protocol data unit (PDU) and the value of the DOCSIS extended header length (4)
+- TP: the priority value of the internal additional header in the input packet
+- SCC: the initialization flag bit of the relevant DSID
+- DSID: the DSID value of the internal additional header of the input packet.
+- HCS: the value created by the polynomial  $X^{16} + X^{12} + X^5 + 1$  from FC to DSID.
+
+The message format of a one-byte DS EHDR DOCSIS MAC header is shown in Figure 10. MAC header processing is required to create the one-byte DS EHDR DOCSIS MAC header if the input packet is non-bonded and the priority of service flow is set up as a not zero value (Type=3).
+
+The setting of a one-byte DS EHDR DOCSIS MAC header is shown in Table 8.
+
+![Figure 10: Message format of one-byte DS EHDR DOCSIS MAC header. The diagram shows a 32-bit header structure. Bit 0 to 8: FC (8 bits). Bit 8 to 16: MAC PARM (8 bits). Bit 16 to 32: LEN (16 bits). Below FC are EH_TYPE (4 bits) and EH_LEN (4 bits). Below MAC PARM are TP (3 bits) and xxxx (1 bit). Below LEN is HCS (16 bits). A vertical double-headed arrow on the right indicates the 'Unbonded and nonzero priority DOCSIS MAC header (8 bytes)' covering the first 64 bits (8 bytes). The diagram is labeled J.1103(15)_F10.](90ee16ccc0ad16aeca48087797d7b07f_img.jpg)
+
+Figure 10: Message format of one-byte DS EHDR DOCSIS MAC header. The diagram shows a 32-bit header structure. Bit 0 to 8: FC (8 bits). Bit 8 to 16: MAC PARM (8 bits). Bit 16 to 32: LEN (16 bits). Below FC are EH\_TYPE (4 bits) and EH\_LEN (4 bits). Below MAC PARM are TP (3 bits) and xxxx (1 bit). Below LEN is HCS (16 bits). A vertical double-headed arrow on the right indicates the 'Unbonded and nonzero priority DOCSIS MAC header (8 bytes)' covering the first 64 bits (8 bytes). The diagram is labeled J.1103(15)\_F10.
+
+Figure 10 – Message format of one-byte DS EHDR DOCSIS MAC header
+
+**Table 8 – Setting of a one-byte DS EHDR DOCSIS MAC header**
+
+| Field     | size (bits) | value |                                                |
+|-----------|-------------|-------|------------------------------------------------|
+| FC        | 8           | 0x01  | EHDR_ON = 1                                    |
+| MAC_PARAM | 8           | 0x02  | Extended header length                         |
+| LEN       | 16          |       | packet PDU length + 2 (extended header length) |
+| EH_TYPE   | 4           | 0x8   |                                                |
+| EH_LEN    | 4           | 0x1   |                                                |
+| TP        | 3           |       | DSID of additional area                        |
+| Reserved  | 5           | 0x0   |                                                |
+| HCS       | 16          |       | Calculation of FC to PSN                       |
+
+- LEN: the length of the input packet PDU and the value of the DOCSIS extended header length (4).
+- TP: the priority value of the internal additional header in the input packet
+- HCS: the value created by the polynomial  $X^{16} + X^{12} + X^5 + 1$  from FC to PSN
+
+The message format of a NO DS EHDR DOCSIS MAC header is shown in Figure 11. MAC header processing is required to create the no DS EHDR DOCSIS MAC header if the input packet is a non-bonded and the priority of service flow is not defined (Type=4).
+
+The setting of a NO DS EHDR DOCSIS MAC header is shown in Table 9.
+
+![Diagram of NO DS EHDR DOCSIS MAC header structure. It shows a header with fields FC (8 bits), MAC PARM (8 bits), LEN (16 bits), and HCS (16 bits). Bit positions 0, 8, 16, 24, and 32 are marked. A bracket on the right indicates the 'Unbonded DOCSIS MAC header (6 bytes)' covering FC, MAC PARM, and LEN. The HCS field follows. Source: J.1103(15)_F11.](9cd90f495b95ad2116ff780248c26d95_img.jpg)
+
+Diagram of NO DS EHDR DOCSIS MAC header structure. It shows a header with fields FC (8 bits), MAC PARM (8 bits), LEN (16 bits), and HCS (16 bits). Bit positions 0, 8, 16, 24, and 32 are marked. A bracket on the right indicates the 'Unbonded DOCSIS MAC header (6 bytes)' covering FC, MAC PARM, and LEN. The HCS field follows. Source: J.1103(15)\_F11.
+
+**Figure 11 – Message format of a NO DS EHDR DOCSIS MAC header**
+
+**Table 9 – Setting of a NO DS EHDR DOCSIS MAC header**
+
+| Field     | Size (bits) | Value |                          |
+|-----------|-------------|-------|--------------------------|
+| FC        | 8           | 0x00  | EHDR_ON = 0              |
+| MAC_PARAM | 8           | 0x00  | 0                        |
+| LEN       | 16          |       | packet PDU length        |
+| HCS       | 16          |       | Calculation of FC to PSN |
+
+- LEN: the value of the length of the input packet PDU
+- HCS: the value of polynomial  $X^{16} + X^{12} + X^5 + 1$  from FC to LEN
+
+## 7.4 MPEG-2 TS convergence
+
+MPEG-2 TS convergence is required to store the DOCSIS MAC frame in the queue and for mapping to MPEG-2 TS. The mapped MPEG-2 TS is required to multiplex the MPEG-2 TS from an A/V encoder or re-multiplexer. The structure of MPEG-2 TS convergence is shown in Figure 12 and the structure of MPEG-2 TS encapsulation is shown in Figure 13. The setting values of MPEG-2 TS header are shown in Table 10. An example of MPEG-2 TS encapsulation is shown in Figure B.1.
+
+![Figure 12: Structure of MPEG-2 TS convergence. This block diagram shows the convergence process. On the left, a 'DOCSIS MAC packet' enters a 'DOCSIS MAC packet FIFO'. Above it, 'SYNC message memory' is connected to an 'MPEG-2 TS encapsulator'. The 'DOCSIS MAC packet FIFO' also feeds into this encapsulator. An external 'From A/V encoder or remultiplexer' provides 'MPEG-2 TS' data to an 'MPEG-2 TS multiplex'. The encapsulator outputs 'MPEG-2 TS' data to this multiplex, which then outputs the final 'MPEG-2 TS' stream. A label 'J.1103(15)_F12' is at the bottom right.](9c6461e1e94afae4dec455e69a2ce152_img.jpg)
+
+Figure 12: Structure of MPEG-2 TS convergence. This block diagram shows the convergence process. On the left, a 'DOCSIS MAC packet' enters a 'DOCSIS MAC packet FIFO'. Above it, 'SYNC message memory' is connected to an 'MPEG-2 TS encapsulator'. The 'DOCSIS MAC packet FIFO' also feeds into this encapsulator. An external 'From A/V encoder or remultiplexer' provides 'MPEG-2 TS' data to an 'MPEG-2 TS multiplex'. The encapsulator outputs 'MPEG-2 TS' data to this multiplex, which then outputs the final 'MPEG-2 TS' stream. A label 'J.1103(15)\_F12' is at the bottom right.
+
+**Figure 12 – Structure of MPEG-2 TS convergence**
+
+The MPEG-2 TS convergence is required to set the MPEG-2 TS header format in accordance with Table 10. MPEG-2 TS convergence is required to use the 'pointer field' as the payload unit start indicator (PUSI) is set to 1.
+
+![Figure 13: Structure of MPEG-2 TS encapsulation. This diagram details the encapsulation process. It starts with a 'DOCSIS MAC Frame FIFO' containing four slots. An arrow labeled 'one MAC frame' points from the FIFO to a large dotted rectangle representing the MAC frame. Below the FIFO, a 'TS head block' is shown as a 4x4 grid of bits. A '4-bit counter' is connected to the bottom row of the TS head block. To the right of the MAC frame, 'MAC_remains' are indicated. Below the MAC frame, an arrow labeled 'map MAC frame into payload of TS' points to a new structure. This structure consists of an 'MPEG TS header', a 'pointer_field', a dotted rectangle representing the mapped MAC frame, and 'TS_remains'. A yellow 'SYNC message' box is shown below the TS header, with a dashed arrow pointing to the 'pointer_field'. The 'TS_remains' part of the structure points to a 'TS FIFO' (four slots), which then points to 'To MPEG TS multiplex'. A label 'J.1103(15)_F13' is at the bottom right.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg)
+
+|   |   |   |   |   |   |   |   |
+|---|---|---|---|---|---|---|---|
+| 0 | 1 | 0 | 0 | 1 | 1 | 1 | 1 |
+| 0 | y | 0 | 1 | 1 | 1 | 1 | 1 |
+| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 |
+| 0 | 0 | 0 | 1 | x | x | x | x |
+
+Figure 13: Structure of MPEG-2 TS encapsulation. This diagram details the encapsulation process. It starts with a 'DOCSIS MAC Frame FIFO' containing four slots. An arrow labeled 'one MAC frame' points from the FIFO to a large dotted rectangle representing the MAC frame. Below the FIFO, a 'TS head block' is shown as a 4x4 grid of bits. A '4-bit counter' is connected to the bottom row of the TS head block. To the right of the MAC frame, 'MAC\_remains' are indicated. Below the MAC frame, an arrow labeled 'map MAC frame into payload of TS' points to a new structure. This structure consists of an 'MPEG TS header', a 'pointer\_field', a dotted rectangle representing the mapped MAC frame, and 'TS\_remains'. A yellow 'SYNC message' box is shown below the TS header, with a dashed arrow pointing to the 'pointer\_field'. The 'TS\_remains' part of the structure points to a 'TS FIFO' (four slots), which then points to 'To MPEG TS multiplex'. A label 'J.1103(15)\_F13' is at the bottom right.
+
+**Figure 13 – Structure of MPEG-2 TS encapsulation**
+
+**Table 10 – MPEG-2 TS header**
+
+| <b>Field</b>                        | <b>Size (bits)</b> | <b>Value</b> |          |
+|-------------------------------------|--------------------|--------------|----------|
+| Sync_byte                           | 8                  | 0x47         |          |
+| Transport_error_indicator           | 1                  | '0'          |          |
+| Payload_unit_start_indicator (PUSI) | 1                  |              |          |
+| Transport_priority                  | 1                  | '0'          | Reserved |
+| PID                                 | 13                 | 0x1FFE       |          |
+| Transport_scrambling_control        | 2                  | '0'          | Reserved |
+| Adaptation_field_control            | 2                  | '01'         |          |
+| Continuity_counter                  | 4                  |              |          |
+
+## Annex A
+
+### The service flow classification process
+
+(This annex forms an integral part of this Recommendation.)
+
+The input packet is classified into only one service flow by field searching. The service flow classification process consists of a two-stage approach as follows:
+
+First stage: classification via the destination address of the input MAC packet
+
+Second stage: classification via a defined packet classifier
+
+Figure A.1 illustrates the service flow classification process.
+
+In the first stage, it is possible to determine a specific set-top box (STB) according to the destination MAC address of the input packet. It is necessary to find the specific address from the input MAC Dest. Addr. To CM Classifier Entity Table.
+
+![Flowchart of the service flow classification process showing six tables and numbered steps (1-6).](75e4b78ee25f885d73120e3066a5253e_img.jpg)
+
+The diagram illustrates the service flow classification process through six interconnected tables and numbered steps:
+
+- [1] Input MAC Dest. Addr. to CM classifier entity table**:
+ 
+
+| IN pkt MAC | Table entry addr |
+|------------|------------------|
+| cm1        | 0xee080000       |
+| cm2        | 0xee080008       |
+| cm3        | ...              |
+| cm4        | ...              |
+| cm5        | ...              |
+| cpe1       | 0xee09ee06       |
+| cpe2       | ...              |
+| cpe3       |                  |
+| cpe4       |                  |
+| gmac1      |                  |
+| gmac2      |                  |
+| gmac3      |                  |
+- [2] CM classifier entity table**:
+ 
+
+| CM MAC | Classifier entities (CLID's) |
+|--------|------------------------------|
+| cm1    | 5, 2, 3                      |
+| cm2    | 7, 2                         |
+| cm3    | -                            |
+| ...    | ...                          |
+- [3] Classifier pattern table**:
+ 
+
+|          |
+|----------|
+| pattern1 |
+| pattern2 |
+| pattern3 |
+- [4] Second stage classification table**:
+ 
+
+| CM MAC + matched value | DS SFID |
+|------------------------|---------|
+| cm1 + str1             |         |
+| cm1 + str2             |         |
+| cm2 + str1             |         |
+| cm3                    |         |
+| ...                    |         |
+- [5] Active DS service flow table**:
+ 
+
+| DS SFID | CM MAC | DSID | DC Lists | Pkt type | Priority | QoS Class |
+|---------|--------|------|----------|----------|----------|-----------|
+| sfid 1  | cm1    | 3    | 0x000D   | 1        | 1        |           |
+| sfid 2  | cm1    | 4    | 0x004E   | 1        | 2        |           |
+| sfid 3  | cm2    | null | 0x0002   | 3        | 0        |           |
+| sfid 4  | cm3    | 6    | 0x0020   | 2        | 0        |           |
+| sfid 5  | cm4    | 7    | 0x0040   | 2        | 1        |           |
+| ...     | ...    | ...  | ...      | ...      | ...      |           |
+- [6] DS QoS attribution table**:
+ 
+
+| QoS Class | Max susR | Max Burst | Min RvR | Ass. Min RvR | Max. Latency | Peak rate |
+|-----------|----------|-----------|---------|--------------|--------------|-----------|
+| 1         |          |           |         |              |              |           |
+| 2         |          |           |         |              |              |           |
+| 3         |          |           |         |              |              |           |
+| ...       |          |           |         |              |              |           |
+
+**Process Flow:**
+
+- (1)** Input MAC Dest. Addr. is used to look up the entry address in table [1], which points to the entry in table [2].
+- (2)** The classifier entities (CLID's) from table [2] are used to look up patterns in table [3].
+- (3)** A matching value is determined from the patterns in table [3].
+- (4)** The CM MAC Addr. and the Matching value are used to look up the DS SFID in table [4].
+- (5)** The DS SFID is used to look up the service flow details in table [5].
+- (6)** The QoS Class from table [5] is used to look up the QoS attributes in table [6].
+
+Flowchart of the service flow classification process showing six tables and numbered steps (1-6).
+
+Figure A.1 – Example of a service flow classification process
+
+For the second stage, it is necessary to find a specific service flow using the following three tables: the CM Classifier Entity Table, the Classifier Pattern Table and the Second Stage Classification Table.
+
+The CM Classifier Entity Table is required to store the classifier ID. The maximum number of classifiers depends upon the specification of the headend MAC module.
+
+The input packet is classified into a specific service flow through a field search of the input packet. As stated previously the service flow is generally classified as follows.
+
+Step 1: Classification via the destination address of the input MAC packet
+
+Step 2: Classification via a defined packet classifier
+
+This classification is via the MAC packet destination address of stage 1. A specific MAC address of the terminal platform with which the MAC packet is associated can be found through the first stage of the classification process. In the second stage of the classification process, the final service flow is determined in the relevant terminal MAC in the case where the classification with other fields besides the input MAC address is defined during the registration of the relevant terminal platform or the dynamic service creation procedure. If there is no stage 2 of the classification process, the service flow is mapped as the default service flow (or primary service flow) which is allocated to the relevant terminal platform. Figure A.1 shows the mapping process through which the input packet is classified and mapped into one service flow.
+
+In the first stage of the classification process the terminal to which the packet is to be transmitted is determined according to the MAC address and the result of the Input MAC Dest. Addr to CM Classifier Entity Table.
+
+[1] Input MAC Dest. Addr to CM Classifier Entity Table
+
+The terminal platform associated with the input MAC destination address is set so that it is able to find the relevant saved address of the [2] CM Classifier Entity Table for the second classification.
+
+The saved address from the [2] CM Classifier Entity Table of the relevant cable modem (CM) is obtained from the destination MAC address of the input MAC packet through the [1] Input MAC Dest. Addr to CM Classifier Entity Table for the second classification of the relevant terminal platform.
+
+The aim of the second stage of the classification process is to find to which service flow in the relevant terminal platform the input packet relates and the following three tables are needed for this search:
+
+[2] CM Classifier Entity Table
+
+The MAC address of the CM and the classifier IDs which are to apply to each CM are saved according to priority.
+
+The classifier IDs are the IDs from the [3] Classifier Pattern Table and have values in the range 0 ~ 63556.
+
+In accordance with the supported specification of the headend MAC module, the maximum value of the classifier to which a terminal platform can apply is set at maximum.
+
+[3] Classifier Pattern Table
+
+This table contains the classifier patterns which are commonly used in the headend MAC.
+
+A single classifier can be composed from a combination of fields.
+
+[4] Second Stage Classification Table
+
+The table is set to find the service flow the result value from the MAC address of the CM to which the input packet is transmitted and the defined classifier in the relevant CM.
+
+The result value is input when the terminal platform MAC address and the classifier are applied. As for the result value, the address to which the specific service flow attribution of the [5] Active DS Service Flow Table is saved as output.
+
+The second stage of the classification process is as follows:
+
+From the address of the [2] CM Classifier Entity Table which is obtained from the first stage of the classification process, the terminal platform MAC address and the classifier ID which is applied in the CM are obtained.
+
+According to the MAC address of the relevant terminal platform and the order of the classifier ID which is to be applied to the relevant terminal platform, one character string is composed by adding the result value which is obtained by applying the classifier to the CM Classifier Entity Table.
+
+The value which is relevant to the resulting character string is obtained from the Second Stage Classification Table. Then the address of the service flow which belongs to the relevant character string is found on the [5] Active DS Service Flow Table.
+
+If the second classification procedure is completed, the address of the service flow where the packet belongs can be found on the [5] Active DS Service Flow Table. The basic attribution of the service flow which is necessary for downstream transmission can be obtained from the [5] Active DS Service Flow Table.
+
+### [5] Active DS Service Flow Table
+
+The basic information of downstream service flow is saved as below:
+
+- Terminal platform MAC address
+- DSID
+- DSID channel list
+- Packet type
+- Priority
+- DS QoS attribution
+
+### [6] DS QoS Attribution Table
+
+The supported QoS is classified as the determined number and applied to the relevant service flow.
+
+The following attributions are saved in the DS QoS attribution table:
+
+- QoS class
+- Maximum sustained traffic rate
+- Minimum reserved traffic rate
+- Assumed minimum reserved traffic rate
+- Maximum latency
+- Peak Rate
+
+The DS QoS attribution is not applied in the first implementation.
+
+The Create/Alter/Delete functions of each table are performed in the headend MAC control server module and completed through the following process.
+
+Presetting by the operator in the headend MAC module (provisioning)
+
+Signalling between the headend MAC module and the terminal platform MAC module (registration, DSA)
+
+Obtaining the CPE MAC address (address aging)
+
+The destination MAC address process for multicasting is dealt with separately as it is not relevant to certain terminal platforms (excluded from the first year implementation range).
+
+The [3] Classifier Pattern Table is required to store the classifier pattern and it consists of the following configuration fields: IPV4 packet classification, TCP/UDP packet classification, Ethernet LLC packet classification, IEEE 802.1P/Q packet classification and IPV6 packet classification. The classifier configuration fields are shown in Table A.1.
+
+**Table A.1 – Classifier configuration fields**
+
+| <b>Function</b>                     | <b>Detailed field</b>                                                                                                                                                                                         |
+|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IPv4 Packet Classification          | IPv4 Type of Service Range and Mask<br>IP Protocol<br>IPv4 Source Address<br>IPv4 Source Mask<br>IPv4 Destination Address<br>IPv4 Destination Mask                                                            |
+| TCP/UDP Packet Classification       | TCP/UDP Source Port Start<br>TCP/UDP Source Port End<br>TCP/UDP Destination Port Start<br>TCP/UDP Destination Port End                                                                                        |
+| Ethernet LLC Packet Classification  | Destination MAC Address<br>Source MAC Address<br>Ethertype/DSAP/MacType                                                                                                                                       |
+| IEEE 802.1P/Q Packet Classification | IEEE 802.1P Priority Range<br>IEEE 802.1Q VLAN ID                                                                                                                                                             |
+| IPv6 Packet Classification          | IPv6 Traffic Class Range and Mask<br>IPv6 Flow Label<br>IPv6 Next Header Type<br>IPv6 Source Address<br>IPv6 Source Prefix Length (bits)<br>IPv6 Destination Address<br>IPv6 Destination Prefix Length (bits) |
+
+The [4] Second Stage Classification Table is required to find the service flow and it is possible to find the DS SFID address of the [5] Active DS Service Flow Table.
+
+The [5] Active DS Service Flow Table is required to contain the following information: STB MAC address, DSID, DSID channel list, packet type, priority and DS QoS attribution.
+
+The [6] DS QoS Attribution Table is required to contain the following information: QoS Class, maximum sustained traffic rate, minimum reserved traffic rate, assumed minimum reserved traffic rate, maximum latency and peak rate.
+
+## Annex B
+
+## Examples of MPEG-2 TS encapsulation
+
+(This annex forms an integral part of this Recommendation.)
+
+Examples of MPEG-2 TS encapsulation are shown in Figure B.1.
+
+Case (a) is an example of one MPEG-2 TS transmission including a MAC frame. In this case PUSI is set to '1' and the 'pointer field' is set to '0'.
+
+Case (b) is an example of one MPEG-2 TS transmission including part of a MAC frame and another MAC frame. The value of PUSI is set to '1' and in the 'pointer field' the first 'stuff byte' is indicated.
+
+Case (c) is an example of one MPEG-2 TS transmission including multiple MAC frames. The value of PUSI is set to '1' and the 'pointer field' is set to '0'.
+
+Case (d) is an example of three MPEG-2 TS transmissions for one MAC frame. The value of PUSI is set to '1' and the 'pointer field' is set to '0' in the first MPEG-2 TS transmission.
+
+The value of PUSI is set to '0' in the second MPEG-2 TS transmission.
+
+The value of PUSI is set to '1' and the 'pointer field' indicates the first 'stuff byte' in the third MPEG-2 TS transmission. The third MPEG-2 TS transmission includes a part of one MAC frame and another MAC frame as in Case (b).
+
+![](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg)
+
+DOCSIS MAC frame
+
+(a)
+
+|                |               |  |             |
+|----------------|---------------|--|-------------|
+| MPEG TS header | pointer_field |  | stuff_bytes |
+| PUSI = 1       | 0             |  | 0xFF        |
+
+DOCSIS MAC frame
+
+Frame #1
+
+Frame #2
+
+(b)
+
+|                |               |                  |             |   |
+|----------------|---------------|------------------|-------------|---|
+| MPEG TS header | pointer_field | tail of frame #1 | stuff_bytes | B |
+| PUSI = 1       | ↑             |                  |             |   |
+
+DOCSIS MAC frame
+
+A
+
+B
+
+(c)
+
+|                |               |   |   |             |
+|----------------|---------------|---|---|-------------|
+| MPEG TS header | pointer_field | A | B | stuff_bytes |
+| PUSI = 1       | 0             |   |   | 0xFF        |
+
+DOCSIS MAC frame
+
+Frame #1
+
+Frame #2
+
+(d)
+
+|                |               |                   |
+|----------------|---------------|-------------------|
+| MPEG TS header | pointer_field | Start of frame #1 |
+| PUSI = 1       | 0             |                   |
+
+|                |                          |  |
+|----------------|--------------------------|--|
+| MPEG TS header | Continuation of frame #2 |  |
+| PUSI = 0       |                          |  |
+
+|                |               |                  |             |          |
+|----------------|---------------|------------------|-------------|----------|
+| MPEG TS header | pointer_field | tail of frame #1 | stuff_bytes | Frame #2 |
+| PUSI = 1       | ↑ 0xFF        |                  |             |          |
+
+J.1103(15)\_FB.1
+
+**Figure B.1 – Examples of MPEG-2 TS encapsulation format**
+
+## Bibliography
+
+- [b-ITU-T J.112] Recommendation ITU-T J.112 Annex B (2004), *Data-over-cable service interface specifications: Radio-frequency interface specification.*
+- [b-ANSI/SCTE 133] ANSI/SCTE 133 (2010), *Downstream RF interface for Cable Modem Termination Systems.*
+- [b-ANSI/SCTE 135-1] ANSI/SCTE 135-1 (2013), *DOCSIS 3.0 Part 1: Physical Layer Specification.*
+- [b-ANSI/SCTE 135-2] ANSI/SCTE 135-2 (2013), *DOCSIS 3.0 Part 2: MAC and Upper Layer Protocols.*
+- [b-ANSI/SCTE 135-4] ANSI/SCTE 135-4 (2013), *DOCSIS 3.0 Part 4: Operations Support Systems Interface.*
+- [b-ANSI/SCTE 135-5] ANSI/SCTE 135-5 (2009), *DOCSIS 3.0 Part 5: Cable Modem to Customer Premise Equipment Interface.*
+- [b-ANSI/SCTE 137-1] ANSI/SCTE 137-1 (2010), *Modular Headend Architecture Part 1: DOCSIS Timing Interface.*
+- [b-ANSI/SCTE 137-2] ANSI/SCTE 137-2 (2010), *Modular Headend Architecture Part 2: M-CMTS Downstream External PHY Interface.*
+- [b-ANSI/SCTE 137-3] ANSI/SCTE 137-3 (2010), *Modular Headend Architecture Part 3: M-CMTS Operations Support System Interface.*
+- [b-ANSI/SCTE 137-4] ANSI/SCTE 137-4 (2010), *Modular Headend Architecture Part 4: Edge Resource Manager Interface for Modular Cable Modem Termination Systems.*
+- [b-ANSI/SCTE 137-5] ANSI/SCTE 137-5 (2010), *Modular Headend Architecture Part 5: Edge QAM Provisioning and Management Interface.*
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+|                 |                                                                                                                                                           |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A        | Organization of the work of ITU-T                                                                                                                         |
+| Series D        | General tariff principles                                                                                                                                 |
+| Series E        | Overall network operation, telephone service, service operation and human factors                                                                         |
+| Series F        | Non-telephone telecommunication services                                                                                                                  |
+| Series G        | Transmission systems and media, digital systems and networks                                                                                              |
+| Series H        | Audiovisual and multimedia systems                                                                                                                        |
+| Series I        | Integrated services digital network                                                                                                                       |
+| <b>Series J</b> | <b>Cable networks and transmission of television, sound programme and other multimedia signals</b>                                                        |
+| Series K        | Protection against interference                                                                                                                           |
+| Series L        | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M        | Telecommunication management, including TMN and network maintenance                                                                                       |
+| Series N        | Maintenance: international sound programme and television transmission circuits                                                                           |
+| Series O        | Specifications of measuring equipment                                                                                                                     |
+| Series P        | Terminals and subjective and objective assessment methods                                                                                                 |
+| Series Q        | Switching and signalling                                                                                                                                  |
+| Series R        | Telegraph transmission                                                                                                                                    |
+| Series S        | Telegraph services terminal equipment                                                                                                                     |
+| Series T        | Terminals for telematic services                                                                                                                          |
+| Series U        | Telegraph switching                                                                                                                                       |
+| Series V        | Data communication over the telephone network                                                                                                             |
+| Series X        | Data networks, open system communications and security                                                                                                    |
+| Series Y        | Global information infrastructure, Internet protocol aspects and next-generation networks                                                                 |
+| Series Z        | Languages and general software aspects for telecommunication systems                                                                                      |

marked/J/T-REC-J.1107-201803-I_PDF-E/raw.md

@@ -0,0 +1,397 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**J.1107**
+
+(03/2018)
+
+SERIES J: CABLE NETWORKS AND TRANSMISSION  
+OF TELEVISION, SOUND PROGRAMME AND OTHER  
+MULTIMEDIA SIGNALS
+
+Switched digital video over cable networks
+
+---
+
+**Architecture and specification for radio over IP  
+transmission systems**
+
+Recommendation ITU-T J.1107
+
+
+
+# Recommendation ITU-T J.1107
+
+# Architecture and specification for radio over IP transmission systems
+
+## Summary
+
+As cable television (TV) networks migrate to deep fibre or fibre to the home (FTTH) architectures, it is now possible and easy to provide bidirectional high-quality media services that require very high-speed digital transmission of high-quality content. Cable TV networks provide services by transmitting radio frequency (RF) signals between the headend and a cable modem (CM). The configuration and devices of these networks are optimized for RF signal transmission. When migrating to all-fibre cable TV networks, changing the existing network devices to new network devices for service operators (SOs), who provide broadcasting and various data services through hybrid fibre coaxial (HFC)-based cable TV networks, is recommended. Therefore, a cost-effective solution for deployable and acceptable migration toward optic-based cable TV networks is required.
+
+Recommendation ITU-T J.1107 provides a cost-effective adaptable solution for HFC-based cable TV network devices in optic-based cable TV networks. The purpose of the radio over Internet protocol (RoIP) system is to transmit data over cable service interface specifications (DOCSIS)-based upstream (US) RF signals of CM to cable modem termination system (CMTS) through IP transmission in optic-based cable TV networks.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T J.1107   | 2018-03-16 | 9           | <a href="http://handle.itu.int/11.1002/1000/13564">11.1002/1000/13564</a> |
+
+## Keywords
+
+RoIP.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 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 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 within ITU-T's 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 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 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 possibility 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 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 information and are therefore strongly urged to consult the TSB patent database at <http://www.itu.int/ITU-T/ipr/>.
+
+© ITU 2018
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+|                                               | Page |
+|-----------------------------------------------|------|
+| 1 Scope.....                                  | 1    |
+| 2 References.....                             | 1    |
+| 3 Definitions .....                           | 1    |
+| 3.1 Terms defined elsewhere .....             | 1    |
+| 3.2 Terms defined in this Recommendation..... | 1    |
+| 4 Abbreviations and acronyms .....            | 1    |
+| 5 Conventions .....                           | 2    |
+| 6 Overview.....                               | 2    |
+| 7 Functional architecture .....               | 4    |
+| 7.1 RoIP terminal.....                        | 4    |
+| 7.2 RoIP headend.....                         | 5    |
+| 8 Service flow .....                          | 5    |
+| 8.1 Initialization process.....               | 6    |
+| 8.2 Data transmission process .....           | 7    |
+| Bibliography.....                             | 9    |
+
+
+
+# Recommendation ITU-T J.1107
+
+## Architecture and specification for radio over IP transmission systems
+
+# 1 Scope
+
+This Recommendation describes the architecture and specification for radio over IP transmission (RoIP) systems in hybrid fibre coaxial (HFC)-based networks. The architecture described in this Recommendation is defined according to [ITU-T J.1106]. The architecture and specifications described in this Recommendation are defined as follows:
+
+- radio over IP terminal system;
+- radio over IP headend system.
+
+# 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 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 currently 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.210] Recommendation ITU-T J.210 (2006), *Downstream RF interface for cable modem termination systems*.
+- [ITU-T J.222.1] Recommendation ITU-T J.222.1 (2007), *Third-generation transmission systems for interactive cable television services - IP cable modems: Physical layer specification*.
+- [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.1106] Recommendation ITU-T J.1106 (2017), *Requirement for radio over IP transmission system*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+None.
+
+## 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 Termination System                   |
+| DOCSIS | Data Over Cable Service Interface Specifications |
+
+|      |                         |
+|------|-------------------------|
+| DS   | Downstream              |
+| E/O  | Electric to Optic       |
+| FTTH | Fibre To The Home       |
+| HFC  | Hybrid Fibre Coaxial    |
+| OLT  | Optical Line Terminal   |
+| OMUX | Optical Multiplexer     |
+| PON  | Passive Optical Network |
+| RF   | Radio Frequency         |
+| RoIP | Radio over IP           |
+| SO   | Service Operator        |
+| STB  | Set-Top Box             |
+| US   | Upstream                |
+
+# 5 Conventions
+
+In this Recommendation:
+
+The keywords "**is required to**" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this document 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 from which no deviation is permitted if conformance to this document 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 vendor's implementation must provide 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 document and its annexes, the words *shall*, *shall not*, *should*, 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 normative intent.
+
+# 6 Overview
+
+As shown in Figure 1, the RoIP system [ITU-T J.1106] consists of an RoIP terminal and an RoIP headend. The RoIP terminal is located at the endpoint of an optic-based cable TV network and the RoIP headend is located between the cable modem termination system (CMTS) and optical network endpoint such as an optical line terminal (OLT). It is required to synchronize and transmit upstream (US) using a data over cable service interface specifications (DOCSIS)-based protocol [b-ANSI/SCTE 135-1 2008], [b-ANSI/SCTE 135-2 2008], [b-ANSI/SCTE 135-4 2008], [b-ANSI/SCTE 135-5 2008] for IP transmission.
+
+For fibre to the home (FTTH), a broadcast signal and a signal to be output [ITU-T J.210] from the CMTS are radio frequency (RF) signals which have different center frequencies. These signals may be combined as a signal output by a combiner, and an RF signal to be output from the combiner may be output after being input to a downstream optical transmitter. Through the input and the output, an RF electrical signal may be converted to an optical signal.
+
+An optical signal is different from a passive optical network (PON)-type signal used in general optical communications. The optical signal used in a PON turns on or off an optical source based on a bit value in a bit unit, whereas the optical signal obtained by the conversion in a downstream optical transmitter is an optical amplitude modulation signal to change the intensity of an optical source with respect to an amplitude of an RF signal.
+
+The signal converted to an optical signal may be transmitted to a splitter through an optical cable after being amplified in an erbium-doped fibre amplifier (EDFA), and the signal, split at a rate of 1:N in the splitter, may be input to an optical network terminal (ONT) located on a customer's premise.
+
+In the case of an ONT on a customer's premise, in addition to a function of the ONT used for PON-based optical communications, functions of restoring an optically modulated downstream RF signal and transmitting the signal through a coaxial cable and of detecting an upstream RF signal to be output from the cable modem or the set-top box (STB), digitizing the detected signal, and transmitting the digitized signal via an IP packet [ITU-T J.222.1, ITU-T J.222.2] may be added. It is the RoIP terminal.
+
+Unlike the downstream RF signal, the upstream RF signal is converted into a digital signal by the RoIP terminal and transmits it formed of IP packets over the IP networks (i.e., xPON networks).
+
+In the RoIP headend, the digital signal included in the received IP packet is recovered and the original analogue RF signal is transmitted to the CMTS.
+
+For the purpose of transmitting the upstream signal by the CM during the time interval allocated from the CMTS, it should be synchronized among CMTS, RoIP headend, RoIP terminal and CM.
+
+![Figure 1 – System architecture for radio over Internet protocol. The diagram shows the flow of signals from a 'Digital cable broadcasting headend' to a 'Subscriber'. Inside the headend, 'TV service channels' are combined and sent to an 'E/O converter' to produce an optical signal (λ1 cable TV). A 'CMTS' sends RF signals to a 'RoIP headend', which converts them to IP packets (λ2 IP down). A 'PON OLT' sends IP packets (λ3 IP up) to an 'OMUX'. The 'OMUX' combines the optical signal and IP packets into an 'Optical cable TV network'. From the network, multiple 'RoIP terminal' units are connected to 'Subscribers'. Each subscriber contains a 'CM' (Cable Modem) and an 'STB with CM' (Set-Top Box with Cable Modem). An 'Upstream IP return' path is shown from the subscriber's RoIP terminal back to the headend's RoIP headend.](dbe553cf16dd14073b89a8263a428664_img.jpg)
+
+Figure 1 – System architecture for radio over Internet protocol. The diagram shows the flow of signals from a 'Digital cable broadcasting headend' to a 'Subscriber'. Inside the headend, 'TV service channels' are combined and sent to an 'E/O converter' to produce an optical signal (λ1 cable TV). A 'CMTS' sends RF signals to a 'RoIP headend', which converts them to IP packets (λ2 IP down). A 'PON OLT' sends IP packets (λ3 IP up) to an 'OMUX'. The 'OMUX' combines the optical signal and IP packets into an 'Optical cable TV network'. From the network, multiple 'RoIP terminal' units are connected to 'Subscribers'. Each subscriber contains a 'CM' (Cable Modem) and an 'STB with CM' (Set-Top Box with Cable Modem). An 'Upstream IP return' path is shown from the subscriber's RoIP terminal back to the headend's RoIP headend.
+
+**Figure 1 – System architecture for radio over Internet protocol**
+
+The RoIP system, including the RoIP headend and RoIP terminal, greatly reduces implementation costs for optical modulation as transmitting upstream RF signals in the optical-based cable TV networks, and it is also possible to reuse existing RF-based broadcasting equipment (e.g., STB, CMTS) operating in the cable-based cable TV networks.
+
+# 7 Functional architecture
+
+## 7.1 RoIP terminal
+
+As the upstream RF signal is output from the CM or STB, the RoIP terminal detects the RF signal. The RoIP terminal performs an analog to digital conversion (ADC) on the detected RF signal to digitize the analog RF signal.
+
+The RoIP terminal converts the detected digitized RF signal to the IP packet and transmits it to the headend.
+
+Since upstream traffic transmission is performed through time division multiple access (TDMA), accurate timing synchronization in the network may be necessary. Thus, the timing synchronization between the RoIP terminal, located on the subscriber side, and the RoIP headend may be performed using a network synchronization protocol.
+
+Timing information corresponding to the time when the upstream RF burst signal, output from the STB and CM, is input to the RoIP terminal after timing synchronization is obtained, is digitized and transmitted as an IP packet when the RF signal is transmitted.
+
+After receiving the corresponding IP packet from the RoIP headend and checking timing information, all packets have a predetermined delay time and will generate and output an RF signal again. The CMTS then receives the upstream RF signal at the time assigned to each STB or CM.
+
+![Figure 2 – Architecture for radio over Internet protocol terminal. The diagram shows the internal components of a RoIP terminal and its connections. On the left, an external 'RoIP headend' is connected via 'IP data' to an 'IP access interface' inside the terminal. The 'IP access interface' connects to a 'DOCSIS downstream MAC/PHY module' and a 'Burst data processing module'. The 'DOCSIS downstream MAC/PHY module' is connected to a 'RoIP terminal control module' and a 'DOCSIS timing processing module'. The 'RoIP terminal control module' is connected to an 'RF access interface' and the 'Upstream burst receive module'. The 'DOCSIS timing processing module' is connected to the 'Upstream burst receive module'. The 'Upstream burst receive module' is connected to the 'RF access interface'. The 'RF access interface' is connected to an external 'CM' (Cable Modem) via 'RF data'. The entire internal structure is labeled 'RoIP terminal' at the bottom. A reference code 'J.1107(18)_F02' is in the bottom right corner.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg)
+
+Figure 2 – Architecture for radio over Internet protocol terminal. The diagram shows the internal components of a RoIP terminal and its connections. On the left, an external 'RoIP headend' is connected via 'IP data' to an 'IP access interface' inside the terminal. The 'IP access interface' connects to a 'DOCSIS downstream MAC/PHY module' and a 'Burst data processing module'. The 'DOCSIS downstream MAC/PHY module' is connected to a 'RoIP terminal control module' and a 'DOCSIS timing processing module'. The 'RoIP terminal control module' is connected to an 'RF access interface' and the 'Upstream burst receive module'. The 'DOCSIS timing processing module' is connected to the 'Upstream burst receive module'. The 'Upstream burst receive module' is connected to the 'RF access interface'. The 'RF access interface' is connected to an external 'CM' (Cable Modem) via 'RF data'. The entire internal structure is labeled 'RoIP terminal' at the bottom. A reference code 'J.1107(18)\_F02' is in the bottom right corner.
+
+**Figure 2 – Architecture for radio over Internet protocol terminal**
+
+As shown in Figure 2, the RoIP terminal consists of the following five modules:
+
+- 1) DOCSIS downstream MAC/PHY module: demodulates the downstream signals transmitted from headend devices (e.g., CMTS) to cable terminal devices (e.g., CM, STB) and processes several multicast management messages (e.g., SYNC, UCD, MAP) procedures.
+- 2) Upstream burst receive module: detects the upstream analog RF signal output from cable terminal devices (e.g., CM, STB), obtains the time that the RF signal is detected, converts it into a baseband digital signal, and transmits the converted signal with the obtained time to the DOCSIS timing processing module.
+- 3) DOCSIS timing processing module: synchronizes the RoIP terminal with the RoIP headend using the RF upstream signal detection time of the cable terminal devices (e.g., CM, STB) and the bandwidth allocation information of the downstream multicast management messages.
+- 4) Burst data processing module: compresses the baseband digital signal output from the upstream burst receive module and generates IP frames with information of the detected time and transmits it to IP networks.
+- 5) RoIP terminal control module: analyzes information from the upstream channel and burst of the DOCSIS downstream MAC/PHY module, transmits it to upstream burst receive module. Gathers the status information of modules in the RoIP terminal and manages configuration of the modules.
+
+## 7.2 RoIP headend
+
+The digitized RF signal transmitted to the headend is input to the RoIP headend after passing through the OLT, an apparatus inside the RoIP headend connected to the IP networks (e.g., router, switch).
+
+The RoIP headend reconstructs the original analog RF signal, sent from the cable network terminals, by receiving the digitized RF signal and performing a digital to analog conversion (DAC). The RoIP headend restores the reconstructed original RF signal and outputs it to the CMTS.
+
+The CMTS treats receiving the reconstructed RF signal from the RoIP headend as receiving a signal from the CM or STB at the allocated time by itself.
+
+![Figure 3 – Architecture for radio over Internet protocol headend. The diagram shows the internal components of the RoIP headend and its connection to an external RoIP terminal. Inside the headend, an 'RF QAM' input connects to an 'RF access interface'. This interface connects to a 'DOCSIS upstream MAC/PHY module' and an 'Upstream RF transmission module'. The 'DOCSIS upstream MAC/PHY module' connects to a 'RoIP headend control module' and the 'Upstream RF transmission module'. The 'RoIP headend control module' connects to an 'IP access interface' and the 'Upstream burst scheduling module'. The 'Upstream RF transmission module' connects to the 'Upstream burst scheduling module', which in turn connects to the 'Upstream receive and reconstruction module'. The 'Upstream receive and reconstruction module' connects to the 'IP access interface'. The 'IP access interface' connects to an external 'RoIP terminal' via 'IP data' lines. The entire internal structure is labeled 'RoIP headend' at the bottom. A reference code 'J.1107(18)_F03' is in the bottom right corner.](d26959f4514c26ca19c3d6f00da85956_img.jpg)
+
+Figure 3 – Architecture for radio over Internet protocol headend. The diagram shows the internal components of the RoIP headend and its connection to an external RoIP terminal. Inside the headend, an 'RF QAM' input connects to an 'RF access interface'. This interface connects to a 'DOCSIS upstream MAC/PHY module' and an 'Upstream RF transmission module'. The 'DOCSIS upstream MAC/PHY module' connects to a 'RoIP headend control module' and the 'Upstream RF transmission module'. The 'RoIP headend control module' connects to an 'IP access interface' and the 'Upstream burst scheduling module'. The 'Upstream RF transmission module' connects to the 'Upstream burst scheduling module', which in turn connects to the 'Upstream receive and reconstruction module'. The 'Upstream receive and reconstruction module' connects to the 'IP access interface'. The 'IP access interface' connects to an external 'RoIP terminal' via 'IP data' lines. The entire internal structure is labeled 'RoIP headend' at the bottom. A reference code 'J.1107(18)\_F03' is in the bottom right corner.
+
+**Figure 3 – Architecture for radio over Internet protocol headend**
+
+As shown in Figure 3, the RoIP headend consists of the following five modules:
+
+- 1) DOCSIS upstream MAC/PHY module: synchronizes with the time of CMTS so that the upstream burst data received from the RoIP terminal can be transmitted according to the time set in the CMTS.
+- 2) Upstream receive and reconstruction module: extracts digitized upstream RF signals sent by the RoIP terminal in the received IP packets and decompresses if the digital data has been compressed by the RoIP terminal.
+- 3) Upstream burst scheduling module: performs the function to transmit the recovered upstream RF burst data sent by the RoIP terminal to the CMTS at the bandwidth designated by the CMTS.
+- 4) Upstream RF transmission module: performs the function of converting the digitized upstream RF signal sent by the RoIP terminal into an analog RF signal at the frequency and speed specified by the CMTS and then transmitting it.
+- 5) RoIP headend control module: handles DOCSIS message processing procedures required for network synchronization, manages the control and status information for modules configuring the RoIP headend, and provides user interface functions for operators.
+
+# 8 Service flow
+
+Figure 4 shows the service flow of RoIP service including RoIP headend and RoIP terminal.
+
+![Sequence diagram showing the service flow of radio over Internet protocol service. It is divided into two main phases: Initialization process and Data transmission process. The participants are CMTS, RoIP headend, RoIP terminal, and CM. The diagram shows the flow of DOCSIS downstream and upstream signals, ranging, clock synchronization, and IP packet transmission between the headend and terminal.](d4af765160d04ecef538e5066006dc77_img.jpg)
+
+The diagram illustrates the service flow of radio over Internet protocol (RoIP) service across four entities: CMTS, RoIP headend, RoIP terminal, and CM. It is organized into two primary phases:
+
+- Initialization process:**
+  - The CMTS sends a **DOCSIS downstream** signal to the RoIP headend.
+  - The RoIP headend performs **Clock synchronization** and **MAP/UCD parsing**.
+  - A **Ranging process** occurs between the CMTS and the RoIP headend, involving a **Ranging request** and **Ranging response**.
+  - The RoIP headend then performs **Network time synchronization**.
+  - The RoIP terminal also performs **Clock synchronization** and **MAP/UCD parsing** using the **Preamble pattern from UCD**.
+  - The CM receives **US allocation Info. from MAP** from the RoIP terminal.
+- Data transmission process:**
+  - The CM sends a **DOCSIS upstream** signal to the RoIP terminal.
+  - The RoIP terminal processes this through **RF signal digitization**, **Burst RF Sig. detection/time Info. acquisition**, **Compression**, **Time compensation**, **IP packetization**, and **Send RF Sig. encapsulated in IP**.
+  - The RoIP terminal sends an **IP transmission** to the RoIP headend.
+  - The RoIP headend processes this through **IP data depacketization**, **Getting signal sending time**, **Decompression**, **RF Sig. Reconstruction**, **RF scheduling**, and **DA converting/RF out**.
+  - The RoIP headend then sends a **DOCSIS upstream** signal to the CMTS.
+  - Various information flows are indicated, such as **Burst time Info.**, **Detection time/burst type**, **US allocation Info. from MAP**, and **Network time**.
+
+Sequence diagram showing the service flow of radio over Internet protocol service. It is divided into two main phases: Initialization process and Data transmission process. The participants are CMTS, RoIP headend, RoIP terminal, and CM. The diagram shows the flow of DOCSIS downstream and upstream signals, ranging, clock synchronization, and IP packet transmission between the headend and terminal.
+
+J.1107(18)\_F04
+
+Figure 4 – Service flow of radio over Internet protocol service
+
+## 8.1 Initialization process
+
+### 8.1.1 RoIP headend
+
+#### 8.1.1.1 INIT-RoIP headend-01: clock synchronization
+
+The RoIP headend synchronizes the local clock using the timestamp value included in the SYNC message of the DOCSIS downstream transmitted from the CMTS.
+
+#### 8.1.1.2 INIT-RoIP headend-02: MAP/UCD parsing
+
+The RoIP headend interprets the header information in the MAC management message frame of the DOCSIS downstream and gets the channel information, preamble information of each burst type and
+
+upstream bandwidth allocation information in order to reschedule the upstream RF burst signal from the MAP/UCD.
+
+#### **8.1.1.3 INIT-RoIP headend-03: ranging process**
+
+The RoIP headend performs the DOCSIS ranging procedure on the upstream channels allowed to be used between the RoIP headend and the CMTS.
+
+#### **8.1.1.4 INIT-RoIP headend-04: network time synchronization**
+
+The RoIP headend performs network time synchronization after performing the ranging procedure.
+
+### **8.1.2 RoIP terminal**
+
+#### **8.1.2.1 INIT-RoIP terminal-01: clock synchronization**
+
+The RoIP terminal synchronizes the local clock using the timestamp value in the SYNC message of the DOCSIS downstream transmitted from the CMTS.
+
+#### **8.1.2.2 INIT-RoIP terminal-02: MAP/UCD parsing**
+
+The RoIP terminal interprets the header information in the MAC management message frame of the DOCSIS downstream and gets the channel information, preamble information of each burst type and upstream bandwidth allocation information from the MAP/UCD in order to receive the upstream RF burst signal from the CM.
+
+## **8.2 Data transmission process**
+
+### **8.2.1 RoIP terminal**
+
+#### **8.2.1.1 DT-RoIP terminal-01: RF signal digitization**
+
+The RoIP terminal converts the upstream RF burst signal to a digital signal.
+
+#### **8.2.1.2 DT-RoIP terminal-02: burst RF signal detection/time info. acquisition**
+
+The RoIP terminal detects the upstream RF burst signal transmitted from the CM using the preamble pattern obtained from the UCD, and acquires the clock time and determines burst type at detection time.
+
+#### **8.2.1.3 DT-RoIP terminal-03: compression**
+
+The RoIP terminal may compress the upstream burst signal converted into a digital signal.
+
+#### **8.2.1.4 DT-RoIP terminal-04: time compensation**
+
+The RoIP terminal estimates and compensates a transmission time of the upstream RF burst signal using the obtained clock time of the upstream RF burst signal, the determined burst type information, and the upstream band allocation information.
+
+#### **8.2.1.5 DT-RoIP terminal-05: IP packetization**
+
+The RoIP terminal packetizes the digitized upstream RF burst signal and the compensated transmission time information to IP packets.
+
+#### **8.2.1.6 DT-RoIP terminal-06: send RF signal encapsulated in IP**
+
+The RoIP terminal transmits the upstream RF burst signal encapsulated in the IP packet.
+
+### **8.2.2 RoIP headend**
+
+#### **8.2.2.1 DT-RoIP headend-01: IP data depacketization**
+
+The RoIP headend extracts the upstream RF burst signal in the received IP packets from the RoIP terminal.
+
+#### **8.2.2.2 DT-RoIP headend-02: getting signal sending time**
+
+The RoIP headend gets the transmitted time information of the upstream RF burst signal by the CM from the received IP packet.
+
+#### **8.2.2.3 DT-RoIP headend-03: decompression**
+
+The RoIP headend is required to perform decompression procedures as the RoIP terminal performs compression.
+
+#### **8.2.2.4 DT-RoIP headend-04: RF signal reconstruction**
+
+The RoIP headend reconstructs the original digitized upstream RF burst signal from the received IP packets.
+
+#### **8.2.2.5 DT-RoIP headend-05: RF scheduling**
+
+The RoIP headend schedules the sending time of the reconstructed upstream RF signal using the upstream allocation information and the transmission time of the extracted upstream RF burst signal.
+
+#### **8.2.2.6 DT-RoIP headend-06: DA converting/RF out**
+
+The RoIP headend converts the digital upstream RF burst signal to an analogue RF burst signal and sends it to the CMTS in the cable network.
+
+# Bibliography
+
+- [b-ANSI/SCTE 135-1 2008] American National Standards Institute/Society of Cable Telecommunications Engineers, ANSI/SCTE 135-1 (2008), *DOCSIS 3.0 Part 1: Physical layer specification.*
+- [b-ANSI/SCTE 135-2 2008] American National Standards Institute/Society of Cable Telecommunications Engineers, ANSI/SCTE 135-2 (2008), *DOCSIS 3.0 Part 2: MAC and upper layer protocols.*
+- [b-ANSI/SCTE 135-4 2008] American National Standards Institute/Society of Cable Telecommunications Engineers, ANSI/SCTE 135-4 (2008), *DOCSIS 3.0 Part 4: Operations support systems interface.*
+- [b-ANSI/SCTE 135-5 2009] American National Standards Institute/Society of Cable Telecommunications Engineers, ANSI/SCTE 135-5 (2009), *DOCSIS 3.0 Part 5: Cable modem to customer premise equipment interface.*
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+|                 |                                                                                                                                                           |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A        | Organization of the work of ITU-T                                                                                                                         |
+| Series D        | Tariff and accounting principles and international telecommunication/ICT economic and policy issues                                                       |
+| Series E        | Overall network operation, telephone service, service operation and human factors                                                                         |
+| Series F        | Non-telephone telecommunication services                                                                                                                  |
+| Series G        | Transmission systems and media, digital systems and networks                                                                                              |
+| Series H        | Audiovisual and multimedia systems                                                                                                                        |
+| Series I        | Integrated services digital network                                                                                                                       |
+| <b>Series J</b> | <b>Cable networks and transmission of television, sound programme and other multimedia signals</b>                                                        |
+| Series K        | Protection against interference                                                                                                                           |
+| Series L        | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M        | Telecommunication management, including TMN and network maintenance                                                                                       |
+| Series N        | Maintenance: international sound programme and television transmission circuits                                                                           |
+| Series O        | Specifications of measuring equipment                                                                                                                     |
+| Series P        | Telephone transmission quality, telephone installations, local line networks                                                                              |
+| Series Q        | Switching and signalling, and associated measurements and tests                                                                                           |
+| Series R        | Telegraph transmission                                                                                                                                    |
+| Series S        | Telegraph services terminal equipment                                                                                                                     |
+| Series T        | Terminals for telematic services                                                                                                                          |
+| Series U        | Telegraph switching                                                                                                                                       |
+| Series V        | Data communication over the telephone network                                                                                                             |
+| Series X        | Data networks, open system communications and security                                                                                                    |
+| Series Y        | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities                               |
+| Series Z        | Languages and general software aspects for telecommunication systems                                                                                      |

marked/J/T-REC-J.1108-201901-I_PDF-E/raw.md

@@ -0,0 +1,238 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**J.1108**
+
+(01/2019)
+
+SERIES J: CABLE NETWORKS AND TRANSMISSION  
+OF TELEVISION, SOUND PROGRAMME AND OTHER  
+MULTIMEDIA SIGNALS
+
+Switched digital video over cable networks
+
+# --- **Transmission specification for radio over IP transmission systems**
+
+Recommendation ITU-T J.1108
+
+
+
+## Recommendation ITU-T J.1108
+
+# Transmission specification for radio over IP transmission systems
+
+## Summary
+
+As cable TV network is migrating to deep fibre or fibre to the home (FTTH) architecture, it is now possible and easy to provide bidirectional high quality media services that require very high speed digital transmission of various high quality contents. Cable TV networks provide services by transmitting radio frequency (RF) signals between headend and cable modems (CM), the configuration and devices of cable TV networks are optimized for RF signal transmission. For the migration of all-fibre access cable TV networks, the existing network devices of service operators (SOs) providing broadcasting services and various data services through the hybrid fibre coaxial (HFC) based cable TV network is recommended to change into the new network devices. Therefore, a cost-effective solution for deployable and acceptable migration toward an optic-based cable TV network is required.
+
+Recommendation ITU-T J.1108 provides a cost-effective adaptable solution for HFC-based cable TV network devices in an optic-based cable TV network. The purpose of a radio over IP (RoIP) system is to transmit data over cable service interface specifications (DOCSIS) based up stream (US) RF signals of a cable modem (CM) to a cable modem termination system (CMTS) through IP transmission in optic-based cable TV networks.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T J.1108   | 2019-01-13 | 9           | <a href="http://handle.itu.int/11.1002/1000/13838">11.1002/1000/13838</a> |
+
+## Keywords
+
+Radio over IP, RoIP.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 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 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 within ITU-T's 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 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 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 possibility 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 Recommendation development process.
+
+As of the date of approval of this Recommendation, 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.itu.int/ITU-T/ipr/>.
+
+© ITU 2019
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+|                                               | Page |
+|-----------------------------------------------|------|
+| 1 Scope.....                                  | 1    |
+| 2 References.....                             | 1    |
+| 3 Definitions .....                           | 1    |
+| 3.1 Terms defined elsewhere .....             | 1    |
+| 3.2 Terms defined in this Recommendation..... | 1    |
+| 4 Abbreviations and acronyms .....            | 2    |
+| 5 Conventions .....                           | 2    |
+| 6 Overview.....                               | 2    |
+| 7 Functional architecture .....               | 3    |
+| 8 Timing processing specification .....       | 3    |
+| Bibliography.....                             | 4    |
+
+
+
+## Recommendation ITU-T J.1108
+
+# Transmission specification for radio over IP transmission systems
+
+## 1 Scope
+
+Recommendation ITU-T J.1108 describes the transmission specification for a radio over IP (RoIP) transmission system in a hybrid fibre coaxial (HFC) based network. The architecture described in this Recommendation is defined according to [ITU-T J.1106]. The transmission specifications described in this Recommendation are defined as follows:
+
+- Radio over IP terminal system.
+- Radio over IP headend system.
+
+The most important part of the RoIP transmission system is having the correct network timing synchronization between the RoIP headend and RoIP terminal. The transmission specifications described in this Recommendation are defined in the timing processing specification.
+
+## 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 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 currently 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.210] Recommendation ITU-T J.210 (2006), *Downstream RF interface for cable modem termination systems*.
+- [ITU-T J.222.1] Recommendation ITU-T J.222.1 (2007), *Third-generation transmission systems for interactive cable television services – IP cable modems: Physical layer specification*.
+- [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.1106] Recommendation ITU-T J.1106 (2017), *Requirement for radio over IP transmission system*.
+- [ITU-T J.1107] Recommendation ITU-T J.1107 (2011), *Architecture and specification for radio over IP transmission systems*.
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following term defined elsewhere:
+
+**3.1.1 local clock** [b-ITU-T X.743]: The collection of hardware and software that comprises a local source of time for a system.
+
+## 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 Termination System                   |
+| DOCSIS | Data Over Cable Service Interface Specifications |
+| DS     | Down Stream                                      |
+| E/O    | Electric to Optic                                |
+| FTTH   | Fibre To The Home                                |
+| HFC    | Hybrid Fibre Coaxial                             |
+| OLT    | Optical Line Terminal                            |
+| OMUX   | Optical Multiplexer                              |
+| PON    | Passive Optical Network                          |
+| RF     | Radio Frequency                                  |
+| RoIP   | Radio over IP                                    |
+| SO     | Service Operator                                 |
+| STB    | Set-Top Box                                      |
+| US     | Up Stream                                        |
+
+## 5 Conventions
+
+In this Recommendation:
+
+The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this document 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 from which no deviation is permitted if conformance to this document 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 vendor's implementation must provide 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*, 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 normative intent.
+
+## 6 Overview
+
+The overview is defined according to clause 6 of [ITU-T J.1106].
+
+## 7 Functional architecture
+
+The functional architecture is defined according to clause 7 of [ITU-T J.1107].
+
+## 8 Timing processing specification
+
+It is important to synchronize upstream data based on the data over cable service interface specification (DOCSIS) with the existing cable network through the optical IP network (i.e., xPON networks). The most important part of the RoIP transmission system is having the correct network timing synchronization between the RoIP headend and RoIP terminal.
+
+Since many cable modems (CMs) on the subscriber side share one physical medium, it is required to transmit data according to a synchronous time-division multiplexing method, that is, the CMs are required to transmit data during time slots allocated by the cable modem termination system (CMTS). In the uplink band, the collision avoidance time of the allocated band between the terminals is 1us or less and very strict timing synchronization is required. In order to operate the RoIP transmission system, accurate timing synchronization between the terminal and the headend is required. Specifically, it is necessary to establish synchronization between the IP network and a mixed heterogeneous network, not a single RF network.
+
+Therefore, the following requirements are required to perform the function of timing processing.
+
+**TIME-REQ-01:** The RoIP terminal for terminal access network synchronization is required to synchronize the local clock which is adjusted to the CMTS reference clock using the timestamp in the SYNC message coming from the CMTS.
+
+**TIME-REQ-02:** The RoIP terminal for terminal access network synchronization is required to acquire burst time information.
+
+**TIME-REQ-03:** The RoIP terminal for terminal access network synchronization is required to estimate and compensate a transmission time.
+
+**TIME-REQ-04:** The RoIP terminal for detection and acquisition of transmission RF burst is required to store the acquisition time information.
+
+**TIME-REQ-05:** The RoIP terminal for IP network access is required to transmit the transmitted RF burst and the acquired time information.
+
+**TIME-REQ-06:** The RoIP headend for headend access network synchronization is required to synchronize the local clock which is adjusted to the CM reference clock using MAP information during DOCSIS ranging.
+
+**TIME-REQ-07:** The RoIP headend for headend access network synchronization is required to acquire the synchronized time information.
+
+**TIME-REQ-08:** The RoIP headend for RF signal scheduling of IP network interworking is required to acquire burst time information.
+
+**TIME-REQ-09:** The RoIP headend for RF signal scheduling of IP network interworking is required to schedule the received burst.
+
+**TIME-REQ-10:** The RoIP headend for RF signal reconstruction is required to reconstruct RF compressed signal.
+
+**TIME-REQ-11:** The RoIP headend for RF signal reconstruction is required to transform Digital to Analogue and frequency band.
+
+## Bibliography
+
+- [b-ITU-T X.743] Recommendation ITU-T X.743 (1998), *Information technology – Open Systems Interconnection - Systems Management: Time Management Function.*
+- [b-ANSI/SCTE 135-1] ANSI/SCTE 135-1 2013, *DOCSIS 3.0 Part 1: Physical Layer Specification.*
+- [b-ANSI/SCTE 135-2] ANSI/SCTE 135-2 2013, *DOCSIS 3.0 Part 2: MAC and Upper Layer Protocols.*
+- [b-ANSI/SCTE 135-4] ANSI/SCTE 135-4 2013, *DOCSIS 3.0 Part 4: Operations Support Systems Interface.*
+- [b-ANSI/SCTE 135-5] ANSI/SCTE 135-5 2013, *DOCSIS 3.0 Part 5: Cable Modem to Customer Premise Equipment Interface.*
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+|                 |                                                                                                                                                           |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A        | Organization of the work of ITU-T                                                                                                                         |
+| Series D        | Tariff and accounting principles and international telecommunication/ICT economic and policy issues                                                       |
+| Series E        | Overall network operation, telephone service, service operation and human factors                                                                         |
+| Series F        | Non-telephone telecommunication services                                                                                                                  |
+| Series G        | Transmission systems and media, digital systems and networks                                                                                              |
+| Series H        | Audiovisual and multimedia systems                                                                                                                        |
+| Series I        | Integrated services digital network                                                                                                                       |
+| <b>Series J</b> | <b>Cable networks and transmission of television, sound programme and other multimedia signals</b>                                                        |
+| Series K        | Protection against interference                                                                                                                           |
+| Series L        | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M        | Telecommunication management, including TMN and network maintenance                                                                                       |
+| Series N        | Maintenance: international sound programme and television transmission circuits                                                                           |
+| Series O        | Specifications of measuring equipment                                                                                                                     |
+| Series P        | Telephone transmission quality, telephone installations, local line networks                                                                              |
+| Series Q        | Switching and signalling, and associated measurements and tests                                                                                           |
+| Series R        | Telegraph transmission                                                                                                                                    |
+| Series S        | Telegraph services terminal equipment                                                                                                                     |
+| Series T        | Terminals for telematic services                                                                                                                          |
+| Series U        | Telegraph switching                                                                                                                                       |
+| Series V        | Data communication over the telephone network                                                                                                             |
+| Series X        | Data networks, open system communications and security                                                                                                    |
+| Series Y        | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities                               |
+| Series Z        | Languages and general software aspects for telecommunication systems                                                                                      |

marked/J/T-REC-J.1112-202307-I_PDF-E/raw.md

@@ -0,0 +1,234 @@
+
+
+# Recommendation**ITU-T J.112 (07/2023)**
+
+SERIES J: Cable networks and transmission of television,  
+sound programme and other multimedia signals
+
+Switched digital video over cable networks
+
+## --- **Functional requirements for IP-based digital video convergence service**
+
+![ITU logo](0538daaa5583c23e17db3a12f2281a55_img.jpg)
+
+The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with white grid lines and the letters 'ITU' in a bold, blue, sans-serif font.
+
+ITU logo
+
+## ITU-T J-SERIES RECOMMENDATIONS
+
+## Cable networks and transmission of television, sound programme and other multimedia signals
+
+|                                                                                                 |                      |
+|-------------------------------------------------------------------------------------------------|----------------------|
+| GENERAL RECOMMENDATIONS                                                                         | J.1-J.9              |
+| GENERAL SPECIFICATIONS FOR ANALOGUE SOUND-PROGRAMME TRANSMISSION                                | J.10-J.19            |
+| PERFORMANCE CHARACTERISTICS OF ANALOGUE SOUND-PROGRAMME CIRCUITS                                | J.20-J.29            |
+| EQUIPMENT AND LINES USED FOR ANALOGUE SOUND-PROGRAMME CIRCUITS                                  | J.30-J.39            |
+| DIGITAL ENCODERS FOR ANALOGUE SOUND-PROGRAMME SIGNALS - PART 1                                  | J.40-J.49            |
+| DIGITAL TRANSMISSION OF SOUND-PROGRAMME SIGNALS                                                 | J.50-J.59            |
+| CIRCUITS FOR ANALOGUE TELEVISION TRANSMISSION                                                   | J.60-J.69            |
+| ANALOGUE TELEVISION TRANSMISSION OVER METALLIC LINES AND INTERCONNECTION WITH RADIO-RELAY LINKS | J.70-J.79            |
+| DIGITAL TRANSMISSION OF TELEVISION SIGNALS                                                      | J.80-J.89            |
+| ANCILLARY DIGITAL SERVICES FOR TELEVISION TRANSMISSION                                          | J.90-J.99            |
+| OPERATIONAL REQUIREMENTS AND METHODS FOR TELEVISION TRANSMISSION                                | J.100-J.109          |
+| INTERACTIVE SYSTEMS FOR DIGITAL TELEVISION DISTRIBUTION (DOCSIS FIRST AND SECOND GENERATIONS)   | J.110-J.129          |
+| TRANSPORT OF MPEG-2 SIGNALS ON PACKETIZED NETWORKS                                              | J.130-J.139          |
+| MEASUREMENT OF THE QUALITY OF SERVICE - PART 1                                                  | J.140-J.149          |
+| DIGITAL TELEVISION DISTRIBUTION THROUGH LOCAL SUBSCRIBER NETWORKS                               | J.150-J.159          |
+| IPCABLECOM (MGCP-BASED) - PART 1                                                                | J.160-J.179          |
+| DIGITAL TRANSMISSION OF TELEVISION SIGNALS - PART 1                                             | J.180-J.189          |
+| CABLE MODEMS AND HOME NETWORKING                                                                | J.190-J.199          |
+| APPLICATION FOR INTERACTIVE DIGITAL TELEVISION - PART 1                                         | J.200-J.209          |
+| INTERACTIVE SYSTEMS FOR DIGITAL TELEVISION DISTRIBUTION (DOCSIS THIRD TO FIFTH GENERATIONS)     | J.210-J.229          |
+| MULTI-DEVICE SYSTEMS FOR CABLE TELEVISION                                                       | J.230-J.239          |
+| MEASUREMENT OF THE QUALITY OF SERVICE - PART 2                                                  | J.240-J.249          |
+| DIGITAL TELEVISION DISTRIBUTION THROUGH LOCAL SUBSCRIBER NETWORKS                               | J.250-J.259          |
+| IPCABLECOM (MGCP-BASED) - PART 2                                                                | J.260-J.279          |
+| DIGITAL TRANSMISSION OF TELEVISION SIGNALS - PART 2                                             | J.280-J.289          |
+| CABLE SET-TOP BOX                                                                               | J.290-J.299          |
+| APPLICATION FOR INTERACTIVE DIGITAL TELEVISION - PART 2                                         | J.300-J.309          |
+| MEASUREMENT OF THE QUALITY OF SERVICE - PART 3                                                  | J.340-J.349          |
+| IPCABLECOM2 (SIP-BASED) - PART 1                                                                | J.360-J.379          |
+| DIGITAL TRANSMISSION OF TELEVISION SIGNALS - PART 3                                             | J.380-J.389          |
+| MEASUREMENT OF THE QUALITY OF SERVICE - PART 4                                                  | J.440-J.449          |
+| IPCABLECOM2 (SIP-BASED) - PART 2                                                                | J.460-J.479          |
+| DIGITAL TRANSMISSION OF TELEVISION SIGNALS - PART 4                                             | J.480-J.489          |
+| TRANSPORT OF LARGE SCREEN DIGITAL IMAGERY                                                       | J.600-J.699          |
+| SECONDARY DISTRIBUTION OF IPTV SERVICES                                                         | J.700-J.799          |
+| MULTIMEDIA OVER IP IN CABLE                                                                     | J.800-J.899          |
+| TRANSMISSION OF 3-D TV SERVICES                                                                 | J.900-J.999          |
+| CONDITIONAL ACCESS AND PROTECTION                                                               | J.1000-J.1099        |
+| <b>SWITCHED DIGITAL VIDEO OVER CABLE NETWORKS</b>                                               | <b>J.1100-J.1119</b> |
+| SMART TV OPERATING SYSTEM                                                                       | J.1200-J.1209        |
+| IP VIDEO BROADCAST                                                                              | J.1210-J.1219        |
+| CLOUD-BASED CONVERGED MEDIA SERVICES FOR IP AND BROADCAST CABLE TELEVISION                      | J.1300-J.1309        |
+| TELEVISION TRANSPORT NETWORK AND SYSTEM DEPLOYMENT IN DEVELOPING COUNTRIES                      | J.1400-J.1409        |
+| ARTIFICIAL INTELLIGENCE (AI) ASSISTED CABLE NETWORKS                                            | J.1600-J.1649        |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+### Recommendation ITU-T J.1112
+
+## Functional requirements for an IP-based digital video convergence service
+
+## Summary
+
+Recommendation ITU-T J.1112 specifies functional requirements of a digital video convergence service (DVCS) based on the Internet protocol (IP) including IP-based switched digital video technologies taking into consideration a convergence environment.
+
+As digital broadcasting services have been rapidly deployed, many service operators are considering more effective transmission of digital broadcasting services. Recently, digital broadcasting services have been changed to use resources efficiently and transmit them to easily accommodate the varying needs and environments of subscribers. Therefore, it is necessary to redefine the advanced IP-based DVCS to maintain quality of service (QoS) and using bandwidth effectively for transmission on broadband network environment.
+
+The IP-based DVCS is a service mechanism for distributing digital video via IP-based broadband networks. It is the service mechanism for providing interfaces and functionalities to enable the service operators to offer QoS-guaranteed broadcasting to subscribers via IP-based converged broadband networks.
+
+## History \*
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID          |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0     | ITU-T J.1112   | 2023-07-14 | 9           | 11.1002/1000/15582 |
+
+## Keywords
+
+Digital broadcasting, digital video convergence service, IP.
+
+---
+
+\* To access the Recommendation, type the URL <https://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID.
+
+## 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 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 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 within ITU-T's 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 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 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 possibility 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 Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, 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 appropriate ITU-T databases available via the ITU-T website at <http://www.itu.int/ITU-T/ipr/>.
+
+© ITU 2023
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+|                                                | Page |
+|------------------------------------------------|------|
+| 1 Scope.....                                   | 1    |
+| 2 References.....                              | 1    |
+| 3 Definitions .....                            | 1    |
+| 3.1 Terms defined elsewhere .....              | 1    |
+| 3.2 Terms defined in this Recommendation ..... | 1    |
+| 4 Abbreviations and acronyms .....             | 1    |
+| 5 Conventions .....                            | 1    |
+| 6 Overview.....                                | 2    |
+| 7 DVCS transmission function .....             | 2    |
+| 8 DVCS transmission control function.....      | 3    |
+
+
+
+### Recommendation ITU-T J.1112
+
+### Functional requirements for IP-based digital video convergence service
+
+## 1 Scope
+
+This Recommendation specifies functional requirements of a digital video convergence service (DVCS) based on the Internet protocol (IP) taking into consideration a converged broadband environment. The functionalities described in this Recommendation are specified according to [ITU-T J.1111]. The IP-based DVCS takes into consideration a converged environment as the service mechanism for providing interfaces and functionalities to enable service operators to offer quality of service-guaranteed broadcasting. It is a service mechanism for distributing digital video via IP-based broadband networks considering convergence service.
+
+## 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 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 currently 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.1111] Recommendation ITU-T J.1111 (2022), *Requirements for the advanced IP-based digital video convergence service*.
+
+## 3 Definitions
+
+None.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+DVCS        Digital Video Convergence Service
+
+IP            Internet Protocol
+
+## 5 Conventions
+
+In this Recommendation:
+
+The phrase "**is required**" indicates a requirement that must be strictly followed and from which no deviation is permitted if conformance to this Recommendation is to be claimed.
+
+The phrase "**is recommended**" indicates a requirement that is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance.
+
+The phrase "**is prohibited**" indicates a requirement that must be strictly followed and from which no deviation is permitted if conformance to this Recommendation is to be claimed.
+
+The phrase "**can optionally**" indicates an optional requirement that is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendor's implementation must provide the option and the feature can be optionally enabled by the network operator or service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with the specification.
+
+In this Recommendation, the words *shall*, *shall not*, *should* and *may* sometimes appear, in which case they are to be interpreted, respectively, as *is required*, *is prohibited*, *is recommended*, and *can optionally*. The appearance of such phrases or verbal forms in an appendix or in material explicitly marked as informative are to be interpreted as having no normative intent.
+
+## 6 Overview
+
+A DVCS should be able to incorporate functions for transmission and its control. The DVCS transmission function should be able to generate transmission information for the convergence service and generate configuration information of a service delivered to a transmission network such as a broadcasting or communication network according to the transmission information. The DVCS transmission function should be able to receive the content for the DVCS conforming to the media storage standard format. In addition, it should be possible to create a segment suitable for convergence transmission based on the received content, packetize it into a form suitable for convergence transmission protocol, and generate related metadata. The DVCS transmission control function should be able to determine the operation policy so that the convergence service can be transmitted based on information about service use and information related to service operation. In addition, it should be possible to coordinate system parameters related to interworking relationships between convergence services and efficient service transmission. The DVCS transmission control function should be able to receive service usage information from the convergence transmission receiver and determine the service transmission method by reflecting the transmission network usage status of the receiver, network load and characteristics of the service to be transmitted.
+
+## 7 DVCS transmission function
+
+7.1 [DVCS-TR-FSPEC-001] The DVCS transmission function is recommended to receive convergence service contents in the form of standard media file formats from the file system.
+
+7.2 [DVCS-TR-FSPEC-002] The DVCS transmission function is recommended to receive convergence service configuration information and metadata from the convergence transmission control function.
+
+7.3 [DVCS-TR-FSPEC-003] The DVCS transmission function is recommended to receive parameters for signalling and multiplexing from the convergence transmission control function.
+
+7.4 [DVCS-TR-FSPEC-004] The DVCS transmission function is recommended to transmit the packetized media transport stream.
+
+7.5 [DVCS-TR-FSPEC-005] The DVCS transmission function is recommended to transmit the signalling data.
+
+## 8 DVCS transmission control function
+
+8.1 [DVCS-TC-FSPEC-001] The DVCS transmission control function is recommended to efficiently operate network and control services.
+
+8.2 [DVCS-TC-FSPEC-002] The DVCS transmission control function is recommended to generate data and control information required for service signalling related to transmission.
+
+8.3 [DVCS-TC-FSPEC-003] The DVCS transmission control function is recommended to coordinate system parameters related to efficient service delivery.
+
+8.4 [DVCS-TC-FSPEC-004] The DVCS transmission control function is recommended to determine a service transmission method by receiving service use information from the receiver and reflecting the receiver's transmission network usage status, network load, and characteristics of the service to be transmitted.
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+|                 |                                                                                                                                                           |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A        | Organization of the work of ITU-T                                                                                                                         |
+| Series D        | Tariff and accounting principles and international telecommunication/ICT economic and policy issues                                                       |
+| Series E        | Overall network operation, telephone service, service operation and human factors                                                                         |
+| Series F        | Non-telephone telecommunication services                                                                                                                  |
+| Series G        | Transmission systems and media, digital systems and networks                                                                                              |
+| Series H        | Audiovisual and multimedia systems                                                                                                                        |
+| Series I        | Integrated services digital network                                                                                                                       |
+| <b>Series J</b> | <b>Cable networks and transmission of television, sound programme and other multimedia signals</b>                                                        |
+| Series K        | Protection against interference                                                                                                                           |
+| Series L        | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M        | Telecommunication management, including TMN and network maintenance                                                                                       |
+| Series N        | Maintenance: international sound programme and television transmission circuits                                                                           |
+| Series O        | Specifications of measuring equipment                                                                                                                     |
+| Series P        | Telephone transmission quality, telephone installations, local line networks                                                                              |
+| Series Q        | Switching and signalling, and associated measurements and tests                                                                                           |
+| Series R        | Telegraph transmission                                                                                                                                    |
+| Series S        | Telegraph services terminal equipment                                                                                                                     |
+| Series T        | Terminals for telematic services                                                                                                                          |
+| Series U        | Telegraph switching                                                                                                                                       |
+| Series V        | Data communication over the telephone network                                                                                                             |
+| Series X        | Data networks, open system communications and security                                                                                                    |
+| Series Y        | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities                               |
+| Series Z        | Languages and general software aspects for telecommunication systems                                                                                      |

marked/J/T-REC-J.1201-202201-I_PDF-E/raw.md

@@ -0,0 +1,391 @@
+
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**J.1201**
+
+(01/2022)
+
+SERIES J: CABLE NETWORKS AND TRANSMISSION  
+OF TELEVISION, SOUND PROGRAMME AND OTHER  
+MULTIMEDIA SIGNALS
+
+Smart TV operating system
+
+---
+
+**Smart television operating system – Functional  
+requirements**
+
+Recommendation ITU-T J.1201
+
+
+
+# Recommendation ITU-T J.1201
+
+## Smart television operating system – Functional requirements
+
+## Summary
+
+Recommendation ITU-T J.1201 specifies the functional requirements for a smart television operating system (TVOS) over integrated broadcast and broadband (IBB) cable networks. A smart TVOS is intended to be installed in an IBB-capable cable set top box (STB) and television (TV) and to enable broadcasting and interactive services based on the Internet protocol (IP) provided by cable TV operators and third parties. By running a smart TVOS, the IBB-capable cable STB and TV are able to intelligently provide subscribers with advanced and personalized services by downloading and installing advanced and personalized apps from the platforms of cable operators and third parties, which are interconnected with them.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T J.1201   | 2019-01-13 | 9           | <a href="http://handle.itu.int/11.1002/1000/13840">11.1002/1000/13840</a> |
+| 2.0     | ITU-T J.1201   | 2022-01-13 | 9           | <a href="http://handle.itu.int/11.1002/1000/14871">11.1002/1000/14871</a> |
+
+## Keywords
+
+Functional requirements, smart TV operating system, TVOS.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## 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 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 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 within ITU-T's 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 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 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 possibility 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 Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, 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 appropriate ITU-T databases available via the ITU-T website at <http://www.itu.int/ITU-T/ipr/>.
+
+© ITU 2022
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+|                                               | 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 .....            | 3    |
+| 5 Conventions .....                           | 3    |
+| 6 General requirements.....                   | 4    |
+| 6.1 System functional requirements .....      | 4    |
+| 6.2 System architecture requirements.....     | 5    |
+| 6.3 Software code tree requirements .....     | 5    |
+| 6.4 System interface requirements .....       | 5    |
+| 6.5 System security requirements.....         | 6    |
+| 6.6 Performance requirements.....             | 7    |
+| Bibliography.....                             | 8    |
+
+# Introduction
+
+This Recommendation is the first in a series on a smart television operating system (TVOS). The Recommendations for this smart TVOS cover functional requirements, architecture, and security and application programming interfaces (APIs):
+
+Smart television operating system – Functional requirements (ITU-T J.1201)
+
+Smart television operating system – Architecture [b-ITU-T J.1202]
+
+Smart television operating system – Specification [b-ITU-T J.1203]
+
+Smart television operating system – Security framework [b-ITU-T J.1204]
+
+Smart television operating system – Hardware abstract layer application programming interface [b-ITU-T J.1205]
+
+## Recommendation ITU-T J.1201
+
+## Smart television operating system – Functional requirements
+
+# 1 Scope
+
+This Recommendation specifies functional requirements for a smart television operating system (TVOS) over integrated broadcast and broadband (IBB) cable networks. The smart TVOS is intended to be installed in an IBB-capable cable set top box (STB) and TV and to enable broadcasting and interactive services based on the Internet protocol (IP) provided by cable TV operators and third-parties. By running the smart TVOS, the IBB-capable cable STB and TV are able to intelligently provide subscribers with advanced and personalized services by downloading and installing advanced and personalized apps from the platforms of cable operators and third-parties that are interconnected with them.
+
+# 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 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 currently 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.205] Recommendation ITU-T J.205 (2012), *Requirements for an application control framework using integrated broadcast and broadband digital television*.
+- [ITU-T J.218] Recommendation ITU-T J.218 (2007), *Cable modem IPv4 and IPv6 eRouter specification*.
+- [ITU-T J.295] Recommendation ITU-T J.295 (2012), *Functional requirements for a hybrid cable set-top box*.
+- [ECMA 262] ECMA-262 (2021), *ECMAScript® 2021 language specification*.
+- [W3C CSS2.1] W3C CSS2.1 (2011), *Cascading style sheets level 2 revision 1 (CSS 2.1) specification*.
+- [W3C DOM2 Core] W3C DOM2 Core (2030), *Document object model (DOM) level 2 core specification*.
+- [W3C DOM2 Events] W3C DOM2 Events (2020), *Document object model (DOM) level 2 events specification*.
+- [W3C DOM2 HTML] W3C DOM2 HTML (2020), *Document object model (DOM) level 2 HTML specification*.
+- [W3C DOM2 Style] W3C DOM2 Style (2020), *Document object model (DOM) level 2 style specification*.
+- [W3C DOM2 Trav] W3C DOM2 Traversal and Range (2020), *Document object model (DOM) level 2 traversal and range specification*.
+- [W3C DOM2 Views] W3C DOM2 Views (2020), *Document object model (DOM) level 2 views specification*.
+
+|                 |                                                                                        |
+|-----------------|----------------------------------------------------------------------------------------|
+| [W3C DOM3 Core] | W3C DOM3 Core (2004), <i>Document object model (DOM) level 3 core specification</i> .  |
+| [W3C HTML5]     | W3C HTML5.2 (2017), <i>HTML5 A vocabulary and associated APIs for HTML and XHTML</i> . |
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 integrated broadcast and broadband (IBB) DTV service** [ITU-T J.205]: A service that simultaneously provides an integrated experience of broadcasting and interactivity relating to media content, data and applications from multiple sources, where the interactivity is sometimes associated with broadcasting programmes.
+
+**3.1.2 second screen** [ITU-T J.295]: This refers to a display screen of mobile phones or other network-enabled devices that show services associated with the television screen.
+
+**3.1.3 social television** [ITU-T J.295]: This is a general term for technology that supports communication and social interaction in either the context of watching television, or related to TV content. It includes the study of television-related social behaviour, devices and networks. Social television systems can for example integrate voice communication, text chat, presence and context awareness, TV recommendations, ratings, or video-conferencing with the TV content, either directly on the screen or by using ancillary devices.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 cable digital television service (cable DTV service)**: Any DTV service, delivered through cable.
+
+**3.2.2 dual-platform version of a smart television operating system (TVOS-C)**: TVOS software that supports both Java and web applications.
+
+**3.2.3 functional component interface**: An interface for a software module in the functional component layer.
+
+**3.2.4 hardware abstraction interface**: An interface for a software module in the hardware abstraction layer.
+
+**3.2.5 rich execution environment (REE)**: An extensible and versatile operating environment that brings flexibility and capability.
+
+**3.2.6 single-platform version of a smart television operating system (TVOS-H)**: TVOS software that supports only web applications.
+
+**3.2.7 start-up time**: The interval between power-on and appearance of video and sound for an integrated broadcast and broadband -capable cable set top box and television.
+
+**3.2.8 smart television operating system (TVOS)**: A system software running on an integrated broadcast and broadband-capable (IBB-capable) cable set top box (STB) and television (TV) that is capable of managing hardware, software and data resources of the IBB-capable cable STB and TV, supporting and controlling the application software execution.
+
+**3.2.9 trusted execution environment (TEE)**: A secure area of the main processor in an integrated broadcast and broadband-capable cable set top box and television to ensure that sensitive data is stored, processed and protected in an isolated and trusted environment. It offers isolated safe execution of authorized security software providing end-to-end security by enforcement of
+
+protected execution of authenticated code, confidentiality, authenticity, privacy, system integrity and data access rights.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|        |                                                                |
+|--------|----------------------------------------------------------------|
+| API    | Application Programming Interface                              |
+| AV     | Audio/Video                                                    |
+| DTV    | Digital Television                                             |
+| EPG    | Electronic Programme Guide                                     |
+| HAL    | Hardware Abstraction Layer                                     |
+| HCI    | Human-Computer Interaction                                     |
+| IBB    | Integrated Broadcast and Broadband                             |
+| IP     | Internet Protocol                                              |
+| JS     | JavaScript                                                     |
+| REE    | Rich Execution Environment                                     |
+| STB    | Set Top Box                                                    |
+| TEE    | Trusted Execution Environment                                  |
+| TV     | Television                                                     |
+| TVOS   | Television Operating System                                    |
+| TVOS-C | dual-platform version of a smart Television Operating System   |
+| TVOS-H | single-platform version of a smart Television Operating System |
+| VOD    | Video On Demand                                                |
+
+# 5 Conventions
+
+In this Recommendation:
+
+The phrase "is required to" indicates a requirement that must be strictly followed and from which no deviation is permitted if conformity with this document is to be claimed.
+
+The phrase "is recommended" indicates a requirement that is recommended but which is not absolutely required. Thus this requirement needs not be present to claim conformity.
+
+The phrase "is prohibited from" indicates a requirement that must be strictly followed and from which no deviation is permitted if conformity with this document is to be claimed.
+
+The phrase "can optionally" indicates an optional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendor's implementation must provide the option and the feature can be optionally enabled by the network operator or service provider. Rather, it means the vendor may optionally provide the feature and still claim conformity with this Recommendation.
+
+In the body of this document and its annexes, the words *shall*, *shall not*, *should*, 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 normative intent.
+
+# **6 General requirements**
+
+## **6.1 System functional requirements**
+
+#### **6.1.1 Cable digital television service**
+
+A smart TVOS is required to support playback of the content provided by broadcast DTV services as specified in [ITU-T J.295]. See also [b-GB/T 28160] and [b-ETSI EN 301 192].
+
+### **6.1.2 Video-on-demand service**
+
+A TVOS is required to support playback of the content provided by IP-based video on demand (VOD) and pay-per-view services as specified in [ITU-T J.295], and shall support playback of the content provided by IP quadrature amplitude modulation-based VOD services.
+
+### **6.1.3 Integrated broadcast and broadband digital television service**
+
+A TVOS is required to support playback of the content provided by IBB DTV services as specified in [ITU-T J.205]. See also [b-ETSI TS 102 809].
+
+#### **6.1.4 Local media playing**
+
+A TVOS is required to support playback of the medial files stored in the local storage medium of the IBB-capable cable STB and TV.
+
+#### **6.1.5 Media processing**
+
+A TVOS media processing is required to support unified media processing of both Java and web-based media applications, and is required to support video and audio decoder as specified in [ITU-T J.295]. See also [b-ISO/IEC 14496-12].
+
+#### **6.1.6 Electronic programme guide**
+
+A TVOS is required to support parsing and presentation of electronic programme guide (EPG) information as specified in [ITU-T J.295]. See also [b-GB/T 28161] and [b-ETSI TS 102 851].
+
+#### **6.1.7 Second screen interaction capability**
+
+A TVOS is required to have second screen interaction capabilities as specified in [ITU-T J.295].
+
+#### **6.1.8 Smart home**
+
+A TVOS is recommended to have smart home capabilities that can identify, establish connection with and control smart home devices.
+
+#### **6.1.9 Terminal control**
+
+A TVOS is required to have terminal control capability that can query, count, configure and monitor the information and parameters of the IBB-capable cable STB and TV, and report the information to the terminal control head-end, so that it can configure terminal restart and trigger software upgrade of the IBB-capable cable STB and TV as specified in [ITU-T J.295].
+
+#### **6.1.10 Management of subscriber information**
+
+A TVOS is required to support a gathering function of subscriber information including viewing history and application usage as specified in [ITU-T J.295].
+
+#### **6.1.11 Application software support**
+
+A TVOS-H platform is required to support web applications. A TVOS-C platform is required to support both Java applications and web applications.
+
+#### **6.1.12 Application management**
+
+A TVOS is required to support management functions of installation, uninstallation and updating applications through unidirectional broadcast network or IP network.
+
+#### **6.1.13 Upgrade support**
+
+A TVOS is required to support secure local system upgrade, and remote system upgrade through unidirectional broadcast network or IP network as specified in [ITU-T J.295].
+
+#### **6.1.14 Power saving**
+
+A TVOS is required to support power saving states of IBB-capable cable STB and TV as specified in [ITU-T J.295].
+
+#### **6.1.15 Dual-IPv4/v6 stack**
+
+A TVOS is required to have a dual-stack function to support both IPv4 and IPv6 as specified in [ITU-T J.218].
+
+#### **6.1.16 Social television**
+
+A TVOS is required to support social TV services as specified in [ITU-T J.295].
+
+## **6.2 System architecture requirements**
+
+A TVOS is required to consist of a REE and TEE.
+
+A TVOS REE is required to employ a hierarchical and modular software architecture that typically consists of five loosely coupled functional software layers of: kernel; hardware abstraction layer (HAL); functional component; execution environment; and application framework. Each functional software layer shall consist of multiple loosely coupled software modules. A TVOS TEE shall consist of the secure operating system, TEE HAL, and trusted application.
+
+A TVOS functional component layer is required to support conveniently adding and tailoring components according to system functional requirements and is required to support multiple execution environments. TVOS functional components are required to be independent from each other.
+
+A TVOS execution environment layer is required to support conveniently adding and tailoring execution environments. TVOS execution environments are required to be independent from each other. Each TVOS execution environment is required to have its own application framework.
+
+A TVOS application framework layer is required to have independent application frameworks corresponding to execution environments.
+
+A TVOS is required to support, independently, multiple types of applications such as Java applications and web applications.
+
+## **6.3 Software code tree requirements**
+
+The TVOS code is recommended to be managed in a hierarchical manner and should be allocated carefully to create binary code for different platforms easily.
+
+## **6.4 System interface requirements**
+
+To provide ease of application development and system extension, a TVOS is required to include application programming interfaces (APIs), functional component interfaces and hardware abstract interfaces. TVOS APIs are used to provide a common application environment for various IBB-capable cable STB and TV implementations; see [b-ETSI TS 102 809]. TVOS functional component interfaces are used to expand IBB-capable cable STB and TV functionalities.
+
+TVOS hardware abstract interfaces are used to provide facility to extend the hardware of IBB-capable cable STB and TV. These purposes can be achieved by following example structures.
+
+TVOS APIs include those for the web and Java.
+
+TVOS Java APIs consist of functional interface units of the Digital Audio Video Council (DAVIC), unidirectional broadcast network access, broadcast protocol processing, bidirectional broadband access, human-computer interaction (HCI), audio/video (AV) setting, media processing, message management and application engine. The Java functional interface units implement Java native interface encapsulation for interfaces of software modules in TVOS functional component layers, and provide Java applications with invocation interfaces in Java object mode, and assist applications in implementing IBB DTV services such as an EPG channel list, and TV programme playing. TVOS Java APIs are recommended to be compatible with Android APIs.
+
+TVOS web APIs consist of HTML5-related functional interface units and TVOS specific functional interface units.
+
+The HTML5-related functional interface units support the HTML5 interface [W3C HTML5], cascading style sheet interface [W3C CSS2.1], JavaScript (JS) interface [ECMA 262] and document object model (DOM) interface [W3C DOM3 Core], [W3C DOM2 HTML], [W3C DOM2 Core], [W3C DOM2 Events], [W3C DOM2 Style], [W3C DOM2 Trav], [W3C DOM2 Views].
+
+TVOS specific functional interface units consist of unidirectional broadcast network access, broadcast protocol processing, bidirectional broadband access, HCI, AV setting, media processing, message management, application engine, conditional access and broadcast information service units (see [b-ETSI EN 301 192]).
+
+TVOS specific functional interface units implement JS interface encapsulation for interfaces of software modules in the TVOS functional component layer, and provide web applications with invocation interfaces in JS object mode, and assist applications in implementing IBB DTV services such as an EPG, channel list and TV programme playing.
+
+There shall be some functional component interfaces that support invocation of the functional interface units of Java and web applications.
+
+The hardware abstract interfaces mask the lower-layer hardware differences and allow functional components to invoke hardware functions through unified interfaces.
+
+## 6.5 System security requirements
+
+TVOS security is required to provide the following aspects: a TVOS security mechanism, security architecture, fundamental security capabilities and basic functionalities.
+
+A TVOS security mechanism shall include a secure computational mechanism based on a TEE, a secure trust mechanism based on a digital certificate, a secure trust chain verification mechanism based on a secure chipset and hardware trust root as well as a video content protection mechanism based on a secure video path (see [b-OIFR-APP]).
+
+TVOS security architecture should establish how TVOS fundamental security capabilities can be built and expanded based on TVOS software architecture and the security mechanism, and shall include the protection methods of runtime software security, which determine how TVOS system software and application software can be sandboxed.
+
+TVOS fundamental security capabilities shall include hardware security, software security, network security, data security (see [b-ISO/IEC 23001-7]) and application security. The hardware security capability shall include a secure storage area and hardware trust root key, and shall support a TEE.
+
+TVOS basic functionalities shall include content security, service security and payment security. TVOS basic functionalities also shall include secure upgrade and boot based on hardware security. TVOS basic functionalities shall be able continuously to be enhanced and expanded through the
+
+improvement of TVOS fundamental capabilities and addition of more secure functional components.
+
+## **6.6 Performance requirements**
+
+### **6.6.1 Start-up time requirements**
+
+With typical hardware configuration or computational environment support, a TVOS with basic software settings is recommended to support an IBB-capable cable STB with a time interval between power-on and appearance of the first screen of a few seconds, and a TVOS with basic software settings is recommended to support an IBB-capable cable STB with the minimized start-up time so that viewers' viewing experiences are not impaired.
+
+#### **6.6.2 Live channel switching time requirements**
+
+With a typical hardware configuration or computational environment support, a TVOS with basic software settings is recommended to support an IBB-capable cable STB with minimum switchover time between high definition channels.
+
+## Bibliography
+
+- [b-ITU-T J.1202] Recommendation ITU-T J.1202 (2022), *Smart television operating system – Architecture*.
+- [b-ITU-T J.1203] Recommendation ITU-T J.1203 (2022), *Smart television operating system – Specification*.
+- [b-ITU-T J.1204] Recommendation ITU-T J.1204 (2022), *Smart television operating system – Security framework*.
+- [b-ITU-T J.1205] Recommendation ITU-T J.1205 (2022), *Smart television operating system – Hardware abstract layer application programming interface*.
+- [b-ETSI EN 301 192] ETSI EN 301 192 V1.7.1 (2021), *Digital video broadcasting (DVB); DVB specification for data broadcasting*.
+- [b-ETSI TS 102 809] ETSI TS 102 809 V1.3.1 (2017), *Digital video broadcasting (DVB); Signalling and carriage of interactive applications and services in hybrid broadcast/broadband environments*.
+- [b-ETSI TS 102 851] ETSI TS 102 851 V1.3.1 (2012), *Digital video broadcasting (DVB); Uniform resource identifiers (URI) for DVB systems*.
+- [b-GB/T 28160] Chinese standard GB/T 28160-2011, *Specification of electronic programme guide for digital television broadcasting* [in Chinese].
+- [b-GB/T 28161] Chinese standard GB/T 28161-2011, *Specification of service information for digital television broadcasting* [in Chinese].
+- [b-ISO/IEC 14496-12] ISO/IEC 14496-12:2020, *Information technology – Coding of audio-visual objects – Part 12: ISO base media file format*.
+- [b-ISO/IEC 23001-7] ISO/IEC 23001-7:2016, *Information technology – MPEG systems technologies – Part 7: Common encryption in ISO base media file format files*.
+- [b-OIFR-APP] Open IPTV Forum (2014), *OIPF – Release 2 Specification – Volume 7 – Authentication, content protection and service protection V2.3*.
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+|                 |                                                                                                                                                           |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A        | Organization of the work of ITU-T                                                                                                                         |
+| Series D        | Tariff and accounting principles and international telecommunication/ICT economic and policy issues                                                       |
+| Series E        | Overall network operation, telephone service, service operation and human factors                                                                         |
+| Series F        | Non-telephone telecommunication services                                                                                                                  |
+| Series G        | Transmission systems and media, digital systems and networks                                                                                              |
+| Series H        | Audiovisual and multimedia systems                                                                                                                        |
+| Series I        | Integrated services digital network                                                                                                                       |
+| <b>Series J</b> | <b>Cable networks and transmission of television, sound programme and other multimedia signals</b>                                                        |
+| Series K        | Protection against interference                                                                                                                           |
+| Series L        | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M        | Telecommunication management, including TMN and network maintenance                                                                                       |
+| Series N        | Maintenance: international sound programme and television transmission circuits                                                                           |
+| Series O        | Specifications of measuring equipment                                                                                                                     |
+| Series P        | Telephone transmission quality, telephone installations, local line networks                                                                              |
+| Series Q        | Switching and signalling, and associated measurements and tests                                                                                           |
+| Series R        | Telegraph transmission                                                                                                                                    |
+| Series S        | Telegraph services terminal equipment                                                                                                                     |
+| Series T        | Terminals for telematic services                                                                                                                          |
+| Series U        | Telegraph switching                                                                                                                                       |
+| Series V        | Data communication over the telephone network                                                                                                             |
+| Series X        | Data networks, open system communications and security                                                                                                    |
+| Series Y        | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities                               |
+| Series Z        | Languages and general software aspects for telecommunication systems                                                                                      |