hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 5.2.2 ContentName | This mandatory MOT parameter uniquely identifies the object within the MOT carousel The ContentName parameter is used as specified in the MOT specification [2]. To permit receiver interoperability, the character set for the ContentName of Filecast objects shall be ISO Latin Alphabet No 1, see TS 101 756 [3]. The permit... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 5.2.3 CompressionType | The CompressionType parameter is used as specified in the MOT specification [2]. ETSI ETSI TS 103 177 V1.1.1 (2013-08) 11 |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 5.2.4 CAInfo | This parameter is used if conditional access on the MOT level is applied to the MOT data. The CAInfo parameter is used as specified in the MOT specification [2]. If this parameter is present a non CA-capable device shall discard this MOT object. |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 5.2.5 AvailabilityStart | This is the date and time from which the media file is transmitted on this Filecast channel. • If the AvailabilityStart has a value in the future then this parameter indicates that the media file (and updates to the media file in the case of dynamic content) is not part of the current carousel. It informs the receiver ... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 5.2.6 PresentationPriority | The use of this Filecast parameter for each MOT object is optional. This MOT parameter carries a presentation priority value for this MOT object. This parameter enables the broadcaster to define the presentation ordering of multiple items. If this parameter is specified then where multiple items are displayed they shal... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 5.2.7 MemberOf | The use of this Filecast parameter for each MOT object is optional. This MOT parameter carries a shortID linking this MOT object to the corresponding group element of the group information in an optionally transmitted EPG service. The value of the parameter field is coded using the same format as the Binary EPG shortCR... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 5.2.8 ClickThroughURL | The use of this Filecast parameter for each MOT object is optional. This describes a URL that may be used by a device to respond to a user action (e.g. tapping the screen while the content is presented) to show a linked X(HTML) resource within a capable application on the device, e.g. an integrated web browser. The URL... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 5.2.9 AlternativeLocationURL | The use of this Filecast parameter for each MOT object is optional . This describes a URL that may be used by the device to acquire the content using a HTTP request over an IP connection. This may be specified on a MOT object that has slide content within its body data, indicating an alternative means of acquisition. I... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 5.2.10 Location | The use of this Filecast parameter for each MOT object is optional. This parameter enables location-based services to be supported. The location parameter is encoded as a latitude/longitude value pair. A latitude value is specified as a 24-bit 2's complement integer number, in 1/92 000th degrees between -90,0 degrees (... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 5.2.11 ContentDescription | The use of this Filecast parameter for each MOT object is mandatory. This MOT parameter contains a description for the media file. It has a maximum length of 128 characters or a maximum of 512 bytes. The character set used shall be ISO/IEC 10646 [7] (UTF-8 encoding). The ContentDescription is presented to the user for ... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 5.2.12 ContentCategory | The use of this Filecast parameter for each MOT object is optional. This MOT parameter contains information about the category or categories for this media file. It has a maximum length of 64 characters or a maximum of 256 bytes. The character set used shall be ISO/IEC 10646 [7] (UTF-8 encoding). The ContentCategory is... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 5.2.13 ParentService | If the media file contains content that is related to one or more audio services, then this parameter indicates the parent audio service. If the media file does not have a parent service signalled in its MOT parameters the device shall not assume any relationship of the content file with a particular service. It uses t... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 5.2.14 MOT caching parameters | It is optional but recommended for service providers and receivers to support the MOT parameters Expiration and DefaultExpiration in the MOT Directory as detailed in the MOT specification [2]. |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 5.3 Recommended signalling for updated and dynamic content | When the content of an item changes (i.e. the MOT body object is updated, but the ContentName is not changed), the UniqueBodyVersion parameter should be used, as detailed in the MOT specification [2]. Where the previous version of the item is still valid until the new item (MOT body) is fully received, the MOT paramete... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 5.4 Rebroadcasting media files | Where the content within a media file is unchanged, and that file is re-broadcast at a later time, the second and subsequent broadcasts should be treated as a retransmission. Consequently the header information, body content and SegmentSize of the objects should not be changed, and the TransportId should remain the sam... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 5.5 Supported content types | Filecast-enabled receivers are only required to support the content types specified below. |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 5.5.1 Audio | The supported audio compression format is MPEG-4 High Efficiency Advanced Audio Coding v2 (HE AAC v2) profile (1 024 frame size) carried in a MP4 container file. The file extension in the MOT parameter ContentName shall be ".m4a". The ContentType and SubType parameters shall be signalled as MPEG4 Audio, as indicated in... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 5.5.2 Text | The supported document types are HTML and PDF. The file extension in the MOT parameter ContentName shall be ".html" and ".pdf" respectively. It is permitted for hmtl files to contain hyperlinks (URLs) which can be activated if the receiver has the ability to connect to the internet. The ContentType and SubType paramete... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 5.5.3 Video | The supported audio compression format is MPEG-4 profile carried in a MP4 container file. The file extension in the MOT parameter ContentName shall be ".mp4". The ContentType and SubType parameters shall be signalled as MPEG4 Video, as indicated in the DAB Registered Table specification (TS 101 756 [3]). |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 6 Signalling | |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 6.1 Application type, FIG0/13 | The use of this application shall be indicated by the use of FIG0/13 with the UserApplicationType signalled as Filecasting as defined in TS 101 756 [3]. |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 6.2 Secondary component signalling | If the Filecast channel contains media files that are linked to an audio service on the same multiplex and the Filecast channel is not transported in the PAD capacity of that audio service, then the Filecast channel will be signalled as a secondary service component of that audio service. ETSI ETSI TS 103 177 V1.1.1 (2... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 6.3 Time and date, FIG0/9 and FIG 0/10 | The provision of a correctly broadcast reference time using FIG0/10 and local time offset using FIG0/9 is a mandatory requirement of this User Application. For further details on these parameters, see EN 300 401 [1]. |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 7 Receiver functionality | |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 7.1 General functionality | A receiver: • Shall be able to decode packet mode sub-channels including additional FEC. • Shall be able to decode a compressed MOT Directory. • Shall, as a minimum, support the decoding of the audio content type, see clause 5.5.1. • Shall be able to display all the characters from the extended RDS character set, see I... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 7.2 Presentation of the content to the user | It is recommended that a receiver: • Should provide a simple means for listing media files that are linked (using the MOT parameter ParentService) to the audio service they are currently listening to. • Should provide details on the status of the download of a particular media file, e.g. "xx% complete" and "available".... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 7.3 Downloading content | If the receiver is battery-powered, then it is recommended that a user is given the option of not downloading media files in the background whilst the unit is in standby. If a receiver has a scheduling clash, and is unable to decode all of the available content, it should first prioritize the downloading of any content... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 7.4 File management | Filecast uses the MOT Directory to announce the content available to the user, and the Filecast receiver application will have various means to filter the content and transfer relevant media files for later use by the user. The receiver keeps all objects referred to in the most recently received MOT Directory (this all... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 7.5 URL Handling | A ClickThroughURL MOT parameter defines a web page that is shown on the device as a result of user prompting (e.g. clicking a button or tapping the screen) when the content is being displayed. This web page will then launch in a web browser on the device and be displayed to the user. An AlternateLocationURL MOT paramet... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 7.5.1 AlternativeLocationURL | When acquiring content using the Alternative Location URL, devices are recommended to include the following HTTP headers in their request, indicating the display dimensions and resolution density of the device, to assist in returning a more appropriate resource for that device. Table 3 Header Name Description Mandatory... |
e16e1132c3a9a95bab520e549a2a32e6 | 103 177 | 7.5.2 ClickThroughURL | A device without the means to display X(HTML) content shall ignore a ClickThroughURL and not indicate to the user that one is available, nor perform any actions on user interaction. If the device does have the means to display X(HTML) content, for example by using a web browser, then it should switch to this content on... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 1 Scope | The present document of DVB-Simulcrypt addresses the requirements for interoperability between two or more conditional access systems at a head-end. It specifies the system architecture, timing relationships, messaging structures, extended interoperability and control. The components within the system architecture repr... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 1.1 Common scrambling algorithm | The DVB-Simulcrypt group has looked at issues relating to the concepts of the common scrambling algorithm, within the DVB-Simulcrypt environment. The DVB-Simulcrypt system is based on the concept of a shared scrambling and descrambling method. The group has looked at the possible constraints, which the DVB-Simulcrypt a... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 1.2 Language | The word "shall" is used in a normative statement that can be verified and is mandatory. The word "should" is used in the context of a recommendation or a statement that cannot be verified or is not mandatory (it may be optional). |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI EN 300 468: "Digital Video Broadcasting (DVB); S... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] ETSI TR 101 154: "Digital Video Broadcasting (DV... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 3 Definitions and abbreviations | |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: access criteria: CA system specific information needed by the ECMG to build an ECM Access Criteria Generator (ACG): See clause 4.2.16. broadcaster (service provider): organization which assembles a sequence of events or services to be ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AC Access Criteria ACG Access Criteria Generator AES Advanced Encryption Standard ASI Asynchronous Serial Interface ASN.1 Abstract Syntax Notation One bslbf bit string, left bit first C(P)SIG Custom PSI/SI Generator CA Conditional Access CAS C... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4 Architecture | |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.1 System architecture | Figure 1 shows the logical relationships between the components and which component-to-component interfaces are defined in the present document. Other components exist in a head-end, which are not illustrated in figure 1 (for example: SMS or Subscriber Management System, etc.). ETSI ETSI TS 103 197 V1.5.1 (2008-10) 20 ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.1.1 Host Head-end components | Host head-end components are those that will need to exist before Simulcrypt CA components can be introduced into a DVB-Simulcrypt head-end. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.1.2 Simulcrypt CA components | Simulcrypt CA components are typically those, which are brought by a new CA provider to introduce his CA into a DVB-Simulcrypt head-end. NOTE: The EMMGs, PDGs and Custom SI generators are not necessarily required in a DVB-Simulcrypt system. ETSI ETSI TS 103 197 V1.5.1 (2008-10) 21 |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.1.3 Simulcrypt Integrated Management Framework (SIMF) | The components of multiple Conditional Access Systems (CASs) involved in a Simulcrypt architecture can be supported by a network management function existing in a head-end. For ECMG, EMMG, PDG, C(P)SIG and (P)SIG, a Simulcrypt Integrated Management Framework (SIMF) is defined to address the requirements for interoperab... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.1.4 Multiplexer Redundancy | The Simulcrypt Architecture provides specific support for head-end implementations in which the multiplexer components are redundantly configured. An optional protocol is specified that allows Simulcrypt Components (SIMCOMPs) to discover the multiplexer redundancy topology and to request the current multiplexer connect... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.2 Description of Components | |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.2.1 Event Information Scheduler (EIS) | In the DVB-Simulcrypt system architecture diagram (see clause 4.1), the EIS is the functional unit in charge of holding the entire schedule information, all the configurations and CA specific information required for the complete system. It is the overall database store for the whole head-end system. For instance, it i... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.2.2 Simulcrypt Synchronizer (SCS) | The role of the Simulcrypt Synchronizer is to: • establish TCP connections with ECMGs and setup one channel per connection; • setup streams within channels as needed and allocate ECM_stream_id values; • get the control words from the CWG; • supply the CWs to the relevant ECMGs on the relevant streams, as well as any CA... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.2.3 ECM Generator (ECMG) | The ECMG shall receive CWs in a CW provision message as well as access criteria and shall reply with an ECM or an error message. The ECMG does not support ECM repetition. ETSI ETSI TS 103 197 V1.5.1 (2008-10) 22 |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.2.4 EMM Generator (EMMG) | This component, supplied by the CA provider shall interface over a DVB-Simulcrypt specified interface to the MUX. The EMMG initiates connections to the MUX. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.2.5 Private Data Generator (PDG) | This component is shown in the DVB-Simulcrypt System Architecture diagram to highlight the fact that the EMMG to MUX interface can be used for EMMs and other CA related private data. The PDG initiates connections to the MUX. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.2.6 Service Information Generator (SIG) | This component is responsible for generating the SI for the system in the form of DVB SI tables (see EN 300 468 [1]). The SI Generator takes its primary data from the EIS and supplementary data from the Custom SI Generators supplied by the CA vendor. The interface between the EIS and the SIG is not specified in the pre... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.2.7 Program Specific Information Generator (PSIG) | This component is responsible for generating the PSI for the system in the form of MPEG-2 PSI tables (see ISO/IEC 13818-1 [3]). The PSI Generator takes its primary data from the MUXCONFIG and supplementary data from the Custom PSI Generators supplied by the CA vendor. The interface between the MUXCONFIG and the PSI Gen... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.2.8 Custom Service Information Generator (CSIG) | This component is responsible for generating CAS-specific private data for insertion in selected DVB SI tables. It interfaces to the SI Generator. Each CAS may include one or more CSIGs. In the context of private SI data generation, the generic term C(P)SIG refers to a head-end process that serves as a CSIG or a combin... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.2.9 Custom Program Specific Information Generator (CPSIG) | This component is responsible for generating CAS-specific private data for insertion in selected MPEG-2 PSI tables and interfaces to the PSI Generator. Each CAS may include one or more CPSIGs. In the context of private PSI data generation the generic term C(P)SIG refers to a head-end process that serves as a CPSIG or a... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.2.10 Multiplexer Configuration (MUXCONFIG) | This component is responsible for configuring the MUX and providing a link to the PSI generator for PSI construction and play-out. The interfaces MUXCONFIG ⇔ MUX and MUXCONFIG ⇔ PSIG are not defined by the present document. ETSI ETSI TS 103 197 V1.5.1 (2008-10) 23 |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.2.11 Multiplexer (MUX) | The role of this head-end component is to perform time multiplexing of input data, and to output an MPEG-2 transport stream. The input data can be transport packets, MPEG sections or raw data. The exact functionality of a MUX is implementer specific. For the purpose of the present document, the MUX shall be able to com... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.2.12 Scrambler (SCR) | This component is responsible for scrambling data in the MPEG2 Transport Stream. The exact functionality of the Scrambler is implementer specific. For the purpose of the present document, the Scrambler shall be able to receive Control Words from the SCS. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.2.13 Control Word Generator (CWG) | This component is responsible for generating control words used in scrambler initialization stream. The exact functionality of the Scrambler is implementer specific. For the purpose of the present document, the Control Word Generator shall be able to provide the SCS with control words. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.2.14 Network Management System (NMS) | This component is responsible for monitoring and control of SIMF agents. The exact nature of this function depends on the type of host component the agent is situated in, i.e. ECMG, EMMG, PDG, etc., and the type of management function the NMS component is performing, i.e. fault, configuration, accounting, performance a... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.2.15 SIMF agent | This component supports network management protocol transactions on the Simulcrypt Management Information Base (SMIB), which it implements. It instruments the SMIB with monitoring and control functionality of the host component, i.e. ECMG, EMMG, PDG, etc. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.2.16 Access Criteria Generator (ACG) | This component, supplied by the CA provider is responsible for generating CAS related information, e.g. access criteria, related to each event managed by the EIS when this event involves its associated CAS. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.3 Description of interfaces | 4.3.1 ECMG ⇔ SCS The interface allowing a CAS to provide a SCS with ECMs under the control of this SCS. This interface is mandatory and shall be implemented as described in clause 5. 4.3.2 EMMG ⇔ MUX The interface allowing a CAS to provide a MUX with EMM under the control of the CAS. This interface is mandatory and sha... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.3.11 SCR onward | Proprietary, not defined by the present document. 4.3.12 SCS ⇔ MUX Proprietary, not defined by the present document. 4.3.13 SCS ⇔ SCR Proprietary, not defined by the present document. 4.3.14 SCS ⇔ CWG Proprietary, not defined by the present document. 4.3.15 EIS ⇔ SCS The interface providing the SCS with the Scrambling ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.3.19 Mandatory or optional characteristics of Simulcrypt interfaces | Clauses 4.3.1 to 4.3.18 give the global mandatory or optional characteristic of each interface described in the present document. Table 1a sums up these characteristics. Table 1a: Mandatory or optional characteristics of the Simulcrypt interfaces Interfaces Global Characteristic Particular points See clauses ECMG ⇔ SCS... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.4 Protocol types | |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.4.1 Connection-oriented TLV protocols | For the connection-oriented protocols defined in the present document, the messages shall have the following generic structure. Table 1b: Message-type values for command/response-based protocols generic_message { protocol_version 1 byte message_type 2 bytes message_length 2 bytes for (i=0; i < n; i++) { parameter_type ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.4.2 Connection oriented XML protocols | All messages exchanged on XML-based Simulcrypt protocols share a common general format as detailed in this clause. The messages are encoded using XML over a TCP connection. All messages share a common structure that wraps the data for the specific message being sent. Each message follows a standard format starting with... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 4.4.3 SIMF-based protocols | All Simulcrypt CAS/Head-end interface specifications such as ECMG ⇔ SCS, EMMG ⇔ MUX, PDG ⇔ MUX, C(P)SIG ⇔ (P)SIG, (P)SIG MUX and EIS SCS are based on a connection-oriented communications paradigm (i.e. channel/streams). Alternatively, some of these interfaces can be implemented using a transaction-based communications ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 5.1 Interface principles | |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 5.1.1 Channel and Stream specific messages | This interface shall carry the following channel messages defined further in clause 5.4: • Channel_setup. • Channel_test. • Channel_status. • Channel_close. • Channel_error. and the following stream messages defined further in clause 5.5: • Stream_setup. • Stream_test. • Stream_status. ETSI ETSI TS 103 197 V1.5.1 (2008... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 5.1.2 Channel establishment | There is always one (and only one) channel per TCP connection. Once the TCP connection is established, the SCS sends a channel_setup message to the ECMG. In case of success the ECMG replies by sending back a channel_status message. In case of a rejection or a failure during channel setup the ECMG replies with a channel... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 5.1.3 Stream establishment | The SCS sends a stream_setup message to the ECMG. In case of success the ECMG replies by sending back a stream_status message. In case of a rejection or a failure the ECMG replies with a stream_error message. Once the connection, channel and stream have been correctly established the ECM will be transferred. It can be ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 5.1.4 Stream closure | Stream closure is always initiated by the SCS. This can occur when an ECM stream is no longer needed or in the case of an error. This is done by means of a stream_close_request message. A stream_close_response message indicates the stream has been closed. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 5.1.5 Channel closure | Channel closure can occur when the channel is no longer needed or in case of error (detected by SCS or reported by ECMG). This is done by means of a channel_close message sent by the SCS. Subsequently, the connection shall be closed by both sides. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 5.1.6 Channel/Stream testing and status | At any moment either component can send a channel_test/stream_test message to check the integrity of a channel/stream. In response to this message the receiving component shall reply with either a channel/stream status message or a channel/stream error message. ETSI ETSI TS 103 197 V1.5.1 (2008-10) 31 |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 5.1.7 Unexpected communication loss | Both SCS and ECMG shall be able to handle an unexpected communication loss (either on the connection, channel or stream level). Each component, when suspecting a possible communication loss (e.g. a 10 second silent period), should check the communication status by sending a test message and expecting to receive a statu... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 5.1.8 Handling data inconsistencies | If the ECMG detects an inconsistency it shall send an error message to the SCS. If the SCS receives such a message or detects an inconsistency it may close the connection. The SCS (as the client) will then (re-)establish the connection, channel and (if applicable) streams. The occurrence of a user defined or unknown pa... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 5.2 Parameter_type values | Table 5: ECMG protocol parameter_type values Parameter_type Value Parameter type Type/units Length (bytes) 0x0000 DVB Reserved - - 0x0001 Super_CAS_id uimsbf 4 0x0002 section_TSpkt_flag uimsbf 1 0x0003 delay_start tcimsbf/ms 2 0x0004 delay_stop tcimsbf/ms 2 0x0005 transition_delay_start tcimsbf/ms 2 0x0006 transition_d... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 5.3 Parameter semantics | AC_delay_start: this parameter shall be used in place of the delay start parameter for the first Crypto period following a change in AC. AC_delay_stop: this parameter shall be used in place of the delay stop parameter for the last Crypto period preceding a change in AC. access_criteria: this parameter contains CA syste... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 5.4 Channel specific Messages | 5.4.1 Channel_setup message: ECMG ⇐ SCS Parameter Number of instances in message ECM_channel_id 1 Super_CAS_id 1 The channel_setup message (message_type = 0x0001) is sent by the SCS to setup a channel once the TCP connection has been established, as described in clause 5.1.2. It shall contain the Super_CAS_id parameter... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 5.5 Stream specific messages | 5.5.1 Stream_setup message: ECMG ⇐ SCS Parameter Number of instances in message ECM_channel_id 1 ECM_stream_id 1 ECM_id 1 nominal_CP_duration 1 The stream_setup message (message type = 0x0101) is sent by the SCS to setup a stream once the channel has been established, as described in clause 5.1.3. 5.5.2 Stream_test mes... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 5.6 Error status | NOTE: TCP connection level errors are beyond the scope of the present document. Only channel, stream and application level errors are dealt with. These errors occur during the lifetime of a TCP connection. There are two different error messages on these interfaces. The channel_error message for channel wide errors and ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 6.2 TCP-based protocol | |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 6.2.1 Interface principles | |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 6.2.1.1 Channel and Stream specific messages | The interface shall carry the following channel messages defined further in clause 6.2.4: • Channel_setup • Channel_test • Channel_status • Channel_close • Channel_error and the following stream messages defined further in clause 6.2.5: • Stream_setup • Stream_test • Stream_status • Stream_close_request • Stream_close_... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 6.2.1.2 Channel establishment | The EMMG/PDG sends a channel_setup message to the MUX. In case of success the MUX replies by sending back a channel_status message. In case of a rejection or a failure during channel setup the MUX replies with a channel_error message. This means that the channel has not been opened by the MUX and the EMMG/PDG shall clo... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 6.2.1.3 Stream establishment | The EMMG/PDG sends a stream_setup message to the MUX. In case of success the MUX replies by sending back a stream_status message. In case of a rejection or a failure the MUX replies with a stream_error message. When a new EMM/private data stream is created in a transport stream, a new data_id shall be assigned to it by... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 6.2.1.4 Bandwidth allocation | The interface allows bandwidth negotiation between the EMMG/PDG and the MUX. This is not mandatory. During stream setup the EMMG/PDG will request the optimal bandwidth for that stream. The MUX will then respond with the bandwidth that has been allocated for that stream. The EMMG/PDG can, at a later time, request an adj... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 6.2.1.5 Stream closure | Stream closure is always initiated by the EMMG/PDG. This can occur when an EMM/private data stream is no longer needed. This is done by means of a stream_close_request message. A stream_close_response message indicates the stream has been closed. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 6.2.1.6 Channel closure | Channel closure can occur when the channel is no longer needed or in case of error (detected by EMMG/PDG or reported by MUX). This is done by means of a channel_close message sent by the EMMG/PDG. Subsequently, the connection shall be closed by both sides. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 6.2.1.7 Channel/Stream testing and status | At any moment either component can send a channel_test/stream_test message to check the integrity of a channel/stream. In response to this message the receiving component shall reply with either a channel/stream status message or a channel/stream error message. |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 6.2.1.8 Unexpected connection loss | Both EMMG/PDG and MUX shall be able to handle an unexpected communication loss (either on the connection, channel or stream level). Each component, when suspecting a possible communication loss (e.g. a 10 second silent period), should check the communication status by sending a test message and expecting to receive a s... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 6.2.1.9 Handling data inconsistencies | If the MUX detects an inconsistency it shall send an error message to the EMMG/PDG. If the EMMG/PDG receives such a message or detects an inconsistency it should close the connection. The EMMG/PDG (as the client) will then (re-) establish the connection, channel and (if applicable) streams. The occurrence of a user def... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 6.2.2 Parameter Type Values | Table 7: EMMG/PDG protocol parameter_type values Parameter_type value Parameter type Type/Units Length (bytes) 0x0000 DVB Reserved - - 0x0001 client_id uimsbf 4 0x0002 section_TSpkt_flag uimsbf 1 0x0003 data_channel_id uimsbf 2 0x0004 data_stream_id uimsbf 2 0x0005 datagram user defined variable 0x0006 bandwidth uimsbf... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 6.2.3 Parameter semantics | bandwidth: this parameter is used in stream_BW_request and stream_BW_allocation messages to indicate the requested bit rate or the allocated bit rate respectively. It is the responsibility of the EMMG/PDG to maintain the bit rate generated within the limits specified by the MUX when the bandwidth allocation method is u... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 6.2.4 Channel specific messages | 6.2.4.1 Channel_setup message: EMMG/PDG ⇒ MUX Parameter Number of instances in message client_id 1 data_channel_id 1 section_TSpkt_flag 1 The channel_setup message (message_type = 0x0011) is sent by the EMMG/PDG to the MUX to setup a channel once the TCP connection has been established, as described in clause 6.2.1.2. ... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 6.2.5 Stream specific messages | 6.2.5.1 Stream_setup message: EMMG/PDG ⇒ MUX Parameter Number of instances in message client_id 1 data_channel_id 1 data_stream_id 1 data_id 1 data_type 1 The stream_setup message (message_type = 0x0111) is sent by the EMMG/PDG to setup a stream once the channel has been established, as described in clause 6.2.1.3. 6.2... |
af1c0d99efa57e65117cf22743ed5e19 | 103 197 | 6.2.6 Error status | NOTE: TCP connection level errors are beyond the scope of the present document. Only channel, stream and application level errors are dealt with. These errors occur during the lifetime of a TCP connection. There are two different error messages on that interface. The channel_error message for channel wide errors, and t... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.