WO2017217825A1 - Dispositif et procédé de transmission/réception de signal de diffusion - Google Patents

Dispositif et procédé de transmission/réception de signal de diffusion Download PDF

Info

Publication number
WO2017217825A1
WO2017217825A1 PCT/KR2017/006361 KR2017006361W WO2017217825A1 WO 2017217825 A1 WO2017217825 A1 WO 2017217825A1 KR 2017006361 W KR2017006361 W KR 2017006361W WO 2017217825 A1 WO2017217825 A1 WO 2017217825A1
Authority
WO
WIPO (PCT)
Prior art keywords
header
packet
field
information
lct
Prior art date
Application number
PCT/KR2017/006361
Other languages
English (en)
Korean (ko)
Inventor
권우석
Original Assignee
엘지전자(주)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 엘지전자(주) filed Critical 엘지전자(주)
Publication of WO2017217825A1 publication Critical patent/WO2017217825A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/234—Processing of video elementary streams, e.g. splicing of video streams, manipulating MPEG-4 scene graphs
    • H04N21/2343—Processing of video elementary streams, e.g. splicing of video streams, manipulating MPEG-4 scene graphs involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/235—Processing of additional data, e.g. scrambling of additional data or processing content descriptors
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/236—Assembling of a multiplex stream, e.g. transport stream, by combining a video stream with other content or additional data, e.g. inserting a URL [Uniform Resource Locator] into a video stream, multiplexing software data into a video stream; Remultiplexing of multiplex streams; Insertion of stuffing bits into the multiplex stream, e.g. to obtain a constant bit-rate; Assembling of a packetised elementary stream
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/238—Interfacing the downstream path of the transmission network, e.g. adapting the transmission rate of a video stream to network bandwidth; Processing of multiplex streams
    • H04N21/2381—Adapting the multiplex stream to a specific network, e.g. an Internet Protocol [IP] network

