hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.4.5.3 CICAM AppMMI application launch | Figure 23 depicts an example scenario of the launch of CICAM AppMMI applications. The operator provisions the CICAM with one or more applications. Applications are associated with an application domain and an XML AIT file. The mechanism by which the operator provisions these applications to the CICAM is out of the scop... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.4.5.4 Broadcast application launches CICAM broadcast application | Figure 24 depicts an example scenario of the launch of CICAM AppMMI applications. The operator provisions the CICAM with one or more applications. Applications are associated with an application domain and an XML AIT file. The mechanism by which the operator provisions those applications to the CICAM is out of the scop... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.5 Host application environments | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.5.1 General | Clause 12.5.2 notes what needs to be defined by an application environment specification that intends to make use of the framework to provision and launch applications from the CICAM. Clause 12.5.3 lists the methods by which the CICAM is able to determine the application environments supported by the Host. |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.5.2 Application provision on a CICAM | In order for a middleware system or application environment to include the facility to provision and launch applications that are compliant with that system from a CICAM according to the present document, the middleware system needs to define an identification of the middleware system and an object which allows the Hos... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.5.3 Determining Host application environment support | A CICAM is able to discover which application environment(s) a Host supports in two ways: • From the sequence of data_broadcast_id listed in the application_capability_byte field of the operator_search_start() APDU in the operator profile resource. • By the FileSystemAck() APDU AckCode value received from the Host for ... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 13 DVB Host Control version 3 | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 13.1 General | DVB Host Control resource version 3 (with resource ID 0x00200043) is an extension to version 2 and adds the following features: • The capability to tune directly to a logical channel number, including the CICAM Virtual Channel and IP-delivered services. • The capability to tune directly to an IP location. • The capabil... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 13.2 DVB Host Control version 3 APDUs | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 13.2.1 tune_broadcast_req APDU | The tune_broadcast_req() APDU defined in clause 14.6.2.1 in CI Plus V1.3 [3] is extended as shown in Table 97. The Host shall respond to this with a tune_reply() APDU. ETSI ETSI TS 103 205 V1.4.1 (2019-05) 127 Table 97: tune_broadcast_req APDU Syntax Number of bits Mnemonic tune_broadcast_req() { tune_broadcast_req_tag... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 13.2.2 tune_triplet_req APDU | The tune_triplet_req() APDU replicates the tune() APDU defined in clause 8.5.1.1 of the DVB-CI specification [1], but it omits the network_id parameter and adds the dsd_type parameter, to enable the CICAM to specify from which broadcast system the service is to be obtained. It also adds the tune_quietly_flag and the ke... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 13.2.3 tune_lcn_req APDU | The tune_lcn_req() APDU is sent by the CICAM to the Host in order to tune the Host directly to a service by the LCN. Its syntax is shown in Table 99. The Host shall respond to this APDU with a tune_reply() APDU. This APDU cannot be used to tune between channel lists. The Host shall resolve the LCN according to its acti... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 13.2.4 tune_ip_req APDU | The tune_ip_req() APDU is sent by the CICAM to the Host to provide the location of a single IP-delivered service to which the Host is requested to connect. Its syntax is shown in Table 100. The Host shall respond to this with a tune_reply() APDU. Table 100: tune_ip_req APDU Syntax Number of bits Mnemonic tune_ip_req ()... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 13.2.5 tuner_status_req APDU | The tuner_status_req() APDU is sent by the CICAM to the Host to gain knowledge of what broadcast delivery systems are supported by the Host, and the likely success of a tune depending on the delivery system type. Its syntax is shown in Table 101. The Host shall reply to this APDU with the tuner_status_reply() APDU. Tab... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 13.2.6 tuner_status_reply APDU | The tuner_status_reply() APDU is sent by the Host in response to the tuner_status_req() APDU. The Host uses this APDU to inform the CICAM which broadcast delivery system or systems it supports, and which of them is likely to give a successful tune, and whether it supports IP-delivered services. The APDU syntax is shown... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 14 CICAM Virtual Channel | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 14.1 Introduction | This clause specifies the mechanism by which the user is able to select to run an application or high-level MMI session offered by the CICAM. The application or high-level MMI session is offered as a Virtual Channel entry in the Host's channel line-up. When the Virtual Channel is selected by the user, the CICAM applica... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 14.2 Application Information version 4 | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 14.2.1 General | Application Information resource (resource ID 0x00020044) version 4 adds a new command (APDU), namely the enter_cicam_channel() APDU, that requests the launch of the application associated with the CICAM Virtual Channel. Since the Virtual Channel does not have any associated content in a TS, the usual mechanism for the... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 14.2.2 enter_cicam_channel APDU | The syntax of the enter_cicam_channel()APDU is shown in Table 103. On reception of this APDU, the CICAM shall stop descrambling the Local TS indicated by the LTS_id parameter that it may still be receiving. In single-stream mode the LTS_id parameter shall be ignored. Table 103: enter_cicam_channel APDU syntax Syntax Nu... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 15 Operator Profile version 2 | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 15.1 Introduction | Operator Profile Version 2 (with resource ID 0x008F1002) adds the following new features: • A new profile_type which enables the Host to construct a combined logical channel list from the received broadcast SI and additional services provided by the CICAM, signalled in the extended CICAM NIT. • The ability for the CICA... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 15.2 Profile Type 2 | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 15.2.1 Introduction | In addition to profile_type = 0 and profile_type = 1 specified in CI Plus V1.3 [3], the new profile_type = 2 is specified as follows: • profile_type = 2 - Profiled operation where the Host constructs a logical channel list from the broadcast SI and the CICAM NIT. The broadcast SI takes precedence over the CICAM NIT. Th... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 15.2.2 Initialization and profile discovery | A CICAM that reports profile_type = 2 supports a partial channel list to be integrated with a channel list constructed from the broadcast SI. The Host is expected to install the broadcast channel list before installing the operator profile channel lists. The Host then informs of any collisions in requested logical chan... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 15.2.3 Moving between profiles | There is no facility to move into or out of profile type of type 2, so the Host does not need to inform the CICAM that it is in this profile. ETSI ETSI TS 103 205 V1.4.1 (2019-05) 133 |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 15.2.4 LCN collision management | On reception of the CICAM NIT, the Host shall add the operator profile services to the logical channel list. If the Host sees two LCN which are not unique, the Host shall keep the broadcast SI service in its logical channel list. The Host shall inform the CICAM which LCN and service from the CICAM NIT is not unique to ... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 15.3 CICAM Virtual Channel | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 15.3.1 CICAM Virtual Channel descriptor | The CICAM Virtual Channel descriptor defined in Table 104 shall be present in the first loop of the CICAM NIT and shall be preceeded by the CI Plus private data specifier descriptor. The CICAM Virtual Channel may be interpreted by the Host as a data broadcast service. The descriptor provides a LCN, service name, event ... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 15.3.2 Selection of the CICAM Virtual Channel | The Host shall use the Application Information resource version 4, as specified in clause 14, to inform the CICAM that the CICAM Virtual Channel has been selected by the user. |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 15.3.3 Operator NIT management APDU | The operator_nit_management() APDU shall be sent by the Host at most once per CICAM NIT to inform the CICAM when there is an issue with the CICAM NIT. On reception of this APDU, the CICAM may update the CICAM NIT to resolve any issue reported by the Host. If the CICAM does not provide an updated CICAM NIT, the Host sha... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 15.4 IP delivered services | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 15.4.1 operator_status() APDU | The operator_status() APDU is extended to add the option to the delivery_system_hint field, using the reserved bit in Operator Profile version 1, as defined in Table 14.42 in the CI Plus V1.3 specification [3]. Table 108 shows the set of delivery_system_hint values for Operator Profile version 2. Table 108: delivery_sy... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 15.4.2 IP service discovery and update | For IP delivered services, the CICAM NIT may include one or more uri_linkage_descriptors in the first loop of the CICAM NIT. The uri_linkage_descriptor is defined in the DVB SI specification [10], clause 6.4.14. Only uri_linkage_descriptors containing a uri_linkage_type with value 0x00 are defined for use within this s... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 15.4.3 operator_osdt_request APDU | The Host sends this APDU to the CICAM to query the current OSDT file. Its syntax is shown in Table 109. The CICAM shall reply with an operator_osdt_reply() APDU returning the OSDT to the Host. Table 109: operator_osdt_request APDU syntax Syntax No. of bits Mnemonic operator_osdt_request() { operator_osdt_request_tag le... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 15.4.4 operator_osdt_reply APDU | The CICAM shall send this APDU to the Host in response to an operator_osdt_request() APDU. Its syntax is shown in Table 110. The APDU, if successful, contains the latest OSDT file. Table 110: operator_osdt_reply APDU syntax Syntax No. of bits Mnemonic operator_osdt_reply () { operator_osdt_reply_tag length_field() osdt... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 16 High-Level MMI | A general recommendation is that High-Level MMI should be implemented on the Host in a way so as to avoid disruption to applications that may be running on the Host. The following additional requirements are specified, which clarify the Host minimum capabilities relating to High-Level MMI, as specified in CENELEC EN 50... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 17 Operator Profile version 3 | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 17.1 General | Operator Profile resource version 3 (with resource ID 0x008F1003) is an extension to version 3 and adds fine grained negotiation of the Host supported component types and the component types that are actually used in a service. |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 17.2 Operator Profile version 3 APDUs | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 17.2.1 operator_codec_verify_req APDU | The CICAM may send the operator_codec_verify_req() APDU to the Host to verify that the Host is capable of presenting a service with a given combination of components of different types. The Host shall reply with an operator_codec_verify_reply() APDU. The CICAM should send the operator_codec_verify_req() APDU when the s... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 17.2.2 operator_codec_verify_reply APDU | The Host shall send this APDU to the CICAM in response to the operator_codec_verify_req() APDU, to inform about the support of each of the combination requested for verification. This information is used by the CICAM to determine if installation of services corresponding to a combination is required. The CICAM may send... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 17.3 ciplus_advanced_service_descriptor | The ciplus_advanced_service_descriptor extends the ciplus_service_descriptor by a loop of component types. For services where the service_type alone does not fully allow a receiver to determine the specific type of the service (e.g. for HEVC service_types 0x1F or 0x20), this loop shall be used to indicate the specific ... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 18 CICAM Player version 2 | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 18.1 General | CICAM Player resource version 2 (with resource ID 0x00930042) is an extension to version 1 and adds fine grained advertisement of the Host supported component types. |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 18.2 CICAM Player version 3 APDUs | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 18.2.1 CICAM_player_codec_verify_req APDU | The CICAM may send the CICAM_player_codec_verify_req() APDU to the Host to verify that the Host is capable of presenting a service with a given combination of components of different types. The Host shall reply with an CICAM_player_codec_verify_reply() APDU. ETSI ETSI TS 103 205 V1.4.1 (2019-05) 141 The combination of ... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 18.2.2 CICAM_player_codec_verify_reply APDU | The Host shall send this APDU to the CICAM in response to the CICAM_player_codec_verify_req() APDU, to inform about the support of each of the combination requested for verification. The CICAM may send the CICAM_player_codec_verify_reply() APDU to the Host to verify that the Host is capable of presenting a service cont... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 19 Usage Rules Information (URI) version 5 | Versions 1 and 2 of this message are defined in clause 5.7.1 of CI Plus 1.3 [3]. Version 3 of this message is defined in clause 11. Version 4 is defined in clause 22.2.1. The present document specifies an extension to the CI Plus Usage Rules Information (URI) by defining version 5 of the CI Plus URI for the purpose of ... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 20 Clarifications on usage of Content Control System ID | Clause 11.3.1.2 of CI Plus 1.3 [3] defines how a Host can advertise the set of CC system IDs that it supports by use of the cc_system_id_bitmask as indicated in the cc_open_cnf() APDU. From the list of the CC system IDs that are supported by the Host, the CICAM shall select the applicable CC system ID and use a cc_syst... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 21 Application Information version 5 | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 21.1 General | Version 1 of this resource with the resource type 0x00020041 is defined in clause 8.4.2 of CENELEC EN 50221 [1]. Version 2 of this resource with the resource type 0x00020042 is defined in clause 5 of ETSI TS 101 699 [2]. Version 3 of this resource with the resource type 0x00020043 is defined in clause 11.1 of CI Plus [... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 21.2 APDU extensions | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 21.2.0 Application Information resource summary | Table 119: Application Information resource summary Resource Application Object Direction Name Resource Identifier Cl a s s T y p V er si o n APDU Tag Tag value H o st CI C A Application 00 02 00 45 2 1 5 application_info_enq 9F 80 20 Information application_info 9F 80 21 enter_menu 9F 80 22 request_CICAM_reset 9... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 21.2.1 Host diagnostic screen APDUs | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 21.2.1.0 General | The Host Diagnostic Screen APDUs are used to request the Host to display a diagnostic screen about itself to the viewer. This information can be useful to the viewer when troubleshooting viewing of controlled content, for example by reading the information to a customer support agent on the phone. Since not all Hosts i... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 21.2.1.1 HDS request APDU | Table 120: hds_request APDU syntax Syntax No. of bits Mnemonic hds_request() { hds_req_tag 24 uimsbf length_field() variable reserved_future_use 7 bslbf hds_command 1 uimsbf } hds_req_tag: This 24-bit field indicates the type of APDU message, and shall be coded according to Table 119. hds_command: This 1-bit field indi... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 21.2.1.2 HDS confirmation APDU | Table 122: hds_confirm APDU syntax Syntax No. of bits Mnemonic hds_confirm() { hds_cnf_tag 24 uimsbf length_field() variable reserved_future_use 6 bslbf hds_status 2 uimsbf } hds_cnf_tag: This 24-bit field indicates the type of APDU message, and shall be coded according to Table 119. hds_status: This 2-bit field indica... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 21.2.2 Power down APDUs | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 21.2.2.0 General | The power_down_notice() APDU is used to announce to the CICAM that the Host intends to remove power from the CICAM soon. The CICAM is given a grace period. If the CICAM does not wish to use the grace period, it can inform the Host by using the power_down_ok() APDU so that power can be removed immediately. |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 21.2.2.1 Power down notice APDU | This APDU shall be sent by the Host before entering a power mode where the CICAM will be powered down. Host shall give a minimum of 30 seconds notice before powering down the CICAM. This is allowing the CICAM to perform operations which should not be delayed like e.g. a firmware update or a channel map update. During t... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 21.2.2.2 Power down OK APDU | This APDU shall be sent by the CICAM after receiving a power_down_notice() APDU to signal the Host that CICAM does not have any more pending operation to perform and that the Host may power it down immediately. This message should be sent as early as possible to reduce power consumption of the system. Table 125: power_... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 22 Content Control version 4 (multi-stream version 2) | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 22.1 General | Version 1 of this resource with the resource type 0x008C1001 is defined in clause 11.3 of CI Plus [3]. Version 2 of this resource with the resource type 0x008C1002 is defined in clause 11.3 of CI Plus [3]. Version 3 of this resource with the resource type 0x008C1003 is defined in clause 11. Clause 6.4.3 of the present ... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 22.2 Protocol extensions | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 22.2.1 Usage Rules Information (URI) version 4 | Versions 1 and 2 of this message are defined in clause 5.7.1 of CI Plus [3]. Version 3 of this message is defined in clause 11. The present clause specifies an extension to the CI Plus Usage Rules Information (URI) by defining version 4 of the CI Plus URI. Version 5 of this message is defined in clause 19. Table 126: U... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 22.2.2 Output Control protocol | Table 128 shows the Output Control protocol for use with version 2 of this resource with the resource type 0x008C1042 for multi-stream. The output_num parameter shall use a datatype_id set to value 51, and indicates the number of simultaneous outputs of different CI Plus controlled content received from a CICAM, which ... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 23 Content Control version 5 (multi-stream version 3) | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 23.1 Negotiation of optional features | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 23.1.1 General | The Content Control (CC) single stream resource version 5 (type 0x008C1005) and multi-stream resource version 3 (type 0x008C1043) include a negotiation protocol to decouple optional features from the CC resource version. This enables the definition of optional features without the need for new CC resource versions, and... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 23.1.2 Negotiation protocol for optional features | Devices that support CC resource version 5 or multi-stream version 3 shall support the protocol for the negotiation of optional features for use with those resources. The CICAM may only run the optional features protocol at power-up after the URI version negotiation. Before this protocol is completed, the Host and CICA... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 23.1.3 Data type for optional features | The optional_features parameter is a 32-bit bitmask used by the Host to convey the list of optional features it supports to the CICAM, and shall use a datatype_id value set to 52. Each bit corresponds to one single optional feature. If an optional feature is supported by the Host, it shall set the corresponding bit (='... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 24 Optional Content Control Features | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 24.1 List of optional features | Table 130 contains the list of optional CC features defined in the present document. Additional optional features may be added in future versions of the present document. NOTE: Bit 0 refers to the least significant bit of the optional_features parameter. Table 130: CC resource optional features Bit Feature Definition 0... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 24.2 Overt Watermarking | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 24.2.1 General | The overt watermarking feature enables the CICAM to request the Host to display a text string over the video as a means of identifying the source of the content (e.g. a subscriber ID). Overt watermarking is sometimes referred to as fingerprinting, although the latter term has an additional meaning relating to the ident... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 24.2.2 Overt watermark content | The overt watermark shall consist of a 7-bit prinTable ASCII text string, with configurable font size, colour, opacity and position. ETSI ETSI TS 103 205 V1.4.1 (2019-05) 152 |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 24.2.3 Logical plane, rendering and displaying | The Host uses overt watermark text and parameters communicated by the CICAM to render the watermark, i.e. to construct the graphical element representing the watermark, which the Host then displays over its video plane. Figure 25: Overt watermark rendering and display sequence (informative) Overt watermarking uses a lo... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 24.2.4 Overt watermarking data types | 24.2.4.1 wm_instructions (CICAM Host) The wm_instructions parameter of variable length contains the watermark text and rendering parameters, as defined in Table 131, and shall use a datatype_id value set to 53. Table 131: wm_instructions data type Syntax Number of bits Mnemonic wm_instructions () { position_x 16 uims... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 24.2.5 Overt watermarking protocol | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 24.2.5.1 Displaying an overt watermark | Table 134 describes the overt watermarking protocol used by a CICAM to request the Host to display an overt watermark. In single-stream mode, the LTS_id shall be set to the fixed value of 0x47, but it may be safely ignored by the device receiving the message. In multi-stream mode, the LTS_id identifies the Local TS tha... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 24.2.5.2 Host status updates | Table 135 describes the overt watermarking protocol used by the Host to provide overt watermark rendering status updates to the CICAM. Table 135: Overt watermarking protocol for providing status updates Step Action APDU Content 1 Host reports a change in the status of the watermark rendering cc_sac_data_req send_dataty... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 24.2.5.3 CICAM removing an overt watermark | Table 136 describes the overt watermarking protocol used by the CICAM to request the Host to remove an overt watermark. Table 136: Overt watermarking protocol for removing an overt watermark Step Action APDU Content 1 CICAM instructs the Host to stop rendering the watermark cc_sac_data_req send_datatype_nbr = 2 index d... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 24.2.5.4 Host removing an overt watermark | The Host shall stop rendering the watermark when a channel change occurs that causes the Host to no longer display the watermark's corresponding programme. In such a case, the Host shall not report a change in watermark rendering status, the CA_PMT sent during programme selection with a different program_number and a c... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 24.2.6 Overt watermarking during recording and playback | When recording a CA protected service, the Host shall associate overt watermark instructions (i.e. text, parameters, rendering status) received with the recording, at the time they were received, so they can be displayed at the same position in the content during playback. When the Host has initiated a recording using ... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 24.2.7 Overt watermarking during playback of IP-delivered content | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 24.2.7.1 General | The same overt watermarking protocol shall be used during playback of IP-delivered content as when descrambling and displaying live broadcast content, as defined in clause 24.2.5, with the following differences. |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 24.2.7.2 Overt watermarking in CICAM player mode | When in CICAM player mode, a CICAM shall only ask the Host to display an overt watermark for content it can descramble after it has received CICAM_player_start_reply() from the Host during establishment of the CICAM player session, with input_status set to 0x00 (OK). ETSI ETSI TS 103 205 V1.4.1 (2019-05) 157 The Host s... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 24.2.7.3 Overt watermarking in Host player mode | When in Host player mode, a CICAM shall only ask the Host to display an overt watermark for content it can descramble after it has sent sd_start_reply() to the Host with transmission_status set to 0x00 (ready to receive) and drm_status set to 0x00 (decryption possible), during establishment of the Host player session. ... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 24.2.8 Overt watermarking sequence (informative) | [13] cc_sac_data_cnf(LTS_id+program_number+wm_rendered) [9] cc_sac_data_cnf(LTS_id+program_number+wm_rendered) [3] cc_sac_data_cnf(LTS_id+program_number+wm_rendered) [1] ca_pmt(program_number) [2] cc_sac_data_req(LTS_id+program_number+wm_instructions) Host CICAM [5] cc_sac_data_cnf(LTS_id+program_number) [4] cc_sac_dat... |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 1 Scope | |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 1.1 Purpose | The present document defines the Management Event Mechanism that IPCablecom elements can use to report asynchronous events that indicate malfunction situations and notification about important non-fault situation. Events are defined in the present document as conditions requiring the reporting of information to managem... |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 1.2 Introduction | The present document is one of two documents that together define a framework for reporting Management Events in the IPCablecom architecture. The present document defines the general event reporting mechanism and framework. The mechanism consists of a set of protocols and interfaces that can be used by individual eleme... |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 2 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 reference document (including any amendments) applies. Referenced documents which ar... |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 103 161-20: "Access, Terminals, Transmission and Multiplexing (ATTM); Integrated Broadband Cable and Television Networks; IPCablecom 1.5; Part 20: Management Event MIB Specification". [2] ETSI TS 103 161-11: "Acces... |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TS 103 161: "Access, Terminals, Transmission and Multiplexing (ATTM); Integrated Broadband Cable and Television Networks; IPCablecom 1.5". [i.2] ... |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 3 Definitions and abbreviations | |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: network management: functions related to the management of data across the network |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: BSD Berkeley Software Distribution CDR Call Detail Record CMIP Common Management Information Protocol CMS Call Management Server CMTS Cable Modem Termination System DHCP Dynamic Host Configuration Protocol DNS Domain Name Server DOCSIS® Data O... |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 4 Void |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.