hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 7.5.5.2.3 Flush Table (FLT) | The FLT sections conform to the syntax for private sections as defined in MPEG-2 Systems [4]. The syntax of the FLT section is specified in Table 42. ETSI ETSI TS 103 205 V1.4.1 (2019-05) 77 Table 42: Flush section syntax Syntax Number of bits Mnemonic flush_section(){ table_id section_syntax_indicator reserve_future_u... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 7.5.5.3 Track-related messages | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 7.5.5.3.1 General | Messages that are related to a track, i.e. SSP and SEP are mapped as Transport Stream Packets as defined in MPEG-2 Systems [4]. In this way, it is possible to transmit the beginning (SSP) and end (SEP) signalling in the same PID stream as the Samples themselves. For a TS packet being a track-related message, the TS pac... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 7.5.5.3.2 Sample Start TS Packet (SSP) | The Sample Start TS Packet (SSP) is a track-related message as defined in clause 7.5.5.3.1. The SSP indicates the start of a Sample. For setting the TS header fields the following rules shall apply: • The payload_unit_start_indicator of a SSP shall be set to 0b1. • The transport_scrambling_control shall be set to the o... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 7.5.5.3.3 Sample End TS Packet (SEP) | The Sample End TS Packet (SEP) is a track-related message as defined in clause 7.5.5.3.1. The SEP indicates the end of a Sample. For setting the TS header fields the following rules shall apply: • The payload_unit_start_indicator of a SEP shall be set to 0b0. • The transport_scrambling_control shall be set to 0b00. For... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 7.5.5.4 Descriptors | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 7.5.5.4.1 General | This clause defines the descriptors that may be used within Sample Mode messages. Zero or more of these descriptors may be inserted into any of the messages specified in clauses 7.5.5.2 and 7.5.5.3, as the construct "descriptor ()". The following semantics apply to all of the descriptors defined in this clause. descrip... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 7.5.5.4.2 CI Plus initialization vector descriptor | The ciplus_initialization_vector_descriptor(), shown in Table 46, is used by the Host to provide the initialization vector associated with the following Sample. ETSI ETSI TS 103 205 V1.4.1 (2019-05) 80 Table 46: ciplus_initialization_vector_descriptor syntax Syntax Number of bits Mnemonic ciplus_initialization_vector_d... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 7.5.5.4.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. Its syntax is shown in Table 47. Table 47: ciplus_key_identifier_descriptor syntax Syntax Number of bits Mnemonic ciplus_key_identifier_descriptor(){ descriptor_tag 8 uimsbf descriptor_... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 7.6 URI | The CICAM shall associate some URI to a Sample decryption program, following the rules as described in the CI Plus V1.3 specification [3], in clause 5.7. The CICAM shall use the program_number indicated in the sd_start() APDU when sending a URI message to the Host. The Host shall enforce the URI received from the CICAM... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8 IP delivery CICAM player mode | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.1 General | The CI Plus V1.3 specification [3] provides support for the delivery of IP data across the Command Interface; however this has a limited throughput. Due to the increased data rate needed for the delivery of video data, the present document ETSI ETSI TS 103 205 V1.4.1 (2019-05) 81 adds support for the transfer of downst... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.2 Player controls | To enable the CICAM to manage the flow of data, it needs to be able to know when particular user actions have taken place. For example it may need to know if the user has paused the playback of the content, so that it can stop requesting data from the server. The CICAM may also need to disable the use of particular pla... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.3 Session initialization | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.3.1 General | The consumption of a service making use of the IP delivery CICAM player mode may be initiated by the CICAM, via the use of a CICAM application, or it may be requested by the Host via an IP channel defined on the channel line up or other out of scope mechanism. |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.3.2 Host-initiated playback | In this mode the user has requested content consumption (i.e. a service or asset) that the Host is unable to fulfil. Therefore the Host checks with each available CICAM to determine if there is one that is able to fulfil the content consumption. This is achieved using the CICAM_player_verify_req() APDU. This check may ... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.3.3 CICAM-initiated playback | The CICAM may at any time establish a player session with the Host in response to an event outside the scope of the present document. This is performed by the CICAM making a CICAM_player_start_req() call to the Host, signalling both the PMT of the SPTS that the CICAM will generate and output to the Host, and the bitrat... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.4 Communication errors | If the Host detects a communication error on the IP network interface then the Host shall relay this information to the CICAM across the Command Interface using the existing LSC comms_reply() APDU as defined in clause 8.7.1.5 of DVB-CI [1]. Server errors announced via protocols above TCP or UDP (e.g. HTTP over TCP) sha... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.5 Trick mode support | Where the content format, delivery protocol and CICAM support trick modes, the CICAM may manage the data flow and content to support the requested trick mode. The CICAM shall continue to output a compliant TS across the TS interface at all times during a player session. For example, in the case of fast-forward trick pl... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.6 Session termination | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.6.1 General | A player session may be terminated for any of the reasons specified in the following clauses. The list is not exhaustive. After a session termination the Host may need to re-initialize its A/V decoding and rendering functions, to avoid undesirable video and audio artifacts caused by the loss of the input stream. |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.6.2 Unrecoverable error | This is where the CICAM has detected an error condition which results in it being unable to continue the player session. The CICAM should signal to the user details of the error, for example via an MMI or application MMI message, and shall send a CICAM_player_end() APDU to the Host. If the player session was CICAM-init... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.6.3 Termination by the user | With a Host-initiated session, the Player session may be terminated at any time by the user, including when performing some action such as channel change. Whenever the Host wishes to terminate the player session, it shall send a CICAM_player_stop() APDU to the CICAM, upon which the CICAM shall terminate the session by ... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.6.4 End of content | If the CICAM reaches the end of the content asset in a Host-initiated player session, then the CICAM shall signal to the Host that the end of the content has been reached, using the CICAM_player_asset_end() APDU. When the Host receives the CICAM_player_asset_end() APDU it may then instruct the CICAM to terminate the pl... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.7 CICAM player mode sequence | Figure 18 depicts the overall sequence diagram for a typical CICAM player mode content playback session for Host- initiated playback. Figure 19, similarly, depicts the CICAM-initiated content playback session. Both figures are informative. ETSI ETSI TS 103 205 V1.4.1 (2019-05) 84 Figure 18: Example sequence diagram for... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.8 CICAM Player resource | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.8.1 General | The CICAM Player resource enables the Host to request the CICAM to initiate a play session and play a service on behalf of the Host. It also allows the CICAM to spontaneously request the initiation of a play session. The CICAM Player resource is provided by the Host. The CICAM may request a session to the CICAM Player ... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.8.2 CICAM Player resource APDUs | Table 48 lists the APDUs of the CICAM Player resource and provides a brief description of the purpose of each APDU. Table 48: CICAM Player resource APDUs APDU Direction APDU usage CICAM_player_verify_req Host CICAM Requests CICAM to check to see if the content can be consumed CICAM_player_verify_reply CICAM Host Si... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.8.3 CICAM_player_verify_req APDU | The Host may send this APDU to the CICAM to verify that the CICAM is capable of playing a content asset in IP delivery CICAM player mode. The CICAM shall reply with a CICAM_player_verify_reply() APDU. The syntax of the CICAM_player_verify_req() APDU is shown in Table 49. ETSI ETSI TS 103 205 V1.4.1 (2019-05) 87 Table 4... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.8.4 CICAM_player_verify_reply APDU | The CICAM shall send this APDU to the Host in response to the CICAM_player_verify_req() APDU. It indicates whether the CICAM is capable of playing the IP content. The syntax of the CICAM_player_verify_reply() APDU is shown in Table 50. Table 50: CICAM_player_verify_reply APDU Syntax Syntax Number of bits Mnemonic CICAM... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.8.5 CICAM_player_capabilities_req APDU | The CICAM shall send this APDU to the Host to request the set of codecs that the Host supports. This information is used by the CICAM to determine if transcoding of the source content is required. If the CICAM needs to know if a specific combination of components can be played by the Host, it shall use CICAM_player_cod... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.8.6 CICAM_player_capabilities_reply APDU | The Host shall send this APDU to the CICAM in response to the CICAM_player_capabilities_req() APDU, to inform about which codecs the Host supports. This information is used by the CICAM to determine if transcoding of the source content is required. The syntax of the CICAM_player_capabilities_reply() APDU is shown in Ta... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.8.7 CICAM_player_start_req APDU | The CICAM shall send this APDU in order to start a CICAM player session. The Host shall reserve bitrate across the TS interface for the Host to CICAM, and for the CICAM to Host directions respectively, according to the information provided by the CICAM. This APDU may contain the PMT describing the components that will ... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.8.8 CICAM_player_start_reply APDU | The Host shall send this APDU as a reply to a CICAM_player_start_req() APDU. The Host shall provide the Local TS identifier allocated for data delivery across the TS interface for this session. This identifier also serves as a unique identifier for the CICAM player session. The Host shall decide whether to create a new... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.8.9 CICAM_player_play_req APDU | The Host shall send this APDU to the CICAM to request that the CICAM plays a service on behalf of the Host. The CICAM shall reply with either a CICAM_player_status_error() APDU, in the case when an error is detected, or a CICAM_player_start_req() APDU. The syntax of the CICAM_player_play_req() APDU is shown in Table 57... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.8.10 CICAM_player_status_error APDU | The CICAM shall send this APDU to the Host in response to the CICAM_player_play_req() APDU if an error is detected. In the case where there is no error the CICAM shall send a CICAM_player_start_req() APDU instead. It may also be sent by the CICAM at any point during player session establishment or following player sess... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.8.11 CICAM_player_control_req APDU | The Host shall send this APDU to the CICAM in order to set the position, or change the speed of a current player session. The CICAM shall respond with a CICAM_player_info_reply() APDU, which signals the actual position and speed. The syntax of the CICAM_player_control_req() APDU is shown in Table 60. ETSI ETSI TS 103 2... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.8.12 CICAM_player_info_req APDU | The Host shall send this APDU to the CICAM in order to get information about the currently played content, including the duration of the content, current playout position and speed. The CICAM shall reply with a CICAM_player_info_reply() APDU. The syntax of the CICAM_player_info_req() APDU is shown in Table 63. Table 63... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.8.13 CICAM_player_info_reply APDU | The CICAM shall send this APDU as a reply to a CICAM_player_info_req() APDU. The syntax of the CICAM_player_info_reply() APDU is shown in Table 64. Table 64: CICAM_player_info_reply APDU Syntax Syntax Number of bits Mnemonic CICAM_player_info_reply() { CICAM_player_info_reply_tag length_field() = 11 LTS_id duration pos... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.8.14 CICAM_player_stop APDU | The Host sends this APDU to the CICAM in order to terminate a player session. The syntax of the CICAM_player_stop() APDU is shown in Table 65. ETSI ETSI TS 103 205 V1.4.1 (2019-05) 94 Table 65: CICAM_player_stop APDU syntax Syntax Number of bits Mnemonic CICAM_player_stop() { CICAM_player_stop_tag length_field() = 1 LT... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.8.15 CICAM_player_end APDU | The CICAM shall send this APDU in order to end a CICAM player session. This allows the Host to free up any allocated resources, e.g. bandwidth on the TS interface. The CICAM shall close all Hybrid LSC connections used by the CICAM player session before this APDU is called. The syntax of the CICAM_player_end() APDU is s... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.8.16 CICAM_player_asset_end APDU | The CICAM shall send this APDU in order to notify the Host that either the beginning or the end of the content asset has been reached. The syntax of the CICAM_player_asset_end() APDU is shown in Table 67. Table 67: CICAM_player_asset_end APDU syntax Syntax Number of bits Mnemonic CICAM_player_asset_end() { CICAM_player... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.8.17 CICAM_player_update_req APDU | The CICAM shall send this APDU in order to notify the Host of the PMT describing the components that will be delivered by the CICAM to the Host on the TS interface. This APDU shall be sent with every change of the PMT in the corresponding Local TS. The syntax of the CICAM_player_update_req() APDU is shown in Table 68. ... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.8.18 CICAM_player_update_reply APDU | The Host shall send this APDU as a reply to a CICAM_player_update_req() APDU. From the reception of this APDU, the CICAM may deliver a valid SPTS to the Host with the guarantee that the Host is ready to interpret the transport packets from the SPTS delivery start. Table 69: CICAM_player_update_reply APDU syntax Syntax ... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 8.8.19 CICAM player resource summary | Table 71 provides a summary of the attributes of the CICAM player resource. Table 71: CICAM player resource summary Resource Application Object Direction Name Resource identifier Class Type Ver. APDU tag Tag value Host CICA M CICAM player 00 93 00 41 147 1 1 CICAM_player_verify_req 9F A0 00 CICAM_player_verify_reply ... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 9 CICAM file retrieval | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 9.1 General | CICAM file retrieval is realized via a new CI Plus resource, namely the auxiliary file system resource. It provides a generic mechanism for a CICAM to offer files to the Host, including CICAM broadcast applications, which can be launched to run on the Host. The method used by a Host or running application to access thi... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 9.2 File system offer APDU | This APDU specifies the file system that is provided by the CICAM. Its syntax is shown in Table 72. The CICAM shall request a new session for each CICAM file system that it wishes to offer. Only one FileSystemOffer APDU shall be sent over each session of an auxiliary file system resource opened by the CICAM. ETSI ETSI ... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 9.3 File System Ack APDU | This APDU shall be sent by the Host in response to the FileSystemOffer() APDU to confirm whether the offered application domain is supported by the Host or not. Table 73: FileSystemAck APDU Syntax Number of bits Mnemonic FileSystemAck() { FilesystemAck_tag 24 uimsbf length_field() AckCode 8 bslbf } FileSystemAck_tag: T... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 9.4 File request APDU | This APDU is copied from the Application MMI v2 resource and is fully described in clause 14.5.1 of CI Plus V1.3 [3]. It allows the Host to support file caching and to discover reqtypes supported by the CICAM (file, data, hash, etc.). |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 9.5 File acknowledge APDU | This APDU is copied from the Application MMI v2 resource and is fully described in clause 14.5.2 of CI Plus V1.3 [3]. |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 9.6 Auxiliary file system resource summary | Table 75 provides a summary of the attributes of the auxiliary file system resource. Table 75: Auxiliary file system resource summary Resource Application Object Direction Name Resource Identifier Class Type Vers. APDU Tag Tag value Host CICA M Auxiliary file system 00 91 00 41 145 1 1 FileSystemOffer 9F 94 00 FileSy... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 10 Low Speed Communication resource version 4 | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 10.1 General | This clause specifies a new version, version 4, of the Low Speed Communication (LSC) resource, which adds features to facilitate IP delivery CICAM player mode, to the LSC resource version 3 that is defined in clause 14.1 of the CI Plus V1.3 specification [3]. Version 4 of the LSC resource extends version 3 to add suppo... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 10.2 Host IP configuration information | For some delivery mechanisms the CICAM needs to make low-level IP network calls to obtain network information. For example it may need to: • Perform a DNS lookup to establish a server's IP address from a DNS name. • Perform a DHCP query to obtain the domain in which the Host is located. Therefore the CICAM should have ... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 10.3 Information about IP streams | The present document adds support for exchanging information about the IP connection between the Host and the CICAM. A new comms_info_request() APDU is defined that enables the CICAM to obtain information about the established IP connection. In particular, for hybrid connections it defines the PID on which the TCP or U... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 10.4 IP multicast | The present document adds support for multicast streams from the Host to the CICAM across the TS interface. When the CICAM joins a multicast connection (through the multicast_descriptor as defined in clause 10.11.3), the Host shall send out an IGMP join packet and shall transfer the data received from the multicast sou... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 10.5 Source ports | For some IP connections, it may be important that the outgoing data uses the same source port as used by the Host. For instance for linear TV services with Retransmission or Fast Channel Change mechanisms as defined by DVB-IPTV [16], or for NAT traversal mechanism messages sent to different destinations, data should or... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 10.6 Host to CICAM delivery | When working with a hybrid IP connection, on receipt of IP data the Host shall encapsulate the TCP or UDP payload into TS packets as defined in clause 10.12.4 and shall deliver the resulting TS packets to the CICAM using the TS interface. Implementers should note that server errors, etc. resulting from CICAM requests w... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 10.7 CICAM to Host delivery | When a Hybrid connection has been established, the CICAM shall output to the Host an ISO/IEC 13818-1 [4] compliant TS, also respecting the TS buffer models. This TS may be protected using the existing CI Plus TS-level scrambling mechanism. The TS shall contain a PAT, and PMT for the service, along with the A/V componen... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 10.8 IP flow control | In IP delivery CICAM player mode all flow control measures shall be performed by the CICAM. When working with a pull protocol, for example HTTP, the CICAM will request data segments based on its buffer model. In the case of a push protocol, the Host shall stream the data to the CICAM with minimal delay. ETSI ETSI TS 10... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 10.9 comms_info | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 10.9.1 General | The present document introduces a new APDU to request information about an LSC session. It is only appropriate when the CICAM has requested an IP, hostname, hybrid or IP Source connection using the appropriate connection_descriptor_type. The CICAM shall use this APDU when establishing a hybrid connection after it has r... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 10.9.2 comms_info_req APDU | This APDU is sent from the CICAM to the Host in order to request detailed connection information about an LSC session operating in hybrid mode. Its syntax is shown in Table 76. Table 76: comms_info_req APDU syntax Syntax Number of bits Mnemonic comms_info_req () { comms_info_req_tag 24 uimsbf length_field() = 1 } comms... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 10.9.3 comms_info_reply APDU | This APDU shall be sent in reply to the comms_info_req() APDU from the Host to the CICAM to inform the CICAM about the source IP address used by the Host for this connection, and the PID used to transfer this information from the Host to the CICAM for Hybrid connections. The syntax is shown in Table 77. Table 77: comms... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 10.12.4.1 TS packet syntax | When using a Hybrid connection, the data received by the Host is delivered across the TS interface by encapsulating the TCP or UDP payloadin TS packets. Table 89 shows the TS packet header syntax for this encapsulation. ETSI ETSI TS 103 205 V1.4.1 (2019-05) 109 Table 89: TS packet syntax for Hybrid data transfer Syntax... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 10.12.4.2 Adaptation field usage | The adaptation field shall only be used to enable the stuffing of TS packets when the last section of IP datagram data within the TS packet does not completely fill the TS packet. This is achieved by setting the fields as follows: adaptation_field_length: This shall be set to the number of remaining bytes in the TS pac... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 10.12.4.3 Detection of last fragment of last UDP Packet on CICAM side (informative) | The last fragment of the last UDP packet can be detected either by checking for a TS packet containing an adaptation field or by implementing a timeout. The adaptation field method is usable only when the packet payload does not fit exactly into an integral number of TS packets. |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 11 Usage Rules Information version 3 | CI Plus V1.3 [3], in clause 5.7.1, contains the definitions of CI Plus URI Versions 1 and 2. The present document specifies an extension to the CI Plus Usage Rules Information (URI) by defining CI Plus URI version 3. To ensure interoperability with legacy devices, URI version 3 applies only to Content Control type 64, ... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12 CICAM applications | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.1 General | The present clause contains the specification of three aspects related to Application MMI, CICAM applications in general and their coordination with broadcast applications: • Clause 12.2 specifies extensions to the CI Plus Browser (CI Plus Engine profile, application domain "CIEngineProfile1"), specified in CI Plus V1.... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.2 CI Plus Browser extensions | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.2.1 InteractionChannelExtension | The CI Plus Engine Profile is extended to include the functionality of the InteractionChannelExtension as specified in clause 15.1.2 of the MHEG-5 Broadcast Profile specification [6], with the following exception: • In clause 15.12.2 of the MHEG-5 Broadcast Profile specification [6], Resolution of References, the hybri... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.2.2 ICStreamingExtension | The CI Plus Engine Profile is extended to include the requirements for ICStreamingExtension including clause 14.2.9 of the MHEG-5 Broadcast Profile specification [6] except that those relating to audio, video and subtitle formats are optional. It is expected that system specifications referring to the present document ... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.2.3 ICEncryptedStreamExtension | ICEncryptedStreamExtension, specified in clause 15.16 of the MHEG-5 Broadcast Profile specification [6] on "HTTP profile for delivering encrypted streams", is optional. It is expected that system specifications referring to the present document for CI Plus functionality will include separately the specification of stre... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.2.4 Video scaling | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.2.4.1 General | In CI Plus V1.3 [3] video scaling as a feature is not required in the CI Plus Engine Profile. The present document removes this exception, thus video scaling is a required feature in the CI Plus Engine Profile. The following clauses specify the consequent resulting amendments to CI Plus V1.3 [3]. ETSI ETSI TS 103 205 V... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.2.4.2 Set of features | In clause 12.2.3, Table 12.2, the row Video Scaling is removed from the list of GetEngineSupport behaviour exceptions. Table 93 lists the GetEngineSupport behaviour exceptions in the CI Plus Engine Profile compared to the MHEG-5 Broadcast Profile specification [6]. Table 93: CI Plus Engine Profile exceptions compared t... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.2.4.3 GetEngineSupport | In clause 12.2.4, Table 12.3 of the MHEG-5 Broadcast Profile specification [6], the rows VideoScaling(Chook,X,Y)[a] and VideoDecodeOffset(Chook,Level) are removed from the list of GetEngineSupport "feature" string exceptions. Table 94 lists the CI Plus Engine Profile GetEngineSupport "feature" strings. Table 94: CI Plu... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.3 Application life cycle | The CI application life cycle management tools specified in clause 12.6 of CI Plus V1.3 [3] are extended in the present clause to add the ability for the CICAM to enquire whether a particular application environment is supported in the Host without the Host attempting to launch the CICAM AppMMI application, and whether... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.4 Application Coordination Framework | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.4.1 General | CI Plus Host devices typically provide one or more application environments that can load and run applications that are either delivered via the broadcast channel or from elsewhere via a link communicated in broadcast signalling. These applications are referred to as broadcast applications. Contention may occur between... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.4.2 Modifications to referenced specifications | The DVB CI extensions [2] and CI Plus V1.3 [3] specifications leave room for various interpretations about the relative priority of CICAM AppMMI applications and broadcast applications that want to run on the Host. Hence the present document makes the following changes in these referenced specifications. ETSI ETSI TS 1... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.4.3 CICAM application launch mechanisms | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.4.3.1 General | Two separate mechanisms for starting applications provided by the CICAM are defined. The first is for CICAM AppMMI applications, as specified in ETSI TS 101 699 [2] and qualified in the context of the Application Coordination Framework in the present clause 12.4. The second, specified in clause 12.4.3.3 below, is for a... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.4.3.2 CICAM AppMMI applications | The CICAM uses the requestStart() APDU to request the Host to start an application. In this case, the files of the application are delivered using the Application MMI resource as defined in ETSI TS 101 699 [2]. ETSI ETSI TS 103 205 V1.4.1 (2019-05) 117 |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.4.3.3 CICAM broadcast applications | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.4.3.3.1 General | A CICAM broadcast application is an application that is provided on the CICAM auxiliary file system (specified in clause 9) and that the Host launches after reading the corresponding file. A CICAM broadcast application may be launched following a request by broadcast signalling or a running broadcast application. |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.4.3.3.2 Signalling CICAM broadcast applications in the broadcast stream | DVB defines a method for broadcast application signalling in ETSI TS 102 809 [7] and ETSI TS 102 727 [i.1]. This is extended to include broadcast signalling for CICAM broadcast applications, as specified in annex F. CICAM broadcast applications that are signalled within a system using the aforementioned DVB specificati... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.4.3.3.3 Advertising CICAM broadcast applications | The present clause specifies the method by which the CICAM advertises applications stored on its auxiliary file system (see clause 9) to the Host. Each CICAM broadcast application provided shall be exposed to the Host through an XML AIT file (see clause 5.4 of ETSI TS 102 809 [7]), which is also stored on the auxiliary... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.4.4 Broadcast and CICAM application coordination | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.4.4.1 General | The present clause (12.4.4) provides the technical embodiment of the Application Coordination Framework. As described in clause 12.4.1, user preferences administered on the Host device, if set accordingly, shall override any of the assertions relating to application priority in the present clause (12.4.4). Clause 12.4.... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.4.4.2 Changing to a DVB service | After the change to a DVB Service has been completed and the corresponding TS is being received, the Host shall monitor the TS for broadcast application signalling, interpret the signalling provided for that DVB Service, and launch the broadcast application if and as appropriate. The Host is said to have determined tha... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.4.4.3 An application is running and has focus | If a CICAM AppMMI application is running then the Host shall not start a broadcast application except as part of the process for changing to a DVB Service as defined above. This implies that a broadcast application middleware would be prevented from obeying changes in application signalling, for example, if a new autos... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.4.4.4 Changing to the CICAM Virtual Channel | Clause 14.2.1 of the present document defines the use of Application MMI when entering the Virtual Channel. When the user chooses to start the Virtual Channel, the application identified in the requestStart() APDU shall have user focus and any running broadcast or CICAM application may lose focus or be terminated, depe... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.4.4.5 enter_menu | The Host sends the enter_menu() APDU to the CICAM as a result of the user choosing to enter the CICAM menu. If the CICAM responds to enter_menu() with a requestStart() APDU then the application identified in the requestStart() APDU coming from the CICAM shall have user focus and any running broadcast or CICAM applicati... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.4.4.6 Application termination | An application environment need not comply with requirements in CI Plus 1.3 [3] or ETSI TS 101 699 [2] for the Host to terminate a CICAM AppMMI application following a service change if all of the following apply: • the application environment supports the identification of applications; and • the application environme... |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.4.5 Application coordination scenarios | |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.4.5.1 General | Figures 22, 23 and 24 provide informative examples, in the form of annotated sequence diagrams, of three typical scenarios of operation of the Application Coordination Framework. |
640cdd88dcdf317f90107dbb72f1d840 | 103 205 | 12.4.5.2 Broadcast signalled application launch | Figure 22 depicts an example scenario of the launch of broadcast signalled applications. The operator provisions the CICAM with one or more applications. Applications are associated with an application domain. The mechanism by which the operator provisions these applications to the CICAM is out of the scope of the pres... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.