Definitions

  • the present invention relates to a broadcast signal transmitting apparatus, a broadcast signal receiving apparatus, a broadcast signal transmitting method, and a broadcast signal receiving method.
  • the digital broadcast signal may include a larger amount of video / audio data than the analog broadcast signal, and may further include various types of additional data as well as the video / audio data.
  • the digital broadcasting system may provide high definition (HD) images, multichannel audio, and various additional services.
  • HD high definition
  • data transmission efficiency for a large amount of data transmission, robustness of a transmission / reception network, and network flexibility in consideration of a mobile receiving device should be improved.
  • the present invention proposes a broadcast signal transmission method and a broadcast signal transmission apparatus.
  • a broadcast signal transmission method comprising: encoding service data for a broadcast service based on a Real Time Object Delivery over Unidirectional Transport (ROUTE) protocol; Generating at least one IP packet by processing the service data in a User Datagram Protocol (UDP) / Internet Protocol (IP) layer, each IP packet including an IP header, a UDP header, and a Layered Coding Transport (LCT) header; Link layer processing the at least one IP packet to output at least one link layer packet; And
  • ROUTE Real Time Object Delivery over Unidirectional Transport
  • Physical layer processing the link layer packet to generate a broadcast signal comprises: performing header compression on the at least one IP packet and the at least one IP packet Encapsulating the data and the link layer signaling information into at least one link layer packet, wherein the link layer signaling information may include header compression information including information related to the header compression.
  • the performing of the header compression may include performing header compression on an LCT header of the at least one IP packet.
  • the header compression information may include LCT compression flag information indicating whether header compression on the LCT header is performed.
  • the compressing the LCT header may compress the LCT header by deleting fields having a fixed value among the fields in the LCT header.
  • the fixed value field may include a version number field indicating a protocol version number, a control control flag field indicating a length of a control control field, and a length of a transport session identifier field. It may include at least one of a transport session identifier flag field used, a transport object identifier flag field used to indicate the length of the transport object identifier field, or a conference control field including conference control information.
  • the performing of the header compression may further include performing header compression on an IP header of the at least one IP packet based on a Robust Header Compression (RoHC) scheme.
  • RoHC Robust Header Compression
  • the generating of the link layer packet may further include, after compressing the IP header, extracting context information based on at least one adaptation mode, wherein the header compression information is generated.
  • the apparatus may further include context information, and the context information may include at least one of static chain information or dynamic chain information.
  • a broadcast signal transmitter includes a communication unit for transmitting a broadcast signal; A memory for storing data; And a processor controlling the communication unit and the memory.
  • the broadcast signal transmitter comprises: encoding service data for a broadcast service based on a Real time Object delivery over Unidirectional Transport (ROUTE) protocol; Processing the service data by User Datagram Protocol (UDP) / Internet Protocol (IP) layer to generate at least one IP packet, each IP packet including an IP header, a UDP header and a Layered Coding Transport (LCT) header; Link layer processing the at least one IP packet to output at least one link layer packet; And physical layer processing the link layer packet to generate a broadcast signal, wherein generating the link layer packet comprises: performing header compression on the at least one IP packet and data and link of the at least one IP packet Encapsulating layer signaling information into at least one link layer packet, wherein the link layer signaling information may include header compression information including information related to the header compression.
  • ROUTE Real time Object delivery over Unidirectional Transport
  • IP Internet Protocol
  • LCT Layer
  • the present invention can provide various broadcast services by processing data according to service characteristics to control a quality of service (QoS) for each service or service component.
  • QoS quality of service
  • the present invention can achieve transmission flexibility by transmitting various broadcast services through the same radio frequency (RF) signal bandwidth.
  • RF radio frequency
  • the present invention it is possible to provide a broadcast signal transmission and reception method and apparatus capable of receiving a digital broadcast signal without errors even when using a mobile reception device or in an indoor environment.
  • the present invention can effectively support the next generation broadcast service in an environment supporting the next generation hybrid broadcast using the terrestrial broadcast network and the Internet network.
  • FIG. 1 is a diagram illustrating a protocol stack according to an embodiment of the present invention.
  • FIG. 2 is a diagram illustrating a service discovery process according to an embodiment of the present invention.
  • LLS low level signaling
  • SLT service list table
  • FIG. 4 illustrates a USBD and an S-TSID delivered to ROUTE according to an embodiment of the present invention.
  • FIG. 5 is a diagram illustrating a USBD delivered to MMT according to an embodiment of the present invention.
  • FIG. 6 illustrates a link layer operation according to an embodiment of the present invention.
  • FIG. 7 illustrates a link mapping table (LMT) according to an embodiment of the present invention.
  • FIG. 8 shows a structure of a broadcast signal transmission apparatus for a next generation broadcast service according to an embodiment of the present invention.
  • FIG 9 illustrates a writing operation of a time interleaver according to an embodiment of the present invention.
  • FIG. 10 is a block diagram of an interleaving address generator composed of a main-PRBS generator and a sub-PRBS generator according to each FFT mode included in a frequency interleaver according to an embodiment of the present invention.
  • FIG. 11 shows a header structure of an LCT packet according to an embodiment of the present invention.
  • FIG. 12 shows a header structure of an LCT packet according to another embodiment of the present invention.
  • FIG. 13 shows an LCT header compression method according to a first embodiment of the present invention.
  • FIG. 14 illustrates an LCT header compression method according to a second embodiment of the present invention.
  • FIG. 15 illustrates a LCT header compression method according to a third embodiment of the present invention.
  • FIG. 16 shows an LCT header compression method according to a fourth embodiment of the present invention.
  • FIG 17 illustrates a reduced LCT header according to an embodiment of the present invention.
  • FIG. 18 illustrates a reduced LCT header according to an embodiment of the present invention.
  • RHC ROHC-U Description Table
  • FIG. 20 illustrates a broadcast signal transmitter / receiver configuration according to an embodiment of the present invention.
  • FIG. 21 illustrates a broadcast signal transmission method according to an embodiment of the present invention.
  • the present invention provides an apparatus and method for transmitting and receiving broadcast signals for next generation broadcast services.
  • the next generation broadcast service includes a terrestrial broadcast service, a mobile broadcast service, a UHDTV service, and the like.
  • a broadcast signal for a next generation broadcast service may be processed through a non-multiple input multiple output (MIMO) or MIMO scheme.
  • the non-MIMO scheme according to an embodiment of the present invention may include a multiple input single output (MISO) scheme, a single input single output (SISO) scheme, and the like.
  • MISO multiple input single output
  • SISO single input single output
  • the present invention proposes a physical profile (or system) that is optimized to minimize receiver complexity while achieving the performance required for a particular application.
  • FIG. 1 is a diagram illustrating a protocol stack according to an embodiment of the present invention.
  • the service may be delivered to the receiver through a plurality of layers.
  • the transmitting side can generate service data.
  • the delivery layer on the transmitting side performs processing for transmission to the service data, and the physical layer encodes it as a broadcast signal and transmits it through a broadcasting network or broadband.
  • the service data may be generated in a format according to ISO BMFF (base media file format).
  • the ISO BMFF media file may be used in broadcast network / broadband delivery, media encapsulation and / or synchronization format.
  • the service data is all data related to the service, and may include a concept including service components constituting the linear service, signaling information thereof, non real time (NRT) data, and other files.
  • the delivery layer will be described.
  • the delivery layer may provide a transmission function for service data.
  • the service data may be delivered through a broadcast network and / or broadband.
  • the first method may be to process service data into Media Processing Units (MPUs) based on MPEG Media Transport (MMT) and transmit the data using MMM protocol (MMTP).
  • MPUs Media Processing Units
  • MMT MPEG Media Transport
  • MMTP MMM protocol
  • the service data delivered through the MMTP may include service components for linear service and / or service signaling information thereof.
  • the second method may be to process service data into DASH segments based on MPEG DASH and transmit it using Real Time Object Delivery over Unidirectional Transport (ROUTE).
  • the service data delivered through the ROUTE protocol may include service components for the linear service, service signaling information and / or NRT data thereof. That is, non-timed data such as NRT data and files may be delivered through ROUTE.
  • Data processed according to the MMTP or ROUTE protocol may be processed into IP packets via the UDP / IP layer.
  • a service list table (SLT) may also be transmitted through a broadcasting network through a UDP / IP layer.
  • the SLT may be included in the LLS (Low Level Signaling) table and transmitted. The SLT and the LLS table will be described later.
  • IP packets may be treated as link layer packets at the link layer.
  • the link layer may encapsulate data of various formats delivered from an upper layer into a link layer packet and then deliver the data to the physical layer. The link layer will be described later.
  • At least one or more service elements may be delivered via a broadband path.
  • the data transmitted through the broadband may include service components in a DASH format, service signaling information and / or NRT data thereof. This data can be processed via HTTP / TCP / IP, passed through the link layer for broadband transmission, and delivered to the physical layer for broadband transmission.
  • the physical layer may process data received from a delivery layer (upper layer and / or link layer) and transmit the data through a broadcast network or a broadband. Details of the physical layer will be described later.
  • the service may be a collection of service components that are shown to the user as a whole, the components may be of different media types, the service may be continuous or intermittent, the service may be real time or non-real time, and the real time service may be a sequence of TV programs. It can be configured as.
  • the service may be a linear audio / video or audio only service that may have app-based enhancements.
  • the service may be an app-based service whose reproduction / configuration is controlled by the downloaded application.
  • the service may be an ESG service that provides an electronic service guide (ESG).
  • ESG electronic service guide
  • EA Emergency Alert
  • the service component may be delivered by (1) one or more ROUTE sessions or (2) one or more MMTP sessions.
  • the service component When a linear service with app-based enhancement is delivered through a broadcast network, the service component may be delivered by (1) one or more ROUTE sessions and (2) zero or more MMTP sessions.
  • data used for app-based enhancement may be delivered through a ROUTE session in the form of NRT data or other files.
  • linear service components (streaming media components) of one service may not be allowed to be delivered using both protocols simultaneously.
  • the service component may be delivered by one or more ROUTE sessions.
  • the service data used for the app-based service may be delivered through a ROUTE session in the form of NRT data or other files.
  • some service components or some NRT data, files, etc. of these services may be delivered via broadband (hybrid service delivery).
  • the linear service components of one service may be delivered through the MMT protocol.
  • the linear service components of one service may be delivered via a ROUTE protocol.
  • the linear service component and NRT data (NRT service component) of one service may be delivered through the ROUTE protocol.
  • linear service components of one service may be delivered through the MMT protocol, and NRT data (NRT service components) may be delivered through the ROUTE protocol.
  • some service component or some NRT data of a service may be delivered over broadband.
  • the data related to the app-based service or the app-based enhancement may be transmitted through a broadcast network according to ROUTE or through broadband in the form of NRT data.
  • NRT data may also be referred to as locally cashed data.
  • Each ROUTE session includes one or more LCT sessions that deliver, in whole or in part, the content components that make up the service.
  • an LCT session may deliver an individual component of a user service, such as an audio, video, or closed caption stream.
  • Streaming media is formatted into a DASH segment.
  • Each MMTP session includes one or more MMTP packet flows carrying an MMT signaling message or all or some content components.
  • the MMTP packet flow may carry a component formatted with an MMT signaling message or an MPU.
  • an LCT session For delivery of NRT user service or system metadata, an LCT session carries a file based content item.
  • These content files may consist of continuous (timed) or discrete (non-timed) media components of an NRT service, or metadata such as service signaling or ESG fragments.
  • Delivery of system metadata, such as service signaling or ESG fragments, can also be accomplished through the signaling message mode of the MMTP.
  • the tuner can scan frequencies and detect broadcast signals at specific frequencies.
  • the receiver can extract the SLT and send it to the module that processes it.
  • the SLT parser can parse the SLT, obtain data, and store it in the channel map.
  • the receiver may acquire bootstrap information of the SLT and deliver it to the ROUTE or MMT client. This allows the receiver to obtain and store the SLS. USBD or the like can be obtained, which can be parsed by the signaling parser.
  • FIG. 2 is a diagram illustrating a service discovery process according to an embodiment of the present invention.
  • the broadcast stream delivered by the broadcast signal frame of the physical layer may carry LLS (Low Level Signaling).
  • LLS data may be carried through the payload of an IP packet delivered to a well known IP address / port. This LLS may contain an SLT depending on its type.
  • LLS data may be formatted in the form of an LLS table. The first byte of every UDP / IP packet carrying LLS data may be the beginning of the LLS table. Unlike the illustrated embodiment, the IP stream carrying LLS data may be delivered to the same PLP along with other service data.
  • the SLT enables the receiver to generate a service list through a fast channel scan and provides access information for locating the SLS.
  • the SLT includes bootstrap information, which enables the receiver to obtain Service Layer Signaling (SLS) for each service.
  • SLS Service Layer Signaling
  • the bootstrap information may include destination IP address and destination port information of the ROUTE session including the LCT channel carrying the SLS and the LCT channel.
  • the bootstrap information may include a destination IP address and destination port information of the MMTP session carrying the SLS.
  • the SLS of service # 1 described by the SLT is delivered via ROUTE, and the SLT includes bootstrap information (sIP1, dIP1, dPort1) for the ROUTE session including the LCT channel to which the SLS is delivered. can do.
  • SLS of service # 2 described by the SLT is delivered through MMT, and the SLT may include bootstrap information (sIP2, dIP2, and dPort2) for an MMTP session including an MMTP packet flow through which the SLS is delivered.
  • the SLS is signaling information describing characteristics of a corresponding service and may include information for acquiring a corresponding service and a service component of the corresponding service, or may include receiver capability information for reproducing the corresponding service significantly. Having separate service signaling for each service allows the receiver to obtain the appropriate SLS for the desired service without having to parse the entire SLS delivered in the broadcast stream.
  • the SLS When the SLS is delivered through the ROUTE protocol, the SLS may be delivered through a dedicated LCT channel of a ROUTE session indicated by the SLT.
  • the SLS may include a user service bundle description (USBD / USD), a service-based transport session instance description (S-TSID), and / or a media presentation description (MPD).
  • USBD / USD user service bundle description
  • S-TSID service-based transport session instance description
  • MPD media presentation description
  • USBD to USD is one of the SLS fragments and may serve as a signaling hub for describing specific technical information of a service.
  • the USBD may include service identification information, device capability information, and the like.
  • the USBD may include reference information (URI reference) to other SLS fragments (S-TSID, MPD, etc.). That is, USBD / USD can refer to S-TSID and MPD respectively.
  • the USBD may further include metadata information that enables the receiver to determine the transmission mode (broadcast network / broadband). Details of the USBD / USD will be described later.
  • the S-TSID is one of the SLS fragments, and may provide overall session description information for a transport session carrying a service component of a corresponding service.
  • the S-TSID may provide transport session description information for the ROUTE session to which the service component of the corresponding service is delivered and / or the LCT channel of the ROUTE sessions.
  • the S-TSID may provide component acquisition information of service components related to one service.
  • the S-TSID may provide a mapping between the DASH Representation of the MPD and the tsi of the corresponding service component.
  • the component acquisition information of the S-TSID may be provided in the form of tsi, an identifier of an associated DASH representation, and may or may not include a PLP ID according to an embodiment.
  • the component acquisition information enables the receiver to collect audio / video components of a service and to buffer, decode, and the like of DASH media segments.
  • the S-TSID may be referenced by the USBD as described above. Details of the S-TSID will be described later.
  • the MPD is one of the SLS fragments and may provide a description of the DASH media presentation of the service.
  • the MPD may provide a resource identifier for the media segments and may provide contextual information within the media presentation for the identified resources.
  • the MPD may describe the DASH representation (service component) delivered through the broadcast network, and may also describe additional DASH representations delivered through the broadband (hybrid delivery).
  • the MPD may be referenced by the USBD as described above.
  • the SLS When the SLS is delivered through the MMT protocol, the SLS may be delivered through a dedicated MMTP packet flow of an MMTP session indicated by the SLT.
  • packet_id of MMTP packets carrying SLS may have a value of 00.
  • the SLS may include a USBD / USD and / or MMT Package (MP) table.
  • USBD is one of the SLS fragments, and may describe specific technical information of a service like that in ROUTE.
  • the USBD here may also include reference information (URI reference) to other SLS fragments.
  • the USBD of the MMT may refer to the MP table of the MMT signaling.
  • the USBD of the MMT may also include reference information on the S-TSID and / or the MPD.
  • the S-TSID may be for NRT data transmitted through the ROUTE protocol. This is because NRT data can be delivered through the ROUTE protocol even when the linear service component is delivered through the MMT protocol.
  • MPD may be for a service component delivered over broadband in hybrid service delivery. Details of the USBD of the MMT will be described later.
  • the MP table is a signaling message of the MMT for MPU components and may provide overall session description information for an MMTP session carrying a service component of a corresponding service.
  • the MP table may also contain descriptions for assets delivered via this MMTP session.
  • the MP table is streaming signaling information for MPU components, and may provide a list of assets corresponding to one service and location information (component acquisition information) of these components. Specific contents of the MP table may be in a form defined in MMT or a form in which modifications are made.
  • Asset is a multimedia data entity, which may mean a data entity associated with one unique ID and used to generate one multimedia presentation. Asset may correspond to a service component constituting a service.
  • the MP table may be used to access a streaming service component (MPU) corresponding to a desired service.
  • the MP table may be referenced by the USBD as described above.
  • MMT signaling messages may be defined. Such MMT signaling messages may describe additional information related to the MMTP session or service.
  • ROUTE sessions are identified by source IP address, destination IP address, and destination port number.
  • the LCT session is identified by a transport session identifier (TSI) that is unique within the scope of the parent ROUTE session.
  • MMTP sessions are identified by destination IP address and destination port number.
  • the MMTP packet flow is identified by a unique packet_id within the scope of the parent MMTP session.
  • the S-TSID, the USBD / USD, the MPD, or the LCT session carrying them may be called a service signaling channel.
  • the S-TSID, the USBD / USD, the MPD, or the LCT session carrying them may be called a service signaling channel.
  • the S-TSID, the USBD / USD, the MPD, or the LCT session carrying them may be called a service signaling channel.
  • the MMT signaling messages or packet flow carrying them may be called a service signaling channel.
  • one ROUTE or MMTP session may be delivered through a plurality of PLPs. That is, one service may be delivered through one or more PLPs. Unlike shown, components constituting one service may be delivered through different ROUTE sessions. In addition, according to an embodiment, components constituting one service may be delivered through different MMTP sessions. According to an embodiment, components constituting one service may be delivered divided into a ROUTE session and an MMTP session. Although not shown, a component constituting one service may be delivered through a broadband (hybrid delivery).
  • LLS low level signaling
  • SLT service list table
  • An embodiment t3010 of the illustrated LLS table may include information according to an LLS_table_id field, a provider_id field, an LLS_table_version field, and / or an LLS_table_id field.
  • the LLS_table_id field may identify a type of the corresponding LLS table, and the provider_id field may identify service providers related to services signaled by the corresponding LLS table.
  • the service provider is a broadcaster using all or part of the broadcast stream, and the provider_id field may identify one of a plurality of broadcasters using the broadcast stream.
  • the LLS_table_version field may provide version information of a corresponding LLS table.
  • the corresponding LLS table includes the above-described SLT, a rating region table (RRT) including information related to a content advisory rating, a SystemTime information providing information related to system time, and an emergency alert. It may include one of the CAP (Common Alert Protocol) message that provides information related to. According to an embodiment, other information other than these may be included in the LLS table.
  • RRT rating region table
  • CAP Common Alert Protocol
  • One embodiment t3020 of the illustrated SLT may include an @bsid attribute, an @sltCapabilities attribute, a sltInetUrl element, and / or a Service element.
  • Each field may be omitted or may exist in plurality, depending on the value of the illustrated Use column.
  • the @bsid attribute may be an identifier of a broadcast stream.
  • the @sltCapabilities attribute can provide the capability information required to decode and significantly reproduce all services described by the SLT.
  • the sltInetUrl element may provide base URL information used to obtain ESG or service signaling information for services of the corresponding SLT through broadband.
  • the sltInetUrl element may further include an @urlType attribute, which may indicate the type of data that can be obtained through the URL.
  • the service element may be an element including information on services described by the corresponding SLT, and a service element may exist for each service.
  • the Service element contains the @serviceId property, the @sltSvcSeqNum property, the @protected property, the @majorChannelNo property, the @minorChannelNo property, the @serviceCategory property, the @shortServiceName property, the @hidden property, the @broadbandAccessRequired property, the @svcCapabilities property, the BroadcastSvcSignaling element, and / or the svcInetUrl element. It may include.
  • the @serviceId attribute may be an identifier of a corresponding service, and the @sltSvcSeqNum attribute may indicate a sequence number of SLT information for the corresponding service.
  • the @protected attribute may indicate whether at least one service component necessary for meaningful playback of the corresponding service is protected.
  • the @majorChannelNo and @minorChannelNo attributes may indicate the major channel number and the minor channel number of the corresponding service, respectively.
  • the @serviceCategory attribute can indicate the category of the corresponding service.
  • the service category may include a linear A / V service, a linear audio service, an app-based service, an ESG service, and an EAS service.
  • the @shortServiceName attribute may provide a short name of the corresponding service.
  • the @hidden attribute can indicate whether the service is for testing or proprietary use.
  • the @broadbandAccessRequired attribute may indicate whether broadband access is required for meaningful playback of the corresponding service.
  • the @svcCapabilities attribute can provide the capability information necessary for decoding and meaningful reproduction of the corresponding service.
  • the BroadcastSvcSignaling element may provide information related to broadcast signaling of a corresponding service. This element may provide information such as a location, a protocol, and an address with respect to signaling through a broadcasting network of a corresponding service. Details will be described later.
  • the svcInetUrl element may provide URL information for accessing signaling information for a corresponding service through broadband.
  • the sltInetUrl element may further include an @urlType attribute, which may indicate the type of data that can be obtained through the URL.
  • the aforementioned BroadcastSvcSignaling element may include an @slsProtocol attribute, an @slsMajorProtocolVersion attribute, an @slsMinorProtocolVersion attribute, an @slsPlpId attribute, an @slsDestinationIpAddress attribute, an @slsDestinationUdpPort attribute, and / or an @slsSourceIpAddress attribute.
  • the @slsProtocol attribute can indicate the protocol used to deliver the SLS of the service (ROUTE, MMT, etc.).
  • the @slsMajorProtocolVersion attribute and @slsMinorProtocolVersion attribute may indicate the major version number and the minor version number of the protocol used to deliver the SLS of the corresponding service, respectively.
  • the @slsPlpId attribute may provide a PLP identifier for identifying a PLP that delivers the SLS of the corresponding service.
  • this field may be omitted, and the PLP information to which the SLS is delivered may be identified by combining information in the LMT to be described later and bootstrap information of the SLT.
  • the @slsDestinationIpAddress attribute, @slsDestinationUdpPort attribute, and @slsSourceIpAddress attribute may indicate the destination IP address, the destination UDP port, and the source IP address of the transport packet carrying the SLS of the corresponding service, respectively. They can identify the transport session (ROUTE session or MMTP session) to which the SLS is delivered. These may be included in the bootstrap information.
  • FIG. 4 illustrates a USBD and an S-TSID delivered to ROUTE according to an embodiment of the present invention.
  • One embodiment t4010 of the illustrated USBD may have a bundleDescription root element.
  • the bundleDescription root element may have a userServiceDescription element.
  • the userServiceDescription element may be an instance of one service.
  • the userServiceDescription element may include an @globalServiceID attribute, an @serviceId attribute, an @serviceStatus attribute, an @fullMPDUri attribute, an @sTSIDUri attribute, a name element, a serviceLanguage element, a capabilityCode element, and / or a deliveryMethod element.
  • Each field may be omitted or may exist in plurality, depending on the value of the illustrated Use column.
  • the @globalServiceID attribute is a globally unique identifier of the service and can be used to link with ESG data (Service @ globalServiceID).
  • the @serviceId attribute is a reference corresponding to the corresponding service entry of the SLT and may be the same as service ID information of the SLT.
  • the @serviceStatus attribute may indicate the status of the corresponding service. This field may indicate whether the corresponding service is active or inactive.
  • the @fullMPDUri attribute can refer to the MPD fragment of the service. As described above, the MPD may provide a reproduction description for a service component delivered through a broadcast network or a broadband.
  • the @sTSIDUri attribute may refer to the S-TSID fragment of the service.
  • the S-TSID may provide parameters related to access to the transport session carrying the service as described above.
  • the name element may provide the name of the service.
  • This element may further include an @lang attribute, which may indicate the language of the name provided by the name element.
  • the serviceLanguage element may indicate the available languages of the service. That is, this element may list the languages in which the service can be provided.
  • the capabilityCode element may indicate capability or capability group information of the receiver side necessary for significantly playing a corresponding service. This information may be compatible with the capability information format provided by the service announcement.
  • the deliveryMethod element may provide delivery related information with respect to contents accessed through a broadcasting network or a broadband of a corresponding service.
  • the deliveryMethod element may include a broadcastAppService element and / or a unicastAppService element. Each of these elements may have a basePattern element as its child element.
  • the broadcastAppService element may include transmission related information on the DASH presentation delivered through the broadcast network.
  • These DASH representations may include media components across all periods of the service media presentation.
  • the basePattern element of this element may represent a character pattern used by the receiver to match the segment URL. This can be used by the DASH client to request segments of the representation. Matching may imply that the media segment is delivered over the broadcast network.
  • the unicastAppService element may include transmission related information on the DASH representation delivered through broadband. These DASH representations may include media components across all periods of the service media presentation.
  • the basePattern element of this element may represent a character pattern used by the receiver to match the segment URL. This can be used by the DASH client to request segments of the representation. Matching may imply that the media segment is delivered over broadband.
  • An embodiment t4020 of the illustrated S-TSID may have an S-TSID root element.
  • the S-TSID root element may include an @serviceId attribute and / or an RS element.
  • Each field may be omitted or may exist in plurality, depending on the value of the illustrated Use column.
  • the @serviceId attribute is an identifier of a corresponding service and may refer to a corresponding service of USBD / USD.
  • the RS element may describe information on ROUTE sessions through which service components of a corresponding service are delivered. Depending on the number of such ROUTE sessions, there may be a plurality of these elements.
  • the RS element may further include an @bsid attribute, an @sIpAddr attribute, an @dIpAddr attribute, an @dport attribute, an @PLPID attribute, and / or an LS element.
  • the @bsid attribute may be an identifier of a broadcast stream through which service components of a corresponding service are delivered. If this field is omitted, the default broadcast stream may be a broadcast stream that includes a PLP that carries the SLS of the service. The value of this field may be the same value as the @bsid attribute of SLT.
  • the @sIpAddr attribute, the @dIpAddr attribute, and the @dport attribute may indicate a source IP address, a destination IP address, and a destination UDP port of the corresponding ROUTE session, respectively. If these fields are omitted, the default values may be the source IP address, destination IP address, and destination UDP port values of the current, ROUTE session carrying that SLS, that is, carrying that S-TSID. For other ROUTE sessions that carry service components of the service but not the current ROUTE session, these fields may not be omitted.
  • the @PLPID attribute may indicate PLP ID information of a corresponding ROUTE session. If this field is omitted, the default value may be the PLP ID value of the current PLP to which the corresponding S-TSID is being delivered. According to an embodiment, this field is omitted, and the PLP ID information of the corresponding ROUTE session may be confirmed by combining information in the LMT to be described later and IP address / UDP port information of the RS element.
  • the LS element may describe information on LCT channels through which service components of a corresponding service are delivered. Depending on the number of such LCT channels, there may be a plurality of these elements.
  • the LS element may include an @tsi attribute, an @PLPID attribute, an @bw attribute, an @startTime attribute, an @endTime attribute, an SrcFlow element, and / or a RepairFlow element.
  • the @tsi attribute may represent tsi information of a corresponding LCT channel. Through this, LCT channels through which a service component of a corresponding service is delivered may be identified.
  • the @PLPID attribute may represent PLP ID information of a corresponding LCT channel. In some embodiments, this field may be omitted.
  • the @bw attribute may indicate the maximum bandwidth of the corresponding LCT channel.
  • the @startTime attribute may indicate the start time of the LCT session, and the @endTime attribute may indicate the end time of the LCT channel.
  • the SrcFlow element may describe the source flow of ROUTE.
  • the source protocol of ROUTE is used to transmit the delivery object, and can establish at least one source flow in one ROUTE session. These source flows can deliver related objects as an object flow.
  • the RepairFlow element may describe the repair flow of ROUTE. Delivery objects delivered according to the source protocol may be protected according to Forward Error Correction (FEC).
  • FEC Forward Error Correction
  • the repair protocol may define a FEC framework that enables such FEC protection.
  • FIG. 5 is a diagram illustrating a USBD delivered to MMT according to an embodiment of the present invention.
  • One embodiment of the illustrated USBD may have a bundleDescription root element.
  • the bundleDescription root element may have a userServiceDescription element.
  • the userServiceDescription element may be an instance of one service.
  • the userServiceDescription element may include an @globalServiceID attribute, an @serviceId attribute, a Name element, a serviceLanguage element, a content advisoryRating element, a Channel element, an mpuComponent element, a routeComponent element, a broadbandComponent element, and / or a ComponentInfo element.
  • Each field may be omitted or may exist in plurality, depending on the value of the illustrated Use column.
  • the @globalServiceID attribute, the @serviceId attribute, the Name element and / or the serviceLanguage element may be the same as the corresponding fields of the USBD delivered to the above-described ROUTE.
  • the contentAdvisoryRating element may indicate the content advisory rating of the corresponding service. This information may be compatible with the content advisory rating information format provided by the service announcement.
  • the channel element may include information related to the corresponding service. The detail of this element is mentioned later.
  • the mpuComponent element may provide a description for service components delivered as an MPU of a corresponding service.
  • This element may further include an @mmtPackageId attribute and / or an @nextMmtPackageId attribute.
  • the @mmtPackageId attribute may refer to an MMT package of service components delivered as an MPU of a corresponding service.
  • the @nextMmtPackageId attribute may refer to an MMT package to be used next to the MMT package referenced by the @mmtPackageId attribute in time.
  • the MP table can be referenced through the information of this element.
  • the routeComponent element may include a description of service components of the corresponding service delivered to ROUTE. Even if the linear service components are delivered in the MMT protocol, the NRT data may be delivered according to the ROUTE protocol as described above. This element may describe information about such NRT data. The detail of this element is mentioned later.
  • the broadbandComponent element may include a description of service components of the corresponding service delivered over broadband.
  • some service components or other files of a service may be delivered over broadband. This element may describe information about these data.
  • This element may further include the @fullMPDUri attribute. This attribute may refer to an MPD that describes service components delivered over broadband.
  • the element when the broadcast signal is weakened due to driving in a tunnel or the like, the element may be needed to support handoff between the broadcast network and the broadband band. When the broadcast signal is weakened, while acquiring the service component through broadband, and when the broadcast signal is stronger, the service continuity may be guaranteed by acquiring the service component through the broadcast network.
  • the ComponentInfo element may include information on service components of a corresponding service. Depending on the number of service components of the service, there may be a plurality of these elements. This element may describe information such as the type, role, name, identifier, and protection of each service component. Detailed information on this element will be described later.
  • the aforementioned channel element may further include an @serviceGenre attribute, an @serviceIcon attribute, and / or a ServiceDescription element.
  • the @serviceGenre attribute may indicate the genre of the corresponding service
  • the @serviceIcon attribute may include URL information of an icon representing the corresponding service.
  • the ServiceDescription element provides a service description of the service, which may further include an @serviceDescrText attribute and / or an @serviceDescrLang attribute. Each of these attributes may indicate the text of the service description and the language used for that text.
  • the aforementioned routeComponent element may further include an @sTSIDUri attribute, an @sTSIDDestinationIpAddress attribute, an @sTSIDDestinationUdpPort attribute, an @sTSIDSourceIpAddress attribute, an @sTSIDMajorProtocolVersion attribute, and / or an @sTSIDMinorProtocolVersion attribute.
  • the @sTSIDUri attribute may refer to an S-TSID fragment. This field may be the same as the corresponding field of USBD delivered to ROUTE described above. This S-TSID may provide access related information for service components delivered in ROUTE. This S-TSID may exist for NRT data delivered according to the ROUTE protocol in the situation where linear service components are delivered according to the MMT protocol.
  • the @sTSIDDestinationIpAddress attribute, the @sTSIDDestinationUdpPort attribute, and the @sTSIDSourceIpAddress attribute may indicate a destination IP address, a destination UDP port, and a source IP address of a transport packet carrying the aforementioned S-TSID, respectively. That is, these fields may identify a transport session (MMTP session or ROUTE session) carrying the aforementioned S-TSID.
  • the @sTSIDMajorProtocolVersion attribute and the @sTSIDMinorProtocolVersion attribute may indicate a major version number and a minor version number of the transport protocol used to deliver the aforementioned S-TSID.
  • ComponentInfo element may further include an @componentType attribute, an @componentRole attribute, an @componentProtectedFlag attribute, an @componentId attribute, and / or an @componentName attribute.
  • the @componentType attribute may indicate the type of the corresponding component. For example, this property may indicate whether the corresponding component is an audio, video, or closed caption component.
  • the @componentRole attribute can indicate the role (role) of the corresponding component. For example, this property can indicate whether the main audio, music, commentary, etc., if the corresponding component is an audio component. If the corresponding component is a video component, it may indicate whether it is primary video. If the corresponding component is a closed caption component, it may indicate whether it is a normal caption or an easy reader type.
  • the @componentProtectedFlag attribute may indicate whether a corresponding service component is protected, for example, encrypted.
  • the @componentId attribute may represent an identifier of a corresponding service component.
  • the value of this attribute may be a value such as asset_id (asset ID) of the MP table corresponding to this service component.
  • the @componentName attribute may represent the name of the corresponding service component.
  • FIG. 6 illustrates a link layer operation according to an embodiment of the present invention.
  • the link layer may be a layer between the physical layer and the network layer.
  • the transmitter may transmit data from the network layer to the physical layer
  • the receiver may transmit data from the physical layer to the network layer (t6010).
  • the purpose of the link layer may be to compress all input packet types into one format for processing by the physical layer, to ensure flexibility and future scalability for input packet types not yet defined. have.
  • the link layer may provide an option of compressing unnecessary information in the header of the input packet, so that the input data may be efficiently transmitted. Operations such as overhead reduction and encapsulation of the link layer may be referred to as a link layer protocol, and a packet generated using the corresponding protocol may be referred to as a link layer packet.
  • the link layer may perform functions such as packet encapsulation, overhead reduction, and / or signaling transmission.
  • the link layer ALP may perform an overhead reduction process on input packets and then encapsulate them into link layer packets.
  • the link layer may encapsulate the link layer packet without performing an overhead reduction process.
  • the use of the link layer protocol can greatly reduce the overhead for data transmission on the physical layer, and the link layer protocol according to the present invention can provide IP overhead reduction and / or MPEG-2 TS overhead reduction. have.
  • the link layer may sequentially perform IP header compression, adaptation, and / or encapsulation. In some embodiments, some processes may be omitted.
  • the RoHC module performs IP packet header compression to reduce unnecessary overhead, and context information may be extracted and transmitted out of band through an adaptation process.
  • the IP header compression and adaptation process may be collectively called IP header compression.
  • IP packets may be encapsulated into link layer packets through an encapsulation process.
  • the link layer may sequentially perform an overhead reduction and / or encapsulation process for the TS packet. In some embodiments, some processes may be omitted.
  • the link layer may provide sync byte removal, null packet deletion and / or common header removal (compression).
  • Sync byte elimination can provide overhead reduction of 1 byte per TS packet. Null packet deletion can be performed in a manner that can be reinserted at the receiving end. In addition, common information between successive headers can be deleted (compressed) in a manner that can be recovered at the receiving side. Some of each overhead reduction process may be omitted. Thereafter, TS packets may be encapsulated into link layer packets through an encapsulation process.
  • the link layer packet structure for encapsulation of TS packets may be different from other types of packets.
  • IP header compression will be described.
  • the IP packet has a fixed header format, but some information required in a communication environment may be unnecessary in a broadcast environment.
  • the link layer protocol may provide a mechanism to reduce broadcast overhead by compressing the header of the IP packet.
  • IP header compression may include a header compressor / decompressor and / or adaptation module.
  • the IP header compressor (RoHC compressor) may reduce the size of each IP packet header based on the RoHC scheme.
  • the adaptation module may then extract the context information and generate signaling information from each packet stream.
  • the receiver may parse signaling information related to the packet stream and attach context information to the packet stream.
  • the RoHC decompressor can reconstruct the original IP packet by recovering the packet header.
  • IP header compression may mean only IP header compression by a header compressor, or may mean a concept in which the IP header compression and the adaptation process by the adaptation module are combined. The same is true for decompressing.
  • the adaptation function may generate link layer signaling using context information and / or configuration parameters.
  • the adaptation function may periodically send link layer signaling over each physical frame using previous configuration parameters and / or context information.
  • the context information is extracted from the compressed IP packets, and various methods may be used according to the adaptation mode.
  • Mode # 1 is a mode in which no operation is performed on the compressed packet stream, and may be a mode in which the adaptation module operates as a buffer.
  • Mode # 2 may be a mode for extracting context information (static chain) by detecting IR packets in the compressed packet stream. After extraction, the IR packet is converted into an IR-DYN packet, and the IR-DYN packet can be transmitted in the same order in the packet stream by replacing the original IR packet.
  • context information static chain
  • Mode # 3 t6020 may be a mode for detecting IR and IR-DYN packets and extracting context information from the compressed packet stream.
  • Static chains and dynamic chains can be extracted from IR packets and dynamic chains can be extracted from IR-DYN packets.
  • the IR and IR-DYN packets can be converted into regular compressed packets.
  • the switched packets can be sent in the same order within the packet stream, replacing the original IR and IR-DYN packets.
  • the remaining packets after the context information is extracted may be encapsulated and transmitted according to the link layer packet structure for the compressed IP packet.
  • the context information may be transmitted by being encapsulated according to a link layer packet structure for signaling information as link layer signaling.
  • the extracted context information may be included in the RoHC-U Description Table (RTT) and transmitted separately from the RoHC packet flow.
  • the context information may be transmitted through a specific physical data path along with other signaling information.
  • a specific physical data path may mean one of general PLPs, a PLP to which LLS (Low Level Signaling) is delivered, a dedicated PLP, or an L1 signaling path. path).
  • the RDT may be signaling information including context information (static chain and / or dynamic chain) and / or information related to header compression.
  • the RDT may be transmitted whenever the context information changes.
  • the RDT may be transmitted in every physical frame. In order to transmit the RDT in every physical frame, a previous RDT may be re-use.
  • the receiver may first select PLP to acquire signaling information such as SLT, RDT, LMT, and the like. When the signaling information is obtained, the receiver may combine these to obtain a mapping between the service-IP information-context information-PLP. That is, the receiver can know which service is transmitted to which IP streams, which IP streams are delivered to which PLP, and can also obtain corresponding context information of the PLPs. The receiver can select and decode a PLP carrying a particular packet stream. The adaptation module can parse the context information and merge it with the compressed packets. This allows the packet stream to be recovered, which can be delivered to the RoHC decompressor. Decompression can then begin.
  • signaling information such as SLT, RDT, LMT, and the like.
  • the receiver may combine these to obtain a mapping between the service-IP information-context information-PLP. That is, the receiver can know which service is transmitted to which IP streams, which IP streams are delivered to which PLP, and can also obtain corresponding context information of the PLPs.
  • the receiver detects the IR packet and starts decompression from the first received IR packet according to the adaptation mode (mode 1), or detects the IR-DYN packet to perform decompression from the first received IR-DYN packet.
  • the link layer protocol may encapsulate all types of input packets, such as IP packets and TS packets, into link layer packets. This allows the physical layer to process only one packet format independently of the protocol type of the network layer (here, consider MPEG-2 TS packet as a kind of network layer packet). Each network layer packet or input packet is transformed into a payload of a generic link layer packet.
  • Segmentation may be utilized in the packet encapsulation process. If the network layer packet is too large to be processed by the physical layer, the network layer packet may be divided into two or more segments.
  • the link layer packet header may include fields for performing division at the transmitting side and recombination at the receiving side. Each segment may be encapsulated into a link layer packet in the same order as the original position.
  • Concatenation may also be utilized in the packet encapsulation process. If the network layer packet is small enough that the payload of the link layer packet includes several network layer packets, concatenation may be performed.
  • the link layer packet header may include fields for executing concatenation. In the case of concatenation, each input packet may be encapsulated into the payload of the link layer packet in the same order as the original input order.
  • the link layer packet may include a header and a payload, and the header may include a base header, an additional header, and / or an optional header.
  • the additional header may be added depending on the chaining or splitting, and the additional header may include necessary fields according to the situation.
  • an optional header may be further added to transmit additional information.
  • Each header structure may be predefined. As described above, when the input packet is a TS packet, a link layer header structure different from other packets may be used.
  • Link layer signaling may operate at a lower level than the IP layer.
  • the receiving side can acquire the link layer signaling faster than the IP level signaling such as LLS, SLT, SLS, and the like. Therefore, link layer signaling may be obtained before session establishment.
  • Link layer signaling may include internal link layer signaling and external link layer signaling.
  • Internal link layer signaling may be signaling information generated in the link layer.
  • the above-described RDT or LMT to be described later may correspond to this.
  • the external link layer signaling may be signaling information received from an external module, an external protocol, or an upper layer.
  • the link layer may encapsulate link layer signaling into a link layer packet and deliver it.
  • a link layer packet structure (header structure) for link layer signaling may be defined, and link layer signaling information may be encapsulated according to this structure.
  • FIG. 7 illustrates a link mapping table (LMT) according to an embodiment of the present invention.
  • the LMT may provide a list of higher layer sessions carried by the PLP.
  • the LMT may also provide additional information for processing link layer packets carrying higher layer sessions.
  • the higher layer session may be called multicast.
  • Information on which IP streams and which transport sessions are being transmitted through a specific PLP may be obtained through the LMT. Conversely, information on which PLP a specific transport session is delivered to may be obtained.
  • the LMT may be delivered to any PLP identified as carrying an LLS.
  • the PLP through which the LLS is delivered may be identified by the LLS flag of the L1 detail signaling information of the physical layer.
  • the LLS flag may be a flag field indicating whether LLS is delivered to the corresponding PLP for each PLP.
  • the L1 detail signaling information may correspond to PLS2 data to be described later.
  • the LMT may be delivered to the same PLP together with the LLS.
  • Each LMT may describe the mapping between PLPs and IP address / port as described above.
  • the LLS may include an SLT, where these IP addresses / ports described by the LMT are all IP addresses associated with any service described by the SLT forwarded to the same PLP as that LMT. It can be / ports.
  • the PLP identifier information in the above-described SLT, SLS, etc. may be utilized, so that information on which PLP the specific transmission session indicated by the SLT, SLS is transmitted may be confirmed.
  • the PLP identifier information in the above-described SLT, SLS, etc. may be omitted, and the PLP information for the specific transport session indicated by the SLT, SLS may be confirmed by referring to the information in the LMT.
  • the receiver may identify the PLP to know by combining LMT and other IP level signaling information.
  • PLP information in SLT, SLS, and the like is not omitted, and may remain in the SLT, SLS, and the like.
  • the LMT according to the illustrated embodiment may include a signaling_type field, a PLP_ID field, a num_session field, and / or information about respective sessions.
  • a PLP loop may be added to the LMT according to an embodiment, so that information on a plurality of PLPs may be described.
  • the LMT may describe PLPs for all IP addresses / ports related to all services described by the SLTs delivered together, in a PLP loop.
  • the signaling_type field may indicate the type of signaling information carried by the corresponding table.
  • the value of the signaling_type field for the LMT may be set to 0x01.
  • the signaling_type field may be omitted.
  • the PLP_ID field may identify a target PLP to be described. When a PLP loop is used, each PLP_ID field may identify each target PLP. From the PLP_ID field may be included in the PLP loop.
  • the PLP_ID field mentioned below is an identifier for one PLP in a PLP loop, and the fields described below may be fields for the corresponding PLP.
  • the num_session field may indicate the number of upper layer sessions delivered to the PLP identified by the corresponding PLP_ID field. According to the number indicated by the num_session field, information about each session may be included. This information may include an src_IP_add field, a dst_IP_add field, a src_UDP_port field, a dst_UDP_port field, a SID_flag field, a compressed_flag field, a SID field, and / or a context_id field.
  • the src_IP_add field, dst_IP_add field, src_UDP_port field, and dst_UDP_port field are the source IP address, destination IP address, source UDP port, destination UDP port for the transport session among the upper layer sessions forwarded to the PLP identified by the corresponding PLP_ID field. It can indicate a port.
  • the SID_flag field may indicate whether a link layer packet carrying a corresponding transport session has an SID field in its optional header.
  • a link layer packet carrying an upper layer session may have an SID field in its optional header, and the SID field value may be the same as an SID field in an LMT to be described later.
  • the compressed_flag field may indicate whether header compression has been applied to data of a link layer packet carrying a corresponding transport session.
  • the existence of the context_id field to be described later may be determined according to the value of this field.
  • the SID field may indicate a sub stream ID (SID) for link layer packets carrying a corresponding transport session.
  • SID sub stream ID
  • These link layer packets may include an SID having the same value as this SID field in the optional header.
  • the context_id field may provide a reference to a context id (CID) in the RDT.
  • the CID information of the RDT may indicate the context ID for the corresponding compressed IP packet stream.
  • the RDT may provide context information for the compressed IP packet stream. RDT and LMT may be associated with this field.
  • each field, element, or attribute may be omitted or replaced by another field, and additional fields, elements, or attributes may be added according to an embodiment. .
  • service components of one service may be delivered through a plurality of ROUTE sessions.
  • the SLS may be obtained through the bootstrap information of the SLT.
  • the SLS's USBD allows the S-TSID and MPD to be referenced.
  • the S-TSID may describe transport session description information for other ROUTE sessions to which service components are delivered, as well as a ROUTE session to which an SLS is being delivered.
  • all service components delivered through a plurality of ROUTE sessions may be collected. This may be similarly applied when service components of a service are delivered through a plurality of MMTP sessions.
  • one service component may be used simultaneously by a plurality of services.
  • bootstrapping for ESG services may be performed by a broadcast network or broadband.
  • URL information of the SLT may be utilized. ESG information and the like can be requested to this URL.
  • one service component of one service may be delivered to the broadcasting network and one to the broadband (hybrid).
  • the S-TSID may describe components delivered to a broadcasting network, so that a ROUTE client may acquire desired service components.
  • USBD also has base pattern information, which allows you to describe which segments (which components) are to be routed to which path. Therefore, the receiver can use this to know what segment to request to the broadband server and what segment to find in the broadcast stream.
  • scalable coding for a service may be performed.
  • the USBD may have all the capability information needed to render the service. For example, when a service is provided in HD or UHD, the capability information of the USBD may have a value of “HD or UHD”.
  • the receiver may know which component should be played in order to render the UHD or HD service using the MPD.
  • app components to be used for app-based enhancement / app-based service may be delivered through a broadcast network or through broadband as an NRT component.
  • app signaling for app-based enhancement may be performed by an application signaling table (AST) delivered with SLS.
  • an event which is a signaling of an operation to be performed by the app, may be delivered in the form of an event message table (EMT) with SLS, signaled in an MPD, or in-band signaled in a box in a DASH representation. . AST, EMT, etc. may be delivered via broadband.
  • App-based enhancement may be provided using the collected app components and such signaling information.
  • a CAP message may be included in the aforementioned LLS table for emergency alerting. Rich media content for emergency alerts may also be provided. Rich media may be signaled by the CAP message, and if rich media is present it may be provided as an EAS service signaled by the SLT.
  • the linear service components may be delivered through a broadcasting network according to the MMT protocol.
  • NRT data for example, an app component
  • data on the service may be delivered through a broadcasting network according to the ROUTE protocol.
  • data on the service may be delivered through broadband.
  • the receiver can access the MMTP session carrying the SLS using the bootstrap information of the SLT.
  • the USBD of the SLS according to the MMT may refer to the MP table so that the receiver may acquire linear service components formatted with the MPU delivered according to the MMT protocol.
  • the USBD may further refer to the S-TSID to allow the receiver to obtain NRT data delivered according to the ROUTE protocol.
  • the USBD may further reference the MPD to provide a playback description for the data delivered over the broadband.
  • the receiver may transmit location URL information for obtaining a streaming component and / or a file content item (such as a file) to the companion device through a method such as a web socket.
  • An application of a companion device may request the component, data, and the like by requesting the URL through an HTTP GET.
  • the receiver may transmit information such as system time information and emergency alert information to the companion device.
  • FIG. 8 shows a structure of a broadcast signal transmission apparatus for a next generation broadcast service according to an embodiment of the present invention.
  • a broadcast signal transmission apparatus for a next generation broadcast service includes an input format block 1000, a bit interleaved coding & modulation (BICM) block 1010, and a frame building block 1020, orthogonal frequency division multiplexing (OFDM) generation block (OFDM generation block) 1030, and signaling generation block 1040. The operation of each block of the broadcast signal transmission apparatus will be described.
  • BICM bit interleaved coding & modulation
  • OFDM generation block orthogonal frequency division multiplexing
  • signaling generation block 1040 The operation of each block of the broadcast signal transmission apparatus will be described.
  • IP streams / packets and MPEG2-TS may be main input formats, and other stream types are treated as general streams.
  • the input format block 1000 can demultiplex each input stream into one or multiple data pipes to which independent coding and modulation is applied.
  • the data pipe is the basic unit for controlling robustness, which affects the quality of service (QoS).
  • QoS quality of service
  • One or multiple services or service components may be delivered by one data pipe.
  • a data pipe is a logical channel at the physical layer that carries service data or related metadata that can carry one or multiple services or service components.
  • the BICM block 1010 may include a processing block applied to a profile (or system) to which MIMO is not applied and / or a processing block of a profile (or system) to which MIMO is applied, and for processing each data pipe. It may include a plurality of processing blocks.
  • the processing block of the BICM block to which MIMO is not applied may include a data FEC encoder, a bit interleaver, a constellation mapper, a signal space diversity (SSD) encoding block, and a time interleaver.
  • the processing block of the BICM block to which MIMO is applied is distinguished from the processing block of BICM to which MIMO is not applied in that it further includes a cell word demultiplexer and a MIMO encoding block.
  • the data FEC encoder performs FEC encoding on the input BBF to generate the FECBLOCK procedure using outer coding (BCH) and inner coding (LDPC).
  • Outer coding (BCH) is an optional coding method.
  • the bit interleaver interleaves the output of the data FEC encoder to achieve optimized performance with a combination of LDPC codes and modulation schemes.
  • Constellation Mapper uses QPSK, QAM-16, non-uniform QAM (NUQ-64, NUQ-256, NUQ-1024) or non-uniform constellation (NUC-16, NUC-64, NUC-256, NUC-1024)
  • the cell word from the bit interleaver or cell word demultiplexer can then be modulated to provide a power-normalized constellation point.
  • NUQ has any shape, while QAM-16 and NUQ have a square shape. Both NUQ and NUC are specifically defined for each code rate and are signaled by the parameter DP_MOD of PLS2 data.
  • the time interleaver may operate at the data pipe level. The parameters of time interleaving can be set differently for each data pipe.
  • the time interleaver of the present invention may be located between a BICM chain block and a frame builder.
  • the time interleaver according to the present invention may selectively use a convolution interleaver (CI) and a block interleaver (BI) according to a physical layer pipe (PLP) mode, or both.
  • PLP according to an embodiment of the present invention is a physical path used in the same concept as the above-described DP, the name can be changed according to the designer's intention.
  • the PLP mode according to an embodiment of the present invention may include a single PLP mode or a multiple PLP mode according to the number of PLPs processed by the broadcast signal transmitter or the broadcast signal transmitter.
  • time interleaving using different time interleaving methods according to the PLP mode may be referred to as hybrid time interleaving.
  • the hybrid time deinterleaver may perform an operation corresponding to the reverse operation of the aforementioned hybrid time interleaver.
  • the cell word demultiplexer is used to separate a single cell word stream into a dual cell word stream for MIMO processing.
  • the MIMO encoding block can process the output of the cell word demultiplexer using the MIMO encoding scheme.
  • the MIMO encoding scheme of the present invention may be defined as full-rate spatial multiplexing (FR-SM) to provide capacity increase with a relatively small complexity increase at the receiver side.
  • MIMO processing is applied at the data pipe level. NUQ (e 1, i ), the pair of constellation mapper outputs And e 2, i are fed to the input of the MIMO encoder, the MIMO encoder output pairs g1, i and g2, i are transmitted by the same carrier k and OFDM symbol l of each transmit antenna.
  • the frame building block 1020 may map data cells of an input data pipe to OFDM symbols and perform frequency interleaving for frequency domain diversity within one frame.
  • a frame according to an embodiment of the present invention is divided into a preamble, one or more frame signaling symbols (FSS), and normal data symbols.
  • the preamble is a special symbol that provides a set of basic transmission parameters for efficient transmission and reception of a signal.
  • the preamble may signal a basic transmission parameter and a transmission type of the frame.
  • the preamble may indicate whether an emergency alert service (EAS) is provided in the current frame.
  • EAS emergency alert service
  • the main purpose of the FSS is to carry PLS data. For fast synchronization and channel estimation, and fast decoding of PLS data, the FSS has a higher density pilot pattern than normal data symbols.
  • the frame building block adjusts the timing between the data pipes and the corresponding PLS data so that a delay compensation block is provided at the transmitter to ensure co-time between the data pipes and the corresponding PLS data.
  • a cell mapper and a frequency interleaver for mapping a PLS, a data pipe, an auxiliary stream, and a dummy cell to an active carrier of an OFDM symbol in a frame.
  • the frequency interleaver may provide frequency diversity by randomly interleaving data cells received from the cell mapper.
  • the frequency interleaver uses a different interleaving seed order to obtain the maximum interleaving gain in a single frame.
  • the frequency interleaver uses a single symbol or data corresponding to an OFDM symbol pair consisting of two sequential OFDM symbols. Operate on corresponding data.
  • OFDM generation block 1030 modulates the OFDM carrier, inserts pilots, and generates time-domain signals for transmission by the cells generated by the frame building block. In addition, the block sequentially inserts a guard interval and applies a PAPR reduction process to generate a final RF signal.
  • the signaling generation block 1040 may generate physical layer signaling information used for the operation of each functional block.
  • Signaling information may include PLS data.
  • PLS provides a means by which a receiver can connect to a physical layer data pipe.
  • PLS data consists of PLS1 data and PLS2 data.
  • PLS1 data is the first set of PLS data delivered to the FSS in frames with fixed size, coding, and modulation that convey basic information about the system as well as the parameters needed to decode the PLS2 data.
  • PLS1 data provides basic transmission parameters including the parameters required to enable reception and decoding of PLS2 data.
  • PLS2 data carries more detailed PLS data about the data pipes and systems and is the second set of PLS data sent to the FSS.
  • PLS2 signaling further consists of two types of parameters: PLS2 static data (PLS2-STAT data) and PLS2 dynamic data (PLS2-DYN data).
  • PLS2 static data is PLS2 data that is static during the duration of a frame group
  • PLS2 dynamic data is PLS2 data that changes dynamically from frame to frame.
  • the PLS2 data may include FIC_FLAG information.
  • FIC Fast Information Channel
  • the FIC_FLAG information is a 1-bit field and indicates whether a fast information channel (FIC) is used in the current frame group.If the value of this field is set to 1, the FIC is provided in the current frame. If the value of the field is set to 0, the FIC is not transmitted in the current frame.
  • the BICM block 1010 may include a BICM block for protecting PLS data
  • the BICM block for protecting PLS data is a PLS FEC encoder. , Bit interleaver, and constellation mapper.
  • the PLS FEC encoder performs external encoding on scrambled PLS 1,2 data using a scrambler for scrambling PLS1 data and PLS2 data, shortened BCH code for PLS protection, and a BCH for inserting zero bits after BCH encoding.
  • An encoding / zero insertion block, an LDPC encoding block for performing encoding using an LDPC code, and an LDPC parity puncturing block may be included.
  • the output bits of zero insertion can be permutated before LDPC encoding.
  • the bit interleaver interleaves the respective shortened and punctured PLS1 data and PLS2 data, and the constellation mapper bit interleaves.
  • the PLS1 data and the PLS2 data can be mapped to the constellation.
  • the broadcast signal receiving apparatus for the next generation broadcast service may perform a reverse process of the broadcast signal transmitting apparatus for the next generation broadcast service described with reference to FIG. 8.
  • An apparatus for receiving broadcast signals for a next generation broadcast service includes a synchronization and demodulation module for performing demodulation corresponding to a reverse process of a procedure executed by a broadcast signal transmitting apparatus and an input signal.
  • a frame parsing module for parsing a frame, extracting data on which a service selected by a user is transmitted, converting an input signal into bit region data, and then deinterleaving the bit region data as necessary, and transmitting efficiency
  • a demapping and decoding module for performing demapping on the mapping applied for decoding, and correcting an error occurring in a transmission channel through decoding, of various compression / signal processing procedures applied by a broadcast signal transmission apparatus.
  • Demodulated by an output processor and a synchronization and demodulation module that executes the inverse process It may include a signaling decoding module for obtaining and processing the PLS information from the signal.
  • the frame parsing module, the demapping and decoding module, and the output processor may execute the function by using the PLS data output from the signaling decoding module.
  • a time interleaving group according to an embodiment of the present invention is directly mapped to one frame or spread over P I frames.
  • Each time interleaving group is further divided into one or more (N TI ) time interleaving blocks.
  • each time interleaving block corresponds to one use of the time interleaver memory.
  • the time interleaving block in the time interleaving group may include different numbers of XFECBLOCKs.
  • the time interleaver may also act as a buffer for data pipe data prior to the frame generation process.
  • the time interleaver according to an embodiment of the present invention is a twisted row-column block interleaver.
  • the twisted row-column block interleaver according to an embodiment of the present invention writes the first XFECBLOCK in the column direction to the first column of the time interleaving memory, the second XFECBLOCK to the next column and the remaining XFECBLOCKs in the time interleaving block in the same manner. You can fill in these. And in an interleaving array, cells can be read diagonally from the first row to the last row (starting from the leftmost column to the right along the row).
  • the interleaving array for the twisted row-column block interleaver may insert the virtual XFECBLOCK into the time interleaving memory to achieve a single memory deinterleaving at the receiver side regardless of the number of XFECBLOCKs in the time interleaving block.
  • the virtual XFECBLOCK must be inserted in front of the other XFECBLOCKs to achieve a single memory deinterleaving on the receiver side.
  • FIG 9 illustrates a writing operation of a time interleaver according to an embodiment of the present invention.
  • the block shown on the left side of the figure represents a TI memory address array, and the block shown on the right side of the figure shows that virtual FEC blocks are placed at the front of the TI group for two consecutive TI groups. It represents the writing operation when two and one are inserted respectively.
  • the frequency interleaver may include an interleaving address generator for generating an interleaving address for applying to data corresponding to a symbol pair.
  • FIG. 10 is a block diagram of an interleaving address generator composed of a main-PRBS generator and a sub-PRBS generator according to each FFT mode included in a frequency interleaver according to an embodiment of the present invention.
  • the interleaving process for an OFDM symbol pair uses one interleaving sequence and is described as follows.
  • x m, l, p is the p th cell of the l th OFDM symbol in the m th frame
  • N data is the number of data cells.
  • H l (p) is an interleaving address generated based on the cyclic shift value (symbol offset) of the PRBS generator and the sub-PRBS generator.
  • the input packet input to the link layer may be an IP packet processed based on the IP / UDP / ROUTE protocol.
  • each IP packet may include an IP header, a UDP header, and an LCT header.
  • the header of such an IP packet may be compressed at the link layer.
  • the compression (RoHC compression) for the IP / UDP header of the IP packet may follow the RoHC scheme described above with reference to FIG. 6.
  • compression of the LCT header (LCT header compression) of the IP packet may be performed in the link layer, and the LCT header compression may use a method different from the RoHC compression.
  • a method of performing LCT header compression in a link layer will be described with reference to FIGS. 11 to 21.
  • FIG. 11 shows a header structure of an LCT packet according to an embodiment of the present invention.
  • the LCT packet header of the embodiment of FIG. 11 may be, for example, a File Delivery over Unidi-rectional Transport (FLUTE) protocol for file delivery, or a header of an LCT packet used in a ROUTE protocol.
  • FLUTE File Delivery over Unidi-rectional Transport
  • the LCT packet header includes an LCT version number (V) field, a control control flag (C) field, a protocol-specific indication (PSI) field, a transport session identifier flag (S) field, and a transport object identifier flag.
  • (O) field half-word flag (H) field, close session flag (A) field, close object flag (B) field, LCT header length (HDR_LEN) field, codepoint (CP) field, conference control information (CCI) field, transport session identifier (TSI) field and / or transport object identifier (TOI) field. Description of each field is as follows.
  • the V field is a 4-bit field and may indicate a protocol version number, for example, an LCT version number.
  • the LCT version number field may be referred to as a version number field or a version field.
  • Control Control Flag (C) field A 2-bit field.
  • the first value of the C field may indicate that the control control information (CCI) field is 32 bits long.
  • the second value of the C field may indicate that the CCI field is 64 bits long.
  • the value of the C field is a third value (eg, 2)
  • the third value of the C field may indicate that the CCI field is 96 bits long.
  • the value of the C field is the fourth value (eg, 3)
  • the third value of the C field may indicate that the CCI field is 128 bits long.
  • Protocol-specific indication (PSI) field A 2-bit field. If yes, the usage of these bits can be specific to each protocol instantiation using the LCT building block. If protocol-instantiation-specific use of these bits is not defined, the sender should set them to zero and the receiver should ignore these bits.
  • PSI Protocol-specific indication
  • Transport session identifier flag (S) field A field of 1 bit.
  • the S field may be the number of full 32-bit words in the TSI field.
  • the TSI field may be a length of '32 * S + 16 * H 'bits. That is, the length may be one of 0 bits, 16 bits, 32 bits or 48 bits.
  • Transport Object Identifier Flag (O) field A 2-bit field.
  • the O field may be the number of full 32-bit words in the TOI field.
  • the TOI field may be a length of '32 * O + 16 * H 'bits. That is, the length may be one of 0 bits, 16 bits, 32 bits, 48 bits, 80 bits, 96 bits, or 112 bits.
  • Half-Word Flag (H) Field The TSI field and the TOI field may both be multiples of 32 bits plus '16 * H 'bits.
  • the H field may allow the TSI field and the TOI field to be a multiple of half word (16 bits), but the aggregate length of the TSI field and the TOI field may be a multiple of 32 bits.
  • Close session flag (A) field 1 bit field.
  • the A field may be set to zero. If the end of packet transmission for the session is imminent, the transmitter may set the A field to a first value (eg, 1). The A field may be set to 1 only in the last packet sent for the session, or the A field may be set to 1 in the last few seconds of packets sent for the session. Once the transmitter sets the A field to 1 in one packet, the transmitter must set the A field to 1 in all subsequent packets until the packet transmission for the session is terminated.
  • a received packet with an A field set to 1 may instruct the receiver to immediately stop sending the packets for the session. When the receiver receives a packet with the A field set to 1, the receiver should assume that no more packets will be sent in the session.
  • Close object flag (B) field 1 bit field.
  • the B field may be set to zero. If the end of packet transmission for the object is imminent, the transmitter may set the B field to a first value (eg, 1). If the TOI field is in use and the B field is set to 1, the end of transmission for the object identified by the TOI field may be imminent. If the TOI field is not in use and the B field is set to 1, the end of transmission for one object in the session identified by out-of-band information may be imminent.
  • the B field may be set to 1 only within the last packet sent for the object, or the B field may be set to 1 in the last few seconds that packets were sent for the object.
  • the transmitter sets the B field to 1 in one packet for a particular object, the transmitter must set the B field to 1 in all subsequent packets until the packet transmission for the object is terminated.
  • a received packet with a B field set to 1 may instruct the receiver to immediately stop sending the packets for the object.
  • the receiver receives a packet with a B field set to 1, the receiver should assume that no more packets will be sent for the object in the session.
  • LCT Header Length (HDR_LEN) field 8-bit field. This field may be the total length of the LCT header in 32-bit word units. The length of the LCT header must be a multiple of 32 bits. This field is directly in the portion of the packet that is beyond the LCT header, i.e. in the first other header if present, or in the packet payload if no other header is present, or at the end of the packet if no other headers and packet payload are present. Can be used for access.
  • Code Point (CP) field 8-bit field.
  • the CP field may be an opaque identifier passed to the packet payload decoder to convey information about the codec used for the packet payload.
  • the mapping between codepoints and actual codecs can be defined on a per session basis and communicated out of band as part of the session description information.
  • the use of the CP field may be similar to the payload type (PT) field in the RTP header, as described in the RFC3550 standard.
  • Control Control Information (CCI) field A field of 32, 64, 96, or 128 bits.
  • the CCI field may be used to carry the control control information.
  • the control control information may include a layer number, a logical channel number, and a sequence number.
  • the CCI field may be opaque for the purpose of this specification.
  • the C field is the first value (eg, 0)
  • the CCI field must be 32 bits.
  • the C field is the second value (eg, 1)
  • the CCI field must be 64 bits.
  • the C field is a third value (eg, 2)
  • the CCI field should be 96 bits.
  • the C field is the fourth value (eg, 3)
  • the CCI field should be 128 bits.
  • Transport Session Identifier (TSI) field A field of 0, 16, 32, or 48 bits.
  • the TSI field may uniquely identify one session of all sessions from a particular transmitter.
  • the TSI field may be scoped by the transmitter's IP address, and thus the transmitter's IP address and the TSI field may together uniquely identify the session.
  • the TSI field in conjunction with the transmitter's IP address uniquely identifies the session, whether the TSI field is included in the LCT header may depend on which value is used as the TSI value. If the underlying transmission is UDP, a 16-bit UDP source port number may be provided as the TSI field for that session. If a TSI value occurs multiple times in a packet, all occurrences must be the same value. If there is no underlying TSI field provided by the network, transport or any other layer, the TSI field should be included in the LCT header.
  • the TSI field should be shared among all sessions provided by the transmitter during the period during which the session is activated, and for long periods before and after the session is activated.
  • the main purpose of the TSI field is to prevent the receiver from inadvertently accepting packets from a transmitter belonging to sessions other than the session to which the receiver subscribes. For example, suppose a session is deactivated, then another session is activated by the transmitter, and then the two sessions use a set of channels that overlap. During this transmitter activation, the receiver connected and staying connected to the first session will probably accept packets from the second session as belonging to the first session if the TSIs of the two sessions were the same.
  • the mapping of TSI field values to sessions is outside the scope of this document and should be done out of band.
  • the length of the TSI field may be '32 * S + 16 * H '.
  • the aggregate length of the TSI field plus the TOI field may be a multiple of 32 bits.
  • TOI Transport Object Identifier
  • the TOI field may indicate which object is in the session in which this packet is included.
  • the sender may use the first value of the TOI field (e.g., 0) for the first file, the second value of the TOI field (e.g., 1), etc. for the second file, and the like. I can send a number.
  • the TOI field may be a unique global identifier of an object transmitted simultaneously from several transmitters, and the TOI value may be the output of a hash function applied to the object.
  • the mapping of TOI field values to objects is outside the scope of this document and should be done out of band.
  • the TOI field should be used in all packets if more than one object is sent in the session. That is, the TOI field may be present in all packets of the session or none at all.
  • the length of the TOI field may be '32 * O + 16 * H '.
  • the aggregate length of the TSI field plus the TOI field may be a multiple of 32 bits.
  • FIG. 12 shows a header structure of an LCT packet according to another embodiment of the present invention.
  • a description overlapping with FIG. 11 will be omitted.
  • the LCT packet header of the embodiment of FIG. 12 may be a header of an LCT packet used in a ROUTE protocol.
  • the LCT packet header of FIG. 12 may be a header of the LCT packet used in the ROUTE protocol used in ATSC 3.0.
  • This ROUTE protocol is divided into two main components: 1) A source protocol for delivery of an object or flow / collection of objects (ROUTE source protocol) and 2) A repair protocol (ROUTE repair protocol) for flexibly protecting a delivery object or a bundle of delivery objects delivered through a source protocol.
  • all packets are LCT packets, and source packets and repair packets can be distinguished by: 1) Different ROUTE sessions, ie they may be carried in different IP / UDP port combinations. 2) Different LCT channels, that is, they may use different TSI values in the LCT header. And / or, 3) PSI bits in the LCT header if they are carried in the same LCT channel.
  • the scope of this ROUTE protocol is the reliable transport of delivery objects and associated metadata using LCT packets.
  • the packet format used in ROUTE may be an ALC packet format, that is, a packet format in which the LCT header follows the UDP header.
  • the LCT header may follow the LCT header structure described above with reference to FIG. 11. That is, the LCT packet header for the ROUTE protocol may use the structure of the LCT packet header of FIG. 11.
  • ALC packet format that is, a packet format in which the LCT header follows the UDP header.
  • the LCT header may follow the LCT header structure described above with reference to FIG. 11. That is, the LCT packet header for the ROUTE protocol may use the structure of the LCT packet header of FIG. 11.
  • the V field may be a 4-bit field indicating a protocol version number.
  • the V field may be interpreted as the ROUTE version number field.
  • the version number field should be set to '0001'.
  • the PSI field may be a 2-bit field for distinguishing a source packet or a repair packet.
  • the PSI field may be a 2-bit field indicating whether the current packet is a source packet or an FEC repair packet.
  • the PSI field should be set to '10'. That is, in the case of the ROUTE source protocol, the PSI field should be set to '10'.
  • the MSB of the PSI field may be set to '1' to indicate a source packet.
  • C Congestion Control Flag
  • the S field may be set to '1' for a 32-bit long TSI field representation. Specifically, for the ROUTE protocol, the S field should be set to '1' to indicate a 32-bit word in the TSI field.
  • O field shall be set to '01' for a 32-bit TOI field representation. Specifically, for the ROUTE protocol, the S field should be set to '01' to indicate the number of full 32-bit words in the TSI field.
  • Half-Word Flag (F) Field The F field shall be set to '0'. Specifically, for the ROUTE protocol, the F field should be set to '0' to indicate that half-word field size is not used.
  • the TSI field is a 32-bit field that can be used to identify a transport session within a ROUTE session. That is, the TSI field may identify a transport session (ie, LCT channel) in a ROUTE session.
  • the context of the transport session may be provided by the signaling metadata.
  • the TSI field is limited to 32 bits in length because the transport session identifier flag S is set to '1' and the half-word flag H field is set to '0'.
  • the TSI field may be set equal to the value of the TSI attribute of the LS element in the RS element in the S-TSID.
  • the TOI field is a 32-bit field that can be used to identify the object to which the current packet payload belongs. Specifically, the TOI field may identify the object in this session to which the payload of the current packet belongs.
  • the mapping of the TOI field to the object may be provided by an extended FDT (EFDT).
  • EFDT extended FDT
  • the TOI field is limited to 32 bits in length because the transport object identifier flag O is set to '01' and the half-word flag H field is set to '0'.
  • the CP field is an 8-bit field that can be used to identify the type of the current packet payload. Specifically, the CP field may be used to indicate the type of payload carried by this packet. In the case of ROUTE, it may be defined to support the MPD-less start and playback operations to indicate the type of delivery object carried in the payload of the associated ROUTE packet. Depending on the type of payload, additional payload headers may be added to prefix payload data. As an embodiment, the CP field may be used to signal the applied formattin as defined in the signaling metadata.
  • An example of a header of the LCT packet having the aforementioned constraint may be the same as that of FIG. 12.
  • the broadcast transmitter may compress the LCT header, for example, by deleting some or all of the fields with fixed values, and the broadcast receiver may compress the LCT header using a known fixed value of the deleted fields.
  • the original LCT header can be restored from.
  • the compression or decompression of the LCT header may be performed in the link layer. That is, the compression or decompression of the LCT header may be performed through link layer processing.
  • the link layer is a layer between the physical layer and the network layer.
  • the broadcast transmitter may receive data at the network layer, transmit the data to the physical layer, and then process the data in physical layer to transmit the data to the broadcast receiver.
  • the link layer processor may process or format the input packets into link layer packets so that they can be processed in the physical layer.
  • encapsulation and compression of a link layer performed at a link layer may be performed based on, for example, an ASC (ATSC Link layer Protocol) protocol, and link layer packets generated based on an ALP protocol may be converted into an ALP packet. May be referred to.
  • the link layer processor may receive network layer data in a format such as IP data or MPEG-2 TS data and encapsulate the ALP packet.
  • LCT header compression may be performed at the link layer.
  • LCT header compression may be performed based on a link layer protocol (eg, ALP protocol).
  • link layer protocol eg, ALP protocol
  • the IP packet processed in the IP layer may include an IP header, a UDP header, and an LCT header.
  • the IP header and the UDP header may have a fixed length.
  • the IP header can be 20 bytes long and the UDP header can be 8 bytes long.
  • the broadcast transmitter can quickly know from which byte of the IP packet the LCT header starts. That is, the broadcast transmitter can quickly know from which byte of the IP packet the LCT header starts without checking the length fields in the IP header and the UDP header.
  • the IP packet may include a ROUTE packet, and the ROUTE packet may include a ROUTE header and payload data.
  • the IP packet may not include a ROUTE header and / or payload data.
  • the ROUTE packet may not include ROUTE header or payload data.
  • the total datagram length carried by the outer protocol header IP header or UDP header) allows the broadcast receiver to detect the absence of the ROUTE header and payload.
  • the IP packet may be IPv4 or IPv6.
  • the ROUTE packet does not have a dependency on the IP version value.
  • the broadcast transmitter may first compress an IP / UDP packet, that is, compress an IP header (IP packet header) and / or a UDP header (UDP packet header).
  • IP packet header IP packet header
  • UDP packet header UDP header
  • the RoHC module may perform such IP header and UDP header compression (RoHC compression) using an appropriate version of the RoHC scheme.
  • RoHC packet the IP header and the UDP header may be compressed into an RoHC header, and the compressed packet including the RoHC header (RoHC packet) may be the same as the second packet of FIG. 13 (b).
  • the broadcast transmitter may compress the LCT packet, that is, the LCT header (LCT packet header). Compression of such LCT header may be performed by the adaptation module. Through this compression process, the LCT header may be compressed into a reduced LCT header, and the compressed packet including the reduced LCT header may be the same as the third packet of FIG. 13 (b).
  • the reduced LCT header will be described below with reference to FIGS. 17 and 18. In this specification, the reduced LCT header may be referred to as a compressed LCT header.
  • the adaptation module may perform the original functions such as the above-described context extraction, packet conversion, signaling information generation, and the like. This is the same as described above with reference to FIG. 6.
  • the broadcast transmitter may configure or process a packet in which an IP header, a UDP header, and an LCT header are compressed into an ALP packet (or a link layer packet) through ALP encapsulation.
  • the generated ALP packet includes an ALP header (or ALP packet header or link layer packet header), and may be the same as the fourth packet of FIG. 13 (b).
  • the ALP packet encapsulation including the insertion procedure of the ALP header may be performed by the encapsulation module. This is the same as described above with reference to FIG. 6.
  • the generated ALP packet may be processed as a broadcast signal in the physical layer and transmitted to the broadcast transmitter.
  • the LCT header compression is performed by the adaptation module after the IP header and the UDP header compression are performed by the RoHC module. That is, in the embodiment of FIG. 13, LCT header compression is performed separately / independently from IP / UDP header compression by the RoHC module, and is performed after compression by the RoHC module.
  • LCT header compression may be performed in the link layer.
  • LCT header compression may be performed based on a link layer protocol (eg, ALP protocol).
  • ALP protocol eg, ALP protocol
  • an IP packet including an IP header, a UDP header, and an LCT header may be delivered to the link layer.
  • the broadcast transmitter may first compress an LCT header (LCT packet header). Compression of such LCT header may be performed by the LCT header compression module. That is, unlike in the embodiment of FIG. 13, in the embodiment of FIG. 14, LCT header compression may be performed by a separate LCT header compression module. As described above, when the length of the IP / UDP header is fixed, since the broadcast transmitter can quickly know from which byte of the IP packet the LCT header starts without checking the length fields in the IP header and the UDP header, In this manner, LCT header compression may be performed before RoHC compression of the IP / UDP header.
  • LCT header compression may be performed before RoHC compression of the IP / UDP header.
  • the LCT header may be compressed into a reduced LCT header, and the compressed packet including the reduced LCT header may be the same as the second packet of FIG. 14 (b).
  • the reduced LCT header will be described below with reference to FIGS. 17 and 18.
  • the broadcast transmitter may compress an IP header (IP packet header) and / or a UDP header (UDP packet header).
  • IP header IP packet header
  • UDP packet header UDP header
  • Such compression of the IP header and the UDP header may be performed by the RoHC module.
  • the RoHC module may perform such IP header and UDP header compression using an appropriate version of the RoHC scheme.
  • the IP header and the UDP header may be compressed into an RoHC header, and the compressed packet including the RoHC header may be the same as the third packet of FIG. 14 (b).
  • the broadcast transmitter may perform a function such as context extraction, packet conversion, and signaling information generation using an adaptation module. This is the same as described above with reference to FIG. 6.
  • the broadcast transmitter may configure or process a packet in which an IP header, a UDP header, and an LCT header are compressed into an ALP packet through ALP encapsulation.
  • the generated ALP packet includes an ALP header (ALP packet header) and may be the same as the fourth packet of FIG. 13 (b).
  • the generated ALP packet may be processed as a broadcast signal in the physical layer and transmitted to the broadcast transmitter.
  • LCT header compression is performed by the LCT header compression module before IP header and UDP header compression by the RoHC module is performed. It is done. That is, in the embodiment of FIG. 14, LCT header compression is performed separately / independently from IP / UDP header compression by the RoHC module, and is performed by a separate LCT header compression module before compression by the RoHC module. It is done.
  • LCT header compression may be performed at the link layer.
  • LCT header compression may be performed based on a link layer protocol (eg, ALP protocol).
  • ALP protocol eg, ALP protocol
  • an IP packet including an IP header, a UDP header, and an LCT header may be delivered to the link layer.
  • the broadcast transmitter may first compress an IP header (IP packet header) and / or a UDP header (UDP packet header).
  • IP header IP packet header
  • UDP packet header UDP header
  • the RoHC module may perform such IP header and UDP header compression using an appropriate version of the RoHC scheme.
  • the IP header and the UDP header may be compressed into the RoHC header, and the compressed packet including the RoHC header may be the same as the second packet of FIG. 15 (b).
  • the broadcast transmitter may compress an LCT header (LCT packet header). Compression of such LCT header may be performed by the LCT header compression module. That is, unlike in the embodiment of FIG. 13, in the embodiment of FIG. 15, LCT header compression may be performed by a separate LCT header compression module. Through this compression process, the LCT header may be compressed into a reduced LCT header, and the compressed packet including the reduced LCT header may be the same as the third packet of FIG. 15 (b). The reduced LCT header will be described below with reference to FIGS. 17 and 18.
  • the broadcast transmitter may perform a function such as context extraction, packet conversion, and signaling information generation using an adaptation module. This is the same as described above with reference to FIG. 6.
  • the broadcast transmitter may configure or process a packet in which an IP header, a UDP header, and an LCT header are compressed into an ALP packet through ALP encapsulation.
  • the generated ALP packet includes an ALP header (ALP packet header) and may be the same as the fourth packet of FIG. 15 (b).
  • the generated ALP packet may be processed as a broadcast signal in the physical layer and transmitted to the broadcast transmitter.
  • the LCT header compression is performed by the LCT header compression module after the IP header and the UDP header compression are performed by the RoHC module. That is, in the embodiment of FIG. 15, the LCT header compression is performed by a separate LCT header compression module after the compression by the RoHC module is performed.
  • LCT header compression may be performed in the link layer.
  • LCT header compression may be performed based on a link layer protocol (eg, ALP protocol).
  • ALP protocol eg, ALP protocol
  • an IP packet including an IP header, a UDP header, and an LCT header may be delivered to the link layer.
  • the broadcast transmitter may first compress an IP header (IP packet header) and / or a UDP header (UDP packet header).
  • IP header IP packet header
  • UDP packet header UDP header
  • Such compression of the IP header and the UDP header may be performed by the RoHC module.
  • the RoHC module may perform such IP header and UDP header compression using an appropriate version of the RoHC scheme.
  • the IP header and the UDP header may be compressed into the RoHC header, and the compressed packet including the RoHC header may be the same as the second packet of FIG. 15 (b).
  • the broadcast transmitter may perform functions such as context extraction, packet conversion, and signaling information generation using an adaptation module. This is the same as described above with reference to FIG. 6.
  • the broadcast transmitter may compress an LCT header (LCT packet header). Compression of such LCT header may be performed by the LCT header compression module. That is, unlike in the embodiment of FIG. 13, in the embodiment of FIG. 16, LCT header compression may be performed by a separate LCT header compression module. Through this compression process, the LCT header may be compressed into a reduced LCT header, and the compressed packet including the reduced LCT header may be the same as the third packet of FIG. 16 (b). The reduced LCT header will be described below with reference to FIGS. 17 and 18.
  • the broadcast transmitter may configure or process a packet in which an IP header, a UDP header, and an LCT header are compressed into an ALP packet through ALP encapsulation.
  • the generated ALP packet includes an ALP header (ALP packet header) and may be the same as the fourth packet of FIG. 15 (b).
  • the generated ALP packet may be processed as a broadcast signal in the physical layer and transmitted to the broadcast transmitter.
  • LCT header compression is performed by the LCT header compression module after the IP / UDP header compression process by the RoHC module and the adaptation process by the adaptation module are performed. Characterized in that it is carried out. That is, in the embodiment of FIG. 16, the LCT header compression is performed by a separate LCT header compression module after the compression by the RoHC module and the adaptation process by the adaptation module are performed.
  • the reduced LCT header refers to an LCT header compressed through the LCT header compression method described above with reference to FIGS. 13 to 16.
  • the reduced LCT header may be referred to as a compressed LCT header.
  • the ROUTE protocol is a ROUTE source protocol that delivers only source packets.
  • the PSI field has a fixed value (eg, '10').
  • the shaded fields in the LCT header have a fixed value, and furthermore, the PSI field also has a fixed value. Therefore, the fields having this fixed value may be deleted through the LCT header compression process as in the embodiment of FIGS. 13 to 16.
  • the LCT header from which fields having a fixed value are deleted may be as shown in FIG. 17 (b).
  • the reduced (or compressed) LCT header may include only an LCT header length field, a code point field, a TSI field, and / or a TOI field.
  • the size (or length) of the LCT header may be reduced from 16 bytes to 10 bytes. This reduces the transmission overhead.
  • the reduced LCT header refers to an LCT header compressed through the LCT header compression method described above with reference to FIGS. 13 to 16.
  • the reduced LCT header may be referred to as a compressed LCT header.
  • FIG. 18 a description overlapping with the description above is omitted.
  • the ROUTE protocol is not specified as a ROUTE source protocol that delivers only source packets.
  • the PSI field may not be set to a fixed value. Therefore, the PSI field cannot be deleted in the LCT header compression process.
  • the LCT header length field can use only 6 bits.
  • the LCT header length field is an 8-bit field and may indicate the total length of the LCT header.
  • This LCT header length field may indicate the length of an LCT header part including a header extension (LCT header extension) in word units (4 bytes).
  • the total length of the LCT header including the length of the LCT header extension does not generally exceed 64 words (256 bytes).
  • only 6 bits may be used for the LCT header length field, and the remaining 2 bits of space may be used for the PSI field.
  • the shaded fields in the LCT header may have a fixed value. Therefore, the fields having this fixed value may be deleted through the LCT header compression process as in the embodiment of FIGS. 13 to 16.
  • the LCT header length field in the LCT header may indicate the length of the LCT packet header using only 6 bits. Therefore, the LCT header length field may be compressed from 8 bits to 6 bits through the LCT header compression process.
  • the reduced (or compressed) LCT header may include only a PSI field, an LCT header length field, a code point field, a TSI field, and / or a TOI field.
  • the first byte of the reduced (or compressed) LCT header may include a PSI field and an LCT header length field.
  • the first byte of the reduced (or compressed) LCT header may consist of a 2-bit PSI field and a 6-bit LCT header length field.
  • the RDT information may include a signaling field / information for notifying the broadcast receiver whether the LCT header is compressed.
  • the RDT information may be referred to as header compression information.
  • the RDT information corresponds to one of link layer signaling information generated in the link layer.
  • the signaling type field indicates the type of signaling carried by this table.
  • the value of the signaling type field for the RDT may be 0x02.
  • the PLP ID field may indicate a PLP corresponding to this table.
  • max_CID The max CID field may indicate a maximum value of a context ID used in correspondence with this PLP.
  • the adaptation mode field may indicate the mode of the adaptation module in this PLP.
  • the adaptation mode according to the adaptation mode field value may be provided as follows.
  • context_config may indicate a combination of context information. If there is no context information in this table, this field may be set to '0x0'. When static_chain_byte () or dynamic_chain_byte () is included in this table, this field may be set to '0x01' or '0x02', respectively. If static_chain_byte () and dynamic_chain_byte () are included in this table, this field may be set to '0x3'.
  • num_context This field indicates the number of contexts in this table. The value of the num_context field cannot be greater than the value of the max_CID field.
  • context_id This field indicates the context ID (CID) of the compressed IP stream.
  • context_profile This field may indicate the range of protocols used to compress the stream. This field may carry 8 bits of Least Significant bits (LSB) of the ROHC profile identifier.
  • LSB Least Significant bits
  • context_length This field may indicate the length of a context length sequence in bytes.
  • static_chain_byte This field carries the static information used to initialize the ROHC-U decompressor. The size and structure of this field is based on the context profile.
  • dynamic_chain_byte This field carries the dynamic information used to initialize the ROHC-U decompressor. The size and structure of this field is based on the context profile.
  • the LCT header may be compressed in the link layer separately / independently from the IP / UDP header compression according to the RoHC scheme.
  • the RDT information providing information on header compression should be able to provide information related to LCT header compression in addition to information related to RoHC compression.
  • the RDT information may include an additional LCT compression flag field (additional_LCT_compression_flag) / information.
  • the additional LCT compression flag field is a 1-bit field and may be a field indicating whether the LCT header is compressed in addition to RoHC compression. That is, the additional LCT compression flag field may indicate whether LCT header compression is performed.
  • the additional LCT compression flag field when the additional LCT compression flag field is set to a first value (eg, 1), the additional LCT compression flag field may indicate that LCT header compression is performed. Or, if the additional LCT compression flag field is set to a second value (eg, 0), the additional LCT compression flag field may indicate that LCT header compression is not performed.
  • an additional LCT compression flag field may be referred to as an LCT compression flag field.
  • the broadcast transmitter may indicate whether LCT header compression is performed using this LCT compression flag field.
  • the broadcast receiver may determine whether to perform restoration (decompression) of the LCT header based on the LCT compression flag field. For example, when the LCT compression flag field indicates that LCT header compression is performed, the broadcast receiver may perform LCT header reconstruction. In this case, the broadcast receiver may restore the original LCT header from the compressed LCT header by using a value of the deleted or compressed field known in advance.
  • the LCT compression flag field has been described as being included in the RDT, that is, the header compression information. However, in some embodiments, the LCT compression flag field may be included in the LMT information. In any case, however, the LCT compression flag field may be included in the link layer signaling information and signaled.
  • a broadcast signal transmitter may be referred to as a broadcast transmitter, a transmitter, or the like
  • a broadcast signal receiver may be referred to as a broadcast receiver, a receiver, or the like.
  • the broadcast signal receiver / transmitter 2000 may include a communication unit 2010, a processor 2020, and a memory 2030.
  • the communication unit 2010 may be connected to the processor 2020 to transmit / receive a broadcast signal.
  • the communication unit 2010 may up-convert data received from the processor 2020 into a transmission / reception band to transmit a signal.
  • the communication unit 2010 may downconvert the received data and forward it to the processor 2020.
  • the processor 2020 may be connected to the communication unit 2010 to implement broadcast signal processing technology according to the ATSC 3.0 system.
  • the processor 2020 may be configured to perform an operation according to various embodiments of the present disclosure according to the drawings and description described above.
  • a module that implements the operation of the broadcast signal transmitter / receiver 2000 according to various embodiments of the present disclosure described above may be stored in the memory 2030 and executed by the processor 2020.
  • the memory 2030 is connected to the processor 2020 and stores various information for driving the processor 2020.
  • the memory 2030 may be included in the processor 2020 or may be installed outside the processor 2020 and connected to the processor 2020 by known means.
  • the specific configuration of the broadcast signal transmitter / receiver 2000 may be implemented so that the above-described matters described in various embodiments of the present invention are applied independently or two or more embodiments are simultaneously applied.
  • FIG. 21 illustrates a broadcast signal transmission method according to an embodiment of the present invention.
  • the broadcast transmitter may encode service data for a broadcast service based on the ROUTE protocol (S21010).
  • the broadcast transmitter may generate service data (or content data) for a broadcast service and encode it based on a ROUTE protocol, which is one of delivery protocols.
  • the broadcast transmitter may generate service layer signaling (SLS) information for a broadcast service and encode the same based on a delivery protocol.
  • SLS service layer signaling
  • the service data and the SLS information may be encoded based on the ROUTE protocol, which is the same delivery protocol.
  • the generated ROUTE packet may include an LCT header, a ROUTE header, and / or payload data.
  • the broadcast transmitter may generate at least one IP packet by processing the service data in a UDP / IP layer (S21020).
  • the broadcast transmitter may generate at least one IP packet by performing UDP / IP layer processing on the SLS information.
  • the broadcast transmitter may generate service list table (SLT) information before UDP / IP layer processing.
  • the broadcast transmitter may generate at least one IP packet by performing UDP / IP layer processing on the service data, the SLS information, and the SLT information.
  • the SLT information may be processed into IP packets having a well-known IP address / port number.
  • the generated IP packet may include an IP header, a UDP header, and an LCT header.
  • the broadcast transmitter may output at least one link layer packet by link layer processing the at least one IP packet (S21030).
  • link layer processing the broadcast transmitter may perform header compression on at least one IP packet.
  • the header compression for the IP packet may include RoHC compression for the IP header and / or UDP header and / or LCT header compression for the LCT header. Each is as described above in FIGS. 6 and 11 to 19.
  • the broadcast transmitter may generate link layer signaling information.
  • the link layer signaling information may include header compression information including information related to header compression.
  • the header compression information may be the above-described RDT information.
  • the link layer signaling information may further include the above-described link mapping table (LMT) information. This is the same as described above with reference to FIG. 7.
  • LMT link mapping table
  • the broadcast transmitter may encapsulate data and link layer signaling information of at least one IP packet into at least one link layer packet.
  • the broadcast transmitter may encapsulate data of the IP packet and link layer signaling information into separate link layer packets.
  • the broadcast transmitter may perform header compression (IP header compression) on an IP header (or IP / UDP header) of at least one IP packet based on a Robust Header Compression (RoHC) scheme. Thereafter, the broadcast transmitter may extract context information based on at least one adaptation mode.
  • the header compression information may include context information
  • the context information may include at least one of static chain information or dynamic chain information. This is the same as described above with reference to FIGS. 6 and 13 to 16.
  • the broadcast transmitter may perform header compression (LCT header compression) on the LCT header of at least one IP packet.
  • the broadcast transmitter may perform additional LCT header compression before IP header compression or after IP header compression.
  • the broadcast receiver may perform LCT header compression in a manner separate from the IP header compression based on the RoHC scheme (eg, ATSC3.0 specific scheme).
  • the broadcast transmitter may perform LCT header compression by using a module separate from the RoHC module that performs IP header compression (for example, an adaptation module or an LCT header compression module).
  • the broadcast transmitter may compress the LCT header by deleting fields having a fixed value among the fields in the LCT header.
  • the field having a fixed value may include a version number field indicating a protocol version number, a control control flag field indicating a length of a control control field, and a transmission used to indicate a length of a transmission session identifier field. It may include at least one of a session identifier flag field, a transport object identifier flag field used to indicate the length of the transport object identifier field, or a conference control field including conference control information.
  • Such LCT header compression is as described above with reference to FIGS. 11 to 18.
  • the header compression information may include LCT compression flag information indicating whether LCT header compression is performed.
  • the LCT compression flag information may be used to indicate whether additional LCT header compression is performed in addition to IP header compression (RoHC compression) based on RoHC.
  • the LCT compression flag information may be included in the LMT information. This is the same as described above with reference to FIG. 19.
  • the broadcast transmitter may generate a broadcast signal by performing physical layer processing on the at least one link layer packet (S21040).
  • the broadcast transmitter may process the physical layer processing of at least one link layer packet based on the PLP. Physical layer processing operations using the physical layer processor of the broadcast transmitter have been described above with reference to FIG. 8.
  • the broadcast receiver may perform a reverse operation of the broadcast transmitter.
  • a broadcast signal reception method by a broadcast receiver will be described.
  • the broadcast receiver may receive a broadcast signal.
  • the broadcast signal may include SLT information, SLS information, and / or link layer signaling information.
  • the link layer signaling information may include LMT information and RDT information.
  • the broadcast receiver may first acquire SLT information, LMT information, and / or RDT information before acquiring the packet stream. As described above, when the signaling information is obtained, the broadcast receiver may combine these to obtain a mapping between the service, the IP information, the context information, and the PLP.
  • the broadcast receiver may select and decode a PLP carrying a specific packet stream.
  • This particular packet stream may be a compressed packet stream.
  • the compressed packet stream may be a packet stream including a packet in which an IP header, a UDP header, and / or an LCT header are compressed. This is the same as described above with reference to FIGS. 13 to 18.
  • the broadcast receiver may restore the IP packet header from a specific packet stream including the header compressed packet.
  • the broadcast receiver may decompress the compressed IP header, UDP header and / or LCT header of the packets in a particular packet stream.
  • information related to header compression in the LMT information and / or the RDT information may be used.
  • the decompression process in the broadcast receiver is performed in the link layer, and may be performed in the reverse process of the compression process.
  • the broadcast signal receiving method may follow the following procedure.
  • the broadcast receiver may receive link layer signaling information.
  • the link layer signaling information may include LMT information and / or RDT information (header compression information).
  • the header compression information may include LCT compression flag information.
  • the broadcast receiver may receive a packet stream including the header compressed packet.
  • the broadcast receiver may decompress the header of the header compressed packet based on the received link layer signaling information to output the IP packet stream.
  • the broadcast receiver may decompress an IP header (IP / UDP) by RoHC based on the LMT information and the RDT information.
  • the broadcast receiver may determine whether to decompress the LCT header based on the LCT compression flag information in the RDT information, and may decompress the LCT header according to a predetermined method. In this case, the broadcast receiver may decompress the LCT header based on previously known deleted or compressed field information. This is the same as described above with reference to FIGS. 6, 7 and 11 to 20.
  • the broadcast receiver may process the IP packet stream to obtain service data for the broadcast service.
  • the broadcast receiver may perform decoding on service data based on the ROUTE protocol.
  • Each of the steps described in the above embodiments may be performed by hardware / processors.
  • Each module / block / unit described in the above embodiments can operate as a hardware / processor.
  • the methods proposed by the present invention can be executed as code. This code can be written to a processor readable storage medium and thus read by a processor provided by an apparatus.
  • the processor-readable recording medium includes all kinds of recording devices that store data that can be read by the processor.
  • Examples of the processor-readable recording medium include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like, and may also be implemented in the form of a carrier wave such as transmission over the Internet.
  • the processor-readable recording medium can also be distributed over network coupled computer systems so that the processor-readable code is stored and executed in a distributed fashion.
  • the present invention is used in the field of transmitting / receiving a series of broadcast signals.

