+

WO2017030344A1 - Appareil et procédé pour émettre et recevoir un signal de radiodiffusion - Google Patents

Appareil et procédé pour émettre et recevoir un signal de radiodiffusion Download PDF

Info

Publication number
WO2017030344A1
WO2017030344A1 PCT/KR2016/008979 KR2016008979W WO2017030344A1 WO 2017030344 A1 WO2017030344 A1 WO 2017030344A1 KR 2016008979 W KR2016008979 W KR 2016008979W WO 2017030344 A1 WO2017030344 A1 WO 2017030344A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
service
lls
slt
signaling
Prior art date
Application number
PCT/KR2016/008979
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 WO2017030344A1 publication Critical patent/WO2017030344A1/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/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/47—End-user applications
    • H04N21/472—End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content
    • H04N21/4722—End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content for requesting additional data associated with the content
    • H04N21/4725—End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content for requesting additional data associated with the content using interactive regions of the image, e.g. hot spots
    • 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/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/61—Network physical structure; Signal processing
    • 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/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/643—Communication protocols
    • 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/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/85—Assembly of content; Generation of multimedia applications
    • H04N21/858—Linking data to content, e.g. by linking an URL to a video object, by creating a hotspot

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: generating service data for a broadcast service and service layer signaling (SLS) information for the service data; Encoding the service data and the SLS information based on a delivery protocol, wherein the delivery protocol is a Real-Time Object Delivery over Unidirectional Transport (ROUTE) protocol or an MPEG Media Transport (MMT) protocol; Generating service list table (SLT) information for the service data, the SLT information including bootstrap information for discovery of the SLS information; Encapsulating the service data, the SLS information, and the SLT information, respectively; User Datagram Protocol (UDP) / Internet Protocol (IP); And generating a signal frame by performing physical layer processing on the service data, the SLS information, and the SLT information.
  • the SLT information may be included in the low level signaling (LLS) information for delivery, and the LLS information may include provider identification information for identifying a broadcaster using part or all of a broadcast stream.
  • LLS low level signaling
  • the broadcast signal transmitter for performing the above-described broadcast signal transmission method may include service layer signaling (SLS) information on service data for broadcast service and service list table (SLT) information on the service data.
  • a signaling generator for generating, wherein the SLT information includes bootstrap information for discovery of the SLS information;
  • a delivery layer encoder for encoding the service data and the SLS information based on a delivery protocol, wherein the delivery protocol is a Real-Time Object Delivery over Unidirectional Transport (ROUTE) protocol or an MPEG Media Transport (MMT) protocol;
  • a UDP / IP encapsulator for encapsulating the service data, the SLS information, and the SLT information, respectively;
  • a physical layer processor configured to physically process the service data, the SLS information, and the SLT information to generate a signal frame, wherein the SLT information is included in low level signaling (LLS) information for delivery.
  • LLS low level signaling
  • It may include provider identification
  • the LLS information further includes LLS table identification information for identifying signaling information included in the LLS information and delivered, and LLS table version information indicating a version of the LLS information.
  • the LLS table version information may be increased by 1 whenever data in the LLS information is changed.
  • the LLS information when the LLS table identification information has a first value, includes the SLT information, and when the LLS table identification information has a second value, the LLS information. May include rating region table (RRT) information including information related to rating for the service data.
  • RRT rating region table
  • the SLT information includes service category information
  • the service category indicated by the service category information includes a linear audio / video service, a linear audio only service, and an app-based service. It may include an Electronic Service Guide (ESG) service and an Emergency Alert System (EAS) service.
  • ESG Electronic Service Guide
  • EAS Emergency Alert System
  • the SLT information includes URL information for providing a base URL (Uniform Resource Locator) for acquiring signaling information about one or more services through broadband, and the base URL includes one or more URLs. It may be used to generate an HTTP request message for the signaling information along with a path term.
  • URL Uniform Resource Locator
  • the one or more paths may include service information for identifying a requested service, mode information for identifying a requested mode of the signaling information, and a requested version of the signaling information. It may include at least one of the version information for and the type information for identifying the requested type of the signaling information.
  • the URL information may include first URL information for providing a first base URL for acquiring signaling information for all services in the SLT information, or signaling information for a specific service in the SLT information. It may include second URL information that provides a second base URL for obtaining the.
  • 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 LLS information according to an embodiment of the present invention.
  • FIG 13 shows LLS information according to another embodiment of the present invention.
  • FIG. 16 illustrates a USBD of SLS information transmitted through an MMT protocol according to an embodiment of the present invention.
  • FIG. 17 illustrates a broadcast signal transmission method according to an embodiment of the present invention.
  • FIG. 18 illustrates a broadcast signal transmitter and a broadcast signal receiver 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 @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.
  • LLS information may also be referred to as LLS table or LLS data.
  • LLS table LLS data
  • FIG. 11 the same description as in FIG. 3 is omitted.
  • the LLS information may include an LLS_table_id field (information), an LLS_section_version field (information), an LLS_section_num field (information), and / or an LLS_total_section_num field (information).
  • the LLS_table_id field, LLS_section_version field, LLS_section_num field and LLS_total_section_num field may be included in the header portion of the LLS information. Description of each field (information) is as follows.
  • LLS_table_id As an unsigned integer of 8 bits, it is possible to identify the type of table (signaling information) delivered in the body portion of the LLS information.
  • the corresponding LLS information may include one of the above-described Service List Table (SLT) and Rating Region Table (RRT).
  • SLT Service List Table
  • RRT Rating Region Table
  • the LLS information is information related to rating for service data. It may include RRT information.
  • the SLT information or the RRT information may be included in the body portion of the LLS information.
  • the SLT and the RRT may be a table in binary format or XML format. According to an embodiment, other information other than these may be included in the LLS information.
  • the LLS information may include Advanced Emergency Alerting Table (AEAT) information that provides information related to an emergency alert.
  • AEAT Advanced Emergency Alerting Table
  • the LLS information is not processed in a delivery layer or a service layer, which is an upper layer, but may be processed and transmitted in a lower layer of an IP / UDP layer, for fast acquisition at a receiver. It may include.
  • LLS_section_version As an unsigned integer of 8 bits, it can be incremented by 1 whenever any data in the section of the table identified by the LLS_table_id information is changed. If this field value reaches the maximum value of 0xFF, the value may return to 0x00 again.
  • LLS_section_num An unsigned integer of 8 bits and may indicate a corresponding section of LLS information, counting from 1. If it does not exist, it may have a default value of 1.
  • LLS_total_section_num As an unsigned integer of 8 bits, it may indicate the total number of sections (ie, the section having the highest LLS section number) of the table to which the section belongs.
  • the LLS_section_num field and the LLS_total_section_num field may be considered together to indicate that a part of the LLS information is the Mth part of N when the LLS information is transmitted to the fragments. If it does not exist, it may have a default value of 1.
  • the LLS information described above may be processed (encapsulated) and transmitted as a UDP / IP packet in the UDP / IP layer.
  • the LLS information may be carried through the payload of an IP packet delivered to a well known IP address / port, and may include SLT information according to its type.
  • the LLS information since the LLS information is transmitted in an IP packet format without being encoded at the delivery layer, the LLS information may be processed faster at the receiver, thus reducing the delay required for providing a service when the receiver is turned on.
  • FIG. 12 illustrates SLT information according to an embodiment of the present invention.
  • the same description as in FIG. 3 is omitted.
  • the SLT information may enable the receiver to generate a service list through a quick channel scan and provide access information for locating the SLS information.
  • the SLT information may be processed and transmitted in the UDP / IP layer without being encoded in the delivery layer.
  • the SLT information of the embodiment of FIG. 12 may be included in the LLS information of the above-described embodiment of FIG. 11 and discarded. That is, the SLT information of FIG. 12 may be transmitted through the LLS information of FIG. 11.
  • the SLT information may not include attributes (fields) that provide section information for a section of the SLT. This will be described in detail below.
  • the broadcast transmitter transmits signaling information (table), such as SLT information, in a binary format
  • the signaling information may be divided into several sections and transmitted due to a size limitation.
  • the signaling information may include fields that provide information about the section.
  • the signaling information may include a field indicating a version of a corresponding section, a field indicating a number of the corresponding section, and / or a field indicating a number of all sections.
  • each SLT information may include an @sltSectionVersion attribute indicating the version number of the SLT section, an @sltSectionNumber attribute indicating the number of the section of the SLT, and / or the SLT to which the section belongs. It can include an @totalSltSectionNumbers attribute that indicates the total number of sections.
  • section information about the signaling information may be included in the header of the LLS information.
  • each signaling information may not include section information. That is, the section information may be included only in the header of the LLS information instead of included in the signaling information.
  • each SLT information may not include an @sltSectionVersion attribute, an @sltSectionNumber attribute, and / or an @totalSltSectionNumbers attribute.
  • the broadcast receiver uses the section information included in the header of the LLS information to obtain the same version as the section of the signaling information that has already been parsed.
  • the parsing of the section of signaling information may not be performed again. Through this, the efficiency of the receiver operation can be improved by avoiding unnecessary repetition of the operation.
  • the LLS information may be processed and transmitted as a UDP / IP packet in the UDP / IP layer.
  • the LLS information since the LLS information is transmitted in the UDP / IP packet format without being encoded in the delivery layer, the LLS information may be processed faster at the receiver, thus reducing the delay required for providing a service when the receiver is turned on.
  • FIG. 13 shows LLS information according to another embodiment of the present invention.
  • the same descriptions as those of FIGS. 3 and 11 are omitted.
  • the LLS information may include an LLS_table_id field (information) and / or an LLS_table_version field (information).
  • the LLS information may further include a provider_id field (information).
  • the LLS_table_id field is an 8-bit unsigned integer and may identify the type of signaling information (table) delivered in the body portion of the LLS information.
  • the LLS_table_version field is an 8-bit unsigned integer and may be incremented by 1 whenever any data in the table identified by the LLS_table_id information is changed. If this field value reaches 0xFF, the value may return to 0x00 on increment. As an embodiment, when there are one or more providers sharing one broadcast stream, the LLS_table_version field may be identified by an LLS_table_id field and a provider_id field.
  • the broadcast receiver uses the information in the LLS_table_id field and the LLS_table_version field to identify signaling information, such as SLT delivered by the LLS information, and to verify the version of the signaling information, so that the signaling information has the same version as the signaling information that has already been parsed. You may not perform parsing again. Through this, the efficiency of the receiver operation can be improved by avoiding unnecessary repetition of the operation.
  • the provider_id field is an 8-bit unsigned integer and may identify a provider using part or all of a broadcast stream.
  • the provider is a person who provides a broadcast service, for example, may be a broadcaster. If the value of this field is 0x00, the value may mean that the corresponding broadcast stream is used by one broadcaster.
  • the provider may be associated with a service signaled in the LLS information.
  • one broadcast stream may be shared by a plurality of broadcasters. In this case, each broadcaster sharing a broadcast stream may be identified by a value of a provider_id field.
  • the LLS_table_id field and / or the LLS_table_version field may be included in the header portion of the LLS information.
  • the provider_id field may be included in the body portion of the LLS information.
  • the provider_id field may be included in the body portion of the LLS information along with the SLT information.
  • the provider_id field may be included in the header portion of the LLS information.
  • the provider_id field may be included in the header portion of the LLS information together with the LLS_table_id field and the LLS_table_version field described above.
  • FIG. 14 illustrates SLT information according to another embodiment of the present invention.
  • the same description as in FIGS. 3 and 12 will be omitted.
  • the SLT information may provide rapid channel scans and service acquisition by including the following information for each service in the broadcast stream.
  • the SLT information may be processed and transmitted in the UDP / IP layer without being encoded in the delivery layer.
  • the SLT information of the embodiment of FIG. 14 may be included in the LLS information described above and discarded.
  • the SLT information may have a binary format or an XML format.
  • the SLT information may include information about one or more types of services.
  • the SLT information may include information about a Viewer service and / or a native service.
  • the SLT information may include a ViewerService element and / or a NativeService element, and may provide information on the Viewer service and information on the Native service through each element.
  • the Viewer service may be a service intended for viewer selection
  • the ViewerService element may provide service information about a service intended for viewer selection.
  • An example of the viewer service may include a linear service provided by a viewer's selection.
  • the native service may be a service intended for device consumption
  • the ViewerService element may provide information about a service intended for device consumption.
  • Examples of the native service may include a service used by a native application (app) of the device, for example, an emergency alert system (EAS) service or an electronic service guide (ESG) service.
  • EAS emergency alert system
  • ESG electronic service guide
  • the ViewerService element may be an element used as a mentorship.
  • the ViewerService element contains the @serviceId attribute, @sltSvcSeqNum attribute, @protected attribute, @majorChannelNo attribute, @minorChannelNo attribute, @serviceCategory attribute, @shortServiceName attribute, @hidden attribute, SignalingLoc element, @serviceLanguage attribute, @broadbandAccessRequired attribute, @capabilities attribute, And / or the @svcInetEsgUri attribute.
  • the @serviceId attribute may indicate an integer that uniquely identifies the corresponding service within a range of the corresponding broadcast service.
  • the @serviceId attribute may be a 16-bit integer that uniquely identifies the service within the range of the broadcast service.
  • the @serviceId attribute may be an attribute used as a mandatory.
  • the @sltSvcSeqNum attribute may indicate the version of the SLT service information for the corresponding service.
  • the @sltSvcSeqNum attribute may be an integer indicating a sequence number of SLT service information having the same service ID as the @serviceId attribute.
  • the value of the @sltSvcSeqNum attribute starts at 0 for each service and can be increased by 1 whenever any attribute in the corresponding service element changes.
  • the value of the @sltSvcSeqNum attribute may not be incremented if no attribute value is changed compared to the previous service element with a particular value of the service ID. This field may return to zero after reaching the maximum value.
  • the @sltSvcSeqNum attribute may be an attribute used as a mandatory.
  • the @protected attribute may indicate whether one or more components needed for a meaningful presentation need to be protected. If one or more components needed for a meaningful presentation need to be protected, this value may be set to a value indicating "true” (eg, 1). If one or more components needed for a meaningful presentation do not need to be protected, this value may be set to a value representing "false” (eg, 0). The default value may be a false value.
  • the @sltSvcSeqNum attribute may be an optional attribute.
  • the @majorChannelNo attribute may indicate the major channel number of the corresponding service.
  • the @majorChannelNo attribute may be an integer between 1 and 999 indicating a major channel number of a service.
  • the @majorChannelNo attribute may be an attribute used as a mandatory. That is, in the case of a Viewer service, the @majorChannelNo attribute may be an attribute used as a mandatory. Meanwhile, as described below, in the case of a native service such as an EAS service or an ESG service, the @majorChannelNo attribute may not be used or may be an optional attribute.
  • the @minorChannelNo attribute may indicate the minor channel number of the corresponding service.
  • the @minorChannelNo attribute may be an integer between 1 and 999 indicating a minor channel number of the service.
  • the @minorChannelNo attribute may be an attribute used as a mandatory. That is, in the case of the Viewer service, the @minorChannelNo attribute may be an attribute used as a mandatory. Meanwhile, as described below, in the case of a native service such as an EAS service or an ESG service, the @minorChannelNo attribute may not be used or may be an optional attribute.
  • the @serviceCategory attribute may indicate a category of a service.
  • the @serviceCategory attribute of the ViewerService element may indicate a service category indicating the Viewer service.
  • the @serviceCategory attribute of the ViewerService element may have a value of a service category indicating a linear audio / video service or a linear audio only service.
  • the @serviceCategory attribute of the ViewerService element is used for linear A / V service with app-based enhancement and linear audio only with app-based enhancement. It may have a value of a service category indicating service with app-based enhancement.
  • the linear audio / video service having the above-described app-based enhancement may be a service included in the linear audio / video service, and only the linear audio having the above-described app-based enhancement may be the linear audio. It may be a service included in the service of the bay.
  • the @serviceCategory attribute may be an attribute used as a mandatory.
  • the @shortServiceName attribute may indicate a short string name of a service.
  • the @shortServiceName attribute may indicate the short name of the service within seven characters.
  • the @shortServiceName attribute may be an attribute used as a mandatory. That is, in the case of the Viewer service, the @shortServiceName attribute may be an attribute used as a mandatory. Meanwhile, as described below, in the case of a native service such as an EAS service or an ESG service, the @shortServiceName attribute may not be used or may be an optional attribute.
  • the @hidden attribute may indicate whether the service is intended for testing or proprietary use, rather than being selected by a normal TV receiver. If the service is for testing or for proprietary use, the value of this attribute may be set to a value (eg, 1) indicating "true”. If not present, the value of this attribute may be set to a value (eg, 0) indicating a default value of "false”. In an embodiment, the @hidden attribute may be an optional attribute.
  • the SignalingLoc element may indicate a location and protocol for signaling. More specifically, the SignalingLoc element, if available, can provide a service level signaling protocol and signaling location for the service, including broadband and brocast locations. If the SignalingLoc element does not contain a broadcast location for a service, the SignalingLoc element may contain the svcInetSigUri attribute for that service or the svcInetSigUri attribute may exist as an attribute of the SLT root element, and the ⁇ service_id> path described below. A path term may be supported for the service_id of the parent Service element of the corresponding BroadcastSignaling element. In an embodiment, the SignalingLoc element may be an element used optionally.
  • the @serviceLanguage attribute may indicate a language code of 3 characters per ISO indicating the main language of the service.
  • the @serviceLanguage attribute may be an optional attribute.
  • the @broadbandAccessRequired attribute may indicate whether broadband access is necessary for a meaningful presentation of a corresponding service.
  • the default value may be "false”.
  • the @broadbandAccessRequired attribute may be an optional attribute.
  • the @capabilities attribute can provide the capability information necessary for decoding and meaningful presentation of the service.
  • the @capabilities attribute may be an optional attribute.
  • the @svcInetEsgUri attribute if available, can provide a URL for accessing ESG data for the service over broadband.
  • the NativeService element may be an element used optionally.
  • the NativeService element may include an @serviceId attribute, an @sltSvcSeqNum attribute, an @serviceCategory attribute, and / or a SignalingLoc sub element.
  • the @serviceId attribute is the same attribute as the @serviceId attribute of the above-described ViewerService element and may indicate an integer that uniquely identifies the corresponding service within the scope of the corresponding broadcast service.
  • the @serviceId attribute may be an attribute used as a mandatory.
  • the @sltSvcSeqNum attribute is the same attribute as the @serviceId attribute of the ViewerService element described above and may indicate a version of SLT service information for the corresponding service.
  • the @sltSvcSeqNum attribute may be an attribute used as a mandatory.
  • the @serviceCategory attribute may indicate a category of a service.
  • the @serviceCategory attribute of the NativeService element may indicate a service category indicating a native service.
  • the @serviceCategory attribute of the NativeService element may have a value of a service category indicating an ESG service or an EAS service.
  • the @serviceCategory attribute may be an attribute used as a mandatory.
  • the SignalingLoc element may be the same sub-element as the SignalingLoc element of the ViewerService element described above and may indicate a location and a protocol for signaling.
  • the SLT information may include a ViewerService element for the Viewer service and a NativeService element for the Native service, and may provide information about the Viewer service and information about the Native service through each element.
  • the SLT information may include one or more Service elements for a service having a broad meaning including a Viewer service and a Native service, and in this case, the SLT information may include each Service element.
  • SLT information is not 1) to provide service-related information using other types of service-related elements (eg, ViewerService element or NativeService element) according to the type of service, as shown in FIG.
  • service related information including information on a type of a corresponding service may be provided through a single type of service related element (eg, a service element).
  • the service element may include at least one of an attribute and a sub element included in the ViewerService element and the NativeService element.
  • the Service element in the SLT information may include the above-described @serviceId attribute, @sltSvcSeqNum attribute, @protected attribute, @majorChannelNo attribute, @minorChannelNo attribute, @serviceCategory attribute, @shortServiceName attribute, @hidden attribute, SignalingLoc subelement, @slsProtocolType Include the following properties: @slsMajorProtocolVersion property, @SlsMinorProtocolVersion property, @slsPlpId property, @slsDestinationIpAddress property, @slsDestinationUdpPort property, @slsSourceIpAddress property, @svcInetSigUri property, @serviceLanguage property, @broadbandAccessRequi
  • the cardinality or value of the attribute and sub element included in the Service element may be different from the cardinality or value of the same attribute and sub element included in the ViewerService element or the NativeService element.
  • @majorChannelNo attribute, @minorChannelNo, and @shortServiceName attributes in the ViewerService element described above are attributes used as manholes
  • the @majorChannelNo attribute, @minorChannelNo, and @shortServiceName attributes in the Service element are optional.
  • an @majorChannelNo attribute, an @minorChannelNo and an @shortServiceName attribute are required to provide a channel number, a short service name, etc.
  • an EAS service or an ESG is required.
  • the @serviceCategory attribute in the ViewerService element described above includes code values that indicate the category of the viewer service and the @serviceCategory attribute of the NativeService element contains code values that indicate the category of the native service, while the Service element
  • the @serviceCategory attribute in may include code values indicating the category of the native service as well as the viewer service. This is because the service element is an element that provides information on a broad meaning of a service including a viewer service and a native service.
  • code values of the @serviceCategory attribute in the service element may be as shown in Table 1 below.
  • the value of the @serviceCategory attribute is "0", it means that the service is not specified, and if the value is "1”, it means linear audio / video service, and if the value is "2", linear Audio-only service; a value of "3” means an app-based service; a value of "4" means a linear audio / video service with app-based enhancement, the value of " 5 "means only the service of Leading Audio with app-based enhancement, the value of" 6 “means the program guide related ESG service, and the value” 7 "means the emergency alert related EAS service. Values other than, may be reserved values for future use.
  • the SLT information may include an @sltInetSigUri attribute and an @sltInetEsgUrl attribute.
  • the @sltInetSigUri attribute and the @sltInetEsgUrl attribute may be attributes included in an SLT element that is a root element.
  • the @sltInetSigUri attribute may provide base URL information used to obtain service signaling information for services of the corresponding SLT through broadband
  • the @sltInetEsgUrl attribute may provide a URL for obtaining ESG data for services of the corresponding SLT. Can be.
  • the @sltInetSigUri attribute and the @sltInetEsgUrl attribute of the SLT element may be collectively referred to as a sltInetUrl element.
  • the sltInetUrl element may provide URL information for obtaining service layer signaling information or ESG information for services in the corresponding SLT.
  • the sltInetUrl element may include an @urlType attribute, and the @urlType attribute may indicate the type of files (information) available with the sltInetUrl element. Through the @urlType attribute in the sltInetUrl element, it may be signaled whether the URL information provided by the sltInetUrl element is URL information for obtaining ESG information or URL information for obtaining service layer signaling information.
  • the SLT information may include an @svcInetSigUri attribute and an @svcInetEsgUrl attribute.
  • the @svcInetSigUri attribute and the @svcInetEsgUrl attribute may be attributes included in the service element in the SLT element.
  • the @svcInetSigUri attribute may provide base URL information used to obtain service signaling information for the corresponding service through broadband, and the @svcInetEsgUrl attribute may provide a URL for obtaining ESG data for the corresponding service.
  • the @sltInetSigUri attribute and the @sltInetEsgUrl attribute of the service element may be collectively referred to as a svcInetUrl element.
  • the svcInetUrl element may provide URL information for obtaining service layer signaling information or ESG information for a corresponding service.
  • the svcInetUrl element may include an @urlType attribute, and the @urlType attribute may indicate the type of files (information) available with the svcInetUrl element.
  • the @urlType attribute in the svcInetUrl element it may be signaled whether the URL information provided by the svcInetUrl element is URL information for obtaining ESG information or information for obtaining service layer signaling information.
  • this attribute is the base URL for making an HTTP request for signaling metadata.
  • Desired signaling objects to be returned may be indicated by appending a path term to the base URL (instead of using a query term). Since no server-side application is required to retrieve the requested objects, this makes it possible to retrieve the signaling object more efficiently from a server perspective. Each search can simply fetch files. To make this request, a GET method may be used, and a path appended to the end of the base URL may include a request signaling object or terms that indicate the objects.
  • One embodiment of the path terms is as indicated in Table 2 below.
  • the service_id term may be used to indicate the service to which the requested signaling metadata object is applied. If the service_id term does not exist, signaling metadata objects for all services in the section may be requested.
  • the service_id term may be referred to as a service term.
  • template term may indicate whether a normal form of the metadata object (s), a diff form of the metadata object (s), or a template form of the metadata object (s) is requested. If a normal form is requested, the "nomal" term may be omitted.
  • template term may be referred to as a mode term.
  • next term may indicate whether the current version of the metadata object (s) or the next version of the metadata object (s) after the current version has been requested. If the current virgin is requested, the "current" term can be omitted.
  • next term may be referred to as a version term.
  • AEI term that is, the fourth term, indicates what type of metadata object (s) is requested. Can be used to indicate. The supported types and their descriptions are listed in Table 3 below. The fourth term may be referred to as a type term.
  • URLs for HTTP requests for signaling metadata objects are as follows.
  • the same paths may be added after the same semantics.
  • the service term may be excluded.
  • the response body for HTTP requests may include an MBMS metadata envelope that includes an "item” element for each signaling object included in the response.
  • Zero or one of the signaling objects may be embedded within an “item” element, as specified in the MBMS standard. Any signaling objects that are not embedded can be referenced in their item element, and they can be packaged together in a metadata envelope in a multi-part MIME message, in the order in which they were referenced.
  • the URL can be used to retrieve ESG data for all services in the SLT over broadband. If the svcInetEsgUri attribute is present, the URL may be used to retrieve ESG data for a service with the same service_id as the service element for which the svcInetEsgUri attribute is present over broadband. In both cases, the URL may be used for queries such as those specified in the ATSC 3.0 broadcast service announcement and personalization standard.
  • FIG. 15 illustrates a service discovery process according to another embodiment of the present invention.
  • FIG. 15 illustrates a service discovery process using SLT information.
  • the SLT information may be delivered through one PLP, and whether the SLT information exists in the corresponding PLP may be indicated through the L1 signaling information.
  • the same description as in FIG. 2 is omitted.
  • the signal frame of the physical layer may carry physical layer signaling (PLS) information.
  • PLS physical layer signaling
  • the broadcast stream carried by the signal frame of the physical layer may carry PLS information.
  • the PLS information may be referred to as Layer 1 (L1) signaling information.
  • the L1 signaling information may include bootstrap, L1 basic information, and L1 detail information.
  • the L1 basic information may include the most basic (fundamental) signaling information of the system and the parameter information necessary for decoding the L1 detail information.
  • the L1 detail information may include a data context and information necessary to decode the data context.
  • the L1 detail information may include flag information indicating whether the corresponding PLP includes LLS information.
  • the L1 detail information may include SLT_exist (SLT flag) information indicating whether the corresponding PLP includes SLT information.
  • the SLT flag information may be set to a value (eg, 1) indicating "true”.
  • the SLT flag information may be set to a value (eg, 0) indicating "false”. That is, if there is an SLT in the corresponding PLP, the SLT flag information set to the "true” value is signaled through the L1 detail information, and if the SLT does not exist in the corresponding PLP, the SLT flag information set to the "false” value is transmitted through the L1 detail information May be signaled.
  • the broadcast receiver parses only the L1 signaling information, so as to determine whether the corresponding PLP includes SLT information or LLS information including SLT information. Therefore, the broadcast receiver can reduce the operation of informing the upper system module of the PLP ID through I2C, thereby reducing the burden of implementing the receiver.
  • the signal frame of the physical layer may carry SLT information.
  • the broadcast stream carried by the signal frame of the physical layer may carry SLT information.
  • the SLT information may be included in the LLS information and carried.
  • SLT information or LLS information including SLT information may be encapsulated in a UDP / IP packet and carried.
  • the SLT information or the LLS information may be carried through a payload of an IP packet delivered to a well known IP address / port.
  • an IP stream carrying SLT information or LLS information may be delivered to the same PLP along with other service data.
  • the SLT information may enable the receiver to generate a service list through a quick channel scan and provide access information for locating Service Layer Signaling (SLS) information.
  • the SLT information includes bootstrap information, which enables the receiver to obtain SLS information for each service.
  • the bootstrap information may include a 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 information for service # 1 described by the SLT information may be encoded based on the ROUTE protocol and encapsulated in a UDP / IP packet, and the SLT information may be delivered.
  • Bootstrap information (sIP1, dIP1, dPort1) for the ROUTE session including the LCT channel may be included.
  • the SLS information of service # 2 described by the SLT information may be encoded based on the MMT protocol, encapsulated into a UDP / IP packet, and delivered, and the SLT information may include an MMTP packet flow in which the SLS information is delivered.
  • Bootstrap information (sIP2, dIP2, dPort2) for may be included.
  • the SLS information is delivered through the ROUTE protocol, that is, the SLS information is encoded based on the ROUTE protocol, the SLT information is identified by a dedicated LCT channel (eg, tsi-SLS) of the ROUTE session indicated by the SLT information.
  • LCT channel e.g, tsi-SLS
  • the SLS information 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 and the like.
  • the service identification information in the USBD may have the same value (0x1001) as the service identification information for the service # 1 in the SLT information.
  • the USBD may include reference information (URI reference) to other SLS fragments (S-TSID, MPD, etc.).
  • 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 transport session description information (tsi-v, etc.) for the ROUTE session (RS) and the LCT channel (LS) to which the video component (segment) related to service # 1 is delivered. have.
  • the S-TSID may provide transport session description information (tsi-a, etc.) for the ROUTE session RS and the LCT channel LS to which an audio component (segment) related to service # 1 is delivered.
  • 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 media segments and provide contextual information within the media presentation for the identified resources.
  • the MPD may provide period information for video and audio components related to service # 1.
  • the SLS information When the SLS information is delivered through the MMT protocol, i.e., when the SLS information is encoded based on the MMT protocol, the SLS information is a dedicated MMTP packet flow (e.g., packet-signling) of the MMTP session indicated by the SLT information. (Identified MMTP packet flow).
  • the SLS information may include a USBD / USD and / or MMT Package (MP) table.
  • the USBD is one of the SLS fragments, and may describe specific technical information of a service including service identification information, such as USBD in ROUTE.
  • the service identification information in the USBD may have the same value (0x1002) as the service identification information for the service # 2 in the SLT information.
  • the USBD of the MMT may also include reference information (URI reference) to another SLS fragment.
  • the USBD of the MMT may refer to the MP table of the MMT signaling.
  • the USBD of the MMT may include signaling information about a component transmitted through a delivery path other than the MMT protocol. This will be described in detail below with reference to FIG. 16.
  • the MP table is an MMT signaling message 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 (MMT Signaling Message) may provide overall session description information for the MPU components (Video MPUs and Audio MPUs) associated with service # 2.
  • 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).
  • FIG. 16 illustrates a USBD of SLS information transmitted through an MMT protocol according to an embodiment of the present invention.
  • the USBD of the MMT may provide signaling information about a component transmitted through a delivery path other than the MMT protocol.
  • the USBD of the MMT may provide signaling information about the content component of the service delivered by the ROUTE protocol and / or information about the content component of the service delivered through broadband in the hybrid service delivery.
  • the MMT's USBD includes a routeComponent element (atsc: routeComponent) that provides a description of the service component delivered by the ROUTE protocol and a broadbandComponent element (atsc: broadbandComponent) that provides a description of the service component delivered by broadband. It may include.
  • the routeComponent element may include an sTSIDUri attribute (@atsc: sTSIDUri), an sTSIDMajorProtocolVersion attribute (@atsc: sTSIDMajorProtocolVersion), and / or an sTSIDMinorProtocolVersion attribute (@atsc: sTSIDMinorProtocolVersion).
  • the sTSIDUri attribute may provide reference information to the S-TSID fragment that provides parameters related to access to the transport session carrying the content of the corresponding service.
  • the sTSIDMajorProtocolVersion attribute may provide a major version number of a protocol used for delivering SLS information of a corresponding service. In this case, the default value may be 1.
  • the sTSIDMinorProtocolVersion attribute may provide a minor version number of a protocol used for delivering SLS information of a corresponding service. In this case, the default value may be 0.
  • the broadbandComponent element may include a fullMPDUri attribute (@atsc: fullMPDUri), an sTSIDMajorProtocolVersion attribute (@atsc: sTSIDMajorProtocolVersion), and / or an sTSIDMinorProtocolVersion attribute (@atsc: sTSIDMinorProtocolVersion).
  • the fullMPDUri attribute may provide referencing information to an MPD fragment including a description of a content component of a service delivered through broadband.
  • the sTSIDMajorProtocolVersion attribute may provide a major version number of a protocol used to deliver SLS information of a corresponding service. In this case, the default value may be 1.
  • the sTSIDMinorProtocolVersion attribute may provide a minor version number of a protocol used to deliver SLS information of a corresponding service. In this case, the default value may be 0.
  • FIG. 17 illustrates a broadcast signal transmission method according to an embodiment of the present invention.
  • the broadcast transmitter may generate service data for the broadcast service and service layer signaling (SLS) information on the service data (S17010).
  • the service data is data supporting a function provided by the broadcast service and may include media segments (audio segments, video segments, etc.).
  • the SLS information may be signaling information including information for discovery and acquisition of service data.
  • the SLS information may be referred to as service level signaling or first level signaling.
  • the broadcast transmitter may encode the service data and the SLS information based on the delivery protocol (S17020).
  • the delivery protocol through which service data and SLS information are delivered may be a Real-Time Object Delivery over Unidirectional Transport (ROUTE) protocol or an MPEG Media Transport (MMT) protocol. Meanwhile, the same delivery protocol may be applied to the service data and the SLS information. That is, when broadcast service data is encoded in the MMT protocol, the SLS information for the broadcast service data may be encoded in the MMT protocol. In addition, when broadcast service data is encoded in the ROUTE protocol, SLS information for the broadcast service may be encoded in the ROUTE protocol.
  • ROUTE Real-Time Object Delivery over Unidirectional Transport
  • MMT MPEG Media Transport
  • the broadcast transmitter may generate service list table (SLT) information about service data (S17030).
  • SLT service list table
  • the SLT information is signaling information for providing discovery of SLS information and building of a basic service list
  • the SLT information may include bootstrap information for discovery of SLS information.
  • the SLT may include first bootstrap information for discovery of SLS information delivered in a ROUTE protocol, and the first bootstrap information includes source_IP_address information, destination_IP_address information, and / or destination_UDP_port information for the SLS information. can do.
  • the SLT may include second bootstrap information for discovery of SLS information delivered by the MMT protocol, and the second bootstrap information may include source_IP_address information, destination_IP_address information, and / or destination_UDP_port information for the SLS information. It may include.
  • the receiver may acquire the SLS for the broadcast service based on the bootstrap information, and obtain the service data based on the SLS.
  • SLT information may be referred to as second level signaling.
  • the SLT information may include URL information that provides a base URL for acquiring signaling information about one or more services through broadband.
  • the base URL may be used to generate an HTTP request message for the signaling information together with one or more path terms.
  • the at least one path term includes service information for identifying a requested service, mode information for identifying a requested mode of signaling information, version information for identifying a requested version of signaling information, and requested information for signaling information. It may include at least one of the type information for identifying the type.
  • the URL information may include first URL information for providing first base URL for obtaining signaling information for all services in the SLT information or second base URL for obtaining signaling information for a specific service in the SLT information. It may include the provided second URL information.
  • the SLT information may be delivered via low level signaling (LLS) information. That is, the SLT information may be included in the LLS information and transmitted. In this case, the SLT information may be included in the body (or payload) of the LLS information.
  • LLS low level signaling
  • the LLS information may include provider id information for identifying a broadcaster using part or all of the broadcast stream. As described above, one broadcast stream may be shared by multiple broadcasters. In this case, each broadcaster sharing the broadcast stream may be identified by provider identification information in the LLS information.
  • the LLS information may further include LLS table identification information for identifying signaling information delivered through the LLS information and LLS table version information indicating a version of the LLS information.
  • the LLS information when the LLS table identification information has the first value, the LLS information includes the SLT information, and when the LLS table identification information has the second value, the LLS information may include information related to the rating for the service data. It may include RRT information.
  • the above-described provider identification information, LLS table identification information and LLS table version information may be included in the header of the LLS information.
  • the broadcast transmitter may encapsulate service data, SLS information, and SLT information, respectively, in User Datagram Protocol (UDP) / IP (Internet Protocol) (S28040).
  • UDP User Datagram Protocol
  • IP Internet Protocol
  • S28040 User Datagram Protocol
  • UDP / IP encapsulated service data, SLS information, and SLT information may be identified as IP packets by IP address and port number. Therefore, data transmitted by the broadcast transmitter according to the present invention may be operated / identified based on IP.
  • the broadcast transmitter may generate a signal frame by performing physical layer processing on the service data, the SLS information, and the SLT information (S28050).
  • the signal frame may be referred to as layer 1 (L1) signaling information.
  • the L1 signaling information may include bootstrap, L1 basic information, and L1 detail information.
  • the L1 detail information may include flag information indicating whether the corresponding PLP includes LLS information.
  • the L1 detail information may include SLT flag information (SLT_exist information) indicating whether the corresponding PLP includes SLT information.
  • FIG. 18 illustrates a broadcast signal transmitter and a broadcast signal receiver according to an embodiment of the present invention.
  • the broadcast signal transmitter 18100 may include a signaling generator 18110, a delivery layer encoder 18120, a UDP / IP encapsulator 18130, and a physical layer processor 18140.
  • the signaling generator 18110 may generate service layer signaling (SLS) information on service data for broadcast service and service list table (SLT) information on the service data.
  • SLS service layer signaling
  • SLT service list table
  • the delivery layer encoder 18120 may encode service data and the SLS information based on a delivery protocol.
  • the delivery protocol may include at least one of a Real-Time Object Delivery over Unidirectional Transport (ROUTE) protocol or an MPEG Media Transport (MMT) protocol.
  • ROUTE Real-Time Object Delivery over Unidirectional Transport
  • MMT MPEG Media Transport
  • the UDP / IP encapsulator 18130 may encapsulate service data, SLS information, and SLT information, respectively, by User Datagram Protocol (UDP) / Internet Protocol (IP).
  • UDP User Datagram Protocol
  • IP Internet Protocol
  • the physical layer processor 18140 may generate a signal frame by performing physical layer processing on the service data, the SLS information, and the SLT information.
  • the broadcast signal transmitter 18100 of FIG. 18 performs the above-described broadcast signal transmission method, and the same description is not repeated.
  • the broadcast signal receiver 18200 may include a signaling parser 18610, a delivery layer decoder 18220, a UDP / IP packet parser 18230, and a physical layer parser 18240.
  • the broadcast signal receiver 18200 may perform a reverse operation of the broadcast signal transmitter.
  • the physical layer parser 18240 may perform physical layer processing of the received signal frame to output a UDP / IP packet stream including service component data.
  • the UDP / IP packet parser 18230 may output the service component data by decapsulating the received IP packet stream.
  • the delivery layer decoder 18220 may decode service component data according to a delivery protocol.
  • the signaling parser 18610 may control the operation of the broadcast signal receiver by obtaining and parsing signaling information.
  • the broadcast signal receiver may acquire an SLT and parse the SLT to obtain an IP address and a port number of the required SLS.
  • the broadcast signal receiver may parse the SLS to obtain a transmission path of necessary service data.
  • the broadcast signal receiver may provide a corresponding broadcast service to a user by physical layer parsing and delivery layer decoding of necessary broadcast data along the entire path.
  • subunits of a broadcast signal transmitter and a broadcast signal receiver are classified according to their operation. That is, one sub unit does not have to be implemented as one physical processor, one sub unit may be implemented by a plurality of physical processors, or a plurality of sub units may be implemented by one physical processor.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Human Computer Interaction (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Abstract

L'invention concerne un procédé d'émission d'un signal de radiodiffusion. Selon un mode de réalisation de la présente invention, un procédé d'émission d'un signal de radiodiffusion comprend les étapes consistant à : effectuer un traitement de couche de distribution de données de service de radiodiffusion et d'informations de signalisation sur les données de service de radiodiffusion ; à effectuer une encapsulation UDP/IP des données de service de radiodiffusion et des informations de signalisation pour les données de service de radiodiffusion ; et à effectuer un traitement de couche physique des données de service de radiodiffusion et des informations de signalisation pour les données de service de radiodiffusion.
PCT/KR2016/008979 2015-08-17 2016-08-16 Appareil et procédé pour émettre et recevoir un signal de radiodiffusion WO2017030344A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201562205753P 2015-08-17 2015-08-17
US62/205,753 2015-08-17
US201562211858P 2015-08-30 2015-08-30
US62/211,858 2015-08-30

Publications (1)

Publication Number Publication Date
WO2017030344A1 true WO2017030344A1 (fr) 2017-02-23

Family

ID=58052083

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2016/008979 WO2017030344A1 (fr) 2015-08-17 2016-08-16 Appareil et procédé pour émettre et recevoir un signal de radiodiffusion

Country Status (1)

Country Link
WO (1) WO2017030344A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20090021120A (ko) * 2007-08-24 2009-02-27 엘지전자 주식회사 디지털 방송 시스템 및 데이터 처리 방법
WO2010000928A1 (fr) * 2008-07-03 2010-01-07 Nokia Corporation Encapsulation de contenu de diffusion non sélective
US20120051320A1 (en) * 2010-08-26 2012-03-01 Nokia Corporation Providing signaling information and performing a handover using the signaling information
WO2012036429A2 (fr) * 2010-09-14 2012-03-22 엘지전자 주식회사 Appareil d'émission de signaux de radiodiffusion, appareil de réception de signaux de radiodiffusion et procédé d'émission/réception de signaux de radiodiffusion par l'intermédiaire de l'appareil d'émission/réception de signaux de radiodiffusion
WO2014209057A1 (fr) * 2013-06-27 2014-12-31 엘지전자 주식회사 Procédé et dispositif pour émettre et recevoir un service de diffusion dans un système de diffusion hybride sur la base d'une connexion d'un réseau de diffusion terrestre et d'un réseau à protocole internet

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20090021120A (ko) * 2007-08-24 2009-02-27 엘지전자 주식회사 디지털 방송 시스템 및 데이터 처리 방법
WO2010000928A1 (fr) * 2008-07-03 2010-01-07 Nokia Corporation Encapsulation de contenu de diffusion non sélective
US20120051320A1 (en) * 2010-08-26 2012-03-01 Nokia Corporation Providing signaling information and performing a handover using the signaling information
WO2012036429A2 (fr) * 2010-09-14 2012-03-22 엘지전자 주식회사 Appareil d'émission de signaux de radiodiffusion, appareil de réception de signaux de radiodiffusion et procédé d'émission/réception de signaux de radiodiffusion par l'intermédiaire de l'appareil d'émission/réception de signaux de radiodiffusion
WO2014209057A1 (fr) * 2013-06-27 2014-12-31 엘지전자 주식회사 Procédé et dispositif pour émettre et recevoir un service de diffusion dans un système de diffusion hybride sur la base d'une connexion d'un réseau de diffusion terrestre et d'un réseau à protocole internet

Similar Documents

Publication Publication Date Title
WO2017014586A1 (fr) Dispositif et procédé d'émission et de réception de signal de radiodiffusion
WO2016140486A1 (fr) Appareil et procédé d'émission/réception de signal de diffusion
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
WO2016186407A1 (fr) Appareil et procédé d'émission ou 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
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
WO2017209514A1 (fr) Dispositif et procédé d'émission et de réception de signal de diffusion
WO2017204546A1 (fr) Dispositif et procédé d'émission/réception de signaux 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
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
WO2018101566A1 (fr) Dispositif et procédé d'émission/réception de signal de radiodiffusion
WO2017061792A1 (fr) Dispositif et procédé d'émission/réception de signal 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
WO2016068564A1 (fr) Appareil et procédé d'émission de signal de diffusion, appareil et procédé de réception de signal de diffusion
WO2016122269A1 (fr) Dispositif de transmission de signaux de radiodiffusion, dispositif de réception de signaux de radiodiffusion, procédé de transmission de signaux de radiodiffusion et procédé de réception de signaux de radiodiffusion
WO2017164595A1 (fr) Dispositif et procédé d'émission/réception de signal de diffusion
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
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
WO2016129904A1 (fr) Appareil d'émission de signal de radiodiffusion, appareil 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
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
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
WO2017043898A1 (fr) Appareil et procédé pour émettre et recevoir un signal de radiodiffusion
WO2017026714A1 (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

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: 16837286

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: 16837286

Country of ref document: EP

Kind code of ref document: A1

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载