Coding device and method for radio program and multimedia service in television broadcasting

Abstract

Figure 1 shows a decoding device according to an embodiment. The apparatus comprises an interface (110) for receiving a plurality of ATSC link layer protocol packets, each packet comprising a packet header and a packet load encapsulating digital content. In addition, the apparatus comprises a decoding unit (120). In a first embodiment, digital content encapsulated within a packet load of one or more of the plurality of ATSC link layer protocol packets includes digital broadcast content, and / or distribution with communication protocol packets or portions thereof, and / or unified voice and audio encoded content or extended high-efficiency advanced audio encoded content, and / or data packet load of one or more of the plurality of ATSC link layer protocol packets, and / or data packet load of one or more of the plurality of ATSC link layer protocol packets, and / or data packet load of one or more of the plurality of ATSC link layer protocol packets, and / or data packet load of one or more of the plurality of ATSC link layer protocol packets. And / or the Jurnaline content. The decoding unit (120) is configured to decode a data packet load of each of at least one of the one or more ATSC link layer protocol data packets to obtain digital content of the one of the at least one ATSC link layer protocol data packets.

Description

[0001] manual Technical Field

[0002] The present invention relates to the coding of radio programs and multimedia services in television broadcasting, and in particular to the integration of distribution and communication protocols into ATSC, and to the transmission of xHE-AAC and Journalin in ATSC for audio and multimedia services. Background Art

[0003] The ATSC standard is a set of digital television transmission standards provided by the Advanced Television Systems Committee (ATSC). For detailed information on the data link layer protocol used by ATSC, see the relevant standard [1]: A / 330:2022-03, "Link-Layer Protocol", published on March 31, 2022. The ATSC Link-Layer Protocol (ALP) supports the encapsulation of IP packets.

[0004] However, ATSC does not provide native support for transmitting over-the-air programming.

[0005] To address the problem that ATSC does not natively support the transmission of radio programs, broadcasters can transmit audio-only television programs. However, this method is inefficient. In addition, the mature audio codec xHE-AAC (extended High Efficiency Advanced Audio Coding) / USAC (Unified Speech and Audio Coding) designed and optimized for digital radio broadcast cannot be used with this method. In addition, multimedia applications such as Journaline (a text messaging service) cannot be used with this method. Journaline (also known as the "news service Journaline") is described in

[10] .

[0006] Digital Radio Mondiale (DRM) is a globally deployed radio broadcasting standard that provides full-featured digital broadcasting services in a highly efficient coding manner, while supporting advanced text and other data services to fully utilize available channel resources. In regions where DRM is adopted, broadcasters have a strong desire to create and transmit the same Multiplex Distribution Interface (MDI) stream over both the radio and television spectrum, effectively reaching mobile and handheld devices and ensuring a consistent digital broadcasting experience for consumers.

[0007] DRM allows the transmission of multimedia data at very low data rates by adopting xHE-AAC (Extended High-Efficiency Advanced Audio Coding) / USAC (Unified Speech and Audio Coding) and Journaline technologies.

[0008] The specific technology used by DRM is the Distribution and Communications Protocol (DCP), see [3]: ETSI: TS 102 821, Digital Radio for All (DRM); Distribution and Communications Protocol

[0009] (DCP), V1.4.1 (2012-10), European Telecommunications Standards Institute, Vallaud-Sophia-Antipolis, France, October 2012.

[0010] However, the prior art does not provide the concept of transmitting DRM over ATSC.

[0011] Broadcasters already have the tools, equipment, knowledge and experience to generate DRM streams.

[0012] As ATSC gains traction and is expected to be adopted in more countries, there is a high expectation that ATSC will be able to support full-featured digital broadcasting services in addition to carrying existing TV audio services. Summary of the Invention

[0013] The object of the present invention is to provide an improved scheme for encoding broadcast programs and multimedia services in television broadcasting. This object of the present invention is achieved by the subject matter of the independent claims.

[0014] According to an embodiment, a decoding device is provided. The device includes: an interface for receiving a plurality of ATSC link layer protocol data packets, each of the plurality of ATSC link layer protocol data packets including a data packet header and a data packet payload encapsulating digital content. In addition, the device also includes a decoding unit. The digital content encapsulated in the data packet payload of one or more ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets includes: digital broadcast content, and / or distribution and communication protocol data packets or parts thereof, and / or unified voice and audio coding content or extended high-efficiency advanced audio coding content, and / or Journaline content. The decoding unit is configured to decode the data packet payload of each of at least one ATSC link layer protocol data packet in the one or more ATSC link layer protocol data packets to obtain the digital content of the one ATSC link layer protocol data packet in the at least one ATSC link layer protocol data packet.

[0015] In addition, according to another embodiment, a decoding device is provided. The device includes: an interface for receiving multiple ATSC link layer protocol data packets, each of the multiple ATSC link layer protocol data packets including a data packet header and a data packet payload encapsulating digital content, wherein one or more of the multiple ATSC link layer protocol data packets include the content of one or more services transmitted by ATSC. In addition, the device also includes a decoding unit, wherein the decoding unit is configured to decode the data packet payload of each of at least one ATSC link layer protocol data packet in the multiple ATSC link layer protocol data packets to obtain the digital content of the one ATSC link layer protocol data packet in the at least one ATSC link layer protocol data packet. One or more other ATSC link layer protocol data packets in the multiple ATSC link layer protocol data packets include one or more fragments of a service link mapping table. The one or more fragments of the service link mapping table indicate one or more services transmitted by ATSC. The decoding unit is configured to identify an ATSC link layer protocol data packet including the content of one of the one or more services by analyzing the one or more fragments of the service link mapping table.

[0016] In addition, according to another embodiment, a decoding device is provided. The device includes an interface for receiving a plurality of ATSC link layer protocol data packets, each of the plurality of ATSC link layer protocol data packets including a data packet header and a data packet payload encapsulating digital content, wherein one or more of the plurality of ATSC link layer protocol data packets include content of one or more services transmitted by ATSC. Furthermore, the device also includes a decoding unit, wherein the decoding unit is configured to decode the data packet payload of each of at least one ATSC link layer protocol data packet in the plurality of ATSC link layer protocol data packets to obtain the digital content of the one ATSC link layer protocol data packet in the at least one ATSC link layer protocol data packet. One or more of the plurality of ATSC link layer protocol data packets include one or more fragments of a service packet link mapping table, wherein the one or more fragments of the service packet link mapping table indicate one or more packets of a plurality of services transmitted by ATSC. The device includes an output interface for providing an output based on at least one of the one or more data packets, wherein the output depends on at least one of the plurality of services.

[0017] In addition, according to another embodiment, a decoding device is provided. The device includes an interface for receiving a plurality of ATSC link layer protocol data packets, each of the plurality of ATSC link layer protocol data packets including a data packet header and a data packet payload encapsulating digital content, wherein one or more of the plurality of ATSC link layer protocol data packets include content of one or more services transmitted by ATSC. The device also includes a decoding unit, wherein the decoding unit is configured to decode the data packet payload of each of at least one ATSC link layer protocol data packet in the plurality of ATSC link layer protocol data packets to obtain the digital content of the one ATSC link layer protocol data packet of the at least one ATSC link layer protocol data packet. One or more other ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets include one or more table fragments of each of one or more tables, wherein each of the one or more table fragments includes metadata supporting service selection and / or includes information about the content of the payload of each of the one or more ATSC link layer protocol data packets and / or includes information about another table fragment in the one or more table fragments. Each of the one or more table fragments of each of the one or more tables includes table management information including management information for the table fragment and / or for the table, wherein the table management information includes information about one or more management parameters.

[0018] In addition, according to an embodiment, a device for generating multiple ATSC link layer protocol data packets is provided. The device includes: an interface for receiving input data. In addition, the device also includes a data packet generator for generating multiple ATSC link layer protocol data packets based on the input data, so that each of the multiple ATSC link layer protocol data packets includes a data packet header and a data packet payload that encapsulates digital content. The data packet generator is configured to generate one or more ATSC link layer protocol data packets from the multiple ATSC link layer protocol data packets, so that the digital content encapsulated in the data packet payload of each of the one or more ATSC link layer protocol data packets includes: digital broadcast content, and / or distribution and communication protocol data packets or part thereof, and / or unified speech and audio coding content or extended high-efficiency advanced audio coding content, and / or Journaline content.

[0019] In addition, according to another embodiment, a device for generating a plurality of ATSC link layer protocol data packets is provided. The device includes: an interface for receiving input data. Moreover, the device also includes a data packet generator for generating a plurality of ATSC link layer protocol data packets based on the input data, so that each of the plurality of ATSC link layer protocol data packets includes a data packet header and a data packet payload encapsulating digital content, wherein one or more of the plurality of ATSC link layer protocol data packets include the content of one or more services transmitted by ATSC. The data packet generator is configured to generate a plurality of ATSC link layer protocol data packets, so that one or more other ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets include one or more fragments of a service link mapping table, wherein the one or more fragments of the service link mapping table indicate one or more services transmitted by ATSC.

[0020] In addition, according to another embodiment, a device for generating a plurality of ATSC link layer protocol data packets is provided. The device includes: an interface for receiving input data. Moreover, Figure 2 The apparatus further includes a data packet generator configured to generate a plurality of ATSC link layer protocol data packets based on input data, such that each ATSC link layer protocol data packet includes a data packet header and a data packet payload encapsulating digital content, wherein one or more of the plurality of ATSC link layer protocol data packets include content of one or more services transmitted by ATSC. The data packet generator is configured to generate the plurality of ATSC link layer protocol data packets such that one or more of the plurality of ATSC link layer protocol data packets include one or more fragments of a service packet link mapping table, wherein the one or more fragments of the service packet link mapping table indicate packets of the one or more services transmitted by ATSC.

[0021] According to yet another embodiment, an apparatus for generating multiple ATSC link layer protocol data packets is provided. The apparatus includes an interface for receiving input data. Furthermore, the apparatus includes a data packet generator for generating multiple ATSC link layer protocol data packets based on the input data, each of which includes a data packet header and a data packet payload encapsulating digital content. One or more of the multiple ATSC link layer protocol data packets include content of one or more services transmitted by ATSC. The data packet generator is configured to generate the multiple ATSC link layer protocol data packets such that one or more other ATSC link layer protocol data packets in the multiple ATSC link layer protocol data packets include one or more table fragments for each of one or more tables, wherein each of the one or more table fragments includes metadata supporting selection of the service, and / or includes information regarding the content of the data packet payload of each of the one or more ATSC link layer protocol data packets, and / or includes information regarding another table fragment in the one or more table fragments. Each of the one or more table fragments in each of the one or more tables includes table management information, the table management information including management information for the table fragment and / or for the table, wherein the table management information includes information regarding one or more management parameters.

[0022] Furthermore, according to an embodiment, a data stream is provided, comprising a plurality of ATSC link layer protocol packets. Each of the plurality of ATSC link layer protocol packets includes a packet header and a packet payload encapsulating digital content. The digital content encapsulated within the packet payload of one or more ATSC link layer protocol packets in the plurality of ATSC link layer protocol packets includes: digital broadcast content, and / or distribution and communication protocol packets or portions thereof, and / or unified speech and audio coding content or extended high-efficiency advanced audio coding content, and / or journaline content.

[0023] In addition, according to another embodiment, a data stream is provided, comprising a plurality of ATSC link layer protocol data packets. Each of the plurality of ATSC link layer protocol data packets includes a data packet header and a data packet payload encapsulating digital content, wherein one or more of the plurality of ATSC link layer protocol data packets include content of one or more services transmitted by ATSC. The data stream includes one or more ATSC link layer protocol data packets among the plurality of ATSC link layer protocol data packets, wherein the one or more ATSC link layer protocol data packets include one or more fragments of a service link mapping table. The one or more fragments of the service link mapping table indicate one or more services transmitted by ATSC.

[0024] In addition, according to another embodiment, a data stream is provided, comprising a plurality of ATSC link layer protocol packets. Each of the plurality of ATSC link layer protocol packets includes a packet header and a packet payload encapsulating digital content, wherein one or more of the plurality of ATSC link layer protocol packets include content of one or more services transmitted by ATSC. The data stream includes one or more further ATSC link layer protocol packets among the plurality of ATSC link layer protocol packets, wherein the one or more further ATSC link layer protocol packets include one or more fragments of a service packet link mapping table, wherein the one or more fragments of the service packet link mapping table indicate one or more packets of a plurality of services transmitted by ATSC.

[0025] In addition, according to another embodiment, a data stream is provided, comprising a plurality of ATSC link layer protocol data packets. Each of the plurality of ATSC link layer protocol data packets includes a data packet header and a data packet payload encapsulating digital content, wherein one or more of the plurality of ATSC link layer protocol data packets include content of one or more services transmitted by ATSC. One or more other ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets include one or more table fragments for each of one or more tables, wherein each of the one or more table fragments includes metadata supporting selection of a service, and / or includes information about the content of the data packet payload of each of the one or more ATSC link layer protocol data packets, and / or includes information about another table fragment in the one or more table fragments. Each of the one or more table fragments in each of the one or more tables includes table management information, the table management information including management information for the table fragment and / or for the table, wherein the table management information includes information about one or more management parameters.

[0026] In addition, according to an embodiment, a method for decoding is provided. The method includes:

[0027] - receiving a plurality of ATSC link layer protocol packets, each ATSC link layer protocol packet comprising a packet header and a packet payload encapsulating digital content, wherein the digital content encapsulated within the packet payload of each of one or more ATSC link layer protocol packets in the plurality of ATSC link layer protocol packets comprises digital broadcast content, and / or distribution and communication protocol packets or portions thereof, and / or unified speech and audio coding content or extended high-efficiency advanced audio coding content, and / or Journaline content; and

[0028] -Decoding a packet payload of each of at least one ATSC link layer protocol packet among the one or more ATSC link layer protocol packets to obtain digital content of the one ATSC link layer protocol packet among the at least one ATSC link layer protocol packet.

[0029] In addition, according to another embodiment, a method for decoding is provided. The method includes:

[0030] - receiving a plurality of ATSC link layer protocol packets, each ATSC link layer protocol packet including a packet header and a packet payload encapsulating digital content, wherein one or more of the plurality of ATSC link layer protocol packets include content of one or more services transmitted by ATSC; and

[0031] -Decoding a packet payload of each of at least one ATSC link layer protocol packet among a plurality of ATSC link layer protocol packets to obtain digital content of the one ATSC link layer protocol packet among the at least one ATSC link layer protocol packet.

[0032] One or more other ATSC link layer protocol packets in the plurality of ATSC link layer protocol packets include one or more segments of a service link map table. The one or more segments of the service link map table indicate one or more services transmitted by the ATSC. The method includes identifying an ATSC link layer protocol packet including content of one of the one or more services by analyzing the one or more segments of the service link map table.

[0033] In addition, according to another embodiment, a method for decoding is provided. The method includes:

[0034] - receiving a plurality of ATSC link layer protocol packets, each ATSC link layer protocol packet including a packet header and a packet payload encapsulating digital content, wherein one or more of the plurality of ATSC link layer protocol packets include content of one or more services transmitted by ATSC; and

[0035] - decoding a packet payload of each of at least one ATSC link layer protocol packet of a plurality of ATSC link layer protocol packets to obtain digital content of the one ATSC link layer protocol packet of the at least one ATSC link layer protocol packet.

[0036] One or more other ATSC link layer protocol packets in the plurality of ATSC link layer protocol packets include one or more segments of a service packet link map table, wherein the one or more segments of the service packet link map table indicate one or more packets of a plurality of services transmitted by the ATSC. The method includes providing an output based on at least one of the one or more packets, the output being dependent on at least one of the plurality of services.

[0037] In addition, according to another embodiment, a method for decoding is provided. The method includes:

[0038] - receiving a plurality of ATSC link layer protocol packets, each ATSC link layer protocol packet including a packet header and a packet payload encapsulating digital content, wherein one or more of the plurality of ATSC link layer protocol packets include content of one or more services transmitted by ATSC; and

[0039] -Decoding a packet payload of each of at least one ATSC link layer protocol packet among a plurality of ATSC link layer protocol packets to obtain digital content of the one ATSC link layer protocol packet among the at least one ATSC link layer protocol packet.

[0040] One or more other ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets include one or more table fragments for each of the one or more tables, wherein each of the one or more table fragments includes metadata supporting service selection, and / or includes information about the content of the packet payload of one or more of the plurality of ATSC link layer protocol data packets, and / or includes information about another table fragment in the one or more table fragments. Each of the one or more table fragments in each of the one or more tables includes table management information, the table management information including management information for the table fragment and / or for the table, wherein the table management information includes information about one or more management parameters.

[0041] In addition, according to an embodiment, a method for generating multiple ATSC link layer protocol data packets is provided. The method includes:

[0042] - receiving input data; and

[0043] -Generate a plurality of ATSC link layer protocol packets according to the input data, such that each of the plurality of ATSC link layer protocol packets includes a packet header and a packet payload encapsulating digital content.

[0044] Generate one or more ATSC link layer protocol packets among a plurality of ATSC link layer protocol packets such that the digital content encapsulated in the packet payload of each of the one or more ATSC link layer protocol packets includes digital broadcast content, and / or distribution and communication protocol packets or portions thereof, and / or unified speech and audio coding content or extended high-efficiency advanced audio coding content, and / or Journaline content.

[0045] In addition, according to another embodiment, a method for generating multiple ATSC link layer protocol data packets is provided. The method includes:

[0046] - receiving input data; and

[0047] -Generate multiple ATSC link layer protocol data packets based on input data, so that each of the multiple ATSC link layer protocol data packets includes a data packet header and a data packet payload encapsulating digital content, wherein one or more of the multiple ATSC link layer protocol data packets include content of one or more services transmitted by ATSC.

[0048] The method includes generating multiple ATSC link layer protocol data packets, so that one or more other ATSC link layer protocol data packets in the multiple ATSC link layer protocol data packets include one or more fragments of a service link mapping table, wherein the one or more fragments of the service link mapping table indicate one or more services transmitted by ATSC.

[0049] In addition, according to an embodiment, a method for generating multiple ATSC link layer protocol data packets is provided. The method includes:

[0050] - receiving input data; and

[0051] -Generate multiple ATSC link layer protocol data packets based on input data, so that each of the multiple ATSC link layer protocol data packets includes a data packet header and a data packet payload encapsulating digital content, wherein one or more of the multiple ATSC link layer protocol data packets include content of one or more services transmitted by ATSC.

[0052] Generating multiple ATSC link layer protocol data packets is implemented so that one or more of the multiple ATSC link layer protocol data packets include one or more fragments of a service packet link mapping table, and the one or more fragments of the service packet link mapping table indicate one or more packets of multiple services transmitted by ATSC.

[0053] In addition, according to another embodiment, a method for generating multiple ATSC link layer protocol data packets is provided. The method includes:

[0054] - receiving input data; and

[0055] -Generate multiple ATSC link layer protocol data packets based on input data, so that each of the multiple ATSC link layer protocol data packets includes a data packet header and a data packet payload encapsulating digital content, wherein one or more of the multiple ATSC link layer protocol data packets include content of one or more services transmitted by ATSC.

[0056] Wherein, generating a plurality of ATSC link layer protocol data packets is implemented so that one or more other ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets include one or more table fragments of each of the one or more tables, wherein each of the one or more table fragments includes metadata supporting selection of a service, and / or includes information about the content of the packet payload of each of the one or more ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets, and / or includes information about another table fragment in the one or more table fragments.

[0057] Each of the one or more table fragments of each of the one or more tables includes table management information including management information for the table fragment and / or for the table, wherein the table management information includes information about one or more management parameters.

[0058] Furthermore, according to an embodiment, a computer program is provided for implementing any of the above methods when running on a computer or a signal processor.

[0059] The embodiments implement low-level packet transmission in ATSC.

[0060] In some embodiments, DCP packet encapsulation in ATSC is implemented.

[0061] According to some embodiments, an ALP packet structure for DCP encapsulation is provided.

[0062] Some embodiments support specific "digital broadcast" applications.

[0063] For example, according to some embodiments, the integration of DRM and ATSC is achieved through DCP packaging.

[0064] In an embodiment, the xHE-AAC / USAC audio codec and the Journaline text application are enabled for use in ATSC by integrating DRM into ATSC.

[0065] In particular, in some embodiments, integration of Digital Radio Manager (DRM) data streams with ATSC signals, system configuration, service bit bandwidth allocation, and signaling optimization can be achieved.