Abstract

La présente invention concerne un procédé de transmission de signal de diffusion. Un procédé de transmission de signal de diffusion, selon un mode de réalisation de la présente invention, comprend : une étape de codage de données de service d'un service de diffusion, sur la base d'un protocole ROUTE ; une étape de génération d'au moins un paquet IP par une couche UDP/IP traitant les données de service ; une étape de production d'au moins un paquet de couche de liaison par traitement de couche de liaison dudit paquet IP ; et une étape de génération d'un signal de diffusion par traitement de couche physique du paquet de couche de liaison.
PCT/KR2017/006361 2016-06-17 2017-06-16 Dispositif et procédé de transmission/réception de signal de diffusion WO2017217825A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662351312P 2016-06-17 2016-06-17
US62/351,312 2016-06-17

Publications (1)

Publication Number Publication Date
WO2017217825A1 true WO2017217825A1 (fr) 2017-12-21

Family

ID=60663298

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2017/006361 WO2017217825A1 (fr) 2016-06-17 2017-06-16 Dispositif et procédé de transmission/réception de signal de diffusion

Country Status (1)

Country Link
WO (1) WO2017217825A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113170219A (zh) * 2018-11-23 2021-07-23 索尼集团公司 用于通过中间件的调谐器控制的装置和方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7430617B2 (en) * 2003-12-19 2008-09-30 Nokia Corporation Method and system for header compression
WO2015167245A1 (fr) * 2014-04-30 2015-11-05 엘지전자 주식회사 Appareil de transmission de signal de diffusion, appareil de réception de signal de diffusion, procédé de transmission de signal de diffusion, et procédé de réception de signal de diffusion
KR20160048157A (ko) * 2014-03-03 2016-05-03 엘지전자 주식회사 방송 신호를 송신 및 수신하기 위한 장치 및 방법
KR20160056302A (ko) * 2014-11-11 2016-05-19 삼성전자주식회사 송신 장치, 수신 장치 및 그 제어 방법
KR20160059477A (ko) * 2014-10-20 2016-05-26 엘지전자 주식회사 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7430617B2 (en) * 2003-12-19 2008-09-30 Nokia Corporation Method and system for header compression
KR20160048157A (ko) * 2014-03-03 2016-05-03 엘지전자 주식회사 방송 신호를 송신 및 수신하기 위한 장치 및 방법
WO2015167245A1 (fr) * 2014-04-30 2015-11-05 엘지전자 주식회사 Appareil de transmission de signal de diffusion, appareil de réception de signal de diffusion, procédé de transmission de signal de diffusion, et procédé de réception de signal de diffusion
KR20160059477A (ko) * 2014-10-20 2016-05-26 엘지전자 주식회사 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법
KR20160056302A (ko) * 2014-11-11 2016-05-19 삼성전자주식회사 송신 장치, 수신 장치 및 그 제어 방법

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113170219A (zh) * 2018-11-23 2021-07-23 索尼集团公司 用于通过中间件的调谐器控制的装置和方法
CN113170219B (zh) * 2018-11-23 2024-02-02 索尼集团公司 用于通过中间件的调谐器控制的装置和方法

