hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.5.9 org.hbbtv.ipplayer.selectComponents | Requests the player to make changes to the set of components selected for presentation. These requests shall conform to a schema whose normative definition is found in Annex H of the present document. This method is called by the terminal whenever one or more selected components needs to change. Example of when this ma... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.5.10 org.hbbtv.ipplayer.resolveTimeline | Requests the player to provide a mapping from a specific timeline to the play position of the HTML media element being used to present the operator application presented channel. These requests shall conform to a schema whose normative definition is found in Annex H of the present document. ETSI ETSI TS 103 606 V1.2.1 ... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.5 Regular application control of media presentation | This clause defines the behaviour of the video/broadcast object when an operator application presented channel is selected. It applies when a video/broadcast object is not in the Unrealized state and an operator application presented channel is selected. This can arise if a regular HbbTV® application or operator applic... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 10 Capabilities | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 10.1 Terminal capabilities and functions | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 10.1.1 Component selection | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 10.1.1.1 Introduction | Default component selection by the Terminal and additional component selection by regular HbbTV® applications is defined in clause 10.2.7 of ETSI TS 102 796 [1]. The present document specifies the different methods of component selection by operator applications, in line with the approach defined in clause 10.2.7 of ET... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 10.1.1.2 Component selection via user preferences | An operator application shall be able to set any of the following properties of the Configuration class as defined in clause A.1: • preferredAudioLanguage, as defined in clause 7.3.2 of the OIPF DAE specification [29]. When the preferredAudioLanguage property is set to a new value, all subsequent reads of either prefer... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 10.1.1.3 Direct component selection via BroadcastSupervisor class | In all operator application states, the operator application shall be able to directly select components of the currently presented broadcast content using the method selectComponent of the BroadcastSupervisor class as defined in clause A.2.5. The terminal shall maintain such changes made by an operator application unt... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 10.1.1.4 Standard direct component selection | If the operator application is in the Foreground state or Overlaid foreground state, the operator application shall be able to use all standard methods of direct component selection for content that it is presenting itself as defined in clause 10.2.7.3 of ETSI TS 102 796 [1]. The terminal shall maintain such changes ma... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 10.1.1.5 Clarification of component selection by regular HbbTV® applications | Clause 10.2.7.3 of ETSI TS 102 796 [1] defines that a terminal shall maintain a change in component selection which was requested by a regular HbbTV® application until one of a set of events occurs. The following event shall be added to that set: • An operator application makes a further change: - in which case compone... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 10.1.2 Minimum terminal capabilities | Minimum terminal capabilities which shall be available to applications are listed in table 16 for general capabilities. Additional capabilities shall be signalled as defined in clause 10.1.4. Table 16: Minimum terminal capabilities Value for regular operator applications Value for privileged operator applications Value... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 10.1.3 User Input | For Privileged and Operator-specific operator applications, the rules governing access to key events differ from those of regular HbbTV® applications and table 17 takes precedence over clause 10.2.2.1 of ETSI TS 102 796 [1]. The Type column defines when an operator application receives key events for the associated key... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 10.1.4 HbbTV® reported capabilities and option strings | The present document does not define any extensions to the reported capabilities and option strings defined in clause 10.2.4 of ETSI TS 102 796 [1]. NOTE: Diversity between terminal models should be addressed as part of the bilateral agreement. Private extensions to the XML capabilities are possible. |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 11 Security | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 11.1 Overview | From time to time terminals will require privileged access to resources available from specific servers. Whilst it is usual for remote terminals to authenticate servers over TLS, further provision has to be made to enable terminals to be recognized and securely authenticated by servers in a managed way as a basis for p... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 11.2 Device and Server Authentication | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 11.2.1 Mutual TLS Authentication | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 11.2.1.1 Overview | Terminals and operator applications may use mutual TLS authentication to verify the trust of one another. Mutual TLS authentication refers to the server requesting and verifying an X.509 client certificate during the TLS handshake process. ETSI ETSI TS 103 606 V1.2.1 (2024-03) 100 Mutual TLS authentication may be used ... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 11.2.1.2 Client certificate | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 11.2.1.2.1 Client certificate overview | Terminals shall provide a client certificate if requested to do so during the TLS handshake process. Client certificates may have a hierarchy depicted in figure 2. The client certificate shall be issued by either by an intermediate certificate authority or a self-signed root certificate authority. It is good practice f... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 11.2.1.2.2 Operational considerations | In order that operators are able to remotely authenticate the manufacturer terminals over TLS, the manufacturers shall provide and release to operators subject to the bilateral agreement the appropriate Client CA anchor certificate, (either the self-signed Client Root CA certificate or alternative Client Intermediate C... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 11.2.1.2.3 Client Root and Intermediate Certificate Authority Certificate Profiles | The manufacturer's Client Root Certificate Authority (Client Root CA) shall issue either a client certificate or one or more Intermediate Certificate Authority (Client Intermediate CA) certificates. The Client Root CA shall manage a certificate revocation list dedicated to the revocation of these intermediate CA certif... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 11.2.1.2.4 Client certificate profile | The terminal shall contain a valid client certificate and associated private key to enable the terminal to authenticate to a server over TLS. The client certificate shall be a standard X.509 v3 certificate conforming to IETF RFC 5280 [11] with the additional constraints profiled in table 20 and table 21. • The public k... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 11.2.2 Device authentication in broadcast (informative) | There is no equivalent of explicit device authentication using TLS client certificates for broadcast-only deployments. In order for an operator application to be installed, it needs to be decrypted using the private key corresponding to the terminal packaging certificate(s) of a trusted manufacturer. It is recommended ... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 11.3 Operator application authentication | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 11.3.1 Encrypted application package overview | This clause defines how to create the encrypted application package using the application ZIP file as defined in clause 7.4 with authentication information. The file is signed, encrypted and packaged into a Cryptographic Message Syntax (CMS) message (IETF RFC 5652 [12]) for delivery to a terminal as defined in clause 1... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 11.3.2 Operator Signing Certificate | In order to sign an application package, an Operator signing key is used and published in an Operator Signing Certificate. Each Operator Signing Certificate is issued by a self-signed Operator Signing Root CA as described in figure 3. Operators may use an intermediate CA to provide better separation between different s... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 11.3.3 Terminal Packaging Certificate | Manufacturers may create a hierarchy as described in figure 4 including the use of Intermediate CAs to provide better separation between different packaging certificates. Manufacturers shall create a Terminal Packaging Certificate that is either self-signed or signed by a self-signed Manufacturer Packaging Root CA cert... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 11.3.4 Encrypted application packaging process | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 11.3.4.1 Encrypted application packaging process overview | Clauses 11.3.4.2 and 11.3.4.3 describe the signing and encryption processes used by the operator to generate an encrypted application package, using the Operator Signing Certificate (see clause 11.3.2) and Terminal Packaging Certificates (see clause 11.3.3). Clauses 11.3.4.4 and 11.3.4.5 describe the decryption and sig... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 11.3.4.2 Operator application signing process | This clause describes the process of packaging an application ZIP file into a CMS SignedData structure. This structure is then encrypted into a CMS EnvelopedData structure according to clause 11.3.4.3. A CMS SignedData shall be constructed according to section 5 of IETF RFC 5652 [12], with the following additional requ... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 11.3.4.3 Process for encrypting an application package | To create the final encrypted application package, the operator shall use the CMS SignedData defined in clause 11.3.4.2 to create an CMS EnvelopedData defined in section 6 of IETF RFC 5652 [12], with the following additional requirements: • The contentEncryptionAlgorithm used to encrypt the data shall be set to either ... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 11.3.4.4 Process for decrypting an application package | After downloading the encrypted application package as defined in clause 6.1.7, terminals shall decrypt the encrypted application package to access the application zip file according to the following process. The terminal shall use the private key of the Terminal Packaging Certificate to decrypt the EncryptedKey of the... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 11.3.4.5 Application ZIP package signature verification process | After decrypting the encrypted application package as defined in clause 11.3.4.4, terminals shall verify the resulting CMS SignedData according to the following process. Terminals shall use the Operator Signing Root CA to verify the certificates included in the certificates block of the CMS SignedData structure as deta... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 11.4 CI Plus | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 11.4.1 CI Plus communication | Clause 4.2.3.4.1.1 of OIPF CSP [15] specifies how and when the terminal sets up a session to the CI Plus SAS resource (as specified in CI Plus Specification v1.3.2 [5]) for messaging between the terminal and the CICAM. In addition to this session and at the same time, the terminal shall open an additional session to th... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 11.4.2 IP Delivery CICAM Player Mode | Terminals supporting the "IP delivery CICAM player mode" as defined in the DVB Extensions to CI Plus ETSI TS 103 205 [7] shall support the use of "Host-initiated playback" (as defined in clause 8.3.2 of [7]) in combination with the HTML5 video element as defined in Annex F of the present document. |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 12 Privacy | In the case of privileged operator applications, use of an operator application is entirely a user choice. Terminals are also required to allow the user to uninstall a privileged operator application (see clause 6.7). In the case of operator-specific operator applications, the operator application essentially forms a p... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 13 Media synchronization | Operator applications have access to the same media synchronization functions as regular HbbTV® applications. Operator applications shall be able to enable multi-stream and inter-device synchronization for content being presented by an operator application video/broadcast object, A/V control object or HTML5 video eleme... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 14 Companion screens | Privileged and operator-specific operator applications shall be able to use application to application communications as defined in clause 14.5 of ETSI TS 102 796 [1] simultaneously with a regular HbbTV® application also using that feature. Terminals shall support at least the number of concurrent WebSocket connections... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 15 Communication with regular HbbTV® applications | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 15.1 General | Terminals shall implement a mechanism for communication between operator-applications and regular HbbTV® applications. The implementation and behaviour of this mechanism shall be identical to that of application-to- application communications defined in clause 14.5 of ETSI TS 102 796 [1] but with the differences as des... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 15.2 Service endpoints provided by the terminal | The terminal shall provide two service endpoints as defined in clause 14.5.2 of ETSI TS 102 796 [1]. However, instead of there being a remote endpoint and a local endpoint there shall instead be two local endpoints as follows: • A local "operator application endpoint" for connecting to by clients that are HbbTV® operat... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 15.3 Handling of new connections from clients | The terminal shall be able to handle new connection requests as specified in clause 14.5.3 of ETSI TS 102 796 [1] and shall support the same minimum number of concurrent connections. |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 15.4 Connection Pairing | Connection pairing shall follow the same process as defined in clause 14.5.4 of ETSI TS 102 796 [1]. Connections to the operator application endpoint shall only be paired with connections to the regular application endpoint and vis- versa. NOTE: The URLs for the endpoints are not advertised via the terminal and service... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 15.5 Paired Connections | Paired connections shall behave as defined in clause 14.5.5 of ETSI TS 102 796 [1] including requirements for minimum payload sizes and traffic rates. However, instead of sending the UTF-8 encoded text message 'pairingcompleted', the terminal shall send a UTF-8 encoded text message containing a JSON object with the fol... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 1 Scope | The present document defines USB physical, link and transport layers for the DVB Common Interface to replace the PC Card interface defined in CENELEC EN 50221 [1]. The present document also profiles and extends the application layer defined in CENELEC EN 50221 [1], ETSI TS 101 699 [2] and CI Plus specification [3] to c... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 2 References | |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 3 Definition of terms and abbreviations | |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 3.1 Terms | For the purposes of the present document, the terms given in CENELEC EN 50221 [1], ETSI TS 101 699 [2], CI Plus™ specification v1.3.2 [3], ETSI TS 103 205 [4] and the following apply: cipher block size: size of the unit of operation of a block-based cipher algorithm DVB-CI command interface: interface used to transfer ... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in CENELEC EN 50221 [1], ETSI TS 101 699 [2], CI Plus™ specification v1.3.2 [3], ETSI TS 103 205 [4] and the following apply: CENC Common ENCryption scheme NOTE: See ISO/IEC 23001-7 [9]. MPEG Moving Pictures Expert Group |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 4 Mechanical and electrical characteristics | |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 4.1 Mechanical characteristics | |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 4.1.1 Connector | The CICAM shall have a USB 2.0 Standard-A plug as defined in clause 6.5.4 of USB 2.0 [5], or a USB 3.1 Standard-A plug as defined in clause 5.3.1 of USB 3.2 [6]. NOTE: The compatibility between USB 2.0 and USB 3.1 plugs and receptacles is described in clause 5.2.1 of USB 3.2 [6]. Since the Standard-A is the most widesp... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 4.1.2 Mechanical properties | To be able to be plugged directly into a Host, a CICAM shall not exceed the size limits defined in table 1. These limits do not include the USB Standard-A plug [5] and USB 3.2 [6]. If a CICAM is designed to not be directly plugged into a Host (e.g. by using a flying lead), it may exceed these size limits. A Host shall ... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 4.2 Electrical characteristics | The CICAM shall work within the electrical characteristics defined in USB 2.0 [5] or USB 3.2 [6]. A Host which implements one or more USB 2.0 slots with the mechanical characteristics defined in clause 4.1.2, shall allow for high-power bus-powered functions as defined in clause 7.2.1 of USB 2.0 [5] on these ports. NOTE... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 5 Module discovery and capabilities description | |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 5.1 General | For describing the CICAM during bus enumeration, the following rules shall apply: a) In the device descriptor, the CICAM shall report a device Class code of 0xEF, SubClass 0x02, and DeviceProtocol 0x01 to indicate a multi-interface function class, for which the information is given in the Interface Association Descript... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 6 Command interface | |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 6.1 Command endpoints | CICAM Interface shall contain two endpoints for command transfer: one bulk IN endpoint and one bulk OUT endpoint. Endpoint sizes shall be at least 64 bytes for transfer efficiency. NOTE: A 64 byte endpoint size with 1 USB packet transferred per micro frame gives around 4 Mbit/s transfer rate which is above the required... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 6.2 Command data encapsulation | |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 6.2.1 USB transfer format | Data transferred over command endpoints shall be SPDUs as defined by CENELEC EN 50221 [1], chapter 7.2 "Session Layer". Data can be either a standalone SPDU (Topen_session_request, Topen_session_response, Tclose_session_request, Tclose_session_response) or an SPDU Tsession_number followed by an APDU. Tcreate_session_re... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 6.3 Modification to resources and APDU | |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 6.3.1 Introduction | Once the USB device enumeration is complete (an USB configuration supporting DVB-CI has been set) the CICAM shall continue with the initialization process as defined in clause 8.4.1.1 of ETSI TS 103 205 [4]. The behaviour of some resources and APDUs defined in CI Plus specifications [2] and [3] needs to be adjusted for... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 6.3.2 Application information | |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 6.3.2.1 request_ci_cam_reset APDU | This APDU, defined in CI Plus specification [3], clause 11.1.2, shall not be sent by the CICAM. NOTE 1: The CICAM can reset itself and force a re-enumeration at USB level as specified in USB 2.0 [5], clause 9.1. NOTE 2: This APDU was introduced with version 3 of the resource in CI Plus specification [3]. |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 6.3.2.2 data_rate_info APDU | This APDU, defined in CI Plus specification [3], clause 11.1.3.1, shall not be sent by the Host. NOTE: This APDU was introduced with version 3 of the resource in CI Plus specification [3]. |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 6.3.3 Low Speed communication | This resource, defined in CI Plus specification [3], clauses 14.1 and 14.2, shall not be offered by the Host. IP communication shall instead happen over the USB CDC EEM Networking Interface defined in clause 8 of the present document. |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 6.3.4 CAM upgrade | |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 6.3.4.1 cam_firmware_upgrade_complete APDU | This APDU is defined in CI Plus specification [3], clause 14.3.5.5. The reset_request_status field shall be ignored by the Host. NOTE: The CICAM can reset itself and force a re-enumeration at USB level as specified in USB 2.0 [5], clause 9.1. |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 7 Media interface | |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 7.1 Introduction | A CICAM may offer one or more media interfaces as defined in the present clause. ETSI ETSI TS 103 605 V1.1.1 (2018-10) 16 As shown in figure 8, ISOBMFF samples or MPEG TS packets shall be mapped into one or more Fragments according to clauses 7.4 and 7.5, using a fragment header (which is defined in clause 7.7) precedi... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 7.2 Media endpoints | A CICAM media interface shall offer one pair of media interface stream endpoints. Media endpoint sizes shall be at least 128 bytes for transfer efficiency. For the highest transfer efficiency, it is recommended that the CICAM supports the maximum possible endpoint size. NOTE: For USB 2 the maximum endpoint size is 512 ... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 7.3 Use of USB3.1 bulk streams | If the device supports bulk streams and the Host chooses to use them, data for an LTS_id shall only be carried with a single bulk Stream ID. A bulk stream may carry data for more than one LTS_id, however. The CICAM shall not change the LTS_id to bulk Stream ID mapping when returning data received from the Host. For the... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 7.4 MPEG TS content encapsulation | |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 7.4.1 Mapping MPEG TS packets to fragments | MPEG TS Fragments shall be composed of an integral number of MPEG TS packets from the same local transport stream. ETSI ETSI TS 103 605 V1.1.1 (2018-10) 17 Figure 7: TS Packet mapping overview |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 7.4.2 Protection of MPEG TS content from CICAM to Host | When data transported over the Media interface is MPEG TS packets, the CICAM shall scramble this data if required using the mechanism described in clause 5.6 of CI Plus specification [3]. |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 7.5 Sample content encapsulation | |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 7.5.1 Mapping samples to fragments | A sample may be mapped into one or more Fragments. A Fragment shall not contain data from more than one sample. A fragment is composed of one or more subsamples. DVB Transport Stream DP DP HDR HDR USB Data Packets Metadata T1 T2 T3 T4 USB Transfers DP DP DP DP D P TS Packets = Short Packet Fragment Fragment Data Fragme... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 7.5.2 Protection of sample content from CICAM to Host | |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 7.5.2.1 Content encryption | The CICAM should encrypt every data byte which it received encrypted from the Host. To achieve this, the CICAM may have to insert some padding bytes as part of the encrypted data returned from the CICAM to the Host. These padding bytes are added to ensure that the total number of encrypted bytes is a multiple of the ci... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 7.5.2.2 Native CI Plus 2.0 Encryption | If the CICAM is using a native CI Plus 2.0 encryption and it wishes to insert padding to avoid returning any previously encrypted data unencrypted, it shall insert any padding bytes at the end of the encrypted data bytes and it shall set the crypto_reload_period in the fragment header to zero. Clear 212 bytes Encrypted... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 7.5.2.3 CI Plus1.4 Compatible Encryption | When the CICAM is a CI Plus1.4 device connected via a USB adapter device, the adapter converts the sample data in MPEG TS encapsulation format over the PC Card interface as described in clause 7.5.3 of ETSI TS 103 205 [4]. To address the encapsulation of data inside MPEG TS packet where the IV was reloaded at the begin... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 7.6 Encapsulation rules | Fragments shall be transmitted in a single USB transfer, immediately following the fragment header (see clause 7.7). NOTE 1: This means that at most one USB short packet can be present, and if so, it occurs at the end of the transfer. The following rules shall apply: a) The first fragment of a media sample which contai... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 7.7 Fragment header | |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 7.7.1 Syntax | A fragment header shall precede each Fragment. This header shall be contained in a single USB transfer, and no other data shall be present in that USB transfer. Each fragment header shall be followed by a Fragment. Table 3: Fragment header syntax Syntax No. of Bits Mnemonic fragment_header() { protocol_version 8 uimsbf... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 7.7.2 Fragment header descriptors | |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 7.7.2.1 General | This clause defines the descriptors that may be used within fragment headers. Zero or more of these descriptors may be inserted into the fragment headers specified in clause 7.7.1 as the construct "descriptor ()". The semantics defined in ETSI TS 103 205 [4], clause 7.5.5.4 apply to all of the descriptors. Table 4 list... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 7.7.2.2 CI Plus initialization vector descriptor | The ciplus_initialization_vector_descriptor(), defined in ETSI TS 103 205 [4], clause 7.5.5.4.2, table 46, is used by the Host to provide the initialization vector associated with the following sample. This descriptor is allowed to appear in a fragment header only when the first_fragment field is set to 1. |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 7.7.2.3 CI Plus key identifier descriptor | The ciplus_key_identifier_descriptor() is used by the Host to provide the content key identifier associated with the following Sample. This descriptor is allowed to appear in a fragment header only when the first_fragment field is set to 1. Its syntax is defined in ETSI TS 103 205 [4], clause 7.5.5.4.3, table 47. |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 7.7.3 Fragment header fields usage (informative) | Table 5 below summarizes the use of fragment header fields depending on the type of data transported and on the direction. ETSI ETSI TS 103 605 V1.1.1 (2018-10) 24 Table 5: Use of fragment header fields Field Host to CICAM CICAM to Host MPEG TS Samples MPEG TS Samples LTS_id LTS_id LTS_id same as received from Host sam... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 8 Networking Interface (NI) | |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 8.1 Introduction | A CICAM that requires IP connectivity shall implement a Networking Interface (NI). ETSI ETSI TS 103 605 V1.1.1 (2018-10) 25 Figure 11: Networking using USB CDC The NI is a CDC-EEM (Communication Device Class-Ethernet Emulation Model) interface as defined in USB CDC EEM [8]. The interface, if present, shall be present b... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 8.2 Descriptors | Clauses 3 and 4 of USB CDC EEM [8] require devices to provide the following descriptors. Those descriptors shall be hierarchically below the Interface Association Descriptor, but they do not need to be immediately after it: • Interface descriptor with the following values: - bClass = 0x02 (Communication Device Class) -... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 8.3 USB Control requests | Ethernet Emulation Model USB CDC EEM [8] does not impose any additional control requests or messages on Endpoint 0. All control information passes through the bulk endpoints as described in clause 5.1.2.2 of USB CDC EEM [8]. Internet Local Router DHCP LAN Firewall Host Internet netw in ’s eth wifi other CI+ netw in USB... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 8.4 Content on the bulk endpoints | Clause 5 of USB CDC EEM [8] defines an EEM Packet. It also specifies that a bulk transfer shall contain an integral number of EEM Packets. There are two types of EEM Packets: Data (in clause 5.1.2.1 of USB CDC EEM [8]) and Command (in clause 5.1.2.2 of USB CDC EEM [8]). Given that an EEM Data Packet (clause 5.1.2.1 of ... |
6ae14ac7d3534e69dfd6dc98ce29d4bb | 103 605 | 8.5 CICAM access to network services |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.