[0066] According to an embodiment, a link mapping table for DRM broadcast is provided.

[0067] In an embodiment, LMT-R fragments are provided (eg, distribution across multiple physical layer pipes (PLPs), version management, fragment management, etc.).

[0068] According to an embodiment, an additional header value for an ALP data packet for LMT-R is provided.

[0069] In an embodiment, a general method is provided for accessing DRM service metadata for service selection, and providing a link with the physical DCP data stream carrying the corresponding broadcast service.

[0070] Optionally, a link mapping table is provided for DRM radio service data packet selection. For example, generic, ATSC-wide category definitions can be provided, such as language, country of origin, program type, target audience, and broadcast network. Each DRM service can then be assigned to "none," one or more values ​​in any or all categories. This can be technically implemented, for example, via the LMT-R-SG segment, involving aspects such as PLP and version control.

[0071] According to some embodiments, the ATSC standard A / 330 revision (see [1]) is provided for signaling and carrying of DRM DCP packets.

[0072] In an embodiment, the A / 330 standard is extended to enable it to carry additional types of data packets, and signaling using the new data types is defined to make it practical.

[0073] According to an embodiment, DRM DCP packets are added to the data format type that can be carried directly in the ATSC Link-Layer Protocol (ALP) packet stream, and multiple dedicated Link Mapping Tables (LMTs) are provided to enable the receiver to locate specific DRM services carried in the Multiplex Distribution Interface (MDI) stream within the DCP packets. According to an embodiment, the LMT provides sufficient information and supporting elements to enable efficient selection of specific DRM services in ATSC 3.0 transmissions.

[0074] In one embodiment, the structure of the A / 330 standard is extended by using certain reserved addresses that should be ignored by devices unaware of their assigned purpose. Thus, they only utilize the extensibility features built into ATSC 3.0 for these purposes. Existing ATSC television and data services implemented according to the relevant standards are not affected by this addition.

[0075] The embodiment enables DRM transmission via ATSC, thereby also enabling xHE-AAC and Journaline transmission via ATSC. By signaling services in ATSC, a receiving end can access programs and services and playback them.

[0076] In an embodiment, an efficient service signaling method is provided.

[0077] According to an embodiment, the transmission of radio programs is achieved in a manner that enables users to actually find and distinguish the differences between radio programs and television broadcast programs.

[0078] Embodiments provide that a mobile device can switch between different communication paths (depending on their availability), wherein service layer decoding is available for all communication paths. The terminal can receive the same digital broadcast standard (DRM) via ATSC (for example, when a particular broadcast program is not directly available via DRM).

[0079] The embodiments provide a device or software at a transmission end for providing DRM to ATSC, or multiplexing and / or transmitting DRM within ATSC.

[0080] The embodiment provides a receiving-end device and software for receiving, decoding, and replaying ATSC, wherein DCP is transmitted via ATSC.

[0081] Specific embodiments are provided in the dependent claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0082] The following describes the embodiments of the present disclosure in detail with reference to the accompanying drawings, wherein:

[0083] Figure 1 A decoding device according to an embodiment is shown.

[0084] Figure 2 An apparatus for generating a plurality of ATSC link layer protocol packets according to an embodiment is shown.

[0085] Figure 3 A data flow including a plurality of ATSC link layer protocol packets is shown according to an embodiment.

[0086] Figure 4 The components of the service grouping mechanism are shown, in particular categories and attributes.

[0087] Figure 5 The service grouping mechanism is shown, especially an example of service grouping achieved through multi-screen sequence.

[0088] Figure 6 The service grouping mechanism is shown, especially an example of single-screen service grouping achieved through intermediate attribute titles.

[0089] Figure 7 An example of a service grouping mechanism, in particular service filtering, is shown. DETAILED DESCRIPTION

[0090] Figure 1 A decoding device according to an embodiment is shown.

[0091] The apparatus includes an interface 110 for receiving a plurality of ATSC link layer protocol data packets, each of the plurality of ATSC link layer protocol data packets including a data packet header and a data packet payload encapsulating digital content.

[0092] In addition, the apparatus further comprises a decoding unit 120 .

[0093] In a first embodiment, the digital content encapsulated within the packet payload of one or more ATSC link layer protocol packets in a plurality of ATSC link layer protocol packets includes: digital broadcast content, and / or distribution communication protocol packets or a portion thereof, and / or unified speech and audio coding content or extended high-efficiency advanced audio coding content, and / or Journaline content.

[0094] The decoding unit 120 is configured to decode the packet payload of each of at least one ATSC link layer protocol packet among the one or more ATSC link layer protocol packets to obtain the digital content of the one ATSC link layer protocol packet among the at least one ATSC link layer protocol packet.

[0095] According to an embodiment, the digital content encapsulated in the packet payload of one of the one or more ATSC link layer protocol packets may include, for example, digital broadcast content. The decoding unit 120 may be configured to decode the packet payload of the ATSC link layer protocol packet to obtain the digital broadcast content encapsulated in the packet payload of the ATSC link layer protocol packet.

[0096] In an embodiment, the digital content encapsulated in the packet payload of the ATSC link layer protocol packet in one or more ATSC link layer protocol packets may include, for example, a distribution and communication protocol packet or a portion thereof. The decoding unit 120 may be configured to decode the packet payload of the ATSC link layer protocol packet to obtain the distribution and communication protocol packet or a portion thereof encapsulated in the packet payload of the ATSC link layer protocol packet.

[0097] According to an embodiment, the distribution and communication protocol packet or a portion thereof encapsulated in the packet payload of the ATSC link layer protocol packet may include, for example, digital broadcast content. The decoding unit 12, for example, 0, may be configured to decode the packet payload of the ATSC link layer protocol packet to obtain the digital broadcast content included in the distribution and communication protocol packet or a portion thereof encapsulated in the packet payload of the ATSC link layer protocol packet.

[0098] In an embodiment, the digital broadcast content includes, for example, global digital broadcast content.

[0099] According to an embodiment, the digital content within the packet payload of the ATSC link layer protocol packet encapsulated in one or more ATSC link layer protocol packets may include, for example, unified speech and audio coding content or extended high-efficiency advanced audio coding content. The decoding unit 120 may be configured to, for example, decode the packet payload of the ATSC link layer protocol packet to obtain the unified speech and audio coding content or extended high-efficiency advanced audio coding content encapsulated within the packet payload of the ATSC link layer protocol packet.

[0100] In an embodiment, the digital content encapsulated in the packet payload of the ATSC link layer protocol packet in one or more ATSC link layer protocol packets may include, for example, Journaline content. The decoding unit 120 may be configured to, for example, decode the packet payload of the ATSC link layer protocol packet to obtain the Journaline content encapsulated in the packet payload of the ATSC link layer protocol packet.

[0101] According to an embodiment, the apparatus may also include, for example, a renderer for providing an output, which may be one or more audio output signals, or visual output, or data output, depending on the digital content encapsulated within the ATSC link layer protocol packets.

[0102] In an embodiment, the renderer may be configured to provide output using Journaline content, for example.

[0103] According to an embodiment, one or more other ATSC link layer protocol packets in the plurality of ATSC link layer protocol packets include one or more segments of a service link mapping table. The one or more segments of the service link mapping table indicate one or more services of ATSC transmission. The decoding unit 120 may be configured to, for example, analyze the one or more segments of the service link mapping table to identify an ATSC link layer protocol packet, for example, including the content of one of the one or more services.

[0104] exist Figure 1 In the first variant of the first embodiment shown, Figure 1 The device shown includes: an interface 110 for receiving multiple ATSC link layer protocol data packets, each ATSC link layer protocol data packet including a data packet header and a data packet payload encapsulating digital content, wherein one or more of the multiple ATSC link layer protocol data packets include content of one or more services transmitted by ATSC.

[0105] In addition, the device also includes a decoding unit 120, wherein the decoding unit 120 is configured to decode the packet payload of each of at least one ATSC link layer protocol data packet among multiple ATSC link layer protocol data packets to obtain the digital content of the one ATSC link layer protocol data packet among the at least one ATSC link layer protocol data packet.

[0106] One or more other ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets include one or more fragments of the service link mapping table.

[0107] One or more segments of the service link mapping table indicate one or more services transmitted by ATSC.

[0108] The decoding unit 120 is configured to identify an ATSC link layer protocol data packet including content of one of the one or more services by analyzing one or more segments of the service link mapping table.

[0109] According to an embodiment, the one or more segments of the service link mapping table are one or more segments of a radio service link mapping table. The one or more segments of the radio service link mapping table indicate one or more radio services transmitted by ATSC. The decoding unit 120 can be configured to, for example, identify an ATSC link layer protocol packet including content of one of the one or more radio services by analyzing the one or more segments of the radio service link mapping table.

[0110] In an embodiment, one or more segments of the radio service link mapping table include metadata of one or more radio services transmitted by ATSC.

[0111] According to an embodiment, at least some of the plurality of ATSC link layer protocol packets encapsulate a plurality of distribution and communication protocol packets, wherein the plurality of distribution and communication protocol packets include one or more radio services of an ATSC transmission.

[0112] In an embodiment, the metadata of one or more radio services may, for example, include information about a service tag, and / or information about a reuse tag, and / or information about a language, and / or information about a program type, and / or information about a region, and / or information about a country of origin, and / or audio configuration information, and / or a data application identifier.

[0113] According to an embodiment, the one or more segments of the radio service link mapping table are one or more segments of the global digital broadcast radio link mapping table. The one or more segments of the global digital broadcast radio link mapping table indicate one or more global digital broadcast radio services transmitted by ATSC. The decoding unit 120 can be configured to, for example, identify an ATSC link layer protocol packet including content of one of the one or more global digital broadcast radio services by analyzing the one or more segments of the global digital broadcast radio link mapping table.

[0114] In an embodiment, one or more segments of the global digital broadcast radio link mapping table indicate an association between at least one of the one or more global digital broadcast radio services and one or more global digital broadcast multiplex distribution interface streams. The decoding unit 120 can be configured to, for example, identify, based on the association, an ATSC link layer protocol packet including, for example, global digital broadcast content.

[0115] According to an embodiment, one or more fragments of the global digital broadcast radio link mapping table indicate the association of at least one of the one or more global digital broadcast radio services with one or more global digital broadcast multiplex distribution interface streams by indicating a physical layer pipe identifier and / or an ATSC link layer protocol packet identifier, and by indicating at least one of the one or more global digital broadcast radio service identifiers associated with one interface stream in the one or more global digital broadcast multiplex distribution interface streams.

[0116] In an embodiment, the metadata of one global digital broadcast radio service in the one or more global digital broadcast radio services corresponds to metadata included in one global digital broadcast multiplex distribution interface stream in the one or more global digital broadcast multiplex distribution interface streams associated with the one or more global digital broadcast radio services.

[0117] According to an embodiment, one or more segments of the radio service link mapping table include emergency alert information, indicating whether at least one of the one or more global digital broadcast multiplex distribution interface streams associated with the one or more global digital broadcast radio services indicates emergency alert information. The decoding unit 120 can be configured to analyze the emergency alert information to determine whether it indicates an emergency alert.

[0118] In an embodiment, if the packet payloads of two ATSC link layer protocol packets in the plurality of ATSC link layer protocol packets include global digital broadcast content of the same global digital broadcast multiplexing distribution interface stream, the packet headers of the two ATSC link layer protocol packets may, for example, include the same substream identifier associated with the global digital broadcast multiplexing distribution interface stream. The decoding unit 120 may, for example, be configured to decode the global digital broadcast multiplexing distribution interface stream by analyzing the substream identifiers of the packet headers of the two ATSC link layer protocol packets and decoding the packet payloads of the two ATSC link layer protocol packets.

[0119] According to an embodiment, the one or more segments of the radio service link mapping table are one or more segments of the digital audio broadcasting link mapping table. The one or more segments of the digital audio broadcasting link mapping table indicate one or more digital audio broadcasting services transmitted by ATSC. The decoding unit 120 can be configured to, for example, identify an ATSC link layer protocol packet including content of one of the one or more digital audio broadcasting services by analyzing the one or more segments of the digital audio broadcasting link mapping table.

[0120] In an embodiment, one or more segments of the digital audio broadcast link mapping table indicate an association between at least one of the one or more digital audio broadcast services and one or more EDI (DAB interface encapsulation) streams. The decoding unit 120 may be configured to, for example, identify ATSC link layer protocol packets including digital audio broadcast content based on the association.

[0121] According to an embodiment, the one or more other ATSC link layer protocol packets are two or more other ATSC link layer protocol packets, wherein the one or more segments are two or more segments, and wherein the one or more services are multiple services. The two or more other ATSC link layer protocol packets include two or more segments of a service link mapping table, and the two or more segments of the service link mapping table indicate multiple services transmitted by ATSC. The decoding unit 120 can be configured to, for example, identify an ATSC link layer protocol packet including the content of one of the one or more services by analyzing the two or more segments of the service link mapping table.

[0122] In an embodiment, one or more other ATSC link layer protocol packets in the plurality of ATSC link layer protocol packets include one or more fragments of a service packet link mapping table, wherein the one or more fragments of the service packet link mapping table indicate one or more packets of a plurality of services of the ATSC transmission. The apparatus may, for example, include an output interface for providing an output based on at least one of the one or more packets, wherein the output depends on at least one of the plurality of services.

[0123] exist Figure 1 In the second variation of the first embodiment shown, Figure 1 The device shown includes: an interface 110 for receiving multiple ATSC link layer protocol data packets, each ATSC link layer protocol data packet including a data packet header and a data packet payload encapsulating digital content, wherein one or more of the multiple ATSC link layer protocol data packets include content of one or more services transmitted by ATSC.

[0124] In addition, the device also includes a decoding unit 120, wherein the decoding unit 120 is configured to decode the packet payload of each of at least one ATSC link layer protocol data packet in a plurality of ATSC link layer protocol data packets to obtain the digital content of the one ATSC link layer protocol data packet in the at least one ATSC link layer protocol data packet.

[0125] One or more other ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets include one or more fragments of a service packet link mapping table, wherein the one or more fragments of the service packet link mapping table indicate one or more packets of a plurality of services transmitted by ATSC.

[0126] The apparatus further comprises an output interface for providing an output based on at least one of the one or more data packets, wherein the output is dependent on at least one of the plurality of services.

[0127] According to an embodiment, the one or more segments of the service packet link mapping table are one or more segments of a radio service packet link mapping table. The one or more segments of the radio service packet link mapping table indicate one or more packets of a plurality of radio services transmitted by ATSC. The output interface may, for example, be configured to provide an output based on at least one of the one or more packets, wherein the output depends on at least one of the plurality of radio services.

[0128] In an embodiment, the one or more segments of the service packet link mapping table are one or more segments of a global digital broadcast radio service packet link mapping table. The one or more segments of the global digital broadcast radio service data packet link mapping table indicate one or more data packets of a plurality of global digital broadcast radio services transmitted by ATSC. The output interface may, for example, be configured to provide an output based on at least one of the one or more data packets, wherein the output depends on at least one of the plurality of global digital broadcast radio services.

[0129] According to an embodiment, the one or more segments of the service packet link mapping table are one or more segments of a digital audio broadcasting service packet link mapping table. The one or more segments of the digital audio broadcasting service packet link mapping table indicate one or more data packets of a plurality of digital audio broadcasting services transmitted by ATSC. The output interface may, for example, be configured to provide an output based on at least one of the one or more data packets, wherein the output depends on at least one of the plurality of digital audio broadcasting services.

[0130] In an embodiment, the one or more other ATSC link layer protocol data packets are two or more other ATSC link layer protocol data packets, wherein the one or more fragments of the service packet link mapping table are two or more fragments. The two or more other ATSC link layer protocol data packets include two or more fragments of the service packet link mapping table.

[0131] According to an embodiment, the apparatus may be configured to use a service group link mapping table, for example, to enable a user to select a service from a plurality of services.

[0132] In an embodiment, the apparatus may be configured, for example, to use a service group link mapping table to present a filtered subset of multiple services to a user according to one or more filtering conditions.

[0133] According to an embodiment, the output interface may be configured to output information of at least two services among the plurality of services according to at least one of the one or more groups. The apparatus may include a user interface or other mechanism for enabling a user to select a service from the information of at least two services among the plurality of services.

[0134] In an embodiment, one or more segments of the service group link mapping table associate two or more of the plurality of services with at least one of two or more categories and / or with at least one of two or more attributes.

[0135] According to an embodiment, if the user has selected at least two categories from two or more categories using a user interface or other mechanism, the output interface may be configured to present only services from a plurality of services associated with all at least two categories selected by the user to the user.

[0136] In an embodiment, if the user has selected at least two attributes from two or more attributes using a user interface or other mechanism, the output interface may be configured, for example, to present to the user services from a plurality of services associated with at least one of the at least two attributes selected by the user.

[0137] According to an embodiment, one or more fragments of the service group link mapping table indicate one or more groups, including: language-based grouping, and / or program type-based grouping, and / or region-based grouping, and / or country-of-origin-based grouping, and / or target audience age group-based grouping, and / or broadcast network-based grouping, and / or data application type-based grouping.

[0138] In an embodiment, one or more fragments of the service packet link mapping table include an indication of a physical layer pipe, and / or an indication of an ATSC link layer protocol data packet, and the indication of the physical layer pipe and the indication of the ATSC link layer protocol data packet include one of the one or more fragments of the service packet link mapping table.

[0139] According to an embodiment, one or more other ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets include one or more table fragments for each of the one or more tables, wherein each of the one or more table fragments may, for example, include metadata supporting service selection, and / or may, for example, include information about the content of the packet payload of one or more of the plurality of ATSC link layer protocol data packets, and / or may, for example, include information about another table fragment in the one or more table fragments. Each of the one or more table fragments in each of the one or more tables may, for example, include table management information, which may, for example, include management information for the table fragment and / or for the table, wherein the table management information may, for example, include information about one or more management parameters.

[0140] exist Figure 1 In the third variation of the first embodiment shown, Figure 1 The device shown includes: an interface 110 for receiving multiple ATSC link layer protocol data packets, each ATSC link layer protocol data packet including a data packet header and a data packet payload encapsulating digital content, wherein one or more of the multiple ATSC link layer protocol data packets include content of one or more services transmitted by ATSC.

[0141] In addition, the device also includes a decoding unit 120, wherein the decoding unit 120 is configured to decode the packet payload of each of at least one ATSC link layer protocol data packet among multiple ATSC link layer protocol data packets to obtain the digital content of the one ATSC link layer protocol data packet among the at least one ATSC link layer protocol data packet.

[0142] One or more other ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets include one or more table fragments for each of the one or more tables, wherein each of the one or more table fragments includes metadata supporting service selection, and / or includes information about the content of the packet payload of each of the one or more ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets, and / or includes information about another table fragment in the one or more table fragments.

[0143] Each of the one or more table fragments of each of the one or more tables includes table management information including management information for the table fragment and / or for the table, wherein the table management information includes information about one or more management parameters.

[0144] According to an embodiment, at least one of the one or more tables may, for example, include two or more table fragments.Information on at least one of the one or more management parameters exists in each of the two or more table fragments.

[0145] In an embodiment, the one or more management parameters include a plurality of management parameters, and information of each management parameter in the plurality of management parameters exists in each of the two or more table fragments.

[0146] According to an embodiment, at least one of the one or more table fragments of a table in the one or more tables may, for example, include a value of a data revision parameter for the table as information about one of the one or more management parameters. Decoding unit 120 may, for example, be configured to compare a current revision number of the table stored in decoding unit 120 with the value of the data revision parameter for the table in the at least one table fragment to determine whether information stored in the table in decoding unit 120 needs to be updated.

[0147] In an embodiment, each of at least one table segment in one or more table segments of a table in the one or more tables may, for example, include a value of a segment data revision parameter of the at least one table segment as information about another management parameter in the one or more management parameters. Decoding unit 120 may, for example, be configured to compare a current revision number of the table segment stored in decoding unit 120 with the value of the segment data revision parameter of the table segment to determine whether information stored in decoding unit 120 for the table segment needs to be updated.

[0148] According to an embodiment, a body portion of at least one of the one or more table fragments of at least one of the one or more tables is compressed.

[0149] In an embodiment, each of the one or more table fragments of at least one table may, for example, include a compression value indicating whether a body portion of the table fragment is compressed, the compression value being information about another management parameter of the one or more management parameters.

