WO2016195412A1 - 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 - Google Patents
방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 Download PDFInfo
- Publication number
- WO2016195412A1 WO2016195412A1 PCT/KR2016/005901 KR2016005901W WO2016195412A1 WO 2016195412 A1 WO2016195412 A1 WO 2016195412A1 KR 2016005901 W KR2016005901 W KR 2016005901W WO 2016195412 A1 WO2016195412 A1 WO 2016195412A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- packet
- link layer
- mpeg2
- packets
- header
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/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
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/32—Flow control; Congestion control by discarding or delaying data units, e.g. packets or frames
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/234—Processing of video elementary streams, e.g. splicing of video streams, manipulating MPEG-4 scene graphs
- H04N21/2343—Processing of video elementary streams, e.g. splicing of video streams, manipulating MPEG-4 scene graphs involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements
- H04N21/234309—Processing of video elementary streams, e.g. splicing of video streams, manipulating MPEG-4 scene graphs involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements by transcoding between formats or standards, e.g. from MPEG-2 to MPEG-4 or from Quicktime to Realvideo
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/235—Processing of additional data, e.g. scrambling of additional data or processing content descriptors
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/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/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 MPEG packets from an 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/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 MPEG packets from an IP network
- H04N21/4381—Recovering the multiplex stream from a specific network, e.g. recovering MPEG packets from ATM cells
Definitions
- the present invention relates to a broadcast signal transmission apparatus, a broadcast signal reception apparatus, and a broadcast signal transmission and reception 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 provides a system and an associated signaling scheme that can effectively support next-generation broadcast services in an environment that supports next-generation hybrid broadcasting using terrestrial broadcasting networks and Internet networks. Suggest.
- 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 is a diagram illustrating processing of data in a link layer, according to an embodiment of the present invention.
- FIG 9 illustrates a structure and an interface of an ALP according to an embodiment of the present invention.
- FIG. 10 illustrates a format of a link layer packet according to an embodiment of the present invention.
- FIG. 11 illustrates a base header structure of a link layer packet according to an embodiment of the present invention.
- FIG. 12 is a diagram illustrating syntax of a header of a link layer packet according to an embodiment of the present invention.
- FIG. 13 is a diagram illustrating the structure and syntax of an additional header for a single packet according to an embodiment of the present invention.
- FIG. 14 illustrates a structure and syntax of an additional header of a link layer packet in case of segmentation according to an embodiment of the present invention.
- 15 is a diagram illustrating the structure and syntax of an additional header of a link layer packet in the case of concatenation according to an embodiment of the present invention.
- 16 is a diagram illustrating syntax of a link layer packet including link layer signaling and an additional header included therein according to an embodiment of the present invention.
- FIG. 17 is a diagram illustrating syntax of a link layer packet including an extended type packet (input packet) and an additional header included therein according to an embodiment of the present invention.
- FIG. 18 is a diagram illustrating syntax of a link layer packet including an MPEG2-TS packet and a header of a link layer packet according to an embodiment of the present invention.
- FIG. 19 illustrates a process of removing a null packet from MPEG2-TS packets according to an embodiment of the present invention.
- FIG. 20 illustrates a process of deleting a header from MPEG2-TS packets according to an embodiment of the present invention.
- 21 is a diagram illustrating a single packet encapsulation structure of a link layer according to an embodiment of the present invention.
- FIG. 22 is a diagram illustrating an encapsulation structure of a link layer packet to which segmentation is applied according to an embodiment of the present invention.
- FIG. 23 is a diagram illustrating an encapsulation structure of a link layer packet to which concatenation is applied according to an embodiment of the present invention.
- FIG. 24 illustrates a concept of encapsulation for an MPEG2-TS packet in a link layer according to an embodiment of the present invention.
- FIG. 25 is a diagram illustrating the concept of encapsulation for MPEG2-TS packets in the link layer, using null packet cancellation, according to an embodiment of the present invention.
- FIG. 26 illustrates a concept of encapsulation for MPEG2-TS packets in a link layer using TS header removal according to an embodiment of the present invention.
- FIG. 27 is a diagram illustrating a transmission path for a context when header compression is performed on an IP packet in a link layer according to an embodiment of the present invention.
- FIG. 28 is a diagram illustrating a process of acquiring a context in a receiver according to an embodiment of the present invention.
- 29 is a flowchart illustrating a method of generating and processing a broadcast signal according to an embodiment of the present invention.
- FIG. 30 is a diagram illustrating a broadcast system according to an embodiment of the present invention.
- the present invention provides an apparatus and method for transmitting and receiving broadcast signals for next generation broadcast services.
- the next generation broadcast service includes a terrestrial broadcast service, a mobile broadcast service, a UHDTV service, and the like.
- a broadcast signal for a next generation broadcast service may be processed through a non-multiple input multiple output (MIMO) or MIMO scheme.
- the non-MIMO scheme according to an embodiment of the present invention may include a multiple input single output (MISO) scheme, a single input single output (SISO) scheme, and the like.
- MISO multiple input single output
- SISO single input single output
- the present invention proposes a physical profile (or system) that is optimized to minimize receiver complexity while achieving the performance required for a particular application.
- FIG. 1 is a diagram illustrating a protocol stack according to an embodiment of the present invention.
- the service may be delivered to the receiver through a plurality of layers.
- the transmitting side can generate service data.
- the delivery layer on the transmitting side performs processing for transmission to the service data, and the physical layer encodes it as a broadcast signal and transmits it through a broadcasting network or broadband.
- the service data may be generated in a format according to ISO BMFF (base media file format).
- the ISO BMFF media file may be used in broadcast network / broadband delivery, media encapsulation and / or synchronization format.
- the service data is all data related to the service, and may include a concept including service components constituting the linear service, signaling information thereof, non real time (NRT) data, and other files.
- the delivery layer will be described.
- the delivery layer may provide a transmission function for service data.
- the service data may be delivered through a broadcast network and / or broadband.
- the first method may be to process service data into Media Processing Units (MPUs) based on MPEG Media Transport (MMT) and transmit the data using MMM protocol (MMTP).
- MPUs Media Processing Units
- MMT MPEG Media Transport
- MMTP MMM protocol
- the service data delivered through the MMTP may include service components for linear service and / or service signaling information thereof.
- the second method may be to process service data into DASH segments based on MPEG DASH and transmit it using Real Time Object Delivery over Unidirectional Transport (ROUTE).
- the service data delivered through the ROUTE protocol may include service components for the linear service, service signaling information and / or NRT data thereof. That is, non-timed data such as NRT data and files may be delivered through ROUTE.
- Data processed according to the MMTP or ROUTE protocol may be processed into IP packets via the UDP / IP layer.
- a service list table (SLT) may also be transmitted through a broadcasting network through a UDP / IP layer.
- the SLT may be included in the LLS (Low Level Signaling) table and transmitted. The SLT and the LLS table will be described later.
- IP packets may be treated as link layer packets at the link layer.
- the link layer may encapsulate data of various formats delivered from an upper layer into a link layer packet and then deliver the data to the physical layer. The link layer will be described later.
- At least one or more service elements may be delivered via a broadband path.
- the data transmitted through the broadband may include service components in a DASH format, service signaling information and / or NRT data thereof. This data can be processed via HTTP / TCP / IP, passed through the link layer for broadband transmission, and delivered to the physical layer for broadband transmission.
- the physical layer may process data received from a delivery layer (upper layer and / or link layer) and transmit the data through a broadcast network or a broadband. Details of the physical layer will be described later.
- the service may be a collection of service components that are shown to the user as a whole, the components may be of different media types, the service may be continuous or intermittent, the service may be real time or non-real time, and the real time service may be a sequence of TV programs. It can be configured as.
- the service may be a linear audio / video or audio only service that may have app-based enhancements.
- the service may be an app-based service whose reproduction / configuration is controlled by the downloaded application.
- the service may be an ESG service that provides an electronic service guide (ESG).
- ESG electronic service guide
- EA Emergency Alert
- the service component may be delivered by (1) one or more ROUTE sessions or (2) one or more MMTP sessions.
- the service component When a linear service with app-based enhancement is delivered through a broadcast network, the service component may be delivered by (1) one or more ROUTE sessions and (2) zero or more MMTP sessions.
- data used for app-based enhancement may be delivered through a ROUTE session in the form of NRT data or other files.
- linear service components (streaming media components) of one service may not be allowed to be delivered using both protocols simultaneously.
- the service component may be delivered by one or more ROUTE sessions.
- the service data used for the app-based service may be delivered through a ROUTE session in the form of NRT data or other files.
- some service components or some NRT data, files, etc. of these services may be delivered via broadband (hybrid service delivery).
- the linear service components of one service may be delivered through the MMT protocol.
- the linear service components of one service may be delivered via a ROUTE protocol.
- the linear service component and NRT data (NRT service component) of one service may be delivered through the ROUTE protocol.
- linear service components of one service may be delivered through the MMT protocol, and NRT data (NRT service components) may be delivered through the ROUTE protocol.
- some service component or some NRT data of a service may be delivered over broadband.
- the data related to the app-based service or the app-based enhancement may be transmitted through a broadcast network according to ROUTE or through broadband in the form of NRT data.
- NRT data may also be referred to as locally cashed data.
- Each ROUTE session includes one or more LCT sessions that deliver, in whole or in part, the content components that make up the service.
- an LCT session may deliver an individual component of a user service, such as an audio, video, or closed caption stream.
- Streaming media is formatted into a DASH segment.
- Each MMTP session includes one or more MMTP packet flows carrying an MMT signaling message or all or some content components.
- the MMTP packet flow may carry a component formatted with an MMT signaling message or an MPU.
- an LCT session For delivery of NRT user service or system metadata, an LCT session carries a file based content item.
- These content files may consist of continuous (timed) or discrete (non-timed) media components of an NRT service, or metadata such as service signaling or ESG fragments.
- Delivery of system metadata, such as service signaling or ESG fragments, can also be accomplished through the signaling message mode of the MMTP.
- the tuner can scan frequencies and detect broadcast signals at specific frequencies.
- the receiver can extract the SLT and send it to the module that processes it.
- the SLT parser can parse the SLT, obtain data, and store it in the channel map.
- the receiver may acquire bootstrap information of the SLT and deliver it to the ROUTE or MMT client. This allows the receiver to obtain and store the SLS. USBD or the like can be obtained, which can be parsed by the signaling parser.
- FIG. 2 is a diagram illustrating a service discovery process according to an embodiment of the present invention.
- the broadcast stream delivered by the broadcast signal frame of the physical layer may carry LLS (Low Level Signaling).
- LLS data may be carried through the payload of an IP packet delivered to a well known IP address / port. This LLS may contain an SLT depending on its type.
- LLS data may be formatted in the form of an LLS table. The first byte of every UDP / IP packet carrying LLS data may be the beginning of the LLS table. Unlike the illustrated embodiment, the IP stream carrying LLS data may be delivered to the same PLP along with other service data.
- the SLT enables the receiver to generate a service list through a fast channel scan and provides access information for locating the SLS.
- the SLT includes bootstrap information, which enables the receiver to obtain Service Layer Signaling (SLS) for each service.
- SLS Service Layer Signaling
- the bootstrap information may include destination IP address and destination port information of the ROUTE session including the LCT channel carrying the SLS and the LCT channel.
- the bootstrap information may include a destination IP address and destination port information of the MMTP session carrying the SLS.
- the SLS of service # 1 described by the SLT is delivered via ROUTE, and the SLT includes bootstrap information (sIP1, dIP1, dPort1) for the ROUTE session including the LCT channel to which the SLS is delivered. can do.
- SLS of service # 2 described by the SLT is delivered through MMT, and the SLT may include bootstrap information (sIP2, dIP2, and dPort2) for an MMTP session including an MMTP packet flow through which the SLS is delivered.
- the SLS is signaling information describing characteristics of a corresponding service and may include information for acquiring a corresponding service and a service component of the corresponding service, or may include receiver capability information for reproducing the corresponding service significantly. Having separate service signaling for each service allows the receiver to obtain the appropriate SLS for the desired service without having to parse the entire SLS delivered in the broadcast stream.
- the SLS When the SLS is delivered through the ROUTE protocol, the SLS may be delivered through a dedicated LCT channel of a ROUTE session indicated by the SLT.
- the SLS may include a user service bundle description (USBD / USD), a service-based transport session instance description (S-TSID), and / or a media presentation description (MPD).
- USBD / USD user service bundle description
- S-TSID service-based transport session instance description
- MPD media presentation description
- USBD to USD is one of the SLS fragments and may serve as a signaling hub for describing specific technical information of a service.
- the USBD may include service identification information, device capability information, and the like.
- the USBD may include reference information (URI reference) to other SLS fragments (S-TSID, MPD, etc.). That is, USBD / USD can refer to S-TSID and MPD respectively.
- the USBD may further include metadata information that enables the receiver to determine the transmission mode (broadcast network / broadband). Details of the USBD / USD will be described later.
- the S-TSID is one of the SLS fragments, and may provide overall session description information for a transport session carrying a service component of a corresponding service.
- the S-TSID may provide transport session description information for the ROUTE session to which the service component of the corresponding service is delivered and / or the LCT channel of the ROUTE sessions.
- the S-TSID may provide component acquisition information of service components related to one service.
- the S-TSID may provide a mapping between the DASH Representation of the MPD and the tsi of the corresponding service component.
- the component acquisition information of the S-TSID may be provided in the form of tsi, an identifier of an associated DASH representation, and may or may not include a PLP ID according to an embodiment.
- the component acquisition information enables the receiver to collect audio / video components of a service and to buffer, decode, and the like of DASH media segments.
- the S-TSID may be referenced by the USBD as described above. Details of the S-TSID will be described later.
- the MPD is one of the SLS fragments and may provide a description of the DASH media presentation of the service.
- the MPD may provide a resource identifier for the media segments and may provide contextual information within the media presentation for the identified resources.
- the MPD may describe the DASH representation (service component) delivered through the broadcast network, and may also describe additional DASH representations delivered through the broadband (hybrid delivery).
- the MPD may be referenced by the USBD as described above.
- the SLS When the SLS is delivered through the MMT protocol, the SLS may be delivered through a dedicated MMTP packet flow of an MMTP session indicated by the SLT.
- packet_id of MMTP packets carrying SLS may have a value of 00.
- the SLS may include a USBD / USD and / or MMT Package (MP) table.
- USBD is one of the SLS fragments, and may describe specific technical information of a service like that in ROUTE.
- the USBD here may also include reference information (URI reference) to other SLS fragments.
- the USBD of the MMT may refer to the MP table of the MMT signaling.
- the USBD of the MMT may also include reference information on the S-TSID and / or the MPD.
- the S-TSID may be for NRT data transmitted through the ROUTE protocol. This is because NRT data can be delivered through the ROUTE protocol even when the linear service component is delivered through the MMT protocol.
- MPD may be for a service component delivered over broadband in hybrid service delivery. Details of the USBD of the MMT will be described later.
- the MP table is a signaling message of the MMT for MPU components and may provide overall session description information for an MMTP session carrying a service component of a corresponding service.
- the MP table may also contain descriptions for assets delivered via this MMTP session.
- the MP table is streaming signaling information for MPU components, and may provide a list of assets corresponding to one service and location information (component acquisition information) of these components. Specific contents of the MP table may be in a form defined in MMT or a form in which modifications are made.
- Asset is a multimedia data entity, which may mean a data entity associated with one unique ID and used to generate one multimedia presentation. Asset may correspond to a service component constituting a service.
- the MP table may be used to access a streaming service component (MPU) corresponding to a desired service.
- the MP table may be referenced by the USBD as described above.
- MMT signaling messages may be defined. Such MMT signaling messages may describe additional information related to the MMTP session or service.
- ROUTE sessions are identified by source IP address, destination IP address, and destination port number.
- the LCT session is identified by a transport session identifier (TSI) that is unique within the scope of the parent ROUTE session.
- MMTP sessions are identified by destination IP address and destination port number.
- the MMTP packet flow is identified by a unique packet_id within the scope of the parent MMTP session.
- the S-TSID, the USBD / USD, the MPD, or the LCT session carrying them may be called a service signaling channel.
- the S-TSID, the USBD / USD, the MPD, or the LCT session carrying them may be called a service signaling channel.
- the S-TSID, the USBD / USD, the MPD, or the LCT session carrying them may be called a service signaling channel.
- the MMT signaling messages or packet flow carrying them may be called a service signaling channel.
- one ROUTE or MMTP session may be delivered through a plurality of PLPs. That is, one service may be delivered through one or more PLPs. Unlike shown, components constituting one service may be delivered through different ROUTE sessions. In addition, according to an embodiment, components constituting one service may be delivered through different MMTP sessions. According to an embodiment, components constituting one service may be delivered divided into a ROUTE session and an MMTP session. Although not shown, a component constituting one service may be delivered through a broadband (hybrid delivery).
- LLS low level signaling
- SLT service list table
- An embodiment t3010 of the illustrated LLS table may include information according to an LLS_table_id field, a provider_id field, an LLS_table_version field, and / or an LLS_table_id field.
- the LLS_table_id field may identify a type of the corresponding LLS table, and the provider_id field may identify service providers related to services signaled by the corresponding LLS table.
- the service provider is a broadcaster using all or part of the broadcast stream, and the provider_id field may identify one of a plurality of broadcasters using the broadcast stream.
- the LLS_table_version field may provide version information of a corresponding LLS table.
- the corresponding LLS table includes the above-described SLT, a rating region table (RRT) including information related to a content advisory rating, a SystemTime information providing information related to system time, and an emergency alert. It may include one of the CAP (Common Alert Protocol) message that provides information related to. According to an embodiment, other information other than these may be included in the LLS table.
- RRT rating region table
- CAP Common Alert Protocol
- One embodiment t3020 of the illustrated SLT may include an @bsid attribute, an @sltCapabilities attribute, a sltInetUrl element, and / or a Service element.
- Each field may be omitted or may exist in plurality, depending on the value of the illustrated Use column.
- the @bsid attribute may be an identifier of a broadcast stream.
- the @sltCapabilities attribute can provide the capability information required to decode and significantly reproduce all services described by the SLT.
- the sltInetUrl element may provide base URL information used to obtain ESG or service signaling information for services of the corresponding SLT through broadband.
- the sltInetUrl element may further include an @urlType attribute, which may indicate the type of data that can be obtained through the URL.
- the service element may be an element including information on services described by the corresponding SLT, and a service element may exist for each service.
- the Service element contains the @serviceId property, the @sltSvcSeqNum property, the @protected property, the @majorChannelNo property, the @minorChannelNo property, the @serviceCategory property, the @shortServiceName property, the @hidden property, the @broadbandAccessRequired property, the @svcCapabilities property, the BroadcastSvcSignaling element, and / or the svcInetUrl element. It may include.
- the @serviceId attribute may be an identifier of a corresponding service, and the @sltSvcSeqNum attribute may indicate a sequence number of SLT information for the corresponding service.
- the @protected attribute may indicate whether at least one service component necessary for meaningful playback of the corresponding service is protected.
- the @majorChannelNo and @minorChannelNo attributes may indicate the major channel number and the minor channel number of the corresponding service, respectively.
- the @serviceCategory attribute can indicate the category of the corresponding service.
- the service category may include a linear A / V service, a linear audio service, an app-based service, an ESG service, and an EAS service.
- the @shortServiceName attribute may provide a short name of the corresponding service.
- the @hidden attribute can indicate whether the service is for testing or proprietary use.
- the @broadbandAccessRequired attribute may indicate whether broadband access is required for meaningful playback of the corresponding service.
- the @svcCapabilities attribute can provide the capability information necessary for decoding and meaningful reproduction of the corresponding service.
- the BroadcastSvcSignaling element may provide information related to broadcast signaling of a corresponding service. This element may provide information such as a location, a protocol, and an address with respect to signaling through a broadcasting network of a corresponding service. Details will be described later.
- the svcInetUrl element may provide URL information for accessing signaling information for a corresponding service through broadband.
- the sltInetUrl element may further include an @urlType attribute, which may indicate the type of data that can be obtained through the URL.
- the aforementioned BroadcastSvcSignaling element may include an @slsProtocol attribute, an @slsMajorProtocolVersion attribute, an @slsMinorProtocolVersion attribute, an @slsPlpId attribute, an @slsDestinationIpAddress attribute, an @slsDestinationUdpPort attribute, and / or an @slsSourceIpAddress attribute.
- the @slsProtocol attribute can indicate the protocol used to deliver the SLS of the service (ROUTE, MMT, etc.).
- the @slsMajorProtocolVersion attribute and @slsMinorProtocolVersion attribute may indicate the major version number and the minor version number of the protocol used to deliver the SLS of the corresponding service, respectively.
- the @slsPlpId attribute may provide a PLP identifier for identifying a PLP that delivers the SLS of the corresponding service.
- this field may be omitted, and the PLP information to which the SLS is delivered may be identified by combining information in the LMT to be described later and bootstrap information of the SLT.
- the @slsDestinationIpAddress attribute, @slsDestinationUdpPort attribute, and @slsSourceIpAddress attribute may indicate the destination IP address, the destination UDP port, and the source IP address of the transport packet carrying the SLS of the corresponding service, respectively. They can identify the transport session (ROUTE session or MMTP session) to which the SLS is delivered. These may be included in the bootstrap information.
- FIG. 4 illustrates a USBD and an S-TSID delivered to ROUTE according to an embodiment of the present invention.
- One embodiment t4010 of the illustrated USBD may have a bundleDescription root element.
- the bundleDescription root element may have a userServiceDescription element.
- the userServiceDescription element may be an instance of one service.
- the userServiceDescription element may include an @globalServiceID attribute, an @serviceId attribute, an @serviceStatus attribute, an @fullMPDUri attribute, an @sTSIDUri attribute, a name element, a serviceLanguage element, a capabilityCode element, and / or a deliveryMethod element.
- Each field may be omitted or may exist in plurality, depending on the value of the illustrated Use column.
- the @globalServiceID attribute is a globally unique identifier of the service and can be used to link with ESG data (Service @ globalServiceID).
- the @serviceId attribute is a reference corresponding to the corresponding service entry of the SLT and may be the same as service ID information of the SLT.
- the @serviceStatus attribute may indicate the status of the corresponding service. This field may indicate whether the corresponding service is active or inactive.
- the @fullMPDUri attribute can refer to the MPD fragment of the service. As described above, the MPD may provide a reproduction description for a service component delivered through a broadcast network or a broadband.
- the @sTSIDUri attribute may refer to the S-TSID fragment of the service.
- the S-TSID may provide parameters related to access to the transport session carrying the service as described above.
- the name element may provide the name of the service.
- This element may further include an @lang attribute, which may indicate the language of the name provided by the name element.
- the serviceLanguage element may indicate the available languages of the service. That is, this element may list the languages in which the service can be provided.
- the capabilityCode element may indicate capability or capability group information of the receiver side necessary for significantly playing a corresponding service. This information may be compatible with the capability information format provided by the service announcement.
- the deliveryMethod element may provide delivery related information with respect to contents accessed through a broadcasting network or a broadband of a corresponding service.
- the deliveryMethod element may include a broadcastAppService element and / or a unicastAppService element. Each of these elements may have a basePattern element as its child element.
- the broadcastAppService element may include transmission related information on the DASH presentation delivered through the broadcast network.
- These DASH representations may include media components across all periods of the service media presentation.
- the basePattern element of this element may represent a character pattern used by the receiver to match the segment URL. This can be used by the DASH client to request segments of the representation. Matching may imply that the media segment is delivered over the broadcast network.
- the unicastAppService element may include transmission related information on the DASH representation delivered through broadband. These DASH representations may include media components across all periods of the service media presentation.
- the basePattern element of this element may represent a character pattern used by the receiver to match the segment URL. This can be used by the DASH client to request segments of the representation. Matching may imply that the media segment is delivered over broadband.
- An embodiment t4020 of the illustrated S-TSID may have an S-TSID root element.
- the S-TSID root element may include an @serviceId attribute and / or an RS element.
- Each field may be omitted or may exist in plurality, depending on the value of the illustrated Use column.
- the @serviceId attribute is an identifier of a corresponding service and may refer to a corresponding service of USBD / USD.
- the RS element may describe information on ROUTE sessions through which service components of a corresponding service are delivered. Depending on the number of such ROUTE sessions, there may be a plurality of these elements.
- the RS element may further include an @bsid attribute, an @sIpAddr attribute, an @dIpAddr attribute, an @dport attribute, an @PLPID attribute, and / or an LS element.
- the @bsid attribute may be an identifier of a broadcast stream through which service components of a corresponding service are delivered. If this field is omitted, the default broadcast stream may be a broadcast stream that includes a PLP that carries the SLS of the service. The value of this field may be the same value as the @bsid attribute of SLT.
- the @sIpAddr attribute, the @dIpAddr attribute, and the @dport attribute may indicate a source IP address, a destination IP address, and a destination UDP port of the corresponding ROUTE session, respectively. If these fields are omitted, the default values may be the source IP address, destination IP address, and destination UDP port values of the current, ROUTE session carrying that SLS, that is, carrying that S-TSID. For other ROUTE sessions that carry service components of the service but not the current ROUTE session, these fields may not be omitted.
- the @PLPID attribute may indicate PLP ID information of a corresponding ROUTE session. If this field is omitted, the default value may be the PLP ID value of the current PLP to which the corresponding S-TSID is being delivered. According to an embodiment, this field is omitted, and the PLP ID information of the corresponding ROUTE session may be confirmed by combining information in the LMT to be described later and IP address / UDP port information of the RS element.
- the LS element may describe information on LCT channels through which service components of a corresponding service are delivered. Depending on the number of such LCT channels, there may be a plurality of these elements.
- the LS element may include an @tsi attribute, an @PLPID attribute, an @bw attribute, an @startTime attribute, an @endTime attribute, an SrcFlow element, and / or a RepairFlow element.
- the @tsi attribute may represent tsi information of a corresponding LCT channel. Through this, LCT channels through which a service component of a corresponding service is delivered may be identified.
- the @PLPID attribute may represent PLP ID information of a corresponding LCT channel. In some embodiments, this field may be omitted.
- the @bw attribute may indicate the maximum bandwidth of the corresponding LCT channel.
- the @startTime attribute may indicate the start time of the LCT session, and the @endTime attribute may indicate the end time of the LCT channel.
- the SrcFlow element may describe the source flow of ROUTE.
- the source protocol of ROUTE is used to transmit the delivery object, and can establish at least one source flow in one ROUTE session. These source flows can deliver related objects as an object flow.
- the RepairFlow element may describe the repair flow of ROUTE. Delivery objects delivered according to the source protocol may be protected according to Forward Error Correction (FEC).
- FEC Forward Error Correction
- the repair protocol may define a FEC framework that enables such FEC protection.
- FIG. 5 is a diagram illustrating a USBD delivered to MMT according to an embodiment of the present invention.
- One embodiment of the illustrated USBD may have a bundleDescription root element.
- the bundleDescription root element may have a userServiceDescription element.
- the userServiceDescription element may be an instance of one service.
- the userServiceDescription element may include an @globalServiceID attribute, an @serviceId attribute, a Name element, a serviceLanguage element, a content advisoryRating element, a Channel element, an mpuComponent element, a routeComponent element, a broadbandComponent element, and / or a ComponentInfo element.
- Each field may be omitted or may exist in plurality, depending on the value of the illustrated Use column.
- the @globalServiceID attribute, the @serviceId attribute, the Name element and / or the serviceLanguage element may be the same as the corresponding fields of the USBD delivered to the above-described ROUTE.
- the contentAdvisoryRating element may indicate the content advisory rating of the corresponding service. This information may be compatible with the content advisory rating information format provided by the service announcement.
- the channel element may include information related to the corresponding service. The detail of this element is mentioned later.
- the mpuComponent element may provide a description for service components delivered as an MPU of a corresponding service.
- This element may further include an @mmtPackageId attribute and / or an @nextMmtPackageId attribute.
- the @mmtPackageId attribute may refer to an MMT package of service components delivered as an MPU of a corresponding service.
- the @nextMmtPackageId attribute may refer to an MMT package to be used next to the MMT package referenced by the @mmtPackageId attribute in time.
- the MP table can be referenced through the information of this element.
- the routeComponent element may include a description of service components of the corresponding service delivered to ROUTE. Even if the linear service components are delivered in the MMT protocol, the NRT data may be delivered according to the ROUTE protocol as described above. This element may describe information about such NRT data. The detail of this element is mentioned later.
- the broadbandComponent element may include a description of service components of the corresponding service delivered over broadband.
- some service components or other files of a service may be delivered over broadband. This element may describe information about these data.
- This element may further include the @fullMPDUri attribute. This attribute may refer to an MPD that describes service components delivered over broadband.
- the element when the broadcast signal is weakened due to driving in a tunnel or the like, the element may be needed to support handoff between the broadcast network and the broadband band. When the broadcast signal is weakened, while acquiring the service component through broadband, and when the broadcast signal is stronger, the service continuity may be guaranteed by acquiring the service component through the broadcast network.
- the ComponentInfo element may include information on service components of a corresponding service. Depending on the number of service components of the service, there may be a plurality of these elements. This element may describe information such as the type, role, name, identifier, and protection of each service component. Detailed information on this element will be described later.
- the aforementioned channel element may further include an @serviceGenre attribute, an @serviceIcon attribute, and / or a ServiceDescription element.
- the @serviceGenre attribute may indicate the genre of the corresponding service
- the @serviceIcon attribute may include URL information of an icon representing the corresponding service.
- the ServiceDescription element provides a service description of the service, which may further include an @serviceDescrText attribute and / or an @serviceDescrLang attribute. Each of these attributes may indicate the text of the service description and the language used for that text.
- the aforementioned routeComponent element may further include an @sTSIDUri attribute, an @sTSIDDestinationIpAddress attribute, an @sTSIDDestinationUdpPort attribute, an @sTSIDSourceIpAddress attribute, an @sTSIDMajorProtocolVersion attribute, and / or an @sTSIDMinorProtocolVersion attribute.
- the @sTSIDUri attribute may refer to an S-TSID fragment. This field may be the same as the corresponding field of USBD delivered to ROUTE described above. This S-TSID may provide access related information for service components delivered in ROUTE. This S-TSID may exist for NRT data delivered according to the ROUTE protocol in the situation where linear service components are delivered according to the MMT protocol.
- the @sTSIDDestinationIpAddress attribute, the @sTSIDDestinationUdpPort attribute, and the @sTSIDSourceIpAddress attribute may indicate a destination IP address, a destination UDP port, and a source IP address of a transport packet carrying the aforementioned S-TSID, respectively. That is, these fields may identify a transport session (MMTP session or ROUTE session) carrying the aforementioned S-TSID.
- the @sTSIDMajorProtocolVersion attribute and the @sTSIDMinorProtocolVersion attribute may indicate a major version number and a minor version number of the transport protocol used to deliver the aforementioned S-TSID.
- ComponentInfo element may further include an @componentType attribute, an @componentRole attribute, an @componentProtectedFlag attribute, an @componentId attribute, and / or an @componentName attribute.
- the @componentType attribute may indicate the type of the corresponding component. For example, this property may indicate whether the corresponding component is an audio, video, or closed caption component.
- the @componentRole attribute can indicate the role (role) of the corresponding component. For example, this property can indicate whether the main audio, music, commentary, etc., if the corresponding component is an audio component. If the corresponding component is a video component, it may indicate whether it is primary video. If the corresponding component is a closed caption component, it may indicate whether it is a normal caption or an easy reader type.
- the @componentProtectedFlag attribute may indicate whether a corresponding service component is protected, for example, encrypted.
- the @componentId attribute may represent an identifier of a corresponding service component.
- the value of this attribute may be a value such as asset_id (asset ID) of the MP table corresponding to this service component.
- the @componentName attribute may represent the name of the corresponding service component.
- FIG. 6 illustrates a link layer operation according to an embodiment of the present invention.
- the link layer may be a layer between the physical layer and the network layer.
- the transmitter may transmit data from the network layer to the physical layer
- the receiver may transmit data from the physical layer to the network layer (t6010).
- the purpose of the link layer may be to compress all input packet types into one format for processing by the physical layer, to ensure flexibility and future scalability for input packet types not yet defined. have.
- the link layer may provide an option of compressing unnecessary information in the header of the input packet, so that the input data may be efficiently transmitted. Operations such as overhead reduction and encapsulation of the link layer may be referred to as a link layer protocol, and a packet generated using the corresponding protocol may be referred to as a link layer packet.
- the link layer may perform functions such as packet encapsulation, overhead reduction, and / or signaling transmission.
- the link layer ALP may perform an overhead reduction process on input packets and then encapsulate them into link layer packets.
- the link layer may encapsulate the link layer packet without performing an overhead reduction process.
- the use of the link layer protocol can greatly reduce the overhead for data transmission on the physical layer, and the link layer protocol according to the present invention can provide IP overhead reduction and / or MPEG-2 TS overhead reduction. have.
- the link layer may sequentially perform IP header compression, adaptation, and / or encapsulation. In some embodiments, some processes may be omitted.
- the RoHC module performs IP packet header compression to reduce unnecessary overhead, and context information may be extracted and transmitted out of band through an adaptation process.
- the IP header compression and adaptation process may be collectively called IP header compression.
- IP packets may be encapsulated into link layer packets through an encapsulation process.
- the link layer may sequentially perform an overhead reduction and / or encapsulation process for the TS packet. In some embodiments, some processes may be omitted.
- the link layer may provide sync byte removal, null packet deletion and / or common header removal (compression).
- Sync byte elimination can provide overhead reduction of 1 byte per TS packet. Null packet deletion can be performed in a manner that can be reinserted at the receiving end. In addition, common information between successive headers can be deleted (compressed) in a manner that can be recovered at the receiving side. Some of each overhead reduction process may be omitted. Thereafter, TS packets may be encapsulated into link layer packets through an encapsulation process.
- the link layer packet structure for encapsulation of TS packets may be different from other types of packets.
- IP header compression will be described.
- the IP packet has a fixed header format, but some information required in a communication environment may be unnecessary in a broadcast environment.
- the link layer protocol may provide a mechanism to reduce broadcast overhead by compressing the header of the IP packet.
- IP header compression may include a header compressor / decompressor and / or adaptation module.
- the IP header compressor (RoHC compressor) may reduce the size of each IP packet header based on the RoHC scheme.
- the adaptation module may then extract the context information and generate signaling information from each packet stream.
- the receiver may parse signaling information related to the packet stream and attach context information to the packet stream.
- the RoHC decompressor can reconstruct the original IP packet by recovering the packet header.
- IP header compression may mean only IP header compression by a header compressor, or may mean a concept in which the IP header compression and the adaptation process by the adaptation module are combined. The same is true for decompressing.
- the adaptation function may generate link layer signaling using context information and / or configuration parameters.
- the adaptation function may periodically send link layer signaling over each physical frame using previous configuration parameters and / or context information.
- the context information is extracted from the compressed IP packets, and various methods may be used according to the adaptation mode.
- Mode # 1 is a mode in which no operation is performed on the compressed packet stream, and may be a mode in which the adaptation module operates as a buffer.
- Mode # 2 may be a mode for extracting context information (static chain) by detecting IR packets in the compressed packet stream. After extraction, the IR packet is converted into an IR-DYN packet, and the IR-DYN packet can be transmitted in the same order in the packet stream by replacing the original IR packet.
- context information static chain
- Mode # 3 t6020 may be a mode for detecting IR and IR-DYN packets and extracting context information from the compressed packet stream.
- Static chains and dynamic chains can be extracted from IR packets and dynamic chains can be extracted from IR-DYN packets.
- the IR and IR-DYN packets can be converted into regular compressed packets.
- the switched packets can be sent in the same order within the packet stream, replacing the original IR and IR-DYN packets.
- the remaining packets after the context information is extracted may be encapsulated and transmitted according to the link layer packet structure for the compressed IP packet.
- the context information may be transmitted by being encapsulated according to a link layer packet structure for signaling information as link layer signaling.
- the extracted context information may be included in the RoHC-U Description Table (RTT) and transmitted separately from the RoHC packet flow.
- the context information may be transmitted through a specific physical data path along with other signaling information.
- a specific physical data path may mean one of general PLPs, a PLP to which LLS (Low Level Signaling) is delivered, a dedicated PLP, or an L1 signaling path. path).
- the RDT may be signaling information including context information (static chain and / or dynamic chain) and / or information related to header compression.
- the RDT may be transmitted whenever the context information changes.
- the RDT may be transmitted in every physical frame. In order to transmit the RDT in every physical frame, a previous RDT may be re-use.
- the receiver may first select PLP to acquire signaling information such as SLT, RDT, LMT, and the like. When the signaling information is obtained, the receiver may combine these to obtain a mapping between the service-IP information-context information-PLP. That is, the receiver can know which service is transmitted to which IP streams, which IP streams are delivered to which PLP, and can also obtain corresponding context information of the PLPs. The receiver can select and decode a PLP carrying a particular packet stream. The adaptation module can parse the context information and merge it with the compressed packets. This allows the packet stream to be recovered, which can be delivered to the RoHC decompressor. Decompression can then begin.
- signaling information such as SLT, RDT, LMT, and the like.
- the receiver may combine these to obtain a mapping between the service-IP information-context information-PLP. That is, the receiver can know which service is transmitted to which IP streams, which IP streams are delivered to which PLP, and can also obtain corresponding context information of the PLPs.
- the receiver detects the IR packet and starts decompression from the first received IR packet according to the adaptation mode (mode 1), or detects the IR-DYN packet to perform decompression from the first received IR-DYN packet.
- the link layer protocol may encapsulate all types of input packets, such as IP packets and TS packets, into link layer packets. This allows the physical layer to process only one packet format independently of the protocol type of the network layer (here, consider MPEG-2 TS packet as a kind of network layer packet). Each network layer packet or input packet is transformed into a payload of a generic link layer packet.
- Segmentation may be utilized in the packet encapsulation process. If the network layer packet is too large to be processed by the physical layer, the network layer packet may be divided into two or more segments.
- the link layer packet header may include fields for performing division at the transmitting side and recombination at the receiving side. Each segment may be encapsulated into a link layer packet in the same order as the original position.
- Concatenation may also be utilized in the packet encapsulation process. If the network layer packet is small enough that the payload of the link layer packet includes several network layer packets, concatenation may be performed.
- the link layer packet header may include fields for executing concatenation. In the case of concatenation, each input packet may be encapsulated into the payload of the link layer packet in the same order as the original input order.
- the link layer packet may include a header and a payload, and the header may include a base header, an additional header, and / or an optional header.
- the additional header may be added depending on the chaining or splitting, and the additional header may include necessary fields according to the situation.
- an optional header may be further added to transmit additional information.
- Each header structure may be predefined. As described above, when the input packet is a TS packet, a link layer header structure different from other packets may be used.
- Link layer signaling may operate at a lower level than the IP layer.
- the receiving side can acquire the link layer signaling faster than the IP level signaling such as LLS, SLT, SLS, and the like. Therefore, link layer signaling may be obtained before session establishment.
- Link layer signaling may include internal link layer signaling and external link layer signaling.
- Internal link layer signaling may be signaling information generated in the link layer.
- the above-described RDT or LMT to be described later may correspond to this.
- the external link layer signaling may be signaling information received from an external module, an external protocol, or an upper layer.
- the link layer may encapsulate link layer signaling into a link layer packet and deliver it.
- a link layer packet structure (header structure) for link layer signaling may be defined, and link layer signaling information may be encapsulated according to this structure.
- FIG. 7 illustrates a link mapping table (LMT) according to an embodiment of the present invention.
- the LMT may provide a list of higher layer sessions carried by the PLP.
- the LMT may also provide additional information for processing link layer packets carrying higher layer sessions.
- the higher layer session may be called multicast.
- Information on which IP streams and which transport sessions are being transmitted through a specific PLP may be obtained through the LMT. Conversely, information on which PLP a specific transport session is delivered to may be obtained.
- the LMT may be delivered to any PLP identified as carrying an LLS.
- the PLP through which the LLS is delivered may be identified by the LLS flag of the L1 detail signaling information of the physical layer.
- the LLS flag may be a flag field indicating whether LLS is delivered to the corresponding PLP for each PLP.
- the L1 detail signaling information may correspond to PLS2 data to be described later.
- the LMT may be delivered to the same PLP together with the LLS.
- Each LMT may describe the mapping between PLPs and IP address / port as described above.
- the LLS may include an SLT, where these IP addresses / ports described by the LMT are all IP addresses associated with any service described by the SLT forwarded to the same PLP as that LMT. It can be / ports.
- the PLP identifier information in the above-described SLT, SLS, etc. may be utilized, so that information on which PLP the specific transmission session indicated by the SLT, SLS is transmitted may be confirmed.
- the PLP identifier information in the above-described SLT, SLS, etc. may be omitted, and the PLP information for the specific transport session indicated by the SLT, SLS may be confirmed by referring to the information in the LMT.
- the receiver may identify the PLP to know by combining LMT and other IP level signaling information.
- PLP information in SLT, SLS, and the like is not omitted, and may remain in the SLT, SLS, and the like.
- the LMT according to the illustrated embodiment may include a signaling_type field, a PLP_ID field, a num_session field, and / or information about respective sessions.
- a PLP loop may be added to the LMT according to an embodiment, so that information on a plurality of PLPs may be described.
- the LMT may describe PLPs for all IP addresses / ports related to all services described by the SLTs delivered together, in a PLP loop.
- the signaling_type field may indicate the type of signaling information carried by the corresponding table.
- the value of the signaling_type field for the LMT may be set to 0x01.
- the signaling_type field may be omitted.
- the PLP_ID field may identify a target PLP to be described. When a PLP loop is used, each PLP_ID field may identify each target PLP. From the PLP_ID field may be included in the PLP loop.
- the PLP_ID field mentioned below is an identifier for one PLP in a PLP loop, and the fields described below may be fields for the corresponding PLP.
- the num_session field may indicate the number of upper layer sessions delivered to the PLP identified by the corresponding PLP_ID field. According to the number indicated by the num_session field, information about each session may be included. This information may include an src_IP_add field, a dst_IP_add field, a src_UDP_port field, a dst_UDP_port field, a SID_flag field, a compressed_flag field, a SID field, and / or a context_id field.
- the src_IP_add field, dst_IP_add field, src_UDP_port field, and dst_UDP_port field are the source IP address, destination IP address, source UDP port, destination UDP port for the transport session among the upper layer sessions forwarded to the PLP identified by the corresponding PLP_ID field. It can indicate a port.
- the SID_flag field may indicate whether a link layer packet carrying a corresponding transport session has an SID field in its optional header.
- a link layer packet carrying an upper layer session may have an SID field in its optional header, and the SID field value may be the same as an SID field in an LMT to be described later.
- the compressed_flag field may indicate whether header compression has been applied to data of a link layer packet carrying a corresponding transport session.
- the existence of the context_id field to be described later may be determined according to the value of this field.
- the SID field may indicate a sub stream ID (SID) for link layer packets carrying a corresponding transport session.
- SID sub stream ID
- These link layer packets may include an SID having the same value as this SID field in the optional header.
- the context_id field may provide a reference to a context id (CID) in the RDT.
- the CID information of the RDT may indicate the context ID for the corresponding compressed IP packet stream.
- the RDT may provide context information for the compressed IP packet stream. RDT and LMT may be associated with this field.
- each field, element, or attribute may be omitted or replaced by another field, and additional fields, elements, or attributes may be added according to an embodiment. .
- service components of one service may be delivered through a plurality of ROUTE sessions.
- the SLS may be obtained through the bootstrap information of the SLT.
- the SLS's USBD allows the S-TSID and MPD to be referenced.
- the S-TSID may describe transport session description information for other ROUTE sessions to which service components are delivered, as well as a ROUTE session to which an SLS is being delivered.
- all service components delivered through a plurality of ROUTE sessions may be collected. This may be similarly applied when service components of a service are delivered through a plurality of MMTP sessions.
- one service component may be used simultaneously by a plurality of services.
- bootstrapping for ESG services may be performed by a broadcast network or broadband.
- URL information of the SLT may be utilized. ESG information and the like can be requested to this URL.
- one service component of one service may be delivered to the broadcasting network and one to the broadband (hybrid).
- the S-TSID may describe components delivered to a broadcasting network, so that a ROUTE client may acquire desired service components.
- USBD also has base pattern information, which allows you to describe which segments (which components) are to be routed to which path. Therefore, the receiver can use this to know what segment to request to the broadband server and what segment to find in the broadcast stream.
- scalable coding for a service may be performed.
- the USBD may have all the capability information needed to render the service. For example, when a service is provided in HD or UHD, the capability information of the USBD may have a value of “HD or UHD”.
- the receiver may know which component should be played in order to render the UHD or HD service using the MPD.
- app components to be used for app-based enhancement / app-based service may be delivered through a broadcast network or through broadband as an NRT component.
- app signaling for app-based enhancement may be performed by an application signaling table (AST) delivered with SLS.
- an event which is a signaling of an operation to be performed by the app, may be delivered in the form of an event message table (EMT) with SLS, signaled in an MPD, or in-band signaled in a box in a DASH representation. . AST, EMT, etc. may be delivered via broadband.
- App-based enhancement may be provided using the collected app components and such signaling information.
- a CAP message may be included in the aforementioned LLS table for emergency alerting. Rich media content for emergency alerts may also be provided. Rich media may be signaled by the CAP message, and if rich media is present it may be provided as an EAS service signaled by the SLT.
- the linear service components may be delivered through a broadcasting network according to the MMT protocol.
- NRT data for example, an app component
- data on the service may be delivered through a broadcasting network according to the ROUTE protocol.
- data on the service may be delivered through broadband.
- the receiver can access the MMTP session carrying the SLS using the bootstrap information of the SLT.
- the USBD of the SLS according to the MMT may refer to the MP table so that the receiver may acquire linear service components formatted with the MPU delivered according to the MMT protocol.
- the USBD may further refer to the S-TSID to allow the receiver to obtain NRT data delivered according to the ROUTE protocol.
- the USBD may further reference the MPD to provide a playback description for the data delivered over the broadband.
- the receiver may transmit location URL information for obtaining a streaming component and / or a file content item (such as a file) to the companion device through a method such as a web socket.
- An application of a companion device may request the component, data, and the like by requesting the URL through an HTTP GET.
- the receiver may transmit information such as system time information and emergency alert information to the companion device.
- FIG. 8 is a diagram illustrating processing of data in a link layer, according to an embodiment of the present invention.
- the link layer may correspond to a protocol for processing data between the physical layer and the network layer.
- the information on each layer may refer to the OSI 7 layer model.
- the processing of data at the link layer at the transmitting side may include processing data transferred from the network layer (upper layer of the physical layer) and transferring the data to the physical layer.
- processing of data at the link layer may include processing data from the physical layer and delivering it to the network layer.
- the purpose of processing data at the link layer is to process packets input at the upper layer in a single format in a form that can be processed at the physical layer.
- the purpose of the processing of data in the link layer is to secure the broadcast system with a determinism and flexibility to handle the types of input packets from higher layers, which have not yet been defined but can be defined later.
- the purpose of the data processing in the link layer is to process the data so that input data (input packets-packets transmitted from the upper layer of the link layer to the link layer on the sender's basis) can be efficiently transmitted.
- processing of data at the link layer may include compressing or removing redundant information in the header of the input packets.
- a process processed in a link layer defined in the present broadcasting system may be referred to as an ATSC link layer protocol (ALP, hereinafter referred to as a link layer protocol), and packets including data processed through ALP may be ALP packets. Can be named.
- ALP ATSC link layer protocol
- ALP packets including data processed through ALP may be ALP packets. Can be named.
- an upper layer of the link layer may deliver IP, MPEG2-TS and / or other types of packets to the link layer.
- the link layer may process the data and / or packets carried in the upper layer as an ALP packet (link layer packet).
- ALP packet signaling information including data (hereinafter, referred to as media data) used for the presentation of a service and / or content and information necessary to properly obtain these data may be generated through processing at the link layer.
- the ALP packet may include media data and / or signaling information.
- the ALP packet may be generated in a form that can be processed at the physical layer. Therefore, even if data / packets conforming to any protocol are transmitted in the upper layer of the link layer, the broadcast system may transmit the data / packets from the transmitting side to the receiving side through the physical layer.
- the broadcast system receives a service signal (broadcast signal and / or broadband signal) at a physical layer and extracts one or more ALP packets including media data and / or signaling information.
- a service signal broadcast signal and / or broadband signal
- the broadcast system may restore data and / or packets of an upper layer of the link layer as a reverse process of the data processing performed at the transmitting side.
- the broadcast system may process data and / or packets according to a higher layer protocol to provide a service and / or content to a viewer.
- the processing at the link layer may include the aforementioned overhead reduction, IP overhead removal, MPEG2-TS overhead removal, packet encapsulation, concatenation and / or segmentation. It may include some or all of the processes.
- FIG 9 illustrates a structure and an interface of an ALP according to an embodiment of the present invention.
- the ALP processes network layer packets such as IPv4 and MPEG2-TS as input packets.
- IPv4 is a protocol mainly used in communication environment
- MPEG2-TS is a protocol mainly used in broadcasting environment.
- a packet that can be processed by the link layer may provide scalability and flexibility to process packets according to other third protocols as well as packets according to the above two protocols.
- the ALP can identify signaling and packets for link layer signaling.
- the link layer signaling may include information for mapping between a specific channel or multicast (which may be defined as a set of data provided by a broadcast system for a range of purposes) and a physical layer.
- the link layer signaling may include information necessary for recovering at the receiving side the aforementioned overhead-removed (or compressed) packets.
- FIG. 10 illustrates a format of a link layer packet according to an embodiment of the present invention.
- the link layer packet may include a header and a payload (payload including data).
- the header of the link layer packet may include a base header, an additional header, and / or an optional header.
- the additional header may or may not be included in the header of the link layer packet, depending on the control fields (informations) included in the base header.
- the presence of an optional header can be indicated by the flag field (information) of the additional header.
- a field indicating the presence of an additional header and an optional header may be located in the base header.
- FIG. 11 illustrates a base header structure of a link layer packet according to an embodiment of the present invention.
- the structure of the header will be described.
- the structure of the base header will be described.
- the base header for link layer packet encapsulation has a hierarchical structure.
- the base header may have a length of 2 bytes and is the minimum length of the link layer packet header.
- the base header according to the embodiment of the present invention shown may include a Packet_Type field, a PC field, and / or a length field. According to an embodiment, the base header may further include an HM field or an S / C field.
- the position of each field included in the base header is as shown in the figure, and the position of each field may be changed in the base header or the entire header.
- FIG. 12 is a diagram illustrating syntax of a header of a link layer packet according to an embodiment of the present invention.
- the header of a link layer packet includes a Packet_Type field, a Payload_Configuration (PC) field, a Header_Mode (HM) field, a Segmentation_Concatenation (S / C) field, a length field, an additional header for a single packet (Additional_Header_For_Single_Packet), and an additional header for segmentation. It may include a header (Additional_Header_For_Segmentation_Packet) and / or an additional header (Additional_Header_For_Concatenation_Packet) for combining.
- the Packet_Type field is a 3-bit field indicating the original protocol or the packet type of input data before encapsulation into a link layer packet.
- IPv4 packets, compressed IP packets, link layer signaling packets, and other types of packets have this base header structure and can be encapsulated.
- the MPEG-2 TS packet may have another special structure and may be encapsulated. If the value of Packet_Type is "000", the original data type "001" "100" or "111" of the ALP packet is one of an IPv4 packet, a compressed IP packet, a link layer signaling or an extension packet. If the MPEG-2 TS packet is encapsulated, the value of Packet_Type may be "010". The values of other Packet_Type fields may be reserved for future use.
- the Payload_Configuration (PC) field may be a 1-bit field indicating the configuration of the payload.
- a value of 0 may indicate that the link layer packet carries one full input packet and the next field is Header_Mode.
- a value of 1 may indicate that the link layer packet carries one or more input packets (chains) or a portion of a large input packet (segmentation) and the next field is Segmentation_Concatenation.
- the Header_Mode (HM) field may be a 1-bit field indicating that there is no additional header and indicating that the length of the payload of the link layer packet is less than 2048 bytes. This value may vary depending on the embodiment. A value of 1 may indicate that an additional header for one packet defined below exists after the length field. In this case, the payload length is greater than 2047 bytes and / or optional features may be used (sub stream identification, header extension, etc.). This value may vary depending on the embodiment. This field may be present only when the Payload_Configuration field of the link layer packet has a value of zero.
- the Segmentation_Concatenation (S / C) field may be a 1-bit field indicating that the payload carries a segment of the input packet and that an additional header for segmentation defined below exists after the length field.
- a value of 1 may indicate that the payload carries more than one complete input packet and that an additional header for concatenation defined below exists after the length field. This field may be present only when the value of the Payload_Configuration field of the ALP packet is 1.
- the length field may be an 11-bit field indicating 11 LSBs (least significant bits) of the length in bytes of the payload carried by the link layer packet. If there is a Length_MSB field in the next additional header, the length field is concatenated to the Length_MSB field and becomes the LSB to provide the actual total length of the payload. The number of bits in the length field may be changed to other bits in addition to 11 bits.
- Additional_Header_For_Segmentation_Packet for partitioning and / or the additional header (Additional_Header_For_Concatenation_Packet) for combining will be replaced with the following description.
- a packet may correspond to the following packet structure type. That is, one packet without a single header (single packet), one packet with an additional header, a divided packet, and a concatenated packet are possible. According to an embodiment, more packet configurations may be possible by combining each additional header and optional header, an additional header for signaling information to be described later, and an additional header for type extension.
- FIG. 13 is a diagram illustrating the structure and syntax of an additional header for a single packet according to an embodiment of the present invention.
- Additional headers may be of various types. Hereinafter, an additional header for a single packet will be described.
- Header_Mode (HM) "1".
- Header_Mode (HM) may be set to one.
- the additional header for a single packet may include a Length_MSB field, a Sub-stream Identifier Flag (SIF) field, a HEF field, an SID field, and / or an Header_Extension.
- SIF Sub-stream Identifier Flag
- the Length_MSB field may be a 5-bit field that may indicate the most significant bits (MSBs) of the total payload length in bytes in the current link layer packet, and is concatenated into a length field containing 11 LSBs to obtain the total payload length. .
- MSBs most significant bits
- the number of bits in the length field may be changed to other bits in addition to 11 bits.
- the length_MSB field may also change the number of bits, and thus the maximum representable payload length may also change.
- each length field may indicate the length of the entire link layer packet, not the payload.
- the Sub-stream Identifier Flag (SIF) field may be a 1-bit field that may indicate whether a sub-stream ID (SID) exists after the header extension flag (HEF) field. If there is no SID in the link layer packet, the SIF field may be set to zero. If there is an SID after the HEF field in the link layer packet, the SIF may be set to one. Details of the SID will be described later.
- the HEF field may be a 1-bit field that may indicate that a header exists for later expansion. A value of 0 can indicate that this extension header does not exist.
- the SID field may be an 8-bit field that may indicate a sub stream identifier for the link layer packet.
- the SID field may be used to filter a particular packet stream at the link layer level.
- the SID field may identify a substream including link layer packets transmitting a specific multicast.
- the mapping between the substreams and the values of the SID field may be included in link layer signaling and / or signaling information of a higher layer (eg, SLT and / or SLS).
- the SID field may serve as a service identifier. If there is an optional header extension, the SID is between the additional header and the optional header extension.
- the SID field may be included in link layer signaling.
- the extension header may include information for extensibility of the additional header.
- the extension header may include an Extension_Type field, an Extension_Length field, and / or an Extension_Byte element.
- the Extension_Type field may be an 8-bit field that may indicate the type of Header_Extension ().
- the Extension_Length field may be an 8-bit field that may indicate the byte length of Header Extension () counting from the next byte to the last byte of Header_Extension ().
- the Extension_Byte element may be a byte indicating the value of Header_Extension ().
- FIG. 14 illustrates a structure and syntax of an additional header of a link layer packet in case of segmentation according to an embodiment of the present invention.
- Segmentation_Concatenation (S / C) “ 0 ", there may be an additional header (hereinafter, additional header for segmentation) for the link layer packet in case of segmentation.
- the additional header for splitting may include a Segment_Sequence_Number field, a Last_Segment_Indicator (LSI) field, a Sub-stream Identifier Flag (SIF) field, a HEF field, an SID field, and / or an extension header.
- LSI Last_Segment_Indicator
- SIF Sub-stream Identifier Flag
- Segment_Sequence_Number may be a 5-bit unsigned integer that may indicate the order of the corresponding segment carried by the link layer packet. For a link layer packet carrying the first segment of the input packet, the value of this field may be set to 0x0. This field may be incremented by one for each additional segment belonging to the input packet to be split.
- the LSI may be a 1-bit field that may indicate that the partition in the payload is the end of the input packet. A value of zero can indicate that it is not the last partition.
- the Sub-stream Identifier Flag may be a 1-bit field that may indicate whether the SID exists after the HEF field. If there is no SID in the link layer packet, the SIF field may be set to zero. If there is an SID after the HEF field in the link layer packet, the SIF may be set to one.
- the HEF field may be a 1-bit field that may indicate that there is an optional header extension after the additional header for later expansion of the link layer header.
- a value of 0 can indicate that there is no optional header extension.
- a packet ID field indicating that each divided segment is generated from the same input packet may be added. This field may not be necessary if the segmented segments are transmitted in order.
- 15 is a diagram illustrating the structure and syntax of an additional header of a link layer packet in the case of concatenation according to an embodiment of the present invention.
- the additional header for combining may include a Length_MSB field, a Count field, a HEF field, a Component_Length field, and / or a confirmation header.
- the Length_MSB field may be a 4-bit field that may indicate the MSB bit of the payload length in bytes in the corresponding link layer packet.
- the maximum length of the payload is 32767 bytes for concatenation. As described above, the detailed values may be changed.
- the Count field may be a field that may indicate the number of packets (input packets) included in the link layer packet. 2 corresponding to the number of packets included in the link layer packet may be set in the corresponding field. Therefore, the maximum value of concatenated packets in the link layer packet is nine.
- the way in which the Count field indicates the number may vary from embodiment to embodiment. That is, the number from 1 to 8 may be indicated.
- the HEF field may be a 1-bit field that may indicate that an optional header extension exists after an additional header for future extension of the link layer header. A value of 0 can indicate that no extension header exists.
- the Component_Length field may be a 12-bit field that may indicate the length in bytes of each packet.
- the Component_Length field is included in the same order as the packets present in the payload except for the last component packet.
- the number of length fields may be represented by (Count + 1). In some embodiments, there may be the same number of length fields as the value of the Count field.
- four stuffing bits may follow the last Component_Length field. These bits can be set to zero.
- the Component_Length field indicating the length of the last concatenated input packet may not exist. In this case, the length of the last concatenated input packet may be indicated as the length obtained by subtracting the sum of the values indicated by each Component_length field from the total payload length.
- the aforementioned SID field and / or extension header may be included in the link layer packet in the form of an optional null header.
- 16 is a diagram illustrating syntax of a link layer packet including link layer signaling and an additional header included therein according to an embodiment of the present invention.
- link layer signaling is included in a link layer packet is as follows.
- the signaling packet is identified when the Packet_Type field of the base header is equal to 100.
- the link layer packet may include two additional portions of an additional header for signaling information and actual signaling data itself.
- the total length of the link layer signaling packet is indicated in the link layer packet header.
- the additional header for signaling information may include the following fields. In some embodiments, some fields may be omitted.
- Signaling_Type may be an 8-bit field that may indicate the type of signaling.
- Signaling_Type_Extension may be a 16-bit field that may indicate an attribute of signaling. Details of this field may be defined in the signaling specification.
- Signaling_Version may be an 8-bit field that may indicate the version of signaling.
- Signaling_Format may be a 2-bit field that may indicate a data format of signaling data.
- the signaling format may mean a data format such as binary, XML, ATSC's own format, table, or descriptor.
- Signaling_Encoding_Type may be a field indicating an encoding / compression format. This field may indicate whether compression has not been performed or what specific compression has been performed. This field may indicate whether encoding has been performed on signaling information (signaling data) in a manner such as gzip, zip, or DEPLATE according to the value.
- FIG. 17 is a diagram illustrating syntax of a link layer packet including an extended type packet (input packet) and an additional header included therein according to an embodiment of the present invention.
- Additional headers may be defined to provide a mechanism that allows for the near unlimited number of packet types and additional protocols carried by the link layer later.
- Packet_type is 111 in the base header
- packet type extension may be used.
- the figure shows the structure of a link layer packet including an additional header for type extension to a link layer packet containing an input packet using a protocol different from that described above, which can be added later.
- the additional header for type extension may include the following fields. In some embodiments, some fields may be omitted.
- the extended_type field may be information indicating a protocol or packet type of an input encapsulated in a link layer packet as a payload. This field may not be used for all protocols or packet types already defined by the Packet_Type field.
- FIG. 18 is a diagram illustrating syntax of a link layer packet including an MPEG2-TS packet and a header of a link layer packet according to an embodiment of the present invention.
- the link layer packet may include an MPEG2-TS packet.
- One or more TS packets may be encapsulated within each link layer packet.
- the number of TS packets may be signaled through the NUMTS field.
- a special link layer packet header format may be used.
- the link layer provides an overhead reduction mechanism for MPEG-2 TS to improve transmission efficiency.
- the sync byte (0x47) of each TS packet may be deleted.
- the option to delete null packets and similar TS headers is also provided.
- the deleted null packet may be recovered at the receiver side using the DNP field.
- the DNP field indicates the count of deleted null packets. The null packet deletion mechanism using the DNP field is described below.
- CC continuity counter
- other header fields are also the same, the header is transmitted once in the first packet and the other header is deleted.
- the HDM field may indicate whether the header has been deleted. The detailed procedure of common TS header deletion is described below.
- the CC field may be included in the header of the MPEG2-TS packet and is information indicating a sequence number of payloads of the TS packets within a range of the stream.
- overhead reduction may be performed in the following order: sink removal, null packet deletion, common header deletion. According to an embodiment, the order in which each mechanism is performed may be changed. In addition, some mechanisms may be omitted in some embodiments.
- the header of a link layer packet is shown when using MPEG-2 TS packet encapsulation.
- the header of the link layer packet may be a Packet_Type field, a Number of TS packets (NUMTS) field, an additional header flag (AHF) field, a header deletion mode (HDM) field, and / or a DNP. (deleted null packets) field.
- Packet_Type may be a 3-bit field that may indicate a protocol type of an input packet as described above. For MPEG-2 TS packet encapsulation, this field may be set to 010.
- An additional header flag may be a field that may indicate whether an additional header exists. A value of zero indicates that no additional header is present. A value of 1 indicates that an additional header of length 1 byte exists after the base header. If a null TS packet is deleted or TS header compression is applied, this field may be set to one.
- the additional header for TS packet encapsulation consists of the following two fields and exists only when the value of AHF in the corresponding link layer packet is set to 1.
- the header deletion mode may be a 1-bit field indicating whether TS header deletion may be applied to the corresponding link layer packet. A value of 1 indicates that TS header deletion can be applied. A value of 0 indicates that the TS header deletion method is not applied to the link layer packet.
- the number of bits of each field described above may be changed, and the minimum / maximum value of the value indicated by the corresponding field may be changed according to the changed number of bits. This can be changed according to the designer's intention.
- the sync byte (0x47) may be deleted from the start of each TS packet during the processing of data in the link layer.
- the length of an MPEG2-TS packet encapsulated in the payload of a link layer packet can be 187 bytes (instead of the original 188 bytes).
- FIG. 19 illustrates a process of removing a null packet from MPEG2-TS packets according to an embodiment of the present invention.
- the transport stream rule requires that the bit rates at the output of the multiplexer of the transmitter and the input of the demultiplexer of the receiver are constant over time, and the end-to-end delay is also constant.
- null packets may be present to accommodate variable bitrate services in a constant bitlace stream.
- PID 0x1FFF
- a counter called DNP can be incremented for each dropped null packet, which is first reset to zero and then preceded the first non-null TS packet that will be encapsulated in the payload of the current link layer packet. have.
- a group of consecutive useful TS packets can then be encapsulated in the payload of the current link layer packet, and the value of each field in its header can be determined.
- the DNP is reset to zero. If the DNP reaches the highest allowance, if the next packet is also a null packet, that null packet remains a useful packet and is encapsulated in the payload of the next link layer packet.
- Each link layer packet may include at least one TS packet in its payload.
- the first link layer packet one null packet was removed before two useful TS packets were sent in the link layer packet.
- the packet following the useful TS packet included in the first link layer packet may be a null packet.
- the DNP counter may be reset to zero.
- the value of the NUMTS field may be set to '2', and the value of the DNP field may be set to '1'.
- the second link layer packet two null packets were removed before four useful TS packets.
- the NUMTS field of the second link layer packet may be set to '4' and the DNP field may be set to '2'.
- FIG. 20 illustrates a process of deleting a header from MPEG2-TS packets according to an embodiment of the present invention.
- TS packet header deletion may be referred to as TS packet header compression.
- the header of the TS packet is equal to one of the first packet. Sent once, and may be deleted in other headers.
- the aforementioned HDM field may indicate whether the header is deleted. When the header of the TS packet is deleted, the HDM may be set to one.
- three TS packets have the same header as the first TS packet (fields in the remaining headers except the CC field are the same header).
- the value of the NUMTS field included in the link layer packet may be set to '4'
- the value of the HDM field may be set to '1'
- the value of the DNP field may be set to '0'.
- the value of the AHF field may be set to '1'.
- 21 is a diagram illustrating a single packet encapsulation structure of a link layer according to an embodiment of the present invention.
- the short packet may include a Packet_Type field, a PC field, an HM field, a Length field, and / or a payload. Description of these is as described above.
- the long packet may include a Packet_Type field, a PC field, an HM field, a Length field, a Length_MSB field, an R (Reserved) field, an SIF field, a HEF field, and / or a payload. Description of these is as described above.
- Long packets may include SID fields and / or optional headers.
- FIG. 22 is a diagram illustrating an encapsulation structure of a link layer packet to which segmentation is applied according to an embodiment of the present invention.
- the link layer packet may include a Packet_Type field, a PC field, an S / C field, a Length field, a Seg_SN field, an LSI field, an SIF field, an HEF field, and / or a payload. Description of these is as described above.
- the link layer packet may include a Packet_Type field, a PC field, an S / C field, a Length field, a Seg_SN field, an LSI field, an SIF field, an HEF field, and / or a payload. Description of these is as described above.
- the link layer packet may include a Packet_Type field, a PC field, an S / C field, a Length field, a Seg_SN field, an LSI field, an SIF field, an HEF field, and / or a payload. Description of these is as described above.
- FIG. 23 is a diagram illustrating an encapsulation structure of a link layer packet to which concatenation is applied according to an embodiment of the present invention.
- a link layer packet including a plurality of input packets may include a Packet_Type field, a PC field, an S / C field, a Length field, a Length_MSB field, a Count field, a HEF field, and fields indicating the length of each input packet (L_1, L_2, ... L_n-1 field) and / or payload. Description of these is as described above.
- FIG. 24 illustrates a concept of encapsulation for an MPEG2-TS packet in a link layer according to an embodiment of the present invention.
- the link layer packet may include one or more MPEG2-TS packets, where a sync byte of the MPEG2-TS packet may not be included in the payload of the link layer packet.
- Each field value in the header of the above-described link layer packet is set to generate a header of the link layer packet.
- the value of the Packet_Type field may be set to '010'
- the value of the NUMTS field may be set to '1000'
- the value of the AHF field may be set to '0'.
- the link layer processing makes it possible to reduce the amount of transmission of 7 bytes rather than directly transmitting eight MPEG2-TS packets to the physical layer.
- FIG. 25 is a diagram illustrating the concept of encapsulation for MPEG2-TS packets in the link layer, using null packet cancellation, according to an embodiment of the present invention.
- Processing at the link layer may include removing null MPEG2-TS packets existing prior to the first MPEG2-TS packet included in the link layer packet.
- the transmitting side can inform the receiving side of the number of null MPEG2-TS packets removed.
- the link layer packet includes six MPEG2-TS packets, and two null MPEG2-TS packets preceding the first MEGG2-TS packet in the payload of the link layer packet, is deleted.
- the broadcast system For null packet removal, the broadcast system removes null packets from the incoming packets and counts the number of null packets removed. The broadcast system removes sync bytes contained in MPEG2-TS packets. The broadcast system includes six MPEG2-TS packets in the payload of the link layer packet. The broadcast system generates a header of a link layer packet according to the present embodiment.
- the value of the Packet_Type field included in the header may be set to '010', the value of the NUMTS field may be set to '0110', and the value of the AHF field is set to '1'.
- the corresponding MPEG2-TS packets may be properly processed by the broadcasting system. Has the effect of being able to.
- FIG. 26 illustrates a concept of encapsulation for MPEG2-TS packets in a link layer using TS header removal according to an embodiment of the present invention.
- the link layer may perform additional compression on the header of MPEG2-TS packets to generate link layer packets.
- headers of eight MPEG2-TS packets may include fields having the same value, except for the CC field.
- the process of the broadcast system compressing the header of MPEG2-TS in the link layer may include the following process.
- the broadcast system may group eight TS packets, the number of which may be changed, including headers having values of the same fields except for the CC field.
- the broadcast system may keep the header of the first MPEG2-TS packet, except for the sync byte, and remove the headers for the remaining seven MPEG2-TS packets.
- the broadcast system may generate a header of a link layer packet.
- the value of the Packet_Type field included in the header of the link layer packet may be set to '010', the value of the NUMTS field may be set to '0100', the value of the AHF field may be set to '1', The value of the HCM field may be set to '1' and the value of the DNP field may be set to '0000000'.
- the broadcast system may generate a link layer packet including a portion of the eight MPEG2-TS packets (the remaining portion after the header compression is performed).
- the generated link layer packet may have a length of 1477 bytes, which is 27 bytes less than when eight MPEG2-TS packets are sent directly through the physical layer. Therefore, according to the present embodiment, the amount of data transmitted by the broadcast system can be reduced.
- FIG. 27 is a diagram illustrating a transmission path for a context when header compression is performed on an IP packet in a link layer according to an embodiment of the present invention.
- IP header compression may be performed to reduce the amount of data transmitted through the broadcast system.
- the context (or context information) generated in this process may be transmitted from the transmitting side to the receiving side through a path separate from the IP packets on which the header compression is performed.
- the context is transmitted through a path separate from the IP packets on which the header compression is performed, and the receiver acquires the context in the corresponding path at the time of channel change or power-on, and immediately obtains the IP packet. It has the effect of restoring.
- the path through which the context is transmitted may be a path through which signaling information is transmitted.
- the PLP may transmit a context.
- the path for transmitting the context may be specified in advance, and the receiving side may directly access the path to receive the context.
- the same context may be transmitted repeatedly, at regular or non-uniform periods. This is because the channel change or power-on time may be different for each receiver, so that the context can be obtained immediately at that time.
- FIG. 28 is a diagram illustrating a process of acquiring a context in a receiver according to an embodiment of the present invention.
- the receiver may first acquire signaling information. That is, the receiver may acquire the context transmitted to the corresponding PLP in the process of obtaining the signaling information by accessing the PLP (or DP) that transmits the signaling information. After obtaining the signaling information, the receiver may select a PLP for obtaining a stream for transmitting IP packets. In this process, the receiver may acquire the context before obtaining the stream for transmitting the IP packets.
- the adaptation module of the receiver may detect the IR-DYN packet from the received packet flow (set of IP packets). The adaptation module can parse the static chain included in the context. This process is similar to the process of obtaining an IR packet. IR-DYN packets having the same context identifier may be restored to IR packets. The recovered RoHC packet flow may be transmitted to the RoHC recovery unit and restored to the IP packet.
- 29 is a flowchart illustrating a method of generating and processing a broadcast signal according to an embodiment of the present invention.
- the transmitter receives at least one or more packets of Internet Protocol (IP) packets and MPEG2-TS packets as input packets (JS29010).
- IP Internet Protocol
- MPEG2-TS packets as input packets (JS29010).
- the transmitter generates one or more link layer packets including the received input packets (JS29020).
- the transmitter removes null packets of the MPEG2-TS packets and sync bits included in the MPEG2-TS packets from which the null packets are removed.
- the transmitter generates a broadcast signal including the one or more link layer packets (JS29030).
- the transmitter transmits the broadcast signal (JS29040).
- a header of the link layer packet includes Packet_Type information for identifying a type of an input packet included in a payload of the link layer packet, and the synchronization included in the payload of the link layer packet. It may include NUMTS information indicating the number of MPEG2-TS packets from which bytes have been removed.
- the link layer packet header may further include DNP information indicating the number of the removed null packets.
- the MPEG2-TS packets include a first MPEG2-TS packet, a second MPEG2-TS packet, and a third MPEG2-TS packet, wherein the first MPEG2-TS packet includes: A first MPEG2-TS packet header and a first MPEG2-TS packet payload, wherein the second MPEG2-TS packet includes a second MPEG2-TS packet header and a second MPEG2-TS packet payload;
- the 3 MPEG2-TS packet includes a third MPEG2-TS packet header and a third MPEG2-TS packet payload, and generating the one or more link layer packets comprises: the second MPEG2-TS packet header and a third If the MPEG2-TS packet header includes fields having the same value as other fields except for the value of the continuity counter (CC) field included in the first MPEG2-TS packet header, the second MPEG2-TS packet Deleting the header and the third MPEG2-TS packet header, and the first MPEG2-TS packet header, the first MPEG2-TS packet.
- the header of the link layer packet may include HDM information indicating that a process of deleting the second MPEG2-TS packet header and the third MPEG2-TS packet header has been performed.
- the generating of the one or more link layer packets may include generating link layer signaling information including information for processing the link layer packet and generating the generated link layer signaling information.
- the method may further include generating a link layer signaling packet.
- the link layer signaling packet includes signaling type information for identifying a type of the link layer signaling information included in the link layer signaling packet, and signaling version information indicating a version of the link layer signaling information. It may include signaling format information for identifying a data format of the link layer signaling information and signaling encoding type information for identifying an encoding format applied to the data of the link layer signaling information.
- FIG. 30 is a diagram illustrating a broadcast system according to an embodiment of the present invention.
- the broadcast system includes a transmitter J30100 and / or a receiver J30200.
- the transmitter J30100 may include a data generator J30110, a processor J30120, a broadcast signal generator J30130, and / or a broadcast signal transmitter J30140.
- the data generator J30110 generates data for broadcast content provided by the broadcast system.
- the processor J30120 receives at least one or more packets of Internet Protocol (IP) packets and MPEG2-TS packets as input packets, and generates one or more link layer packets including the received input packets.
- IP Internet Protocol
- the processor J30120 removes null packets of MPEG2-TS packets, removes a sync byte included in MPEG2-TS packets from which null packets have been removed, and removes a link layer packet. And generating a link layer packet including a payload of a link layer packet including MPEG2-TS packets from which a header and a sync byte have been removed.
- the processor J30120 may include a signaling encoder (not shown), which encodes or generates the aforementioned signaling information.
- the signaling information includes low level signaling, service list table, service layer signaling, MPD, MP table, copy control information and / or metadata of ISOBMFF, as described above.
- the broadcast signal generator J30130 generates a broadcast signal including one or more link layer packets.
- the broadcast signal transmitter J30140 transmits a broadcast signal.
- the receiver J43200 includes a signal receiver J43210, a processor J43220, and / or a display unit J43230.
- the signal receiver J30210 receives a broadcast signal or a broadband signal.
- Processor J30220 is responsible for processing the IP packets and / or MPEG2-TS packets corresponding to the processing at the link layer described above, applied to IP packets and / or MPEG2-TS packets, which may be included in link layer packets. Restore That is, when header compression is performed on the IP packets included in the link layer packets, the processor J30220 restores the compressed header to restore the form of an input packet input to the link layer on the transmitting side. The processor J30220 restores the compressed header, null packet recovery and / or sync byte recovery when header compression, null packet removal, and / or sync byte removal has been performed on MPEG2-TS packets included in link layer packets.
- the processor J30220 may decode the signaling information.
- the processor J30220 processes the signaling information and the data constituting the broadcast content, and decodes the data into data for presentation of the media.
- the display unit J30230 expresses the media using the decoded data.
- the module or unit may be processors that execute successive procedures stored in a memory (or storage unit). 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.
- Apparatus and method according to the present invention is not limited to the configuration and method of the embodiments described as described above, the above-described embodiments may be selectively all or part of each embodiment so that various modifications can be made It may be configured in combination.
- the processor-readable recording medium includes all kinds of recording devices that store data that can be read by the processor.
- Examples of the processor-readable recording medium include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like, and may also be implemented in the form of a carrier wave such as transmission over the Internet.
- the processor-readable recording medium can also be distributed over network coupled computer systems so that the processor-readable code is stored and executed in a distributed fashion.
- the present invention is used in the field of providing a series of broadcast signals.
Abstract
Description
Claims (14)
- IP (Internet Protocol) 패킷들 및 MPEG2-TS 패킷들 중 적어도 하나 이상의 패킷들을 입력 패킷들로 수신하는 단계;상기 수신한 입력 패킷들을 포함하는 하나 이상의 링크 계층 패킷들을 생성하는 단계,여기서, 상기 하나 이상의 링크 계층 패킷들을 생성하는 단계는,상기 MPEG2-TS 패킷들 중 널 (null) 패킷들을 제거하는 단계;상기 널 패킷들이 제거된 MPEG2-TS 패킷들에 포함되는 동기 바이트 (sync byte)를 제거하는 단계; 및상기 링크 계층 패킷의 헤더 (header) 및 상기 동기 바이트가 제거된 MPEG2-TS 패킷들을 포함하는 링크 계층 패킷의 페이로드 (payload)를 포함하는 링크 계층 패킷을 생성하는 단계; 를 포함하며;상기 하나 이상의 링크 계층 패킷들을 포함하는 방송 신호를 생성하는 단계; 및상기 방송 신호를 전송하는 단계;를 포함하는 방송 신호 생성 처리 방법.
- 제 1 항에 있어서, 상기 링크 계층 패킷의 헤더는,상기 링크 계층 패킷의 페이로드에 포함되는 입력 패킷의 타입을 식별하는 Packet_Type 정보, 및상기 링크 계층 패킷의 페이로드에 포함되는 상기 동기 바이트가 제거된 MPEG2-TS 패킷들의 개수를 나타내는 NUMTS 정보,를 포함하는 특징으로 하는 방송 신호 생성 처리 방법.
- 제 2 항에 있어서, 상기 링크 계층 패킷의 헤더는,상기 제거된 널 패킷들의 개수를 나타내는 DNP 정보,를 더 포함하는 것을 특징으로 하는 방송 신호 생성 처리 방법.
- 제 1 항에 있어서,상기 MPEG2-TS 패킷들은, 제 1 MPEG2-TS 패킷, 제 2 MPEG2-TS 패킷 및 제 3 MPEG2-TS 패킷을 포함하고,상기 제 1 MPEG2-TS 패킷은, 제 1 MPEG2-TS 패킷 헤더 및 제 1 MPEG2-TS 패킷 페이로드를 포함하고,상기 제 2 MPEG2-TS 패킷은, 제 2 MPEG2-TS 패킷 헤더 및 제 2 MPEG2-TS 패킷 페이로드를 포함하고,상기 제 3 MPEG2-TS 패킷은, 제 3 MPEG2-TS 패킷 헤더 및 제 3 MPEG2-TS 패킷 페이로드를 포함하고,상기 하나 이상의 링크 계층 패킷들을 생성하는 단계는,상기 제 2 MPEG2-TS 패킷 헤더 및 제 3 MPEG2-TS 패킷 헤더가, 상기 제 1 MPEG2-TS 패킷 헤더에 포함되는, CC (continuity counter) 필드의 값을 제외한 다른 필드들과 동일한 값을 가지는 필드들을 포함하는 경우, 상기 제 2 MPEG2-TS 패킷 헤더 및 제 3 MPEG2-TS 패킷 헤더를 삭제하는 단계; 및상기 제 1 MPEG2-TS 패킷 헤더, 제 1 MPEG2-TS 패킷 페이로드, 제 2 MPEG2-TS 패킷 페이로드 및 제 3 MPEG2-TS 패킷 페이로드를 포함하는 링크 계층 패킷의 페이로드 및 상기 링크 계층 패킷의 헤더를 포함하는 링크 계층 패킷을 생성하는 단계;를 포함하는 것을 특징으로 하는 방송 신호 생성 처리 방법.
- 제 4 항에 있어서, 상기 링크 계층 패킷의 헤더는,상기 상기 제 2 MPEG2-TS 패킷 헤더 및 제 3 MPEG2-TS 패킷 헤더를 삭제하는 과정이 수행되었음을 나타내는 HDM 정보,를 포함하는 것을 특징으로 하는 방송 신호 생성 처리 방법.
- 제 1 항에 있어서, 상기 하나 이상의 링크 계층 패킷들을 생성하는 단계는,상기 링크 계층 패킷을 처리하기 위한 정보를 포함하는 링크 계층 시그널링 정보를 생성하는 단계; 및상기 생성된 링크 계층 시그널링 정보를 포함하는 링크 계층 시그널링 패킷을 생성하는 단계;를 더 포함하는 방송 신호 생성 처리 방법.
- 제 6 항에 있어서, 상기 링크 계층 시그널링 패킷은,상기 링크 계층 시그널링 패킷에 포함되는 상기 링크 계층 시그널링 정보의 타입을 식별하는 시그널링 타입 정보,상기 링크 계층 시그널링 정보의 버전을 나타내는 시그널링 버전 정보,상기 링크 계층 시그널링 정보의 데이터 포맷을 식별하는 시그널링 포맷 정보, 및상기 링크 계층 시그널링 정보의 데이터에 적용되는 인코딩 포맷을 식별하는 시그널링 인코딩 타입 정보,를 포함하는 것을 특징으로 하는 방송 신호 생성 처리 방법.
- IP (Internet Protocol) 패킷들 및 MPEG2-TS 패킷들 중 적어도 하나 이상의 패킷들을 입력 패킷들로 수신하고, 상기 수신한 입력 패킷들을 포함하는 하나 이상의 링크 계층 패킷들을 생성하는 프로세서,여기서, 상기 프로세서는,상기 MPEG2-TS 패킷들 중 널 (null) 패킷들을 제거하고,상기 널 패킷들이 제거된 MPEG2-TS 패킷들에 포함되는 동기 바이트 (sync byte)를 제거하고,상기 링크 계층 패킷의 헤더 (header) 및 상기 동기 바이트가 제거된 MPEG2-TS 패킷들을 포함하는 링크 계층 패킷의 페이로드 (payload)를 포함하는 링크 계층 패킷을 생성하는 것을 특징으로 하며;상기 하나 이상의 링크 계층 패킷들을 포함하는 방송 신호를 생성하는 방송 신호 생성 장치; 및상기 방송 신호를 전송하는 방송 신호 전송 장치;를 포함하는 방송 신호 송신기.
- 제 8 항에 있어서, 상기 링크 계층 패킷의 헤더는,상기 링크 계층 패킷의 페이로드에 포함되는 입력 패킷의 타입을 식별하는 Packet_Type 정보, 및상기 링크 계층 패킷의 페이로드에 포함되는 상기 동기 바이트가 제거된 MPEG2-TS 패킷들의 개수를 나타내는 NUMTS 정보,를 포함하는 특징으로 하는 방송 신호 송신기.
- 제 9 항에 있어서, 상기 링크 계층 패킷의 헤더는,상기 제거된 널 패킷들의 개수를 나타내는 DNP 정보,를 더 포함하는 것을 특징으로 하는 방송 신호 송신기.
- 제 8 항에 있어서,상기 MPEG2-TS 패킷들은, 제 1 MPEG2-TS 패킷, 제 2 MPEG2-TS 패킷 및 제 3 MPEG2-TS 패킷을 포함하고,상기 제 1 MPEG2-TS 패킷은, 제 1 MPEG2-TS 패킷 헤더 및 제 1 MPEG2-TS 패킷 페이로드를 포함하고,상기 제 2 MPEG2-TS 패킷은, 제 2 MPEG2-TS 패킷 헤더 및 제 2 MPEG2-TS 패킷 페이로드를 포함하고,상기 제 3 MPEG2-TS 패킷은, 제 3 MPEG2-TS 패킷 헤더 및 제 3 MPEG2-TS 패킷 페이로드를 포함하고,상기 프로세서는,,상기 제 2 MPEG2-TS 패킷 헤더 및 제 3 MPEG2-TS 패킷 헤더가, 상기 제 1 MPEG2-TS 패킷 헤더에 포함되는, CC (continuity counter) 필드의 값을 제외한 다른 필드들과 동일한 값을 가지는 필드들을 포함하는 경우, 상기 제 2 MPEG2-TS 패킷 헤더 및 제 3 MPEG2-TS 패킷 헤더를 삭제하고,상기 제 1 MPEG2-TS 패킷 헤더, 제 1 MPEG2-TS 패킷 페이로드, 제 2 MPEG2-TS 패킷 페이로드 및 제 3 MPEG2-TS 패킷 페이로드를 포함하는 링크 계층 패킷의 페이로드 및 상기 링크 계층 패킷의 헤더를 포함하는 링크 계층 패킷을 생성하는 것을 특징으로 하는 방송 신호 송신기.
- 제 11 항에 있어서, 상기 링크 계층 패킷의 헤더는,상기 상기 제 2 MPEG2-TS 패킷 헤더 및 제 3 MPEG2-TS 패킷 헤더를 삭제하는 과정이 수행되었음을 나타내는 HDM 정보,를 포함하는 것을 특징으로 하는 방송 신호 송신기.
- 제 8 항에 있어서, 상기 프로세서는,상기 링크 계층 패킷을 처리하기 위한 정보를 포함하는 링크 계층 시그널링 정보를 생성하고, 상기 생성된 링크 계층 시그널링 정보를 포함하는 링크 계층 시그널링 패킷을 생성하는 것을 특징으로 하는 방송 신호 송신기.
- 제 13 항에 있어서, 상기 링크 계층 시그널링 패킷은,상기 링크 계층 시그널링 패킷에 포함되는 상기 링크 계층 시그널링 정보의 타입을 식별하는 시그널링 타입 정보,상기 링크 계층 시그널링 정보의 버전을 나타내는 시그널링 버전 정보,상기 링크 계층 시그널링 정보의 데이터 포맷을 식별하는 시그널링 포맷 정보, 및상기 링크 계층 시그널링 정보의 데이터에 적용되는 인코딩 포맷을 식별하는 시그널링 인코딩 타입 정보,를 포함하는 것을 특징으로 하는 방송 신호 송신기.
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201680000833.5A CN106471813B (zh) | 2015-06-04 | 2016-06-03 | 发送广播信号的装置、接收广播信号的装置、发送广播信号的方法和接收广播信号的方法 |
US15/115,885 US10237196B2 (en) | 2015-06-04 | 2016-06-03 | Apparatus for transmitting broadcast signal, apparatus for receiving broadcast signal, method for transmitting broadcast signal and method for receiving broadcast signal |
EP16791293.0A EP3142369A4 (en) | 2015-06-04 | 2016-06-03 | Broadcast signal transmission apparatus, broadcast signal reception apparatus, broadcast signal transmission method, and broadcast signal reception method |
KR1020167018029A KR101792519B1 (ko) | 2015-06-04 | 2016-06-03 | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 |
US16/262,154 US10616124B2 (en) | 2015-06-04 | 2019-01-30 | Apparatus for transmitting broadcast signal, apparatus for receiving broadcast signal, method for transmitting broadcast signal and method for receiving broadcast signal |
US16/781,347 US10887242B2 (en) | 2015-06-04 | 2020-02-04 | Apparatus for transmitting broadcast signal, apparatus for receiving broadcast signal, method for transmitting broadcast signal and method for receiving broadcast signal |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201562171227P | 2015-06-04 | 2015-06-04 | |
US62/171,227 | 2015-06-04 | ||
US201562174534P | 2015-06-12 | 2015-06-12 | |
US62/174,534 | 2015-06-12 | ||
US201562180018P | 2015-06-15 | 2015-06-15 | |
US62/180,018 | 2015-06-15 |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/115,885 A-371-Of-International US10237196B2 (en) | 2015-06-04 | 2016-06-03 | Apparatus for transmitting broadcast signal, apparatus for receiving broadcast signal, method for transmitting broadcast signal and method for receiving broadcast signal |
US16/262,154 Continuation US10616124B2 (en) | 2015-06-04 | 2019-01-30 | Apparatus for transmitting broadcast signal, apparatus for receiving broadcast signal, method for transmitting broadcast signal and method for receiving broadcast signal |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016195412A1 true WO2016195412A1 (ko) | 2016-12-08 |
Family
ID=57441208
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2016/005901 WO2016195412A1 (ko) | 2015-06-04 | 2016-06-03 | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 |
Country Status (5)
Country | Link |
---|---|
US (3) | US10237196B2 (ko) |
EP (1) | EP3142369A4 (ko) |
KR (1) | KR101792519B1 (ko) |
CN (1) | CN106471813B (ko) |
WO (1) | WO2016195412A1 (ko) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108307204A (zh) * | 2017-01-13 | 2018-07-20 | 上海交通大学 | 一种基于多业务ts流的alp封装方法 |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2017026110A1 (en) * | 2015-08-07 | 2017-02-16 | Sharp Kabushiki Kaisha | Systems and methods for data transmission based on a link layer packet structure |
US11057605B2 (en) | 2018-11-05 | 2021-07-06 | Korea Electronics Technology Institute | 360-degree VR video segmentation transmission system and method |
KR102035148B1 (ko) * | 2018-11-05 | 2019-10-22 | 전자부품연구원 | 360 vr 영상 분할 전송 시스템 및 방법 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20080072019A (ko) * | 2005-12-01 | 2008-08-05 | 노키아 코포레이션 | 미디어 스트림의 타임쉬프트 프리젠테이션 |
US20090055417A1 (en) * | 2007-08-20 | 2009-02-26 | Nokia Corporation | Segmented metadata and indexes for streamed multimedia data |
KR20100028546A (ko) * | 2007-05-04 | 2010-03-12 | 노키아 코포레이션 | 멀티미디어 컨테이너 파일의 수신 힌트 트랙으로의 미디어 스트림 기록 |
WO2010082768A2 (ko) * | 2009-01-14 | 2010-07-22 | 엘지전자 주식회사 | 효율적인 mac 헤더 설계 및 이를 이용한 통신 |
WO2012011722A2 (ko) * | 2010-07-19 | 2012-01-26 | 엘지전자 주식회사 | 미디어 송수신 방법 및 그를 이용한 송수신 장치 |
Family Cites Families (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2002141945A (ja) * | 2000-11-06 | 2002-05-17 | Sony Corp | データ送信装置、およびデータ送信方法、並びにプログラム記憶媒体 |
JP3757857B2 (ja) * | 2001-12-12 | 2006-03-22 | ソニー株式会社 | データ通信システム、データ送信装置、データ受信装置、および方法、並びにコンピュータ・プログラム |
JP2006211602A (ja) * | 2005-01-31 | 2006-08-10 | Toshiba Corp | データ送信機及びプログラム |
EP2053821B1 (en) | 2007-10-22 | 2013-05-15 | Nokia Siemens Networks Oy | Method, apparatus and computer program product for service decomposition in IP-broadcast networks |
EP2362654A1 (en) | 2010-02-26 | 2011-08-31 | Panasonic Corporation | Short baseband frame headers |
CN104584510B (zh) * | 2013-07-05 | 2019-04-19 | 索尼公司 | 发送设备、发送方法、接收设备和接收方法 |
EP3022900A4 (en) | 2013-07-14 | 2017-03-22 | LG Electronics Inc. | Apparatus for transmitting broadcast signals, apparatus for receiving broadcast signals, method for transmitting broadcast signals and method for receiving broadcast signals |
US9838233B2 (en) * | 2013-08-01 | 2017-12-05 | Lg Electronics Inc. | Apparatus for transmitting broadcast signals, apparatus for receiving broadcast signals, method for transmitting broadcast signals and method for receiving broadcast signals |
WO2015026137A1 (en) * | 2013-08-19 | 2015-02-26 | Lg Electronics Inc. | Apparatus for transmitting broadcast signals, apparatus for receiving broadcast signals, method for transmitting broadcast signals and method for receiving broadcast signals |
KR101731355B1 (ko) * | 2013-09-26 | 2017-04-28 | 엘지전자 주식회사 | 시그널링 정보를 전송하기 위한 장치, 시그널링 정보를 수신하기 위한 장치, 시그널링 정보를 전송하기 위한 방법 및 시그널링 정보를 수신하기 위한 방법 |
CN109547820B (zh) * | 2013-09-27 | 2020-12-01 | Lg 电子株式会社 | 发送、接收广播信号的装置及方法 |
CN105493499B (zh) | 2013-10-28 | 2018-09-25 | Lg电子株式会社 | 发送广播信号的设备、接收广播信号的设备、发送广播信号的方法和接收广播信号的方法 |
US9264521B2 (en) * | 2013-11-01 | 2016-02-16 | Broadcom Corporation | Methods and systems for encapsulating and de-encapsulating provider backbone bridging inside upper layer protocols |
CA2921894C (en) | 2014-04-04 | 2021-03-30 | Lg Electronics Inc. | Method for transmitting broadcast signal, method for receiving broadcast signal, apparatus for transmitting broadcast signal, and apparatus for receiving broadcast signal |
PL3026918T3 (pl) | 2014-08-01 | 2019-09-30 | Lg Electronics Inc. | Sposób nadawania sygnału rozgłaszania i urządzenie do nadawania sygnału rozgłaszania wykorzystujące hermetyzację w pakietach warstwy łącza |
CN106464395B (zh) * | 2015-03-01 | 2019-07-05 | Lg电子株式会社 | 发送广播信号的设备、接收广播信号的设备、发送广播信号的方法和接收广播信号的方法 |
US10721538B2 (en) * | 2015-03-08 | 2020-07-21 | Lg Electronics Inc. | Apparatus and method for transmitting and receiving broadcast signal |
US9942000B2 (en) * | 2015-08-05 | 2018-04-10 | Samsung Electronics Co., Ltd. | Broadcast receiving apparatus and signal processing method thereof |
-
2016
- 2016-06-03 CN CN201680000833.5A patent/CN106471813B/zh active Active
- 2016-06-03 US US15/115,885 patent/US10237196B2/en active Active
- 2016-06-03 EP EP16791293.0A patent/EP3142369A4/en not_active Withdrawn
- 2016-06-03 WO PCT/KR2016/005901 patent/WO2016195412A1/ko active Application Filing
- 2016-06-03 KR KR1020167018029A patent/KR101792519B1/ko active IP Right Grant
-
2019
- 2019-01-30 US US16/262,154 patent/US10616124B2/en active Active
-
2020
- 2020-02-04 US US16/781,347 patent/US10887242B2/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20080072019A (ko) * | 2005-12-01 | 2008-08-05 | 노키아 코포레이션 | 미디어 스트림의 타임쉬프트 프리젠테이션 |
KR20100028546A (ko) * | 2007-05-04 | 2010-03-12 | 노키아 코포레이션 | 멀티미디어 컨테이너 파일의 수신 힌트 트랙으로의 미디어 스트림 기록 |
US20090055417A1 (en) * | 2007-08-20 | 2009-02-26 | Nokia Corporation | Segmented metadata and indexes for streamed multimedia data |
WO2010082768A2 (ko) * | 2009-01-14 | 2010-07-22 | 엘지전자 주식회사 | 효율적인 mac 헤더 설계 및 이를 이용한 통신 |
WO2012011722A2 (ko) * | 2010-07-19 | 2012-01-26 | 엘지전자 주식회사 | 미디어 송수신 방법 및 그를 이용한 송수신 장치 |
Non-Patent Citations (1)
Title |
---|
See also references of EP3142369A4 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108307204A (zh) * | 2017-01-13 | 2018-07-20 | 上海交通大学 | 一种基于多业务ts流的alp封装方法 |
CN108307204B (zh) * | 2017-01-13 | 2020-07-28 | 上海交通大学 | 一种基于多业务ts流的alp封装方法 |
Also Published As
Publication number | Publication date |
---|---|
CN106471813B (zh) | 2019-09-10 |
US20200177515A1 (en) | 2020-06-04 |
US20170163548A1 (en) | 2017-06-08 |
EP3142369A4 (en) | 2018-01-10 |
US10887242B2 (en) | 2021-01-05 |
KR20170003904A (ko) | 2017-01-10 |
KR101792519B1 (ko) | 2017-11-02 |
US20190166060A1 (en) | 2019-05-30 |
US10616124B2 (en) | 2020-04-07 |
EP3142369A1 (en) | 2017-03-15 |
US10237196B2 (en) | 2019-03-19 |
CN106471813A (zh) | 2017-03-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2015008986A1 (ko) | 하이브리드 방송 시스템의 방송 신호를 송신/수신하는 방법 및 장치 | |
WO2010058958A2 (ko) | 비실시간 서비스 처리 방법 및 방송 수신기 | |
WO2014209057A1 (ko) | 지상파 방송망과 인터넷 프로토콜망 연동 기반의 하이브리드 방송 시스템에서 방송 서비스의 송수신 방법 및 장치 | |
WO2016018042A1 (en) | Apparatus and method for transmitting/receiving processes of a broadcast signal | |
WO2009151265A2 (ko) | 방송 신호 수신 방법 및 수신 시스템 | |
WO2010068040A2 (ko) | 비실시간 서비스 처리 방법 및 방송 수신기 | |
WO2009151266A2 (ko) | 서비스 제공 방법 및 모바일 방송 수신기 | |
WO2010082783A2 (ko) | 비실시간 서비스 처리 방법 및 방송 수신기 | |
WO2010068033A2 (ko) | 비실시간 서비스 처리 방법 및 방송 수신기 | |
WO2017204546A1 (ko) | 방송 신호 송수신 장치 및 방법 | |
WO2016093586A1 (ko) | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 | |
WO2017014586A1 (ko) | 방송 신호 송수신 장치 및 방법 | |
WO2016089095A1 (ko) | 방송 신호 송신 방법, 방송 신호 송신 장치, 방송 신호 수신 방법 및 방송 신호 수신 장치 | |
WO2015167245A1 (ko) | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 | |
WO2011074844A2 (en) | Method of processing non-real time service and broadcast receiver | |
WO2018101566A1 (ko) | 방송 신호 송수신 장치 및 방법 | |
WO2016064150A1 (ko) | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 | |
WO2016171518A2 (ko) | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 | |
WO2010068034A2 (ko) | 비실시간 서비스 처리 방법 및 방송 수신기 | |
WO2016108606A1 (ko) | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 | |
WO2017135673A1 (ko) | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 | |
WO2016144031A1 (ko) | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 | |
WO2017209514A1 (ko) | 방송 신호 송수신 장치 및 방법 | |
WO2016108610A1 (ko) | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 | |
WO2016195412A1 (ko) | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
ENP | Entry into the national phase |
Ref document number: 20167018029 Country of ref document: KR Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15115885 Country of ref document: US |
|
REEP | Request for entry into the european phase |
Ref document number: 2016791293 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2016791293 Country of ref document: EP |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 16791293 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |