{"id":820,"date":"2022-09-25T08:13:39","date_gmt":"2022-09-25T06:13:39","guid":{"rendered":"https:\/\/localdab.org\/?page_id=820"},"modified":"2022-09-30T16:03:23","modified_gmt":"2022-09-30T14:03:23","slug":"eti-and-edi","status":"publish","type":"page","link":"https:\/\/localdab.org\/index.php\/dab-in-more-detail\/eti-and-edi\/","title":{"rendered":"ETI and EDI"},"content":{"rendered":"\n<h2 class=\"has-large-font-size wp-block-heading\">The interface between DAB-MUX and DAB-Transmitter?<\/h2>\n\n\n\n<p><em>Ensemble Transport Interface see ETSI ETS 300 799 Output stream of the DAB-multiplexer to the DAB-transmitter.<\/em><\/p>\n\n\n\n<p><img loading=\"lazy\" decoding=\"async\" width=\"1500\" height=\"517\" class=\"wp-image-845\" style=\"width: 1500px;\" src=\"https:\/\/localdab.org\/wp-content\/uploads\/2022\/09\/ETI-interface_general.jpg\" alt=\"\" srcset=\"https:\/\/localdab.org\/wp-content\/uploads\/2022\/09\/ETI-interface_general.jpg 1272w, https:\/\/localdab.org\/wp-content\/uploads\/2022\/09\/ETI-interface_general-300x103.jpg 300w, https:\/\/localdab.org\/wp-content\/uploads\/2022\/09\/ETI-interface_general-1024x353.jpg 1024w, https:\/\/localdab.org\/wp-content\/uploads\/2022\/09\/ETI-interface_general-768x264.jpg 768w\" sizes=\"auto, (max-width: 1500px) 100vw, 1500px\" \/><\/p>\n\n\n\n<p><\/p>\n\n\n\n<p>We noticed that a lot of misunderstandings exists between these two mnemonics used in DAB\/DAB+ literature. Both <strong>ETI<\/strong> and <strong>EDI<\/strong> are used to interface the MUX output to the transmitter input.<\/p>\n\n\n\n<p><strong>ETI<\/strong> (<strong>E<\/strong>nsemble <strong>T<\/strong>ransport <strong>I<\/strong>nterface) is to be seen as a general name for the interface between the DAB-MUX and the DAB-transmitter. More specific we could talk about the <strong>ETI-LI<\/strong> (LI = <strong>Logical<\/strong> <strong>Frame<\/strong>). This frame is the basic ETI-frame which we need to be transported between the two devices DAB-MUX and DAB-Transmitter.<\/p>\n\n\n\n<p>In addition we will see different standard and non-standard ways to transport this logical frame. These more specific interfaces will be defined by the extension following te mnemonic such as ETI-NI, ETI-NA and ETI-EDI. <\/p>\n\n\n\n<p><strong>EDI<\/strong> is only one of the available <strong>transport methods<\/strong> under which <strong>ETI<\/strong> can be transported. Most of the time the mnemonic is used on his own without the prefix ETI.<\/p>\n\n\n\n<p>In fact we can say that both are ETI-signals although EDI is the <strong>envelope<\/strong> in which ETI is transported. Any transport of ETI over IP-networks will be called an EDI- interface because ETI will always be transported in an EDI-envelope when transported over IP-networks.<\/p>\n\n\n\n<p>When we put data into a specific envelope we speak about <strong>encapsulation<\/strong>. This leads us finally to the name <strong>EDI<\/strong> which means <strong>E<\/strong>ncapsulation of <strong>D<\/strong>AB <strong>I<\/strong>nterfaces. Later we will see that the EDI-envelope will also be used for the STI-interface.<\/p>\n\n\n\n<p>Further ETI can also be transported over other types of networks. Momentary two versions <strong>ETI-NI <\/strong>(Network Independent) and <strong>ETI-NA<\/strong> (Network Adapted) interfaces exist. We will look into this in the future.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<blockquote class=\"wp-block-quote has-medium-font-size is-layout-flow wp-block-quote-is-layout-flow\"><p><\/p><p><strong><em>Be aware that ETI is a mnemonic usually used in a broad range of meanings<\/em>.<\/strong><br><br><em style=\"\"><b>It does not say which <\/b><\/em><strong><em>underlying protocol will be used to transport it nor will it say something about the specifications of the physical interface (such as electrical and physical (connector) characteristics)!<\/em><\/strong><\/p><p><strong><em>In whatever format the ETI-information is transported it is important to know that the information need to be received every <span style=\"text-decoration: underline;\">24<\/span> milliseconds by the transmitter! <\/em><\/strong><\/p><p><\/p><\/blockquote>\n\n\n\n<p>Conversion from from ETI-signals to (ETI-)EDI and vice versa is possible with commercial available equipment and ODR-software. <\/p>\n\n\n\n<p><a href=\"https:\/\/localdab.org\/index.php\/dab-in-more-detail\/\" data-type=\"page\" data-id=\"30\">Back<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>The interface between DAB-MUX and DAB-Transmitter? Ensemble Transport Interface see ETSI ETS 300 799 Output stream of the DAB-multiplexer to the DAB-transmitter. We noticed that a lot of misunderstandings exists between these two mnemonics used in DAB\/DAB+ literature. Both ETI and EDI are used to interface the MUX output to the transmitter input. ETI (Ensemble [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"parent":30,"menu_order":100,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-820","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/localdab.org\/index.php\/wp-json\/wp\/v2\/pages\/820","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/localdab.org\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/localdab.org\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/localdab.org\/index.php\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/localdab.org\/index.php\/wp-json\/wp\/v2\/comments?post=820"}],"version-history":[{"count":12,"href":"https:\/\/localdab.org\/index.php\/wp-json\/wp\/v2\/pages\/820\/revisions"}],"predecessor-version":[{"id":1083,"href":"https:\/\/localdab.org\/index.php\/wp-json\/wp\/v2\/pages\/820\/revisions\/1083"}],"up":[{"embeddable":true,"href":"https:\/\/localdab.org\/index.php\/wp-json\/wp\/v2\/pages\/30"}],"wp:attachment":[{"href":"https:\/\/localdab.org\/index.php\/wp-json\/wp\/v2\/media?parent=820"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}