[0150] According to an embodiment, the decoding unit 120 may be configured, for example, to decompress the body portion of at least one table segment among the one or more table segments if it is determined that the storage information of the table segment stored in the decoding unit 120 needs to be updated. The decoding unit 120 may be configured, for example, not to decompress the body portion of the table segment if it is determined that the storage information of the table segment stored in the decoding unit 120 does not need to be updated.

[0151] In an embodiment, each of at least one of the one or more table segments of a table in the one or more tables may include, for example, revision table information for the table. The revision table information for the table indicates a value of a segment data revision parameter for each of the one or more table segments of the table in the ATSC transmission.

[0152] According to an embodiment, the decoding unit 120 can, for example, be configured to compare the current revision number of the table segment stored in the decoding unit 120 and the value of the segment data revision parameter for the table segment to determine whether the storage information of the table segment stored in the decoding unit 120 needs to be updated.

[0153] In an embodiment, the revised table information for a table indicates the location of each of one or more table segments of the table in the ATSC transmission.

[0154] According to an embodiment, revised table information for a table indicates the location of each of one or more table segments of a table in an ATSC transmission by indicating a physical layer pipe including the table segment and / or by indicating an ATSC link layer protocol packet including the table segment.

[0155] In an embodiment, the decoding unit 120 may be configured, for example, to obtain the table segment from the location of the table segment in the ATSC transmission if the decoding unit 120 has determined that the storage information of the table segment stored in the decoding unit 120 needs to be updated. The decoding unit 120 may be configured, for example, not to obtain the table segment from the location of the table segment in the ATSC transmission if the decoding unit 120 has determined that the storage information of the table segment stored in the decoding unit 120 does not need to be updated.

[0156] According to an embodiment, the one or more table fragments of each of the one or more tables include one or more fragments of a traffic link mapping table.

[0157] In an embodiment, the one or more table fragments of each of the one or more tables include one or more fragments of a traffic packet link mapping table.

[0158] According to an embodiment, one or more table fragments of each of the one or more tables include one or more fragments of a logo / icon table (LIT), which includes information about one or more versions of a logo or icon; and / or, one or more table fragments of each of the one or more tables include one or more fragments of a logo / icon variant (LIV), which includes image data of a version of a logo or icon.

[0159] In an embodiment, a first table in the one or more tables has a first table type, wherein a second table in the one or more tables has a second table type different from the first table type. The decoding unit 120 can, for example, be configured to decode the one or more table segments of the first table and the one or more table segments of the second table using the same decoding algorithm.

[0160] According to an embodiment, the first table has a table type from a group consisting of at least four table types, the group of table types including the following table types:

[0161] Link Mapping Table for Radio Services (LMT-R);

[0162] Service Group Link Mapping Table (LMT-R-SG);

[0163] Logo / Icon Table (LIT); and

[0164] Logo / Icon Variant (LIV).

[0165] The second table has a different one of the group of at least four table types.

[0166] Figure 2 An apparatus for generating a plurality of ATSC link layer protocol packets according to an embodiment is shown.

[0167] The apparatus comprises an interface 210 for receiving input data.

[0168] Moreover, the apparatus further includes a data packet generator 220 for generating a plurality of ATSC link layer protocol data packets according to the input data, so that each of the plurality of ATSC link layer protocol data packets may, for example, include a data packet header and a data packet payload encapsulating digital content.

[0169] In a first embodiment, the data packet generator 220 is configured to generate one or more ATSC link layer protocol data packets from a plurality of ATSC link layer protocol data packets, such that the digital content encapsulated within the data packet payload of each of the one or more ATSC link layer protocol data packets includes: digital broadcast content, and / or distribution and communication protocol data packets or portions thereof, and / or unified speech and audio coding content or extended high-efficiency advanced audio coding content, and / or Journaline content.

[0170] According to an embodiment, the data packet generator 220 can, for example, be configured to generate an ATSC link layer protocol data packet in one or more ATSC link layer protocol data packets, so that the digital content encapsulated within the ATSC link layer protocol data packet can, for example, include digital broadcast content.

[0171] In an embodiment, the data packet generator 220 can, for example, be configured to generate an ATSC link layer protocol data packet in one or more ATSC link layer protocol data packets, so that the digital content encapsulated within the ATSC link layer protocol data packet can, for example, include a distribution and communication protocol data packet or a portion thereof.

[0172] According to an embodiment, the distribution and communication protocol data packet or portion thereof encapsulated within the data packet payload of the ATSC link layer protocol data packet may include, for example, digital broadcast content.

[0173] In an embodiment, the digital broadcast content may, for example, include global digital broadcast content.

[0174] According to an embodiment, the data packet generator 220 can, for example, be configured to generate an ATSC link layer protocol data packet in one or more ATSC link layer protocol data packets, so that the digital content encapsulated within the ATSC link layer protocol data packet can, for example, include unified voice and audio coding content or extended high-efficiency advanced audio coding content.

[0175] In an embodiment, the data packet generator 220 may, for example, be configured to generate an ATSC link layer protocol data packet in one or more ATSC link layer protocol data packets such that the digital content encapsulated within the ATSC link layer protocol data packet may, for example, include Journaline content.

[0176] According to an embodiment, the data packet generator 220 may be configured to generate a plurality of ATSC link layer protocol data packets, such that one or more other ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets include one or more segments of a service link mapping table. The one or more segments of the service link mapping table indicate one or more services of the ATSC transmission.

[0177] exist Figure 2 In the first variant of the device shown, Figure 2 The illustrated apparatus comprises an interface 210 for receiving input data.

[0178] In addition, the device also includes a data packet generator 220, which is used to generate multiple ATSC link layer protocol data packets based on the input data, so that each ATSC link layer protocol data packet includes a data packet header and a data packet payload that encapsulates digital content, wherein one or more of the multiple ATSC link layer protocol data packets include the content of one or more services transmitted by ATSC.

[0179] The data packet generator 220 is configured to generate a plurality of ATSC link layer protocol data packets, such that one or more other ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets include one or more fragments of a service link mapping table, wherein the one or more fragments of the service link mapping table indicate one or more services of the ATSC transmission.

[0180] In an embodiment, the one or more segments of the service link mapping table are one or more segments of a radio service link mapping table. The one or more segments of the radio service link mapping table indicate one or more radio services of ATSC transmission.

[0181] According to an embodiment, the data packet generator 220 may, for example, be configured to generate one or more other ATSC link layer protocol data packets such that one or more segments of the radio service link mapping table include metadata of one or more radio services transmitted by ATSC.

[0182] In an embodiment, at least a portion of the plurality of ATSC link layer protocol packets encapsulate a plurality of distribution and communication protocol packets comprising one or more radio services of an ATSC transmission.

[0183] According to an embodiment, the data packet generator 220 can, for example, be configured to generate one or more other ATSC link layer protocol data packets so that the metadata of one or more radio services can, for example, include information about a service tag, and / or information about a multiplexing tag, and / or information about a language, and / or information about a program type, and / or information about a region, and / or information about a country of origin, and / or audio configuration information, and / or a data application identifier.

[0184] In an embodiment, the data packet generator 220 can, for example, be configured to generate one or more other ATSC link layer protocol data packets such that one or more fragments of the radio service link mapping table are one or more fragments of the global digital broadcast radio link mapping table, wherein the one or more fragments of the global digital broadcast radio link mapping table indicate one or more global digital broadcast radio services transmitted by ATSC.

[0185] According to an embodiment, the data packet generator 220 can, for example, be configured to generate one or more other ATSC link layer protocol data packets such that one or more fragments of the global digital broadcast radio link mapping table indicate an association of at least one of the one or more global digital broadcast radio services with one or more global digital broadcast multiplex distribution interface streams.

[0186] In an embodiment, the packet generator 220 can, for example, be configured to generate one or more other ATSC link layer protocol packets such that one or more fragments of the global digital broadcast radio link mapping table indicate the association of at least one of the one or more global digital broadcast radio services with one or more global digital broadcast multiplex distribution interface streams by indicating a physical layer pipe identifier and / or an ATSC link layer protocol packet identifier, and by indicating at least one of one or more global digital broadcast radio service identifiers associated with one of the one or more global digital broadcast multiplex distribution interface streams.

[0187] According to an embodiment, the data packet generator 220 may be configured, for example, to analyze one or more global digital broadcast multiplex distribution interface streams associated with one or more global digital broadcast radio services. The data packet generator 220 may be configured, for example, to generate one or more other ATSC link layer protocol data packets so that the metadata of one of the one or more global digital broadcast radio services corresponds to the metadata included in one of the one or more global digital broadcast multiplex distribution interface streams associated with the one or more global digital broadcast radio services.

[0188] In an embodiment, the data packet generator 220 may be configured, for example, to analyze one or more global digital broadcast multiplex distribution interface streams associated with one or more global digital broadcast radio services. The data packet generator 220 may be configured, for example, to generate one or more other ATSC link layer protocol packets such that one or more segments of the radio service link mapping table include emergency alert information indicating whether at least one of the one or more global digital broadcast multiplex distribution interface streams associated with the one or more global digital broadcast radio services indicates an emergency alert.

[0189] According to an embodiment, the data packet generator 220 can, for example, be configured to generate multiple ATSC link layer protocol data packets, so that if the data packet payloads of two ATSC link layer protocol data packets among the multiple ATSC link layer protocol data packets include global digital broadcast content of the same global digital broadcast multiplexing distribution interface stream, then the data packet headers of the two ATSC link layer protocol data packets can, for example, include the same sub-stream identifier associated with the global digital broadcast multiplexing distribution interface stream.

[0190] In an embodiment, the one or more segments of the radio service link mapping table are one or more segments of a digital audio broadcasting link mapping table. The one or more segments of the digital audio broadcasting link mapping table indicate one or more digital audio broadcasting services transmitted by ATSC.

[0191] According to an embodiment, the one or more segments of the digital audio broadcast link mapping table indicate an association of at least one of the one or more digital audio broadcast services with one or more EDI (DAB Interface Encapsulation) streams.

[0192] In an embodiment, the one or more other ATSC link layer protocol packets are two or more other ATSC link layer protocol packets, wherein the one or more segments are two or more segments, and wherein the one or more services are multiple services. The packet generator 220 may be configured to generate the two or more other ATSC link layer protocol packets, such that the two or more other ATSC link layer protocol packets include two or more segments of a service link mapping table; wherein the two or more segments of the service link mapping table indicate multiple services of ATSC transmission.

[0193] According to an embodiment, the apparatus may, for example, be configured to repeatedly transmit one or more ATSC link layer protocol data packets including one or more fragments of a service link mapping table.

[0194] In an embodiment, the data packet generator 220 can, for example, be configured to generate multiple ATSC link layer protocol data packets, such that one or more other data packets in the multiple data packets include one or more fragments of a service packet link mapping table, and the one or more fragments of the service packet link mapping table indicate one or more packets of the ATSC transmission of multiple services.

[0195] exist Figure 2 In the second variant of the device shown, Figure 2 The illustrated apparatus comprises an interface 210 for receiving input data.

[0196] also, Figure 2 The device shown also includes a data packet generator 220, which is used to generate multiple ATSC link layer protocol data packets based on input data, so that each ATSC link layer protocol data packet includes a data packet header and a data packet payload encapsulating digital content, wherein one or more of the multiple ATSC link layer protocol data packets include the content of one or more services transmitted by ATSC.

[0197] The data packet generator 220 is configured to generate a plurality of ATSC link layer protocol data packets, such that one or more other ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets include one or more fragments of a service packet link mapping table, wherein the one or more fragments of the service packet link mapping table indicate one or more packets of a plurality of services transmitted by ATSC.

[0198] According to an embodiment, the one or more segments of the service packet link mapping table are one or more segments of the radio service packet link mapping table. The one or more segments of the radio service packet link mapping table indicate one or more packets of a plurality of radio services transmitted by ATSC.

[0199] In an embodiment, the one or more segments of the service packet link mapping table are one or more segments of the global digital broadcast radio service packet link mapping table. The one or more segments of the global digital broadcast radio service packet link mapping table indicate one or more packets of multiple global digital broadcast radio services transmitted by ATSC.

[0200] According to an embodiment, the one or more segments of the service packet link mapping table are one or more segments of the digital audio broadcasting service packet link mapping table. The one or more segments of the digital audio broadcasting service packet link mapping table indicate one or more packets of multiple digital audio broadcasting services transmitted by ATSC.

[0201] In an embodiment, the one or more other ATSC link layer protocol data packets are two or more other ATSC link layer protocol data packets, wherein the one or more fragments of the service packet link mapping table are two or more fragments.

[0202] The data packet generator 220 may, for example, be configured to generate two or more further ATSC link layer protocol data packets such that the two or more further ATSC link layer protocol data packets include two or more fragments of the service packet link mapping table.

[0203] According to an embodiment, the data packet generator 220 can, for example, be configured to generate one or more other ATSC link layer protocol data packets so that one or more fragments of the service packet link mapping table associate two or more of the multiple services with at least one of the two or more categories and / or with at least one of the two or more attributes.

[0204] In an embodiment, the data packet generator 220 can, for example, be configured to generate one or more other ATSC link layer protocol data packets such that one or more fragments of the service packet link mapping table indicate one or more groups, including: language-based groups, and / or program type-based groups, and / or region-based groups, and / or country-of-origin-based groups, and / or target audience age group-based groups, and / or broadcast network-based groups, and / or data application type-based groups.

[0205] According to an embodiment, the data packet generator 220 can be configured, for example, to generate one or more other ATSC link layer protocol data packets, so that one or more fragments of the service link mapping table include an indication of a physical layer pipe, and / or an indication of an ATSC link layer protocol data packet, and the indication of the physical layer pipe and the indication of the ATSC link layer protocol data packet include one of the one or more fragments of the service packet link mapping table.

[0206] In an embodiment, the apparatus may, for example, be configured to repeatedly transmit one or more further ATSC link layer protocol data packets including one or more fragments of the service packet link mapping table.

[0207] According to an embodiment, the packet generator 220 may be configured to generate a plurality of ATSC link layer protocol packets, such that one or more other ATSC link layer protocol packets in the plurality of ATSC link layer protocol packets include one or more table fragments for each of the one or more tables, wherein each of the one or more table fragments may, for example, include metadata supporting a selection of services, and / or may, for example, include information about the content of a packet payload of each of the one or more ATSC link layer protocol packets, and / or may, for example, include information about another table fragment in the one or more table fragments. Each of the one or more table fragments in each of the one or more tables may, for example, include table management information, which may, for example, include management information for the table fragment and / or for the table, wherein the table management information may, for example, include information about one or more management parameters.

[0208] exist Figure 2 In the third variant of the device shown, Figure 2 The illustrated apparatus comprises an interface 210 for receiving input data.

[0209] In addition, the device also includes a data packet generator 220, which is used to generate multiple ATSC link layer protocol data packets based on the input data, so that each data packet includes a data packet header and a data packet payload that encapsulates digital content, wherein one or more of the multiple ATSC link layer protocol data packets include the content of one or more services transmitted by ATSC.

[0210] The packet generator 220 is configured to generate a plurality of ATSC link layer protocol packets such that one or more other ATSC link layer protocol packets in the plurality of ATSC link layer protocol packets include one or more table fragments for each of the one or more tables, wherein each of the one or more table fragments includes metadata supporting selection of a service, and / or includes information about the content of a packet payload of each of one or more of the plurality of ATSC link layer protocol packets, and / or includes information of another table fragment in the one or more table fragments.

[0211] Each of the one or more table fragments of each of the one or more tables includes table management information including management information for the table fragment and / or for the table, wherein the table management information includes information about one or more management parameters.

[0212] According to an embodiment, at least one of the one or more tables may, for example, include two or more table fragments.Information on at least one of the one or more management parameters exists in each of the two or more table fragments.

[0213] In an embodiment, the one or more management parameters include a plurality of management parameters. Information of each management parameter in the plurality of management parameters exists in each of the two or more table fragments.

[0214] According to an embodiment, at least one of the one or more table fragments of a table of the one or more tables may, for example, include a value of a data revision parameter for the table as information of one of the one or more management parameters.

[0215] In an embodiment, each of at least one table fragment of one or more table fragments of a table in one or more tables may, for example, include a value of a fragment data revision parameter of a table fragment for at least one table fragment, the value serving as information of another management parameter in the one or more management parameters.

[0216] According to an embodiment, the data packet generator 220 may be configured to generate a plurality of ATSC link layer protocol data packets such that a body portion of at least one of one or more table fragments of at least one of the one or more tables is compressed.

[0217] In an embodiment, each of the one or more table fragments of the at least one table may include, for example, a compression value indicating whether a body portion of the table fragment is compressed, the compression value being information of another management parameter of the one or more management parameters.

[0218] According to an embodiment, the data packet generator 220 may be configured to generate a plurality of ATSC link layer protocol data packets, for example, so that each of at least one table segment in one or more table segments of a table in one or more tables may include, for example, revised table information for the table. The revised table information for the table indicates a value of a segment data revision parameter for each of the one or more table segments of the table in the ATSC transmission.

[0219] In an embodiment, the revised table information for the table indicates the location of each of the one or more table segments of the table in the ATSC transmission.

[0220] According to an embodiment, the revised table information for the table indicates the location of each of the one or more table segments of the table in the ATSC transmission by indicating the physical layer pipe including the table segment and / or by indicating the ATSC link layer protocol data packet including the table segment.

[0221] In an embodiment, the one or more table fragments of each of the one or more tables include one or more fragments of a service link mapping table.

[0222] According to an embodiment, the one or more table fragments of each of the one or more tables include one or more fragments of a service packet link mapping table.

[0223] In an embodiment, the one or more table fragments of each of the one or more tables include one or more fragments of a logo / icon table (LIT), which includes information of one or more versions of a logo or icon; and / or, the one or more table fragments of each of the one or more tables include one or more fragments of a logo / icon variant (LIV), which includes image data of a version of a logo or icon.

[0224] Figure 3 A data flow including a plurality of ATSC link layer protocol packets is shown according to an embodiment.

[0225] Each of the plurality of ATSC link layer protocol packets includes a packet header and a packet payload encapsulating digital content.

[0226] According to a first embodiment, the digital content encapsulated within the packet payload of each of one or more ATSC link layer protocol packets includes: digital broadcast content, and / or distribution and communication protocol packets or portions thereof, and / or unified speech and audio coding content or extended high-efficiency advanced audio coding content, and / or Journaline content.

[0227] According to an embodiment, the digital content encapsulated within the ATSC link layer protocol data packet may include, for example, digital broadcast content.

[0228] In an embodiment, the digital content encapsulated within the ATSC link layer protocol data packets may, for example, include distribution and communication protocol data packets or portions thereof.

[0229] According to an embodiment, the distribution and communication protocol data packet or portion thereof encapsulated within the data packet payload of the ATSC link layer protocol data packet may include, for example, digital broadcast content.

[0230] In an embodiment, the digital broadcast content may, for example, include global digital broadcast content.

[0231] According to an embodiment, the digital content encapsulated within the ATSC link layer protocol data packet may include, for example, unified speech and audio coding content or extended high-efficiency advanced audio coding content.

[0232] In an embodiment, the digital content encapsulated within the ATSC link layer protocol data packets may include, for example, Journaline content.

[0233] According to an embodiment, the data stream may include, for example, one or more other ATSC link layer protocol data packets among a plurality of ATSC link layer protocol data packets, wherein the one or more other ATSC link layer protocol data packets include one or more fragments of a service link mapping table. The one or more fragments of the service link mapping table indicate one or more services of the ATSC transmission.

[0234] exist Figure 3 In a first variation of the data stream shown, each of the multiple ATSC link layer protocol data packets includes a data packet header and a data packet payload encapsulating digital content, wherein one or more of the multiple ATSC link layer protocol data packets include content of one or more services transmitted by ATSC.

[0235] The data stream includes one or more ATSC link layer protocol data packets among a plurality of ATSC link layer protocol data packets, and the one or more ATSC link layer protocol data packets include one or more fragments of the service link mapping table.

[0236] One or more segments of the service link mapping table indicate one or more services transmitted by ATSC.

[0237] According to an embodiment, the one or more segments of the service link mapping table are one or more segments of a radio service link mapping table. The one or more segments of the radio service link mapping table indicate one or more radio services transmitted by ATSC.

[0238] In an embodiment, one or more segments of the radio service link mapping table include metadata of one or more radio services transmitted by ATSC.

