{"id":2412,"date":"2026-07-31T11:30:36","date_gmt":"2026-07-31T09:30:36","guid":{"rendered":"https:\/\/localdab.org\/?page_id=2412"},"modified":"2026-07-31T11:38:04","modified_gmt":"2026-07-31T09:38:04","slug":"dcp","status":"publish","type":"page","link":"https:\/\/localdab.org\/index.php\/glossary\/a-d\/dcp\/","title":{"rendered":"DCP"},"content":{"rendered":"\n

Distribution Communications Protocol<\/p>\n\n\n\n

The aim of the following text is to explain what EDI (Encapsulated DAB Interface) entails.
In fact, EDI is simply an application of the generic DCP\/TAG mechanism or DCP protocol.


In the text below, we frequently use the word \u2018packaging\u2019. The technical term for this is \u2018encapsulation\u2019.<\/p><\/blockquote><\/figure>\n\n\n\n

The Distribution and Communication Protocol (DCP)<\/strong> is a general-purpose protocol that describes how data is logically packaged and structured<\/strong>. DCP is not, in itself, tied to any specific application<\/strong> (it is application-independent). It merely defines the way in which data is organised, but does not specify exactly what that data should be.<\/p>\n\n\n\n

EDI (ETI Distribution Interface)<\/strong> then describes how DCP is used to transmit ETI information over IP networks<\/strong>. In other words, EDI uses DCP as a building block and specifies which TAGs (packaging boxes) are to be used and how they should be filled in.<\/p>\n\n\n\n

ETI was originally designed for stable serial connections between an ensemble multiplexer (MUX) and a DAB transmitter. However, this format is less suitable for transmission over IP networks.<\/p>\n\n\n\n

For this reason, the information from an ETI-LI frame is repackaged using the DCP protocol in accordance with the prescribed EDI rules.<\/p>\n\n\n\n

Instead of sending the entire ETI-LI frame as a single large data block, the information is split into several logical data blocks. Each block is encapsulated in a TAG (the proverbial box).<\/p>\n\n\n\n

For example, there is a TAG (box) called DETI<\/strong>, this box contains general information about the ETI-LI frame, such as the frame parameters and the synchronisation data TIST, TAI and UTCO (UTC Offset).<\/p>\n\n\n\n

In addition, there is a separate ESTn-TAG<\/strong> for each sub-channel of the multiplexer, where n<\/strong> represents the sub-channel number. Thus, EST0<\/strong> contains the data for sub-channel 0, EST1<\/strong> that for sub-channel 1, and so on.<\/p>\n\n\n\n

All TAG items (the small boxes) that together describe a single ETI-LI frame are then combined into a single larger package: the TAG package<\/strong>. This TAG package constitutes the complete description of a single ETI-LI frame.<\/p>\n\n\n\n

The TAG packet is then encapsulated in an Application Frame (AF)<\/strong> for transmission over the network. You can think of an AF as a large shipping box into which the entire TAG packet is placed. The AF layer does not recognise the meaning of the individual TAG items; its sole purpose is to ensure that the entire TAG packet can be transmitted securely as a single unit.<\/p>\n\n\n\n

\n

The AF (the large box) therefore does not contain the ETI frame itself, but rather the collection of TAGs (packaged boxes) which, taken together, represent all the information contained in that ETI frame.<\/strong><\/em><\/p>\n\n\n\n

It is important to note that the content of the ETI information does not change. Only the way in which this information is packaged for transmission over an IP network is different.<\/strong><\/em><\/p>\n<\/blockquote>\n\n\n\n

When the IP connection is less reliable, an additional layer of encapsulation can be added on top of the AF: PFT (Protection, Fragmentation and Transportation)<\/strong>. This layer can split the AF into smaller fragments and, optionally, add Forward Error Correction (FEC)<\/strong>, so that a limited number of lost IP packets can be reconstructed.<\/p>\n\n\n\n

Finally, all of this is transmitted over the network via the UDP\/IP protocol stack<\/strong>.<\/p>\n\n\n\n

By analogy with Russian babushkas (or matryoshkas), we would like to present the protocol stack as a series of nested boxes, viewed from above. In technical documentation, this is often depicted as a stack of layers, with the smallest box representing the top layer and the bottom box representing the lowest layer (layered model).<\/p>\n\n\n\n

In the model below, the physical layer (the lowest layer) is shown together with the link layer (Ethernet). Everything above the UDP box constitutes the application layers. The encapsulation carried out by DCP is found in the application sub-layers: TAGs<\/strong>, AF<\/strong> and the optional PFT<\/strong> layer. It is important to realise that each layer is encapsulated within the layer below it, even when this is depicted vertically (see technical documents).<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

Back<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Distribution Communications Protocol The aim of the following text is to explain what EDI (Encapsulated DAB Interface) entails.In fact, EDI is simply an application of the generic DCP\/TAG mechanism or DCP protocol. In the text below, we frequently use the word \u2018packaging\u2019. The technical term for this is \u2018encapsulation\u2019. The Distribution and Communication Protocol (DCP) […]<\/p>\n","protected":false},"author":3,"featured_media":0,"parent":1257,"menu_order":160,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-2412","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/localdab.org\/index.php\/wp-json\/wp\/v2\/pages\/2412","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=2412"}],"version-history":[{"count":1,"href":"https:\/\/localdab.org\/index.php\/wp-json\/wp\/v2\/pages\/2412\/revisions"}],"predecessor-version":[{"id":2414,"href":"https:\/\/localdab.org\/index.php\/wp-json\/wp\/v2\/pages\/2412\/revisions\/2414"}],"up":[{"embeddable":true,"href":"https:\/\/localdab.org\/index.php\/wp-json\/wp\/v2\/pages\/1257"}],"wp:attachment":[{"href":"https:\/\/localdab.org\/index.php\/wp-json\/wp\/v2\/media?parent=2412"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}