Similar Documents

Publication Publication Date Title
WO2017014586A1 (fr) Dispositif et procédé d'émission et de réception de signal de radiodiffusion
WO2017204546A1 (fr) Dispositif et procédé d'émission/réception de signaux de diffusion
WO2016186407A1 (fr) Appareil et procédé d'émission ou de réception de signal de diffusion
WO2016076623A1 (fr) Dispositif d'émission de signal de diffusion, dispositif de réception de signal de diffusion, procédé d'émission de signal de diffusion et procédé de réception de signal de diffusion
WO2016144072A1 (fr) Appareil et procédé pour émettre et recevoir un signal de radiodiffusion
WO2016093537A1 (fr) Dispositif de transmission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé de transmission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion
WO2016076654A1 (fr) Dispositif d'émission de signal de diffusion, dispositif de réception de signal de diffusion, procédé d'émission de signal de diffusion et procédé de réception de signal de diffusion
WO2016060422A1 (fr) Dispositif et procédé d'émission de signal de diffusion, dispositif et procédé de réception de signal de diffusion
WO2016140486A1 (fr) Appareil et procédé d'émission/réception de signal de diffusion
WO2018101566A1 (fr) Dispositif et procédé d'émission/réception de signal de radiodiffusion
WO2017209514A1 (fr) Dispositif et procédé d'émission et de réception de signal de diffusion
WO2019093829A1 (fr) Appareil de transmission de diffusion, procédé de transmission de diffusion, appareil de réception de diffusion, et procédé de réception de diffusion
WO2016153241A1 (fr) Dispositif d'émission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé d'émission de signal de radiodiffusion et procédé de réception de signal de radiodiffusion
WO2016080802A1 (fr) Dispositif de transmission de signal de diffusion, dispositif de réception de signal de diffusion, procédé de transmission de signal de diffusion et procédé de réception de signal de diffusion
WO2017061792A1 (fr) Dispositif et procédé d'émission/réception de signal de diffusion
WO2020091573A1 (fr) Appareil de transmission de diffusion, procédé de transmission de diffusion, appareil de réception de diffusion, et procédé de réception de diffusion
WO2016114638A1 (fr) Appareil de transmission de signal de radiodiffusion, appareil de réception de signal de radiodiffusion, procédé de transmission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion
WO2016190720A1 (fr) Dispositif d'émission et de réception de signal de radiodiffusion, et procédé d'émission et de réception de signal de radiodiffusion
WO2016178549A1 (fr) Dispositif d'émission de signaux de diffusion, dispositif de réception de signaux de diffusion, procédé d'émission de signaux de diffusion, et procédé de réception de signaux de diffusion
WO2017123044A1 (fr) Appareil et procédé pour émettre et recevoir un signal de diffusion
WO2017164595A1 (fr) Dispositif et procédé d'émission/réception de signal de diffusion
WO2016072725A1 (fr) Dispositif de transmission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé de transmission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion
WO2017007281A1 (fr) Dispositif et procédé d'émission et de réception d'un signal de diffusion
WO2016195412A1 (fr) Appareil d'émission de signal de diffusion, appareil de réception de signal de diffusion, procédé d'émission de signal de diffusion, et procédé de réception de signal de diffusion
WO2017043898A1 (fr) Appareil et procédé pour émettre et recevoir un signal de radiodiffusion

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17813648

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17813648

Country of ref document: EP

Kind code of ref document: A1