[0239] According to an embodiment, at least some of the plurality of ATSC link layer protocol packets encapsulate a plurality of distribution and communication protocol packets comprising one or more radio services of an ATSC transmission.

[0240] In an embodiment, the metadata of one or more radio services may, for example, include information about a service tag, and / or information about a reuse tag, and / or information about a language, and / or information about a program type, and / or information about a region, and / or information about a country of origin, and / or audio configuration information, and / or a data application identifier.

[0241] According to an embodiment, the one or more segments of the radio service link mapping table are one or more segments of the global digital broadcast radio link mapping table, wherein the one or more segments of the global digital broadcast radio link mapping table indicate one or more global digital broadcast radio services transmitted by ATSC.

[0242] In an embodiment, the one or more segments of the global digital broadcast radio link mapping table indicate an association of at least one global digital broadcast radio service of the one or more global digital broadcast radio services with one or more global digital broadcast multiplex distribution interface flows.

[0243] According to one embodiment, one or more fragments of the global digital broadcast radio link mapping table indicate the association of at least one global digital broadcast radio service of one or more global digital broadcast radio services with one or more global digital broadcast multiplex distribution interface streams by indicating a physical layer pipe identifier and / or an ATSC link layer protocol packet identifier, and by indicating at least one global digital broadcast radio service identifier of one or more global digital broadcast radio service identifiers associated with corresponding global digital broadcast multiplex distribution interface streams in one or more global digital broadcast multiplex distribution interface streams.

[0244] In an embodiment, the metadata of one global digital broadcast radio service among the one or more global digital broadcast radio services corresponds to the metadata included in one global digital broadcast multiplex distribution interface stream among the one or more global digital broadcast radio services associated with the one or more global digital broadcast radio services.

[0245] According to an embodiment, one or more fragments of the radio service link mapping table include emergency warning information for indicating whether at least one global digital broadcast multiplexing distribution interface flow among one or more global digital broadcast multiplexing distribution interface flows associated with one or more global digital broadcast radio services indicates an emergency warning.

[0246] In an embodiment, if the packet payloads of two ATSC link layer protocol data packets among a plurality of ATSC link layer protocol data packets include global digital broadcast content of the same global digital broadcast multiplexing distribution interface stream, the packet headers of the two ATSC link layer protocol data packets may, for example, include the same sub-stream identifier associated with the global digital broadcast multiplexing distribution interface stream.

[0247] According to an embodiment, the one or more segments of the radio service link mapping table are one or more segments of a digital audio broadcasting link mapping table. The one or more segments of the digital audio broadcasting link mapping table indicate one or more digital audio broadcasting services transmitted by ATSC.

[0248] In an embodiment, the one or more segments of the digital audio broadcast link mapping table indicate an association of at least one digital audio broadcast service of the one or more digital audio broadcast services with one or more EDI (DAB Interface Encapsulation) streams.

[0249] According to an embodiment, the one or more further ATSC link layer protocol data packets are two or more further ATSC link layer protocol data packets, wherein the one or more segments are two or more segments, wherein the one or more services are multiple services. The two or more further ATSC link layer protocol data packets include two or more segments of a service link mapping table; wherein the two or more segments of the service link mapping table indicate multiple services transmitted by ATSC.

[0250] In an embodiment, the data stream may, for example, include one or more further ATSC link layer protocol data packets among a plurality of ATSC link layer protocol data packets, the one or more further ATSC link layer protocol data packets including one or more fragments of a service packet link mapping table, the one or more fragments of the service packet link mapping table indicating one or more packets of a plurality of services transmitted by ATSC.

[0251] exist Figure 3 In a second variation of the data stream shown, each of the multiple ATSC link layer protocol data packets includes a data packet header and a data packet payload encapsulating digital content, wherein one or more of the multiple ATSC link layer protocol data packets include content of one or more services transmitted by ATSC.

[0252] The data stream includes one or more other ATSC link layer protocol data packets among multiple ATSC link layer protocol data packets, and the one or more other ATSC link layer protocol data packets include one or more fragments of a service packet link mapping table, and the one or more fragments of the service packet link mapping table indicate one or more packets of multiple services transmitted by ATSC.

[0253] According to an embodiment, the one or more segments of the service packet link mapping table are one or more segments of the radio service packet link mapping table. The one or more segments of the radio service packet link mapping table indicate one or more packets of a plurality of radio services transmitted by ATSC.

[0254] In an embodiment, the one or more segments of the service packet link mapping table are one or more segments of the global digital broadcast radio service packet link mapping table. The one or more segments of the global digital broadcast radio service packet link mapping table indicate one or more packets of multiple global digital broadcast radio services transmitted by ATSC.

[0255] According to an embodiment, the one or more segments of the service packet link mapping table are one or more segments of the digital audio broadcasting service packet link mapping table. The one or more segments of the digital audio broadcasting service packet link mapping table indicate one or more packets of multiple digital audio broadcasting services transmitted by ATSC.

[0256] In an embodiment, the one or more further ATSC link layer protocol data packets are two or more further ATSC link layer protocol data packets, wherein the one or more fragments of the service packet link mapping table are two or more fragments.

[0257] Two or more further ATSC link layer protocol data packets include two or more fragments of the service packet link mapping table.

[0258] According to an embodiment, one or more segments of the service group link mapping table associate two or more of the plurality of services with at least one of two or more categories and / or with at least one of two or more attributes.

[0259] In an embodiment, one or more segments of the service group link mapping table indicate one or more groups, including: language-based grouping, and / or program type-based grouping, and / or region-based grouping, and / or country-of-origin-based grouping, and / or target audience age group-based grouping, and / or broadcast network-based grouping, and / or data application type-based grouping.

[0260] According to an embodiment, one or more fragments of the service link mapping table include an indication of a physical layer pipe and / or an indication of an ATSC link layer protocol data packet, and the indication of the physical layer pipe and the indication of the ATSC link layer protocol data packet include one of the one or more fragments of the service packet link mapping table.

[0261] In an embodiment, one or more other ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets include one or more table fragments for each of the one or more tables, wherein each of the one or more table fragments may, for example, include metadata supporting selection of a service, and / or may, for example, include information about the content of a packet payload of each of the one or more ATSC link layer protocol data packets, and / or may, for example, include information about another table fragment in the one or more table fragments. Each of the one or more table fragments in each of the one or more tables may, for example, include table management information, the table management information including management information for the table fragment and / or for the table, wherein the table management information may, for example, include information about one or more management parameters.

[0262] exist Figure 3 In the third variation of the data stream shown, each of the multiple ATSC link layer protocol data packets includes a data packet header and a data packet payload encapsulating digital content, wherein one or more of the multiple ATSC link layer protocol data packets include content of one or more services transmitted by ATSC.

[0263] One or more other ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets include one or more table fragments for each of the one or more tables, wherein each of the one or more table fragments includes metadata supporting selection of a service, and / or includes information about the content of a packet payload of each of one or more of the plurality of ATSC link layer protocol data packets, and / or includes information about another table fragment in the one or more table fragments.

[0264] Each of the one or more table fragments of each of the one or more tables includes table management information including management information for the table fragment and / or for the table, wherein the table management information includes information about one or more management parameters.

[0265] According to an embodiment, at least one of the one or more tables may, for example, include two or more table fragments.Information on at least one of the one or more management parameters exists in each of the two or more table fragments.

[0266] In an embodiment, the one or more management parameters include a plurality of management parameters. Information of each management parameter in the plurality of management parameters exists in each of the two or more table fragments.

[0267] According to an embodiment, at least one of the one or more table fragments of a table of the one or more tables may, for example, include a value of a data revision parameter of the table as information of one of the one or more management parameters.

[0268] In an embodiment, each of at least one table fragment of one or more table fragments of a table in one or more tables may, for example, include a value of a fragment data revision parameter of the one table fragment in the at least one table fragment, the value serving as information about another management parameter in the one or more management parameters.

[0269] According to an embodiment, a body portion of at least one of the one or more table fragments of at least one of the one or more tables is compressed.

[0270] In an embodiment, each of the one or more table fragments of the at least one table may include, for example, a compression value indicating whether a body portion of the table fragment is compressed, the compression value being information of another management parameter of the one or more management parameters.

[0271] According to an embodiment, each of at least one table segment in one or more table segments of a table in one or more tables may, for example, include revision table information for the table. The revision table information for the table indicates a value of a segment data revision parameter for each of the one or more table segments in the table in an ATSC transmission.

[0272] In an embodiment, the revised table information for the table indicates the location of each of the one or more table segments of the table in the ATSC transmission.

[0273] According to an embodiment, the revised table information for the table indicates the location of each of the one or more table segments of the table in the ATSC transmission by indicating the physical layer pipe including the table segment and / or by indicating the ATSC link layer protocol data packet including the table segment.

[0274] In an embodiment, the one or more table fragments of each of the one or more tables include one or more fragments of a service link mapping table.

[0275] According to an embodiment, the one or more table fragments of each of the one or more tables include one or more fragments of a service packet link mapping table.

[0276] In an embodiment, the one or more table fragments of each of the one or more tables include one or more fragments of a logo / icon table (LIT), which includes information of one or more versions of a logo or icon; and / or, the one or more table fragments of each of the one or more tables include one or more fragments of a logo / icon variant (LIV), which includes image data of a version of a logo or icon.

[0277] In addition, a system is provided, comprising an apparatus for generating a plurality of ATSC link layer protocol packets according to any of the above embodiments; and a decoding apparatus, wherein the decoding apparatus is configured to receive and decode the plurality of ATSC link layer protocol packets according to any of the above embodiments.

[0278] Specific embodiments of the present invention are described below.

[0279] Some embodiments involve novel and inventive extensions of ATSC.

[0280] First, DCP packet encapsulation is described.

[0281] This section specifies the format of ALP packets when the input consists of DCP packets[3], i.e. when the packet_type field in the base header is equal to '101'. For example, DCP packets are used to transport DRM-Radio[4] MDI streams[5].

[0282] The DCP packet will now be described.

[0283] DCP, the standardized Distribution and Communication Protocol, supports the one-way transmission of streaming information in the form of a sequence of DCP packets.

[0284] Each DCP packet represents a segment of streaming content and consists of either an Application Framing (AF) packet or a Protection, Fragmentation, and Transport (PFT) fragment (which encapsulates AF packets to provide additional functionality). The optional PFT layer enhances the AF layer by adding forward error correction capabilities and addressing and fragmentation mechanisms, for example to address limitations of underlying transport protocols such as UDP / IP. The Application PFT layer typically splits a single AF packet into a series of PFT fragments, where a single AF packet or each PFT fragment is referred to as an independent DCP packet in this specification.

[0285] Next, the ALP packet structure (used for DCP packet encapsulation) is described.

[0286] When encapsulating DCP data packets, the overall structure of the ALP data packet header is as follows: Figure 5 .2 and Figure 5 .3 or Figure 5 .4 or Figure 5 .5 and are described in Table 5.1 and Table 5.2 in conjunction with Table 5.4, Table 5.5 or Table 5.6 and in the text following the corresponding table in [1]. The following conditions apply:

[0287] ALP packets that carry a sequence of DCP packets representing a single streaming content should be identified by a single unique sub-stream identifier (SID). The SID value is carried in the header extension of each ALP packet. Therefore, when the payload_configuration (PC) bit is set to '0', the mode header_mode (HM) bit of the basic header of the ALP packet should be set to '1' to indicate the presence of an additional header. The sub-stream identifier flag (SIF) in the additional header should also be set to '1' to indicate the presence of an extended header carrying the SID. When the PC bit is set to '1', both states of the segmentation_concatenation (S / C) bit indicate the presence of an additional header, and the SIF bit in the additional header should be set to '1' to indicate the presence of an extended header carrying the SID. In each case, the first 8 bits of the header extension of the ALP packet are the SID value, which ranges from 0 to 255, as described in section 5.1.3.1 of [1], to indicate the specific ALP sub-flow associated with the packet.

[0288] Therefore, the overall structure of the ALP packet header carrying the DCP packet consists of at least 4 bytes: 2 bytes for the base header, 1 byte for the additional header, and 1 byte for the extended header carrying the SID value. If the Header Extension Flag (HEF) bit in the additional header is set to '1', the extended header can be extended by a variable number of additional bytes.

[0289] Now, DRM Radio MDI, an application based on DCP packets, will be described.

[0290] Radio services in ATSC 3.0 shall be based on the DRM global digital radio (DRM) standard[4] and delivered via the MDI stream format (DRM Multiplex Distribution Interface)[5], which itself is based on the DCP standard[3]. A DRM radio MDI stream carries from one to four audio / multimedia DRM radio services and all their directly related signaling.

[0291] Each DRM radio MDI stream is transmitted as a sequence of DCP packets. The ALP packets carrying the DCP packets representing a single DRM radio MDI stream are identified by a unique substream identifier (SID).

[0292] Multiple consecutive DCP packets carrying the same MDI stream may be encapsulated into a single ALP packet using the concatenation method described in section 5.1.2.3 of [1]. Conversely, a single DCP packet carrying an MDI stream may be encapsulated into multiple ALP packets using the segmentation method described in section 5.1.2.2 of [1]. Due to the efficiency of the underlying DRM radio signaling and data encapsulation mechanisms, further data compression or header compression is not beneficial and is not applied.

[0293] The following describes link layer signaling according to an embodiment. A general overview of link layer signaling in ATSC is given in document [1], section 7.

[0294] First, according to some embodiments, a Link Mapping Table for DRM-Radio (LMT-R) is described.

[0295] The generic LMT-R layout for DCP-based DRM radio services is described. The generic LMT format for IP-based services is defined in clause 7.1.1 of [1].

[0296] The DRM Link Mapping Table for Radio (LMT-R) provides a list of DRM digital radio services transmitted in ATSC 3.0 broadcasts, along with descriptions of these services and instructions for finding the locations of the DRM radio MDI streams carrying these services in the ATSC 3.0 multiplex. It provides sufficient information to build a service guide for all DRM digital radio services, and it can reference station identifiers and service identifiers to support visual service discovery and selection. It supports grouping DRM services by category and attributes, allowing for easier discovery, selection, or filtering of broadcast services grouped by broadcaster, language, region, country of origin, program type, multimedia application type, target age group, or other methods.

[0297] The LMT-R structure reserves space for the inclusion of text labels for presentation in service guides and for other purposes derived from the information carried in the LMT-R segments. Such labels should be included to allow users to identify specific DRM radio services and, optionally, DRM multiplexes to facilitate easier service selection. In each case, label characters should be encoded in the UCS code space and identified by 1 to 4 bytes, following the UTF-8 encoding form and the UTF-8 encoding scheme defined in ISO / IEC 10646 [9]. The number of bytes defined in UTF-8 used to encode labels should be limited to 64, and the two's complement representation of characters in labels should be limited to 32 characters. Left-to-right and right-to-left characters and bidirectional text segments are permitted, but only through the use of the Unicode control characters LRI, RLI and PDI. The base direction of a given label and local direction changes within a label should be encoded according to the DRM service label specification, including the first byte of the string as a leading text control field when necessary (see reference [4]). The supported UCS code point set (character set) varies depending on the target market (see DRM region profiles

[11] ).

[0298] LMT-R should be transmitted in segments, with each segment occupying a separate ALP packet. LMT-R segments may be used for a variety of reasons, including supporting multiplexing of content from multiple sources: multiple independent LMT-R segments may exist, for example to provide signaling capacity for more DRM radio services than can be listed in a single segment, or to carry service discovery information for each radio broadcast network. LMT-R segments may be carried in multiple PLPs. All LMT-R segments together describe all available DRM-radio services carried in the ATSC 3.0 transmission. Each MDI stream carrying a DRM radio service should be described in only a single LMT-R segment. The LMT-R segment describing an MDI stream may be carried in the same PLP as the MDI stream itself, or in a different PLP.

[0299] Among the LMT-R segments carried in a given PLP, the LMT-R segment with the lowest index value shall carry a table indicating the location and revision status of all segments, including those carried outside the current PLP.

[0300] If a PLP carries at least one LMT-R segment, the value of the associated L1D_plp_lls_flag shall be set to

[0301] '1' indicates that it carries LLS (see section 9.3.4 of A / 322[1]).

[0302] LMT-R segments shall be carried in separate ALP packets; only the ALP single packet header shall be applied. LMT-R segments shall not be fragmented or concatenated, and their payload shall be limited to 65535 bytes before any compression is applied. Therefore, in the header of the ALP packet carrying an LMT-R segment, PC shall be set to '0' and HM shall be set to '1'. The body of the LMT-R segment shall be compressed using gzip ([8]), but compression shall only be applied if the overall size of the segment is reduced after compression.

[0303] All segments constituting a complete LMT-R shall be repeated at least once per second; however, in no case shall the repetition rate be less than once every 5 seconds. When LMT-R is present, it shall be broadcast at the same rate as SLT.

[0304] When carrying an LMT-R segment, the packet_type value of the basic header of the ALP packet shall be '100' (link layer signaling packet). The values ​​of the additional headers of the ALP packet carrying the LMT-R segment, as defined in Table 5.11, shall be as described in Table 7.6. The syntax of the LMT-R segment itself shall be as described in Table 7.7, and the semantics of the LMT-R segment shall be as described in the text following Table 7.7.

[0305] Table 7.6 Additional header values ​​for ALP packets for LMT-R

[0306]

[0307] Table 7.7 Syntax for DRM Radio Link Mapping Table (LMT-R) fragment

[0308]

[0309]

[0310]

[0311]

[0312] lmt-r_version – The version of the DRM Radio Link Mapping Table protocol in use. For DRM Radio Link Mapping Table fragments constructed according to the specifications of this document, its value shall be '0'. If an entity processing an LMT-R fragment does not understand an lmt-r_version value other than '0', then such LMT-R fragments indicating an ununderstood lmt-r_version value other than '0' shall be ignored.

[0313] drm_ewf_active_flag – When set to '1', indicates that the DRM Emergency Alert feature is enabled for at least one DRM radio service in the ATSC 3.0 transmission.

[0314] lmt-r_data_revision – shall indicate the current revision number of the LMT-R table. Its value shall remain consistent across all LMT-R segments carried in an ATSC transmission. When the value of the parameter fragment_data_revision changes in at least one LMT-R segment representing the LMT-R table, or when the total number of LMT-R segments indicated by the parameter num_fragments_minus1 changes, the value of lmt-r_data_revision for all LMT-R segments shall be incremented by 1, cycling from a value of '15' to a value of '0'. If necessary, changes to the LMT-R table shall be delayed to ensure that each value of lmt-r_data_revision is stable for at least 5 seconds.

[0315] num_fragments_minus1 – Its value shall be one less than the total number of LMT-R fragments in the entire LMT-R table containing the same lmt-r_version value. Its value range is 0 to 2047 (decimal), corresponding to 1 to 2048 LMT-R fragments.

[0316] fragment_index – shall indicate the unique index value of the current LMT-R fragment in the sequence of LMT-R fragments representing the complete LMT-R table. The LMT-R table shall consist of a unique fragment corresponding to each fragment_index value from 0 to num_fragments_minus1.

[0317] fragment_data_revision – shall indicate the current revision of the data carried by the LMT-R fragment.

[0318] When any data between the 'LMT-R fragment "payload part" start' marker and the 'LMT-R fragment "body part" end' marker changes, its fragment_data_revision value shall be incremented by 1, looping from "15" to "0".

[0319] fragment_extension_flag – When set to '1', it shall indicate that the fragment_extension_size_minus1 and fragment_extension fields are present in this LMT-R fragment, otherwise its value shall be set to '0'.

[0320] fragment_compression_flag – When set to '1', the fragment it carries shall be compressed, from the 'LMT-R fragment "body part" start' marker to the 'LMT-R fragment "body part" end' marker, using gzip[8] compression; otherwise, the fragment is uncompressed. Compression shall only be applied if it results in a reduction in the size of the fragment, and shall be applied in that case.

[0321] revision_table_use_flag – When set to '1', this flag indicates that this LMT-R segment carries a revision table. This revision table is used to simplify LMT-R change management. If all LMT-R segments are contained in the same PLP, the use of the revision table is optional. If the LMT-R segments are contained in multiple PLPs, the LMT-R segment with the lowest fragment_index in each PLP must carry the revision table, and the use of the revision table by other LMT-R segments is optional.

