WO2018101566A1 - 방송 신호 송수신 장치 및 방법 - Google Patents
방송 신호 송수신 장치 및 방법 Download PDFInfo
- Publication number
- WO2018101566A1 WO2018101566A1 PCT/KR2017/007217 KR2017007217W WO2018101566A1 WO 2018101566 A1 WO2018101566 A1 WO 2018101566A1 KR 2017007217 W KR2017007217 W KR 2017007217W WO 2018101566 A1 WO2018101566 A1 WO 2018101566A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- service
- delivered
- information
- channel
- broadcast
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 94
- 230000011664 signaling Effects 0.000 claims abstract description 96
- 238000012545 processing Methods 0.000 claims abstract description 35
- 230000010076 replication Effects 0.000 claims description 53
- 230000008054 signal transmission Effects 0.000 claims description 31
- 230000008569 process Effects 0.000 claims description 25
- 238000004891 communication Methods 0.000 claims description 18
- VKALYYFVKBXHTF-UHFFFAOYSA-N 4-(methylsulfanyl)-m-cresol Chemical compound CSC1=CC=C(O)C=C1C VKALYYFVKBXHTF-UHFFFAOYSA-N 0.000 description 29
- 230000005540 biological transmission Effects 0.000 description 28
- 101000596046 Homo sapiens Plastin-2 Proteins 0.000 description 17
- 102100035182 Plastin-2 Human genes 0.000 description 17
- 230000006978 adaptation Effects 0.000 description 15
- 235000007682 pyridoxal 5'-phosphate Nutrition 0.000 description 15
- 230000006835 compression Effects 0.000 description 14
- 238000007906 compression Methods 0.000 description 14
- 239000012634 fragment Substances 0.000 description 14
- 238000005538 encapsulation Methods 0.000 description 11
- 238000012986 modification Methods 0.000 description 8
- 230000004048 modification Effects 0.000 description 8
- 101000596041 Homo sapiens Plastin-1 Proteins 0.000 description 7
- 102100035181 Plastin-1 Human genes 0.000 description 7
- 238000013507 mapping Methods 0.000 description 7
- 230000009467 reduction Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 6
- 230000003068 static effect Effects 0.000 description 6
- 230000006837 decompression Effects 0.000 description 4
- 239000012092 media component Substances 0.000 description 4
- 238000011946 reduction process Methods 0.000 description 4
- 238000002716 delivery method Methods 0.000 description 3
- 230000001934 delay Effects 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 238000000605 extraction Methods 0.000 description 2
- 238000003780 insertion Methods 0.000 description 2
- 230000037431 insertion Effects 0.000 description 2
- 230000008439 repair process Effects 0.000 description 2
- 101100256965 Caenorhabditis elegans sip-1 gene Proteins 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000000295 complement effect Effects 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000008030 elimination Effects 0.000 description 1
- 238000003379 elimination reaction Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000006798 recombination Effects 0.000 description 1
- 238000005215 recombination Methods 0.000 description 1
- 230000011218 segmentation Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L27/00—Modulated-carrier systems
- H04L27/26—Systems using multi-frequency codes
- H04L27/2601—Multicarrier modulation systems
- H04L27/2602—Signal structure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/236—Assembling of a multiplex stream, e.g. transport stream, by combining a video stream with other content or additional data, e.g. inserting a URL [Uniform Resource Locator] into a video stream, multiplexing software data into a video stream; Remultiplexing of multiplex streams; Insertion of stuffing bits into the multiplex stream, e.g. to obtain a constant bit-rate; Assembling of a packetised elementary stream
- H04N21/23605—Creation or processing of packetized elementary streams [PES]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/236—Assembling of a multiplex stream, e.g. transport stream, by combining a video stream with other content or additional data, e.g. inserting a URL [Uniform Resource Locator] into a video stream, multiplexing software data into a video stream; Remultiplexing of multiplex streams; Insertion of stuffing bits into the multiplex stream, e.g. to obtain a constant bit-rate; Assembling of a packetised elementary stream
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/236—Assembling of a multiplex stream, e.g. transport stream, by combining a video stream with other content or additional data, e.g. inserting a URL [Uniform Resource Locator] into a video stream, multiplexing software data into a video stream; Remultiplexing of multiplex streams; Insertion of stuffing bits into the multiplex stream, e.g. to obtain a constant bit-rate; Assembling of a packetised elementary stream
- H04N21/2362—Generation or processing of Service Information [SI]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/238—Interfacing the downstream path of the transmission network, e.g. adapting the transmission rate of a video stream to network bandwidth; Processing of multiplex streams
- H04N21/2381—Adapting the multiplex stream to a specific network, e.g. an Internet Protocol [IP] network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/238—Interfacing the downstream path of the transmission network, e.g. adapting the transmission rate of a video stream to network bandwidth; Processing of multiplex streams
- H04N21/2385—Channel allocation; Bandwidth allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/238—Interfacing the downstream path of the transmission network, e.g. adapting the transmission rate of a video stream to network bandwidth; Processing of multiplex streams
- H04N21/2389—Multiplex stream processing, e.g. multiplex stream encrypting
-
- 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/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/438—Interfacing the downstream path of the transmission network originating from a server, e.g. retrieving encoded video stream packets from an IP network
- H04N21/4381—Recovering the multiplex stream from a specific network, e.g. recovering MPEG packets from ATM cells
-
- 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
- H04N21/615—Signal processing at physical level
-
- 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/631—Multimode Transmission, e.g. transmitting basic layers and enhancement layers of the content over different transmission paths or transmitting with different error corrections, different keys or with different transmission 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/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
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
- H04L1/0041—Arrangements at the transmitter end
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
- H04L1/0056—Systems characterized by the type of code used
- H04L1/0057—Block codes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
- H04L1/0056—Systems characterized by the type of code used
- H04L1/0071—Use of interleaving
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 comprises the steps of: processing at least one component of a broadcast service based on a delivery protocol; Generating service layer signaling (SLS) information including information on the component, wherein the SLS information includes S-TSID including description information of a session carrying at least one component of the broadcast service; based Transport Session Instance Description) information; Generating service list table (SLT) information including bootstrap information for obtaining the SLS information; And generating a signal frame including a physical layer pipe (PLP) by physical layer processing the at least one component, the SLS information, and the SLT information;
- SLS service layer signaling
- SLS Service layer signaling
- SLT Service list table
- PLP physical layer pipe
- the physical layer processing step includes one PLP including the service portion or service duplication. And selectively performing channel bonding for distributing to a plurality of channels, wherein the service portion or the service replication is delivered to a single channel without the channel bonding application, or the channel bonding is applied to the plurality of channels.
- the service portion or the SLT of the channel where the service replication is delivered is the service portion or the service The replication is described, and the service portion or the PLP of each channel through which the service replication is delivered includes the S-TSID information for the service portion or the service replication.
- the service portion when the service portion is channel bonded and delivered, when the essential portion is delivered to a non-bonded PLP, a non-delivering arbitrary portion of the service is delivered.
- Bonded PLPs and a plurality of SLT information associated with the bonded PLPs list the service, and only the SLT information for the essential portion lists the Broadcast Stream ID (BSID) of the broadcast stream from which other potions are delivered.
- BSID Broadcast Stream ID
- the essential portion when the service portion is channel bonded and delivered, the essential portion is associated with the bonded PLP that delivers the essential portion when the essential portion is delivered to the bonded PLP.
- One SLT information lists the service, and the SLT information lists the BSID (Broadcast Stream ID) of the broadcast stream in which the other portion is delivered.
- a non-bonded PLP for delivering the service and a plurality of SLT informations associated with the bonded PLP are delivered.
- the S-TSID is the S-TSID. Describes session and channel information for components that are delivered in a broadcast stream other than the broadcast stream for which it is delivered.
- the broadcast signal transmission apparatus a communication unit for transmitting a broadcast signal; A memory for storing data; And a processor for controlling the communication unit and the memory, wherein the broadcast signal transmission apparatus processes at least one component of a broadcast service based on a delivery protocol, and includes information about the component.
- Generating service layer signaling (SLS) information wherein the SLS information includes service-based transport session instance description (S-TSID) information including description information of a session carrying at least one component of the broadcast service; And generating service list table (SLT) information including bootstrap information for obtaining the SLS information, and physical layer processing the at least one component, the SLS information, and the SLT information.
- SLS service layer signaling
- S-TSID service-based transport session instance description
- SLT service list table
- the set of components corresponds to a service portion containing some components of the service or a service duplicate including all components of the service, the service portion being a service without the use of other portions Corresponds to the available essential potion or non-essential potion.
- 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 SLT information according to an embodiment of the present invention.
- 16 and 17 illustrate a method of constructing a broadcast signal according to an embodiment of the present invention.
- FIG. 20 illustrates a configuration of a broadcast signal transmission / reception apparatus according to an embodiment of the present invention.
- FIG. 21 illustrates a broadcast signal transmission method according to an embodiment of the present invention.
- FIG. 22 illustrates a broadcast signal receiving method according to an embodiment of the present invention.
- the present invention provides an apparatus and method for transmitting and receiving broadcast signals for next generation broadcast services.
- the next generation broadcast service includes a terrestrial broadcast service, a mobile broadcast service, a UHDTV service, and the like.
- a broadcast signal for a next generation broadcast service may be processed through a non-multiple input multiple output (MIMO) or MIMO scheme.
- the non-MIMO scheme according to an embodiment of the present invention may include a multiple input single output (MISO) scheme, a single input single output (SISO) scheme, and the like.
- MISO multiple input single output
- SISO single input single output
- the present invention proposes a physical profile (or system) that is optimized to minimize receiver complexity while achieving the performance required for a particular application.
- FIG. 1 is a diagram illustrating a protocol stack according to an embodiment of the present invention.
- the service may be delivered to the receiver through a plurality of layers.
- the transmitting side can generate service data.
- the delivery layer on the transmitting side performs processing for transmission to the service data, and the physical layer encodes it as a broadcast signal and transmits it through a broadcasting network or broadband.
- the service data may be generated in a format according to ISO BMFF (base media file format).
- the ISO BMFF media file may be used in broadcast network / broadband delivery, media encapsulation and / or synchronization format.
- the service data is all data related to the service, and may include a concept including service components constituting the linear service, signaling information thereof, non real time (NRT) data, and other files.
- the delivery layer will be described.
- the delivery layer may provide a transmission function for service data.
- the service data may be delivered through a broadcast network and / or broadband.
- the first method may be to process service data into Media Processing Units (MPUs) based on MPEG Media Transport (MMT) and transmit the data using MMM protocol (MMTP).
- MPUs Media Processing Units
- MMT MPEG Media Transport
- MMTP MMM protocol
- the service data delivered through the MMTP may include service components for linear service and / or service signaling information thereof.
- the second method may be to process service data into DASH segments based on MPEG DASH and transmit it using Real Time Object Delivery over Unidirectional Transport (ROUTE).
- the service data delivered through the ROUTE protocol may include service components for the linear service, service signaling information and / or NRT data thereof. That is, non-timed data such as NRT data and files may be delivered through ROUTE.
- Data processed according to the MMTP or ROUTE protocol may be processed into IP packets via the UDP / IP layer.
- a service list table (SLT) may also be transmitted through a broadcasting network through a UDP / IP layer.
- the SLT may be included in the LLS (Low Level Signaling) table and transmitted.
- LLS Low Level Signaling
- 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 referred to as a service signaling channel.
- the S-TSID, the USBD / USD, the MPD, or the LCT session carrying them may be referred to as a service signaling channel.
- MMT signaling messages or packet flow carrying them may be called a service signaling channel.
- one ROUTE or MMTP session may be delivered through a plurality of PLPs. That is, one service may be delivered through one or more PLPs. Unlike shown, components constituting one service may be delivered through different ROUTE sessions. In addition, according to an embodiment, components constituting one service may be delivered through different MMTP sessions. According to an embodiment, components constituting one service may be delivered divided into a ROUTE session and an MMTP session. Although not shown, a component constituting one service may be delivered through a broadband (hybrid delivery).
- LLS low level signaling
- SLT service list table
- An embodiment t3010 of the illustrated LLS table may include information according to an LLS_table_id field, a provider_id field, an LLS_table_version field, and / or an LLS_table_id field.
- the LLS_table_id field may identify a type of the corresponding LLS table, and the provider_id field may identify service providers related to services signaled by the corresponding LLS table.
- the service provider is a broadcaster using all or part of the broadcast stream, and the provider_id field may identify one of a plurality of broadcasters using the broadcast stream.
- the LLS_table_version field may provide version information of a corresponding LLS table.
- the corresponding LLS table includes the above-described SLT, a rating region table (RRT) including information related to a content advisory rating, a SystemTime information providing information related to system time, and an emergency alert. It may include one of the CAP (Common Alert Protocol) message that provides information related to. According to an embodiment, other information other than these may be included in the LLS table.
- RRT rating region table
- CAP Common Alert Protocol
- One embodiment t3020 of the illustrated SLT may include an @bsid attribute, an @sltCapabilities attribute, a sltInetUrl element, and / or a Service element.
- Each field may be omitted or may exist in plurality, depending on the value of the illustrated Use column.
- the @bsid attribute may be an identifier of a broadcast stream.
- the @sltCapabilities attribute can provide the capability information required to decode and significantly reproduce all services described by the SLT.
- the sltInetUrl element may provide base URL information used to obtain ESG or service signaling information for services of the corresponding SLT through broadband.
- the sltInetUrl element may further include an @urlType attribute, which may indicate the type of data that can be obtained through the URL.
- the service element may be an element including information on services described by the corresponding SLT, and a service element may exist for each service.
- the Service element contains the @serviceId property, the @sltSvcSeqNum property, the @protected property, the @majorChannelNo property, the @minorChannelNo property, the @serviceCategory property, the @shortServiceName property, the @hidden property, the @broadbandAccessRequired property, the @svcCapabilities property, the BroadcastSvcSignaling element, and / or the svcInetUrl element. It may include.
- the @serviceId attribute may be an identifier of a corresponding service, and the @sltSvcSeqNum attribute may indicate a sequence number of SLT information for the corresponding service.
- the @protected attribute may indicate whether at least one service component necessary for meaningful playback of the corresponding service is protected.
- the @majorChannelNo and @minorChannelNo attributes may indicate the major channel number and the minor channel number of the corresponding service, respectively.
- the @serviceCategory attribute can indicate the category of the corresponding service.
- the service category may include a linear A / V service, a linear audio service, an app-based service, an ESG service, and an EAS service.
- the @shortServiceName attribute may provide a short name of the corresponding service.
- the @hidden attribute can indicate whether the service is for testing or proprietary use.
- the @broadbandAccessRequired attribute may indicate whether broadband access is required for meaningful playback of the corresponding service.
- the @svcCapabilities attribute can provide the capability information necessary for decoding and meaningful reproduction of the corresponding service.
- the BroadcastSvcSignaling element may provide information related to broadcast signaling of a corresponding service. This element may provide information such as a location, a protocol, and an address with respect to signaling through a broadcasting network of a corresponding service. Details will be described later.
- the svcInetUrl element may provide URL information for accessing signaling information for a corresponding service through broadband.
- the sltInetUrl element may further include an @urlType attribute, which may indicate the type of data that can be obtained through the URL.
- the aforementioned BroadcastSvcSignaling element may include an @slsProtocol attribute, an @slsMajorProtocolVersion attribute, an @slsMinorProtocolVersion attribute, an @slsPlpId attribute, an @slsDestinationIpAddress attribute, an @slsDestinationUdpPort attribute, and / or an @slsSourceIpAddress attribute.
- the @slsProtocol attribute can indicate the protocol used to deliver the SLS of the service (ROUTE, MMT, etc.).
- the @slsMajorProtocolVersion attribute and @slsMinorProtocolVersion attribute may indicate the major version number and the minor version number of the protocol used to deliver the SLS of the corresponding service, respectively.
- the @slsPlpId attribute may provide a PLP identifier for identifying a PLP that delivers the SLS of the corresponding service. According to an embodiment, this field may be omitted, and the PLP information to which the SLS is delivered may be identified by combining information in the LMT to be described later and bootstrap information of the SLT.
- the @slsDestinationIpAddress attribute, @slsDestinationUdpPort attribute, and @slsSourceIpAddress attribute may indicate the destination IP address, the destination UDP port, and the source IP address of the transport packet carrying the SLS of the corresponding service, respectively. They can identify the transport session (ROUTE session or MMTP session) to which the SLS is delivered. These may be included in the bootstrap information.
- FIG. 4 illustrates a USBD and an S-TSID delivered to ROUTE according to an embodiment of the present invention.
- One embodiment t4010 of the illustrated USBD may have a bundleDescription root element.
- the bundleDescription root element may have a userServiceDescription element.
- the userServiceDescription element may be an instance of one service.
- the userServiceDescription element may include an @globalServiceID attribute, an @serviceId attribute, an @serviceStatus attribute, an @fullMPDUri attribute, an @sTSIDUri attribute, a name element, a serviceLanguage element, a capabilityCode element, and / or a deliveryMethod element.
- Each field may be omitted or may exist in plurality, depending on the value of the illustrated Use column.
- the @globalServiceID attribute is a globally unique identifier of the service and can be used to link with ESG data (Service @ globalServiceID).
- the @serviceId attribute is a reference corresponding to the corresponding service entry of the SLT and may be the same as service ID information of the SLT.
- the @serviceStatus attribute may indicate the status of the corresponding service. This field may indicate whether the corresponding service is active or inactive.
- the @fullMPDUri attribute can refer to the MPD fragment of the service. As described above, the MPD may provide a reproduction description for a service component delivered through a broadcast network or a broadband.
- the @sTSIDUri attribute may refer to the S-TSID fragment of the service.
- the S-TSID may provide parameters related to access to the transport session carrying the service as described above.
- the name element may provide the name of the service.
- This element may further include an @lang attribute, which may indicate the language of the name provided by the name element.
- the serviceLanguage element may indicate the available languages of the service. That is, this element may list the languages in which the service can be provided.
- the capabilityCode element may indicate capability or capability group information of the receiver side necessary for significantly playing a corresponding service. This information may be compatible with the capability information format provided by the service announcement.
- the deliveryMethod element may provide delivery related information with respect to contents accessed through a broadcasting network or a broadband of a corresponding service.
- the deliveryMethod element may include a broadcastAppService element and / or a unicastAppService element. Each of these elements may have a basePattern element as its child element.
- the broadcastAppService element may include transmission related information on the DASH presentation delivered through the broadcast network.
- These DASH representations may include media components across all periods of the service media presentation.
- the basePattern element of this element may represent a character pattern used by the receiver to match the segment URL. This can be used by the DASH client to request segments of the representation. Matching may imply that the media segment is delivered over the broadcast network.
- the unicastAppService element may include transmission related information on the DASH representation delivered through broadband. These DASH representations may include media components across all periods of the service media presentation.
- the basePattern element of this element may represent a character pattern used by the receiver to match the segment URL. This can be used by the DASH client to request segments of the representation. Matching may imply that the media segment is delivered over broadband.
- An embodiment t4020 of the illustrated S-TSID may have an S-TSID root element.
- the S-TSID root element may include an @serviceId attribute and / or an RS element.
- Each field may be omitted or may exist in plurality, depending on the value of the illustrated Use column.
- the @serviceId attribute is an identifier of a corresponding service and may refer to a corresponding service of USBD / USD.
- the RS element may describe information on ROUTE sessions through which service components of a corresponding service are delivered. Depending on the number of such ROUTE sessions, there may be a plurality of these elements.
- the RS element may further include an @bsid attribute, an @sIpAddr attribute, an @dIpAddr attribute, an @dport attribute, an @PLPID attribute, and / or an LS element.
- the @bsid attribute may be an identifier of a broadcast stream through which service components of a corresponding service are delivered. If this field is omitted, the default broadcast stream may be a broadcast stream that includes a PLP that carries the SLS of the service. The value of this field may be the same value as the @bsid attribute of SLT.
- the @sIpAddr attribute, the @dIpAddr attribute, and the @dport attribute may indicate a source IP address, a destination IP address, and a destination UDP port of the corresponding ROUTE session, respectively. If these fields are omitted, the default values may be the source IP address, destination IP address, and destination UDP port values of the current, ROUTE session carrying that SLS, that is, carrying that S-TSID. For other ROUTE sessions that carry service components of the service but not the current ROUTE session, these fields may not be omitted.
- the @PLPID attribute may indicate PLP ID information of a corresponding ROUTE session. If this field is omitted, the default value may be the PLP ID value of the current PLP to which the corresponding S-TSID is being delivered. According to an embodiment, this field is omitted, and the PLP ID information of the corresponding ROUTE session may be confirmed by combining information in the LMT to be described later and IP address / UDP port information of the RS element.
- the LS element may describe information on LCT channels through which service components of a corresponding service are delivered. Depending on the number of such LCT channels, there may be a plurality of these elements.
- the LS element may include an @tsi attribute, an @PLPID attribute, an @bw attribute, an @startTime attribute, an @endTime attribute, an SrcFlow element, and / or a RepairFlow element.
- the @tsi attribute may represent tsi information of a corresponding LCT channel. Through this, LCT channels through which a service component of a corresponding service is delivered may be identified.
- the @PLPID attribute may represent PLP ID information of a corresponding LCT channel. In some embodiments, this field may be omitted.
- the @bw attribute may indicate the maximum bandwidth of the corresponding LCT channel.
- the @startTime attribute may indicate the start time of the LCT session, and the @endTime attribute may indicate the end time of the LCT channel.
- the SrcFlow element may describe the source flow of ROUTE.
- the source protocol of ROUTE is used to transmit the delivery object, and can establish at least one source flow in one ROUTE session. These source flows can deliver related objects as an object flow.
- the RepairFlow element may describe the repair flow of ROUTE. Delivery objects delivered according to the source protocol may be protected according to Forward Error Correction (FEC).
- FEC Forward Error Correction
- the repair protocol may define a FEC framework that enables such FEC protection.
- FIG. 5 is a diagram illustrating a USBD delivered to MMT according to an embodiment of the present invention.
- One embodiment of the illustrated USBD may have a bundleDescription root element.
- the bundleDescription root element may have a userServiceDescription element.
- the userServiceDescription element may be an instance of one service.
- the userServiceDescription element may include an @globalServiceID attribute, an @serviceId attribute, a Name element, a serviceLanguage element, a content advisoryRating element, a Channel element, an mpuComponent element, a routeComponent element, a broadbandComponent element, and / or a ComponentInfo element.
- Each field may be omitted or may exist in plurality, depending on the value of the illustrated Use column.
- the @globalServiceID attribute, the @serviceId attribute, the Name element and / or the serviceLanguage element may be the same as the corresponding fields of the USBD delivered to the above-described ROUTE.
- the contentAdvisoryRating element may indicate the content advisory rating of the corresponding service. This information may be compatible with the content advisory rating information format provided by the service announcement.
- the channel element may include information related to the corresponding service. The detail of this element is mentioned later.
- the mpuComponent element may provide a description for service components delivered as an MPU of a corresponding service.
- This element may further include an @mmtPackageId attribute and / or an @nextMmtPackageId attribute.
- the @mmtPackageId attribute may refer to an MMT package of service components delivered as an MPU of a corresponding service.
- the @nextMmtPackageId attribute may refer to an MMT package to be used next to the MMT package referenced by the @mmtPackageId attribute in time.
- the MP table can be referenced through the information of this element.
- the routeComponent element may include a description of service components of the corresponding service delivered to ROUTE. Even if the linear service components are delivered in the MMT protocol, the NRT data may be delivered according to the ROUTE protocol as described above. This element may describe information about such NRT data. The detail of this element is mentioned later.
- the broadbandComponent element may include a description of service components of the corresponding service delivered over broadband.
- some service components or other files of a service may be delivered over broadband. This element may describe information about these data.
- This element may further include the @fullMPDUri attribute. This attribute may refer to an MPD that describes service components delivered over broadband.
- the element when the broadcast signal is weakened due to driving in a tunnel or the like, the element may be needed to support handoff between the broadcast network and the broadband band. When the broadcast signal is weakened, while acquiring the service component through broadband, and when the broadcast signal is stronger, the service continuity may be guaranteed by acquiring the service component through the broadcast network.
- the ComponentInfo element may include information on service components of a corresponding service. Depending on the number of service components of the service, there may be a plurality of these elements. This element may describe information such as the type, role, name, identifier, and protection of each service component. Detailed information on this element will be described later.
- the aforementioned channel element may further include an @serviceGenre attribute, an @serviceIcon attribute, and / or a ServiceDescription element.
- the @serviceGenre attribute may indicate the genre of the corresponding service
- the @serviceIcon attribute may include URL information of an icon representing the corresponding service.
- the ServiceDescription element provides a service description of the service, which may further include an @serviceDescrText attribute and / or an @serviceDescrLang attribute. Each of these attributes may indicate the text of the service description and the language used for that text.
- the aforementioned routeComponent element may further include an @sTSIDUri attribute, an @sTSIDDestinationIpAddress attribute, an @sTSIDDestinationUdpPort attribute, an @sTSIDSourceIpAddress attribute, an @sTSIDMajorProtocolVersion attribute, and / or an @sTSIDMinorProtocolVersion attribute.
- the @sTSIDUri attribute may refer to an S-TSID fragment. This field may be the same as the corresponding field of USBD delivered to ROUTE described above. This S-TSID may provide access related information for service components delivered in ROUTE. This S-TSID may exist for NRT data delivered according to the ROUTE protocol in the situation where linear service components are delivered according to the MMT protocol.
- the @sTSIDDestinationIpAddress attribute, the @sTSIDDestinationUdpPort attribute, and the @sTSIDSourceIpAddress attribute may indicate a destination IP address, a destination UDP port, and a source IP address of a transport packet carrying the aforementioned S-TSID, respectively. That is, these fields may identify a transport session (MMTP session or ROUTE session) carrying the aforementioned S-TSID.
- the @sTSIDMajorProtocolVersion attribute and the @sTSIDMinorProtocolVersion attribute may indicate a major version number and a minor version number of the transport protocol used to deliver the aforementioned S-TSID.
- ComponentInfo element may further include an @componentType attribute, an @componentRole attribute, an @componentProtectedFlag attribute, an @componentId attribute, and / or an @componentName attribute.
- the @componentType attribute may indicate the type of the corresponding component. For example, this property may indicate whether the corresponding component is an audio, video, or closed caption component.
- the @componentRole attribute can indicate the role (role) of the corresponding component. For example, this property can indicate whether the main audio, music, commentary, etc., if the corresponding component is an audio component. If the corresponding component is a video component, it may indicate whether it is primary video. If the corresponding component is a closed caption component, it may indicate whether it is a normal caption or an easy reader type.
- the @componentProtectedFlag attribute may indicate whether a corresponding service component is protected, for example, encrypted.
- the @componentId attribute may represent an identifier of a corresponding service component.
- the value of this attribute may be a value such as asset_id (asset ID) of the MP table corresponding to this service component.
- the @componentName attribute may represent the name of the corresponding service component.
- FIG. 6 illustrates a link layer operation according to an embodiment of the present invention.
- the link layer may be a layer between the physical layer and the network layer.
- the transmitter may transmit data from the network layer to the physical layer
- the receiver may transmit data from the physical layer to the network layer (t6010).
- the purpose of the link layer may be to compress all input packet types into one format for processing by the physical layer, to ensure flexibility and future scalability for input packet types not yet defined. have.
- the link layer may provide an option of compressing unnecessary information in the header of the input packet, so that the input data may be efficiently transmitted. Operations such as overhead reduction and encapsulation of the link layer may be referred to as a link layer protocol, and a packet generated using the corresponding protocol may be referred to as a link layer packet.
- the link layer may perform functions such as packet encapsulation, overhead reduction, and / or signaling transmission.
- the link layer ALP may perform an overhead reduction process on input packets and then encapsulate them into link layer packets.
- the link layer may encapsulate the link layer packet without performing an overhead reduction process.
- the use of the link layer protocol can greatly reduce the overhead for data transmission on the physical layer, and the link layer protocol according to the present invention can provide IP overhead reduction and / or MPEG-2 TS overhead reduction. have.
- the link layer may sequentially perform IP header compression, adaptation, and / or encapsulation. In some embodiments, some processes may be omitted.
- the RoHC module performs IP packet header compression to reduce unnecessary overhead, and context information may be extracted and transmitted out of band through an adaptation process.
- the IP header compression and adaptation process may be collectively called IP header compression.
- IP packets may be encapsulated into link layer packets through an encapsulation process.
- the link layer may sequentially perform an overhead reduction and / or encapsulation process for the TS packet. In some embodiments, some processes may be omitted.
- the link layer may provide sync byte removal, null packet deletion and / or common header removal (compression).
- Sync byte elimination can provide overhead reduction of 1 byte per TS packet. Null packet deletion can be performed in a manner that can be reinserted at the receiving end. In addition, common information between successive headers can be deleted (compressed) in a manner that can be recovered at the receiving side. Some of each overhead reduction process may be omitted. Thereafter, TS packets may be encapsulated into link layer packets through an encapsulation process.
- the link layer packet structure for encapsulation of TS packets may be different from other types of packets.
- IP header compression will be described.
- the IP packet has a fixed header format, but some information required in a communication environment may be unnecessary in a broadcast environment.
- the link layer protocol may provide a mechanism to reduce broadcast overhead by compressing the header of the IP packet.
- IP header compression may include a header compressor / decompressor and / or adaptation module.
- the IP header compressor (RoHC compressor) may reduce the size of each IP packet header based on the RoHC scheme.
- the adaptation module may then extract the context information and generate signaling information from each packet stream.
- the receiver may parse signaling information related to the packet stream and attach context information to the packet stream.
- the RoHC decompressor can reconstruct the original IP packet by recovering the packet header.
- IP header compression may mean only IP header compression by a header compressor, or may mean a concept in which the IP header compression and the adaptation process by the adaptation module are combined. The same is true for decompressing.
- the adaptation function may generate link layer signaling using context information and / or configuration parameters.
- the adaptation function may periodically send link layer signaling over each physical frame using previous configuration parameters and / or context information.
- the context information is extracted from the compressed IP packets, and various methods may be used according to the adaptation mode.
- Mode # 1 is a mode in which no operation is performed on the compressed packet stream, and may be a mode in which the adaptation module operates as a buffer.
- Mode # 2 may be a mode for extracting context information (static chain) by detecting IR packets in the compressed packet stream. After extraction, the IR packet is converted into an IR-DYN packet, and the IR-DYN packet can be transmitted in the same order in the packet stream by replacing the original IR packet.
- context information static chain
- Mode # 3 t6020 may be a mode for detecting IR and IR-DYN packets and extracting context information from the compressed packet stream.
- Static chains and dynamic chains can be extracted from IR packets and dynamic chains can be extracted from IR-DYN packets.
- the IR and IR-DYN packets can be converted into regular compressed packets.
- the switched packets can be sent in the same order within the packet stream, replacing the original IR and IR-DYN packets.
- the remaining packets after the context information is extracted may be encapsulated and transmitted according to the link layer packet structure for the compressed IP packet.
- the context information may be transmitted by being encapsulated according to a link layer packet structure for signaling information as link layer signaling.
- the extracted context information may be included in the RoHC-U Description Table (RTT) and transmitted separately from the RoHC packet flow.
- the context information may be transmitted through a specific physical data path along with other signaling information.
- a specific physical data path may mean one of general PLPs, a PLP to which LLS (Low Level Signaling) is delivered, a dedicated PLP, or an L1 signaling path. path).
- the RDT may be signaling information including context information (static chain and / or dynamic chain) and / or information related to header compression.
- the RDT may be transmitted whenever the context information changes.
- the RDT may be transmitted in every physical frame. In order to transmit the RDT in every physical frame, a previous RDT may be re-use.
- the receiver may first select PLP to acquire signaling information such as SLT, RDT, LMT, and the like. When the signaling information is obtained, the receiver may combine these to obtain a mapping between the service-IP information-context information-PLP. That is, the receiver can know which service is transmitted to which IP streams, which IP streams are delivered to which PLP, and can also obtain corresponding context information of the PLPs. The receiver can select and decode a PLP carrying a particular packet stream. The adaptation module can parse the context information and merge it with the compressed packets. This allows the packet stream to be recovered, which can be delivered to the RoHC decompressor. Decompression can then begin.
- signaling information such as SLT, RDT, LMT, and the like.
- the receiver may combine these to obtain a mapping between the service-IP information-context information-PLP. That is, the receiver can know which service is transmitted to which IP streams, which IP streams are delivered to which PLP, and can also obtain corresponding context information of the PLPs.
- the receiver detects the IR packet and starts decompression from the first received IR packet according to the adaptation mode (mode 1), or detects the IR-DYN packet to perform decompression from the first received IR-DYN packet.
- the link layer protocol may encapsulate all types of input packets, such as IP packets and TS packets, into link layer packets. This allows the physical layer to process only one packet format independently of the protocol type of the network layer (here, consider MPEG-2 TS packet as a kind of network layer packet). Each network layer packet or input packet is transformed into a payload of a generic link layer packet.
- Segmentation may be utilized in the packet encapsulation process. If the network layer packet is too large to be processed by the physical layer, the network layer packet may be divided into two or more segments.
- the link layer packet header may include fields for performing division at the transmitting side and recombination at the receiving side. Each segment may be encapsulated into a link layer packet in the same order as the original position.
- Concatenation may also be utilized in the packet encapsulation process. If the network layer packet is small enough that the payload of the link layer packet includes several network layer packets, concatenation may be performed.
- the link layer packet header may include fields for executing concatenation. In the case of concatenation, each input packet may be encapsulated into the payload of the link layer packet in the same order as the original input order.
- the link layer packet may include a header and a payload, and the header may include a base header, an additional header, and / or an optional header.
- the additional header may be added depending on the chaining or splitting, and the additional header may include necessary fields according to the situation.
- an optional header may be further added to transmit additional information.
- Each header structure may be predefined. As described above, when the input packet is a TS packet, a link layer header structure different from other packets may be used.
- Link layer signaling may operate at a lower level than the IP layer.
- the receiving side can acquire the link layer signaling faster than the IP level signaling such as LLS, SLT, SLS, and the like. Therefore, link layer signaling may be obtained before session establishment.
- Link layer signaling may include internal link layer signaling and external link layer signaling.
- Internal link layer signaling may be signaling information generated in the link layer.
- the above-described RDT or LMT to be described later may correspond to this.
- the external link layer signaling may be signaling information received from an external module, an external protocol, or an upper layer.
- the link layer may encapsulate link layer signaling into a link layer packet and deliver it.
- a link layer packet structure (header structure) for link layer signaling may be defined, and link layer signaling information may be encapsulated according to this structure.
- FIG. 7 illustrates a link mapping table (LMT) according to an embodiment of the present invention.
- the LMT may provide a list of higher layer sessions carried by the PLP.
- the LMT may also provide additional information for processing link layer packets carrying higher layer sessions.
- the higher layer session may be called multicast.
- Information on which IP streams and which transport sessions are being transmitted through a specific PLP may be obtained through the LMT. Conversely, information on which PLP a specific transport session is delivered to may be obtained.
- the LMT may be delivered to any PLP identified as carrying an LLS.
- the PLP through which the LLS is delivered may be identified by the LLS flag of the L1 detail signaling information of the physical layer.
- the LLS flag may be a flag field indicating whether LLS is delivered to the corresponding PLP for each PLP.
- the L1 detail signaling information may correspond to PLS2 data to be described later.
- the LMT may be delivered to the same PLP together with the LLS.
- Each LMT may describe the mapping between PLPs and IP address / port as described above.
- the LLS may include an SLT, where these IP addresses / ports described by the LMT are all IP addresses associated with any service described by the SLT forwarded to the same PLP as that LMT. It can be / ports.
- the PLP identifier information in the above-described SLT, SLS, etc. may be utilized, so that information on which PLP the specific transmission session indicated by the SLT, SLS is transmitted may be confirmed.
- the PLP identifier information in the above-described SLT, SLS, etc. may be omitted, and the PLP information for the specific transport session indicated by the SLT, SLS may be confirmed by referring to the information in the LMT.
- the receiver may identify the PLP to know by combining LMT and other IP level signaling information.
- PLP information in SLT, SLS, and the like is not omitted, and may remain in the SLT, SLS, and the like.
- the LMT according to the illustrated embodiment may include a signaling_type field, a PLP_ID field, a num_session field, and / or information about respective sessions.
- a PLP loop may be added to the LMT according to an embodiment, so that information on a plurality of PLPs may be described.
- the LMT may describe PLPs for all IP addresses / ports related to all services described by the SLTs delivered together, in a PLP loop.
- the signaling_type field may indicate the type of signaling information carried by the corresponding table.
- the value of the signaling_type field for the LMT may be set to 0x01.
- the signaling_type field may be omitted.
- the PLP_ID field may identify a target PLP to be described. When a PLP loop is used, each PLP_ID field may identify each target PLP. From the PLP_ID field may be included in the PLP loop.
- the PLP_ID field mentioned below is an identifier for one PLP in a PLP loop, and the fields described below may be fields for the corresponding PLP.
- the num_session field may indicate the number of upper layer sessions delivered to the PLP identified by the corresponding PLP_ID field. According to the number indicated by the num_session field, information about each session may be included. This information may include an src_IP_add field, a dst_IP_add field, a src_UDP_port field, a dst_UDP_port field, a SID_flag field, a compressed_flag field, a SID field, and / or a context_id field.
- the src_IP_add field, dst_IP_add field, src_UDP_port field, and dst_UDP_port field are the source IP address, destination IP address, source UDP port, destination UDP port for the transport session among the higher 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 stream / packet 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.
- the broadcast service may include components in one or more RF channels.
- a set of components such as a service in one RF channel, may be referred to as a portion of a service. If the set of services does not include all the components of the service, this set of services may be referred to as a potion. If a set of services includes all the components of a service, and if one or more such sets are delivered, then the set of components of such a service may be referred to as a duplicate.
- Each service represented by the potions may include essential potions that are sufficient for meaningful provision / presentation of the service without the use of other potions. Each service may include only one essential potion. Portions that are not essential potions may be referred to as non-essential potions. However, a more attractive service may be provided by adding a non-essential potion to the essential potion.
- Portions or copies of services may be delivered to one RF channel without channel bonding.
- channel bonding is applied in the ALP packet stream
- the portion or duplication of the service may be delivered to the bonded RF channel.
- a signaling method according to a transmission method such as whether channel bonding is applied or not will be described.
- Each broadcast service represented by a service portion or copy is included in the SLT of the RF channel in which the portion or copy appears.
- Each of the multiple listings of a service represented by a portion or replica may have a service ID of the same value, a major / minor channel number of the same value. Therefore, when the receiver performs a channel scan, portions or copies of a service transmitted over multiple channels may be consodilate into a single service.
- the SLT for the essential portion or replica may list the Broadcast Stream Identifier (BSID) of the broadcast stream in which another potion or other replica may be found.
- BSID Broadcast Stream Identifier
- the S-TSID may be delivered in the PLP of each RF channel that delivers a service portion or replication.
- the S-TSID for the portion or replication may describe the ROUTE session and LCT channel for each component of the service portion or replication.
- the SLT associated with both a non-bonded PLP and a bonded PLP that delivers any portion of the service lists the service.
- Each of the multiple listings of a service represented by a potion may have a service ID of the same value and a major / minor channel number of the same value. Only the SLT entry for the essential portion of the service can list the BSID of the broadcast stream where other potions can be found.
- the S-TSID may be delivered in the non-bonded PLP of each RF channel that delivers the service portion.
- the S-TSID may be delivered in a bonded PLP of a bonded RF channel that delivers another service portion.
- each S-TSID instance describes a ROUTE session and an LCT channel for each component of the service portion delivered by the corresponding non-bonded PLP in the RF channel to which the PLP containing the S-TSID belongs. can do.
- each S-TSID instance may describe a ROUTE session and an LCT channel for each component of the service portion delivered by the bonded PLP in the RF channel to which the PLP containing the S-TSID belongs. have.
- the essential portion of the service is delivered to the bonded PLP on the bonded RF channel.
- One S-TSID for a service is delivered within a bonded PLP of bonded RF channels that deliver the essential portion of the service.
- the S-TSID instance may describe a ROUTE session and an LCT channel for all components of the service.
- a SLT associated with both a non-bonded PLP and a bonded PLP that delivers a copy of the service lists the service.
- Each of the multiple listings of a service represented by a replica may have a service ID of the same value and a major / minor channel number of the same value.
- the SLT entry for the duplicate of the service may list the BSID of the broadcast stream where other potions may be found.
- the S-TSID may be delivered within the non-bonded PLP of each RF channel delivering service replication.
- Each S-TSID may be delivered in a bonded PLP of a bonded RF channel that delivers another service replica.
- each S-TSID instance describes a ROUTE session and an LCT channel for each component of the service portion delivered by the corresponding non-bonded PLP in the RF channel to which the PLP containing the S-TSID belongs. can do.
- each S-TSID instance may describe a ROUTE session and an LCT channel for each component of service replication delivered by that bonded PLP in the RF channel to which the PLP containing the S-TSID belongs. have.
- Multiple tuners may be required to recover the ALP packet stream from the bonded PLPs. For example, as many tuners as the number of RF channels for a bonded PLP may be needed.
- the receiver In order for a single-tuner receiver to obtain a service with channel bonding applied, the receiver must be able to obtain an SLT describing the service.
- S-TSID When a single-tuner receiver tuned to a specific RF channel obtains the S-TSID of the service, all components listed in the S-TSID can be obtained with the tuner tuned to the same RF channel. That is, due to the above-described signaling structure, even a single tuner receiver can identify all services and receive and acquire components corresponding to the services.
- FIG 9 illustrates SLT information according to an embodiment of the present invention.
- FIG. 9 is another embodiment of the SLT shown in FIG. 3 and further includes signaling information for multi-channel transmission described above. Thus, the descriptions of the elements and attributes included in the SLT described in FIG. 3 do not overlap. Description of the signaling information added to FIG. 9 is as follows. All the added signaling information correspond to the sub information of the service element.
- the essential attribute 9010 included in the service element indicates whether the portion of the service delivered through this broadcast stream is essential.
- This Boolean value indicates whether the essential portion of the service is delivered in this broadcast stream if the service includes one or more potions that are delivered to one or more RF channels.
- This boolean attribute may be present if there is at least one OtherBsid element with a type attribute value of 2 for this service. The default value can be set to "false".
- the other BSID element 9020 corresponds to identifier information identifying a duplicate of this service or another broadcast stream that delivers a portion of this service.
- the format of this OtherBSID instance may be the same format as that of the @bsid instance of the SLT. This element may not be present unless set to "true" in the essential attribute.
- the type attribute 9030 indicates whether the broadcast stream identified by the OtherBsid element includes a duplicate of this service or a portion of this service. If the value of the type attribute is 1, then replication can be indicated. If the value of the type attribute is set to 2, this may indicate that this service element represents a portion of the service. This service portion has components in the broadcast stream identified by the OtherBsid identifier, and the service identifier of this service portion is given the value of the service ID attribute of the parent service element. If more than one OtherBsid element exists below the parent service element, the values of the type attributes of the OtherBsid element may be the same.
- the type attribute When set to a value corresponding to "duplicate", the type attribute may indicate that a broadcast stream identified by another BSID element is a duplicate of this service. When the type attribute is set to a value corresponding to "portion”, the type attribute may indicate that a broadcast stream identified by another BSID element is another portion including additional components of this service. When the type attribute is set to a value corresponding to "portion”, the type attribute may indicate that this service element is a portion of a service having a component in a multicast stream.
- the S-TSID is an SLS metadata fragment including transport session description information for an LCT channel and a ROUTE session in a media content component in which a broadcast service is delivered.
- the S-TSID may include file metadata for delivery objects or object flows carried in the LCT channel of the service.
- the S-TSID may include additional information about the content component and payload format carried within the LCT channel.
- Components of the service may be via one channel or via channel bonding to be delivered over one or more broadcast streams.
- the S-TSID may describe only the ROUTE session and the LCT channel of the broadcast stream in which the S-TSID is delivered.
- the S-TSID associated with the service may describe only the ROUTE session and the LCT channel of the broadcast stream other than the broadcast stream through which the S-TSID is delivered. .
- the @bsid attribute may be included in the RS element of the S-TSID.
- the broadcast stream identifier under the RS element may identify the broadcast stream on which the content component of the broadcast service is carried. If the @bsid attribute is not included in the RS element, the default broadcast stream may include a PLP that carries an SLS fragment for this service. The value of this attribute may be equal to the value of @bsid of the SLT.
- FIG. 10 illustrates an embodiment in which a portion of a service is delivered to multiple RF channels without channel bonding, and illustrates a signal frame of channel A through which an essential portion is delivered.
- the SLT service element associated with the essential portion of the service has an OtherBsid element whose value of the @type attribute is 2.
- the S-TSID included in PLP # 1 of channel A that delivers the S-TSID describes an LCT channel and a ROTUE channel for components delivered in a broadcast stream.
- FIG. 11 illustrates an embodiment in which a portion of a service is delivered to multiple RF channels without channel bonding, and illustrates a signal frame of channel B through which a non-essential portion is delivered.
- the SLT service element associated with the essential portion of the service does not include the OtherBsid element.
- the service is preferably provided mainly for the essential portion, and including signaling for the essential portion in the non-essential portion can be a waste of signaling resources.
- the S-TSID included in PLP # 3 of the signal frame of channel B that delivers the S-TSID describes the LCT channel and the ROTUE channel for the components delivered in the broadcast stream.
- FIG. 12 is an embodiment in which duplication of a service is delivered to multiple RF channels without channel bonding, and illustrates a signal frame of channel A in which duplication of service with a channel number of 9 (1) is transmitted.
- the SLT service element associated with the duplication of the service has an OtherBsid element whose value of the @type attribute is 1.
- BSID A
- essential information about the service is omitted, and otherBSID indicates channel B carrying another service replica.
- the S-TSID included in PLP # 1 of the signal frame of channel A that delivers the S-TSID describes an LCT channel and a ROTUE channel for components delivered in a broadcast stream.
- FIG. 13 is an embodiment in which duplication of a service is delivered to multiple RF channels without channel bonding, and illustrates a signal frame of channel B in which duplication of service with a channel number of 9 (3) is transmitted.
- the SLT service element associated with the essential portion of the service has an OtherBsid element whose value of the @type attribute is 1.
- the S-TSID included in PLP # 3 of the signal frame of channel B that delivers the S-TSID describes the LCT channel and the ROTUE channel for the components delivered in the broadcast stream.
- FIG. 14 is an embodiment in which a portion of a service is delivered to multiple RF channels by channel bonding, and illustrates a signal frame of channel A in which an essential portion is delivered to a non-bonded PLP.
- the signal frame of channel A includes an SLT for a non-bonded portion and an SLT for a bonded portion.
- the SLT service element associated with the essential portion of the service has an OtherBsid element whose value of the @type attribute is 2.
- the essential information about the service is set to "true”, and two otherBSID elements respectively indicate channel B and channel A & B carrying different service portions.
- the S-TSID included in PLP # 1 and PLP # 2 of the signal frame of channel A that delivers the S-TSID describes an LCT channel and a ROTUE channel for components delivered in a broadcast stream.
- the bonded PLP # 2 of the signal frame of channel A includes the SLT.
- the BSIDs of the SLT included in the bonded PLP are A and B, indicating two channels.
- the essential information is set to "fasle. As described above, since only the SLT including the essential portion includes OtherBSID information, the SLT of PLP # 2 does not include the OtherBSID information.
- FIG. 15 is an embodiment in which a portion of a service is delivered to multiple RF channels by channel bonding, and illustrates a signal frame of channel B in which a non-essential portion is delivered to a bonded PLP.
- the signal frame of channel B delivers PLPs corresponding to two services (service 0x1001 and service 0x1004).
- the service 0x1004 may correspond to an unpartitioned intact service.
- the bonded PLP # 2 of the signal frame of the channel B is channel-bonded with the bonded PLP # 2 of the channel A and transmitted.
- the SLT included in PLP # 4 of the signal frame of channel B includes service elements for a plurality of services. Each service element indicates that service 0x1001 is a non-essential potion and that service 0x1004 is an unpartitioned intact service.
- the S-TSID included in PLP # 3 of the signal frame of channel B that delivers the S-TSID describes the LCT channel and the ROTUE channel for the components delivered in the broadcast stream.
- 16 and 17 illustrate a method of constructing a broadcast signal according to an embodiment of the present invention.
- FIG. 16 illustrates an embodiment in which a portion of a service is delivered to multiple RF channels by channel bonding, and illustrates a signal frame of channel A in which an essential portion is delivered to a bonded PLP.
- the signal frame of channel A includes an SLT for a non-bonded portion and an SLT for a bonded portion.
- the SLT service element associated with the essential portion of the service includes OtherBsid elements having a value of the @type attribute of 2.
- the essential information about the service is set to "true”, and the two otherBSID elements respectively indicate channel B and channel B carrying different service portions.
- the S-TSID included in PLP # 1 and PLP # 2 of the signal frame of channel A that delivers the S-TSID describes an LCT channel and a ROTUE channel for components delivered in a broadcast stream.
- PLP # 0 of the signal frame of channel A includes SLT.
- the SLT of PLP # 0 does not describe the service of the bonded PLP. Only the SLT associated with the essential portion of a service will list that service.
- the BSID of the SLT associated with the bonded PLP may indicate both channels together as "A & B".
- FIG. 17 illustrates an embodiment in which a portion of a service is delivered to multiple RF channels by channel bonding, and illustrates a signal frame of channel B in which an essential portion is delivered to a bonded PLP.
- the signal frame of channel B delivers PLPs corresponding to two services (service 0x1001 and service 0x1004).
- the service 0x1004 may correspond to an unpartitioned intact service.
- the bonded PLP # 2 of the signal frame of the channel B is channel-bonded with the bonded PLP # 2 of the channel A and transmitted.
- the SLT included in PLP # 4 of the signal frame of channel B includes a service element for a non-channel bonded service.
- FIG. 18 illustrates an embodiment in which a copy of a service is delivered to multiple RF channels by channel bonding, and illustrates a signal frame of channel A in which a copy of a service is delivered to the PLP bonded.
- the signal frame of channel A includes an SLT for a non-bonded portion and an SLT for a bonded portion.
- the SLT service element associated with the duplication of the service has OtherBsid elements whose value of the @type attribute is 1.
- Two otherBSID elements indicate channel B and channel A & B, respectively, carrying different service replicas.
- the S-TSID included in PLP # 1 and PLP # 2 of the signal frame of channel A that delivers the S-TSID describes an LCT channel and a ROTUE channel for components delivered in a broadcast stream.
- the bonded PLP # 2 of the signal frame of channel A includes the SLT.
- the BSID of the SLT included in the bonded PLP may be A.
- the BSID of the SLT included in the bonded PLP may indicate two channels as A and B. Essential information may not exist.
- the SLT service element associated with the duplication of the service has OtherBsid elements whose value of the @type attribute is 1.
- two otherBSID elements indicate channel A and channel B, respectively, carrying different service replicas.
- FIG. 19 is an embodiment in which a service is replicated to a bonded PLP in which channel replication is delivered to multiple RF channels and service replication is delivered to a bonded PLP.
- the signal frame of channel B includes PLPs whose channel numbers carry replicas of different services.
- the bonded PLP # 2 of the signal frame of the channel B is channel-bonded with the bonded PLP # 2 of the channel A and transmitted.
- the SLT included in PLP # 4 of the signal frame of channel B includes service elements for the service.
- the SLT of PLP # 4 contains OtherBSID elements to which replicas of other services are sent.
- two otherBSID elements indicate channel A and channel AB, respectively, carrying different service replicas.
- FIG. 20 illustrates a configuration of a broadcast signal transmission / reception apparatus according to an embodiment of the present invention.
- the broadcast signal transmission / reception apparatus 20000 may include a communication unit 20010, a processor 20020, and a memory 20030.
- the communication unit 20010 may be connected to the processor 20020 to transmit / receive a broadcast signal.
- the communication unit 20010 of the broadcast signal transmitting apparatus may transmit a signal by upconverting data received from the processor 20020 into a transmission / reception band.
- the communication unit 20010 of the broadcast signal receiving apparatus may down-convert the received data and transmit the received data to the processor 20020.
- the communication unit 20010 may receive an audio / video signal by wire.
- the communication unit may comprise at least one of a communication unit for wireless communication or a communication unit for wired communication.
- the communication unit 20010 may perform the physical layer processing described with reference to FIG. 8. As an embodiment, the communication unit 20010 may perform the link layer processing described with reference to FIGS. 6 to 7.
- the processor 20020 may be connected to the communication unit 20010 to implement broadcast signal processing technology according to the ATSC 3.0 system.
- the processor 20020 may be configured to perform an operation according to various embodiments of the present disclosure according to the above-described drawings and descriptions.
- a module implementing the operation of the broadcast signal transmission / reception apparatus 20000 according to various embodiments of the present disclosure described above may be stored in the memory 20030 and executed by the processor 20020.
- the memory 20030 is connected to the processor 20020 and stores various information for driving the processor 20020.
- the memory 20030 may be included in the processor 20020 or may be installed outside the processor 20020 and connected to the processor 20020 by known means.
- the detailed configuration of the broadcast signal transmitting / receiving device 20000 may be implemented such that the above descriptions of the various embodiments of the present invention are independently applied or two or more embodiments are simultaneously applied.
- the broadcast signal transmitting apparatus may be referred to as a broadcast signal transmitter
- the broadcast signal receiving apparatus may be referred to as a broadcast signal receiver.
- FIG. 21 illustrates a broadcast signal transmission method according to an embodiment of the present invention.
- the broadcast signal transmitter may encode a component of a broadcast service based on a delivery protocol (S21010).
- 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 broadcast signal transmitter may generate SLS information for the broadcast service component (S21020).
- the SLS information includes information for discovering and obtaining at least one component of a broadcast service.
- the SLS information may include service-based transport session instance description (S-TSID) information including description information of a session carrying at least one component of a broadcast service.
- S-TSID service-based transport session instance description
- the broadcast signal transmitter may generate SLT information about a broadcast service (S21030).
- the SLT information includes bootstrap information for obtaining SLS information.
- the broadcast signal transmitter may perform physical layer processing on components of the broadcast service, SLS information, and SLT (S21040).
- the broadcast signal transmitter may generate a signal frame including the PLP by physical layer processing the upper layer data.
- the set of components corresponds to a service portion that includes some components of the service or a service duplicate that includes all the components of the service, and the service portion uses another portion. It is an essential potion or a non-essential potion that can be provided without a service.
- the physical layer processing step may include selectively performing channel bonding for distributing one PLP including the service portion or service duplication into a plurality of channels.
- Service portion or service replication may be delivered to a single channel without channel bonding or channel bonding to be delivered to the plurality of channels.
- the SLT of the service portion or channel from which service replication is delivered describes the service portion or service replication
- the PLP of each channel where the service portion or service replication is delivered is the service portion or It may include S-TSID information for service replication.
- the non-bonded PLP and the plurality of SLT information associated with the bonded PLP delivering any portion of the service may be selected.
- only the SLT information for the essential portion may list a BSID (Broadcast Stream ID) of a broadcast stream in which another portion is delivered.
- BSID Broadcast Stream ID
- the service portion is channel bonded and delivered, when the essential portion is delivered to the bonded PLP, one SLT information associated with the bonded PLP that delivers the essential portion lists the service, and the other portion of the SLT information is delivered.
- the BSID (Broadcast Stream ID) of the broadcast stream may be listed.
- BSID Broadcast Stream ID
- the S-TSID is a session for a component that is delivered in a broadcast stream other than the broadcast stream in which the S-TSID is delivered.
- Channel information may be described.
- FIG. 22 illustrates a broadcast signal receiving method according to an embodiment of the present invention.
- the embodiment of receiving various broadcast signals described with reference to FIGS. 1 to 20 may be applied to the reception method of FIG. 22.
- the broadcast signal receiver may receive a broadcast signal (S22010).
- the broadcast signal receiver may receive a broadcast signal by tuning to a specific channel, and may receive a plurality of broadcast streams by simultaneously tuning a plurality of channels.
- the broadcast signal receiver may process the received broadcast signal physical layer.
- the broadcast signal receiver may parse SLT information included in the broadcast signal (S22020).
- the SLT information includes bootstrap information for obtaining SLS information.
- the broadcast signal receiver may acquire SLS information based on the SLT information (S22030).
- the SLS information includes information for discovering and obtaining at least one component of a broadcast service.
- the broadcast signal receiver may acquire a service component based on the SLS information (S22040).
- the set of components corresponds to a service portion that includes some components of the service or a service duplicate that includes all the components of the service, and the service portion uses another portion. It is an essential potion or a non-essential potion that can be provided without a service.
- the physical layer processing step may include selectively performing channel bonding for distributing one PLP including the service portion or service duplication into a plurality of channels.
- Service portion or service replication may be delivered to a single channel without channel bonding or channel bonding to be delivered to the plurality of channels.
- the SLT of the service portion or channel from which service replication is delivered describes the service portion or service replication
- the PLP of each channel where the service portion or service replication is delivered is the service portion or It may include S-TSID information for service replication.
- the non-bonded PLP and the plurality of SLT information associated with the bonded PLP delivering any portion of the service may be selected.
- only the SLT information for the essential portion may list a BSID (Broadcast Stream ID) of a broadcast stream in which another portion is delivered.
- BSID Broadcast Stream ID
- the service portion is channel bonded and delivered, when the essential portion is delivered to the bonded PLP, one SLT information associated with the bonded PLP that delivers the essential portion lists the service, and the other portion of the SLT information is delivered.
- the BSID (Broadcast Stream ID) of the broadcast stream may be listed.
- BSID Broadcast Stream ID
- the S-TSID is a session for a component that is delivered in a broadcast stream other than the broadcast stream in which the S-TSID is delivered.
- Channel information may be described.
- the present invention proposes a signaling method for transmitting and receiving a service on a multi-channel.
- the present invention proposes a method of signaling a component such as an additional service or a duplicate of a service as one service, and thus can transmit various services through a plurality of channels.
- the receiver may obtain various portions / replications corresponding to the service by using the signaling information of the present invention.
- the receiver When channel bonding is applied to the broadcast signal, the receiver needs signaling information about the channel bonding portion. However, it is desirable to minimize unnecessary signaling information. Therefore, when channel bonding is applied, the present invention determines the signaling structure based on where the essential portion is transmitted. As a result, the present invention can provide a signaling structure for optimizing broadcast signal configuration according to multichannel transmission and channel bonding.
- 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 present invention is used in the field of transmitting / receiving a series of broadcast signals.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Computer Networks & Wireless Communication (AREA)
- Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
Abstract
Description
Claims (14)
- 방송 서비스의 적어도 하나의 컴포넌트를 딜리버리 프로토콜에 기초하여 프로세싱하는 단계;상기 컴포넌트에 대한 정보를 포함하는 SLS(Service Layer Signaling) 정보를 생성하는 단계로서, 상기 SLS 정보는 상기 방송 서비스의 적어도 하나의 컴포넌트를 운반하는 세션에 대한 설명 정보를 포함하는 S-TSID(Service-based Transport Session Instance Description) 정보를 포함하는, 상기 생성 단계;상기 SLS 정보의 획득을 위한 부트스트랩 정보를 포함하는 SLT(Service List Table) 정보를 생성하는 단계; 및상기 적어도 하나의 컴포넌트, 상기 SLS 정보 및 상기 SLT 정보를 피지컬 레이어 프로세싱함으로써 PLP(Physical Layer Pipe)를 포함하는 신호 프레임을 생성하는 단계를 포함하고;상기 방송 서비스의 컴포넌트가 다중 RF 채널로 전송되는 경우, 상기 컴포넌트들의 세트는 상기 서비스의 일부 컴포넌트들을 포함하는 서비스 포션 또는 상기 서비스의 모든 컴포넌트들을 포함하는 서비스 복제(duplicate)에 해당하고, 상기 서비스 포션은 다른 포션의 사용 없이 서비스 제공이 가능한 에센셜 포션 또는 넌-에센셜 포션에 해당하는, 방송 신호 송신 방법.
- 제 1 항에 있어서,상기 방송 서비스의 서비스 포션 또는 서비스 복제가 다중 채널로 전송되는 경우, 상기 피지컬 레이어 프로세싱 단계는 상기 서비스 포션 또는 서비스 복제를 포함하는 하나의 PLP를 복수의 채널로 분배하는 채널 본딩을 선택적으로 수행하는 단계를 포함하고,상기 서비스 포션 또는 상기 서비스 복제는 상기 채널 본딩 적용 없이 단일 채널로 딜리버리되거나, 상기 채널 본딩 적용되어 상기 복수의 채널로 딜리버리되는, 방송 신호 송신 방법.
- 제 2 항에 있어서,상기 서비스 포션 또는 상기 서비스 복제가 채널 본딩 없이 딜리버리되는 경우,상기 서비스 포션 또는 상기 서비스 복제가 딜리버리되는 상기 채널의 SLT는 상기 서비스 포션 또는 상기 서비스 복제를 기술하고,상기 서비스 포션 또는 상기 서비스 복제가 딜리버리되는 상기 각 채널의 PLP는 상기 서비스 포션 또는 상기 서비스 복제에 대한 상기 S-TSID 정보를 포함하는, 방송 신호 송신 방법.
- 제 2 항에 있어서,상기 서비스 포션이 채널 본딩되어 딜리버리되는 경우로서, 상기 에센셜 포션은 넌-본디드 PLP로 딜리버리되는 경우,상기 서비스의 임의의 포션을 딜리버리하는 넌-본디드 PLP 및 본디드 PLP에 연관된 복수의 SLT 정보가 상기 서비스를 리스팅하고, 상기 에센셜 포션에 대한 SLT 정보만이 다른 포션이 딜리버리되는 방송 스트림의 BSID(Broadcast Stream ID)를 리스팅하는, 방송 신호 송신 방법.
- 제 2 항에 있어서,상기 서비스 포션이 채널 본딩되어 딜리버리되는 경우로서, 상기 에센셜 포션은 본디드 PLP로 딜리버리되는 경우,상기 에센셜 포션을 딜리버리하는 상기 본디드 PLP에 연관된 하나의 SLT 정보가 상기 서비스를 리스팅하고, 상기 SLT 정보가 다른 포션이 딜리버리되는 방송 스트림의 BSID(Broadcast Stream ID)를 리스팅하는, 방송 신호 송신 방법.
- 제 2 항에 있어서,상기 서비스 복제가 채널 본딩되어 딜리버리되는 경우,상기 서비스의 복제를 딜리버리하는 넌-본디드 PLP 및 본디드 PLP에 연관된 복수의 SLT 정보가 상기 서비스를 리스팅하고, 상기 서비스 복제에 대한 상기 SLT 정보 각각이 다른 서비스 복제가 딜리버리되는 방송 스트림의 BSID(Broadcast Stream ID)를 리스팅하는, 방송 신호 송신 방법.
- 제 2 항에 있어서,상기 컴포넌트들이 다중 방송 채널의 복수의 방송 스트림에 의해 딜리버리되고, 상기 컴포넌트들에 채널 본딩이 적용되는 경우, 상기 S-TSID는 상기 S-TSID가 딜리버리되는 방송 스트림 외의 다른 방송 스트림에서 딜리버리되는 컴포넌트에 대한 세션 및 채널 정보를 기술하는, 방송 신호 송신 방법.
- 방송 신호를 전송하는 통신 유닛;데이터를 저장하는 메모리; 및상기 통신 유닛 및 상기 메모리를 제어하는 프로세서를 포함하는 방송 신호 송신 장치로서, 상기 방송 신호 송신 장치는,방송 서비스의 적어도 하나의 컴포넌트를 딜리버리 프로토콜에 기초하여 프로세싱하고,상기 컴포넌트에 대한 정보를 포함하는 SLS(Service Layer Signaling) 정보를 생성하며, 상기 SLS 정보는 상기 방송 서비스의 적어도 하나의 컴포넌트를 운반하는 세션에 대한 설명 정보를 포함하는 S-TSID(Service-based Transport Session Instance Description) 정보를 포함하고,상기 SLS 정보의 획득을 위한 부트스트랩 정보를 포함하는 SLT(Service List Table) 정보를 생성하고, 및상기 적어도 하나의 컴포넌트, 상기 SLS 정보 및 상기 SLT 정보를 피지컬 레이어 프로세싱함으로써 PLP(Physical Layer Pipe)를 포함하는 신호 프레임을 생성하고,상기 방송 서비스의 컴포넌트가 다중 RF 채널로 전송되는 경우, 상기 컴포넌트들의 세트는 상기 서비스의 일부 컴포넌트들을 포함하는 서비스 포션 또는 상기 서비스의 모든 컴포넌트들을 포함하는 서비스 복제(duplicate)에 해당하고, 상기 서비스 포션은 다른 포션의 사용 없이 서비스 제공이 가능한 에센셜 포션 또는 넌-에센셜 포션에 해당하는, 방송 신호 송신 장치.
- 제 8 항에 있어서,상기 방송 서비스의 서비스 포션 또는 서비스 복제가 다중 채널로 전송되는 경우, 상기 피지컬 레이어 프로세싱은 상기 서비스 포션 또는 서비스 복제를 포함하는 하나의 PLP를 복수의 채널로 분배하는 채널 본딩 프로세싱을 선택적으로 수행하고,상기 서비스 포션 또는 상기 서비스 복제는 상기 채널 본딩 적용 없이 단일 채널로 딜리버리되거나, 상기 채널 본딩 적용되어 상기 복수의 채널로 딜리버리되는, 방송 신호 송신 장치.
- 제 9 항에 있어서,상기 서비스 포션 또는 상기 서비스 복제가 채널 본딩 없이 딜리버리되는 경우,상기 서비스 포션 또는 상기 서비스 복제가 딜리버리되는 상기 채널의 SLT는 상기 서비스 포션 또는 상기 서비스 복제를 기술하고,상기 서비스 포션 또는 상기 서비스 복제가 딜리버리되는 상기 각 채널의 PLP는 상기 서비스 포션 또는 상기 서비스 복제에 대한 상기 S-TSID 정보를 포함하는, 방송 신호 송신 장치.
- 제 9 항에 있어서,상기 서비스 포션이 채널 본딩되어 딜리버리되는 경우로서, 상기 에센셜 포션은 넌-본디드 PLP로 딜리버리되는 경우,상기 서비스의 임의의 포션을 딜리버리하는 넌-본디드 PLP 및 본디드 PLP에 연관된 복수의 SLT 정보가 상기 서비스를 리스팅하고, 상기 에센셜 포션에 대한 SLT 정보만이 다른 포션이 딜리버리되는 방송 스트림의 BSID(Broadcast Stream ID)를 리스팅하는, 방송 신호 송신 장치.
- 제 9 항에 있어서,상기 서비스 포션이 채널 본딩되어 딜리버리되는 경우로서, 상기 에센셜 포션은 본디드 PLP로 딜리버리되는 경우,상기 에센셜 포션을 딜리버리하는 상기 본디드 PLP에 연관된 하나의 SLT 정보가 상기 서비스를 리스팅하고, 상기 SLT 정보가 다른 포션이 딜리버리되는 방송 스트림의 BSID(Broadcast Stream ID)를 리스팅하는, 방송 신호 송신 장치.
- 제 9 항에 있어서,상기 서비스 복제가 채널 본딩되어 딜리버리되는 경우,상기 서비스의 복제를 딜리버리하는 넌-본디드 PLP 및 본디드 PLP에 연관된 복수의 SLT 정보가 상기 서비스를 리스팅하고, 상기 서비스 복제에 대한 상기 SLT 정보 각각이 다른 서비스 복제가 딜리버리되는 방송 스트림의 BSID(Broadcast Stream ID)를 리스팅하는, 방송 신호 송신 장치.
- 제 9 항에 있어서,상기 컴포넌트들이 다중 방송 채널의 복수의 방송 스트림에 의해 딜리버리되고, 상기 컴포넌트들에 채널 본딩이 적용되는 경우, 상기 S-TSID는 상기 S-TSID가 딜리버리되는 방송 스트림 외의 다른 방송 스트림에서 딜리버리되는 컴포넌트에 대한 세션 및 채널 정보를 기술하는, 방송 신호 송신 장치.
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CA3045597A CA3045597C (en) | 2016-12-02 | 2017-07-06 | Broadcast signal transmitting/receiving device and method |
US16/462,823 US11039186B2 (en) | 2016-12-02 | 2017-07-06 | Broadcast signal transmitting/receiving device and method |
KR1020197018044A KR20190083667A (ko) | 2016-12-02 | 2017-07-06 | 방송 신호 송수신 장치 및 방법 |
US17/202,938 US11252458B2 (en) | 2016-12-02 | 2021-03-16 | Broadcast signal transmitting/receiving device and method |
US17/568,587 US11784860B2 (en) | 2016-12-02 | 2022-01-04 | Broadcast signal transmitting/receiving device and method |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201662429087P | 2016-12-02 | 2016-12-02 | |
US62/429,087 | 2016-12-02 | ||
US201662435084P | 2016-12-16 | 2016-12-16 | |
US62/435,084 | 2016-12-16 |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/462,823 A-371-Of-International US11039186B2 (en) | 2016-12-02 | 2017-07-06 | Broadcast signal transmitting/receiving device and method |
US17/202,938 Continuation US11252458B2 (en) | 2016-12-02 | 2021-03-16 | Broadcast signal transmitting/receiving device and method |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2018101566A1 true WO2018101566A1 (ko) | 2018-06-07 |
Family
ID=62242118
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2017/007217 WO2018101566A1 (ko) | 2016-12-02 | 2017-07-06 | 방송 신호 송수신 장치 및 방법 |
Country Status (4)
Country | Link |
---|---|
US (3) | US11039186B2 (ko) |
KR (1) | KR20190083667A (ko) |
CA (1) | CA3045597C (ko) |
WO (1) | WO2018101566A1 (ko) |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP7062637B2 (ja) * | 2017-03-07 | 2022-05-06 | ソニーセミコンダクタソリューションズ株式会社 | 送信装置、受信装置、及び、データ処理方法 |
JP2020022118A (ja) * | 2018-08-02 | 2020-02-06 | ソニーセミコンダクタソリューションズ株式会社 | 受信装置、通信システム、および、受信装置の制御方法 |
US10911941B2 (en) * | 2019-03-08 | 2021-02-02 | Industry-University Cooperation Foundation Hanyang University | Reconfigurable radio equipment having multiple radio computers, and operation method for the same |
US11368730B2 (en) | 2019-08-27 | 2022-06-21 | Electronics And Telecommunications Research Institute | Apparatus and method for transmitting broadcast content based on ATSC 3.0, and apparatus and method for receiving broadcast content based ATSC 3.0 |
US11363310B2 (en) * | 2020-09-21 | 2022-06-14 | Sony Corporation | ATSC 3.0 hospitality TV system |
KR102620220B1 (ko) * | 2020-12-23 | 2024-01-05 | 주식회사 에어코드 | 지상파 uhd 방송 브로드캐스터 어플리케이션 재전송 시스템 및 그 방법 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20100062541A (ko) * | 2008-12-02 | 2010-06-10 | 주식회사 씨제이헬로비전 | 케이블 방송통신 서비스 방법, 케이블 방송통신용 하이브리드 셋톱박스 및 미들웨어가 기록된 기록매체 |
WO2016108369A1 (ko) * | 2014-12-31 | 2016-07-07 | 엘지전자 주식회사 | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 |
WO2016111430A1 (ko) * | 2015-01-05 | 2016-07-14 | 엘지전자(주) | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 |
WO2016186407A1 (ko) * | 2015-05-17 | 2016-11-24 | 엘지전자(주) | 방송 신호 송수신 장치 및 방법 |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
MX2017008783A (es) * | 2015-01-07 | 2017-10-19 | Sony Corp | Receptor, metodo de recepcion, transmisor y metodo de transmision. |
US10219274B2 (en) * | 2015-04-23 | 2019-02-26 | Marvell World Trade Ltd. | Channel bonding operations in wireless communications |
KR102246464B1 (ko) * | 2015-08-13 | 2021-04-30 | 삼성전자 주식회사 | 무선 통신 시스템에서 전자장치의 전력 절감 방법 및 장치 |
US10715857B2 (en) * | 2015-10-15 | 2020-07-14 | Saturn Licensing Llc | Reception apparatus, transmission apparatus, and data processing method |
KR20180137023A (ko) | 2016-09-13 | 2018-12-26 | 삼성전자주식회사 | 송신 장치 및 그 송신 방법 |
CN109964486B (zh) | 2016-11-03 | 2021-07-20 | 夏普株式会社 | 广播标识符信令 |
-
2017
- 2017-07-06 US US16/462,823 patent/US11039186B2/en active Active
- 2017-07-06 WO PCT/KR2017/007217 patent/WO2018101566A1/ko active Application Filing
- 2017-07-06 KR KR1020197018044A patent/KR20190083667A/ko not_active Application Discontinuation
- 2017-07-06 CA CA3045597A patent/CA3045597C/en active Active
-
2021
- 2021-03-16 US US17/202,938 patent/US11252458B2/en active Active
-
2022
- 2022-01-04 US US17/568,587 patent/US11784860B2/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20100062541A (ko) * | 2008-12-02 | 2010-06-10 | 주식회사 씨제이헬로비전 | 케이블 방송통신 서비스 방법, 케이블 방송통신용 하이브리드 셋톱박스 및 미들웨어가 기록된 기록매체 |
WO2016108369A1 (ko) * | 2014-12-31 | 2016-07-07 | 엘지전자 주식회사 | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 |
WO2016108367A1 (ko) * | 2014-12-31 | 2016-07-07 | 엘지전자 주식회사 | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 |
WO2016111430A1 (ko) * | 2015-01-05 | 2016-07-14 | 엘지전자(주) | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 |
WO2016186407A1 (ko) * | 2015-05-17 | 2016-11-24 | 엘지전자(주) | 방송 신호 송수신 장치 및 방법 |
Also Published As
Publication number | Publication date |
---|---|
US11784860B2 (en) | 2023-10-10 |
US11039186B2 (en) | 2021-06-15 |
CA3045597C (en) | 2024-06-04 |
KR20190083667A (ko) | 2019-07-12 |
US11252458B2 (en) | 2022-02-15 |
US20220182689A1 (en) | 2022-06-09 |
US20190327500A1 (en) | 2019-10-24 |
US20210204005A1 (en) | 2021-07-01 |
CA3045597A1 (en) | 2018-06-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2017204546A1 (ko) | 방송 신호 송수신 장치 및 방법 | |
WO2017014586A1 (ko) | 방송 신호 송수신 장치 및 방법 | |
WO2018101566A1 (ko) | 방송 신호 송수신 장치 및 방법 | |
WO2016186407A1 (ko) | 방송 신호 송수신 장치 및 방법 | |
WO2016140486A1 (ko) | 방송 신호 송수신 장치 및 방법 | |
WO2016076569A1 (ko) | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 | |
WO2016076654A1 (ko) | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 | |
WO2016111526A1 (ko) | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 | |
WO2016126116A1 (ko) | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 | |
WO2016093576A1 (ko) | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 | |
WO2017209514A1 (ko) | 방송 신호 송수신 장치 및 방법 | |
WO2016153241A1 (ko) | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 | |
WO2016122269A1 (ko) | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 | |
WO2016068564A1 (ko) | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 | |
WO2017061792A1 (ko) | 방송 신호 송수신 장치 및 방법 | |
WO2016178549A1 (ko) | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 | |
WO2016129904A1 (ko) | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 | |
WO2016114638A1 (ko) | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 | |
WO2016190720A1 (ko) | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 | |
WO2017164595A1 (ko) | 방송 신호 송수신 장치 및 방법 | |
WO2017123044A1 (ko) | 방송 신호 송수신 장치 및 방법 | |
WO2016072725A1 (ko) | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 | |
WO2017007281A1 (ko) | 방송 신호 송수신 장치 및 방법 | |
WO2016195412A1 (ko) | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 | |
WO2017043898A1 (ko) | 방송 신호 송수신 장치 및 방법 |
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: 17875153 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 3045597 Country of ref document: CA |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 20197018044 Country of ref document: KR Kind code of ref document: A |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 17875153 Country of ref document: EP Kind code of ref document: A1 |