[0322] rt_fragment_plp_id – A value used to identify the PLP carrying the LMT-R fragment, ranging from 0 to 63 (decimal).

[0323] rt_fragment_data_revision – Shall be associated with the value of the fragment_data_revision parameter of the LMT-R fragment within the PLP identified by the rt_fragment_plp_id value.

[0324] rt_byte_alignment – ​​should be used to ensure byte alignment of the revision table. Byte alignment should be applied when the revision table contains an odd number (12-bit) of entries.

[0325] servicegrouping_use_flag – When set to '1', it shall indicate that the ATSC transport supports the service grouping mechanism (described below). Therefore, each DRM radio service in the LMT-R segment may specify a list of service grouping references. The list contains 0 to 255 references per DRM radio service, with the number defined by the parameter num_servicegrouping_references. If set to '0', the DRM radio service specified in this LMT-R segment does not use the service grouping mechanism.

[0326] lmt-r-sg_plp_id – shall be the identifier of the segment with the lowest fragment_index value (usually

[0327] The value of the PLP of the LMT-R-SG segment with '0') ranges from 0 to 63 (decimal).

[0328] lmt-r-sg_revision – shall indicate the required revision of the LMT-R-SG table carrying the service allocation configuration data, as defined by the value of its lmt-r-sg_data_revision parameter. Service group references in this LMT-R fragment are valid only if this value is equal to the revision value used in the LMT-R-SG, and are only processed under this condition. Its value range is 0 to 255 (decimal).

[0329] single_logo_substream_flag – When set to '1', it shall indicate that all LIT segments describing logos referenced (via MDI stream or DRM service) in this LMT-R segment are carried in the same PLP; when the value is '0', it shall indicate that a separate PLP is specified for each LIT segment describing a logo referenced in this LMT-R segment, or that this LMT-R segment does not reference any logo.

[0330] single_logo_plp_id – should be the value that identifies the PLP that carries the LIT segments that describe all logo definitions in this LMT-R segment, and its value range is 0 to 63 (decimal).

[0331] num_mdi_streams_minus1 – Its value shall be one less than the number of MDI streams described in the carried LMT-R table fragment, and its value range shall be 0 to 255 (decimal).

[0332] mux_label_flag – when set to '1', shall indicate that the MDI stream associated with it provides the multiplexing flag; otherwise its value shall be set to '1'.

[0333] mux_logo_flag – when set to '1', shall indicate that the MDI stream associated with it provides the multiplexing flag; otherwise its value shall be set to '0'.

[0334] mux_plp_id – shall be a value identifying the PLP carrying the associated MDI stream content, in the range 0 to 63 (decimal).

[0335] mux_alp_sid – shall be a value identifying the substream in the ALP packet stream associated with this MDI stream that carries the content of this MDI stream, and shall have a value in the range of 0 to 255 (decimal). mux_label_size_minus1 – shall be present when multiplex_label_flag is set to '1', and shall indicate the number of bytes carried by the mux_label field minus one. The number of bytes shall range from 1 to 64 (decimal), with the corresponding values ​​being represented by numbers from 0 to 63, respectively.

[0336] mux_label – present when multiplex_label_flag is set to '1', shall indicate the text label of the DRM multiplex (MDI stream) with which it is associated. It shall consist of a UTF-8 byte string, with a maximum of 64 bytes sent to generate a maximum of 32 displayable characters, in accordance with ISO / IEC 10646 [9]. See section 6.7, "Display of Service Labels and Text Messages," of the DRM System Specification [4].

[0337] logo_id – shall be a decimal numeric identifier between 1 and 65535 that uniquely identifies a logo that visually represents the multiplex or business entity with which it is associated, from the set of available broadcast logos. The value 0 shall mean “no logo / icon” and no actual logo / icon shall be assigned.

[0338] logo_plp_id – present when single_logo_substream_flag is set to '1' and shall be a value identifying the PLP that carries the LIT segment describing its associated logo, in the range 0 to 63 (decimal).

[0339] num_services_minus1 – its value shall be one less than the number of services carried by the DRM radio multiplex (ie MDI stream) associated with this value, and its value range shall be 0 to 3.

[0340] service_id – shall be the identifier defined in Section 6.3.4 of the Service Parameters and Appendix T of the DRM System Specification [4].

[0341] ca_flag_audio – shall be set to '1' to indicate that conditional access (CA) is applied to the audio carried by the associated service ID; a value of '0' shall indicate that CA is not applied to the audio carried by the service ID. See Section 6.3.4 of the DRM System Specification [4] for service parameters.

[0342] ca_flag_data – shall be set to '1' to indicate that conditional access applies to the data content carried by the associated service ID; a value of '0' shall indicate that conditional access does not apply to the data carried by the service ID. See Section 6.3.4 of the DRM System Specification [4] for service parameters.

[0343] audio / data_flag – shall be set to '0' to indicate that the associated service is audio; shall be set to '1' to indicate that the associated service is data. See Section 6.3.4 of the DRM System Specification [4] for service parameters.

[0344] service_descriptor – shall indicate the audio service type or data application identifier, as defined in Section 6.3.4 Service Parameters of the DRM System Specification [4], and the program type codes in Table 19.

[0345] audio_config – shall include the audio information data specified in the Audio Information Data Entity-Type 9 of section 6.4.3.10 of the DRM System Specification [4], encoded according to the order, field sizes and definitions specified in that section, with the exception of the following: Short ID and Stream ID at the beginning and Codec Specific Config at the end, which shall be omitted.

[0346] app_id – shall indicate the application identifier of the data service defined in the DRM Data Application Directory [6].

[0347] app_domain – shall indicate the application domain of the data service defined in Section 4.3.1 of the DRM Data Application Directory [6] and in Table 2 Application Domain.

[0348] language_short – shall indicate the language of the target audience as defined in the service parameters, Table 18, Language Codes, section 6.3.4 of the DRM System Specification [4].

[0349] language-country_flag – when set to '1' shall indicate the presence of the language_long and country_of_origin fields; otherwise it shall be set to '0'.

[0350] language_long – shall indicate the language of the target audience of the service according to the definition of language_code in section 6.4.3.13 Language and Country Data Entity-Type 12 of the DRM System Specification [4].

[0351] country_of_origin – shall indicate the country of origin of the business (where the studio is located) according to the definition of country_code in the Language and Country Data Entity-Type 12 in section 6.4.3.13 of the DRM System Specification [4] [1].

[0352] num_servicegrouping_references – As part of the service grouping mechanism enabled (i.e. when servicegrouping_use_flag is set to '1'), shall indicate the number of references to the category / attribute combination to which the associated DRM radio service belongs, in the range 0 to 255. Although a DRM radio service may be associated with multiple attributes under the same category, each category ID and attribute ID combination in the list must be unique.

[0353] category_id – shall carry an ID value identifying the category referenced by the current service group. Available category IDs are specified in the Service Group Link Mapping Table (LMT-R-SG) (see below).

[0354] property_id – This field shall carry the ID value of the attribute that the current service group references in the category specified by the category_id value. The attribute IDs available for each category are specified in the service group LMT-R-SG table (see below).

[0355] service_logo_flag – When set to '1', it shall indicate that the associated DRM radio service provides a service logo; otherwise, its value shall be set to '0'. The description of the logo-related parameters logo_id, logo_plp_id and logo_alp_sid can be found in Table 7.7 of the semantics section above.

[0356] service_extension_flag – when set to '1', shall indicate that the service_extension field associated with the service is carried in the LMT-R segment containing the service; otherwise, shall be set to '0'.

[0357] service_label_size_minus1 – shall indicate the number of bytes carried by the service_label field minus 1. The range of bytes is 1 to 64 (decimal), and the corresponding value shall be 0 to 63.

[0358] service_label – This shall represent the textual label of the associated service. It shall be a UTF-8 byte string, with a maximum of 64 bytes to generate a maximum of 32 displayable characters, in accordance with ISO / IEC 10646. [9] See Section 6.7 of the DRM System Specification [4] for presentation of service labels and text messages.

[0359] service_extension_size_minus1 – shall indicate the number of bytes included in the associated service_extension field, ranging from 0 to 255 (decimal), corresponding to the service_extension field carrying 1 to 256 bytes respectively.

[0360] service_extension – shall be a field whose length is one more than the number of data bytes indicated in the service_extension_size_minus1 field and is relevant to the service it is associated with. The content of this field is left for future definition and decoders that do not understand how to interpret it shall ignore it.

[0361] fragment_extension_size_minus1 – shall indicate the number of bytes included in the associated fragment_extension field, and shall have a value range of 0 to 255 (decimal), corresponding to the fragment_extension field carrying 1 to 256 bytes, respectively.

[0362] fragment_extension – shall be a field whose length is one more than the number of data bytes indicated in the fragment_extension_size_minus1 field and is associated with the LMT-R fragment it is in. The content of this field is left for future definition and decoders that do not understand how to parse it shall ignore it.

[0363] fragment_crc – shall be a 16-bit cyclic redundancy check (CRC-16) value calculated according to [7]. Its value shall be calculated based on the complete content of the LMT-R fragment containing the value, i.e., the data block from the lmt-r_version field value to the fragment_crc field value.

[0364] The following describes a DRM Radio Traffic Packet Link Mapping Table (LMT-R-SG) according to some embodiments.

[0365] This document describes the generic LMT format for the service grouping mechanism used to transport configuration data to implement DRM radio services. This format is denoted as LMT-R-SG. The generic LMT format for IP-based services is defined in clause 7.1.1, while the generic LMT format for DCP-based DRM radio services is defined in clause 7.1.3.

[0366] The service grouping mechanism allows users to easily discover, find and select services from a long list of potential DRM radio services based on categories and attributes.

[0367] The configuration data carried in the LMT-R-SG implements the service grouping mechanism for DRM radio services by defining the categories available in the current ATSC multiplex and the attributes under each category. Categories allow services to be grouped according to a variety of independent characteristics. Examples of categories include language, broadcast network, data application type, program type, region, country of origin, target audience age group, etc. The attributes (i.e., options) that a user can select in a given category, such as the languages ​​that can be selected in the "language" category, are collectively referred to as the attribute set for that particular category. The collection of all DRM radio services with the same attribute values ​​(such as all "English" services in the "language" category) is called a service group. Figure 4 Shows the components of the business grouping mechanism.

[0368] Specifically, Figure 4 The components of the service grouping mechanism are shown: categories and attributes.

[0369] The service grouping mechanism enables the receiver to present the list of available DRM radio services to the user in a more structured and convenient form. By default, the list may be sorted alphabetically only, allowing for faster and more accurate service identification and selection. The metadata provided by the service grouping mechanism allows the receiver to group and / or filter services. Simple receivers or receivers with smaller screens may display the available categories in the following way: first the available categories are displayed, then the set of available attributes corresponding to the selected category is displayed, and finally the service group corresponding to the attribute selected by the user is displayed. Each step is displayed on a separate screen (see Figure 5 More advanced receivers, which may be equipped with larger screen real estate, are able to present a combined view to the user, ensuring that all available services are always available for selection, but visually grouping the services using attributes as intermediate headers (see Figure 6 ). Finally, the receiver can implement a filtering mechanism based on the service grouping information, allowing the user to combine one or more parameters across multiple categories to quickly reduce the generated service list to services that meet all user-selected criteria simultaneously. In the latter use case, selecting multiple attributes from the attribute set should be considered an "OR" combination, while attributes activated in different categories should be considered an "AND" combination. With this approach, the generated service list only includes services that meet at least one selected attribute in each activated category (see Figure 7 ).

[0370] Specifically, Figure 5 The service grouping mechanism is shown, especially an example of service grouping achieved through multi-screen sequence.

[0371] Figure 6Shown is a service grouping mechanism: an example of single-screen service grouping achieved through intermediate attribute titles.

[0372] Figure 7 An example of a service grouping mechanism: service filtering is shown.

[0373] Each DRM radio service may declare itself as having one or more attributes from one or more available categories as part of the service description in the LMT-R message (or may not use the service grouping mechanism at all).

[0374] In the case of DRM radio service grouping, DRM radio services that do not carry a reference to a specific category of service grouping should still be listed / provided, for example as members of the "undefined / other" service grouping. However, in the case of DRM radio service filtering, these DRM radio services should be hidden if the user selects any attribute of a specific category.

[0375] A DRM radio service declares itself as having attributes of one or more service grouping categories through a list of service grouping references. Each reference consists of a category numeric ID followed by an attribute numeric ID within that category (see below). Only numeric ID values ​​for categories and attributes defined in the LMT-R-SG table in the current ATSC transmission can be used.

[0376] When the service group configuration (LMT-R-SG) changes, the consistency of the service group references is maintained by applying the revision number, that is, the service group references contained in the LMT-R table can only be resolved by the receiver through the LMT-R-SG table with the same specified revision number.

[0377] Each ATSC transmission shall contain only one LMT-R-SG table; however, the table may be carried in multiple segments. The LMT-R-SG table shall include and define all categories and attributes of each category used by all DRM radio services in that ATSC transmission. Service group references carried by the DRM radio LMT-R may only point to the category and attribute values ​​currently defined in the LMT-R-SG table. Categories and attributes that are no longer referenced by any DRM radio service shall be removed from the LMT-R-SG table so that the receiver can deduce the currently used and actually populated list of categories and attributes from the LMT-R-SG table alone.

[0378] In addition to the numeric identifiers for each category and its associated attributes, the LMT-R-SG table also carries labels for each of the two categories of features and can carry identifier references associated with each feature. These labels and identifier references provide the raw material for receivers to construct service guidance and selection systems, which can range from the simplest character-based schemes to the most complex graphically guided navigation systems. Labels for all categories and their associated attributes are mandatory, while identifier references for categories and attributes are optional.

[0379] Categories and attributes are encoded as 5-bit and 11-bit binary enumerations, respectively, collectively referred to as service group references. Therefore, a system can simultaneously define up to 32 different categories, and each category can contain up to 2048 different attributes. Numeric IDs for attributes can be freely assigned (as long as each attribute ID is defined only once within the same category). If attributes within a category are listed, they should be listed in ascending order by attribute ID value (even if attributes within that category are scattered across multiple LMT-R-SG segments). For categories, numeric ID values ​​0 to 15 are reserved for standardized, predefined category types, while numeric ID values ​​16 to 31 can be freely assigned to additional category types (as long as each category ID value is defined only once in the LMT-R-SG table). The predefined category ID values ​​are defined in Table 7.8; they cover the most common category types and allow receivers to easily use localized labels or pre-installed icons. Reference decoders that are unaware of or unconcerned with the specific meaning of the predefined category ID values ​​should treat them the same as any freely assigned category ID value.

[0380] Table 7.8 Service Grouping Mechanism - Category ID Value

[0381]

[0382] Space is reserved in the LMT-R-SG table structure for text labels to be presented in service guides and for other purposes derived from the information carried in the LMT-R-SG segments. Such labels should be included so that users can identify specific categories and attributes. The same encoding and rules used for labels carried in LMT-R segments apply to labels carried in LMT-R-SG segments (see Section 7.1.3).

[0383] A segment can be composed in two ways depending on which of the three information components in the overall LMT-R-SG table it carries. The three information components are: (1) the available categories, identified by a numerical category ID, along with the category's label data and subcategory identification (if any); (2) the available attributes for each category, identified by a numerical attribute ID associated with the relevant category ID, along with the attribute's label data and attribute identification (if any); and (3) optional segment extensions (if any). Each LMT-R-SG segment should begin with a segment management part and end with a segment CRC. Between the segment management part and the segment CRC, the segment can include a category definition (1), followed by the relevant attribute definition (2) and an optional segment extension (3); or only an attribute definition (2) and an optional segment extension (3).

[0384] Each class shall be explicitly defined once in the class definition section (1), and each attribute shall be explicitly defined once in the attribute definition section (2) associated with a single class in the LMT-R-SG table.

[0385] LMT-R-SG table segments shall not be fragmented or concatenated, and their payload shall be limited to 65535 bytes before any compression is applied. Therefore, in the header of the ALP packet carrying an LMT-R-SG segment, PC shall be set to '0' and HM shall be set to '1', which means that a single packet appendage header shall be applied for each ALP packet carrying an LMT-R-SG segment. The body of the LMT-R-SG segment shall be compressed using gzip[8], but compression shall only be applied if the overall size of the segment is reduced after compression.

[0386] All segments that make up the complete LMT-R-SG table shall be repeated at least once per second; however, the repetition frequency shall not be less than once every 5 seconds. If an LMT-R-SG table exists, its broadcast frequency shall be consistent with the SLT. Among the LMT-R-SG segments carried in a given PLP, the LMT-R-SG segment with the lowest index value shall carry a table indicating the location and revision status of all segments, including those carried outside the current PLP.

[0387] When carrying an LMT-R-SG segment, the packet_type value of the basic ALP packet header shall be '100' (Link Layer Signaling Packet). The ALP single packet header shall apply only to packets carrying LMT-R-SG segments. The values ​​of the additional headers of the ALP packet carrying the LMT-R-SG segment, as defined in Table 5.11, shall be as shown in Table 7.9. The syntax of the LMT-R-SG segment itself shall be as shown in Table 7.10, and its semantics shall be as described in the text following Table 7.10.

[0388] Table 7.9 Additional header values ​​for LMT-R-SG ALP packets

[0389]

[0390] Table 7.10 Syntax of DRM Radio Service Packet Link Mapping Table (LMT-R-SG) fragment

[0391]

[0392]

[0393] lmt-r-sg_version – The version of the DRM Radio Service Packet Mechanism Link Mapping Table protocol currently in use. For DRM Radio LMT-R-SG segments constructed according to the specifications of this document, its value shall be '0'. If the entity processing the LMT-R-SG segment does not understand an lmt-r-sg_version value other than '0', then the LMT-R-SG segment indicating a non-understood lmt-r-sg_version value other than '0' shall be ignored.

[0394] lmt-r-sg_data_revision – shall indicate the current revision number of the LMT-R-SG table. Its format and description are identical to the above lmt-r_data_revision parameter.

[0395] num_fragments_minus1 – See above for parameter format and description.

[0396] fragment_index – The parameter format and description are as above.

[0397] fragment_data_revision – The parameter format and description are as above.

[0398] fragment_extension_flag – The parameter format and description are as above.

[0399] fragment_compression_flag – The parameter format and description are as above.

[0400] revision_table_use_flag – When set to '1', this flag indicates that this LMT-R-SG segment carries a revision table. This revision table simplifies change management for the LMT-R-SG. If all LMT-R-SG segments are carried in the same PLP, the use of the revision table is optional. If the LMT-R-SG segments are carried in multiple PLPs, the LMT-R-SG segment with the lowest fragment_index in each PLP must carry the revision table. The use of the revision table for other LMT-R-SG segments is optional.

[0401] rt_fragment_plp_id – This shall be the value that identifies the PLP that carries the LMT-R-SG segment. Its value range is 0 to 63 (decimal).

[0402] rt_fragment_data_revision – shall be the value of the fragment_data_revision parameter of the LMT-R-SG fragment.

[0403] rt_byte_alignment – ​​This should be used to ensure byte alignment of the revision table. When the revision table contains an odd number (12 bits) of entries, byte alignment should be performed.

[0404] single_logo_substream_flag – The parameter format and description are as above.

[0405] single_logo_plp_id – The parameter format and description are as above.

[0406] category_definition_flag – When set to '1', shall indicate that this LMT-R-SG segment includes at least one category definition; otherwise shall be set to '0'.

[0407] num_categories_minus1 – Its value shall be one less than the number of category definitions described by the LMT-R-SG segment carrying it. Its value range is 0 to 31 (decimal).

[0408] category_id – should be the category ID value of the category being defined. Its value range is 0 to 31 (decimal).

[0409] category_logo_flag - when set to '1', shall indicate that a category logo is provided; otherwise its value shall be set to '0'.

[0410] category_label_size_minus1 – The format and description are identical to the mux_label_size_minus1 parameter above.

[0411] category_label – The format and description are the same as the mux_label parameter above.

[0412] logo_id – The parameter format and description are as above.

[0413] logo_plp_id – The parameter format and description are as above.

[0414] num_category_refs_minus1 – Its value shall be one less than the number of categories of any attribute defined in the LMT-R-SG segment carrying this value. Its value range is 0 to 31 (decimal).

[0415] category_ref – The category ID value defined in the CategoryReference section of the category reference to which the attribute to be defined in this section belongs. Its value range is 0 to 31 (decimal).

[0416] num_properties_minus1 – Its value shall be one less than the number of property definitions described in the LMT-R-SG segment carrying the context class ID. Its value range is 0 to 31 (decimal).

[0417] property_id – This shall be the property ID value of the property defined in this section and belonging to the category defined by the associated category_ref value. Its value range is 0 to 2047 (decimal).

[0418] property_logo_flag – when set to '1' shall indicate that a property logo is provided; otherwise its value shall be set to '0'.

[0419] property_label_size_minus1 – The format and description are identical to the mux_label_size_minus1 parameter above.

[0420] property_label – The format and description are the same as the mux_label parameter above.

[0421] logo_id – The parameter format and description are as above.

[0422] logo_plp_id – The parameter format and description are as above.

[0423] fragment_extension_size_minus1 – The parameter format and description are as above.

[0424] fragment_extension – The parameter format and description are as above.

[0425] fragment_crc – The parameter format and description are as above.

[0426] Although certain aspects are described in the context of an apparatus, it is apparent that these aspects also represent descriptions of corresponding methods, where a block or apparatus corresponds to a method step or feature of a method step. Similarly, aspects described in the context of a method step also represent descriptions of functional blocks, components, or features of the corresponding apparatus. Some or all of the method steps may be performed by (or using) a hardware device, such as a microprocessor, a programmable computer, or an electronic circuit. In certain embodiments, one or more key method steps may be performed by such a device.

[0427] Depending on the specific implementation requirements, embodiments of the present invention may be implemented in hardware, or in software, or at least partially in hardware, or at least partially in software. Such implementation may be accomplished via a digital storage medium, such as a floppy disk, a digital optical disc (DVD), a Blu-ray disc, a compact disc (CD), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable read-only memory (EEPROM), or a flash memory, having electronically readable control signals stored thereon and cooperating (or capable of cooperating) with a programmable computer system to perform the corresponding method. Thus, the digital storage medium may be computer-readable.

[0428] Some embodiments according to the invention comprise a data carrier having electronically readable control signals, which are capable of cooperating with a programmable computer system, such that the system performs one of the methods described herein.

[0429] Generally speaking, the embodiments of the present invention can be implemented as a computer program product comprising a program code, which can be used to perform one of the methods when the program code is run on a computer. The program code can be stored on a machine-readable carrier, for example.

[0430] Other embodiments comprise the computer program for performing one of the methods described above, the program being stored on a machine readable carrier.

[0431] In other words, an embodiment of the inventive method is, therefore, a computer program having a program code for performing one of the methods described in this description when the program runs on a computer.

[0432] A further embodiment of the method according to the invention is therefore a data carrier (or a digital storage medium or a computer-readable medium) on which is recorded the computer program for performing one of the methods described herein. The data carrier, digital storage medium or recorded medium is generally tangible and / or non-transitory.

[0433] A further embodiment of the method according to the invention is therefore a data stream or a sequence of signals representing the computer program for performing one of the methods described herein. The data stream or the sequence of signals can be configured, for example, to be transmitted via a data communication connection (for example via the Internet).

[0434] A further embodiment comprises a processing means, for example a computer or a programmable logic device, configured or adapted to perform one of the methods described herein.

[0435] Another embodiment comprises a computer having installed thereon the computer program for performing one of the methods described above.

[0436] Another embodiment of the present invention includes an apparatus or system configured to transmit (e.g., electronically or optically) a computer program for performing one of the above methods to a recipient. The recipient may be, for example, a computer, a mobile device, a storage device, etc. The apparatus or system may include, for example, a file server for transmitting the computer program to the recipient.

[0437] In some embodiments, a programmable logic device (e.g., a field programmable gate array) may be used to perform some or all of the functions of the above method. In some embodiments, the field programmable gate array may be used in conjunction with a microprocessor to perform one of the above methods. Generally, the method is preferably performed by any hardware device.

[0438] The apparatus described herein may be implemented using hardware apparatuses, or using computers, or using a combination of hardware apparatuses and computers.

[0439] The methods described herein may be performed using hardware devices, or using computers, or using a combination of hardware devices and computers.

[0440] The above embodiments are intended to illustrate the principles of the present invention only. It should be understood that modifications and variations of the above arrangements and details will be apparent to those skilled in the art. Therefore, the scope of the present invention is limited only to the scope of the appended claims and is not limited to the specific details presented herein by way of description and explanation of the embodiments.

[0441] References

[0442] [1] ATSC Standard: Link Layer Protocol (A / 330), March 2022, published March 31, 2022.

[0443] [2] ATSC: “ATSC Standard: Physical Layer Protocol,” Document No. A / 322:2017, Advanced Television Systems Committee (ATSC), Washington, DC, June 6, 2017.

[0444] [3]ETSI: TS102 821, “Digital Radio Management (DRM); Distribution Communication Protocol (DCP)”, Version V1.4.1 (2012-10), European Telecommunications Standards Institute, Vallau-Sophia-Antipolis, France, October 2012.

[0445] [4]ETSI: ES201 980, “Digital Radio Management (DRM); System Specification”, Version V4.2.1 (2020-11), European Telecommunications Standards Institute, Vallau-Sophia-Antipolis, France, November 2020.

[0446] [5]ETSI: TS102 820, “Digital Radio Management (DRM); Multiplex Distribution Interface (MDI)”, Version V4.1.1 (2016-03), European Telecommunications Standards Institute, Vallau-Sophia-Antipolis, France, March 2016.

[0447] [6]ETSI: TS101 968, “Digital Radio Management (DRM) for Global Use; Catalogue of Data Applications”, European Telecommunications Standards Institute, Vallaux-Sophia-Antipolis, France, November 2020.

[0448] [7] ITU-T, “Data communications over the V.41 telephone network, Code Independent Error Control System”, 1993.

[0449] [8] IETF: “DEFLATE Compressed Data Format Specification, Version 1.3,” Internet Engineering Task Force, Reston, Virginia, May 1996, http: / / tools.ietf.org / html / rfc1951.

[0450] [9] ISO / IEC: 10646, “Information technology — Universal coded character set (UCS)”, International Organization for Standardization / International Electrotechnical Commission, Geneva, Switzerland, December 2020.

[0451]

[10] EP 1 658 689 A1, “Radio comprising a text information display for referencing other text information objects”.

[0452]

[11] ETSI: TS103 771, “Digital Radio Management (DRM); Regional Profiles”, Version V1.1.1, 2020-11, European Telecommunications Standards Institute, Vallaux-Sophia-Antipolis, France, November 2020.

Claims

1. A decoding device, comprising: An interface (110) for receiving a plurality of ATSC link layer protocol data packets, each of the plurality of ATSC link layer protocol data packets including a data packet header and a data packet payload encapsulating digital content; as well as Decoding unit (120), wherein the digital content encapsulated in the packet payload of each of the one or more ATSC link layer protocol packets in the plurality of ATSC link layer protocol packets comprises: digital broadcast content, and / or distribution and communication protocol packets or portions thereof, and / or unified speech and audio coding content or extended high-efficiency advanced audio coding content, and / or Journaline content; and The decoding unit (120) is configured to decode the packet payload of each of at least one ATSC link layer protocol data packet in the one or more ATSC link layer protocol data packets to obtain the digital content of the one ATSC link layer protocol data packet in the at least one ATSC link layer protocol data packet.

2. The device according to claim 1, in, the digital content encapsulated within the packet payloads of the ATSC link layer protocol packets in the one or more ATSC link layer protocol packets comprises digital broadcast content; and The decoding unit (120) is configured to decode the data packet payload of the ATSC link layer protocol data packet to obtain the digital broadcast content encapsulated in the data packet payload of the ATSC link layer protocol data packet.

3. The device according to claim 1, in, the digital content encapsulated within the packet payload of the ATSC link layer protocol packets in the one or more ATSC link layer protocol packets comprising distribution and communication protocol packets or portions thereof; as well as The decoding unit (120) is configured to decode the data packet payload of the ATSC link layer protocol data packet to obtain the distribution and communication protocol data packet or a portion thereof encapsulated in the data packet payload of the ATSC link layer protocol data packet.

4. The device according to claim 3, in, The distribution and communication protocol data packet or portion thereof encapsulated within the data packet payload of the ATSC link layer protocol data packet includes digital broadcast content; and The decoding unit (120) is configured to decode the data packet payload of the ATSC link layer protocol data packet to obtain the digital broadcast content included in the distribution and communication protocol data packet or part thereof encapsulated in the data packet payload of the ATSC link layer protocol data packet.

5. The device according to claim 2 or 4, in, The digital broadcasting content includes global digital broadcasting content.

6. The device according to any one of the preceding claims, in, the digital content encapsulated within the packet payloads of the ATSC link layer protocol packets in the one or more ATSC link layer protocol packets comprises unified speech and audio coding content or extended high efficiency advanced audio coding content; as well as The decoding unit (120) is configured to decode the data packet payload of the ATSC link layer protocol data packet to obtain unified voice and audio coding content or extended high-efficiency advanced audio coding content encapsulated in the data packet payload of the ATSC link layer protocol data packet.

7. The device according to any one of the preceding claims, in, the digital content encapsulated within the packet payloads of the ATSC link layer protocol packets in the one or more ATSC link layer protocol packets comprises Journaline content; and The decoding unit (120) is configured to decode the data packet payload of the ATSC link layer protocol data packet to obtain the Journaline content encapsulated in the data packet payload of the ATSC link layer protocol data packet.

8. The device according to any one of the preceding claims, in, The apparatus further comprises a renderer for providing an output, wherein the output is one or more audio output signals, or visual output, or data output, depending on the digital content encapsulated in the ATSC link layer protocol data packets.

9. The device according to claim 8, further according to claim 7, in, The renderer is configured to provide output using Journaline content.

10. The device according to any one of the preceding claims, in, One or more other ATSC link layer protocol data packets of the plurality of ATSC link layer protocol data packets include one or more fragments of a service link mapping table; wherein the one or more segments of the service link mapping table indicate one or more services transmitted by ATSC; The decoding unit (120) is configured to identify an ATSC link layer protocol data packet including content of one of the one or more services by analyzing one or more segments of the service link mapping table.

11. A decoding device comprising: An interface (110) for receiving a plurality of ATSC link layer protocol data packets, each of the plurality of ATSC link layer protocol data packets including a data packet header and a data packet payload encapsulating digital content, wherein one or more of the plurality of ATSC link layer protocol data packets include content of one or more services transmitted by ATSC; and a decoding unit (120), wherein the decoding unit (120) is configured to decode a packet payload of each of at least one ATSC link layer protocol packet in the plurality of ATSC link layer protocol packets to obtain digital content of the one ATSC link layer protocol packet in the at least one ATSC link layer protocol packet, wherein one or more other ATSC link layer protocol data packets among the plurality of ATSC link layer protocol data packets include one or more fragments of a service link mapping table; wherein the one or more segments of the service link mapping table indicate one or more services transmitted by ATSC; The decoding unit (120) is configured to identify an ATSC link layer protocol data packet including content of one of the one or more services by analyzing one or more segments of the service link mapping table.

12. The device according to claim 10 or 11, in, The one or more segments of the service link mapping table are one or more segments of a radio service link mapping table; wherein the one or more segments of the radio service link mapping table indicate one or more radio services transmitted by ATSC; The decoding unit (120) is configured to identify an ATSC link layer protocol data packet including content of one of the one or more radio services by analyzing one or more segments of the radio service link mapping table.

13. The device according to claim 12, in, One or more segments of the radio service link mapping table include metadata for one or more radio services transmitted by ATSC.

14. The device according to claim 13, in, At least some of the plurality of ATSC link layer protocol packets encapsulate a plurality of distribution and communication protocol packets comprising one or more radio services of an ATSC transmission.

15. The device according to claim 13 or 14, in, The metadata of one or more radio services includes information about a service tag, and / or information about a multiplexing tag, and / or information about a language, and / or information about a program type, and / or information about a region, and / or information about a country of origin, and / or audio configuration information, and / or a data application identifier.

16. The device according to any one of claims 12 to 15, in, The one or more segments of the radio service link mapping table are one or more segments of the global digital broadcast radio link mapping table; wherein the one or more segments of the global digital broadcast radio link mapping table indicate one or more global digital broadcast radio services transmitted by ATSC; The decoding unit (120) is configured to identify an ATSC link layer protocol data packet including content of one of the one or more global digital broadcast radio services by analyzing one or more segments of the global digital broadcast radio link mapping table.

17. The device according to claim 16, in, The one or more segments of the global digital broadcast radio link mapping table indicate an association of at least one global digital broadcast radio service of the one or more global digital broadcast radio services with the one or more global digital broadcast multiplex distribution interface flows; The decoding unit (120) is configured to identify ATSC link layer protocol data packets including global digital broadcast content according to the association.

18. The device according to claim 17, in, One or more fragments of the global digital broadcast radio link mapping table indicate the association of at least one global digital broadcast radio service of one or more global digital broadcast radio services with one or more global digital broadcast multiplex distribution interface streams by indicating a physical layer pipe identifier and / or an ATSC link layer protocol packet identifier, and by indicating at least one global digital broadcast radio service identifier of one or more global digital broadcast radio service identifiers associated with corresponding global digital broadcast multiplex distribution interface streams in the one or more global digital broadcast multiplex distribution interface streams.

19. The device according to claim 17 or 18, further according to any one of claims 13 to 15, in, The metadata of one global digital broadcast radio service among the one or more global digital broadcast radio services corresponds to metadata included in one global digital broadcast multiplex distribution interface stream among the one or more global digital broadcast multiplex distribution interface streams associated with the one or more global digital broadcast radio services.

20. The device according to any one of claims 17 to 19, in, The one or more segments of the radio service link mapping table include emergency alert information for indicating whether at least one global digital broadcast multiplex distribution interface flow of the one or more global digital broadcast multiplex distribution interface flows associated with the one or more global digital broadcast radio services indicates emergency alert information; as well as The decoding unit (120) is configured to analyze the emergency alert information to determine whether it indicates an emergency alert.

21. The device according to any one of claims 17 to 20, in, If packet payloads of two ATSC link layer protocol packets in the plurality of ATSC link layer protocol packets include global digital broadcast content of the same global digital broadcast multiplex distribution interface stream, packet headers of the two ATSC link layer protocol packets include the same substream identifier associated with the global digital broadcast multiplex distribution interface stream; and The decoding unit (120) is configured to decode the global digital broadcast multiplexing distribution interface stream by analyzing the substream identifiers of the packet headers of the two ATSC link layer protocol packets and decoding the packet payloads of the two ATSC link layer protocol packets.

22. The device according to any one of claims 12 to 15, in, The one or more segments of the radio service link mapping table are one or more segments of a digital audio broadcasting link mapping table; wherein the one or more segments of the digital audio broadcast link mapping table indicate one or more digital audio broadcast services transmitted by ATSC; The decoding unit (120) is configured to identify an ATSC link layer protocol data packet including content of one of the one or more digital audio broadcast services by analyzing one or more segments of the digital audio broadcast link mapping table.

23. The device according to claim 22, in, One or more segments of the digital audio broadcast link mapping table indicating an association of at least one digital audio broadcast service of the one or more digital audio broadcast services with one or more EDI (DAB interface encapsulation) streams; as well as The decoding unit (120) is configured to identify an ATSC link layer protocol data packet including digital audio broadcasting content according to the association.

24. The device according to any one of claims 10 to 23, in, The one or more further ATSC link layer protocol data packets are two or more further ATSC link layer protocol data packets, wherein the one or more segments are two or more segments, and wherein the one or more services are multiple services; wherein the two or more other ATSC link layer protocol data packets include two or more fragments of the service link mapping table; wherein the two or more segments of the service link mapping table indicate a plurality of services transmitted by ATSC; The decoding unit (120) is configured to identify an ATSC link layer protocol data packet including content of one of the one or more services by analyzing two or more segments of the service link mapping table.

25. The device according to any one of the preceding claims, in, One or more further ATSC link layer protocol data packets of the plurality of ATSC link layer protocol data packets include one or more segments of a service packet link mapping table, wherein the one or more segments of the service packet link mapping table indicate one or more packets of a plurality of services transmitted by the ATSC; The apparatus comprises an output interface for providing an output according to at least one of the one or more packets, wherein the output depends on at least one of a plurality of services.

26. A decoding device comprising: An interface (110) for receiving a plurality of ATSC link layer protocol data packets, each of the plurality of ATSC link layer protocol data packets including a data packet header and a data packet payload encapsulating digital content, wherein one or more of the plurality of ATSC link layer protocol data packets include content of one or more services transmitted by ATSC; and a decoding unit (120), wherein the decoding unit (120) is configured to decode a packet payload of each of at least one ATSC link layer protocol packet in the plurality of ATSC link layer protocol packets to obtain digital content of the one ATSC link layer protocol packet in the at least one ATSC link layer protocol packet, wherein one or more of the plurality of ATSC link layer protocol data packets include one or more segments of a service packet link mapping table, wherein the one or more segments of the service packet link mapping table indicate one or more packets of a plurality of services transmitted by ATSC; and The apparatus comprises an output interface for providing an output according to at least one of the one or more packets, wherein the output depends on at least one of a plurality of services.

27. The device according to claim 25 or 26, in, The one or more segments of the service packet link mapping table are one or more segments of the radio service packet link mapping table; wherein the one or more segments of the radio service packet link mapping table indicate one or more packets of a plurality of radio services transmitted by ATSC; The output interface is configured to provide an output based on at least one of the one or more packets, wherein the output depends on at least one of a plurality of radio services.

28. The device according to claim 27, in, The one or more segments of the service packet link mapping table are one or more segments of a global digital broadcast radio service packet link mapping table; wherein the one or more segments of the global digital broadcast radio service packet link mapping table indicate one or more packets of a plurality of global digital broadcast radio services transmitted by ATSC; Wherein the output interface is configured to provide an output based on at least one of the one or more packets, wherein the output is dependent on at least one of a plurality of global digital broadcast radio services.

29. The device according to claim 27, in, The one or more segments of the service packet link mapping table are one or more segments of a digital audio broadcasting service packet link mapping table; wherein the one or more segments of the digital audio broadcasting service packet link mapping table indicate one or more packets of a plurality of digital audio broadcasting services transmitted by ATSC; and The output interface is configured to provide an output based on at least one of the one or more packets, wherein the output depends on at least one of a plurality of digital audio broadcast services.

30. The device according to any one of claims 25 to 29, in, The one or more further ATSC link layer protocol data packets are two or more further ATSC link layer protocol data packets, wherein the one or more segments of the service packet link mapping table are two or more segments; Wherein, two or more ATSC link layer protocol data packets include two or more fragments of the service packet link mapping table.

31. The device according to any one of claims 25 to 30, in, The apparatus is configured to allow a user to select a service from a plurality of services using a service group link mapping table.

32. The device according to any one of claims 25 to 31, in, The apparatus is configured to use a service group link mapping table to present a filtered subset of a plurality of services to a user according to one or more filtering conditions.

33. The device according to any one of claims 25 to 32, in, The output interface is configured to output information about at least two services among the plurality of services according to at least one group among the one or more groups; The apparatus includes a user interface or other mechanism for allowing a user to select a service from the information about at least two services among the plurality of services.

34. The device according to any one of claims 25 to 33, in, One or more segments of the service group link mapping table associate two or more services among the plurality of services with at least one category among the two or more categories and / or with at least one attribute among the two or more attributes.

35. The device according to claim 34, further according to claim 33, in, If the user has selected at least two categories from two or more categories through a user interface or other mechanism, the output interface is configured to present to the user only services of the plurality of services associated with all of the at least two categories selected by the user.

36. The device according to claim 34 or 35, further according to claim 33, in, If the user has selected at least two attributes from two or more attributes through a user interface or other mechanism, the output interface is configured to present to the user services from a plurality of services associated with at least one of the at least two attributes selected by the user.

37. The device according to any one of claims 25 to 36, in, One or more segments of the service group link mapping table indicate one or more groups, including: language-based grouping, and / or program type-based grouping, and / or region-based grouping, and / or country-of-origin-based grouping, and / or target audience age group-based grouping, and / or broadcast network-based grouping, and / or data application type-based grouping.

38. The device according to any one of claims 25 to 37, further according to any one of claims 10 to 24, in, One or more fragments of the service packet link mapping table include an indication of a physical layer pipe and / or an indication of an ATSC link layer protocol data packet, and the indication of the physical layer pipe and the indication of the ATSC link layer protocol data packet include one of the one or more fragments of the service packet link mapping table.

39. The device according to any one of claims 1 to 9, in, One or more other ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets include one or more table fragments for each of the one or more tables, wherein each of the one or more table fragments includes metadata supporting service selection, and / or includes information about content of a packet payload of each of the one or more ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets, and / or includes information about another table fragment in the one or more table fragments; Each of the one or more table fragments of each of the one or more tables includes table management information, the table management information including management information for the table fragment and / or for the table, wherein the table management information includes information about one or more management parameters.

40. A decoding device comprising: An interface (110) for receiving a plurality of ATSC link layer protocol data packets, each of the plurality of ATSC link layer protocol data packets including a data packet header and a data packet payload encapsulating digital content, wherein one or more of the plurality of ATSC link layer protocol data packets include content of one or more services transmitted by ATSC; and A decoding unit (120), wherein the decoding unit (120) is configured to decode a packet payload of each of at least one ATSC link layer protocol packet in a plurality of ATSC link layer protocol packets to obtain digital content of the one ATSC link layer protocol packet in the at least one ATSC link layer protocol packet, wherein one or more other ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets include one or more table fragments of each of the one or more tables, wherein each of the one or more table fragments includes metadata supporting service selection, and / or includes information about content of a packet payload of each of the one or more ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets, and / or includes information about another table fragment in the one or more table fragments; Each of the one or more table fragments of each of the one or more tables includes table management information, the table management information including management information for the table fragment and / or for the table, wherein the table management information includes information about one or more management parameters.

41. The device according to claim 39 or 40, in, At least one of the one or more tables includes two or more table fragments; Information about at least one of the one or more management parameters exists in each of the two or more table segments.

42. The device according to claim 41, in, The one or more management parameters include a plurality of management parameters; Here, information about each of a plurality of management parameters exists in each of the two or more table segments.

43. The device according to any one of claims 39 to 42, in, at least one table fragment of the one or more table fragments of a table of the one or more tables comprises a value of a data revision parameter of the table, the value being information about one of the one or more management parameters; The decoding unit (120) is configured to compare the current revision number of the table stored in the decoding unit (120) with the value of the data revision parameter of the table in at least one table segment to determine whether the storage information of the table stored in the decoding unit (120) needs to be updated.

44. The device according to claim 43, in, each of at least one table fragment of the one or more table fragments of a table of the one or more tables comprises a value of a fragment data revision parameter of the one table fragment of the at least one table fragment, the value being information about another management parameter of the one or more management parameters; The decoding unit (120) is configured to compare the current revision number of the table segment stored in the decoding unit (120) with the value of the segment data revision parameter of the table segment to determine whether the storage information of the table segment stored in the decoding unit (120) needs to be updated.

45. The device according to any one of claims 39 to 44, in, A body portion of at least one of the one or more table fragments of at least one of the one or more tables is compressed.

46. ​​The device according to claim 45, in, Each of the one or more table fragments of the at least one table includes a compression value indicating whether a body portion of the table fragment is compressed, the compression value serving as information on another management parameter of the one or more management parameters.

47. The device according to claim 45 or 46, further according to claim 44, in, The decoding unit (120) is configured to decompress a body portion of at least one table segment of the one or more table segments if it has been determined that storage information of the table segment stored in the decoding unit (120) needs to be updated; and The decoding unit (120) is configured to not decompress the main body of the table segment if it is determined that the storage information of the table segment stored in the decoding unit (120) does not need to be updated.

48. The device according to any one of claims 39 to 47, in, each of at least one table fragment of the one or more table fragments of a table of the one or more tables includes revised table information for the table; The revision table information for the table indicates a value of a segment data revision parameter for each of one or more table segments of the table in an ATSC transmission.

49. The device according to claim 48, in, The decoding unit (120) is configured to compare a current revision number of a table segment stored in the decoding unit (120) with a value of a segment data revision parameter for the table segment to determine whether storage information of the table segment stored in the decoding unit (120) needs to be updated.

50. The device according to claim 48 or 49, in, The revised table information for the table indicates the location of each of one or more table segments of the table in the ATSC transmission.

51. The device according to claim 50, in, The revised table information for the table indicates a location of each of one or more table segments of the table in the ATSC transmission by indicating a physical layer pipe including the table segment and / or by indicating an ATSC link layer protocol packet including the table segment.

52. The apparatus of claim 48 or 49, further comprising: a device according to claim 50 or 51, in, The decoding unit (120) is configured to obtain the table segment from a position of the table segment in the ATSC transmission if the decoding unit (120) has determined that storage information of the table segment stored in the decoding unit (120) needs to be updated; and The decoding unit (120) is configured not to obtain the table segment from the position of the table segment in the ATSC transmission if the decoding unit (120) has determined that the storage information of the table segment stored in the decoding unit (120) does not need to be updated.

53. The device according to any one of claims 39 to 52, further according to any one of claims 10 to 24, in, The one or more table fragments of each of the one or more tables include one or more fragments of a service link mapping table.

54. The device according to any one of claims 39 to 53, further according to any one of claims 25 to 38, in, The one or more table fragments of each of the one or more tables include one or more fragments of a service packet link mapping table.

55. The device according to any one of claims 39 to 54, in, The one or more table segments of each of the one or more tables include one or more segments of a logo / icon table (LIT), the LIT including information about a logo or icon of one or more versions; and / or, The one or more table segments of each of the one or more tables include one or more segments of a logo / icon variant (LIV), the LIV including image data for one version of a logo or icon.

56. The device according to any one of claims 39 to 55, in, A first table of the one or more tables has a first table type, wherein a second table of the one or more tables has a second table type different from the first table type; The decoding unit (120) is configured to decode one or more table fragments of the first table and one or more table fragments of the second table using the same decoding algorithm.

57. The device according to claim 56, in, The first table has a table type from a group consisting of at least four table types, the group consisting of the following table types: Link Mapping Table for Radio Services (LMT-R); Service Group Link Mapping Table (LMT-R-SG); Logo / Icon Table (LIT); and Logo / Icon Variant (LIV), The second table has a different table type from the group of at least four table types.

58. An apparatus for generating a plurality of ATSC link layer protocol packets, comprising: An interface (210) for receiving input data; as well as The data packet generator 220 is configured to generate a plurality of ATSC link layer protocol data packets according to the input data, so that each of the plurality of ATSC link layer protocol data packets includes a data packet header and a data packet payload encapsulating digital content. The data packet generator (220) is configured to generate one or more ATSC link layer protocol data packets from a plurality of ATSC link layer protocol data packets, such that the digital content encapsulated within the data packet payload of each of the one or more ATSC link layer protocol data packets includes: digital broadcast content, and / or distribution and communication protocol data packets or portions thereof, and / or unified speech and audio coding content or extended high-efficiency advanced audio coding content, and / or Journaline content.

59. The device according to claim 58, in, The data packet generator (220) is configured to generate an ATSC link layer protocol data packet in one or more ATSC link layer protocol data packets such that the digital content encapsulated within the ATSC link layer protocol data packet includes digital broadcast content.

60. The device according to claim 58, in, The data packet generator (220) is configured to generate an ATSC link layer protocol data packet in one or more ATSC link layer protocol data packets such that the digital content encapsulated within the ATSC link layer protocol data packet includes a distribution and communication protocol data packet or a portion thereof.

61. The device according to claim 60, in, The distribution and communication protocol data packets, or portions thereof, encapsulated within the data packet payload of the ATSC link layer protocol data packet include digital broadcast content.

62. The device according to claim 59 or 61, in, The digital broadcasting content includes global digital broadcasting content.

63. The device according to any one of claims 58 to 62, in, The data packet generator (220) is configured to generate an ATSC link layer protocol data packet in one or more ATSC link layer protocol data packets such that the digital content encapsulated within the ATSC link layer protocol data packet includes unified speech and audio coding content or extended high-efficiency advanced audio coding content.

64. The device according to any one of claims 58 to 63, in, The data packet generator (220) is configured to generate an ATSC link layer protocol data packet in one or more ATSC link layer protocol data packets such that the digital content encapsulated within the ATSC link layer protocol data packet includes Journaline content.

65. The device according to any one of claims 58 to 64, in, The data packet generator (220) is configured to generate a plurality of ATSC link layer protocol data packets such that one or more further ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets include one or more segments of the service link mapping table; Among them, one or more segments of the service link mapping table indicate one or more services transmitted by ATSC.

66. An apparatus for generating a plurality of ATSC link layer protocol packets, comprising: An interface (210) for receiving input data; as well as A data packet generator (220) is configured to generate a plurality of ATSC link layer protocol data packets based on input data, such that each of the plurality of ATSC link layer protocol data packets includes a data packet header and a data packet payload encapsulating digital content, wherein one or more of the plurality of ATSC link layer protocol data packets include content of one or more services transmitted by ATSC, The data packet generator (220) is configured to generate a plurality of ATSC link layer protocol data packets, so that one or more other ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets include one or more fragments of a service link mapping table, wherein the one or more fragments of the service link mapping table indicate one or more services transmitted by ATSC.

67. The device according to claim 65 or 66, in, The one or more segments of the service link mapping table are one or more segments of a radio service link mapping table; The one or more segments of the radio service link mapping table indicate one or more radio services transmitted by ATSC.

68. The device according to claim 67, in, The data packet generator (220) is configured to generate one or more further ATSC link layer protocol data packets such that one or more segments of the radio service link mapping table include metadata of one or more radio services transmitted by the ATSC.

69. The device according to claim 68, in, At least some of the plurality of ATSC link layer protocol data packets encapsulate a plurality of distribution and communication protocol data packets comprising one or more radio services of an ATSC transmission.

70. The device according to claim 68 or 69, in, The data packet generator (220) is configured to generate one or more further ATSC link layer protocol data packets such that metadata of one or more radio services includes information about a service tag, and / or information about a multiplex tag, and / or information about a language, and / or information about a program type, and / or information about a region, and / or information about a country of origin, and / or audio configuration information, and / or a data application identifier.

71. The device according to any one of claims 67 to 70, in, The data packet generator (220) is configured to generate one or more other ATSC link layer protocol data packets such that one or more segments of the radio service link mapping table are one or more segments of the global digital broadcast radio link mapping table, wherein the one or more segments of the global digital broadcast radio link mapping table indicate one or more global digital broadcast radio services transmitted by ATSC.

72. The device according to claim 71, in, The data packet generator (220) is configured to generate one or more further ATSC link layer protocol data packets such that one or more segments of the global digital broadcast radio link mapping table indicate an association of at least one of the one or more global digital broadcast radio services with one or more global digital broadcast multiplex distribution interface streams.

73. The device according to claim 72, in, The data packet generator (220) is configured to generate one or more further ATSC link layer protocol data packets such that one or more segments of the global digital broadcast radio link mapping table indicate the association of at least one global digital broadcast radio service of one or more global digital broadcast radio services with one or more global digital broadcast multiplex distribution interface streams by indicating a physical layer pipe identifier and / or an ATSC link layer protocol data packet identifier, and by indicating at least one global digital broadcast radio service of one or more global digital broadcast radio service identifiers associated with said one of the one or more global digital broadcast multiplex distribution interface streams.

74. The device of claim 72 or 73, further comprising any one of claims 68 to 70, in, The data packet generator (220) is configured to analyze one or more global digital broadcast multiplex distribution interface flows associated with one or more global digital broadcast radio services; and The data packet generator (220) is configured to generate one or more other ATSC link layer protocol data packets so that the metadata of one global digital broadcast radio service among the one or more global digital broadcast radio services corresponds to the metadata included in one global digital broadcast multiplexing distribution interface stream among the one or more global digital broadcast radio services.

75. The device according to any one of claims 72 to 74, in, The data packet generator (220) is configured to analyze one or more global digital broadcast multiplex distribution interface flows associated with one or more global digital broadcast radio services; and In which, the data packet generator 220 is configured to generate one or more other ATSC link layer protocol data packets so that one or more fragments of the radio service link mapping table include emergency alert information, which is used to indicate whether at least one global digital broadcast multiplexing distribution interface stream of one or more global digital broadcasting multiplexing distribution interface streams associated with one or more global digital broadcasting radio services indicates an emergency alert.

76. The device according to any one of claims 72 to 75, in, The data packet generator (220) is configured to generate a plurality of ATSC link layer protocol data packets such that if the data packet payloads of two ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets include global digital broadcast content of the same global digital broadcast multiplexing distribution interface stream, the data packet headers of the two ATSC link layer protocol data packets include the same substream identifier associated with the global digital broadcast multiplexing distribution interface stream.

77. The device according to any one of claims 65 to 70, in, The one or more segments of the radio service link mapping table are one or more segments of a digital audio broadcasting link mapping table; The one or more segments of the digital audio broadcast link mapping table indicate one or more digital audio broadcast services transmitted by ATSC.

78. The device according to claim 77, in, The one or more segments of the digital audio broadcast link mapping table indicate an association of at least one of the one or more digital audio broadcast services with one or more EDI (DAB interface encapsulation) streams.

79. The device according to any one of claims 65 to 78, in, The one or more other ATSC link layer protocol data packets are two or more other ATSC link layer protocol data packets, wherein the one or more segments are two or more segments, and wherein the one or more services are multiple services; and The data packet generator (220) is configured to generate two or more other ATSC link layer protocol data packets, so that the two or more other ATSC link layer protocol data packets include two or more fragments of the service link mapping table; wherein the two or more fragments of the service link mapping table indicate multiple services transmitted by ATSC.

80. The device according to any one of claims 65 to 79, in, The apparatus is configured to repeatedly transmit one or more ATSC link layer protocol data packets including one or more fragments of a service link mapping table.

81. The device according to any one of claims 58 to 80, in, The data packet generator (220) is configured to generate a plurality of ATSC link layer protocol data packets, such that one or more of the plurality of ATSC link layer protocol data packets include one or more fragments of a service packet link mapping table, the one or more fragments of the service packet link mapping table indicating one or more packets of a plurality of services transmitted by ATSC.

82. An apparatus for generating a plurality of ATSC link layer protocol data packets, comprising: An interface (210) for receiving input data; as well as A data packet generator (220) is configured to generate a plurality of ATSC link layer protocol data packets based on input data, such that each of the plurality of ATSC link layer protocol data packets includes a data packet header and a data packet payload encapsulating digital content, wherein one or more of the plurality of ATSC link layer protocol data packets include content of one or more services transmitted by ATSC, The data packet generator (220) is configured to generate a plurality of ATSC link layer protocol data packets, so that one or more of the plurality of ATSC link layer protocol data packets include one or more fragments of a service packet link mapping table, wherein the one or more fragments of the service packet link mapping table indicate one or more packets of a plurality of services transmitted by ATSC.

83. The device according to claim 81 or 82, in, The one or more segments of the service packet link mapping table are one or more segments of the radio service packet link mapping table; The one or more segments of the radio service packet link mapping table indicate one or more packets of multiple radio services transmitted by ATSC.

84. The device according to claim 83, in, The one or more segments of the service packet link mapping table are one or more segments of a global digital broadcast radio service packet link mapping table; The one or more segments of the global digital broadcast radio service packet link mapping table indicate one or more packets of multiple global digital broadcast radio services transmitted by ATSC.

85. The device according to claim 83, in, The one or more segments of the service packet link mapping table are one or more segments of a digital audio broadcasting service packet link mapping table; as well as The one or more segments of the digital audio broadcasting service packet link mapping table indicate one or more packets of multiple digital audio broadcasting services transmitted by ATSC.

86. The device according to any one of claims 81 to 85, in, The one or more further ATSC link layer protocol data packets are two or more further ATSC link layer protocol data packets, wherein the one or more segments of the service packet link mapping table are two or more segments; The data packet generator (220) is configured to generate two or more ATSC link layer protocol data packets, such that the two or more ATSC link layer protocol data packets include two or more fragments of the service packet link mapping table.

87. The device according to any one of claims 81 to 86, in, The data packet generator (220) is configured to generate one or more ATSC link layer protocol data packets such that one or more segments of the service packet link mapping table associate two or more of the plurality of services with at least one of the two or more categories and / or with at least one of the two or more attributes.

88. The device according to any one of claims 81 to 87, in, The data packet generator (220) is configured to generate one or more ATSC link layer protocol data packets such that one or more segments of the service packet link mapping table indicate one or more groups, including: language-based grouping, and / or program type-based grouping, and / or region-based grouping, and / or country-of-origin grouping, and / or target audience age group-based grouping, and / or broadcast network-based grouping, and / or data application type-based grouping.

89. The device according to any one of claims 81 to 88, further according to any one of claims 65 to 80, in, The data packet generator (220) is configured to generate one or more ATSC link layer protocol data packets such that one or more segments of the service link mapping table include an indication of a physical layer pipe and / or an indication of an ATSC link layer protocol data packet, and the indication of the physical layer pipe and the indication of the ATSC link layer protocol data packet include one of the one or more segments of the service packet link mapping table.

90. The device according to any one of claims 81 to 89, in, The apparatus is configured to repeatedly transmit one or more further ATSC link layer protocol data packets including one or more fragments of a service packet link mapping table.

91. The device according to any one of claims 58 to 64, in, The data packet generator (220) is configured to generate a plurality of ATSC link layer protocol data packets such that one or more other ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets include one or more table fragments of each of the one or more tables, wherein each of the one or more table fragments includes metadata supporting selection of a service, and / or includes information about content of a packet payload of each of the one or more ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets, and / or includes information about another table fragment in the one or more table fragments; Each of the one or more table fragments of each of the one or more tables includes table management information, the table management information including management information for the table fragment and / or for the table, wherein the table management information includes information about one or more management parameters.

92. An apparatus for generating a plurality of ATSC link layer protocol data packets, comprising: An interface (210) for receiving input data; as well as A data packet generator (220) is configured to generate a plurality of ATSC link layer protocol data packets based on input data, such that each of the plurality of ATSC link layer protocol data packets includes a data packet header and a data packet payload encapsulating digital content, wherein one or more of the plurality of ATSC link layer protocol data packets include content of one or more services transmitted by ATSC, wherein the data packet generator (220) is configured to generate a plurality of ATSC link layer protocol data packets such that one or more other ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets include one or more table fragments of each of the one or more tables, wherein each of the one or more table fragments includes metadata supporting selection of a service, and / or includes information about content of a packet payload of each of the one or more ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets, and / or includes information about another table fragment in the one or more table fragments; Each of the one or more table fragments of each of the one or more tables includes table management information, the table management information including management information for the table fragment and / or for the table, wherein the table management information includes information about one or more management parameters.

93. The device according to claim 91 or 92, in, At least one of the one or more tables includes two or more table fragments; Information about at least one of the one or more management parameters exists in each of the two or more table segments.

94. The device according to claim 93, in, The one or more management parameters include a plurality of management parameters; and Here, information about each of a plurality of management parameters exists in each of the two or more table segments.

95. The device according to any one of claims 91 to 94, in, At least one of the one or more table fragments of a table of the one or more tables includes a value of a data revision parameter for the table as information of one of the one or more management parameters.

96. The device according to claim 95, in, Each of at least one of the one or more table fragments of the table of the one or more tables includes a value of a fragment data revision parameter of the table fragment in the at least one table fragment, the value serving as information about another management parameter in the one or more management parameters.

97. The device according to any one of claims 91 to 96, in, The data packet generator (220) is configured to generate a plurality of ATSC link layer protocol data packets such that a body portion of at least one of the one or more table segments of at least one of the one or more tables is compressed.

98. The device according to claim 97, in, Each of the one or more table fragments of the at least one table includes a compression value indicating whether a body portion of the table fragment is compressed, the compression value serving as information on another management parameter of the one or more management parameters.

99. The device according to any one of claims 91 to 98, in, The data packet generator (220) is configured to generate a plurality of ATSC link layer protocol data packets such that each of at least one of the one or more table segments of a table of the one or more tables includes revised table information for the table; The revision table information for the table indicates a value of a segment data revision parameter for each of one or more table segments of the table in an ATSC transmission.

100. The device according to claim 99, in, The revised table information for the table indicates the location of each of one or more table segments of the table in the ATSC transmission.

101. The device according to claim 100, in, The revised table information for the table indicates a location of each of one or more table segments of the table in the ATSC transmission by indicating a physical layer pipe including the table segment and / or by indicating an ATSC link layer protocol packet including the table segment.

102. The device according to any one of claims 91 to 101, further according to any one of claims 65 to 80, in, The one or more table fragments of each of the one or more tables include one or more fragments of a service link mapping table.

103. The device according to any one of claims 91 to 102, further according to any one of claims 81 to 90, in, The one or more table fragments of each of the one or more tables include one or more fragments of a service packet link mapping table.

104. The device according to any one of claims 91 to 103, in, The one or more table segments of each of the one or more tables include one or more segments of a logo / icon table (LIT), the LIT including information about a logo or icon of one or more versions; and / or, The one or more table segments of each of the one or more tables include one or more segments of a logo / icon variant (LIV), the LIV including image data for one version of a logo or icon.

105. The device according to any one of claims 91 to 104, in, A first table of the one or more tables has a first table type, wherein a second table of the one or more tables has a second table type different from the first table type.

106. The device according to claim 105, in, The first table has a table type from a group consisting of at least four table types, the group consisting of the following table types: Link Mapping Table for Radio Services (LMT-R); Service Group Link Mapping Table (LMT-R-SG); Logo / Icon Table (LIT); and Logo / Icon Variant (LIV), The second table has a different table type from the group of at least four table types.

107. A data stream comprising a plurality of ATSC link layer protocol packets, in, Each of the plurality of ATSC link layer protocol packets includes a packet header and a packet payload encapsulating digital content; The digital content encapsulated within the packet payload of each of one or more ATSC link layer protocol packets in the multiple ATSC link layer protocol packets includes: digital broadcast content, and / or distribution and communication protocol packets or parts thereof, and / or unified voice and audio coding content or extended high-efficiency advanced audio coding content, and / or Journaline content.

108. The data stream according to claim 107, in, The digital content encapsulated within the ATSC link layer protocol data packets includes digital broadcast content.

109. The data stream according to claim 107, in, The digital content encapsulated within the ATSC link layer protocol data packets includes distribution and communication protocol data packets or portions thereof.

110. The data stream according to claim 109, in, The distribution and communication protocol data packets, or portions thereof, encapsulated within the data packet payload of the ATSC link layer protocol data packet include digital broadcast content.

111. The data stream according to claim 108 or 110, in, The digital broadcasting content includes global digital broadcasting content.

112. The data stream according to any one of claims 107 to 111, in, The digital content encapsulated in the ATSC link layer protocol data packets includes unified speech and audio coding content or extended high-efficiency advanced audio coding content.

113. A data stream according to any one of claims 107 to 112, in, The digital content encapsulated within the ATSC link layer protocol data packets includes Journaline content.

114. The data stream according to any one of claims 107 to 113, in, The data stream includes one or more other ATSC link layer protocol data packets among the plurality of ATSC link layer protocol data packets, the one or more other ATSC link layer protocol data packets including one or more fragments of the service link mapping table; Among them, one or more segments of the service link mapping table indicate one or more services transmitted by ATSC.

115. A data stream comprising a plurality of ATSC link layer protocol packets, in, Each of the plurality of ATSC link layer protocol packets includes a packet header and a packet payload encapsulating digital content, wherein one or more of the plurality of ATSC link layer protocol packets include content of one or more services transmitted by ATSC; The data stream includes one or more ATSC link layer protocol data packets among the plurality of ATSC link layer protocol data packets, and the one or more ATSC link layer protocol data packets include one or more fragments of a service link mapping table; Among them, one or more segments of the service link mapping table indicate one or more services transmitted by ATSC.

116. The data stream according to claim 114 or 115, in, The one or more segments of the service link mapping table are one or more segments of a radio service link mapping table; The one or more segments of the radio service link mapping table indicate one or more radio services transmitted by ATSC.

117. The data stream according to claim 116, in, One or more segments of the radio service link mapping table include metadata for one or more radio services transmitted by ATSC.

118. The data stream according to claim 117, in, At least some of the plurality of ATSC link layer protocol packets encapsulate a plurality of distribution and communication protocol packets comprising one or more radio services of an ATSC transmission.

119. The data stream according to claim 117 or 118, in, The metadata of one or more radio services includes information about a service tag, and / or information about a multiplexing tag, and / or information about a language, and / or information about a program type, and / or information about a region, and / or information about a country of origin, and / or audio configuration information, and / or a data application identifier.

120. The data stream according to any one of claims 116 to 119, in, The one or more segments of the radio service link mapping table are one or more segments of the global digital broadcast radio link mapping table, wherein the one or more segments of the global digital broadcast radio link mapping table indicate one or more global digital broadcast radio services transmitted by ATSC.

121. The data stream according to claim 120, in, The one or more segments of the global digital broadcast radio link mapping table indicate an association of at least one global digital broadcast radio service of the one or more global digital broadcast radio services with one or more global digital broadcast multiplex distribution interface flows.

122. The data stream according to claim 121, in, One or more fragments of the global digital broadcast radio link mapping table indicate the association of at least one global digital broadcast radio service of one or more global digital broadcast radio services with one or more global digital broadcast multiplex distribution interface streams by indicating a physical layer pipe identifier and / or an ATSC link layer protocol packet identifier, and by indicating at least one global digital broadcast radio service identifier of one or more global digital broadcast radio service identifiers associated with corresponding global digital broadcast multiplex distribution interface streams in the one or more global digital broadcast multiplex distribution interface streams.

123. A data stream according to claim 121 or 122, further according to one of claims 117 to 119, in, The metadata of one global digital broadcast radio service among the one or more global digital broadcast radio services corresponds to metadata included in one global digital broadcast multiplex distribution interface stream among the one or more global digital broadcast multiplex distribution interface streams associated with the one or more global digital broadcast radio services.

124. The data stream according to any one of claims 121 to 123, in, One or more segments of the radio service link mapping table include emergency warning information for indicating whether at least one global digital broadcast multiplex distribution interface flow of one or more global digital broadcast multiplex distribution interface flows associated with one or more global digital broadcast radio services indicates an emergency warning.

125. The data stream according to any one of claims 121 to 124, in, If the packet payloads of two ATSC link layer protocol data packets among the multiple ATSC link layer protocol data packets include global digital broadcast content of the same global digital broadcast multiplexing distribution interface stream, the packet headers of the two ATSC link layer protocol data packets include the same sub-stream identifier associated with the global digital broadcast multiplexing distribution interface stream.

126. The data stream according to any one of claims 114 to 119, in, The one or more segments of the radio service link mapping table are one or more segments of a digital audio broadcasting link mapping table; and The one or more segments of the digital audio broadcast link mapping table indicate one or more digital audio broadcast services transmitted by ATSC.

127. The data stream according to claim 126, in, The one or more segments of the digital audio broadcast link mapping table indicate an association of at least one digital audio broadcast service of the one or more digital audio broadcast services with one or more EDI (DAB interface encapsulation) streams.

128. The data stream according to any one of claims 114 to 127, in, The one or more further ATSC link layer protocol data packets are two or more further ATSC link layer protocol data packets, wherein the one or more segments are two or more segments, wherein the one or more services are multiple services; and Wherein, two or more other ATSC link layer protocol data packets include two or more fragments of the service link mapping table; wherein, the two or more fragments of the service link mapping table indicate multiple services transmitted by ATSC.

129. The data stream according to any one of claims 107 to 128, in, The data stream includes one or more ATSC link layer protocol data packets among multiple ATSC link layer protocol data packets, and the one or more ATSC link layer protocol data packets include one or more fragments of the service packet link mapping table, and the one or more fragments of the service packet link mapping table indicate one or more packets of multiple services transmitted by ATSC.

130. A data stream comprising a plurality of ATSC link layer protocol packets, in, Each of the plurality of ATSC link layer protocol packets includes a packet header and a packet payload encapsulating digital content, wherein one or more of the plurality of ATSC link layer protocol packets include content of one or more services transmitted by ATSC; The data stream includes one or more ATSC link layer protocol data packets among the multiple ATSC link layer protocol data packets, and the one or more ATSC link layer protocol data packets include one or more fragments of the service packet link mapping table, and the one or more fragments of the service packet link mapping table indicate one or more packets of multiple services transmitted by ATSC.

131. The data stream according to claim 129 or 130, in, The one or more segments of the service packet link mapping table are one or more segments of the radio service packet link mapping table; The one or more segments of the radio service packet link mapping table indicate one or more packets of multiple radio services transmitted by ATSC.

132. The data stream according to claim 131, in, The one or more segments of the service packet link mapping table are one or more segments of a global digital broadcast radio service packet link mapping table; The one or more segments of the global digital broadcast radio service packet link mapping table indicate one or more packets of multiple global digital broadcast radio services transmitted by ATSC.

133. The data stream according to claim 131, in, The one or more segments of the service packet link mapping table are one or more segments of a digital audio broadcasting service packet link mapping table; The one or more segments of the digital audio broadcasting service packet link mapping table indicate one or more packets of multiple digital audio broadcasting services transmitted by ATSC.

134. The data stream according to any one of claims 129 to 133, in, The one or more further ATSC link layer protocol data packets are two or more further ATSC link layer protocol data packets, wherein the one or more segments of the service packet link mapping table are two or more segments; Wherein, two or more ATSC link layer protocol data packets include two or more fragments of the service packet link mapping table.

135. The data stream according to any one of claims 129 to 134, in, One or more segments of the service group link mapping table associate two or more services among the plurality of services with at least one of the two or more categories and / or with at least one of the two or more attributes.

136. The data stream according to any one of claims 129 to 135, in, One or more segments of the service group link mapping table indicate one or more groups, including: language-based grouping, and / or program type-based grouping, and / or region-based grouping, and / or country-of-origin-based grouping, and / or target audience age group-based grouping, and / or broadcast network-based grouping, and / or data application type-based grouping.

137. A data stream according to any one of claims 129 to 136, further according to any one of claims 114 to 128, in, One or more fragments of the service link mapping table include an indication of a physical layer pipe and / or an indication of an ATSC link layer protocol data packet, and the indication of the physical layer pipe and the indication of the ATSC link layer protocol data packet include one of the one or more fragments of the service packet link mapping table.

138. The data stream according to any one of claims 107 to 113, in, One or more other ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets include one or more table fragments for each of the one or more tables, wherein each of the one or more table fragments includes metadata supporting selection of a service, and / or includes information regarding content of a packet payload of each of the one or more ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets, and / or includes information regarding another table fragment in the one or more table fragments; Each of the one or more table fragments of each of the one or more tables includes table management information, the table management information including management information for the table fragment and / or for the table, wherein the table management information includes information about one or more management parameters.

139. A data stream comprising a plurality of ATSC link layer protocol packets, in, Each of the plurality of ATSC link layer protocol packets includes a packet header and a packet payload encapsulating digital content, wherein one or more of the plurality of ATSC link layer protocol packets include content of one or more services transmitted by ATSC; wherein one or more other ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets include one or more table fragments of each of the one or more tables, wherein each of the one or more table fragments includes metadata supporting selection of a service, and / or includes information about content of a packet payload of each of the one or more ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets, and / or includes information about another table fragment in the one or more table fragments; Each of the one or more table fragments of each of the one or more tables includes table management information, the table management information including management information for the table fragment and / or for the table, wherein the table management information includes information about one or more management parameters.

140. The data stream according to claim 138 or 139, in, At least one table of the one or more tables includes two or more table fragments; and Information about at least one of the one or more management parameters exists in each of the two or more table segments.

141. The data stream according to claim 140, in, The one or more management parameters include a plurality of management parameters; as well as Here, information about each of a plurality of management parameters exists in each of the two or more table segments.

142. The data stream according to any one of claims 138 to 141, in, At least one of the one or more table fragments of a table of the one or more tables includes a value of a data revision parameter of the table as information about one of the one or more management parameters.

143. The data stream according to claim 142, in, Each of at least one table fragment of the one or more table fragments of a table in the one or more tables includes a value of a fragment data revision parameter of the one table fragment in the at least one table fragment, the value being information about another management parameter in the one or more management parameters.

144. The data stream according to any one of claims 138 to 143, in, A body portion of at least one of the one or more table fragments of at least one of the one or more tables is compressed.

145. The data stream according to claim 144, in, Each of the one or more table fragments of the at least one table includes a compression value indicating whether a body portion of the table fragment is compressed, the compression value serving as information on another management parameter of the one or more management parameters.

146. The data stream according to any one of claims 138 to 145, in, each of at least one table fragment of the one or more table fragments of a table of the one or more tables includes revised table information for the table; and The revision table information for the table indicates a value of a segment data revision parameter for each of one or more table segments of the table in an ATSC transmission.

147. The data stream according to claim 146, in, The revised table information for the table indicates the location of each of one or more table segments of the table in the ATSC transmission.

148. The data stream according to claim 147, in, The revised table information for the table indicates a location of each of one or more table segments of the table in the ATSC transmission by indicating a physical layer pipe including the table segment and / or by indicating an ATSC link layer protocol packet including the table segment.

149. A data stream according to any one of claims 138 to 148, further according to any one of claims 114 to 128, in, The one or more table fragments of each of the one or more tables include one or more fragments of a service link mapping table.

150. A data stream according to any one of claims 138 to 149, further according to any one of claims 129 to 137, in, The one or more table fragments of each of the one or more tables include one or more fragments of a service packet link mapping table.

151. The data stream according to any one of claims 138 to 150, in, The one or more table segments of each of the one or more tables include one or more segments of a logo / icon table (LIT), the LIT including information about a logo or icon of one or more versions; and / or, The one or more table segments of each of the one or more tables include one or more segments of a logo / icon variant (LIV), the LIV including image data for one version of a logo or icon.

152. The data stream according to any one of claims 138 to 151, in, A first table of the one or more tables has a first table type, wherein a second table of the one or more tables has a second table type different from the first table type.

153. The data stream according to claim 152, in, The first table has a table type from a group consisting of at least four table types, the group consisting of the following table types: Link Mapping Table for Radio Services (LMT-R); Service Group Link Mapping Table (LMT-R-SG); Logo / Icon Table (LIT); and Logo / Icon Variant (LIV), The second table has a different table type from the group of at least four table types.

154. A system comprising: The apparatus for generating a plurality of ATSC link layer protocol packets according to any one of claims 58 to 106; as well as The decoding device according to any one of claims 1 to 57, wherein the decoding device is configured to receive and decode a plurality of ATSC link layer protocol packets.

155. A decoding method comprising: receiving a plurality of ATSC link layer protocol packets, each of the plurality of ATSC link layer protocol packets comprising a packet header and a packet payload encapsulating digital content, wherein the digital content encapsulated within the packet payload of each of one or more ATSC link layer protocol packets in the plurality of ATSC link layer protocol packets comprises digital broadcast content, and / or distribution and communication protocol packets or portions thereof, and / or unified speech and audio coding content or extended high-efficiency advanced audio coding content, and / or Journaline content; and The packet payload of each of at least one ATSC link layer protocol data packet of the one or more ATSC link layer protocol data packets is decoded to obtain digital content of the one ATSC link layer protocol data packet of the at least one ATSC link layer protocol data packet.

156. A decoding method comprising: receiving a plurality of ATSC link layer protocol packets, each of the plurality of ATSC link layer protocol packets including a packet header and a packet payload encapsulating digital content, wherein one or more of the plurality of ATSC link layer protocol packets include content of one or more services transmitted by ATSC; and decoding a packet payload of each of at least one ATSC link layer protocol packet in the plurality of ATSC link layer protocol packets to obtain digital content of the one ATSC link layer protocol packet in the at least one ATSC link layer protocol packet, wherein one or more other ATSC link layer protocol data packets among the plurality of ATSC link layer protocol data packets include one or more fragments of a service link mapping table; wherein the one or more segments of the service link mapping table indicate one or more services transmitted by ATSC; and The method includes identifying an ATSC link layer protocol data packet including content of one of the one or more services by analyzing one or more segments of a service link mapping table.

157. A decoding method comprising: receiving a plurality of ATSC link layer protocol packets, each of the plurality of ATSC link layer protocol packets including a packet header and a packet payload encapsulating digital content, wherein one or more of the plurality of ATSC link layer protocol packets include content of one or more services transmitted by ATSC; and decoding a packet payload of each of at least one ATSC link layer protocol packet in the plurality of ATSC link layer protocol packets to obtain digital content of the one ATSC link layer protocol packet in the at least one ATSC link layer protocol packet, wherein one or more of the plurality of ATSC link layer protocol data packets include one or more segments of a service packet link mapping table, wherein the one or more segments of the service packet link mapping table indicate one or more packets of a plurality of services transmitted by ATSC; and The method includes providing an output based on at least one of the one or more groups, the output being dependent on at least one of a plurality of services.

158. A decoding method comprising: receiving a plurality of ATSC link layer protocol packets, each of the plurality of ATSC link layer protocol packets including a packet header and a packet payload encapsulating digital content, wherein one or more of the plurality of ATSC link layer protocol packets include content of one or more services transmitted by ATSC; and decoding a packet payload of each of at least one ATSC link layer protocol packet in the plurality of ATSC link layer protocol packets to obtain digital content of the one ATSC link layer protocol packet in the at least one ATSC link layer protocol packet, wherein one or more other ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets include one or more table fragments of each of the one or more tables, wherein each of the one or more table fragments includes metadata supporting selection of a service, and / or includes information about the content of a packet payload of each of the one or more ATSC link layer protocol data packets in the plurality of ATSC link layer protocol data packets, and / or includes information about another table fragment in the one or more table fragments; and Each of the one or more table fragments of each of the one or more tables includes table management information, the table management information including management information for the table fragment and / or for the table, wherein the table management information includes information about one or more management parameters.

159. A method for generating a plurality of ATSC link layer protocol packets, comprising: Receive input data; as well as generating a plurality of ATSC link layer protocol packets according to the input data, such that each of the plurality of ATSC link layer protocol packets includes a packet header and a packet payload encapsulating digital content, In which, one or more ATSC link layer protocol packets among multiple ATSC link layer protocol packets are generated, so that the digital content encapsulated in the packet payload of each of the one or more ATSC link layer protocol packets includes digital broadcast content, and / or distribution and communication protocol packets or parts thereof, and / or unified voice and audio coding content or extended high-efficiency advanced audio coding content, and / or Journaline content.

160. A method for generating a plurality of ATSC link layer protocol data packets, the method comprising: Receive input data; as well as generating a plurality of ATSC link layer protocol packets based on input data, such that each of the plurality of ATSC link layer protocol packets includes a packet header and a packet payload encapsulating digital content, wherein one or more of the plurality of ATSC link layer protocol packets includes content of one or more services transmitted by ATSC, The method includes generating multiple ATSC link layer protocol data packets, so that one or more other ATSC link layer protocol data packets in the multiple ATSC link layer protocol data packets include one or more fragments of the service link mapping table, wherein the one or more fragments of the service link mapping table indicate one or more services transmitted by ATSC.

161. A method for generating a plurality of ATSC link layer protocol data packets, comprising: Receive input data; as well as generating a plurality of ATSC link layer protocol packets based on input data, such that each of the plurality of ATSC link layer protocol packets includes a packet header and a packet payload encapsulating digital content, wherein one or more of the plurality of ATSC link layer protocol packets includes content of one or more services transmitted by ATSC, In which, generation of multiple ATSC link layer protocol data packets is implemented so that one or more of the multiple ATSC link layer protocol data packets include one or more fragments of the service packet link mapping table, and the one or more fragments of the service packet link mapping table indicate one or more packets of multiple services transmitted by ATSC.

162. A method for generating a plurality of ATSC link layer protocol data packets, comprising: Receive input data, and generating a plurality of ATSC link layer protocol packets based on input data, such that each of the plurality of ATSC link layer protocol packets includes a packet header and a packet payload encapsulating digital content, wherein one or more of the plurality of ATSC link layer protocol packets includes content of one or more services transmitted by ATSC, wherein generating the plurality of ATSC link layer protocol packets is implemented such that one or more other ATSC link layer protocol packets of the plurality of ATSC link layer protocol packets include one or more table fragments of each of the one or more tables, wherein each of the one or more table fragments includes metadata supporting selection of a service, and / or includes information regarding content of a packet payload of each of the one or more of the plurality of ATSC link layer protocol packets, and / or includes information regarding another table fragment of the one or more table fragments; and Each of the one or more table fragments of each of the one or more tables includes table management information, the table management information including management information for the table fragment and / or for the table, wherein the table management information includes information about one or more management parameters.

163. A computer program for implementing the method of any one of claims 155 to 162 when executed on a computer or a signal processor.

Images